On Sun, 26 Jan 2003, Shane wrote: > Ditto. > > There used to be an etherboot group, driven, I think, by Ken Yap. This > is where I started with diskless clients, but that movement seems to > have fizzled out. > Basically, it had a netbootable kerner, and a root f/s per client. I > would like to do this again, as I will be using VIA boards, but don't > really have the understanding of linux to easily do it. > It was based around 2 scripts.....nfsrootinit (for 1st client), and > nfsrootdup (to duplicate some, and softlink others). > I still have those files, which worked on RH 6.?. The LTSP kernel MAY > work, except for setting correct client root at the correct location. > This probably isn't relevant for PXE boot, as the root loc' is > specified in the PXE files on server (rather than in the tagging).. > > If someone can adapt these for RH8, I would be well pleased. > > Shane > > Radu Filip wrote: > > >hello, > > > >after going through lstp documentation and after searching the web, and > >this mailing archive, I'm still confused if ltsp is what I need for my > >purpose: > > > >- as opposed to thin client provided by ltsp (based on xdmcp), I wish - > >ideally - to be able to have a client that runs locally all applications, > >including X, as it were a classic linux desktop. > > > >why I need this: > >- for a small office lan > >- I have tree pc, all the same class and aproximatelly the same cpu-power > >and ram; oll of them are powerful enough (AMD 1.1 GHz, 256 RAM, etc) > >and quite identical, only the vide cards are bit different (on server: > >gefrce mx2, on the other two rivatnt) > >- obviously, I don't want to have three different linux-es installed on > >that three pc-s. > >- but in the same time I don't want to waste the resurces of those two > >(cpu, ram) and have only one (the server) that do all the work > >- I don't want even to have the same fully functional distro from server > >duplicated on /opt/ltps/i386 (file by file) > > > >question: > >- is ltsp what I really need for these purposes? if not, please point me > >to the correct solution > >- in "9.4. Application Configuration" section of ltsp doc it's said that: > > "So, the cleanest way to handle this is to have a complete tree with > > all of the binaries and libraries that the workstation will need, > > independent of the server binaries and libraries" > > > > can I avoid duplicating distro on server? suposing I update a packet > > or I install a new app, I have to do copy all it's files to > > /opt/ltps/i386, which is adding unwanted administration complexity > > > > how I can avoid this and reach my goal? > > > >please help with this issue. if it's needed I can provide more details. > >the linux distro I'm using it's mandrake 9.0 > > > >thank you, > > radu
http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=nfsrootinit ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _____________________________________________________________________ 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
