From brcisna at eazylivin.net Fri Jan 4 02:55:04 2013 From: brcisna at eazylivin.net (Barry R Cisna) Date: Thu, 03 Jan 2013 20:55:04 -0600 Subject: [K12OSN] Audio input on thin clients works ltsp 5. Message-ID: <1357268104.6216.21.camel@server1.eazylivin.net> Hello All, I had posted several days back,,asking about the status of audio input AKA mic interaction on thin clients sans ltsp 5. I finally got around to trying some things out. Happy to report that without any conf,,,juggling, plugging a mic in the front audio jack and testing with audacity i had sound input with ease out of the box and good sound I might add. I am wanting to try and get perlbox-voice to work on tc's if i can,This may be more of a challenge. For completeness i was running audacity as a default install on the server so for that app anyway there is no need to install audacity on the ltsp chroot. Take Care, Barry From radek at bursztynowski.waw.pl Mon Jan 7 21:48:29 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Mon, 7 Jan 2013 22:48:29 +0100 Subject: [K12OSN] K12Linux xfreerdp and Windows Server 2008 Message-ID: <1357595309.8318.100.camel@alpaga.bursztynowski.waw.pl> Hello, I have some problem with sound using xfreerdp with Windows Server 2008. In lts.conf I defined: SCREEN_05 = "xfreerdp -f -k pl -a 16 --plugin rdpsnd 192.168.0.189" where 192.168.0.189 is Windows Server 2008. When I log in to the Windows Server 2008 using xfreerdp I can see red sound icon with the information that "No Audio Output Devices is installed". The same configuration with Windows 7 plays the sound. Please advice me, what I should to do to solve it. Best regards, Radek From jvermeulen at cawdekempen.be Tue Jan 8 12:49:16 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Tue, 08 Jan 2013 13:49:16 +0100 Subject: [K12OSN] blue screen on Logoff In-Reply-To: References: Message-ID: <50EC15CC.6060704@cawdekempen.be> Dear All, I've setup a server from scratch to be able to test this further. In /var/log/Xorg_0_log I see no EM: [root at testserver i386]# tail -f /var/log/Xorg.0.log [ 40.549] AUDIT: Tue Jan 8 13:11:53 2013: 2422: client 23 disconnected [ 40.900] AUDIT: Tue Jan 8 13:11:53 2013: 2422: client 16 disconnected [ 40.901] AUDIT: Tue Jan 8 13:11:53 2013: 2422: client 14 disconnected [ 41.055] AUDIT: Tue Jan 8 13:11:53 2013: 2422: client 14 connected from local host ( uid=42 gid=42 pid=2536 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 279 [ 41.056] AUDIT: Tue Jan 8 13:11:53 2013: 2422: client 14 disconnected [ 41.462] AUDIT: Tue Jan 8 13:11:54 2013: 2422: client 15 disconnected [ 41.463] AUDIT: Tue Jan 8 13:11:54 2013: 2422: client 13 disconnected [ 71.226] AUDIT: Tue Jan 8 13:12:24 2013: 2422: client 22 disconnected [ 71.228] AUDIT: Tue Jan 8 13:12:24 2013: 2422: client 20 disconnected This is my /var/lib/tftpboot/ltsp/i386/lts.conf: [default] # X_COLOR_DEPTH=16 LDM_LANGUAGE=nl_BE.UTF_8 LOCALDEV=True SOUND=True X_NUMLOCK=True NBD_SWAP=True SYSLOG_HOST=server LDM_GLOBAL_DMRC=/etc/ltsp/ldm-global-dmrc XKBLAYOUT=be #LDM_NUMLOCK=true SCREEN_01=ldm # LDM_DIRECTX=yes is very insecure, but it is faster and more scalable LDM_DIRECTX=yes # LDM_DEBUG=yes writes to /var/log/ldm.log during client runtime LDM_DEBUG=yes The thinclient has an AMD Radeon HD 6290 graphical card, I think that is the problem. But I don't know where to make adjustments . Can anyone help? Thanks for any reply. Greetings, J. Op 15-12-12 19:28, Jim Kinney schreef: > > It sounds like the TC is where the problem is. X session ends on > server and local dm is not running as a service. > > On Dec 15, 2012 4:44 AM, "Johan Vermeulen" > wrote: > > Hello Jim, > > > thanks for the reply. I will check this when getting back to work. > > I assumed that log would just show output for the graphics card of > the server and not of the thin client. > > Greetings J. > verzonden m.b.v Android > vandaar de beknoptheid. > > Jim Kinney >schreef: > > >Sounds like the GDM/XDM/ login screen is not starting back up. The > >default X background is bright blue. It should be overlayed with the > >window manager specified stuff. ctl-alt-bkspc is killing X so the > >login screen reappears. > > > >Look in the /var/log/X.org logs for clues on why things are failing. > > > >I'm assuming the system is in runlevel 5. > > > >On Fri, Dec 14, 2012 at 9:18 AM, Johan Vermeulen > >> wrote: > >> Dear All, > >> > >> I'm testing a new thinclient, > >> the machine has an Asus Motherboard, an AMD c-60 APU with Radeon HD > >> Graphics. > >> At the moment it has 4096 MB (DDR3) > >> > >> So far everything runs very fast and good, BUT > >> when logging off it shows a very bright and very blue screen. > >> > >> The only way to get to the logon screen again is by pressing > >> ctrl-alt-2Xbackspace. > >> > >> Can anyone offer any advise on this? I don't know where to > start looking. > >> > >> many thanks for any help. > >> > >> Greetings, J. > >> > >> IT-medewerker > >> Caw De Kempen > >> > >> > >> Opensource Software is the future. > >> > >> _______________________________________________ > >> K12OSN mailing list > >> K12OSN at redhat.com > >> https://www.redhat.com/mailman/listinfo/k12osn > >> For more info see > > > > > > > >-- > >-- > >James P. Kinney III > > > >Every time you stop a school, you will have to build a jail. What you > >gain at one end you lose at the other. It's like feeding a dog on his > >own tail. It won't fatten the dog. > >- Speech 11/23/1900 Mark Twain > > > >http://electjimkinney.org > >http://heretothereideas.blogspot.com/ > > > >_______________________________________________ > >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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvermeulen at cawdekempen.be Tue Jan 8 16:42:22 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Tue, 08 Jan 2013 17:42:22 +0100 Subject: [K12OSN] use K12Linux with "PasswordAuthentication no" Message-ID: <50EC4C6E.2070601@cawdekempen.be> Dear All, in order to secure some servers, I would like to use "PasswordAuthentication no" in /etc/ssh/sshd_config However, if I do that, it goes for all interfaces, making it impossible to log in from the thinclients. Does anybody know of a workaround on order to still be able to do this? Many thanks for any advise. Greetings, J. -- Johan Vermeulen IT-medewerker Caw De Kempen johan.vermeulen at cawdekempen.be 0479.82.01.41 Opensource Software is the future. From jmalone at nrao.edu Tue Jan 8 16:36:03 2013 From: jmalone at nrao.edu (Josh Malone) Date: Tue, 08 Jan 2013 11:36:03 -0500 Subject: [K12OSN] use K12Linux with "PasswordAuthentication no" In-Reply-To: <50EC4C6E.2070601@cawdekempen.be> References: <50EC4C6E.2070601@cawdekempen.be> Message-ID: <24db980968442eee7ab6626c9549be27@nrao.edu> On 2013-01-08 11:42, Johan Vermeulen wrote: > Dear All, > > in order to secure some servers, I would like to use > "PasswordAuthentication no" in > /etc/ssh/sshd_config > > However, if I do that, it goes for all interfaces, making it > impossible to log in from the thinclients. > > Does anybody know of a workaround on order to still be able to do > this? > > Many thanks for any advise. > > Greetings, J. My gut instinct is to run 2 copies of sshd, one on each interface. I think you can just have 2 copies of the config file and start them with adding the "-f /etc/sshd_other_config" option. -Josh -- --------------------------------------------------------- Joshua Malone Systems Administrator (jmalone at nrao.edu) NRAO Charlottesville 434-296-0263 www.nrao.edu 434-249-5699 (mobile) --------------------------------------------------------- From jvermeulen at cawdekempen.be Tue Jan 8 16:55:38 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Tue, 08 Jan 2013 17:55:38 +0100 Subject: [K12OSN] use K12Linux with "PasswordAuthentication no" In-Reply-To: <24db980968442eee7ab6626c9549be27@nrao.edu> References: <50EC4C6E.2070601@cawdekempen.be> <24db980968442eee7ab6626c9549be27@nrao.edu> Message-ID: <50EC4F8A.9010405@cawdekempen.be> Op 08-01-13 17:36, Josh Malone schreef: > On 2013-01-08 11:42, Johan Vermeulen wrote: >> Dear All, >> >> in order to secure some servers, I would like to use >> "PasswordAuthentication no" in >> /etc/ssh/sshd_config >> >> However, if I do that, it goes for all interfaces, making it >> impossible to log in from the thinclients. >> >> Does anybody know of a workaround on order to still be able to do this? >> >> Many thanks for any advise. >> >> Greetings, J. > > My gut instinct is to run 2 copies of sshd, one on each interface. I > think you can just have 2 copies of the config file and start them > with adding the "-f /etc/sshd_other_config" option. > > -Josh That is exactly the solution I was looking for. Looks perfectly doable. Many thanks. Greetings, J. From cisna-barry at wc235.k12.il.us Wed Jan 9 11:52:54 2013 From: cisna-barry at wc235.k12.il.us (Barry Cisna) Date: Wed, 09 Jan 2013 05:52:54 -0600 Subject: [K12OSN] K12Linux xfreerdp and Windows Server 2008 Message-ID: <1357732374.6816.15.camel@wc19.wc235> Hi Radek, Are you sure your Windows 2008 server actually has a sound chip/card onboard? Do you get sound standing at the console of this server will tell you? Barry From radek at bursztynowski.waw.pl Wed Jan 9 12:17:14 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Wed, 9 Jan 2013 13:17:14 +0100 Subject: [K12OSN] K12Linux xfreerdp and Windows Server 2008 In-Reply-To: <1357732374.6816.15.camel@wc19.wc235> References: <1357732374.6816.15.camel@wc19.wc235> Message-ID: <1357733834.7788.27.camel@alpaga.bursztynowski.waw.pl> Barry, Many thanks for reply. This night I solved my problem which follows my ignorance of MS Windows Server. There are two steps to fix this problem: 1. Switch on audio device in Windows Server 2008 (by default is switched off - I didn't expect it!). 2. Execute the instruction: http://blogs.msdn.com/b/rds/archive/2009/07/24/multimedia-redirection-improvements-in-windows-7-and-ws2008-r2-part-1.aspx --- Now I try to connect USB device to LTSP thin client with xfreerdp with no success. I am going to post it in the separated mail with adequate subject. Best regards, Radek ---- > Hi Radek, > > Are you sure your Windows 2008 server actually has a sound chip/card > onboard? > Do you get sound standing at the console of this server will tell you? > > > Barry > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From radek at bursztynowski.waw.pl Wed Jan 9 12:28:05 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Wed, 9 Jan 2013 13:28:05 +0100 Subject: [K12OSN] xfreerdp Windows 7 and WIndows Server 2008 and USB devices conected to thin client Message-ID: <1357734485.7788.39.camel@alpaga.bursztynowski.waw.pl> Hello, I train xfreerdp with Windows 7 (W7) and Windows Server 2008 R2 (W2k8). After solving sound troubles with W2k8 I try to connect USB device to think client. For connection I used command: SCREEN_05 = "xfreerdp -f --ignore-certificate --no-nla -k 0x00000415 -a 16 --plugin rdpsnd --plugin rdpdr --data disk:usb05:/media/dupausb05 -- 192.168.0.4" 192.168.0.4 is Windows 7 computer. Network device in "Computer" window appears, but is empty. I have no problems with USB devices using LDM (SCREEN_01 = ldm). How to solve it? Is this the problem on LTSP linux environment or on Windows? Best regards, Radek From radek at bursztynowski.waw.pl Wed Jan 9 23:04:48 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 10 Jan 2013 00:04:48 +0100 Subject: [K12OSN] xfreerdp Windows 7 and WIndows Server 2008 and USB devices conected to thin client - SOLVED In-Reply-To: <1357734485.7788.39.camel@alpaga.bursztynowski.waw.pl> References: <1357734485.7788.39.camel@alpaga.bursztynowski.waw.pl> Message-ID: <1357772688.3750.15.camel@alpaga.bursztynowski.waw.pl> Hello again, I solved this by changing directory from /media/dupausb05 to /media Best regards, Radek ---- > Hello, > > I train xfreerdp with Windows 7 (W7) and Windows Server 2008 R2 (W2k8). > After solving sound troubles with W2k8 I try to connect USB device to > think client. > > For connection I used command: > > SCREEN_05 = "xfreerdp -f --ignore-certificate --no-nla -k 0x00000415 -a > 16 --plugin rdpsnd --plugin rdpdr --data disk:usb05:/media/dupausb05 -- > 192.168.0.4" > > 192.168.0.4 is Windows 7 computer. > > Network device in "Computer" window appears, but is empty. > > I have no problems with USB devices using LDM (SCREEN_01 = ldm). > > How to solve it? Is this the problem on LTSP linux environment or on > Windows? > > Best regards, > Radek > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From me at todhackett.com Sat Jan 12 14:44:52 2013 From: me at todhackett.com (Todd Hackett) Date: Sat, 12 Jan 2013 07:44:52 -0700 Subject: [K12OSN] Touch Monitor Message-ID: <50F176E4.7020301@todhackett.com> Hi All I haven't been able to find in information about using touch screen monitors on a thin client with PXE. One of my thin clients I have has a 'built-in' calibration widget and I assume the it will be OkieDokie, but the others are software controlled by XPe. I guess that I don't know and need to ask, does the thin client hardware handle this AFTER the calibration widget has been done? If not, where can I find drivers for the terminal server for this? I haven't loaded the TS ... yet as it won't do me any good if the touch screen(s) don't work with it. Thanks! todh -- Todd Hackett Chief Bottle Washer PoBox 1168 Libby, MT 59923 406.293.3843 From dean.jones at oregonstate.edu Mon Jan 14 17:54:30 2013 From: dean.jones at oregonstate.edu (Dean Jones) Date: Mon, 14 Jan 2013 09:54:30 -0800 Subject: [K12OSN] Touch Monitor In-Reply-To: <50F176E4.7020301@todhackett.com> References: <50F176E4.7020301@todhackett.com> Message-ID: What model is the touch screen? They work as long as the kernel knows the USB hardware for the touch panel, and X can be configured to use the display properly. ELO touchscreens work without any additional configuration. Some less popular screens need a bit of tweaking. I haven't bothered to calibrate the touch screens on thin clients. If you have any issues, let me know as I have notes about getting some of the lesser known models working. On Sat, Jan 12, 2013 at 6:44 AM, Todd Hackett wrote: > Hi All > > I haven't been able to find in information about using touch screen > monitors on a thin client with PXE. One of my thin clients I have has a > 'built-in' calibration widget and I assume the it will be OkieDokie, but > the others are software controlled by XPe. I guess that I don't know and > need to ask, does the thin client hardware handle this AFTER > the calibration widget has been done? If not, where can I find drivers > for the terminal server for this? I haven't loaded the TS ... yet as it > won't do me any good if the touch screen(s) don't work with it. > > Thanks! > > todh > > -- > Todd Hackett Chief Bottle Washer > PoBox 1168 > Libby, MT 59923 > 406.293.3843 > > ______________________________**_________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/**mailman/listinfo/k12osn > For more info see > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at todhackett.com Tue Jan 15 01:15:56 2013 From: me at todhackett.com (Todd Hackett) Date: Mon, 14 Jan 2013 18:15:56 -0700 Subject: [K12OSN] Login does not ... um ... login In-Reply-To: References: <50F176E4.7020301@todhackett.com> Message-ID: <50F4ADCC.2060509@todhackett.com> HI all Talked with Dean a bit about this and he suggested that I reload and try it again. Welp, did that and I have the same issue: thin client boots and comes up to the login screen, then when I enter logname and passwd, it waits, the recycles back to the login screen. I have NOT found any messages in /var/log/secure -or- [chroot] /var/log/secure. In fact, there are not any message at all about this issue. Ideas? todh On 01/14/2013 10:54 AM, Dean Jones wrote: > What model is the touch screen? > > They work as long as the kernel knows the USB hardware for the touch > panel, and X can be configured to use the display properly. ELO > touchscreens work without any additional configuration. Some less > popular screens need a bit of tweaking. > > I haven't bothered to calibrate the touch screens on thin clients. > > If you have any issues, let me know as I have notes about getting some > of the lesser known models working. > > > On Sat, Jan 12, 2013 at 6:44 AM, Todd Hackett > wrote: > > Hi All > > I haven't been able to find in information about using touch > screen monitors on a thin client with PXE. One of my thin clients > I have has a 'built-in' calibration widget and I assume the it > will be OkieDokie, but the others are software controlled by XPe. > I guess that I don't know and need to ask, does the thin client > hardware handle this AFTER > the calibration widget has been done? If not, where can I find > drivers for the terminal server for this? I haven't loaded the TS > ... yet as it won't do me any good if the touch screen(s) don't > work with it. > > Thanks! > > todh > > -- > Todd Hackett Chief Bottle Washer > PoBox 1168 > Libby, MT 59923 > 406.293.3843 > > _______________________________________________ > 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 -- Todd Hackett System Administrator POBox 1168 Libby, Montana 59923 406.293.3843 http://www.todhackett.com Network and Server Administration. Secure Firewall management. Antispam/antivirus eMail. Managed Web Hosting. Like trains? http://www.soundrail.com Got Stuff? http://www.libbystuff.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From burke at thealmquists.net Tue Jan 15 02:51:38 2013 From: burke at thealmquists.net (Burke Almquist) Date: Mon, 14 Jan 2013 20:51:38 -0600 Subject: [K12OSN] Login does not ... um ... login In-Reply-To: <50F4ADCC.2060509@todhackett.com> References: <50F176E4.7020301@todhackett.com> <50F4ADCC.2060509@todhackett.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 14, 2013, at 7:15 PM, Todd Hackett wrote: > HI all > > Talked with Dean a bit about this and he suggested that I reload and try it again. Welp, did that and I have the same issue: thin client boots and comes up to the login screen, then when I enter logname and passwd, it waits, the recycles back to the login screen. I have NOT found any messages in /var/log/secure -or- [chroot] /var/log/secure. In fact, there are not any message at all about this issue. > > Ideas? > If you go over to the server and try to log in, I assume the user logs in just fine? -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlD0xDoACgkQxWV7OPa/g5H9PACfWn1a3p4acxVeMYnFAAQHzgNy v58AnjmIS0GkBILQZCNeqJLIVKV5pXvF =ziHN -----END PGP SIGNATURE----- From me at todhackett.com Tue Jan 15 12:31:34 2013 From: me at todhackett.com (Todd Hackett) Date: Tue, 15 Jan 2013 05:31:34 -0700 Subject: [K12OSN] Login does not ... um ... login In-Reply-To: References: <50F176E4.7020301@todhackett.com> <50F4ADCC.2060509@todhackett.com> Message-ID: <50F54C26.2000508@todhackett.com> Yes. It all works just fine on the server. I am gonna install the Virt Desktop today and see what that can tell me On 01/14/2013 07:51 PM, Burke Almquist wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Jan 14, 2013, at 7:15 PM, Todd Hackett wrote: > >> HI all >> >> Talked with Dean a bit about this and he suggested that I reload and try it again. Welp, did that and I have the same issue: thin client boots and comes up to the login screen, then when I enter logname and passwd, it waits, the recycles back to the login screen. I have NOT found any messages in /var/log/secure -or- [chroot] /var/log/secure. In fact, there are not any message at all about this issue. >> >> Ideas? >> > > If you go over to the server and try to log in, I assume the user logs in just fine? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iEYEARECAAYFAlD0xDoACgkQxWV7OPa/g5H9PACfWn1a3p4acxVeMYnFAAQHzgNy > v58AnjmIS0GkBILQZCNeqJLIVKV5pXvF > =ziHN > -----END PGP SIGNATURE----- > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > -- Todd Hackett System Administrator POBox 1168 Libby, Montana 59923 406.293.3843 http://www.todhackett.com Network and Server Administration. Secure Firewall management. Antispam/antivirus eMail. Managed Web Hosting. Like trains? http://www.soundrail.com Got Stuff? http://www.libbystuff.com From jvermeulen at cawdekempen.be Tue Jan 15 13:01:44 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Tue, 15 Jan 2013 14:01:44 +0100 Subject: [K12OSN] Login does not ... um ... login In-Reply-To: <50F54C26.2000508@todhackett.com> References: <50F176E4.7020301@todhackett.com> <50F4ADCC.2060509@todhackett.com> <50F54C26.2000508@todhackett.com> Message-ID: <50F55338.20609@cawdekempen.be> Op 15-01-13 13:31, Todd Hackett schreef: > Yes. It all works just fine on the server. I am gonna install the > Virt Desktop today and see what that can tell me > > On 01/14/2013 07:51 PM, Burke Almquist wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> On Jan 14, 2013, at 7:15 PM, Todd Hackett wrote: >> >>> HI all >>> >>> Talked with Dean a bit about this and he suggested that I reload and >>> try it again. Welp, did that and I have the same issue: thin client >>> boots and comes up to the login screen, then when I enter logname >>> and passwd, it waits, the recycles back to the login screen. I have >>> NOT found any messages in /var/log/secure -or- [chroot] >>> /var/log/secure. In fact, there are not any message at all about >>> this issue. >>> >>> Ideas? >>> >> >> If you go over to the server and try to log in, I assume the user >> logs in just fine? >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG/MacGPG2 v2.0.17 (Darwin) >> Comment: GPGTools - http://gpgtools.org >> >> iEYEARECAAYFAlD0xDoACgkQxWV7OPa/g5H9PACfWn1a3p4acxVeMYnFAAQHzgNy >> v58AnjmIS0GkBILQZCNeqJLIVKV5pXvF >> =ziHN >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see >> > hello, I had a problem some time ago, couldn't log in, no EM, turned out the issue occured because I changed IP adresses. Solved in my case with: #ltsp-update-sshkeys greetings, J. From skerr at rx30.com Tue Jan 15 13:43:03 2013 From: skerr at rx30.com (Steve) Date: Tue, 15 Jan 2013 08:43:03 -0500 Subject: [K12OSN] Login does not ... um ... login In-Reply-To: <50F55338.20609@cawdekempen.be> References: <50F176E4.7020301@todhackett.com> <50F4ADCC.2060509@todhackett.com> <50F54C26.2000508@todhackett.com> <50F55338.20609@cawdekempen.be> Message-ID: <50F55CE7.1000006@rx30.com> I had a similliar issue. was able to get to the TC shell console and ssh to the server. i had to answer yes to accept the server as a known host. afterward login worked fine. On 01/15/2013 08:01 AM, Johan Vermeulen wrote: > > Op 15-01-13 13:31, Todd Hackett schreef: >> Yes. It all works just fine on the server. I am gonna install the >> Virt Desktop today and see what that can tell me >> >> On 01/14/2013 07:51 PM, Burke Almquist wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> >>> On Jan 14, 2013, at 7:15 PM, Todd Hackett wrote: >>> >>>> HI all >>>> >>>> Talked with Dean a bit about this and he suggested that I reload and >>>> try it again. Welp, did that and I have the same issue: thin client >>>> boots and comes up to the login screen, then when I enter logname >>>> and passwd, it waits, the recycles back to the login screen. I have >>>> NOT found any messages in /var/log/secure -or- [chroot] >>>> /var/log/secure. In fact, there are not any message at all about >>>> this issue. >>>> >>>> Ideas? >>>> >>> If you go over to the server and try to log in, I assume the user >>> logs in just fine? >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG/MacGPG2 v2.0.17 (Darwin) >>> Comment: GPGTools - http://gpgtools.org >>> >>> iEYEARECAAYFAlD0xDoACgkQxWV7OPa/g5H9PACfWn1a3p4acxVeMYnFAAQHzgNy >>> v58AnjmIS0GkBILQZCNeqJLIVKV5pXvF >>> =ziHN >>> -----END PGP SIGNATURE----- >>> >>> _______________________________________________ >>> K12OSN mailing list >>> K12OSN at redhat.com >>> https://www.redhat.com/mailman/listinfo/k12osn >>> For more info see >>> > hello, > > I had a problem some time ago, couldn't log in, no EM, turned out the > issue occured because I changed IP adresses. > > Solved in my case with: > > #ltsp-update-sshkeys > > greetings, J. > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From me at todhackett.com Tue Jan 15 14:30:15 2013 From: me at todhackett.com (me) Date: Tue, 15 Jan 2013 06:30:15 -0800 Subject: [K12OSN] Ok, so for the *dumb* questions? In-Reply-To: <50F55CE7.1000006@rx30.com> References: <50F176E4.7020301@todhackett.com> <50F4ADCC.2060509@todhackett.com> <50F54C26.2000508@todhackett.com> <50F55338.20609@cawdekempen.be> <50F55CE7.1000006@rx30.com> Message-ID: <20130115141119.M96534@todhackett.com> Hi All Instead of using the 'login window' I [ctl][alt] to F3 and got to a bash prompt on the thin client. This did NOT show the normal login and dumped me into the filesystem "/". 'whoami' says I am root. I have trouble with this as it is a BIG security problem. Sure, I can fix that by not setting SCREEN_?? in the lts.conf, but what if I forget? I guess that it would only affect the filesystem on the client, but ssh IS available ( yes, have a good password AND not on the usual port ) so some nefarious no gooder could possibly bang at the server. Oh, and yes I could ssh to the server and login; didn't ask me the usual 'accept' question though. Next, there are no errors in Xorg.1.log but boot.log was another matter: Mounting local filesystems: FAILED Starting NFS statd: FAILED Setting NIS domain: not found FAILED the local filesystem failure is probably moot, but I don't know about the other two. bash-4.1# [startx] dies - module mach64 not found - so ima gonna go and figure out where that is! It will work ....someday.... sigh! On Tue, 15 Jan 2013 08:43:03 -0500, Steve wrote > I had a similliar issue. was able to get to the TC shell console and ssh > to the server. i had to answer yes to accept the server as a known host. > afterward login worked fine. -- Todd Hackett Chief Bottle Washer PoBox 1168 Libby, MT 59923 406.293.3843 From bfristen at shaw.ca Tue Jan 15 15:47:24 2013 From: bfristen at shaw.ca (Brian Fristensky) Date: Tue, 15 Jan 2013 09:47:24 -0600 Subject: [K12OSN] Login does not ... um ... login In-Reply-To: <50F55338.20609@cawdekempen.be> References: <50F176E4.7020301@todhackett.com> <50F4ADCC.2060509@todhackett.com> <50F54C26.2000508@todhackett.com> <50F55338.20609@cawdekempen.be> Message-ID: <50F57A0C.5010006@shaw.ca> I missed your first post, but I am assuming that what happens is that you get the login prompt on the TC, type in your userid and password, and get kicked back to the login prompt. I should preface this by saying that this was the solution with LTSP 5.2.4.5. I am currently using 5.2.17-el6, which I installed over a year ago, and I don't remember if it also had this problem. With LTSP, once I get it to work, I try very hard not to monkey with it! This was the problem: 1. ltsp fails to read /var/lib/tftpboot/ltsp/i386/lts.conf from the host when the thin client boots. The only way to fix this problem is to copy the lts.conf file to /opt/ltsp/i386/etc/lts.conf on the host. If you are using NBD, each time this file is changed, you need to rerun ltsp-update-image. 2. The reason this is a problem is that the ldm client on the TC seems to be missing important environment variables. At the very least, we need to include in lts.conf a line reading LDM_XSESSION=gnome-session or whatever your desired session is. -- Brian Fristensky -------------- next part -------------- An HTML attachment was scrubbed... URL: From radek at bursztynowski.waw.pl Tue Jan 15 18:41:20 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Tue, 15 Jan 2013 19:41:20 +0100 Subject: [K12OSN] Troubles with sound Message-ID: <1358275280.32715.18.camel@alpaga.bursztynowski.waw.pl> Hi All I have some troubles with sound. 1) Scientific Linux 6.1 thin client image. When I login to Linux using LDM the sound works fine. When I login to Windows using xfreerdp there is mono sound only. 2) Fedora 14 thin client image. When I login to Linux using LDM or to Windows using xfreerdp there is sound stereo but within few seconds only. After few seconds I can hear silence. What I should to do to fix my sound problem? Best regards, Radek From burke at thealmquists.net Wed Jan 16 00:34:16 2013 From: burke at thealmquists.net (Burke Almquist) Date: Tue, 15 Jan 2013 18:34:16 -0600 Subject: [K12OSN] Ok, so for the *dumb* questions? In-Reply-To: <20130115141119.M96534@todhackett.com> References: <50F176E4.7020301@todhackett.com> <50F4ADCC.2060509@todhackett.com> <50F54C26.2000508@todhackett.com> <50F55338.20609@cawdekempen.be> <50F55CE7.1000006@rx30.com> <20130115141119.M96534@todhackett.com> Message-ID: On Jan 15, 2013, at 8:30 AM, me wrote: > Hi All > > Instead of using the 'login window' I [ctl][alt] to F3 and got to a bash prompt on the > thin client. This did NOT show the normal login and dumped me into the filesystem "/". > 'whoami' says I am root. I have trouble with this as it is a BIG security problem. > Sure, I can fix that by not setting SCREEN_?? in the lts.conf, but what if I forget? I > guess that it would only affect the filesystem on the client, but ssh IS available ( > yes, have a good password AND not on the usual port ) so some nefarious no gooder could > possibly bang at the server. Oh, and yes I could ssh to the server and login; didn't ask > me the usual 'accept' question though. It's not ideal, but OTOH if the students have physical access to the network (a room with a network jack in it), then they certainly could do far worse things, like booting the client from a usb stick with their own malicious tools or sneaking a laptop onto the network. If you are practicing defense in depth, then you assume that even internal users might behave maliciously and set your security accordingly. As for ssh http://www.la-samhna.de/library/brutessh.html http://forums.contribs.org/index.php?topic=40632.5;wap2 I've found these suggestions helpful. > > Next, there are no errors in Xorg.1.log but boot.log was another matter: > Mounting local filesystems: FAILED > Starting NFS statd: FAILED > Setting NIS domain: not found FAILED > > the local filesystem failure is probably moot, but I don't know about the other two. > > bash-4.1# [startx] dies - module mach64 not found - so ima gonna go and figure out where > that is! This makes me wonder EL6 has drivers for your video. How old is the video chipset on those clients? Have you tried setting up a chroot using a FC11? > > It will work ....someday.... sigh! From brcisna at eazylivin.net Wed Jan 16 01:04:14 2013 From: brcisna at eazylivin.net (Barry R Cisna) Date: Tue, 15 Jan 2013 19:04:14 -0600 Subject: [K12OSN] Wifi AP on the cheap Message-ID: <1358298254.32325.16.camel@server1.eazylivin.net> Hello All, Not really K12Linux specific,but thought possibly someone here may be interested in a wifi AP on the cheap to add to their existing K12Linux server to make it even more functional. You can buy one of the N150 mini-usb dongles on Ebay for $7 USD shipped. This is the Ralink RT5370 chipset. This can be made to run in master mode (AP) with the use of the hostapd piece. Very few usb sticks will actually work in AP I have found. One caveat is the driver/firmware for this that will run AP mode will only work at 54mb speed. It took some wrangling to get this to work but have used it for two weeks now and is rock solid. I have my home server in my basement and get a good to fair signal on the main floor and is very adequate.Smartphone, laptop, usually shows connected at 54mb. If anyone is interested I would be glad build an rpm for both 32-bit and 64-bit CentOS 6, SL6, that would plop the driver(s)/firmware , hostapd, configs, pieces all in one rpm as binaries for convenience. Take Care, Barry From brcisna at eazylivin.net Wed Jan 16 03:50:27 2013 From: brcisna at eazylivin.net (Barry R Cisna) Date: Tue, 15 Jan 2013 21:50:27 -0600 Subject: [K12OSN] Troubles with sound Message-ID: <1358308227.32325.23.camel@server1.eazylivin.net> Radeck, Do you get the exact same results of the sound behaviour on many clients? Various sound cards can present various problems it seems. The Fedora 14 problem is very odd that your sound works for just a few seconds then quits. Here is a pretty good link, that may give you a better understanding of Alsa sound and some troubleshooting tips. http://alsa.opensrc.org/TroubleShooting When using xfreedesktop or any remote login client can really present another set of problems as far as sound 'redirection" If you get each item figured out post back your findings. Sorry I couldn't be more help. Take Care, Barry From radek at bursztynowski.waw.pl Wed Jan 16 08:14:28 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Wed, 16 Jan 2013 09:14:28 +0100 Subject: [K12OSN] Troubles with sound In-Reply-To: <1358308227.32325.23.camel@server1.eazylivin.net> References: <1358308227.32325.23.camel@server1.eazylivin.net> Message-ID: <1358324068.31165.6.camel@alpaga.bursztynowski.waw.pl> Barry, Thanks for reply. Yes, the sound behaviour doesn't depend on thin client. I tested it on 7 different clients with different sound cards. Thanks for the link - I am going to see it today. Best regards, Radek > Radeck, > > Do you get the exact same results of the sound behaviour on many > clients? Various sound cards can present various problems it seems. > > The Fedora 14 problem is very odd that your sound works for just a few > seconds then quits. > > Here is a pretty good link, that may give you a better understanding > of Alsa sound and some troubleshooting tips. > > > http://alsa.opensrc.org/TroubleShooting > > When using xfreedesktop or any remote login client can really present > another set of problems as far as sound 'redirection" > > If you get each item figured out post back your findings. > Sorry I couldn't be more help. > > Take Care, > Barry > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From ngaywood at une.edu.au Thu Jan 17 04:34:55 2013 From: ngaywood at une.edu.au (Norman Gaywood) Date: Thu, 17 Jan 2013 15:34:55 +1100 Subject: [K12OSN] Update for kernel-thinclient Message-ID: Hi all, Is there a way to update the kernel-thinclient kernel to be the latest SL kernel? I currently have some display hardware not supported by kernel-thinclient-2.6.32-131.6.1.el6.i686.rpm -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngaywood at une.edu.au Phone: +61 (0)2 6773 2412 http://mcs.une.edu.au/~norm Fax: +61 (0)2 6773 3312 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvermeulen at cawdekempen.be Thu Jan 17 13:15:23 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Thu, 17 Jan 2013 14:15:23 +0100 Subject: [K12OSN] Update for kernel-thinclient In-Reply-To: References: Message-ID: <50F7F96B.4060600@cawdekempen.be> +1. this would maybe solve some of my problems too Op 17-01-13 05:34, Norman Gaywood schreef: > Hi all, > > Is there a way to update the kernel-thinclient kernel to be the latest > SL kernel? > > I currently have some display hardware not supported by > kernel-thinclient-2.6.32-131.6.1.el6.i686.rpm > > > -- > Norman Gaywood, Computer Systems Officer > University of New England, Armidale, > NSW 2351, Australia > > ngaywood at une.edu.au Phone: +61 > (0)2 6773 2412 > http://mcs.une.edu.au/~norm Fax: > +61 (0)2 6773 3312 > > Please avoid sending me Word or Power Point attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at todhackett.com Thu Jan 17 14:06:19 2013 From: me at todhackett.com (me) Date: Thu, 17 Jan 2013 06:06:19 -0800 Subject: [K12OSN] More dumb questions .... Message-ID: <20130117140001.M10617@todhackett.com> Hi all Have a desktop on the TC. I am a little confused though. It looks to be the same desktop that is on the ltsp server if I log in. I figured it would be ...um... different? Also, have no permission to write anything, so I need to enable that somewhere? And, getting strange errors from php running on a local webserver; ( another box ) about session issues when I hit it from the TC. Ideas? thanks! -- Todd Hackett Chief Bottle Washer PoBox 1168 Libby, MT 59923 406.293.3843 From me at todhackett.com Thu Jan 17 15:39:46 2013 From: me at todhackett.com (me) Date: Thu, 17 Jan 2013 07:39:46 -0800 Subject: [K12OSN] More dumb questions .... In-Reply-To: <20130117140001.M10617@todhackett.com> References: <20130117140001.M10617@todhackett.com> Message-ID: <20130117153651.M35344@todhackett.com> On Thu, 17 Jan 2013 06:06:19 -0800, me wrote > And, getting strange errors from php running on a local webserver; ( another > box ) about session issues when I hit it from the TC. Ok, so weirdness happens - I don't know if it was an update or what. Been using the menu system on the local webserver for months. PHP wasn't in any of the updates, but we did do a kernel update the other day. Guess that they fixed the permissions? I had to change the owner of the session_files to fix the above error. Sure, OT but geesh! todh -- Todd Hackett Chief Bottle Washer PoBox 1168 Libby, MT 59923 406.293.3843 From burke at thealmquists.net Thu Jan 17 19:56:48 2013 From: burke at thealmquists.net (burke at thealmquists.net) Date: Thu, 17 Jan 2013 13:56:48 -0600 Subject: [K12OSN] More dumb questions .... Message-ID: The desktops should be the same. Ltsp clients boot a minimal os, just enough to establish a connection to the server. The desktop session is actually running on the server by default. The magic of ltsp is that it automatically makes local devices from the client (mouse, display, sound, usb sticks, etc) available to the server, where your session is actually happening. From brcisna at eazylivin.net Sat Jan 19 21:31:59 2013 From: brcisna at eazylivin.net (Barry R Cisna) Date: Sat, 19 Jan 2013 15:31:59 -0600 Subject: [K12OSN] Ralink rt5370 driver with hostapd Message-ID: <1358631119.31019.23.camel@server1.eazylivin.net> Hello All, CentOS 6.x 32-bit This is for sure not K12Linux specific but thought I would post the rt5370hostapd rpm I built up, that makes the N150 Ralink rt5370 mini-usb wifi dongle work in AP mode. These usb sticks can be had on Ebay for $7 shipped. This rpm throws everything needed into one install and is installing binaries. Tested on 8 different kernel versions of CentOS 6.x. Not tested on the 3.0.x version of the experimental kernels that are available. For post installation configuration help view the README that is installed into the docs directory. rt5370hostapd-1.0. ftp://eazylivin.net/server/rt5370hostapd/ Hope this may help someone. Barry From me at todhackett.com Mon Jan 21 11:51:14 2013 From: me at todhackett.com (Todd Hackett) Date: Mon, 21 Jan 2013 04:51:14 -0700 Subject: [K12OSN] Printer problems Message-ID: <50FD2BB2.4040104@todhackett.com> Hi All Almost everything us up and operational - pretty kwel! Can't seem to get a printer working though. Have the PRINTER_0_??? things in lts.conf and I updated the image. Looking at DMESG on the client shows printer stuff, but I can't print. When the client boots, the printer resets and home's about 3/4 of the way through the boot so I know it is connected and listening. I must be missing something ... ideas? Thanks! -- Todd Hackett System Administrator POBox 1168 Libby, Montana 59923 406.293.3843 http://www.todhackett.com Network and Server Administration. Secure Firewall management. Antispam/antivirus eMail. Managed Web Hosting. Like trains? http://www.soundrail.com Got Stuff? http://www.libbystuff.com From cisna-barry at wc235.k12.il.us Mon Jan 21 12:46:52 2013 From: cisna-barry at wc235.k12.il.us (Barry Cisna) Date: Mon, 21 Jan 2013 06:46:52 -0600 Subject: [K12OSN] Printer problems Message-ID: <1358772412.6816.80.camel@wc19.wc235> Todd, Do you have the following line(s) for this client in your lts.conf ? (you showed only the one line lts.conf config in your post) 1) [MA:CD:DR:ES:SS:SS(myclient)] PRINTER_0_DEVICE=/dev/usb/lp0 (or /dev/usblp0) PRINTER_0_TYPE=U On the TC drop to a shell and do ls -la /dev/usb/ You should see /lp# 2) Asking the obvious . You did add the driver for this printer to the server? Did this printer work alright connected to the server itself? 3) What brand of printer is it. Some Lexmark printers are very difficult to get working on ltsp,or any Linux distro for that matter. Take Care, Barry From julius at turtle.com Mon Jan 21 14:19:48 2013 From: julius at turtle.com (julius at turtle.com) Date: Mon, 21 Jan 2013 09:19:48 -0500 Subject: [K12OSN] Printer problems In-Reply-To: <1358772412.6816.80.camel@wc19.wc235> Message-ID: <847737ab90401fbb597ac8b36bef4e0b08e20563@webmail.turtle.com> I seem to have better luck with? PRINTER_0_TYPE = S when the printer is USB ----- Original Message ----- From: "Support list for open source software in schools." To:"K12LTSP Mailing List" Cc: Sent:Mon, 21 Jan 2013 06:46:52 -0600 Subject:Re: [K12OSN] Printer problems Todd, Do you have the following line(s) for this client in your lts.conf ? (you showed only the one line lts.conf config in your post) 1) [MA:CD:DR:ES:SS:SS(myclient)] PRINTER_0_DEVICE=/dev/usb/lp0 (or /dev/usblp0) PRINTER_0_TYPE=U On the TC drop to a shell and do ls -la /dev/usb/ You should see /lp# 2) Asking the obvious . You did add the driver for this printer to the server? Did this printer work alright connected to the server itself? 3) What brand of printer is it. Some Lexmark printers are very difficult to get working on ltsp,or any Linux distro for that matter. Take Care, Barry _______________________________________________ K12OSN mailing list K12OSN at redhat.com https://www.redhat.com/mailman/listinfo/k12osn For more info see This email is confidential and intended solely for the use of the individual to whom it is addressed. Please note, any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Turtle & Hughes, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From redtex at mail.ru Wed Jan 23 06:27:35 2013 From: redtex at mail.ru (=?UTF-8?B?V2FkaW0gSW5jb2duaXRv?=) Date: Wed, 23 Jan 2013 10:27:35 +0400 Subject: [K12OSN] =?utf-8?q?Update_for_kernel-thinclient?= In-Reply-To: <50F7F96B.4060600@cawdekempen.be> References: <50F7F96B.4060600@cawdekempen.be> Message-ID: <1358922455.638047500@f27.mail.ru> Yes, you can (for EL chroot): Go to LTSP chroot: su cd /opt/ltsp/i386 setarch i386 chroot . mount -t proc proc /proc Update SL in Chroot: yum update yum clean all yum --releasever=6.3 update sl-release yum update yum clean all Install Generic SL kernel: yum install kernel That's all, now you have SL 6.3 latst kernel, and updated chroot.? ? ???????, 17 ?????? 2013, 14:15 +01:00 ?? Johan Vermeulen : >+1. this would maybe solve some of my problems too > >Op 17-01-13 05:34, Norman Gaywood schreef: >>Hi all, >> >>Is there a way to update the kernel-thinclient kernel to be the latest SL kernel? >> >>I currently have some display hardware not supported by? kernel-thinclient-2.6.32-131.6.1.el6.i686.rpm >> >>-- >>Norman Gaywood, Computer Systems Officer >>University of New England, Armidale, >>NSW 2351, Australia >> >>ngaywood at une.edu.au ? ? ? ? ? ?Phone: +61 (0)2 6773 2412 >>http://mcs.une.edu.au/~norm ? ?Fax: ? +61 (0)2 6773 3312 >> >>Please avoid sending me Word or Power Point attachments. >>See http://www.gnu.org/philosophy/no-word-attachments.html >> >> >>_______________________________________________ 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 < http://www.k12os.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jomegat at jomegat.com Wed Jan 23 16:35:05 2013 From: jomegat at jomegat.com (Jomegat) Date: Wed, 23 Jan 2013 11:35:05 -0500 Subject: [K12OSN] Samba print server Message-ID: <51001139.9010508@jomegat.com> Hi everyone, Our teacher has a Win7 laptop and would dearly love to print to my K12LTSP EL6 (64-bit) machine's printer. I have been going around in circles for a while trying to get it set up, but nothing I do seems to work. Does anyone have an smb.conf file that does this? Would you mind sharing it? Alternatively, could someone point me to a howto on this specific to K12LTSP? -- Jim Thomas (a.k.a. J Omega T) jomegat at jomegat.com I thought I was wrong once, but I was mistaken. From jomegat at jomegat.com Wed Jan 23 17:17:47 2013 From: jomegat at jomegat.com (Jomegat) Date: Wed, 23 Jan 2013 12:17:47 -0500 Subject: [K12OSN] Samba print server In-Reply-To: <51001139.9010508@jomegat.com> References: <51001139.9010508@jomegat.com> Message-ID: <51001B3B.7060000@jomegat.com> On 01/23/2013 11:35 AM, Jomegat wrote: > Hi everyone, > > Our teacher has a Win7 laptop and would dearly love to print to my > K12LTSP EL6 (64-bit) machine's printer. I have been going around in > circles for a while trying to get it set up, but nothing I do seems to > work. > > Does anyone have an smb.conf file that does this? Would you mind > sharing it? > > Alternatively, could someone point me to a howto on this specific to > K12LTSP? > Nevermind. I got it working. Not sure what I did though . :-/ -- Jim Thomas (a.k.a. J Omega T) jomegat at jomegat.com I thought I was wrong once, but I was mistaken. From william at fragakis.com Wed Jan 23 17:38:39 2013 From: william at fragakis.com (William Fragakis) Date: Wed, 23 Jan 2013 12:38:39 -0500 Subject: [K12OSN] Update for kernel-thinclient In-Reply-To: References: Message-ID: <1358962719.29663.37.camel@server.ltsp> On Wed, 2013-01-23 at 12:00 -0500, k12osn-request at redhat.com wrote: > Message: 1 > Date: Wed, 23 Jan 2013 10:27:35 +0400 > From: Wadim Incognito > To: Support list for open source software in schools. > > Subject: Re: [K12OSN] Update for kernel-thinclient > Message-ID: <1358922455.638047500 at f27.mail.ru> > Content-Type: text/plain; charset="utf-8" > > Yes, you can (for EL chroot): > Go to LTSP chroot: > > su > cd /opt/ltsp/i386 > setarch i386 chroot . > mount -t proc proc /proc > > Update SL in Chroot: > yum update > yum clean all > yum --releasever=6.3 update sl-release > yum update > yum clean all > > Install Generic SL kernel: > yum install kernel > > That's all, now you have SL 6.3 latst kernel, and updated chroot.? Not quite :-) umount /proc /## don't know if still the case but this used to mucks up client /etc/fstab if you didn't exit ltsp-update-kernels ##so client has boot image for new kernel ltsp-update-image ## if you are booting off nbd image, > ? > > > ???????, 17 ?????? 2013, 14:15 +01:00 ?? Johan Vermeulen > : > >+1. this would maybe solve some of my problems too > > > >Op 17-01-13 05:34, Norman Gaywood schreef: > >>Hi all, > >> > >>Is there a way to update the kernel-thinclient kernel to be > the latest SL kernel? > >> > >>I currently have some display hardware not supported by? > kernel-thinclient-2.6.32-131.6.1.el6.i686.rpm > >> > >>-- > >>Norman Gaywood, Computer Systems Officer > >>University of New England, Armidale, > >>NSW 2351, Australia > >> > >>ngaywood at une.edu.au ? ? ? ? ? ?Phone: +61 (0)2 6773 2412 > >>http://mcs.une.edu.au/~norm ? ?Fax: ? +61 (0)2 6773 3312 > >> > >>Please avoid sending me Word or Power Point attachments. > >>See http://www.gnu.org/philosophy/no-word-attachments.html > >> > >> From adrin at applied-scientific.com Fri Jan 25 01:40:46 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Thu, 24 Jan 2013 17:40:46 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 Message-ID: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> Hello; I'm new to LTSP and generally a novice to Linux. I installed all LTSP-related packages using Fedora 17's Add/Remove Software (GUI). I then followed the instructions on the k12linux site. 1) Everything on the server side installed "properly", except for step 8: there is no ltsp-server-tweaks on my system. I don't know if this is relevant to my problem or not. Anyway, I'd appreciate a hint as to where I can download and install ltsp-server-tweaks 2) The client setup step failed because I'm running F17. If there are instructions I can follow to successfully complete the latter, I'd really appreciate the link. (I'm using the workstation only as a server, and I have a fairly powerful diskless thin/zero client, which I just purchased for remote computing purposes) 3) My system is 64-bit (and so is F17). Is there any reason ltsp defaults to 32-bit even though there are x86-64 ltsp directories/files as well? Is there a way to just stick with x86-64? 4) The main reason for this thread, which I assume/hope is independent of the above three "issues", is the fact that trying to PXE boot via the Virtual Machine fails (so does PXE booting from the diskless client, of course) with the message "No DEFAULT or UI configuration directives found!". The following are the last few lines before the error message, and googling the latter didn't turn up anything useful for me: (text in brackets are my comments) [IP address is assigned] BOOTIF= [hexadecimal numbers] SYSUUID= [hexadecimal numbers] TFTP prefix: /ltsp/i386/ Trying to load: pxelinux.cfg/default ok No DEFAULT or UI configuration directives found! boot: [blank space] The following is the content of the "default" file prompt 0 label linux kernel vmlinuz.ltsp append rw initrd=initrd.ltsp selinux=0 root=dhcp quiet rhgb The following are the relevant ifcfg files [root at vortex network-scripts]# more ifcfg-p1p1 UUID="36f1f167-eeef-45ad-9a03-9a1567b985a7" NM_CONTROLLED="no" BOOTPROTO=none DEVICE="p1p1" ONBOOT="yes" TYPE=Ethernet DEFROUTE="yes" IPV4_FAILURE_FATAL=no IPV6INIT=no NAME="System p1p1" HWADDR=10:BF:48:07:6F:6C BRIDGE=ltspbr0 USERCTL=yes [root at vortex network-scripts]# more ifcfg-ltspbr0 # Sample Configuration for Initscript Driven Bridge # Put this into /etc/sysconfig/network-scripts/ifcfg-ltspbr0 # # Warning: Deleting ifcfg-ltspbr0 alone to disable ltspbr0 will cause you # problems, because it will come back the next time you upgrade the # ltsp-server package. # # Comment out these two lines to disable ltspbr0. ONBOOT=yes IPADDR=172.31.100.254 DEVICE=ltspbr0 TYPE=Bridge BOOTPROTO=static STP=off DELAY=0.1 USERCTL=no IPV6INIT=no PEERDNS=yes NETMASK=255.255.255.0 ARP=yes Thank you very much, in advance, for helping me get started adrin -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianluca.cecchi at gmail.com Fri Jan 25 07:50:34 2013 From: gianluca.cecchi at gmail.com (Gianluca Cecchi) Date: Fri, 25 Jan 2013 08:50:34 +0100 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> Message-ID: Hi, For the last point you defined a label named "linux" but no default one, so I think you have to type linux At "boot:" prompt and enter And see if it boots or gives any error -------------- next part -------------- An HTML attachment was scrubbed... URL: From radek at bursztynowski.waw.pl Fri Jan 25 08:25:30 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Fri, 25 Jan 2013 09:25:30 +0100 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> Message-ID: <1359102330.28659.248.camel@alpaga.bursztynowski.waw.pl> Adrin, K12Linux installation instruction (https://fedorahosted.org/k12linux/wiki/InstallGuide) says: "Fedora 15+ WILL NOT WORK". I don't know is this Fedora status changed. I recomend you CentOS 6.3. Best regards, Radek --- > Hello; I'm new to LTSP and generally a novice to Linux. I installed > all LTSP-related packages using Fedora 17's Add/Remove Software (GUI). > I then followed the instructions on the k12linux site. > > > 1) Everything on the server side installed "properly", except for step > 8: there is no ltsp-server-tweaks on my system. I don't know if this > is relevant to my problem or not. Anyway, I'd appreciate a hint as to > where I can download and install ltsp-server-tweaks > > > 2) The client setup step failed because I'm running F17. If there are > instructions I can follow to successfully complete the latter, I'd > really appreciate the link. (I'm using the workstation only as a > server, and I have a fairly powerful diskless thin/zero client, which > I just purchased for remote computing purposes) > > > 3) My system is 64-bit (and so is F17). Is there any reason ltsp > defaults to 32-bit even though there are x86-64 ltsp directories/files > as well? Is there a way to just stick with x86-64? > > > 4) The main reason for this thread, which I assume/hope is independent > of the above three "issues", is the fact that trying to PXE boot via > the Virtual Machine fails (so does PXE booting from the diskless > client, of course) with the message "No DEFAULT or UI configuration > directives found!". The following are the last few lines before the > error message, and googling the latter didn't turn up anything useful > for me: > > > (text in brackets are my comments) > > > [IP address is assigned] > BOOTIF= [hexadecimal numbers] > SYSUUID= [hexadecimal numbers] > TFTP prefix: /ltsp/i386/ > Trying to load: pxelinux.cfg/default ok > No DEFAULT or UI configuration directives found! > boot: [blank space] > > > > > > The following is the content of the "default" file > > > prompt 0 > label linux > kernel vmlinuz.ltsp > append rw initrd=initrd.ltsp selinux=0 root=dhcp quiet rhgb > > > > > > The following are the relevant ifcfg files > > > [root at vortex network-scripts]# more ifcfg-p1p1 > UUID="36f1f167-eeef-45ad-9a03-9a1567b985a7" > NM_CONTROLLED="no" > BOOTPROTO=none > DEVICE="p1p1" > ONBOOT="yes" > TYPE=Ethernet > DEFROUTE="yes" > IPV4_FAILURE_FATAL=no > IPV6INIT=no > NAME="System p1p1" > HWADDR=10:BF:48:07:6F:6C > BRIDGE=ltspbr0 > USERCTL=yes > > > > [root at vortex network-scripts]# more ifcfg-ltspbr0 > # Sample Configuration for Initscript Driven Bridge > # Put this into /etc/sysconfig/network-scripts/ifcfg-ltspbr0 > # > # Warning: Deleting ifcfg-ltspbr0 alone to disable ltspbr0 will cause > you > # problems, because it will come back the next time you upgrade the > # ltsp-server package. > # > # Comment out these two lines to disable ltspbr0. > ONBOOT=yes > IPADDR=172.31.100.254 > > DEVICE=ltspbr0 > TYPE=Bridge > BOOTPROTO=static > STP=off > DELAY=0.1 > USERCTL=no > IPV6INIT=no > PEERDNS=yes > NETMASK=255.255.255.0 > ARP=yes > > > Thank you very much, in advance, for helping me get started > > > adrin > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From adrin at applied-scientific.com Fri Jan 25 21:59:31 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Fri, 25 Jan 2013 13:59:31 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> Message-ID: <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> Thank you Gianluca, The prompt indeed wanted a "linux" input at the boot prompt. However, it went to the next line and searched for "kernel vmlinuz.ltsp" and couldn't find such a file. I actually did a global search for vmlinuz.ltsp and didn't find it in my system either. So, something is definitely wrong in the fedora installation package. This package was installed directly from the fedora 17 repository, so I would have expected it should be self contained, unless the step that involves ltsp-server-tweaks (which I didn't perform because that file is also missing) is a prerequisite. If anyone can provide a copy of their ltsp-server-tweaks script for centos I'd appreciate it. Perhaps I can use that as a template for fedora adrin On Jan 24, 2013, at 11:50 PM, Gianluca Cecchi wrote: > Hi, > For the last point you defined a label named "linux" but no default one, so I think you have to type > linux > At "boot:" prompt and enter > And see if it boots or gives any error > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrin at applied-scientific.com Fri Jan 25 22:11:48 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Fri, 25 Jan 2013 14:11:48 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <1359102330.28659.248.camel@alpaga.bursztynowski.waw.pl> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <1359102330.28659.248.camel@alpaga.bursztynowski.waw.pl> Message-ID: <6C75E20F-28CF-4958-AEE5-3DECBF9B0AEA@Applied-Scientific.com> Radek, Thanks for the note. Yes, I saw that note as well, but I also remember reading somewhere that LTSP works on fedora 17 (or there is hope for it). Plus, LTSP is in the fedora 17 repository, so I would have expected it should work. Unfortunately, for a number of reasons I cannot use CentOS. If you provide the centos version of ltsp-server-tweaks and can send me the directory where vmlinuz.ltsp resides (is it a link to something else?) that might be a good start. I hope I can get this thing working soon! Thanks adrin On Jan 25, 2013, at 12:25 AM, Radek Bursztynowski wrote: > Adrin, > > K12Linux installation instruction > (https://fedorahosted.org/k12linux/wiki/InstallGuide) says: > "Fedora 15+ WILL NOT WORK". I don't know is this Fedora status changed. > > I recomend you CentOS 6.3. > > Best regards, > Radek > --- >> Hello; I'm new to LTSP and generally a novice to Linux. I installed >> all LTSP-related packages using Fedora 17's Add/Remove Software (GUI). >> I then followed the instructions on the k12linux site. >> >> >> 1) Everything on the server side installed "properly", except for step >> 8: there is no ltsp-server-tweaks on my system. I don't know if this >> is relevant to my problem or not. Anyway, I'd appreciate a hint as to >> where I can download and install ltsp-server-tweaks >> >> >> 2) The client setup step failed because I'm running F17. If there are >> instructions I can follow to successfully complete the latter, I'd >> really appreciate the link. (I'm using the workstation only as a >> server, and I have a fairly powerful diskless thin/zero client, which >> I just purchased for remote computing purposes) >> >> >> 3) My system is 64-bit (and so is F17). Is there any reason ltsp >> defaults to 32-bit even though there are x86-64 ltsp directories/files >> as well? Is there a way to just stick with x86-64? >> >> >> 4) The main reason for this thread, which I assume/hope is independent >> of the above three "issues", is the fact that trying to PXE boot via >> the Virtual Machine fails (so does PXE booting from the diskless >> client, of course) with the message "No DEFAULT or UI configuration >> directives found!". The following are the last few lines before the >> error message, and googling the latter didn't turn up anything useful >> for me: >> >> >> (text in brackets are my comments) >> >> >> [IP address is assigned] >> BOOTIF= [hexadecimal numbers] >> SYSUUID= [hexadecimal numbers] >> TFTP prefix: /ltsp/i386/ >> Trying to load: pxelinux.cfg/default ok >> No DEFAULT or UI configuration directives found! >> boot: [blank space] >> >> >> >> >> >> The following is the content of the "default" file >> >> >> prompt 0 >> label linux >> kernel vmlinuz.ltsp >> append rw initrd=initrd.ltsp selinux=0 root=dhcp quiet rhgb >> >> >> >> >> >> The following are the relevant ifcfg files >> >> >> [root at vortex network-scripts]# more ifcfg-p1p1 >> UUID="36f1f167-eeef-45ad-9a03-9a1567b985a7" >> NM_CONTROLLED="no" >> BOOTPROTO=none >> DEVICE="p1p1" >> ONBOOT="yes" >> TYPE=Ethernet >> DEFROUTE="yes" >> IPV4_FAILURE_FATAL=no >> IPV6INIT=no >> NAME="System p1p1" >> HWADDR=10:BF:48:07:6F:6C >> BRIDGE=ltspbr0 >> USERCTL=yes >> >> >> >> [root at vortex network-scripts]# more ifcfg-ltspbr0 >> # Sample Configuration for Initscript Driven Bridge >> # Put this into /etc/sysconfig/network-scripts/ifcfg-ltspbr0 >> # >> # Warning: Deleting ifcfg-ltspbr0 alone to disable ltspbr0 will cause >> you >> # problems, because it will come back the next time you upgrade the >> # ltsp-server package. >> # >> # Comment out these two lines to disable ltspbr0. >> ONBOOT=yes >> IPADDR=172.31.100.254 >> >> DEVICE=ltspbr0 >> TYPE=Bridge >> BOOTPROTO=static >> STP=off >> DELAY=0.1 >> USERCTL=no >> IPV6INIT=no >> PEERDNS=yes >> NETMASK=255.255.255.0 >> ARP=yes >> >> >> Thank you very much, in advance, for helping me get started >> >> >> adrin >> >> >> _______________________________________________ >> 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 gianluca.cecchi at gmail.com Sat Jan 26 10:52:22 2013 From: gianluca.cecchi at gmail.com (Gianluca Cecchi) Date: Sat, 26 Jan 2013 11:52:22 +0100 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> Message-ID: On Fri, Jan 25, 2013 at 10:59 PM, Adrin Gharakhani wrote: > Thank you Gianluca, > > The prompt indeed wanted a "linux" input at the boot prompt. However, it > went to the next line and searched for "kernel vmlinuz.ltsp" and couldn't > find such a file. I actually did a global search for vmlinuz.ltsp and didn't > find it in my system either. So, something is definitely wrong in the fedora > installation package. This package was installed directly from the fedora 17 > repository, so I would have expected it should be self contained, unless the > step that involves ltsp-server-tweaks (which I didn't perform because that > file is also missing) is a prerequisite. > > If anyone can provide a copy of their ltsp-server-tweaks script for centos > I'd appreciate it. Perhaps I can use that as a template for fedora I currently have not an ltsp environment with Fedora 17 but I do have fedora 17 (with ip 192.168.1.141 in example files below) configured to allow pxe booting + dhcpd/tftp services necessary to boot kernel over the lan. In fact I used it to install a Fedora 18 on a server with PXE boot and this configuration my config When I had to provide this kind of installation service I installed these packages: Jan 19 15:18:45 Installed: 2:xinetd-2.3.15-1.fc17.x86_64 Jan 19 15:18:45 Installed: tftp-server-5.2-2.fc17.x86_64 Jan 19 15:21:59 Installed: syslinux-4.05-1.fc17.x86_64 Jan 19 15:22:54 Installed: 12:dhcp-4.2.4-16.P2.fc17.x86_64 - xinetd installed and enabled [root at ope46 ~]# systemctl status xinetd.service xinetd.service - Xinetd A Powerful Replacement For Inetd Loaded: loaded (/usr/lib/systemd/system/xinetd.service; enabled) Active: active (running) since Sat, 26 Jan 2013 10:20:01 +0100; 1h 15min ago ... In case you have to: # systemctl enable xinetd.service # systemctl start xinetd.service - tftpd service enabled through xinetd see your /etc/xinetd.d/tftp I changed mine putting disable = no and restarting xinetd service - dhcpd installed and enabled [root at ope46 ~]# systemctl status dhcpd.service dhcpd.service - DHCPv4 Server Daemon Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; disabled) Active: inactive (dead) Docs: man:dhcpd(8) man:dhcpd.conf(5) CGroup: name=systemd:/system/dhcpd.service in my case it is disabled because I use it only when necessary not to conflict with dnsmasq used by libvirtd providing dhcp functionality to its virtual machines my dhcpd.conf lines: allow booting; allow bootp; ddns-update-style interim; ignore client-updates; subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; range dynamic-bootp 192.168.1.200 192.168.1.240; next-server 192.168.1.141; filename "pxelinux.0"; } here the next-server ip is the one of my server providing tftpd.. - tftp root directory on fedora 17 is /var/lib/tftpboot/ by default (it should match entry in /etc/xinetd.d/tftp in my case default one for f17: server_args = -s /var/lib/tftpboot ) In my case I only need a default entry for tftp clients that I change when necessary. see docs for mac based ones or more complex configs [root at ope46 ~]# ll /var/lib/tftpboot/ total 32032 -rw-r--r-- 1 root root 27900268 Jan 19 15:52 initrd.img -rwxrwxrwx 1 root root 26460 Jan 19 15:34 pxelinux.0 drwxr-xr-x 2 root root 4096 Jan 20 16:53 pxelinux.cfg -rwxr-xr-x 1 root root 4862486 Jan 19 15:52 vmlinuz [root at ope46 ~]# ll /var/lib/tftpboot/pxelinux.cfg/ total 8 -rw-r--r-- 1 root root 153 Jan 20 16:53 default vmlinuz and initrd are the Fedora 18 installation ones, downloaded over the wire by clients to run anaconda the "default" file contains [root at ope46 ~]# cat /var/lib/tftpboot/pxelinux.cfg/default default pxeboot timeout 50 label pxeboot kernel vmlinuz append initrd=initrd.img repo=http://192.168.1.141/f18 ks=http://192.168.1.141/anaconda-ks.cfg (I also provide httpd service through the next-server server that is my tftp server and I install f18 through kickstart) Please notice that [root at ope46 ~]# rpm -qf /var/lib/tftpboot/pxelinux.0 file /var/lib/tftpboot/pxelinux.0 is not owned by any package In fact I copied there from syslinux package: cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot So, keep from my env what can be of help for your LTSP config. HIH, Gianluca From radek at bursztynowski.waw.pl Sat Jan 26 13:37:21 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Sat, 26 Jan 2013 14:37:21 +0100 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <6C75E20F-28CF-4958-AEE5-3DECBF9B0AEA@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> Message-ID: <1359207441.3148.12.camel@alpaga.bursztynowski.waw.pl> Adrin, You can find in attachement CentOS ltsp-server-tweaks. This file resides /usr/sbin directory. vmlinuz.lts is a symlink to vmlinuz-2.6.32-131.6.1.el6.i686.thinclient, and both reside /var/lib/tftpboot/ltsp/i386 directory. If you will force Fedora 17 to work with LTSP - please send me these new with the truck to success. Best regards, Radek > Radek, > > Thanks for the note. Yes, I saw that note as well, but I also remember reading somewhere that LTSP works on fedora 17 (or there is hope for it). Plus, LTSP is in the fedora 17 repository, so I would have expected it should work. Unfortunately, for a number of reasons I cannot use CentOS. > > If you provide the centos version of ltsp-server-tweaks and can send me the directory where vmlinuz.ltsp resides (is it a link to something else?) that might be a good start. > > I hope I can get this thing working soon! > > Thanks > > adrin > > > On Jan 25, 2013, at 12:25 AM, Radek Bursztynowski wrote: > > > Adrin, > > > > K12Linux installation instruction > > (https://fedorahosted.org/k12linux/wiki/InstallGuide) says: > > "Fedora 15+ WILL NOT WORK". I don't know is this Fedora status changed. > > > > I recomend you CentOS 6.3. > > > > Best regards, > > Radek > > --- > >> Hello; I'm new to LTSP and generally a novice to Linux. I installed > >> all LTSP-related packages using Fedora 17's Add/Remove Software (GUI). > >> I then followed the instructions on the k12linux site. > >> > >> > >> 1) Everything on the server side installed "properly", except for step > >> 8: there is no ltsp-server-tweaks on my system. I don't know if this > >> is relevant to my problem or not. Anyway, I'd appreciate a hint as to > >> where I can download and install ltsp-server-tweaks > >> > >> > >> 2) The client setup step failed because I'm running F17. If there are > >> instructions I can follow to successfully complete the latter, I'd > >> really appreciate the link. (I'm using the workstation only as a > >> server, and I have a fairly powerful diskless thin/zero client, which > >> I just purchased for remote computing purposes) > >> > >> > >> 3) My system is 64-bit (and so is F17). Is there any reason ltsp > >> defaults to 32-bit even though there are x86-64 ltsp directories/files > >> as well? Is there a way to just stick with x86-64? > >> > >> > >> 4) The main reason for this thread, which I assume/hope is independent > >> of the above three "issues", is the fact that trying to PXE boot via > >> the Virtual Machine fails (so does PXE booting from the diskless > >> client, of course) with the message "No DEFAULT or UI configuration > >> directives found!". The following are the last few lines before the > >> error message, and googling the latter didn't turn up anything useful > >> for me: > >> > >> > >> (text in brackets are my comments) > >> > >> > >> [IP address is assigned] > >> BOOTIF= [hexadecimal numbers] > >> SYSUUID= [hexadecimal numbers] > >> TFTP prefix: /ltsp/i386/ > >> Trying to load: pxelinux.cfg/default ok > >> No DEFAULT or UI configuration directives found! > >> boot: [blank space] > >> > >> > >> > >> > >> > >> The following is the content of the "default" file > >> > >> > >> prompt 0 > >> label linux > >> kernel vmlinuz.ltsp > >> append rw initrd=initrd.ltsp selinux=0 root=dhcp quiet rhgb > >> > >> > >> > >> > >> > >> The following are the relevant ifcfg files > >> > >> > >> [root at vortex network-scripts]# more ifcfg-p1p1 > >> UUID="36f1f167-eeef-45ad-9a03-9a1567b985a7" > >> NM_CONTROLLED="no" > >> BOOTPROTO=none > >> DEVICE="p1p1" > >> ONBOOT="yes" > >> TYPE=Ethernet > >> DEFROUTE="yes" > >> IPV4_FAILURE_FATAL=no > >> IPV6INIT=no > >> NAME="System p1p1" > >> HWADDR=10:BF:48:07:6F:6C > >> BRIDGE=ltspbr0 > >> USERCTL=yes > >> > >> > >> > >> [root at vortex network-scripts]# more ifcfg-ltspbr0 > >> # Sample Configuration for Initscript Driven Bridge > >> # Put this into /etc/sysconfig/network-scripts/ifcfg-ltspbr0 > >> # > >> # Warning: Deleting ifcfg-ltspbr0 alone to disable ltspbr0 will cause > >> you > >> # problems, because it will come back the next time you upgrade the > >> # ltsp-server package. > >> # > >> # Comment out these two lines to disable ltspbr0. > >> ONBOOT=yes > >> IPADDR=172.31.100.254 > >> > >> DEVICE=ltspbr0 > >> TYPE=Bridge > >> BOOTPROTO=static > >> STP=off > >> DELAY=0.1 > >> USERCTL=no > >> IPV6INIT=no > >> PEERDNS=yes > >> NETMASK=255.255.255.0 > >> ARP=yes > >> > >> > >> Thank you very much, in advance, for helping me get started > >> > >> > >> adrin > >> > >> > >> _______________________________________________ > >> 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 > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: ltsp-server-tweaks Type: application/x-shellscript Size: 742 bytes Desc: not available URL: From adrin at applied-scientific.com Wed Jan 30 00:57:41 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Tue, 29 Jan 2013 16:57:41 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> Message-ID: <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> Thank you Gianluca, I followed your instructions (similar to the instructions on the fedora site), and I was initially unable to read the initrd.img file. After a long set of experiments I finally found out that the read permissions were not set properly for the default initrd.img. So, heads up to others who might encounter a similar problem: change the read permission to allow all to read. So, finally, I passed the "golden gate", but now I have a hardware incompatibility problem. I don't know if I should continue this thread or create a new one. I'll continue, for now: I'm getting a message that my zero client is unable to boot because "This kernel requires an x86-64 CPU, but only detected an i686 CPU" My workstation is x86-64 and apparently the new zero client that I bought is i686. Any suggestions how to go about correcting this problem? (does fedora 17 provide i686 compatibility?) I have to add that my sole interest is to move my workstation to another building (on the same LAN), but I want my zero client set up such that I'm "in front of the workstation", with _full_ access to all capabilities of the x86-64 kernel (there is only myself; this is not a multi-client environment) Thanks all for your help and suggestions adrin On Jan 26, 2013, at 2:52 AM, Gianluca Cecchi wrote: > On Fri, Jan 25, 2013 at 10:59 PM, Adrin Gharakhani wrote: >> Thank you Gianluca, >> >> The prompt indeed wanted a "linux" input at the boot prompt. However, it >> went to the next line and searched for "kernel vmlinuz.ltsp" and couldn't >> find such a file. I actually did a global search for vmlinuz.ltsp and didn't >> find it in my system either. So, something is definitely wrong in the fedora >> installation package. This package was installed directly from the fedora 17 >> repository, so I would have expected it should be self contained, unless the >> step that involves ltsp-server-tweaks (which I didn't perform because that >> file is also missing) is a prerequisite. >> >> If anyone can provide a copy of their ltsp-server-tweaks script for centos >> I'd appreciate it. Perhaps I can use that as a template for fedora > > I currently have not an ltsp environment with Fedora 17 but I do have > fedora 17 (with ip 192.168.1.141 in example files below) configured to > allow pxe booting + dhcpd/tftp services necessary to boot kernel over > the lan. > In fact I used it to install a Fedora 18 on a server with PXE boot and > this configuration > my config > > When I had to provide this kind of installation service I installed > these packages: > Jan 19 15:18:45 Installed: 2:xinetd-2.3.15-1.fc17.x86_64 > Jan 19 15:18:45 Installed: tftp-server-5.2-2.fc17.x86_64 > Jan 19 15:21:59 Installed: syslinux-4.05-1.fc17.x86_64 > Jan 19 15:22:54 Installed: 12:dhcp-4.2.4-16.P2.fc17.x86_64 > > > - xinetd installed and enabled > [root at ope46 ~]# systemctl status xinetd.service > xinetd.service - Xinetd A Powerful Replacement For Inetd > Loaded: loaded (/usr/lib/systemd/system/xinetd.service; enabled) > Active: active (running) since Sat, 26 Jan 2013 10:20:01 +0100; 1h 15min ago > ... > > In case you have to: > > # systemctl enable xinetd.service > # systemctl start xinetd.service > > - tftpd service enabled through xinetd > see your /etc/xinetd.d/tftp > I changed mine putting > disable = no > > and restarting xinetd service > > - dhcpd installed and enabled > [root at ope46 ~]# systemctl status dhcpd.service > dhcpd.service - DHCPv4 Server Daemon > Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; disabled) > Active: inactive (dead) > Docs: man:dhcpd(8) > man:dhcpd.conf(5) > CGroup: name=systemd:/system/dhcpd.service > > in my case it is disabled because I use it only when necessary not to > conflict with dnsmasq used by libvirtd providing dhcp functionality to > its virtual machines > > my dhcpd.conf lines: > > allow booting; > allow bootp; > ddns-update-style interim; > ignore client-updates; > subnet 192.168.1.0 netmask 255.255.255.0 { > option subnet-mask 255.255.255.0; > option broadcast-address 192.168.1.255; > range dynamic-bootp 192.168.1.200 192.168.1.240; > next-server 192.168.1.141; > filename "pxelinux.0"; } > > here the next-server ip is the one of my server providing tftpd.. > > - tftp root directory on fedora 17 is /var/lib/tftpboot/ by default > (it should match entry in /etc/xinetd.d/tftp > in my case default one for f17: > server_args = -s /var/lib/tftpboot > ) > > In my case I only need a default entry for tftp clients that I change > when necessary. > see docs for mac based ones or more complex configs > > > [root at ope46 ~]# ll /var/lib/tftpboot/ > total 32032 > -rw-r--r-- 1 root root 27900268 Jan 19 15:52 initrd.img > -rwxrwxrwx 1 root root 26460 Jan 19 15:34 pxelinux.0 > drwxr-xr-x 2 root root 4096 Jan 20 16:53 pxelinux.cfg > -rwxr-xr-x 1 root root 4862486 Jan 19 15:52 vmlinuz > > [root at ope46 ~]# ll /var/lib/tftpboot/pxelinux.cfg/ > total 8 > -rw-r--r-- 1 root root 153 Jan 20 16:53 default > > vmlinuz and initrd are the Fedora 18 installation ones, downloaded > over the wire by clients to run anaconda > the "default" file contains > > [root at ope46 ~]# cat /var/lib/tftpboot/pxelinux.cfg/default > default pxeboot > timeout 50 > label pxeboot > kernel vmlinuz > append initrd=initrd.img repo=http://192.168.1.141/f18 > ks=http://192.168.1.141/anaconda-ks.cfg > > (I also provide httpd service through the next-server server that is > my tftp server and I install f18 through kickstart) > > Please notice that > [root at ope46 ~]# rpm -qf /var/lib/tftpboot/pxelinux.0 > file /var/lib/tftpboot/pxelinux.0 is not owned by any package > > In fact I copied there from syslinux package: > cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot > > So, keep from my env what can be of help for your LTSP config. > > HIH, > Gianluca > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From burke at thealmquists.net Wed Jan 30 01:27:00 2013 From: burke at thealmquists.net (Burke Almquist) Date: Tue, 29 Jan 2013 19:27:00 -0600 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 29, 2013, at 6:57 PM, Adrin Gharakhani wrote: > Thank you Gianluca, > > I followed your instructions (similar to the instructions on the fedora site), and I was initially unable to read the initrd.img file. After a long set of experiments I finally found out that the read permissions were not set properly for the default initrd.img. So, heads up to others who might encounter a similar problem: change the read permission to allow all to read. > > So, finally, I passed the "golden gate", but now I have a hardware incompatibility problem. I don't know if I should continue this thread or create a new one. I'll continue, for now: > > I'm getting a message that my zero client is unable to boot because "This kernel requires an x86-64 CPU, but only detected an i686 CPU" > > My workstation is x86-64 and apparently the new zero client that I bought is i686. Any suggestions how to go about correcting this problem? (does fedora 17 provide i686 compatibility?) > > I have to add that my sole interest is to move my workstation to another building (on the same LAN), but I want my zero client set up such that I'm "in front of the workstation", with _full_ access to all capabilities of the x86-64 kernel (there is only myself; this is not a multi-client environment) > > Thanks all for your help and suggestions You built a 64 bit environment for the clients too, which is almost never what you want to do. Make sure you set the chroot to 32 bit when you start building your clients. https://fedorahosted.org/k12linux/wiki/Tips -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlEIduQACgkQxWV7OPa/g5F5QQCfbg1ag2/xpIwmke8zVUggEO3g SaUAoISyrbRp274vwb+y1nUK6BYmAuGo =Wqhf -----END PGP SIGNATURE----- From adrin at applied-scientific.com Wed Jan 30 02:29:30 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Tue, 29 Jan 2013 18:29:30 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> Message-ID: <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> Burke, Right now I'm outside the LTSP realm; my attempt with the latter failed, so I tried what Gianluca suggested and just tried the basic steps of setting up a pxe boot (I don't think I've done any client building, per se). I would have really preferred to use something like LTSP but unfortunately it doesn't support fedora 17 (the client side stops at fedora 14, which is an unacceptable option for me). So, right now I have a 32-bit thin/zero client and a x86-64 F17 OS installation on my workstation. The 32-bit version of F17 is unfortunately not acceptable for what I do (and use), so I can't change the ecosystem of my workstation. The only real solution for me is something that would allow me to connect my 32-bit zero client to my 64-bit OS, but I don't know if/how it's possible (perhaps some sort of a compatibility software or something). Any hope of getting LTSP for F17? Thanks adrin On Jan 29, 2013, at 5:27 PM, Burke Almquist wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Jan 29, 2013, at 6:57 PM, Adrin Gharakhani wrote: > >> Thank you Gianluca, >> >> I followed your instructions (similar to the instructions on the fedora site), and I was initially unable to read the initrd.img file. After a long set of experiments I finally found out that the read permissions were not set properly for the default initrd.img. So, heads up to others who might encounter a similar problem: change the read permission to allow all to read. >> >> So, finally, I passed the "golden gate", but now I have a hardware incompatibility problem. I don't know if I should continue this thread or create a new one. I'll continue, for now: >> >> I'm getting a message that my zero client is unable to boot because "This kernel requires an x86-64 CPU, but only detected an i686 CPU" >> >> My workstation is x86-64 and apparently the new zero client that I bought is i686. Any suggestions how to go about correcting this problem? (does fedora 17 provide i686 compatibility?) >> >> I have to add that my sole interest is to move my workstation to another building (on the same LAN), but I want my zero client set up such that I'm "in front of the workstation", with _full_ access to all capabilities of the x86-64 kernel (there is only myself; this is not a multi-client environment) >> >> Thanks all for your help and suggestions > > You built a 64 bit environment for the clients too, which is almost never what you want to do. Make sure you set the chroot to 32 bit when you start building your clients. > https://fedorahosted.org/k12linux/wiki/Tips > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iEYEARECAAYFAlEIduQACgkQxWV7OPa/g5F5QQCfbg1ag2/xpIwmke8zVUggEO3g > SaUAoISyrbRp274vwb+y1nUK6BYmAuGo > =Wqhf > -----END PGP SIGNATURE----- > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From burke at thealmquists.net Wed Jan 30 04:52:22 2013 From: burke at thealmquists.net (Burke Almquist) Date: Tue, 29 Jan 2013 22:52:22 -0600 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> Message-ID: <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 29, 2013, at 8:29 PM, Adrin Gharakhani wrote: > Burke, > > Right now I'm outside the LTSP realm; my attempt with the latter failed, so I tried what Gianluca suggested and just tried the basic steps of setting up a pxe boot (I don't think I've done any client building, per se). I would have really preferred to use something like LTSP but unfortunately it doesn't support fedora 17 (the client side stops at fedora 14, which is an unacceptable option for me). > > So, right now I have a 32-bit thin/zero client and a x86-64 F17 OS installation on my workstation. The 32-bit version of F17 is unfortunately not acceptable for what I do (and use), so I can't change the ecosystem of my workstation. The only real solution for me is something that would allow me to connect my 32-bit zero client to my 64-bit OS, but I don't know if/how it's possible (perhaps some sort of a compatibility software or something). > > Any hope of getting LTSP for F17? > > Thanks > > adrin > I don't know about LTSP support on F17, most of the work on LTSP and Fedora/EL6 has been done by Warren Togami. I think I might just try to install it on F17 or F18 and see if I can as least spot what has been broken. I've just been messing around with LTSP on EL6 since that seems to mostly be stable and working, and I don't have any pressing reason to be using F17 or 18. I'm curious what you need in Fedora 17 that isn't in EL6. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlEIpwYACgkQxWV7OPa/g5GhuQCghZX2zm6rRm4FkR4zU0yyKzQy d3YAmwWh6X4dbs+uTl5nWWNGNKacbrxz =o+NM -----END PGP SIGNATURE----- From adrin at applied-scientific.com Wed Jan 30 05:55:12 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Tue, 29 Jan 2013 21:55:12 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> Message-ID: If by EL you mean RHEL, then it's just too expensive for me (a one-person operation). If you mean SL (scientific linux), then last I checked it runs a much older version of gcc than I can accept. Fedora always keeps up with the latest and greatest. This is really ironic - a "scientific" OS falls way behind wrt compiler updates. Also, the upgrades are not frequent enough (based on what little I know about it), so even if a newer version becomes available today, I'd have to wait much longer for the next update. Finally, I am by NO means even at the entry level when it comes to OS stuff - I really just want to focus on my work using something I feel very comfortable with by now (because of the regular updates and improvements) BTW, I installed the i386 version of vmlinuz and initrd.img, and the zero client passed that test; moved on to the next stage - it apparently wants more "stuff" from the installation package to get started (but I haven't figured out how I can dump the terminal output to know what exactly is going on at each stage). So, I'm still stuck and the saga continues :) thanks On Jan 29, 2013, at 8:52 PM, Burke Almquist wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Jan 29, 2013, at 8:29 PM, Adrin Gharakhani wrote: > >> Burke, >> >> Right now I'm outside the LTSP realm; my attempt with the latter failed, so I tried what Gianluca suggested and just tried the basic steps of setting up a pxe boot (I don't think I've done any client building, per se). I would have really preferred to use something like LTSP but unfortunately it doesn't support fedora 17 (the client side stops at fedora 14, which is an unacceptable option for me). >> >> So, right now I have a 32-bit thin/zero client and a x86-64 F17 OS installation on my workstation. The 32-bit version of F17 is unfortunately not acceptable for what I do (and use), so I can't change the ecosystem of my workstation. The only real solution for me is something that would allow me to connect my 32-bit zero client to my 64-bit OS, but I don't know if/how it's possible (perhaps some sort of a compatibility software or something). >> >> Any hope of getting LTSP for F17? >> >> Thanks >> >> adrin >> > > I don't know about LTSP support on F17, most of the work on LTSP and Fedora/EL6 has been done by Warren Togami. > I think I might just try to install it on F17 or F18 and see if I can as least spot what has been broken. I've just been messing around with LTSP on EL6 since that seems to mostly be stable and working, and I don't have any pressing reason to be using F17 or 18. > > I'm curious what you need in Fedora 17 that isn't in EL6. > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iEYEARECAAYFAlEIpwYACgkQxWV7OPa/g5GhuQCghZX2zm6rRm4FkR4zU0yyKzQy > d3YAmwWh6X4dbs+uTl5nWWNGNKacbrxz > =o+NM > -----END PGP SIGNATURE----- > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From burke at thealmquists.net Wed Jan 30 06:03:20 2013 From: burke at thealmquists.net (Burke Almquist) Date: Wed, 30 Jan 2013 00:03:20 -0600 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> Message-ID: On Jan 29, 2013, at 11:55 PM, Adrin Gharakhani wrote: > If by EL (RHEL, CentOS or SL) > you mean RHEL, then it's just too expensive for me (a one-person operation). If you mean SL (scientific linux), then last I checked it runs a much older version of gcc than I can accept. Fedora always keeps up with the latest and greatest. This is really ironic - a "scientific" OS falls way behind wrt compiler updates. Also, the upgrades are not frequent enough (based on what little I know about it), so even if a newer version becomes available today, I'd have to wait much longer for the next update. Finally, I am by NO means even at the entry level when it comes to OS stuff - I really just want to focus on my work using something I feel very comfortable with by now (because of the regular updates and improvements) Ahh, so you have something that needs a newer version of GCC. Makes sense. does CentOS 6.3 have it by chance? > BTW, I installed the i386 version of vmlinuz and initrd.img, and the zero client passed that test; moved on to the next stage - it apparently wants more "stuff" from the installation package to get started (but I haven't figured out how I can dump the terminal output to know what exactly is going on at each stage). So, I'm still stuck and the saga continues :) > Sorry I haven't been more help. From adrin at applied-scientific.com Wed Jan 30 06:15:25 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Tue, 29 Jan 2013 22:15:25 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> Message-ID: <1D575345-CF49-408F-A9BF-6EAB0E388BFB@Applied-Scientific.com> On Jan 29, 2013, at 10:03 PM, Burke Almquist wrote: > > On Jan 29, 2013, at 11:55 PM, Adrin Gharakhani wrote: > >> If by EL (RHEL, CentOS or SL) > > >> you mean RHEL, then it's just too expensive for me (a one-person operation). If you mean SL (scientific linux), then last I checked it runs a much older version of gcc than I can accept. Fedora always keeps up with the latest and greatest. This is really ironic - a "scientific" OS falls way behind wrt compiler updates. Also, the upgrades are not frequent enough (based on what little I know about it), so even if a newer version becomes available today, I'd have to wait much longer for the next update. Finally, I am by NO means even at the entry level when it comes to OS stuff - I really just want to focus on my work using something I feel very comfortable with by now (because of the regular updates and improvements) > Ahh, so you have something that needs a newer version of GCC. Makes sense. does CentOS 6.3 have it by chance? Nope, centos is generally worse!!! (older versions of gcc have bugs for what I need, and the newer ones have the much more advanced capabilities that I can utilize) I'm now tempted to take one of two routes: (1) say goodbye to LTSP and try DRBL, which apparently has at least an unstable version for F17 (2) just put a full i386 on a USB stick, pxe boot the zero client off this stick, and use NX server/client to connect it to my workstation. I was told earlier (or read somewhere) that LTSP would be faster than NX on a LAN, but in my case "fast" is meaningless :) If you do get a chance to play with F17 and find out what the problem and the fixes are, I'd truly appreciate it > > >> BTW, I installed the i386 version of vmlinuz and initrd.img, and the zero client passed that test; moved on to the next stage - it apparently wants more "stuff" from the installation package to get started (but I haven't figured out how I can dump the terminal output to know what exactly is going on at each stage). So, I'm still stuck and the saga continues :) >> > > Sorry I haven't been more help. > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From burke at thealmquists.net Wed Jan 30 06:23:45 2013 From: burke at thealmquists.net (Burke Almquist) Date: Wed, 30 Jan 2013 00:23:45 -0600 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <1D575345-CF49-408F-A9BF-6EAB0E388BFB@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> <1D575345-CF49-408F-A9BF-6EAB0E388BFB@Applied-Scientific.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Something worth considering, you could always just to plain old remote X sessions from a fully installed client that boots from a USB stick. Any Linux that can boot the client. LTSP just gives you stuff like sound, local devices, etc. Remote display, KB and mouse is already part of linux. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlEIvHEACgkQxWV7OPa/g5G/kgCfR0CheY8ynlFHqczppbsIhxuq E9sAni+wJcVCY3vM/Zh2DY/CVm7t0Jvt =w6PG -----END PGP SIGNATURE----- From adrin at applied-scientific.com Wed Jan 30 06:34:16 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Tue, 29 Jan 2013 22:34:16 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> <1D575345-CF49-408F-A9BF-6EAB0E388BFB@Applied-Scientific.com> Message-ID: <75CF68A2-68B8-4678-B541-B63E605D9125@Applied-Scientific.com> Remote X won't work - it is extremely slow for graphics intensive applications (like flow visualization, etc). But I've tried NX recently, and it is surprisingly really fast. I would, however, prefer to use the CPU/GPU resources of the zero client as much as possible to free up the workstation to perform computations, etc. This was one main reason I was looking into LTSP :( On Jan 29, 2013, at 10:23 PM, Burke Almquist wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Something worth considering, you could always just to plain old remote X sessions from a fully installed client that boots from a USB stick. > Any Linux that can boot the client. LTSP just gives you stuff like sound, local devices, etc. Remote display, KB and mouse is already part of linux. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iEYEARECAAYFAlEIvHEACgkQxWV7OPa/g5G/kgCfR0CheY8ynlFHqczppbsIhxuq > E9sAni+wJcVCY3vM/Zh2DY/CVm7t0Jvt > =w6PG > -----END PGP SIGNATURE----- > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From burke at thealmquists.net Wed Jan 30 06:42:51 2013 From: burke at thealmquists.net (Burke Almquist) Date: Wed, 30 Jan 2013 00:42:51 -0600 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <75CF68A2-68B8-4678-B541-B63E605D9125@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> <1D575345-CF49-408F-A9BF-6EAB0E388BFB@Applied-Scientific.com> <75CF68A2-68B8-4678-B541-B63E605D9125@Applied-Scientific.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So are you have a big workstation with lots of horsepower you want to run this stuff on, you just would like to access it from a remote computer? Then NX might be the best option here. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlEIwOwACgkQxWV7OPa/g5Gy1ACfWUjWhI4VmqfL4hAMe4jfLhdY cXgAn3vq5OXKjRVBfALYQGUNNJ9VD5hg =lULx -----END PGP SIGNATURE----- From adrin at applied-scientific.com Wed Jan 30 06:46:17 2013 From: adrin at applied-scientific.com (Adrin Gharakhani) Date: Tue, 29 Jan 2013 22:46:17 -0800 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> <1D575345-CF49-408F-A9BF-6EAB0E388BFB@Applied-Scientific.com> <75CF68A2-68B8-4678-B541-B63E605D9125@Applied-Scientific.com> Message-ID: <85535EA6-2176-4F82-A0CD-8E321CA7A48C@Applied-Scientific.com> On Jan 29, 2013, at 10:42 PM, Burke Almquist wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > So are you have a big workstation with lots of horsepower you want to run this stuff on, you just would like to access it from a remote computer? Yes, precisely > Then NX might be the best option here. Except that I remember from somewhere that LTSP is supposed to be faster than NX on a LAN > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iEYEARECAAYFAlEIwOwACgkQxWV7OPa/g5Gy1ACfWUjWhI4VmqfL4hAMe4jfLhdY > cXgAn3vq5OXKjRVBfALYQGUNNJ9VD5hg > =lULx > -----END PGP SIGNATURE----- > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From burke at thealmquists.net Thu Jan 31 06:52:35 2013 From: burke at thealmquists.net (Burke Almquist) Date: Thu, 31 Jan 2013 00:52:35 -0600 Subject: [K12OSN] Trouble with PXE Boot; Fedora 17 In-Reply-To: <85535EA6-2176-4F82-A0CD-8E321CA7A48C@Applied-Scientific.com> References: <0BA753D5-BBD8-4FF5-86BD-295841145F3E@Applied-Scientific.com> <58192AB1-7AF0-4FC8-9645-AACC5C496147@Applied-Scientific.com> <02B219C5-FAF2-4A89-90DD-B56BAB8FE9C4@Applied-Scientific.com> <3D360CD1-77ED-47FC-A4B0-625BBC85CCCC@Applied-Scientific.com> <83CED2BC-A072-4073-B742-99C1D66DC963@thealmquists.net> <1D575345-CF49-408F-A9BF-6EAB0E388BFB@Applied-Scientific.com> <75CF68A2-68B8-4678-B541-B63E605D9125@Applied-Scientific.com> <85535EA6-2176-4F82-A0CD-8E321CA7A48C@Applied-Scientific.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 30, 2013, at 12:46 AM, Adrin Gharakhani wrote: > > > On Jan 29, 2013, at 10:42 PM, Burke Almquist wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> So are you have a big workstation with lots of horsepower you want to run this stuff on, you just would like to access it from a remote computer? > > Yes, precisely > >> Then NX might be the best option here. > > Except that I remember from somewhere that LTSP is supposed to be faster than NX on a LAN This is probably true. X is actually very responsive over a good LAN connection. 100mbit on the clients and 1gbit on the server should provide plenty of bandwidth. The advantage of NX is on connections that have greater latency and less bandwith (over the internet for example) as opposed to a 100mbit or gigabit speed LAN. LTSP 4.0 used XDMCP to establish a remote X Session. No security (I mean it's on a switched network, but ARP spoofing would make traffic sniffing possible) and no compression. LTSP 5.0 has moved to tunneling over SSH. This adds some security, and the use of built in SSH compression, but requires just slightly more horsepower from the client. You CAN specify the use of the SSH tunnel only during the login process in the lts.conf file (this is the default on some distros). This lowers the burden on the client hardware while still protecting the user's password over the wires. All the X traffic itself is unencrypted if you choose this though, so it's not the best for security. Best on a small and closed network. NX also uses SSH for security but has it's own compression that is much more effective than the built in SSH compression. The work of doing the compression is only worth while if the connection is slow enough or has high enough latency. Otherwise you are just burning CPU cycles for no performance gain, and actually the overhead of the higher compression would introduce more latency that it fixes over a faster connection. > >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG/MacGPG2 v2.0.17 (Darwin) >> Comment: GPGTools - http://gpgtools.org >> >> iEYEARECAAYFAlEIwOwACgkQxWV7OPa/g5Gy1ACfWUjWhI4VmqfL4hAMe4jfLhdY >> cXgAn3vq5OXKjRVBfALYQGUNNJ9VD5hg >> =lULx >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlEKFLMACgkQxWV7OPa/g5Hp/ACeNfTjPQbDS6oAC+aG6va6xAaY SdgAnA3O0Jd+soA68grB/VHzxSIy/BGb =RFEB -----END PGP SIGNATURE-----