On Tue, 2004-07-27 at 23:54, Gary Kypers wrote: > What I think I need is another local "root". That is > to say, a place to mount local devices that does not > depend on the LTSP server so that the LTSP server > could be disconnected but the local programs continue > working.
When I've had similar needs in the past, I've used a very small system image that can be included in the tftp download and booted as an initrd. That way you never need to use NFS, and you just don't care if the server goes down later. You could create your own image using uClibc, etc, but I found it somewhat more painful than it could be to get one up and running if you wanted any less common tools. Alternately, you could fairly easily adapt any of the floppy-based Linux distros for use as a network boot image (I converted the Tomsrtbt ISO image to a boot image and used that). Note that this approach won't do you any good if you need a GUI on the client or if you want to use LTSP functionality as well as your monitoring program. > I've looked at several explanations of the "mount" > command. In all cases it is used to mount a device > onto a directory that already exists. I see no > information on how to create a initial mount point > that is local to the client.. You can't - you need at least a root filesystem to mount something on. The root filesystem is mounted by the kernel during boot (though you can use pivot_root to change it later). A possible solution here is to retain the initrd you booted from (or perhaps pivot_root to a ramdisk) then mount anything else you need over NFS in subdirectories. I'd be inclined to entirely avoid NFS if at all possible, and instead send updates to the server using a simple script and HTTP GET requests, or something like that. It might also be possible to mangle the LTSP startup scripts so that the LTSP "root" is mounted in /ltsp (for example) on the client. You'd probably have to spawn your monitoring process then chroot into /ltsp, because the chances are there will be hard-coded paths in the LTSP setup scripts, and even if there are not you'd have to mangle your PATH etc to make it work. Chrooting is likely to be much simpler. Note that I cannot guarantee that this approach will work or that it will prevent the problem you're having - I'd investigate entirely NFS-less clients first (if you don't also need full LTSP functionality, that is). -- Craig Ringer ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _____________________________________________________________________ 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
