Hi Rolf-Werner,
> yes, this was the way to do it. Runs well like this. The only problem
> remaining is the configuration of the rest of the services which I had
> tailored to LTSP 4.2. For instance, KDM is coming up, it doesn't find
> the graphics drivers etc. But it helped a lot.
If I get you right you mount the same root filesystem to both the 4.2
and 5 clients? I can' recall anymore how I did this years ago with
LTSP 4.2 and 5 in parallel (maybe I then had two LTSP Servers) but I
think you could adopt my solution for the two CPU architectures (486
VIA and x86 Intel Atoms; also they have a different graphic chip/card)
in my client pool.
I use Gentoo Linux and its LTSP 5 package which comes with some
scripts to create Chroots for the client root filesystem. So I set up
two Chroots for my two client variants where I installed a tailored
Gentoo Linux for them.
My /var/lib/tftpboot/pxelinux.0 is the pxelinux.0 from the syslinux
package and in /var/lib/tftpboot/pxelinux.cfg/ I have two menu files
for the syslinux bootloader that define the kernel and root filesystem
to boot (the "menu" funtionality is disabled and it just boots the
default kernel). For example:
--------------------------------- file ----------------------------
# see /usr/share/doc/syslinux-x.xx/syslinux.txt.bz2
# and /usr/share/doc/syslinux-x.xx/menu.txt.bz2 for help
# Use the menu system.
UI vesamenu.c32
# Display the boot: prompt only if the Shift or Alt key
# is pressed, or Caps Lock or Scroll lock is set.
PROMPT 0
# Ignore the Shift/Alt/Caps Lock/Scroll Lock escapes.
# So, with the above, the menu system is started.
NOESCAPE 1
# Exit the menu system immediately unless either the Shift
# or Alt key is pressed, or Caps Lock or Scroll Lock is set.
MENU SHIFTKEY
# Timeout for both the syslinux boot: prompt and the menu.
TIMEOUT 50
# Replaces the message "Automatic boot in # second{,s}...".
MENU AUTOBOOT Starting Gentoo Thinclient in # second{,s}
# Menu title
MENU TITLE PXELinux Boot Menu
# --------------------------------------------------------
# The menu entries:
LABEL 3.14.16-ION-NVIDIA
MENU LABEL Gentoo Thinclient 3.14.16-ION-NVIDIA
KERNEL ltsp/x86/kernel-genkernel-x86-3.14.16-gentoo-ION-NVIDIA
APPEND root=/dev/nfs ip=dhcp nfsroot=<Server-IP>:/opt/ltsp/x86 noht
real_init=/sbin/init-ltsp
INITRD ltsp/x86/initramfs-genkernel-x86-3.14.16-gentoo-ION-NVIDIA
LABEL 3.12.21-gentoo-r1-ION-NVIDIA
MENU LABEL Gentoo Thinclient 3.12.21-gentoo-r1-ION-NVIDIA
KERNEL ltsp/x86/kernel-genkernel-x86-3.12.21-gentoo-r1-ION-NVIDIA
APPEND root=/dev/nfs ip=dhcp nfsroot=<Server-IP>:/opt/ltsp/x86 noht
real_init=/sbin/init-ltsp
INITRD ltsp/x86/initramfs-genkernel-x86-3.12.21-gentoo-r1-ION-NVIDIA
#LABEL BIOS Update
# MENU LABEL Zotac IONITX-F-E BIOS Update
# KERNEL ltsp/memdisk
# APPEND initrd=ltsp/AFUDOS.img root=/dev/hda1
------------------------------- file end --------------------------
The file for the other client arch has different kernel and nfsroot
paths.
As you can see I once even used this setup to boot a BIOS update image
for my thin client boards.
Regards,
Horst
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
