Knoppix Documentation Wiki - User contributions [en]

KNOPPIX Terminal Server

2008-04-21T20:27:10Z

Plouj: /* Updating */

==Preamble==

*This page describes how to boot KNOPPIX 5.1.1 (outdated) from the network using Samba (as opposed to NFS).
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a busy day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
We start by configuring a TFTP server. It will serve the bootloader (PXELINUX) files which our client machines will load from the network and run even before starting the Linux/KNOPPIX kernel.

For this guide, we want our TFTP server to use <tt>/var/lib/tftpboot/</tt> as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

For example, tftp-hpa can be started from inetd with this line in <tt>/etc/inetd.conf</tt>:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Next we need to setup a Samba share which will host the KNOPPIX CD filesystem. The network client machines will access this share as if they were accessing the files from a regular KNOPPIX Live CD.

Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share-5.1.1]
comment = Knoppix 5.1.1 Boot Data
path = /shares/knoppix-term-5.1.1
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
After that, we setup a DHCP server. It will provide required values that allow the client to configure its network interface, and to download a bootfile.

'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253

Example entry in the dhcpd.conf file:
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Now it's time to populate the Samba and TFTP server shares with relevant files.

Start by downloading a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Temporarily mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it in the just created directory
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot-5.1.1.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel-5.1.1

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term-5.1.1/KNOPPIX

Cleanup the temporarily mounted directory
umount /mnt/iso

== Configure PXELINUX ==
PXELINUX is a boot loader which actually loads the Linux/KNOPPIX kernel on the client machines and tell them where to find the root filesystem.
Thus we configure PXELINUX with relevant information.

Add the following lines to your <tt>/var/lib/tftpboot/pxelinux.cfg/default</tt> file:
LABEL Knoppix 5.1.1 CIFS
KERNEL knoppix/kernel-5.1.1
APPEND secure nfsdir=//192.168.12.253/knoppix_share-5.1.1 nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot-5.1.1.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your <tt>pxelinux.cfg/default</tt> file

If you would like to have a text-only client terminal, then you can make a copy of the above text in the <tt>/var/lib/tftpboot/pxelinux.cfg/default</tt> file and just add "2" to the knoppix options:
LABEL Knoppix 5.1.1 CIFS
KERNEL knoppix/kernel-5.1.1
APPEND secure nfsdir=//192.168.12.253/knoppix_share-5.1.1 nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot-5.1.1.gz quiet 2 BOOT_IMAGE=knoppix

