[00:16] wow, i broke my ltsp server [01:19] stgraber: while you're up, I'm slowly getting https://wiki.ubuntu.com/Edubuntu/StrategyDocument going [01:19] comments on the outline would be appreciated [01:20] LaserJock: ok, I'll have a look [01:29] LaserJock: looks good, I guess objective #3 will also be to have different set of softwares depending on the target to avoid having gcompris and rasmol with the same install :) [01:30] stgraber: yeah, good point [11:36] this room is not to do support? [15:34] saliom, yes, you can get support here if you wait [15:37] Ahmuck: I think he's gone :) [15:39] k, i followed nubae's script for fat clients, and now my ltsp server is borken :( [15:39] so i'm missing something [18:54] nubae: i tried your fat client setup and borked my ltsp server [18:55] Ahmuck: and how did u do that exactly? [18:56] he used the --bork option :) [18:56] lol [18:56] fatclient doesnt touch the existing ltsp setup [18:56] exactly as you had it in your blog [18:56] unless you indeed use the --bork option [18:57] :-) [18:57] let me pull up the blog entry [18:57] http://www.nubae.com/ltsp-linux-terminal-server-project-netbooted-fat-client-for-ubuntu-hardy-and-intrepid [18:57] Ahmuck: what did u type to install fatclient script [18:57] thanks for pointing to my own blog... [18:58] I'm asking what YOU typed to install the script [18:58] touch 030-fatclient [18:58] sudo nano 030-fatclient [18:58] paste [18:58] save [18:59] reboot [19:00] Edit /etc/ltsp/dhcpd.conf - in this file, it appears i need to specify each thin client [19:00] by mac address [19:00] anywho, my dhcpd.conf file looks exactly as yours with the exception that is set the mac address and the ip address of the client [19:01] how did u install the fatclient script? [19:01] the client is booting pxe and starts looking for a dhcp address, but cannot find one. looking at the instructions, the ip address are set, so it appears that they are static? [19:01] after editting and all... [19:01] nubae: copy/past [19:01] copy/paste [19:01] save [19:02] so i copied it from your blog, pasted it into a file and saved [19:02] no... something along the lines of sudo ltsp-build-client --fatclient Ubuntu [19:02] or did u not build a chroot? [19:03] because without one, it would be hard for dhcp to find it... [19:03] er, yes. but now that i think about it, i may have placed the script in the directory after building chroot. i'll run through the processes again [19:03] though, it did download a ton of stuff [19:04] Ahmuck: the script must be put into the /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu [19:04] directory [19:04] and then u must do ltsp-build-client --chroot name-of-chroot --fatclient Ubuntu --highfat [19:05] the dhcp file must then contain entries to load up both normal clients and fat clients as outlined === spacey_ is now known as spacey [19:09] also, paste me your dhcpd.conf file so I can take a look: pastebin.be [19:10] /usr/share/ltsp/plugins/ltsp-build-client/ubuntu/030-fatclient - on your website [19:10] so i assume that ubuntu should be Ubuntu [19:10] right, is it lower case on my site? [19:10] yes [19:10] let me go fix that, good catch... :-) [19:11] i did however get it in the right directory. removing /opt/ltsp/fati386 now for rebuild [19:11] ya, about the paste. i have no gui at the moment on the server [19:11] :( [19:12] ok, then email or use links [19:12] i'll fiddle with it and see if i can't get a thin client to come up and then firefox and paste [19:12] info at nubae dot com [19:12] nubae: thanks for the howto on your blog, I've just read it [19:12] Eghie: cool [19:12] that same kind of idea has been on my mind for a while [19:13] performance whise, it could be working out very well [19:14] it does yes... if you have powerful clients, it certainly makes a difference [19:14] brainstorm of my on this: http://developer.thuis-online.nl/thinfatclient.txt [19:14] nubae: what is the difference in your proceedure and the other one listed on ubuntu's website? [19:15] which one on the ubuntu site? UbuntuLTSP/fatclient ? [19:15] Eghie: I'll take a look and see if I cant integrate some of that stuff in the next version [19:16] but overall looks like most of that is what I've done :-) [19:16] I guess so yes [19:17] except this: - Use (if harddrive exists) the harddrive, to store all the things [19:17] but performance wise, and also easier for clustering, I will check if I can intergrate OpenAFS to use that to share home directories [19:17] the point is its netbooted, but local hard drive access is enabled [19:17] well, you also need permissions from the administrator of the machine to write to the harddrive [19:17] so, that should be optional [19:18] no, I disable those on setup of client [19:18] ah [19:18] I figure, if its a fat client, local access should be for a storage area or access area to global files [19:19] swap could also be handy [19:19] local swap u mean? [19:19] yes [19:19] yep indeed [19:19] but not every fatclient will have a hard drive [19:19] no that's correct [19:19] Id need to detect if it does, and then if it is there use local swap [19:19] but its a good idea [19:21] Ahmuck: the stuff on the ubuntu site was written by me too [19:22] ah. there are two ways for fat clients ? [19:23] I guess the old and the new way ;) [19:23] not really, more like a manual and automatic way [19:23] or the old and new way like Eghie says [19:24] ah, ok [19:25] but if ltsp is not working at all for u... then its probably a problem with your dhpcd.conf [19:30] nubae: the script mentioned on the blog, expects NFS as homedirectory, right? [19:31] uses i mean [19:31] does that crash the client on network hickups? [19:32] because 2 years ago I had my own homedirectory connected via CIFS to the server [19:32] but when there was a network hickup, my client crashed [19:32] yes [19:32] because, I think it didn't heard of caching that much [19:32] well, not [19:32] hicupps so much as turning off the server [19:32] on hiccupps there is a lag [19:33] and then comes back [19:33] but since its only home mounted, it generally recovers ok [19:33] as in, switch off, hmm reboot and stuff like that [19:33] I've not had problems with it, lets put it that way [19:33] right [19:33] or restarting NFS service/ samba service [19:33] those kind of hicups [19:34] or restarten /etc/init.d/networking [19:34] wouldn't that be done at night and users would not be present? [19:35] nah, it could be recovery work for your network services, or adding a network client, or messing with IPtables, or some things like that [19:35] or even unstable switches [19:36] that generally is ok, its turning off the server that kills it [19:37] other elements it recovers from [19:37] again, in my experience [19:37] hmm ok [19:37] guess that NFS has enough caching support to handle that [19:44] wireless PXE boot is still not possible, or is it? [19:46] pxe boot, no [19:46] but there are workarounds [19:47] installing a basic variant of the LTSP client OS on the client, and setup the network service via wireless [19:47] more like usb sticks [19:47] or via initrd and then load the rest via network [19:47] right [19:48] well, I don't use wireless clients [19:48] but could be usefull [19:48] if it worked though [19:49] it would work ok with netbooted fatclients [19:59] seems not many people tried LTSP fat client [20:00] not that many sources/articles/questions on that one on the internet [20:00] nah, but I get a lot of hits to the blog so enough... [20:04] did you also have quota problems? [20:04] or not using quota's? [20:18] actually, i need quota's 4 sure [20:20] well, what do you do, when a user his homedirectory is full? [20:20] he will not be able to login agai [20:20] n [20:23] so he will not be able to cleanup his own homedirectory [22:09] rm -rf *.mp3 from home directory :) === HedgeMag1 is now known as HedgeMage [23:41] :(, i'm going to re-install [23:50] i've been looking at some ltsp client machines, however with intels atom proc and boards, one can build a ful fledge fat client for the same price they are asking