Hal, You do not need ENBD unless the controlling scripts are running on the LTSP *server* in which case they need access over the network to the client drive. From what it sounds like, this is not what you want.
Many people have modified and played around with the rc.local script in LTSP to get it to do all sorts of things with local partitions, usually to setup local swapping. Search the list archive for some of these keywords: local, swap, ide, partition. There've been lots of posts about this and I think at least one either included or linked to an example modified rc.local script. Basically all you need is to make sure your LTSP kernel includes all the necessary flags to do IDE access. I may be wrong, but I think the default LTSP kernels now include this. Then you just boot your clients into runlevel 3 (via lts.conf) and put your script in /opt/ltsp/i386/etc/rc.local. In this case, the script doing the action is on the client, so you don't need ENBD to access the hard drive. Then to access any additional data from your LTSP server (or some other server), all you need to do is use read-only NFS, which is already part of standard LTSP. Another thing that occurs to me is that you will either have to devote LTSP entirely to this bootstrapping project or find a way to distinguish between normal LTSP clients and new systems that need to be formatted and loaded. The first thing I would try is to configure DHCPD such that known hosts (MAC address hard coded into dhcpd.conf) receive a normal LTSP kernel and boot params, while unknown hosts receive a (possibly modified) kernel and an argument to put it into a special runlevel (say, 4) which could correspond to the bootstrapping script in inittab. Another possibility is to have the default section of lts.conf include a variable which tells rc.local to attempt to bootstrap the client, while known clients all receive a negative value for this parameter. Jason > From: Hal Vaughan <[EMAIL PROTECTED]> > Date: Thu, 4 Jul 2002 16:35:38 -0400 > Subject: [Ltsp-discuss] Access to local devices > > I am looking for a good way to access my local devices on my ltsp client.= > I=20 > am using ltsp to install software on client systems. The idea is that I = > can=20 > take the client system, plug it in, hook it up to my lan, and turn it on = > and=20 > ltsp and a few scripts will do everything I need. > > Part of the setup is formatting a blank hd in the client system. I'm loo= > king=20 > for ways to access the hard drive on the client system to first format it= > ,=20 > then copy over the system files I will need, then install GRUB or LILO on= > it. > > I'm currently reading through the documentation on ENBD, but I'm confused= > =2E =20 > When I set up a box using LTSP, the box booting is the client and the one= > =20 > supplying all the LTSP info and kernel is the server. I'm not sure, but = > it=20 > seems to me that once I get this running, since the drive I want to acces= > s is=20 > on the client, for the purposes of ENBD ONLY, the client is the server. > > Have others used ENBD? Is this the only way or best way to access local=20 > devices? Can I use ENBD to be able to format the drives in the client=20 > system? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf _____________________________________________________________________ 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.openprojects.net
