On Oct 30, 2007, at 12:10 AM, Jim Kronebusch wrote:
>> I have finally managed to roll out my first "commercial" LTSP ENV. I
>> have migrated 15 full systems running M$ to 4 heavy LTSP running
>> local apps. Estimated $ savings in software (lic and support) is
>> estimated at $15K/y. Labor costs > $45k/y (avoided hiring full time
>> support). Everyone wins except M$ (i was the $45K and just kept my
>> current position ;-)
>>
>> All that to say "thank you for LTSP 5."
>>
>> Jaysen O'Dell.
>
> Care to share any insight as to how you achieved local apps under
> LTSP 5? I know that
> is a very sought after feature for many, but has not been nailed
> down yet. You have the
> opportunity to be the hero to many here (is that enough incentive :-)
>
> Jim K
I wonder if local app is really the right term for what I am doing. I
think a better term is "diskless systems" in that the WHOLE systems
runs local. EG KDE runs on the client not the server.
My "server" is just an NFS server using a PIII that I have 500GB
worth of SCSI drives. Each client is a CHEAP MB with integrated CPU
(AMD Sempron) and 512MB RAM. Total including case was $125 (US folks
look to newegg). There are NO drives of any kind in the clients.
personal storage is USB.
The setup is pretty stock up to the client side.
1) Install OS: I prefer debian for some reason. Ubu just feels weird.
2) Install ltsp server and client packages. Use method of choice.
3) Make the client env. Follow the directions. isn't rocket
science. hardest part is
getting the MAC/PXE crap right in dhcpd.conf
At this point my systems worked as advertised. Next comes the part I
added.
4) Set up LDAP on server.
5) Export chroot and /home via NFS on server
6) sudo chroot $CHROOT
7) apt-get install kde-desktop kdm pam-ldap
(that last pkg name is wrong, but I don't have my notes handy
just follow the auth via ldap howtos)(you could just tasksel
workstation
but I despise gnome)
8) get a sandwich
9) modify ldm.conf to set server res and chipset (the only
modification needed)
10) boot. if all goes well you see a kdm login. If you didn't set
up a local user use a LDAP account.
That is it. I wrote a little wrapper for anything that i want to run
off the "other server" (not the wimpy NFS server) that essentially
listens on a port and dispatches requests for the client (su - $user -
c "rdesktop -f -display $TERM win2k3"). rdesktop runs fine on the
clients, but I wanted to try it this way. Guess what? It worked. Once
I pretty it up I will submit it to the list. (it would be the
listener needed for the dedicated IP solution I mentioned). Now that
I think about it this could be used for a real "local app" solution
as well. I guess I should get to work on it.
Jaysen
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.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
