Re: [Etherboot-developers] Moving ltsroot out of /tftpboot

[<ke...@us...>]

I'm all for this. I've always thought it ugly that /tftpboot should
contain stuff that have nothing to do with TFTP. It's the defaults in the
kernel source that need to be changed though, uses of /tftpboot in
Etherboot are for TFTP.

>So, I'm strongly considering putting the root directories into
>"/srv/ltsp".

The other option is /opt/ltsp, it's available for extra packages in many
systems, not just Linux. There's a tradition for using /opt for
third-party packages.

Anyway if you make it relocatable, it should not matter much whether
it's /srv or /opt

I'm against using /var or /usr or /usr/local for LTSP. The /usr
filesystem may itself be imported (remember that the LTSP server doesn't
necessarily have to be the /usr server), /usr/local is often used for
site wide exports. LTSP isn't really something that belongs in /var,
/var tends to be associated with temporary state, or admin files.

>    /srv/ltsp/root_i386     standard x86 based workstations
>    /srv/ltsp/root_i686     workstations with PII, PIII and Celerons
>    /srv/ltsp/root_ppc      workstations with PowerPC cpus
>    /srv/ltsp/root_arm      workstations with StrongArm cpus

Instead of prepending root_ to everything, just use the official
architecture name, e.g. /srv/ltsp/i386. Legions of people in future who
have to type the pathname will thank you. There may also be a place for
a noarch directory for architecture independent files that can be shared
by mounting or by hardlinking.