I interpret them as relating to
processor/ram capabilities. . . . . "fat" being, maybe 300MHz + and 32MB+
Etherboot with, or without LTSP is usually "diskless", though a local disk may be usefull as swap space. BOTH keep all rootfs on server, and BOTH are configured from there. One major difference is that plain etherboot will usually allow users to save their setups/apps/Xconfig etc, whereas LTSP boots as per administrator accessed settings via server. I also see LTSP as being a bit more involved where X configs, and local ports/cd/printer are concerned.
This is my understanding, though others may differ, and there are, I'm sure, grey areas as well.
Shane
Ken Cobler wrote:
Radu Filip wrote:hello,It depends on what your needs are. I view LTSP as computing power without a hard drive. The default configuration has not only the data stored on the server, but, the applications run on the server as well. You can configure LTSP with local application support. This simply means that the workstation can be configured to run some applications, though the data is still stored on the server. Besides LTSP requirements of local applications, you would also need to copy or link the programs and libraries the programs use, available to the workstation via nfs.
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
In fact, this is the arrangement that I have for some workstations. The workstations are powerful enough machines, but don't have a hard drive. I've enabled local apps and copied the specific programs and necessary libraries needed to the /opt/ltsp appropriate directories.
The benefit is central administration, ease of configuration, and don't have to worry about a hard drive failure on the workstation. The server has RAID, so I feel better it will handle a hard drive failure. With the local apps, I can utilize that extra CPU power of the workstation.
If you still think you need a fat client (with hard drive), you can always build an image (kernel, libraries, programs), burn to CD and load from that image to make your workstations look alike.
Ken Cobler
-------------------------------------------------------
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
------------------------------------------------------- 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
