On Sat, 13 Dec 2003 [EMAIL PROTECTED] wrote: > Thank you for your reply, Jim. The kernel works nicely. > > Regarding my second question which I left in the quote below, should I use the > directory structure created by building the lbe, or the one that the install > script created?
Well, you can use either one. if you are going to be building apps to run locally, or doing any customization of LTSP-4, then you would probably want to use the tree that you generated by compiling the ltsp-4 source. Most people, however, would be just using the /opt/ltsp/i386 tree as their root fs for the workstation. There is a whole lot more in the tree that you built. When I make the LTSP-4 packages, I build the entire tree, then when I generate the binary packages, I skip all the documentation files and alot of the other stuff that gets built. Much of it simply isn't needed in a thin client environment. Jim. > > Quoting [EMAIL PROTECTED]: > > > > > kge2, > > > > Just use the LTSP-3 kernel. > > > > We will have the scripts setup to build a kernel with the LBE, but > > it's not complete yet. > > > > the LTSP-3 kernel will work just fine. > > > > Jim. > > > > Second, the lbe has its own ./opt/ltsp/i386 structure which > > is > > > somewhat identical to the root filesystem that the script up above > > created. > > > It's slightly different, however. Should I use the filesystem created > > by the > > > lbe build_all script, or the one created by the ltsp_installer > > script? > ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&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
