PDA

View Full Version : DIY Knoppix boot server?



Stonent
12-29-2002, 07:36 PM
I thought it would be interesting to have a script or utility that could turn a normal linux system (such as a firewall/nat/dhcp) that most of us have into a knoppix boot server without having to be running knoppix already.

Perhaps just mount the cd or ISO on that system and normal windows/linux/unix clients get their IP normally, but if one wants a boot image (pxe/etherboot) then have the server send out a kernel. That way someone could set up Linux "terminals" around their house/business that give web access that don't have to have a local drive or a separate knoppix terminal server. I've been doing a lot of playing with knoppix TS but I have to disable my local DHCP server to enable it. If the two could be combined into one system that runs a different linux (in my case RH 7.2) but still distributes Knoppix, it would be really cool.

stonent
12-29-2002, 10:18 PM
I copied the dhcpd.conf from the Knoppix /etc/ directory to my server and modified the ranges to match like this:

[root@Router etc]# cat /etc/dhcpd.conf
# dhcpd.conf for KNOPPIX terminalserver

# global settings
ddns-update-style ad-hoc;
allow booting;
allow bootp;
default-lease-time 600;
max-lease-time 7200;

subnet 192.168.0.0 netmask 255.255.255.0 {
next-server 192.168.0.1;
if substring (option vendor-class-identifier, 0, 9) = "Etherboot" { filename "
etherboot.nbi"; }
else { filename "pxelinux.0"; }
option subnet-mask 255.255.255.0;
range 192.168.0.51 192.168.0.200;
option domain-name-servers 192.168.0.1;
option routers 192.168.0.1;
}

Then I copied the contents of the tftpboot dir to the tftpboot directory on the server. I added the exports from knoppix and rebooted.

Dhcpd crashed with a bunch of errors. Turns out I was running 2.x on my server and not 3.x like on knoppix. Ok. Went to http://www.isc.org and got the latest tarball.
./configure
make
make install
reboot

BAM! All is well in da' hood.

Make sure the /cdrom is included in your mounts of course. And make sure to add the ddns-update-style ad-hoc otherwise the latest dhcpd won't start.

Stonent
12-30-2002, 12:39 AM
in your hosts.allow file, add

in.ftpd: ALL

Stonent
12-30-2002, 08:14 AM
I guess I should register so I can edit my posts.. Here are some config files I had to mess with. There were a few other things I had to tweek to make it work right that I neglected to add in the first few posts.

hosts.allow

sshd: ALL
in.tftpd: 192.168.0.0/255.255.255.0
rpc.lockd: 192.168.0.0/255.255.255.0
rquotad: 192.168.0.0/255.255.255.0
rpc.mountd: 192.168.0.0/255.255.255.0
rpc.statd: 192.168.0.0/255.255.255.0
portmap: 192.168.0.0/255.255.255.0
exportfs: 192.168.0.0/255.255.255.0
rpc.nfsd: 192.168.0.0/255.255.255.0

(Some of these I'm not sure are even valid, I added everything NFS related to be sure)

/etc/fstab (this is just what I added)

/home/shared/knoppix.iso /cdrom iso9660 loop=/dev/loop0 0 0


/etc/exports (had to add this)

/cdrom (ro,no_root_squash,async,insecure)