== Configure Client Machines to boot from PXE ==
This is a crucial step. Unless your machines can actually boot from the network,
none of the above is going to be of any use!
Unfortunately, each and every BIOS has its own way of being configured for PXE booting
and it's not feasible to document any of that here.
If you do not have this working, a good start would be to read [http://www.kegel.com/linux/pxe.html Dan Kegel's Remote Network Boot via PXE page].

== Testing ==
After all the hard work, it is time to enjoy the fruits of your labor.

*Connect a PXE enabled test machine to the 192.168.12.0 network
*power it on
*wait...
*enjoy!

== Updating ==
Updating the Knoppix Terminal server to newer versions of Knoppix is difficult, but theoretically doable. In general, you have to re-do the following steps:
* repeat the [[#Samba Share Setup]] to create a share for storing the new Knoppix disk image
* re-do the [[#Setting Up Knoppix Boot files]] step in new directories
** this is where it gets hard. There is no updated miniroot available for CIFS network booting. Based on initial investigation, creating an updated miniroot for Knoppix 5.3.1 will be non-trivial. One could start this task by examining the differences between the vanilla 5.1.1 miniroot and the cifs 5.1.1 miniroot as follows:

cp /var/lib/tftpboot/knoppix/miniroot-5.1.1.gz /tmp/
gunzip /tmp/miniroot-5.1.1.gz
mkdir /mnt/cifs-miniroot
mount -o loop /tmp/miniroot-5.1.1 /mnt/cifs-miniroot
mkdir /mnt/knoppix-5.1.1-cd
mount -o loop KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/knoppix-5.1.1-cd/
mkdir /mnt/vanilla-5.1.1-miniroot
cp /mnt/knoppix-5.1.1-cd/boot/isolinux/minirt.gz /tmp
gunzip /tmp/minirt.gz
mount -o loop /tmp/minirt /mnt/vanilla-5.1.1-miniroot
# remove irrelevant device files
rm -rf /mnt/{vanilla-5.1.1,cifs}-miniroot/dev
diff -qr /mnt/vanilla-5.1.1-miniroot /mnt/cifs-miniroot
diff: /mnt/vanilla-5.1.1-miniroot/bin: No such file or directory
diff: /mnt/cifs-miniroot/bin: No such file or directory
diff: /mnt/vanilla-5.1.1-miniroot/boot: No such file or directory
diff: /mnt/cifs-miniroot/boot: No such file or directory
Only in /mnt/vanilla-5.1.1-miniroot/etc: init
Only in /mnt/cifs-miniroot/etc: inittab.secure
diff: /mnt/vanilla-5.1.1-miniroot/etc/ld.so.conf: No such file or directory
diff: /mnt/cifs-miniroot/etc/ld.so.conf: No such file or directory
Files /mnt/vanilla-5.1.1-miniroot/etc/mtab and /mnt/cifs-miniroot/etc/mtab differ
Only in /mnt/cifs-miniroot/etc: nsswitch.conf
Only in /mnt/cifs-miniroot/etc: rpc
Only in /mnt/cifs-miniroot/etc: services
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: bin
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: boot
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: etc
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: lib
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: opt
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: sbin
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: usr
Only in /mnt/vanilla-5.1.1-miniroot/KNOPPIX: var
diff: /mnt/vanilla-5.1.1-miniroot/lib: No such file or directory
Files /mnt/vanilla-5.1.1-miniroot/linuxrc and /mnt/cifs-miniroot/linuxrc differ
Only in /mnt/vanilla-5.1.1-miniroot/media: fd0
Only in /mnt/vanilla-5.1.1-miniroot/media: hd
Only in /mnt/vanilla-5.1.1-miniroot/media: test
Only in /mnt/vanilla-5.1.1-miniroot/modules: a100u2w.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: advansys.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: aic7xxx.ko
Only in /mnt/cifs-miniroot/modules: aufs.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: BusLogic.ko
Only in /mnt/cifs-miniroot/modules: cloop.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: dc395x.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: dtc.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: eata.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: ehci-hcd.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: fdomain.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: ff-memless.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: gdth.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: ieee1394.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: initio.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: libusual.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: loop.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: mptbase.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: mptscsih.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: NCR53c406a.ko
Only in /mnt/cifs-miniroot/modules: net
Only in /mnt/vanilla-5.1.1-miniroot/modules: ohci1394.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: ohci-hcd.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: pas16.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: psi240i.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: sbp2.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: sym53c8xx.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: t128.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: tmscsim.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: u14-34f.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: uhci-hcd.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: ultrastor.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: usbcore.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: usbhid.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: usb-storage.ko
Only in /mnt/vanilla-5.1.1-miniroot/modules: wd7000.ko
diff: /mnt/vanilla-5.1.1-miniroot/opt: No such file or directory
diff: /mnt/cifs-miniroot/opt: No such file or directory
diff: /mnt/cifs-miniroot/sbin: No such file or directory
Only in /mnt/vanilla-5.1.1-miniroot/static: fusermount
Only in /mnt/cifs-miniroot/static: ifconfig
diff: /mnt/cifs-miniroot/static/init: No such file or directory
Files /mnt/vanilla-5.1.1-miniroot/static/insmod and /mnt/cifs-miniroot/static/insmod differ
Only in /mnt/cifs-miniroot/static: mount
Only in /mnt/cifs-miniroot/static: mount.cifs
Only in /mnt/vanilla-5.1.1-miniroot/static: ntfs-3g
Only in /mnt/cifs-miniroot/static: portmap
Only in /mnt/cifs-miniroot/static: pump
Only in /mnt/vanilla-5.1.1-miniroot/static: rmmod
diff: /mnt/cifs-miniroot/static/sh: No such file or directory
diff: /mnt/vanilla-5.1.1-miniroot/usr: No such file or directory
diff: /mnt/cifs-miniroot/usr: No such file or directory
Only in /mnt/cifs-miniroot: var

* finally [[#Configure PXELINUX]] to add a new menu entry to point to the new boot files

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://pxe.dev.aboveaverageurl.com/index.php/PXE_Booting/Knoppix a similar, but outdated guide]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]
* [http://www.kernel.org/pub/software/network/tftp/ tftp-hpa]
* [http://dhcpcd.berlios.de/ dhcpcd]
* [http://us3.samba.org/samba/ samba]

[[Category:Guide]]
[[Category:Booting]]
[[Category:Networking]]

KNOPPIX Terminal Server

2008-04-21T15:20:39Z

Plouj: /* Configure Client Machines' PXE Booting */

KNOPPIX Terminal Server

2008-04-18T16:14:50Z

Plouj: /* TFTP Server Setup */

KNOPPIX Terminal Server

2008-04-18T16:14:30Z

Plouj: formatting

KNOPPIX Terminal Server

2008-04-18T16:03:04Z

Plouj: /* References */

User:Plouj

2008-04-18T15:22:25Z

Plouj: New page: My real name is Michael Ploujnikov. My personal website is: http://plouj.com

My real name is Michael Ploujnikov.

My personal website is: http://plouj.com

KNOPPIX Terminal Server

2008-04-18T15:21:11Z

Plouj: /* Preamble */ specified version

KNOPPIX Terminal Server

2008-04-18T15:10:21Z

Plouj: /* Configure PXELINUX */

==Preamble==

*This page describes how to boot KNOPPIX off the network using Samba (as opposed to NFS).
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
We start by configuring a TFTP server. It will serve the bootloader (PXELINUX) files which our client machines will load from the network and run even before starting the Linux/KNOPPIX kernel.

For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

For example, tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Next we need to setup a Samba share which will host the KNOPPIX CD filesystem. The network client machines will access this share as if they were accessing the files from a regular KNOPPIX Live CD.

Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share-5.1.1]
comment = Knoppix 5.1.1 Boot Data
path = /shares/knoppix-term-5.1.1
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
After that, we setup a DHCP server. It will provide required values that allow the client to configure its network interface, and to download a bootfile.

'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253

Example entry in the dhcpd.conf file:
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Now it's time to populate the Samba and TFTP server shares with relevant files.

Start by downloading a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Temporarily mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it in the just created directory
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot-5.1.1.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel-5.1.1

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term-5.1.1/KNOPPIX

Cleanup the temporarily mounted directory
umount /mnt/iso

== Configure PXELINUX ==
PXELINUX is a boot loader which actually loads the Linux/KNOPPIX kernel on the client machines and tell them where to find the root filesystem.
Thus we configure PXELINUX with relevant information.

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix 5.1.1 CIFS
KERNEL knoppix/kernel-5.1.1
APPEND secure nfsdir=//192.168.12.253/knoppix_share-5.1.1 nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot-5.1.1.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

If you would like to have a text-only client terminal, then you can make a copy of the above text in the /var/lib/tftpboot/pxelinux.cfg/default file and just add "2" to the knoppix options:
LABEL Knoppix 5.1.1 CIFS
KERNEL knoppix/kernel-5.1.1
APPEND secure nfsdir=//192.168.12.253/knoppix_share-5.1.1 nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot-5.1.1.gz quiet 2 BOOT_IMAGE=knoppix

== Configure Client Machines' PXE Booting ==
This is a crucial step. Unless your machines can actually boot from the network,
none of the above is going to be of any use!
Unfortunately, each and every BIOS has its own way of being configured for PXE booting
and it's not feasible to document any of that here.
If you do not have this working, a good start would be to read [http://www.kegel.com/linux/pxe.html Dan Kegel's Remote Network Boot via PXE page].

== Testing ==
After all the hard work, it is time to enjoy the fruits of your labor.

*Connect a PXE enabled test machine to the 192.168.12.0 network
*power it on
*wait...
*enjoy!

== Updating ==
Updating the Knoppix Terminal server to newer versions of Knoppix is doable. You only have to re-do the following steps:
* repeat the [[#Samba Share Setup]] to create a share for storing the new Knoppix disk image
* re-do the [[#Setting Up Knoppix Boot files]] step in new directories
** this actually might not work since the miniroot hasn't been updated to the latest Knoppix version, yet
* finally [[#Configure PXELINUX]] to add a new menu entry to point to the new boot files

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]
* [http://www.kernel.org/pub/software/network/tftp/ tftp-hpa]
* [http://dhcpcd.berlios.de/ dhcpcd]
* [http://us3.samba.org/samba/ samba]

[[Category:Guide]]
[[Category:Booting]]
[[Category:Networking]]

KNOPPIX Terminal Server

2008-04-18T15:08:25Z

Plouj: made Knoppix version specific and some other minor improvements

==Preamble==

*This page describes how to boot KNOPPIX off the network using Samba (as opposed to NFS).
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
We start by configuring a TFTP server. It will serve the bootloader (PXELINUX) files which our client machines will load from the network and run even before starting the Linux/KNOPPIX kernel.

For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

For example, tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Next we need to setup a Samba share which will host the KNOPPIX CD filesystem. The network client machines will access this share as if they were accessing the files from a regular KNOPPIX Live CD.

Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share-5.1.1]
comment = Knoppix 5.1.1 Boot Data
path = /shares/knoppix-term-5.1.1
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
After that, we setup a DHCP server. It will provide required values that allow the client to configure its network interface, and to download a bootfile.

'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253

Example entry in the dhcpd.conf file:
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Now it's time to populate the Samba and TFTP server shares with relevant files.

Start by downloading a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Temporarily mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it in the just created directory
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot-5.1.1.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel-5.1.1

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term-5.1.1/KNOPPIX

Cleanup the temporarily mounted directory
umount /mnt/iso

== Configure PXELINUX ==
PXELINUX is a boot loader which actually loads the Linux/KNOPPIX kernel on the client machines and tell them where to find the root filesystem.
Thus we configure PXELINUX with relevant information.

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix 5.1.1 CIFS
KERNEL knoppix/kernel-5.1.1
APPEND secure nfsdir=//192.168.12.253/knoppix_share-5.1.1 nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot-5.1.1.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
This is a crucial step. Unless your machines can actually boot from the network,
none of the above is going to be of any use!
Unfortunately, each and every BIOS has its own way of being configured for PXE booting
and it's not feasible to document any of that here.
If you do not have this working, a good start would be to read [http://www.kegel.com/linux/pxe.html Dan Kegel's Remote Network Boot via PXE page].

== Testing ==
After all the hard work, it is time to enjoy the fruits of your labor.

*Connect a PXE enabled test machine to the 192.168.12.0 network
*power it on
*wait...
*enjoy!

== Updating ==
Updating the Knoppix Terminal server to newer versions of Knoppix is doable. You only have to re-do the following steps:
* repeat the [[#Samba Share Setup]] to create a share for storing the new Knoppix disk image
* re-do the [[#Setting Up Knoppix Boot files]] step in new directories
** this actually might not work since the miniroot hasn't been updated to the latest Knoppix version, yet
* finally [[#Configure PXELINUX]] to add a new menu entry to point to the new boot files

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]
* [http://www.kernel.org/pub/software/network/tftp/ tftp-hpa]
* [http://dhcpcd.berlios.de/ dhcpcd]
* [http://us3.samba.org/samba/ samba]

[[Category:Guide]]
[[Category:Booting]]
[[Category:Networking]]

KNOPPIX Terminal Server

2008-04-18T14:56:57Z

Plouj:

==Preamble==

*This page describes how to boot KNOPPIX off the network using Samba (as opposed to NFS).
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
We start by configuring a TFTP server. It will serve the bootloader (PXELINUX) files which our client machines will load from the network and run even before starting the Linux/KNOPPIX kernel.

For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

For example, tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Next we need to setup a Samba share which will host the KNOPPIX CD filesystem. The network client machines will access this share as if they were accessing the files from a regular KNOPPIX Live CD.

Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /shares/knoppix-term
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
After that, we setup a DHCP server. It will provide required values that allow the client to configure its network interface, and to download a bootfile.

'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253

Example entry in the dhcpd.conf file:
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Now it's time to populate the Samba and TFTP server shares with relevant files.

Start by downloading a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term/KNOPPIX

== Configure PXELINUX ==
PXELINUX is a boot loader which actually loads the Linux/KNOPPIX kernel on the client machines and tell them where to find the root filesystem.
Thus we configure PXELINUX with relevant information.

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//192.168.12.253/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
This is a crucial step. Unless your machines can actually boot from the network,
none of the above is going to be of any use!
Unfortunately, each and every BIOS has its own way of being configured for PXE booting
and it's not feasible to document any of that here.
If you do not have this working, a good start would be to read [http://www.kegel.com/linux/pxe.html Dan Kegel's Remote Network Boot via PXE page].

== Testing ==
After all the hard work, it is time to enjoy the fruits of your labor.

*Connect a PXE enabled test machine to the 192.168.12.0 network
*power it on
*wait...
*enjoy!

== Updating ==
Updating the Knoppix Terminal server to newer versions of Knoppix is doable. You only have to re-do the following steps:
* repeat the [[#Samba Share Setup]] to create a share for storing the new Knoppix disk image
* re-do the [[#Setting Up Knoppix Boot files]] step in new directories
** this actually might not work since the miniroot hasn't been updated to the latest Knoppix version, yet
* finally [[#Configure PXELINUX]] to add a new menu entry to point to the new boot files

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]
* [http://www.kernel.org/pub/software/network/tftp/ tftp-hpa]
* [http://dhcpcd.berlios.de/ dhcpcd]
* [http://us3.samba.org/samba/ samba]

[[Category:Guide]]
[[Category:Booting]]
[[Category:Networking]]

KNOPPIX Terminal Server

2008-04-18T14:41:38Z

Plouj:

==Preamble==

*This page describes how to boot KNOPPIX off the network using Samba (as opposed to NFS).
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
We start by configuring a TFTP server. It will serve the bootloader (PXELINUX) files which our client machines will load from the network and run even before starting the Linux/KNOPPIX kernel.

For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

For example, tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Next we need to setup a Samba share which will host the KNOPPIX CD filesystem. The network client machines will access this share as if they were accessing the files from a regular KNOPPIX Live CD.

Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /shares/knoppix-term
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
After that, we setup a DHCP server. It will provide required values that allow the client to configure its network interface, and to download a bootfile.

'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253

Example entry in the dhcpd.conf file:
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Now it's time to populate the Samba and TFTP server shares with relevant files.

Start by downloading a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term/KNOPPIX

== Configure PXELINUX ==
PXELINUX is a boot loader which actually loads the Linux/KNOPPIX kernel on the client machines and tell them where to find the root filesystem.
Thus we configure PXELINUX with relevant information.

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//192.168.12.253/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
This is a crucial step. Unless your machines can actually boot from the network,
none of the above is going to be of any use!
Unfortunately, each and every BIOS has its own way of being configured for PXE booting
and it's not feasible to document any of that here.
If you do not have this working, a good start would be to read [http://www.kegel.com/linux/pxe.html Dan Kegel's Remote Network Boot via PXE page].

== Testing ==
After all the hard work, it is time to enjoy the fruits of your labor.

*Connect a PXE enabled test machine to the 192.168.12.0 network
*power it on
*wait...
*enjoy!

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]
* [http://www.kernel.org/pub/software/network/tftp/ tftp-hpa]
* [http://dhcpcd.berlios.de/ dhcpcd]
* [http://us3.samba.org/samba/ samba]

[[Category:Guide]]
[[Category:Booting]]
[[Category:Networking]]

KNOPPIX Terminal Server

2007-04-18T02:28:07Z

Plouj: added links to important programs

==Preamble==

*This page describes how to boot KNOPPIX off the network using Samba (as opposed to NFS).
**This page needs to be categorized.
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
We start by configuring a TFTP server. It will serve the bootloader (PXELINUX) files which our client machines will load from the network and run even before starting the Linux/KNOPPIX kernel.

For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

For example, tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Next we need to setup a Samba share which will host the KNOPPIX CD filesystem. The network client machines will access this share as if they were accessing the files from a regular KNOPPIX Live CD.

Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /shares/knoppix-term
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
After that, we setup a DHCP server. It will provide required values that allow the client to configure its network interface, and to download a bootfile.

'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253

Example entry in the dhcpd.conf file:
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Now it's time to populate the Samba and TFTP server shares with relevant files.

Start by downloading a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term/KNOPPIX

== Configure PXELINUX ==
PXELINUX is a boot loader which actually loads the Linux/KNOPPIX kernel on the client machines and tell them where to find the root filesystem.
Thus we configure PXELINUX with relevant information.

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//192.168.12.253/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
This is a crucial step. Unless your machines can actually boot from the network,
none of the above is going to be of any use!
Unfortunately, each and every BIOS has its own way of being configured for PXE booting
and it's not feasible to document any of that here.
If you do not have this working, a good start would be to read [http://www.kegel.com/linux/pxe.html Dan Kegel's Remote Network Boot via PXE page].

== Testing ==
After all the hard work, it is time to enjoy the fruits of your labor.

*Connect a PXE enabled test machine to the 192.168.12.0 network
*power it on
*wait...
*enjoy!

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]
* [http://www.kernel.org/pub/software/network/tftp/ tftp-hpa]
* [http://dhcpcd.berlios.de/ dhcpcd]
* [http://us3.samba.org/samba/ samba]

KNOPPIX Terminal Server

2007-04-04T14:18:22Z

Plouj: improved DHCP server section

KNOPPIX Terminal Server

2007-04-04T03:48:43Z

Plouj: more refactoring, making it easier to read, fixing formatting, adding useful descriptions

==Preamble==

*This page describes how to boot KNOPPIX off the network using Samba (as opposed to NFS).
**This page needs to be categorized.
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
We start by configuring a TFTP server. It will serve the bootloader (PXELINUX) files which our client machines will load from the network and run even before starting the Linux/KNOPPIX kernel.

For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

For example, tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Next we need to setup a Samba share which will host the KNOPPIX CD filesystem. The network client machines will access this share as if they were accessing the files from a regular KNOPPIX Live CD.

Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /shares/knoppix-term
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
The DHCP server will help our network clients configure their TCP/IP stack, and tell them which bootloader files to get and frp, where.

'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253

Example entry in the dhcpd.conf file:
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Now it's time to populate the Samba and TFTP server shares with relevant files.

Start by downloading a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term/KNOPPIX

== Configure PXELINUX ==
PXELINUX is a boot loader which actually loads the Linux/KNOPPIX kernel on the client machines and tell them where to find the root filesystem.
Thus we configure PXELINUX with relevant information.

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//192.168.12.253/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
This is a crucial step. Unless your machines can actually boot from the network,
none of the above is going to be of any use!
Unfortunately, each and every BIOS has its own way of being configured for PXE booting
and it's not feasible to document any of that here.
If you do not have this working, a good start would be to read [http://www.kegel.com/linux/pxe.html Dan Kegel's Remote Network Boot via PXE page].

== Testing ==
After all the hard work, it is time to enjoy the fruits of your labor.

*Connect a PXE enabled test machine to the 192.168.12.0 network
*power it on
*wait...
*enjoy!

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]

KNOPPIX Terminal Server

2007-04-04T03:01:20Z

Plouj: /* Preamble */ better word choice

==Preamble==

*This page describes how to boot KNOPPIX off the network using Samba (as opposed to NFS).
**This page needs to be categorized.
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /shares/knoppix-term
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253
Example entry for dhcpd.conf below
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Download a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term/KNOPPIX

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//192.168.12.253/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
Making sure that your client machines actually boot from the network is an important step.
However, it is out of the scope of this document.
Consider reading [http://www.kegel.com/linux/pxe.html Dan Kegel's page] about this.

== Testing ==
At this point, you should be able to boot Knoppix over the network no your test machines connected to the 192.168.12.0 network. Go ahead, try it!

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]

KNOPPIX Terminal Server

2007-04-04T03:00:32Z

Plouj: /* Preamble */ rephrased and fixed spelling

==Preamble==

*This page documents how to boot KNOPPIX off the network using Samba (as opposed to NFS).
**This page needs to be categorized.
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /shares/knoppix-term
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253
Example entry for dhcpd.conf below
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Download a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term/KNOPPIX

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//192.168.12.253/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
Making sure that your client machines actually boot from the network is an important step.
However, it is out of the scope of this document.
Consider reading [http://www.kegel.com/linux/pxe.html Dan Kegel's page] about this.

== Testing ==
At this point, you should be able to boot Knoppix over the network no your test machines connected to the 192.168.12.0 network. Go ahead, try it!

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]

Booting

2007-03-30T21:17:25Z

Plouj: fixed cd-rom/dvd-rom reason

En español [[botaje]].
----
=Introduction=
In computing, [[booting]] is a process that starts operating systems when the user turns on a computer system. The origin of the word may be from the wild west in America. The image of a cowboy pulling himself up by his [[booting | bootstraps]] after a long night drinking is the usual idea. You may also hear [[booting]] refered to as [[booting |bootstrapping]] for this very reason. The computer is trying to pull itself up by its [[booting | bootstraps]].

Gnoppix during the booting shows the [[syslinux bootprompt]]:

boot>

At the [[syslinux bootprompt]], a user can type one or more [[Cheat Codes]]. The additional [[Cheat Codes|codes]] alter the default boot sequence. After the [[Cheat Codes]] are entered the Enter key is used to start the [[booting|bootstrapping]] process. If the default options are OK, then the user can press Enter without typing [[Cheat Codes]]. For example, the default keyboard in the German version of [[knoppix]] is great for German speaking individuals. This person would hit the Enter key to take the defaults and starte [[knoppix]]. Howwever, an English speaking person would type

linux lang=en
at the boot prompt.

See : [http://www.wikipedia.org/wiki/booting booting on Wikipedia]

=Different methods of boot=
->here we describe methods that can boot knoppix as it was on cd (iso or cloop(KNOPPIX))

==why not booting the usual way:==

->some people do not have the cd writer

->some people do not have a dvd writer and want to use the dvd-image

->faster on hdd(the hdd is normaly faster than a cd/dvd drive)

->some computers do not have a cd-rom/dvd-rom drive

->consume less power on laptops(hdd consume less than cd)

===limits:===
as it boots from hd... there are several issues with:

->partitioning

->fsck of the partition where reside the knoppix image

->security reasons (booting from cd can be prevented by the bios but here if you can boot from hd you can boot knoppix)

==CD/dvd based bootloader==
->use the cd in order to boot an iso image

==Hdd based boot loader==
->boot from the hd
===On Linux system===
this method is caled "linux" because it needs

->grub,lilo or another linux bootloader installed

->a filesystem readeable by grub/lilo/others (ext2/reiserfs...)
====Grub====

====Lilo====
====Others boot loaders====

==Others boot methods==
===Pxe===
[[KNOPPIX_Terminal_Server]]
===floppy===
->works by storing the boot loader on a floppy

[[Category:Booting|*]]

Booting

2007-03-30T21:15:59Z

Plouj: added link to KNOPPIX_Terminal_Server

En español [[botaje]].
----
=Introduction=
In computing, [[booting]] is a process that starts operating systems when the user turns on a computer system. The origin of the word may be from the wild west in America. The image of a cowboy pulling himself up by his [[booting | bootstraps]] after a long night drinking is the usual idea. You may also hear [[booting]] refered to as [[booting |bootstrapping]] for this very reason. The computer is trying to pull itself up by its [[booting | bootstraps]].

Gnoppix during the booting shows the [[syslinux bootprompt]]:

boot>

At the [[syslinux bootprompt]], a user can type one or more [[Cheat Codes]]. The additional [[Cheat Codes|codes]] alter the default boot sequence. After the [[Cheat Codes]] are entered the Enter key is used to start the [[booting|bootstrapping]] process. If the default options are OK, then the user can press Enter without typing [[Cheat Codes]]. For example, the default keyboard in the German version of [[knoppix]] is great for German speaking individuals. This person would hit the Enter key to take the defaults and starte [[knoppix]]. Howwever, an English speaking person would type

linux lang=en
at the boot prompt.

See : [http://www.wikipedia.org/wiki/booting booting on Wikipedia]

=Different methods of boot=
->here we describe methods that can boot knoppix as it was on cd (iso or cloop(KNOPPIX))

==why not booting the usual way:==

->some people do not have the cd writer

->some people do not have a dvd writer and want to use the dvd-image

->faster on hdd(the hdd is normaly faster than a cd/dvd drive)

->can use the cd-rom/dvd-rom drive

->consume less power on laptops(hdd consume less than cd)

===limits:===
as it boots from hd... there are several issues with:

->partitioning

->fsck of the partition where reside the knoppix image

->security reasons (booting from cd can be prevented by the bios but here if you can boot from hd you can boot knoppix)

==CD/dvd based bootloader==
->use the cd in order to boot an iso image

==Hdd based boot loader==
->boot from the hd
===On Linux system===
this method is caled "linux" because it needs

->grub,lilo or another linux bootloader installed

->a filesystem readeable by grub/lilo/others (ext2/reiserfs...)
====Grub====

====Lilo====
====Others boot loaders====

==Others boot methods==
===Pxe===
[[KNOPPIX_Terminal_Server]]
===floppy===
->works by storing the boot loader on a floppy

[[Category:Booting|*]]

KNOPPIX Terminal Server

2007-03-30T17:34:37Z

Plouj: major renovation

==Preamble==

*This page will be used to document and describe how to boot KNOPPIX off the network using Samba as opposed to NFS.
**This page needs to be catagorized.
*The original author of this document, [[User:Rjent|Rjent]], moved his efforts to working on http://live.debian.net/ .
*You are still welcome to contact him about the model however (please bare with him since he has a day job).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net

== TFTP Server Setup ==
For this guide, we want our TFTP server to use /var/lib/tftpboot/ as the root directory.
How you configure that depends on which tftp server you use (tftp-hpa, atftp, or other)
and how you run it (inetd, xinetd, init daemon, ...).

tftp-hpa can be started from inetd with this line:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

== Samba Share Setup ==
Samba provides the CIFS services out of the box. All we have to do is configure a share.
An example smb.conf is listed below:
[global]
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /shares/knoppix-term
read only = Yes
guest ok = Yes
'''Note1:''' you need 'security = share' for (passwordless) guest access to work

'''Note2:''' you need to make sure that there exists a Unix user 'guest' on the server (in /etc/passwd)

'''Note3:''' After changes to smb.conf you will need to restart samba services.

== DHCP Server Setup ==
'''Note:''' This guide will assume that your server machine has an IP of 192.168.12.253
Example entry for dhcpd.conf below
subnet 192.168.12.0 netmask 255.255.255.0 {
range 192.168.12.251 192.168.12.252;
option broadcast-address 192.168.12.255;
filename "/pxelinux.0";
}
'''Note2:''' Make sure to use the subnet, netmask, broadcast-address and the IP range of your test network.

'''Note2:''' After changes to dhcpd.conf restart or reload dhcp services.

== Setting Up Knoppix Boot files ==
Download a [http://www.knopper.net/knoppix-mirrors/index-en.html KNOPPIX 4.0.2 (or newer) iso]

Mount it (or burn it on a CD)
mount -o loop /iso/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso /mnt/iso

Setup a Knoppix terminal pxeboot subdirectory
mkdir /var/lib/tftpboot/knoppix

Download miniroot.gz from http://knoppix.manty.net and put it
wget http://knoppix.manty.net/files/511/miniroot.gz -O /var/lib/tftpboot/knoppix/miniroot.gz

Copy the kernel from the Knoppix CD to the pxeboot subdirectory
cp /mnt/iso/boot/isolinux/linux /var/lib/tftpboot/knoppix/kernel

Copy the KNOPPIX folder from the KNOPPIX CD to a shared directory on the server
rsync -a --delete /mnt/iso/KNOPPIX/ /shares/knoppix-term/KNOPPIX

Add the following lines to your /var/lib/tftpboot/pxelinux.cfg/default file:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//192.168.12.253/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

'''Note:''' the above APPEND line must appear as a single line in your pxelinux.cfg/default file

== Configure Client Machines' PXE Booting ==
Making sure that your client machines actually boot from the network is an important step.
However, it is out of the scope of this document.
Consider reading [http://www.kegel.com/linux/pxe.html Dan Kegel's page] about this.

== Testing ==
At this point, you should be able to boot Knoppix over the network no your test machines connected to the 192.168.12.0 network. Go ahead, try it!

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.
* [http://live.debian.net/ Debian Live]
* [http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf Hybrid Booting Model]
* [http://www.kegel.com/linux/pxe.html Remote Network Boot via PXE]

KNOPPIX Terminal Server

2007-03-30T16:31:31Z

Plouj: corrections and some formatting fixes

==Preamble==

*This page will be used to document and describe how to boot KNOPPIX off the network using Samba as opposed to NFS.
**The page will pull from several resources to provide an official reference at the KNOPPIX site for all to use.
**Just starting so page will be in progress for a bit and will need to be catagorized.
*You are welcome to contact me on model (I have a day job, so please bare with me see [[User:Rjent|Rjent]]).

==Model==

* Most of the this information is an exert from a paper on the model at http://www.mgr3.k12.mo.us/~rjn103s/HybridNotes-20060504-1.pdf
The methodology for the hybrid environment uses a Common Internet File System (CIFS)
to boot up KNOPPIX. The base work for this model utilizes existing resources and information
from http://knoppix.manty.net . The setup information provided here
assumes you have PXE booting via TFTP already setup on the boot
server. The rest is as follows:
* KNOPPIX:
Download KNOPPIX 4.0.2 (or newer) and burn to a CD.

Download the miniroot.gz and integrate for the pxe bootup.
To do this, place the miniroot.gz in the /tftpboot/hybrid/pxeboot/ directory.
Make a directory under /tftpboot/hybrid/pxeboot/
called knoppix and copy the /boot/isolinux/linux file from the
KNOPPIX CD to /tftpboot/hybrid/pxeboot/knoppix/

Copy the KNOPPIX folder from the KNOPPIX CD to a location on server of
/hybrid/knoppixshare

Modify the pxe boot menu located at /tftpboot/hybrid/pxeboot/pxelinux.cfg
with the below addition:
LABEL Knoppix CIFS
KERNEL knoppix/linux
APPEND secure nfsdir=//xxx.xxx.xxx.xxx/knoppix_share nodhcp lang=en ramdisk_size=100000 init=/etc/init apm=poweroff nomce vga=791 initrd=miniroot.gz quiet BOOT_IMAGE=knoppix

Note1: the above APPEND line must appear as a single line in your pxelinux.cfg/default file

Note2: xxx.xxx.xxx.xxx is the IP address of the server running the samba share.

* Samba
Samba provides the CIFS services, so we setup a share on server xxx.xxx.xxx.xxx.
An example smb.conf is listed below:
[global]
workgroup = HYBRIDGROUP
netbios name = HYBRIDSERVER
security = share
guest account = nobody
[knoppix_share]
comment = Knoppix Boot Data
path = /hybrid/knoppix_share
read only = Yes
guest ok = Yes
Note: After changes to smb.conf you will need to restart samba services.

* DHCP Services
Example entry for dhcpd.conf below
group {
filename "hybrid/pxeboot/pxelinux.0";
host hybrid51 {
hardware ethernet MA:CA:DD:RE:SS:ED; fixedaddress xxx.xxx.xxx.xxx;
}
}
Note: After changes to dhcpd.conf restart or reload dhcp services.

At this point, you should be ready to test boot your KNOPPIX
session.

==References==
* [http://knoppix.manty.net/ The KNOPPIX® terminal server over SMB/CIFS page] - The place where all the starting work was derived.