I am currently helping to manage a small network of Linux workstations,
each of which runs Debian. Given that each workstation has a good amount
of hard disk space on it, I generally keep software installations local.
Additionally, most of the software on these machines is managed via
Debian's apt system.
I'm looking for an easy way to get apt-get functionality across these
workstations (all run the same version of Debian.) More specifically, I
want a distributed version of "apt-get install".
Does anyone know of a pre-built set of scripts/tools that will allow me to
do this, or am I going to have to write my own?
David Ludwig | "The Linux philosophy is laugh in the face of
davidl<at>wpi.edu | danger. Oops. Wrong One. 'Do it yourself.'
http://www.oflove.com | That's it." - Linus Torvalds
I got it to work! In case anyone is interested, here's what it
looks like on SuSE 7.2 with cdrom as hdb and cdrw as hdc:
After messing around with manually editing lilo.conf with no luck, I finally used yast2 LILO configuration to make a boot floppy and got the boot parameters right.
/dev/ram hdb=ide-scsi hdc=ide-scsi ide-cd ignore=hdb ignore=hdc
Or, booting with loadlin, the dos batch file contains:
loadlin vmlinuz /dev/ram rw initrd=c:\loadlin\initrd root=/dev/hda4 ro hdc=ide-scsi hdb=ide-scsi ide-cd ignore=hdc ignore=hdb
Below is /etc/lilo.conf
Does the reference "BOOT_FILE=/boot/vmlinuz" in the append line of the global section mean that I'll boot that image regardless of my menu choices?
If anyone sees any glaring errors or anything that will kill my computer, please let me know.
I guess I should try it. As far as I can tell, there's no difference between vmlinuz and vmlinuz.suse, but I suppose I could replace on with a different kernel. I'm going to send this message before I try rebooting.
# LILO configuration file
# Start LILO global Section
# If you want to prevent console users to boot with init=/bin/bash,
# restrict usage of boot params by setting a passwd and using the option
append="BOOT_FILE=/boot/vmlinuz /dev/ram hdb=ide-scsi hdc=ide-scsi ide-cd ignore=hdb ignore=hdc"
#compact # faster, but won't work on all systems.
# End LILO global Section
image = /boot/vmlinuz
root = /dev/hda4
label = linux
initrd = /boot/initrd
image = /boot/vmlinuz.suse
root = /dev/hda4
label = suse
initrd = /boot/initrd.suse
other = /dev/hda1
label = windows
table = /dev/hda
image = /boot/memtest.bin
label = memtest86
> I believe the file /etc/init.d/boot.local is the SuSE equivalent of
> rc.local, at least boot.local is "where you can enter additional
> to be executed at boot time before changing to a run level"
> (cf 7.2 manual, page 313)
Thanks, Doug. I found that file, and it says the exact same thing at the
end of the file. Any idea why the same file also exists in /etc/rc.d/
along with boot.setup and some others?
Recently I've been thinking of picking up a linux-based handheld and
I've always been interested in the agenda vr3. It seems that their
phone numbers have been disconnected, but the web site still works, as
does their e-mail server. Are they out of business? Did they just
forget about their web site?
Anyway, I've been thinking of saving up some cash and snagging one of
the vr3's that show up on ebay constantly (just as a toy to have
around). Has anyone used one? What do you think? Should I just save
up a lot of cash and get a zarus? And can I run a palm emulator on
This e-mail is to remind you about the upcoming WLUG meeting, to be held
on Thursday, February 14th, 2002, in Kinnicutt Hall on the WPI campus.
This is our "normal" meeting location.
At this meeting, WLUG member Marc Hughes will be presenting some
information about Borland's Kylix software which runs on Linux. For more
info, consult http://www.borland.com/kylix.
I'll be showing the kylix development environment, touching briefly on
the licensing issues with their "free" version, creating a small app,
and then showing off a larger more complex application. Time
permitting, I'll quickly go over some other development environments
such as Kdeveloper and glade.
Also at this meeting, I'll give a quick financial report and we'll talk
about the results of the install fest from this past weekend. There will
be a couple of items available for raffle.
Refreshments will be available. After the meeting, we'll go to the
Boynton Restaurant for pizza and beer. This has become quite a tradition
after WLUG meetings and is a great time.
See ya on Thursday,
Worcester Linux Users' Group
Worcester, MA, USA
(Sorry about the double-post, but I feel your pain for the html email)
Under most distros you can just add it to your /etc/fstab. This file
tells linux what and how to mount various file systems. I would assume
it works under Suse.
The fstab of the machine I'm on looks like this:
/dev/rd/c0d0p3 / ext2 defaults
/dev/rd/c0d0p1 /boot ext2 defaults
/dev/rd/c0d1p6 /data ext2 defaults
/dev/rd/c0d1p2 /home ext2 defaults
/dev/rd/c0d1p5 /tmp ext2 defaults
/dev/rd/c0d1p1 /usr ext2 defaults
/dev/rd/c0d1p3 /var ext2 defaults
/dev/fd0 /mnt/floppy auto noauto,owner
none /proc proc defaults
none /dev/pts devpts gid=5,mode=620
/dev/rd/c0d0p2 swap swap defaults
/dev/hda1 /mnt/windows vfat defaults
Which is a horrible example for a newbie question since the weird dev
devices are hardware raid. But the last line is the interesting one.
It tells the system to mount /dev/hda1 on /mnt/windows using the vfat
There are a bunch of options you can put in there like making it
user-mountable, read all about those in the man pages (man fstab)
From: Gregory Avedissian [mailto:firstname.lastname@example.org]
Sent: Tuesday, February 12, 2002 10:46 AM
Subject: [Wlug] Newbie question
Where do I put the command to mount my windows partition in linux,
automatically at bootup, so I don't have to keep typing it? Using SuSE
7.2 and usually booting with loadlin, occasionally booting with floppy.
Thanks in advance,
P.S. More questions to come as I figure out how to ask them.
Fair Warning: I own a cdrw and a scanner.
Wlug mailing list