Am Dienstag, 8. Juni 2004 18:54 schrieb John Sutton: > Yes, I tripped over that one some time back ;-) Now I only ever download > the 5.0.11 release so I am stuck in a dying backwater... but OTOH I haven't > _yet_ needed a driver which I couldn't find in that release ;-)
The newer releases bring cool stuff like multicast support, http kernel download, ... and are far better supported. If 5.0.x work for you, that's really nice and there's no need to change a running setup. On new nodes or when burning ROMs - or in case you have a gigabit NIC - it's a reasonable decision to go with 5.2 (or 5.3, to have the most features - backporting to 5.2 does happen when the new features commonly are seen as stable, which takes some time - and when someone has time to do so). > BTW, I downloaded ltsp_initrd_kit-3.0.13-i386.tgz from sourceforge because > it is marked as "Source .gz" in the rightmost column of showfiles.php. But > it isn't source at all, it is binary! How (from what sources, by what > build procedure) is this package put together? I see lots of .i386.rpm's > but no .src.rpm's? Where's the beef?! (as the Americans say ;-) Great part of the LTSP functionality is done as scripts, so there's no source for those files. Other parts are put together from standard software packages, like the "busybox" in the initrd. The server side of ltsp only consists of scripts for adapting daemon config files (like dhcpd.conf, /etc/hosts or whatever), the client side (which lives in /opt/ltsp/i386 on the server usually) consists of software like XFree86 that can be downloaded in source form from their respective homepage. "Standing on the shoulders of giants" - Newton said that (wheew, visiting his birthplace tomorrow, on a 3day trip to Grantham, which happens to be partner town of my former home, St Augustin :-). This is true for LTSP as well - it's just the "glue" between the components that's the trick. (Please don't misunderstand that. There's much work behind this "glue", and it's always far more complicated then just copying files over). With LTSP 4, you have the LBE, the LTSP Build Environment, that allows you to compile everything from source if you want to. I didn't do so yet though :-( But it's a nice feature for compiling programs that are intended to run as "local apps" (on the client machines) - this is a good idea for distributing the workload or running video players (then only the compressed video data has to cross the net, instead of an uncompressed X graphics stream). > Vielen Danke! Gern geschehen! Anselm ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _____________________________________________________________________ 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
