Fragged my Ubuntu LTSP install.
Details over at the network janitor’s log. [via Network janitor's log]
Tag Archive for 'ltsp'
Fragged my Ubuntu LTSP install. I thought doing a
sudo apt-get remove openoffice.org;sudo apt-get install openoffice.org2
would upgrade OpenOffice.org. Well, it did, but it also removed xserver-xorg. Ack!
Dumb me.
So I tried Breezy and MueCow. No dice. The tftpd-hpa service won’t start. So back to Hoary, I did.
X on the clients won’t start. The XSERVER = auto directive in lts.conf didn’t work for some reason. Turns out XDCMP wasn’t allowing requests. I just had to remove the hash in /etc/X11/xmd/Xaccess:
#* #any host can get a login window
Slap my forehead! Ten times. 
The server: dual Xeon 2.8 GHz, 4 GB DDR 333 MHz, 3 x 200-GB SATA HD.
Thin-client desktop.
Login screen.
Provisional setup for the thin clients.
Follow-up to my initial Ubuntu LTSP post.
The linux-2.6.10-5-i686 kernel recognized the 4-GB RAM, but registered only 3.5 GB (according to free).
The good thing is, with all 30 clients on and running Firefox and OpenOffice.org, memory use peaked at just about 1.4 GB. Bad news, though: CPU utilization maxed out at 100%! I could barely move the mouse pointer on the server. Clients just sailed along fine, though. Weird.
I have a dual Xeon box, and with the rush of configuring the server in time for the IPR training (for which these critters will be used mostly: our organization is building up its IP management infrastructure) today, I forgot to add an -smp kernel. *Slaps my forehead!* Oh well, nothing that a Synaptic session couldn’t accomplish.
Snags. For one, while the clients rarely hanged, most of them took a long time logging back in (and I mean *lloooong*, as in 10-15 minutes) after lunch break. Seems I’ve set the DHCP lease time way too low, and it was continuously polling for requests. Another one, web browsing was a bit sluggish, but that is mostly due to all the clients accessing the *same site* all at once. Memo to self: consider adding a web cache/accelerator later.
The lag in the network is mainly due to the physical setup. We installed switches in the training room, with one port connected to the outlet that goes up to the second-floor MDF. From the patch panel there, I had to hook up a patch cord to yet another patch panel outlet, and out to the work area outlet to the server. Let’s just say packets had a fun time travelling. Hey, they’re still in the same segment. _shrugs_
But that would not be a problem once the setup roosts in its real home: a retooled training room (structured cabling, fault-tolerant power, airconditioning, {transporter, turbo lifts and photon torpedoes optional}). Once there, the clients can be rented out to students in the area — a thin-client internet cafe, the first one this side of the Sierra Madre!
Okay, plans for the server: am considering replacing GDM with KDM, or some other window manager. Gnome is okay, but I’m looking for a cleaner handling of ghost sessions. (I had to kill some. Yes, I’m a cold-blooded, heartless process killer. One’s gotta do what one’s gotta do.)
A side note: surprisingly, the users took these all in very well. They were very appreciative of the setup, and they didn’t have a hard time poking around with the desktop — a testimony to Ubuntu’s usability. Ubuntu may just be *the* distro that will make it to the desktop primetime.
(Then again, our users were already computer-savvy. Heck, they’re scientists and researchers, and they handle computers the way they deftly tweak those quantum spectrometer thingamajiggies they have down at the labs.)
But I digress. Oh yes, plans: package the software (Firefox and OpenOffice.org) so they’ll be more friendly. While we’ve successfully deployed Firefox as the default browser network-wide, OpenOffice.org adoption is not yet creeping. Problem with the file formats. Somehow, I would have to find a way to package an installer that has default saves to Windows file formats. Actually, my next project is compiling a Firefox installer with all our network settings (proxy, home page, extensions and plugins) built in. Seems a worthwhile weekend project.
Find a way to use the local resources on clients like floppy drives and USB ports. (USB thumb drives are as ubiquitous here as pencils — or maybe more, as this office is really wired.) Or, maybe a way to run apps locally. The clients are diskless but they have 256-MB RAMs. Sayang. Dunno if this is even possible. Oh, Mr. Google…!
(My colleague, the tech-support guy, was impishly whispering, “LAN party! LAN party!”, while we were setting up the boxes. I wonder if we can run a decent Quake session on them thingies… Now, that would be the killer app!)
Gawd, I’m rambling. Must be the heat. Nah, I’m just chipper because I’ve built something good again.
Update: Photos are here. The installation notes are in my wiki.
For now. The firewall’s LAN port is totally fragged, and I can’t even do one-to-one NATing on it just so I can punch a hole to the internet.I’ve given up on doing manual updates on Warty. I’ve ran into a circular dependency on perl and perl-modules. I need those packages to update libwww-perl, which in turn is needed by ltsp-admin. Yep, I could have struck a no/ignore-dependency switch, but I don’t know what that would entail. So instead of totally trashing the Warty install, I’ve placed the server on stand-by for now.
Sayang. We have these 30 cool, totally useless critters in small-form-factor boxes with 15-inch widescreen TFT monitors, and they’re just gonna sit there until I’ve solved the more pressing problem with the firewall.
Sure, I could just as easily put up an old box to add as a firewall, but again, that would take much of my time now that the R&D conference is just around the corner. I’d have to deal with the increased traffic on the intranet, what with the guests going over to the designated kiosks and cubes for the proceedings and possible videostreaming of simultaneous track sessions.
(Besides, I’ve got a paper to present. Speaking of which, I’m glad that I already polished that before my super started doing his frenzied-editing thing again. I pity my cube-farm mates: they were laboring on it Sunday night and into early Monday morning, and when I got back to the office Monday afternoon, they’re nowhere near finishing their papers. One colleague was grumbling that no amount of bola would do the results and conclusions good.)
But I digress. Hay… I was excited pa naman with the installation. Oh well, there’ll be next week for that. I’m looking at it this way: my choice so far of using Ubuntu was fairly safe. While I would have loved to use Bayanihan — heck, ASTI’s our partner and collaborator in some tech research undertaking — it just wasn’t ready when I needed it. The Thin Client Manager, which was put up for a roadshow last month, is still nowhere to be found in their site. Our net-ad says that the Cebu seminar was a blast, but they won’t let him copy the TCM when he was surreptitiously attempting to snag it on his thumbdrive. (Sneaky-sneaky, this BOFH. Hehe.)
I’m very confident that with all the preliminaries out of the way, and all the requirements on hand, the LTSP install would be a breeze. I see it now: a room full of sleek screens with the “poo-colored” theme in the background. Soon, babies, soon…
