The real problem with what yall want is that LTSP is not really a program at all. IT is just a fancy config script for other apps.
Evan > Brian > > I agree with you. The installation process is needs to be > perfected to the point of "hands free" or have a very smart > automated trouble-shooter. I feel lucky (not competent) if I am > able to install LTSP. I disagree with you for only supporting > the two distros and the two "machine profiles" you mentioned. > I would like to see effort expended in the area of trouble shooting. > for example: > > # different distributions of Linux require different > # solutions to the same problem. > if ($distro eq "Red Hat") ; then > msg7="you need to do a service dhcpd restart" > fi > ltsp_status=$(ps -aux | grep dhcpd | grep -v grep) > if ($ltsp_status -ne [*dhcpd*]) ; then > echo "dhcpd is not running" > echo "$msg7" > exit 2 > fi > > The above is just an idea not working code. There are entries or > lack there of in /var/log/messages that give clues as to what is > wrong. Are there corresponding entries in hosts dhcpd.conf and > lts.conf. Does the filename mentioned in lts.conf exist? > things like these could be used for an automated trouble shooter. > Things like dhcpd happens before tftp which happens before ipchains > etc. I am going to be un-netted for three weeks for Christmas but > when I get back I will try to collect all of the thoughts that this > thread is generating (read everyone get involved) and try to put > something together. But I do have another life like everyone else. > > Jim Rich > [EMAIL PROTECTED] > > > I'm a big believer in LTSP; when I installed 2.x it was fast, simple = > > and light. But I've made two, seperate, multi-week install attempts on 3= > > .x and have yet to see an X login screen. And trying to debug it, even a= > > fter knowing how to do it before, was darned near impossible. > > > > This is not to say that there hasn't been a great deal of work, and i= > > mprovements to the core code...but because it supports so many platforms = > > and variations, it's just gotten so complicated that it's no longer easy = > > or fun anymore.=20 > > > > My suggestion: > > > > Let's take LTSP 2.x, simplify and improve upon it, but just for the R= > > edhat/Mandrake installations. Let's make two kinds of configurations by = > > default, Jammin-125 and 'custom' and give the admin some basic starting p= > > oints. > > > > Wether anyone else wants to do it, I have to. I plan to install a bu= > > nch in this area, and it'll be easier to maintain a partial-distro than t= > > o convert from what LTSP has become, to what I need in 99%+ of the situat= > > ions, ya know? > > > > Your thoughts? > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! > Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, > MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. > T H I N K G E E K . C O M http://www.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 > ------------------------------------------------------- This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. T H I N K G E E K . C O M http://www.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
