From skerr at rx30.com Mon Feb 7 21:06:33 2011 From: skerr at rx30.com (Stephen Kerr) Date: Mon, 7 Feb 2011 16:06:33 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot Message-ID: I recently downloaded K12LTSP-5.0.0EL-32bit-dvd.iso, set it up with a single nic and running dhcp on an alternate port. All works great. I am having one show stopper however, many of the packages under the chroot are too old for my purposes. Can someone suggest the best way to go about updating them ? Yum update has updated to CentOS 5.5 final but nothing under /opt/ltsp has changed. Thanks, Steve From skerr at rx30.com Tue Feb 8 13:29:18 2011 From: skerr at rx30.com (Stephen Kerr) Date: Tue, 8 Feb 2011 08:29:18 -0500 Subject: [K12OSN] dhclient and the prebuilt f10 chroot Message-ID: I was attempting to setup the fedora 10 prebuilt chroot on top of a centos host since the packages in the chroot are much newer than the ones in the centos 5 iso. . I've read the wiki guide but I am having one problem. I am using a single nic and using an alternate port, 1067 that my etherboot devices are flashed to use. I can see the devices connecting to the server, and loading the wraplinux kernel ok. But when the thin client makes a 2nd dhcp request, it appears to be using port 67 and attempting to connect to the networks main dhcp server and returning a root-path option missing message. I cant quite find where the config to change that is located. My dhcpd.conf contains the 128 and 129 options to use port 1067. Any help would be appreciated. From microman at cmosnetworks.com Tue Feb 8 14:55:37 2011 From: microman at cmosnetworks.com (Terrell Prude' Jr.) Date: Tue, 08 Feb 2011 09:55:37 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: Message-ID: <4D515969.4010404@cmosnetworks.com> When you say they're too old, what does that mean? Are some things not working? --TP Stephen Kerr wrote: > I recently downloaded K12LTSP-5.0.0EL-32bit-dvd.iso, set it up with a > single nic and running dhcp on an alternate port. All works great. I am > having one show stopper however, many of the packages under the chroot > are too old for my purposes. Can someone suggest the best way to go > about updating them ? Yum update has updated to CentOS 5.5 final but > nothing under /opt/ltsp has changed. > > Thanks, > Steve > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From skerr at rx30.com Tue Feb 8 15:39:32 2011 From: skerr at rx30.com (Stephen Kerr) Date: Tue, 8 Feb 2011 10:39:32 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: <4D515969.4010404@cmosnetworks.com> References: <4D515969.4010404@cmosnetworks.com> Message-ID: Hi Terrell, thanks for responding. Specifically the libc package in the chroot is 2.3.2 while libc in the host centos install is on 2.5 . My main reason for moving off of 4.2 was to update libc. I have started looking into copying the ltsp-build-client script and components under /usr/share/ltsp over and running it on the centos box but am running into issues there as well. maybe my google-fu is not up to snuff, but I havent been able to find any way to update the chroot. On Tue, 2011-02-08 at 09:55 -0500, Terrell Prude' Jr. wrote: > When you say they're too old, what does that mean? Are some things not > working? > > --TP > > Stephen Kerr wrote: > > I recently downloaded K12LTSP-5.0.0EL-32bit-dvd.iso, set it up with a > > single nic and running dhcp on an alternate port. All works great. I am > > having one show stopper however, many of the packages under the chroot > > are too old for my purposes. Can someone suggest the best way to go > > about updating them ? Yum update has updated to CentOS 5.5 final but > > nothing under /opt/ltsp has changed. > > > > Thanks, > > Steve > > > > _______________________________________________ > > K12OSN mailing list > > K12OSN at redhat.com > > https://www.redhat.com/mailman/listinfo/k12osn > > For more info see > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From skerr at rx30.com Tue Feb 8 17:36:10 2011 From: skerr at rx30.com (Stephen Kerr) Date: Tue, 8 Feb 2011 12:36:10 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: <4D516DAC.1050102@cmosnetworks.com> References: <4D515969.4010404@cmosnetworks.com> <4D516DAC.1050102@cmosnetworks.com> Message-ID: I have a number of kickstarts based on centos 5.4 deployed to my customers. many of them have jammin tc's that they connect sheetfed scanners to. I was able migrate the chroot and tftpboot kernels from the k12 iso to my kickstart image without any issues. we were using the avision av210c2 and everything worked great. Unfortunately, as manufacturers often do, they discontinued that model and we are now getting av210D2+ models. that required an upgrade to the sane-backend. we were able to hack together an rpm which runs fine on the server. scanner works. i cant however get the backend to work on the jammin , primarily due to libc, hence my desire to upgrade the jail. I tried the same method of moving the chroot and kernels with the fed9 and fed10 ltsp packages, but i am having issues with the tc's dhcp call after it loads the kernel image connecting on standard port 67 instead of my alt 1067. I tried kludging the fed9 and k12 chroots and managed to get it to give me a telnet login prompt but I am having a prob loading an x desktop. x runs, a conn to port 7100 is established, but i have a problem with ldm loading a desktop. It doesnt matter to me what method i get working, updating the chroot on the centos iso or migrating the chroot and kernels from a fedora distro as long as i can get an x desktop and my scanner to work. On Tue, 2011-02-08 at 11:22 -0500, Terrell Prude' Jr. wrote: > Should that matter, though? Remember that the only app actually running > on the thin client is X11. All the apps run on the server and merely > get displayed via X11 on the client. Thus, all the apps will use the > server's own libc (v2.5). I've actually taken a Sun UltraSPARC box > running Red Hat Linux 6.2--yup, the really ancient one from 11 years > ago--and, doing an X11 indirect query, used that box as a K12LTSP 5EL > thin client (it worked like a champ). > > Is there something specific you need to do on the thin client that > requires the newer libc on the client itself? > > --TP > > Stephen Kerr wrote: > > Hi Terrell, thanks for responding. > > > > Specifically the libc package in the chroot is 2.3.2 while libc in the > > host centos install is on 2.5 . My main reason for moving off of 4.2 was > > to update libc. > > > > I have started looking into copying the ltsp-build-client script and > > components under /usr/share/ltsp over and running it on the centos box > > but am running into issues there as well. maybe my google-fu is not up > > to snuff, but I havent been able to find any way to update the chroot. > > > > On Tue, 2011-02-08 at 09:55 -0500, Terrell Prude' Jr. wrote: > > > >> When you say they're too old, what does that mean? Are some things not > >> working? > >> > >> --TP > >> > >> Stephen Kerr wrote: > >> > >>> I recently downloaded K12LTSP-5.0.0EL-32bit-dvd.iso, set it up with a > >>> single nic and running dhcp on an alternate port. All works great. I am > >>> having one show stopper however, many of the packages under the chroot > >>> are too old for my purposes. Can someone suggest the best way to go > >>> about updating them ? Yum update has updated to CentOS 5.5 final but > >>> nothing under /opt/ltsp has changed. > >>> > >>> Thanks, > >>> Steve > >>> > >>> _______________________________________________ > >>> K12OSN mailing list > >>> K12OSN at redhat.com > >>> https://www.redhat.com/mailman/listinfo/k12osn > >>> For more info see > >>> > >>> > >> _______________________________________________ > >> K12OSN mailing list > >> K12OSN at redhat.com > >> https://www.redhat.com/mailman/listinfo/k12osn > >> For more info see > >> > > > > From brcisna at eazylivin.net Tue Feb 8 21:09:08 2011 From: brcisna at eazylivin.net (Barry Cisna) Date: Tue, 08 Feb 2011 15:09:08 -0600 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot Message-ID: <1297199348.26531.39.camel@localhost.localdomain> What are you seeing on the TC when it is completely booted up? From what you explain you are only presented with a telnet login? No other blinking as if X is trying to start? What have you set in your lts.conf file for screens? If you do CTL-ALT-F2 do you get a bash prompt? Barry From skerr at rx30.com Tue Feb 8 23:22:56 2011 From: skerr at rx30.com (Stephen Kerr) Date: Tue, 8 Feb 2011 18:22:56 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: <1297199348.26531.39.camel@localhost.localdomain> References: <1297199348.26531.39.camel@localhost.localdomain> Message-ID: Hi Barry, when i was trying to get my centos host run with a fedora 10 prebuilt chroot I had problems with the tc after loading the kernel from my dhcpd server on port 1067, the kernel loaded but the tc was making a second dhclient call but back on port 67 and not being able to load a desktop. i wound up moving sysinit_early and a couple other files from the centos chroot into fed10 prebuilt. it then behaved as it should have more or less. when i was on a telnet screen as defined in lts.conf, I was able to login. shell screens give a prompt at the TC, when i specified an x session screen, I had the x mouse cursor and gray/silver desktop background. the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the packages in the chroot are too old. i need to update libc from 2.3.2 and i cant find any utility thatll update the chroot so i have been trying to adapt ltsp-build-client from fedora, without success , so far. On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: > What are you seeing on the TC when it is completely booted up? From what > you explain you are only presented with a telnet login? No other > blinking as if X is trying to start? What have you set in your > lts.conf > file for screens? If you do CTL-ALT-F2 do you get a bash prompt? > > Barry > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From microman at cmosnetworks.com Wed Feb 9 00:13:34 2011 From: microman at cmosnetworks.com (Terrell Prude' Jr.) Date: Tue, 08 Feb 2011 19:13:34 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> Message-ID: <4D51DC2E.3060405@cmosnetworks.com> The way I always did it when I needed a specific set of binaries for the clients was to copy the entire /opt/ltsp/i386 subdirectory (or /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) to my K12LTSP server. Beforehand, I would typically rename the existing /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. These binaries should have *zero* affect on the server itself, since they run only on the client. Give that a shot and let us know. --TP Stephen Kerr wrote: > Hi Barry, > > when i was trying to get my centos host run with a fedora 10 prebuilt > chroot I had problems with the tc after loading the kernel from my dhcpd > server on port 1067, the kernel loaded but the tc was making a second > dhclient call but back on port 67 and not being able to load a desktop. > i wound up moving sysinit_early and a couple other files from the centos > chroot into fed10 prebuilt. > > it then behaved as it should have more or less. when i was on a telnet > screen as defined in lts.conf, I was able to login. shell screens give a > prompt at the TC, when i specified an x session screen, I had the x > mouse cursor and gray/silver desktop background. > > the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the > packages in the chroot are too old. i need to update libc from 2.3.2 and > i cant find any utility thatll update the chroot so i have been trying > to adapt ltsp-build-client from fedora, without success , so far. > > On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: > >> What are you seeing on the TC when it is completely booted up? From what >> you explain you are only presented with a telnet login? No other >> blinking as if X is trying to start? What have you set in your >> lts.conf >> file for screens? If you do CTL-ALT-F2 do you get a bash prompt? >> >> Barry >> >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see >> > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From skerr at rx30.com Wed Feb 9 14:51:33 2011 From: skerr at rx30.com (Stephen Kerr) Date: Wed, 9 Feb 2011 09:51:33 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: <4D51DC2E.3060405@cmosnetworks.com> References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> Message-ID: not sure I completely follow. are you advising to backup the existing directory , drop in the new c libraries (libc) and see what happens ? On Tue, 2011-02-08 at 19:13 -0500, Terrell Prude' Jr. wrote: > The way I always did it when I needed a specific set of binaries for the > clients was to copy the entire /opt/ltsp/i386 subdirectory (or > /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) > to my K12LTSP server. Beforehand, I would typically rename the existing > /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. These binaries > should have *zero* affect on the server itself, since they run only on > the client. > > Give that a shot and let us know. > > --TP > > Stephen Kerr wrote: > > Hi Barry, > > > > when i was trying to get my centos host run with a fedora 10 prebuilt > > chroot I had problems with the tc after loading the kernel from my dhcpd > > server on port 1067, the kernel loaded but the tc was making a second > > dhclient call but back on port 67 and not being able to load a desktop. > > i wound up moving sysinit_early and a couple other files from the centos > > chroot into fed10 prebuilt. > > > > it then behaved as it should have more or less. when i was on a telnet > > screen as defined in lts.conf, I was able to login. shell screens give a > > prompt at the TC, when i specified an x session screen, I had the x > > mouse cursor and gray/silver desktop background. > > > > the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the > > packages in the chroot are too old. i need to update libc from 2.3.2 and > > i cant find any utility thatll update the chroot so i have been trying > > to adapt ltsp-build-client from fedora, without success , so far. > > > > On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: > > > >> What are you seeing on the TC when it is completely booted up? From what > >> you explain you are only presented with a telnet login? No other > >> blinking as if X is trying to start? What have you set in your > >> lts.conf > >> file for screens? If you do CTL-ALT-F2 do you get a bash prompt? > >> > >> Barry > >> > >> > >> _______________________________________________ > >> K12OSN mailing list > >> K12OSN at redhat.com > >> https://www.redhat.com/mailman/listinfo/k12osn > >> For more info see > >> > > > > > > _______________________________________________ > > K12OSN mailing list > > K12OSN at redhat.com > > https://www.redhat.com/mailman/listinfo/k12osn > > For more info see > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From microman at cmosnetworks.com Wed Feb 9 21:15:59 2011 From: microman at cmosnetworks.com (Terrell Prude' Jr.) Date: Wed, 09 Feb 2011 16:15:59 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> Message-ID: <4D53040F.8030208@cmosnetworks.com> Not exactly. I'm suggesting that you backup the existing /opt/ltsp/i386 subdirectory, or just rename it. Then, from your K12Linux Fedora 9/10/11/12/13/14/WhateverYouChoose box, copy *that* /opt/ltsp/i386 subdirectory tree--the entire thing--over to your K12LTSP 5EL server. Your clients will thus be using that Fedora version of the client binaries vs. the ones that came with K12LTSP 5EL. --TP Stephen Kerr wrote: > not sure I completely follow. are you advising to backup the existing > directory , drop in the new c libraries (libc) and see what happens ? > > > On Tue, 2011-02-08 at 19:13 -0500, Terrell Prude' Jr. wrote: > >> The way I always did it when I needed a specific set of binaries for the >> clients was to copy the entire /opt/ltsp/i386 subdirectory (or >> /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) >> to my K12LTSP server. Beforehand, I would typically rename the existing >> /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. These binaries >> should have *zero* affect on the server itself, since they run only on >> the client. >> >> Give that a shot and let us know. >> >> --TP >> >> Stephen Kerr wrote: >> >>> Hi Barry, >>> >>> when i was trying to get my centos host run with a fedora 10 prebuilt >>> chroot I had problems with the tc after loading the kernel from my dhcpd >>> server on port 1067, the kernel loaded but the tc was making a second >>> dhclient call but back on port 67 and not being able to load a desktop. >>> i wound up moving sysinit_early and a couple other files from the centos >>> chroot into fed10 prebuilt. >>> >>> it then behaved as it should have more or less. when i was on a telnet >>> screen as defined in lts.conf, I was able to login. shell screens give a >>> prompt at the TC, when i specified an x session screen, I had the x >>> mouse cursor and gray/silver desktop background. >>> >>> the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the >>> packages in the chroot are too old. i need to update libc from 2.3.2 and >>> i cant find any utility thatll update the chroot so i have been trying >>> to adapt ltsp-build-client from fedora, without success , so far. >>> >>> On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: >>> >>> >>>> What are you seeing on the TC when it is completely booted up? From what >>>> you explain you are only presented with a telnet login? No other >>>> blinking as if X is trying to start? What have you set in your >>>> lts.conf >>>> file for screens? If you do CTL-ALT-F2 do you get a bash prompt? >>>> >>>> Barry >>>> >>>> >>>> From skerr at rx30.com Wed Feb 9 21:49:23 2011 From: skerr at rx30.com (Stephen Kerr) Date: Wed, 9 Feb 2011 16:49:23 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: <4D53040F.8030208@cmosnetworks.com> References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: got you. thats what i was doing with the f10 prebuilt chroot. just renaming the original ltsp and dropping the f10 one in. i did the same with the kernels under tftpboot. it seems like thefed ltsp root work alot differently. unlike the centos root, i could see fed10 aquiring the image on the desired port 1067, load, then make a second dhclient call back to standard 67. i managed to get that squared away , telnet worked but x was broken. got x working but ldm wasnt loading. put that aside, got a pristine cent ltsp box back up moved moved most of lib lib/modules lib/udev /usr/lib from the fed root in, kept existing X and shell scripts and binaries. might be missing a couple of things. tc came up without error. basic functionality ok. ran scanimage from tc shell, not perfect but it saw the device and pulled the paper thru on the old scanner. gonna bolt this on top of my kickstart, load the sane-backend required for the new scanner and see what happens. On Wed, 2011-02-09 at 16:15 -0500, Terrell Prude' Jr. wrote: > Not exactly. I'm suggesting that you backup the existing /opt/ltsp/i386 > subdirectory, or just rename it. Then, from your K12Linux Fedora > 9/10/11/12/13/14/WhateverYouChoose box, copy *that* /opt/ltsp/i386 > subdirectory tree--the entire thing--over to your K12LTSP 5EL server. > Your clients will thus be using that Fedora version of the client > binaries vs. the ones that came with K12LTSP 5EL. > > --TP > > Stephen Kerr wrote: > > not sure I completely follow. are you advising to backup the existing > > directory , drop in the new c libraries (libc) and see what happens ? > > > > > > On Tue, 2011-02-08 at 19:13 -0500, Terrell Prude' Jr. wrote: > > > >> The way I always did it when I needed a specific set of binaries for the > >> clients was to copy the entire /opt/ltsp/i386 subdirectory (or > >> /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) > >> to my K12LTSP server. Beforehand, I would typically rename the existing > >> /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. These binaries > >> should have *zero* affect on the server itself, since they run only on > >> the client. > >> > >> Give that a shot and let us know. > >> > >> --TP > >> > >> Stephen Kerr wrote: > >> > >>> Hi Barry, > >>> > >>> when i was trying to get my centos host run with a fedora 10 prebuilt > >>> chroot I had problems with the tc after loading the kernel from my dhcpd > >>> server on port 1067, the kernel loaded but the tc was making a second > >>> dhclient call but back on port 67 and not being able to load a desktop. > >>> i wound up moving sysinit_early and a couple other files from the centos > >>> chroot into fed10 prebuilt. > >>> > >>> it then behaved as it should have more or less. when i was on a telnet > >>> screen as defined in lts.conf, I was able to login. shell screens give a > >>> prompt at the TC, when i specified an x session screen, I had the x > >>> mouse cursor and gray/silver desktop background. > >>> > >>> the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the > >>> packages in the chroot are too old. i need to update libc from 2.3.2 and > >>> i cant find any utility thatll update the chroot so i have been trying > >>> to adapt ltsp-build-client from fedora, without success , so far. > >>> > >>> On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: > >>> > >>> > >>>> What are you seeing on the TC when it is completely booted up? From what > >>>> you explain you are only presented with a telnet login? No other > >>>> blinking as if X is trying to start? What have you set in your > >>>> lts.conf > >>>> file for screens? If you do CTL-ALT-F2 do you get a bash prompt? > >>>> > >>>> Barry > >>>> > >>>> > >>>> > From rowens at ptd.net Thu Feb 10 01:38:41 2011 From: rowens at ptd.net (Rob Owens) Date: Wed, 9 Feb 2011 20:38:41 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: <20110210013841.GC5474@aurora.owens.net> What about the tftpboot stuff? Will he need to copy Fedora's /var/lib/tftpboot to K12LTSP's /tftpboot, and update dhcpd.conf to load the newer kernels? -Rob On Wed, Feb 09, 2011 at 04:49:23PM -0500, Stephen Kerr wrote: > got you. thats what i was doing with the f10 prebuilt chroot. just > renaming the original ltsp and dropping the f10 one in. i did the same > with the kernels under tftpboot. > > it seems like thefed ltsp root work alot differently. unlike the centos > root, i could see fed10 aquiring the image on the desired port 1067, > load, then make a second dhclient call back to standard 67. i managed to > get that squared away , telnet worked but x was broken. got x working > but ldm wasnt loading. > > put that aside, got a pristine cent ltsp box back up moved moved most of > lib lib/modules lib/udev /usr/lib from the fed root in, kept existing > X and shell scripts and binaries. might be missing a couple of things. > tc came up without error. basic functionality ok. ran scanimage from tc > shell, not perfect but it saw the device and pulled the paper thru on > the old scanner. gonna bolt this on top of my kickstart, load the > sane-backend required for the new scanner and see what happens. > > > On Wed, 2011-02-09 at 16:15 -0500, Terrell Prude' Jr. wrote: > > Not exactly. I'm suggesting that you backup the existing /opt/ltsp/i386 > > subdirectory, or just rename it. Then, from your K12Linux Fedora > > 9/10/11/12/13/14/WhateverYouChoose box, copy *that* /opt/ltsp/i386 > > > subdirectory tree--the entire thing--over to your K12LTSP 5EL server. > > Your clients will thus be using that Fedora version of the client > > binaries vs. the ones that came with K12LTSP 5EL. > > > > --TP > > > > Stephen Kerr wrote: > > > not sure I completely follow. are you advising to backup the existing > > > directory , drop in the new c libraries (libc) and see what happens ? > > > > > > > > > On Tue, 2011-02-08 at 19:13 -0500, Terrell Prude' Jr. wrote: > > > > > >> The way I always did it when I needed a specific set of binaries for the > > >> clients was to copy the entire /opt/ltsp/i386 subdirectory (or > > >> /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) > > >> to my K12LTSP server. Beforehand, I would typically rename the existing > > >> /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. These binaries > > >> should have *zero* affect on the server itself, since they run only on > > >> the client. > > >> > > >> Give that a shot and let us know. > > >> > > >> --TP > > >> > > >> Stephen Kerr wrote: > > >> > > >>> Hi Barry, > > >>> > > >>> when i was trying to get my centos host run with a fedora 10 prebuilt > > >>> chroot I had problems with the tc after loading the kernel from my dhcpd > > >>> server on port 1067, the kernel loaded but the tc was making a second > > >>> dhclient call but back on port 67 and not being able to load a desktop. > > >>> i wound up moving sysinit_early and a couple other files from the centos > > >>> chroot into fed10 prebuilt. > > >>> > > >>> it then behaved as it should have more or less. when i was on a telnet > > >>> screen as defined in lts.conf, I was able to login. shell screens give a > > >>> prompt at the TC, when i specified an x session screen, I had the x > > >>> mouse cursor and gray/silver desktop background. > > >>> > > >>> the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the > > >>> packages in the chroot are too old. i need to update libc from 2.3.2 and > > >>> i cant find any utility thatll update the chroot so i have been trying > > >>> to adapt ltsp-build-client from fedora, without success , so far. > > >>> > > >>> On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: > > >>> > > >>> > > >>>> What are you seeing on the TC when it is completely booted up? From what > > >>>> you explain you are only presented with a telnet login? No other > > >>>> blinking as if X is trying to start? What have you set in your > > >>>> lts.conf > > >>>> file for screens? If you do CTL-ALT-F2 do you get a bash prompt? > > >>>> > > >>>> Barry > > >>>> > > >>>> > > >>>> > > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From microman at cmosnetworks.com Thu Feb 10 02:22:38 2011 From: microman at cmosnetworks.com (Terrell Prude' Jr.) Date: Wed, 09 Feb 2011 21:22:38 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: <20110210013841.GC5474@aurora.owens.net> References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> <20110210013841.GC5474@aurora.owens.net> Message-ID: <4D534BEE.7010405@cmosnetworks.com> Ah, hadn't thought of that. He might, but it's also possible the F10 binaries he's using will be just fine with that kernel rev. The only way to know is to try it. Fortunately, you'll know it right away, yay or nay. --TP Rob Owens wrote: > What about the tftpboot stuff? Will he need to copy Fedora's > /var/lib/tftpboot to K12LTSP's /tftpboot, and update dhcpd.conf to load > the newer kernels? > > -Rob > > On Wed, Feb 09, 2011 at 04:49:23PM -0500, Stephen Kerr wrote: > >> got you. thats what i was doing with the f10 prebuilt chroot. just >> renaming the original ltsp and dropping the f10 one in. i did the same >> with the kernels under tftpboot. >> >> it seems like thefed ltsp root work alot differently. unlike the centos >> root, i could see fed10 aquiring the image on the desired port 1067, >> load, then make a second dhclient call back to standard 67. i managed to >> get that squared away , telnet worked but x was broken. got x working >> but ldm wasnt loading. >> >> put that aside, got a pristine cent ltsp box back up moved moved most of >> lib lib/modules lib/udev /usr/lib from the fed root in, kept existing >> X and shell scripts and binaries. might be missing a couple of things. >> tc came up without error. basic functionality ok. ran scanimage from tc >> shell, not perfect but it saw the device and pulled the paper thru on >> the old scanner. gonna bolt this on top of my kickstart, load the >> sane-backend required for the new scanner and see what happens. >> >> >> On Wed, 2011-02-09 at 16:15 -0500, Terrell Prude' Jr. wrote: >> >>> Not exactly. I'm suggesting that you backup the existing /opt/ltsp/i386 >>> subdirectory, or just rename it. Then, from your K12Linux Fedora >>> 9/10/11/12/13/14/WhateverYouChoose box, copy *that* /opt/ltsp/i386 >>> >>> subdirectory tree--the entire thing--over to your K12LTSP 5EL server. >>> Your clients will thus be using that Fedora version of the client >>> binaries vs. the ones that came with K12LTSP 5EL. >>> >>> --TP >>> >>> Stephen Kerr wrote: >>> >>>> not sure I completely follow. are you advising to backup the existing >>>> directory , drop in the new c libraries (libc) and see what happens ? >>>> >>>> >>>> On Tue, 2011-02-08 at 19:13 -0500, Terrell Prude' Jr. wrote: >>>> >>>> >>>>> The way I always did it when I needed a specific set of binaries for the >>>>> clients was to copy the entire /opt/ltsp/i386 subdirectory (or >>>>> /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) >>>>> to my K12LTSP server. Beforehand, I would typically rename the existing >>>>> /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. These binaries >>>>> should have *zero* affect on the server itself, since they run only on >>>>> the client. >>>>> >>>>> Give that a shot and let us know. >>>>> >>>>> --TP >>>>> >>>>> Stephen Kerr wrote: >>>>> >>>>> >>>>>> Hi Barry, >>>>>> >>>>>> when i was trying to get my centos host run with a fedora 10 prebuilt >>>>>> chroot I had problems with the tc after loading the kernel from my dhcpd >>>>>> server on port 1067, the kernel loaded but the tc was making a second >>>>>> dhclient call but back on port 67 and not being able to load a desktop. >>>>>> i wound up moving sysinit_early and a couple other files from the centos >>>>>> chroot into fed10 prebuilt. >>>>>> >>>>>> it then behaved as it should have more or less. when i was on a telnet >>>>>> screen as defined in lts.conf, I was able to login. shell screens give a >>>>>> prompt at the TC, when i specified an x session screen, I had the x >>>>>> mouse cursor and gray/silver desktop background. >>>>>> >>>>>> the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the >>>>>> packages in the chroot are too old. i need to update libc from 2.3.2 and >>>>>> i cant find any utility thatll update the chroot so i have been trying >>>>>> to adapt ltsp-build-client from fedora, without success , so far. >>>>>> >>>>>> On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: >>>>>> >>>>>> >>>>>> >>>>>>> What are you seeing on the TC when it is completely booted up? From what >>>>>>> you explain you are only presented with a telnet login? No other >>>>>>> blinking as if X is trying to start? What have you set in your >>>>>>> lts.conf >>>>>>> file for screens? If you do CTL-ALT-F2 do you get a bash prompt? >>>>>>> >>>>>>> Barry >>>>>>> >>>>>>> >>>>>>> >>>>>>> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see >> > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From dyoung at mesd.k12.or.us Thu Feb 10 16:08:57 2011 From: dyoung at mesd.k12.or.us (Dan Young) Date: Thu, 10 Feb 2011 08:08:57 -0800 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: I'm a little late to the party here, and not to dissuade your work here... The LTSP5 setup used in the F10 K12Linux chroot is wildly different than that of the LTSP4.2 setup used in K12LTSP5.0.0EL, thus it's likely to be an uphill battle to make the chroot from one work with the other. The LTSP5 chroots are built at install-time from the hosting operating system, LTSP4 distributed an entire self-contained chroot environment. A comparison of LTSP4.2 and LTSP5: https://help.ubuntu.com/community/UbuntuLTSP/Tour I found the old LTSP4.2 era wiki archived here: http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/ -- Dan Young Multnomah ESD - Technology Services 503-257-1562 On Wed, Feb 9, 2011 at 1:49 PM, Stephen Kerr wrote: > got you. thats what i was doing with the f10 prebuilt chroot. just > renaming the original ltsp and dropping the f10 one in. i did the same > with the kernels under tftpboot. > > it seems like thefed ltsp root work alot differently. unlike the centos > root, i could see fed10 aquiring the image on the desired port 1067, > load, then make a second dhclient call back to standard 67. i managed to > get that squared away , telnet worked but x was broken. ?got x working > but ldm wasnt loading. > > put that aside, got a pristine cent ltsp box back up moved moved most of > lib ? lib/modules lib/udev /usr/lib from the fed root in, ?kept existing > X and shell scripts and binaries. might be missing a couple of things. > tc came up without error. basic functionality ok. ran scanimage from tc > shell, not perfect but it saw the device and pulled the paper thru on > the old scanner. gonna bolt this on top of my kickstart, load the > sane-backend required for the new scanner and see what happens. > > > On Wed, 2011-02-09 at 16:15 -0500, Terrell Prude' Jr. wrote: >> Not exactly. ?I'm suggesting that you backup the existing /opt/ltsp/i386 >> subdirectory, or just rename it. ?Then, from your K12Linux Fedora >> 9/10/11/12/13/14/WhateverYouChoose box, copy *that* /opt/ltsp/i386 > >> subdirectory tree--the entire thing--over to your K12LTSP 5EL server. >> Your clients will thus be using that Fedora version of the client >> binaries vs. the ones that came with K12LTSP 5EL. >> >> --TP >> >> Stephen Kerr wrote: >> > not sure I completely follow. ?are you advising to backup the existing >> > directory , drop in the new c libraries (libc) ?and see what happens ? >> > >> > >> > On Tue, 2011-02-08 at 19:13 -0500, Terrell Prude' Jr. wrote: >> > >> >> The way I always did it when I needed a specific set of binaries for the >> >> clients was to copy the entire /opt/ltsp/i386 subdirectory (or >> >> /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) >> >> to my K12LTSP server. ?Beforehand, I would typically rename the existing >> >> /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. ?These binaries >> >> should have *zero* affect on the server itself, since they run only on >> >> the client. >> >> >> >> Give that a shot and let us know. >> >> >> >> --TP >> >> >> >> Stephen Kerr wrote: >> >> >> >>> Hi Barry, >> >>> >> >>> when i was trying to get my centos host run with a fedora 10 prebuilt >> >>> chroot I had problems with the tc after loading the kernel from my dhcpd >> >>> server on port 1067, ?the kernel loaded but the tc was making a second >> >>> dhclient call but back on port 67 and not being able to load a desktop. >> >>> i wound up moving sysinit_early and a couple other files from the centos >> >>> chroot into fed10 prebuilt. >> >>> >> >>> ?it then ?behaved as it should have more or less. when i was on a telnet >> >>> screen as defined in lts.conf, I was able to login. shell screens give a >> >>> prompt at the TC, ?when i specified an x session screen, I had the x >> >>> mouse cursor and gray/silver desktop background. >> >>> >> >>> the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the >> >>> packages in the chroot are too old. i need to update libc from 2.3.2 and >> >>> i cant find any utility thatll update the chroot so i have been trying >> >>> to adapt ltsp-build-client from fedora, without success , so far. >> >>> >> >>> On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: >> >>> >> >>> >> >>>> What are you seeing on the TC when it is completely booted up? From what >> >>>> ? ? ? ? you explain you are only presented with a telnet login? No other >> >>>> ? ? ? ? blinking as if X is trying to start? What have you set in your >> >>>> ? ? ? ? lts.conf >> >>>> ? ? ? ? file for screens? If you do CTL-ALT-F2 do you get a bash prompt? >> >>>> >> >>>> ? ? ? ? Barry >> >>>> >> >>>> >> >>>> >> > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From skerr at rx30.com Thu Feb 10 17:03:17 2011 From: skerr at rx30.com (Stephen Kerr) Date: Thu, 10 Feb 2011 12:03:17 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: Hi Dan, yeah , I noticed things worked alot differently. I do have a frankenbox setup with primarily a K12LTSP5.0.0EL chroot, with all the libraries , or at least the great majority stripped out and replaced with those from a fed root. on this last attempt, i kept the cent kernel under tfptboot. I had been trying the wraplinux kernel from fed on previous incarnations. the tc comes up ok, worked lib inconsistencies out. all apps from the host come up ok. if i enter the tc shell i can communicate with a locally attached scanner, run scanimage and have it pull the paper thru, so I'm somewhat encouraged by that. however, if you have a decent way to update the chroot in K12LTSP5.0.0EL without having to kludge things like I have, I sure am interested. I noticed the ltsp-build-client script from fed and ubuntu. that would be perfect but not trivial to adapt i notice. I'm more or less married to getting a working ltsp implementation on my kickstart based on centos 5.4 .... and hopefully 6 .. someday, but 5.0 libraries in the chroot are pretty ancient and wont work with some of the hardware I need to get working. On Thu, 2011-02-10 at 08:08 -0800, Dan Young wrote: > I'm a little late to the party here, and not to dissuade your work here... > > The LTSP5 setup used in the F10 K12Linux chroot is wildly different > than that of the LTSP4.2 setup used in K12LTSP5.0.0EL, thus it's > likely to be an uphill battle to make the chroot from one work with > the other. The LTSP5 chroots are built at install-time from the > hosting operating system, LTSP4 distributed an entire self-contained > chroot environment. > > A comparison of LTSP4.2 and LTSP5: > https://help.ubuntu.com/community/UbuntuLTSP/Tour > > I found the old LTSP4.2 era wiki archived here: > http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/ > > -- > Dan Young > Multnomah ESD - Technology Services > 503-257-1562 > > > > On Wed, Feb 9, 2011 at 1:49 PM, Stephen Kerr wrote: > > got you. thats what i was doing with the f10 prebuilt chroot. just > > renaming the original ltsp and dropping the f10 one in. i did the same > > with the kernels under tftpboot. > > > > it seems like thefed ltsp root work alot differently. unlike the centos > > root, i could see fed10 aquiring the image on the desired port 1067, > > load, then make a second dhclient call back to standard 67. i managed to > > get that squared away , telnet worked but x was broken. got x working > > but ldm wasnt loading. > > > > put that aside, got a pristine cent ltsp box back up moved moved most of > > lib lib/modules lib/udev /usr/lib from the fed root in, kept existing > > X and shell scripts and binaries. might be missing a couple of things. > > tc came up without error. basic functionality ok. ran scanimage from tc > > shell, not perfect but it saw the device and pulled the paper thru on > > the old scanner. gonna bolt this on top of my kickstart, load the > > sane-backend required for the new scanner and see what happens. > > > > > > On Wed, 2011-02-09 at 16:15 -0500, Terrell Prude' Jr. wrote: > >> Not exactly. I'm suggesting that you backup the existing /opt/ltsp/i386 > >> subdirectory, or just rename it. Then, from your K12Linux Fedora > >> 9/10/11/12/13/14/WhateverYouChoose box, copy *that* /opt/ltsp/i386 > > > >> subdirectory tree--the entire thing--over to your K12LTSP 5EL server. > >> Your clients will thus be using that Fedora version of the client > >> binaries vs. the ones that came with K12LTSP 5EL. > >> > >> --TP > >> > >> Stephen Kerr wrote: > >> > not sure I completely follow. are you advising to backup the existing > >> > directory , drop in the new c libraries (libc) and see what happens ? > >> > > >> > > >> > On Tue, 2011-02-08 at 19:13 -0500, Terrell Prude' Jr. wrote: > >> > > >> >> The way I always did it when I needed a specific set of binaries for the > >> >> clients was to copy the entire /opt/ltsp/i386 subdirectory (or > >> >> /opt/ltsp/ppc, or /opt/ltsp/sparc, as appropriate for my architecture) > >> >> to my K12LTSP server. Beforehand, I would typically rename the existing > >> >> /opt/ltsp/i386 subdir. to, say, /opt/ltsp/i386.orig. These binaries > >> >> should have *zero* affect on the server itself, since they run only on > >> >> the client. > >> >> > >> >> Give that a shot and let us know. > >> >> > >> >> --TP > >> >> > >> >> Stephen Kerr wrote: > >> >> > >> >>> Hi Barry, > >> >>> > >> >>> when i was trying to get my centos host run with a fedora 10 prebuilt > >> >>> chroot I had problems with the tc after loading the kernel from my dhcpd > >> >>> server on port 1067, the kernel loaded but the tc was making a second > >> >>> dhclient call but back on port 67 and not being able to load a desktop. > >> >>> i wound up moving sysinit_early and a couple other files from the centos > >> >>> chroot into fed10 prebuilt. > >> >>> > >> >>> it then behaved as it should have more or less. when i was on a telnet > >> >>> screen as defined in lts.conf, I was able to login. shell screens give a > >> >>> prompt at the TC, when i specified an x session screen, I had the x > >> >>> mouse cursor and gray/silver desktop background. > >> >>> > >> >>> the K12LTSP-5.0.0EL-32bit iso worked perfectly, my only problem is the > >> >>> packages in the chroot are too old. i need to update libc from 2.3.2 and > >> >>> i cant find any utility thatll update the chroot so i have been trying > >> >>> to adapt ltsp-build-client from fedora, without success , so far. > >> >>> > >> >>> On Tue, 2011-02-08 at 15:09 -0600, Barry Cisna wrote: > >> >>> > >> >>> > >> >>>> What are you seeing on the TC when it is completely booted up? From what > >> >>>> you explain you are only presented with a telnet login? No other > >> >>>> blinking as if X is trying to start? What have you set in your > >> >>>> lts.conf > >> >>>> file for screens? If you do CTL-ALT-F2 do you get a bash prompt? > >> >>>> > >> >>>> Barry > >> >>>> > >> >>>> > >> >>>> > >> > > > > > > _______________________________________________ > > K12OSN mailing list > > K12OSN at redhat.com > > https://www.redhat.com/mailman/listinfo/k12osn > > For more info see > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From dyoung at mesd.k12.or.us Thu Feb 10 17:15:54 2011 From: dyoung at mesd.k12.or.us (Dan Young) Date: Thu, 10 Feb 2011 09:15:54 -0800 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: On Thu, Feb 10, 2011 at 9:03 AM, Stephen Kerr wrote: > however, if you have a decent way to update the chroot in K12LTSP5.0.0EL > without having to kludge things like I have, I sure am interested. I > noticed the ltsp-build-client script from fed and ubuntu. that would be > perfect but not trivial to adapt i notice. IIRC, the LTSP4 chroot is built from LBE (LTSP build environment?) Here are a few notes on that: http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/LBE http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/Build-LTSP-42 -- Dan Young Multnomah ESD - Technology Services 503-257-1562 From skerr at rx30.com Thu Feb 10 18:23:00 2011 From: skerr at rx30.com (Stephen Kerr) Date: Thu, 10 Feb 2011 13:23:00 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: Thanks for the Links Dan, I'll check them out. But Im happy to report Frankenbox works. K12LTSP5.0.0EL install, modded with fed10 libraries, keeping the cent udev and esd libs lib/modules, X and bash scripts. vmlinuz kernel from centos. dont recall which dhcpd.conf I started with, but modded to communicate on 1067. then copied to my kickstart based on centos 5.4. Then installed sane-backend1.0.21 on the host, copied output of rpm -ql sane-backend-1.0.21 into chroot and at last, new scanner working utilizing libc-2.8 in place of the original 2.3.2 On Thu, 2011-02-10 at 09:15 -0800, Dan Young wrote: > On Thu, Feb 10, 2011 at 9:03 AM, Stephen Kerr wrote: > > however, if you have a decent way to update the chroot in K12LTSP5.0.0EL > > without having to kludge things like I have, I sure am interested. I > > noticed the ltsp-build-client script from fed and ubuntu. that would be > > perfect but not trivial to adapt i notice. > > IIRC, the LTSP4 chroot is built from LBE (LTSP build environment?) > > Here are a few notes on that: > http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/LBE > http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/Build-LTSP-42 > > -- > Dan Young > Multnomah ESD - Technology Services > 503-257-1562 > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From skerr at rx30.com Thu Feb 10 20:59:59 2011 From: skerr at rx30.com (Stephen Kerr) Date: Thu, 10 Feb 2011 15:59:59 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: I gave the LBE link a quick read and it looks very promising. are there any practical limitations to kernels and package lists ? in other words would it be practical using LBE to build a chroot on the almost mythical centos 6 distribution when it comes out ? On Thu, 2011-02-10 at 09:15 -0800, Dan Young wrote: > On Thu, Feb 10, 2011 at 9:03 AM, Stephen Kerr wrote: > > however, if you have a decent way to update the chroot in K12LTSP5.0.0EL > > without having to kludge things like I have, I sure am interested. I > > noticed the ltsp-build-client script from fed and ubuntu. that would be > > perfect but not trivial to adapt i notice. > > IIRC, the LTSP4 chroot is built from LBE (LTSP build environment?) > > Here are a few notes on that: > http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/LBE > http://ltsp4.2.revamp-it.ch/twiki/bin/view/ltsp/Build-LTSP-42 > > -- > Dan Young > Multnomah ESD - Technology Services > 503-257-1562 > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From rowens at ptd.net Thu Feb 10 23:17:31 2011 From: rowens at ptd.net (Rob Owens) Date: Thu, 10 Feb 2011 18:17:31 -0500 Subject: [K12OSN] How to update K12LTSP-5.0.0EL-32bit chroot In-Reply-To: References: <1297199348.26531.39.camel@localhost.localdomain> <4D51DC2E.3060405@cmosnetworks.com> <4D53040F.8030208@cmosnetworks.com> Message-ID: <20110210231731.GA10524@aurora.owens.net> On Thu, Feb 10, 2011 at 03:59:59PM -0500, Stephen Kerr wrote: > I gave the LBE link a quick read and it looks very promising. are there > any practical limitations to kernels and package lists ? in other words > would it be practical using LBE to build a chroot on the almost mythical > centos 6 distribution when it comes out ? > I don't know the answer to your specific question, but I can tell you this: The reason the LTSP developers don't do things "the LTSP 4.2 way" anymore is because it was too much work for them to keep up with. "The LTSP 5 way" allows them to offload much of the work onto the various distributions. So it seems that the LTSP devs did not change ways because of a technical limitation. I can't say for sure that there aren't any technical limitations, but if you wanted to find out you might do better asking on the ltsp-discuss list. Several of the devs monitor that list. There is also a guy who has configured CentOS with LTSP 5. -Rob From brcisna at eazylivin.net Sat Feb 19 21:02:39 2011 From: brcisna at eazylivin.net (Barry Cisna) Date: Sat, 19 Feb 2011 15:02:39 -0600 Subject: [K12OSN] samba-vscan-clamav update Message-ID: <1298149359.29174.105.camel@localhost.localdomain> Hello All, Don't know if this will interest anyone here. Just made an updated samba-vscan-clamav rpm for recent versions of Samba. This is an binary rpm . The samba-vscan-clamav module had a bug in it that was broke for the last versions of samba.Patch has been applied and working now. If you are running samba as your file server this scanner works pretty nicely. This is built and tested on Samba-3.0333 which is one of the later versions for Centos 5.5. Providing the vfs module of samba has not changed this should work on the very latest versions of samba. Install the rpm, read the README for the two lines to add to your smb.conf and you are in business. This has snagged a lot of junk for our k-12 school setting for what it's worth. Hope this may help someone here. ftp://eazylivin.net/server/vscanclamav-3.0.33/ Take Care, Barry From microman at cmosnetworks.com Sat Feb 19 21:46:30 2011 From: microman at cmosnetworks.com (Terrell Prude' Jr.) Date: Sat, 19 Feb 2011 16:46:30 -0500 Subject: [K12OSN] samba-vscan-clamav update In-Reply-To: <1298149359.29174.105.camel@localhost.localdomain> References: <1298149359.29174.105.camel@localhost.localdomain> Message-ID: <4D603A36.6090407@cmosnetworks.com> Yes, it would interest me. Got a few small businesses on K12LTSP 5EL and sometimes some folks use MS Windows boxes. Thanks! --TP Barry Cisna wrote: > Hello All, > > Don't know if this will interest anyone here. > Just made an updated samba-vscan-clamav rpm for recent versions of > Samba. This is an binary rpm . > The samba-vscan-clamav module had a bug in it that was broke for the > last versions of samba.Patch has been applied and working now. > If you are running samba as your file server this scanner works pretty > nicely. This is built and tested on Samba-3.0333 which is one of the > later versions for Centos 5.5. > Providing the vfs module of samba has not changed this should work on > the very latest versions of samba. > Install the rpm, read the README for the two lines to add to your > smb.conf and you are in business. > This has snagged a lot of junk for our k-12 school setting for what it's > worth. > Hope this may help someone here. > > ftp://eazylivin.net/server/vscanclamav-3.0.33/ > > Take Care, > Barry > > > > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From cisna-barry at wc235.k12.il.us Tue Feb 22 12:14:17 2011 From: cisna-barry at wc235.k12.il.us (Barry Cisna) Date: Tue, 22 Feb 2011 06:14:17 -0600 Subject: [K12OSN] samba-vscan-clamav update Message-ID: <1298376857.16100.4.camel@hi2.wc235.k12.il.us> Terrell, When you have time let me know how the install goes with the vscanclamav rpm. If you download the latest rpm from the url I provided earlier you should not need to do anything,other than test your install with the eicar.com or eicar.zip file . If you are on a Windows machine, you should receive an "access denied" popup. Barry From lars.schade at berlin.de Sat Feb 26 15:19:07 2011 From: lars.schade at berlin.de (Lars Schade) Date: Sat, 26 Feb 2011 16:19:07 +0100 Subject: [K12OSN] Gnome-panels missing on clients Message-ID: <1298733547.15762.36.camel@rosinante.berlin> Hi, I recently ran across the Zotac ZBOX and thought it might make a good cheap this client for K12linux. So I got the ZBOX SD-ID10 and now have some issues/problems: - The bios does not support PXE, bummer. So I got a tiny USB-stick, put ipxe on it, and the thing boot from the stick into pxe. This work around seems to do the job. - Now the client boots ok, but when I log into the client the gnome panels are missing, any idea what the reason could be?? The ZBOX has an Atom D510 and the Intel NM10 chipset with a GMA 3150 for the graphics. Is that not supported or do I have to manually load drivers/modules? Does anyone have ideas or experience with the ZBOX or other Atom/GMA3150 based clients? -Lars From odin at gnuskole.no Sun Feb 27 19:52:16 2011 From: odin at gnuskole.no (=?UTF-8?Q?Odin_N=C3=B8sen?=) Date: Sun, 27 Feb 2011 20:52:16 +0100 Subject: [K12OSN] Gnome-panels missing on clients In-Reply-To: <1298733547.15762.36.camel@rosinante.berlin> References: <1298733547.15762.36.camel@rosinante.berlin> Message-ID: <20110227194440.M81725@gnuskole.no> > Does anyone have ideas or experience with the ZBOX or other Atom/GMA3150 > based clients? ZBOX HD-ID11 - Expensive. Very good on Fedora and Ubuntu (Intel cpu and nVidia chipset) ZBOX HD-AD01 - Middle priced. Very good on Fedora and Ubuntu (AMD cpu and AMD chipset) ZBOX HD-ID10 - Cheap. Problems on Fedora and Ubuntu (Intel cpu and Intel chipset) The BIOS supports PXE on all of the clients (but it's not enabled by default). The ID10-box has problems with Fedora were the gnome-panels are missing. On Ubuntu the screen resolution is bad (vesa-driver). There doesn't seems to be a functional linux-driver for the video card (Intel NM10). AD01 and ID11 works perfect. We like the AD01. It's a fabulous DRBL-client ;-) We try to avoid these Intel-video cards. Odin From lars.schade at berlin.de Mon Feb 28 18:11:55 2011 From: lars.schade at berlin.de (Lars Schade) Date: Mon, 28 Feb 2011 19:11:55 +0100 (CET) Subject: [K12OSN] Gnome-panels missing on clients Message-ID: <1298916715.171567-15699@martha.daybyday.de> Thanks for the info, Odin! Bummer, should have posted my question in the first place, now I am stuck with the problem of the Intel NM10/GMA3150. The hardware works fine when booting a fedora14 live-cd (in simple graphics mode) which I find promising. But it did not work when booting a fedora13 live-cd. So if anyone has experience/ideas on how to get the graphics problem fixed, help is appreciated. There is a driver by Intel for Linux for this chipset GMA3150. Any ideas? Odin, one more question since you have the ZBOX HD-AD01 on hands: Is there a fan installed for cooling? If so, what is the noise level in normal operation? -Lars ----- urspr?ngliche Nachricht --------- Subject: Re: [K12OSN] Gnome-panels missing on clients Date: So 27 Feb 2011 20:58:18 CET From: Odin N?sen To: Support list for open source software in schools.<k12osn at redhat.com> > Does anyone have ideas or experience with the ZBOX or other Atom/GMA3150 > based clients? ZBOX HD-ID11 - Expensive. Very good on Fedora and Ubuntu (Intel cpu and nVidia chipset) ZBOX HD-AD01 - Middle priced. Very good on Fedora and Ubuntu (AMD cpu and AMD chipset) ZBOX HD-ID10 - Cheap. Problems on Fedora and Ubuntu (Intel cpu and Intel chipset) The BIOS supports PXE on all of the clients (but it's not enabled by default). The ID10-box has problems with Fedora were the gnome-panels are missing. On Ubuntu the screen resolution is bad (vesa-driver). There doesn't seems to be a functional linux-driver for the video card (Intel NM10). AD01 and ID11 works perfect. We like the AD01. It's a fabulous DRBL-client ;-) We try to avoid these Intel-video cards. Odin _______________________________________________ K12OSN mailing list K12OSN at redhat.com https://www.redhat.com/mailman/listinfo/k12osn For more info see ---- urspr?ngliche Nachricht Ende ----