Re: Correct Directory for networkboot clients
Am Sam, 2003-08-23 um 20.00 schrieb Petter Reinholdtsen: [Goswin von Brederlow] Then it must be read-only. To the client and the server. No changing of links or hostame or anything in there. LTSP keep all the client specific files in RAM file system. The NFS-mounted root is not written to by the client. So I go to use this directory usr/share/ltsp/arch/ or any more comments ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Retrieve my key from: www.keyserver.de blackhole.pca.dfn.de horowitz.surfnet.nl keyID 7B196671 or send email with subject fetch key signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Correct Directory for networkboot clients
Daniel J. Priem [EMAIL PROTECTED] writes: Where should i place the root directory for networkbooting clients ? i'm packing www.ltsp.org I don't know where to place the / Im thinking about /usr/ltsp/ or /usr/share/ltsp/ /usr/share/ltsp/arch/ is probably better. Otherwise you can#t boot different archs from the same server. MfG Goswin
Re: Correct Directory for networkboot clients
On Sat, Aug 23, 2003 at 01:30:55PM +0200, Goswin von Brederlow wrote: /usr/share/ltsp/arch/ is probably better. Otherwise you can#t boot different archs from the same server. Shouldn't that be /var/lib/ltsp/arch/ instead? I'm assuming the root filesystem is writable. Ben -- ,-. nSLUGhttp://www.nslug.ns.ca [EMAIL PROTECTED] \`' Debian http://www.debian.org[EMAIL PROTECTED] ` [ gpg 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ] [ pgp 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ]
Re: Correct Directory for networkboot clients
Am Sam, 2003-08-23 um 14.30 schrieb Ben Armstrong: On Sat, Aug 23, 2003 at 01:30:55PM +0200, Goswin von Brederlow wrote: /usr/share/ltsp/arch/ is probably better. Otherwise you can#t boot different archs from the same server. Shouldn't that be /var/lib/ltsp/arch/ instead? I'm assuming the root filesystem is writable. The rootfilesystem is writable but will be normaly not changed. Only on Startup the configfiles for the client will be created / linked Ben -- ,-. nSLUGhttp://www.nslug.ns.ca [EMAIL PROTECTED] \`' Debian http://www.debian.org[EMAIL PROTECTED] ` [ gpg 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ] [ pgp 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Retrieve my key from: www.keyserver.de blackhole.pca.dfn.de horowitz.surfnet.nl keyID 7B196671 or send email with subject fetch key signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Correct Directory for networkboot clients
On Sat, Aug 23, 2003 at 02:38:32PM +0200, Daniel J. Priem wrote: The rootfilesystem is writable but will be normaly not changed. Only on Startup the configfiles for the client will be created / linked Still, conceptually, a root filesystem is state information for the netbootable client. Even if the default policy is to not change the root filesystem, is that written in stone? Ben -- ,-. nSLUGhttp://www.nslug.ns.ca [EMAIL PROTECTED] \`' Debian http://www.debian.org[EMAIL PROTECTED] ` [ gpg 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ] [ pgp 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ]
Re: Correct Directory for networkboot clients
On Sat, Aug 23, 2003 at 09:46:55AM -0300, Ben Armstrong wrote: On Sat, Aug 23, 2003 at 02:38:32PM +0200, Daniel J. Priem wrote: The rootfilesystem is writable but will be normaly not changed. Only on Startup the configfiles for the client will be created / linked Still, conceptually, a root filesystem is state information for the netbootable client. Even if the default policy is to not change the root filesystem, is that written in stone? It's often shared between multiple clients -- it should be read-only for normal operations. FWIW, I seem to have a /usr/lib/lts/i386-linux directory on my system; I think this was an upstream default. Since all of the files under there are merely data to the host system, /usr/share/ltsp/i386-linux is probably fine. -- Steve Langasek postmodern programmer pgpUUoRl3GPCd.pgp Description: PGP signature
Re: Correct Directory for networkboot clients
Steve Langasek [EMAIL PROTECTED] writes: On Sat, Aug 23, 2003 at 09:46:55AM -0300, Ben Armstrong wrote: On Sat, Aug 23, 2003 at 02:38:32PM +0200, Daniel J. Priem wrote: The rootfilesystem is writable but will be normaly not changed. Only on Startup the configfiles for the client will be created / linked Still, conceptually, a root filesystem is state information for the netbootable client. Even if the default policy is to not change the root filesystem, is that written in stone? It's often shared between multiple clients -- it should be read-only for normal operations. FWIW, I seem to have a /usr/lib/lts/i386-linux directory on my system; I think this was an upstream default. Since all of the files under there are merely data to the host system, /usr/share/ltsp/i386-linux is probably fine. Then it must be read-only. To the client and the server. No changing of links or hostame or anything in there. You can of cause link some file to var and keep the static files there (if that works). MfG Goswin
Re: Correct Directory for networkboot clients
[Goswin von Brederlow] Then it must be read-only. To the client and the server. No changing of links or hostame or anything in there. LTSP keep all the client specific files in RAM file system. The NFS-mounted root is not written to by the client.
