From wtogami at redhat.com Sun May 4 07:04:44 2008 From: wtogami at redhat.com (Warren Togami) Date: Sun, 04 May 2008 03:04:44 -0400 Subject: small bug: ltsp-update-sshkeys barfs under sudo In-Reply-To: References: Message-ID: <481D600C.1060900@redhat.com> Michael_E_Brown at Dell.com wrote: > I ran 'sudo ltsp-build-client', and got the following near the end: > > /usr/sbin/ltsp-update-sshkeys: line 40: ip: command not found > > Looks like a simple fix: /sbin/ip instead of just ip. > Thanks for the report. This is fixed in ltsp-5.1.7-2.fc9 already in F-9. Warren From franta at hanzlici.cz Sun May 11 19:37:33 2008 From: franta at hanzlici.cz (Frantisek Hanzlik) Date: Sun, 11 May 2008 21:37:33 +0200 Subject: Print to printer connected to ltsp thin client Message-ID: <48274AFD.9030908@hanzlici.cz> As I can see on Ubuntu and Debian forums, jetpipe is very simple python script, and at this time isn't capable initialize serial line printers. I a week ago upgrade some system I manage to F9/LTSP 5 and must solve printing to printers (paralell, serial and USB too) connected to thin clients. Thus I was build print server which was used in ltsp 4 - "lp_server" from P.Powell. After several days utilization, I must say this work without problems. (On older versions K12LTSP I was using this program for more than four years, and it works well, with small system footprint). For easy integration lp_server to F9 I made: - lp_server RPM package for F9/i386 lp_server-1.1.6-1.fc9.i386.rpm available at http://hanzlici.cz/packages/fedora/lp_server/lp_server-1.1.6-1.fc9.i386.rpm (23kB) - lp_server source RPM lp_server-1.1.6-1.fc9.src.rpm available at http://hanzlici.cz/packages/fedora/lp_server/lp_server-1.1.6-1.fc9.src.rpm (73 KB) - patch for ltsp-init-common script from ltsp-5.1.7, which replaces jetpipe with lp-server: ltsp-init-common.patch.tgz available at http://hanzlici.cz/packages/fedora/lp_server/ltsp-init-common.patch.tgz Patch is against ltsp-5.1.7 package (1.2 kB) RPM must be installed in thin client system, either by hand chrooting to /opt/ltsp/i386 or adding to repo and adding it to RPM list in ltsp-build-client. In lts.conf is then possible use all PRINTER_n_{DATABITS,DEBUG,DEVICE,FLOWCTRL,PARITY,SPEED,TYPE,WRITE_ONLY} variables as in LTSP 4. (patch adjust mismatch in nbd-client and nbdswapd communication port as well) I hope this may be useful for k12ltsp project. Frantisek Hanzlik From alexandre.alencar at gmail.com Thu May 15 21:50:35 2008 From: alexandre.alencar at gmail.com (Alexandre Cavalcante Alencar) Date: Thu, 15 May 2008 18:50:35 -0300 Subject: LTSP 5 and Fedora 8 (DHCP on a different server) Message-ID: Hi all, I am trying to test LTSP 5 on Fedora 8 (server) and I get all setup, my thin client boot up and show LDM screen, but when I inform my login and password, my screen turns black and come back to LDM again. If I change the session to Failsafe terminal, and login, it show me the xterm terminal. The install was made as described here http://wtogami.livejournal.com/ I get two lines on messages that say ldminfd started and exited (with status 0) and all logs of secure saying that the user logged on and logged off when I try to open the Default (should be GNOME) session. Does anyone can give some light on this? My DHCP server runs on another box (Fedora 8 x64 with all updates) and here is the relevant config authoritative; allow booting; allow bootp; deny unknown-clients; ddns-updates on; ddns-update-style interim; default-lease-time 21600; max-lease-time 21600; one-lease-per-client true; option domain-name "aspec.aspec.com.br"; option time-offset -10800; use-host-decl-names on; option option-128 code 128 = string; option option-129 code 129 = text; option boot-server code 66 = string; class "PXE" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; vendor-option-space PXE; filename "/pxelinux.0"; } class "Etherboot" { match if substring (option vendor-class-identifier, 0, 9) = "Etherboot"; option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff; option option-128 e4:45:74:68:00:00; option option-129 "MOPTS=nolock,ro,wsize=2048,rsize=2048"; filename "/lts/vmlinuz-2.6.20.9-ltsp-1"; } shared-network Aspec { subnet 192.168.0.0 netmask 255.255.255.0 { option ip-forwarding off; option subnet-mask 255.255.255.0; option broadcast-address 192.168.0.255; option smtp-server 192.168.0.30; option ntp-servers 192.168.0.1; option time-servers 192.168.0.1; option netbios-name-servers 192.168.0.1; option domain-name-servers 192.168.0.1; option routers 192.168.0.5; group SUPORTE { option tftp-server-name "aspec-res-063.aspec.aspec.com.br"; option log-servers aspec-res-063.aspec.aspec.com.br; option root-path "192.168.0.83:/opt/ltsp/i386"; option font-servers 192.168.0.83; option x-display-manager 192.168.0.83; next-server 192.168.0.83; server-name "aspec-res-063.aspec.aspec.com.br"; filename "/ltsp/i386/pxelinux.0"; host aspec-res-006 { hardware ethernet 00:E0:C5:5F:B7:C9; fixed-address 192.168.0.26; } } } } -- Alexandre C Alencar (Skarmeth) http://blog.alexandrealencar.net/ http://www.alexandrealencar.net/ http://people.debian-ce.org/skarmeth/ From jodgipost at gmail.com Fri May 16 11:54:12 2008 From: jodgipost at gmail.com (Dagfinn Stangeland) Date: Fri, 16 May 2008 13:54:12 +0200 Subject: Fedora 9 LTSP install guide, walkthrough, manual... Message-ID: <645415b20805160454v4ffbc949w31de63b79eb8ebc6@mail.gmail.com> I'm struggling with setting up a Fedora LTSP server. Does anyone know of a final F9 resource for installation and setup of LTSP? What i find floating around seems to written a while ago and seems to be meant for beta and testing versions of Fedora and LTSP. -- Dagfinn Stangeland Theodor Dahlsvei 13 4319 Sandnes Norway +47 90795008 jodgipost at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtogami at redhat.com Fri May 16 13:38:46 2008 From: wtogami at redhat.com (Warren Togami) Date: Fri, 16 May 2008 09:38:46 -0400 Subject: Fedora 9 LTSP install guide, walkthrough, manual... In-Reply-To: <645415b20805160454v4ffbc949w31de63b79eb8ebc6@mail.gmail.com> References: <645415b20805160454v4ffbc949w31de63b79eb8ebc6@mail.gmail.com> Message-ID: <482D8E66.40404@redhat.com> Dagfinn Stangeland wrote: > I'm struggling with setting up a Fedora LTSP server. > Does anyone know of a final F9 resource for installation and setup of LTSP? > What i find floating around seems to written a while ago and seems to be > meant for beta and testing versions of Fedora and LTSP. > > https://fedorahosted.org/k12linux/wiki/InstallGuide The instructions here should work. We perhaps need to add or correct things. Let us know if you are confused about something. Warren From wtogami at redhat.com Fri May 16 19:57:43 2008 From: wtogami at redhat.com (Warren Togami) Date: Fri, 16 May 2008 15:57:43 -0400 Subject: LTSP 5 and Fedora 8 (DHCP on a different server) In-Reply-To: References: Message-ID: <482DE737.6070105@redhat.com> Alexandre Cavalcante Alencar wrote: > Hi all, > > I am trying to test LTSP 5 on Fedora 8 (server) and I get all setup, > my thin client boot up and show LDM screen, but when I inform my login > and password, my screen turns black and come back to LDM again. If I > change the session to Failsafe terminal, and login, it show me the > xterm terminal. I'm looking into possible causes of this failure. 1) /opt/ltsp/i386/etc/ssh/ssh_known_hosts Does this contain the IP address of your LTSP5 server? 2) /opt/ltsp/i386/usr/sbin/ltsp-client-launch # Find tftp server # XXX: option routers is not guaranteed to be the tftp server. Need to figure # out a better way to detect the tftp server address. ROOTSERVER="$(cat /dev/.dhclient-eth0.leases |grep "routers" |awk {'print $3'} |sed 's/;//')" This runs late during the client bootup right before X in order to figure out where to grab the lts.conf via tftp. It seems that getting ROOTSERVER from option routers is definitely wrong here because there is no good reason that routers need be the same IP address as the LTSP server. It also falls apart entirely if you have multiple LTSP servers. http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/721 I checked in a fix that improves this aspect. It might not fix your bug, but it could use some testing anyway especially since you have multiple LTSP servers. http://togami.com/~k12linux-temporary/fedora/8/ http://togami.com/~k12linux-temporary/fedora/9/ I built test RPMS into the test repository. There could be something else wrong. Let's see if the two ideas above help first. Warren Togami wtogami at redhat.com From wtogami at redhat.com Sun May 18 05:48:14 2008 From: wtogami at redhat.com (Warren Togami) Date: Sun, 18 May 2008 01:48:14 -0400 Subject: Print to printer connected to ltsp thin client In-Reply-To: <48274AFD.9030908@hanzlici.cz> References: <48274AFD.9030908@hanzlici.cz> Message-ID: <482FC31E.407@redhat.com> Frantisek Hanzlik wrote: > As I can see on Ubuntu and Debian forums, jetpipe is very simple python > script, and at this time isn't capable initialize serial line printers. > I a week ago upgrade some system I manage to F9/LTSP 5 and must solve > printing to printers (paralell, serial and USB too) connected to thin > clients. > Thus I was build print server which was used in ltsp 4 - "lp_server" > from P.Powell. > After several days utilization, I must say this work without problems. > (On older versions K12LTSP I was using this program for more than four > years, and it works well, with small system footprint). > > For easy integration lp_server to F9 I made: > > - lp_server RPM package for F9/i386 lp_server-1.1.6-1.fc9.i386.rpm > available at > http://hanzlici.cz/packages/fedora/lp_server/lp_server-1.1.6-1.fc9.i386.rpm > (23kB) > > - lp_server source RPM lp_server-1.1.6-1.fc9.src.rpm available at > http://hanzlici.cz/packages/fedora/lp_server/lp_server-1.1.6-1.fc9.src.rpm > (73 KB) > > - patch for ltsp-init-common script from ltsp-5.1.7, which replaces > jetpipe with lp-server: ltsp-init-common.patch.tgz available at > http://hanzlici.cz/packages/fedora/lp_server/ltsp-init-common.patch.tgz > Patch is against ltsp-5.1.7 package (1.2 kB) jetpipe is the upstream standard for printing. Debian/Ubuntu developers confirmed that jetpipe can't do serial printing. Both said they evaluated it for Debian or Ubuntu but they cannot ship it because the copyrights on the source files are unclear. They were unable to contact the author to clarify the copyright thus both are unable to ship it. Fedora tends to have as-strict or stricter copyright/license compliance requirements than other distros so we likely cannot ship this either. While lp_server cannot be shipped in Fedora directly, perhaps you could convince upstream to make a standard lts.conf option to allow using 3rd party print servers other than the standard jetpipe. Otherwise, I personally cannot prioritize working on it. Notes about your packages and how to use it should be added to the K12Linux wiki though. Warren Togami wtogami at redhat.com From franta at hanzlici.cz Sun May 18 11:00:37 2008 From: franta at hanzlici.cz (Frantisek Hanzlik) Date: Sun, 18 May 2008 13:00:37 +0200 Subject: Print to printer connected to ltsp thin client In-Reply-To: <482FC31E.407@redhat.com> References: <48274AFD.9030908@hanzlici.cz> <482FC31E.407@redhat.com> Message-ID: <48300C55.6020107@hanzlici.cz> Warren Togami wrote: > Frantisek Hanzlik wrote: >> As I can see on Ubuntu and Debian forums, jetpipe is very simple python >> script, and at this time isn't capable initialize serial line printers. >> I a week ago upgrade some system I manage to F9/LTSP 5 and must solve >> printing to printers (paralell, serial and USB too) connected to thin >> clients. >> Thus I was build print server which was used in ltsp 4 - "lp_server" >> from P.Powell. >> After several days utilization, I must say this work without problems. >> (On older versions K12LTSP I was using this program for more than four >> years, and it works well, with small system footprint). >> >> For easy integration lp_server to F9 I made: >> >> - lp_server RPM package for F9/i386 lp_server-1.1.6-1.fc9.i386.rpm >> available at >> http://hanzlici.cz/packages/fedora/lp_server/lp_server-1.1.6-1.fc9.i386.rpm >> >> (23kB) >> >> - lp_server source RPM lp_server-1.1.6-1.fc9.src.rpm available at >> http://hanzlici.cz/packages/fedora/lp_server/lp_server-1.1.6-1.fc9.src.rpm >> >> (73 KB) >> >> - patch for ltsp-init-common script from ltsp-5.1.7, which replaces >> jetpipe with lp-server: ltsp-init-common.patch.tgz available at >> http://hanzlici.cz/packages/fedora/lp_server/ltsp-init-common.patch.tgz >> Patch is against ltsp-5.1.7 package (1.2 kB) > > jetpipe is the upstream standard for printing. - Yes, I agree with You, but maybe its development stands. - jetpipe lacks some important feature in contrast with lp_server. - jetpipe has much higher memory requirements (RSS=2052 kB vs. 256 kB) than lp_server. Resources on thin client are rather low, and utilize Python on it isn't (I think) so good as on powerfull desktop. > Debian/Ubuntu developers > confirmed that jetpipe can't do serial printing. Both said they > evaluated it for Debian or Ubuntu but they cannot ship it because the > copyrights on the source files are unclear. They were unable to contact > the author to clarify the copyright thus both are unable to ship it. Author, Patrick Powell, seems be still active at LPRng - You can see http://www.lprng.com and there is mail address: papowell at lprng.com Proper homepage for lp_server source is probably at ftp://ftp.lprng.com/pub/LPRng/UNIXTOOLS/lp_server/ "Copyright" and "LICENSE" files attached with lp_server sources says: Use and distribution of this software is covered by the GNU COPYING license. Please refer to this for terms and conditions. And attached "COPYING" file is GNU GPL v2. I can tried contact lp_server author, but unfortunately (as you can see:)) my english is too bad for serious dialogue. > Fedora tends to have as-strict or stricter copyright/license compliance > requirements than other distros so we likely cannot ship this either. > > While lp_server cannot be shipped in Fedora directly, perhaps you could > convince upstream to make a standard lts.conf option to allow using 3rd > party print servers other than the standard jetpipe. How I can do it, please? For me, it appears that LTSP development team laid some groundwork for LTSP 5, and then next active development is at Debian and Ubuntu distros. > > Otherwise, I personally cannot prioritize working on it. Notes about > your packages and how to use it should be added to the K12Linux wiki > though. OK, thank You, I will try do it. > > Warren Togami > wtogami at redhat.com > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/k12linux-devel-list Franta Hanzlik franta at hanzlici.cz From wtogami at redhat.com Sun May 18 15:13:18 2008 From: wtogami at redhat.com (Warren Togami) Date: Sun, 18 May 2008 11:13:18 -0400 Subject: Print to printer connected to ltsp thin client In-Reply-To: <48300C55.6020107@hanzlici.cz> References: <48274AFD.9030908@hanzlici.cz> <482FC31E.407@redhat.com> <48300C55.6020107@hanzlici.cz> Message-ID: <4830478E.5070501@redhat.com> Frantisek Hanzlik wrote: > Author, Patrick Powell, seems be still active at LPRng - You can see > http://www.lprng.com and there is mail address: papowell at lprng.com > > Proper homepage for lp_server source is probably at > ftp://ftp.lprng.com/pub/LPRng/UNIXTOOLS/lp_server/ > > "Copyright" and "LICENSE" files attached with lp_server sources says: > Use and distribution of this software is covered by the GNU COPYING > license. Please refer to this for terms and conditions. > > And attached "COPYING" file is GNU GPL v2. > I can tried contact lp_server author, but unfortunately (as you can see:)) > my english is too bad for serious dialogue. /************************************************************************** * LPRng IFHP Filter * Copyright 1994-1997 Patrick Powell, San Diego, CA * * Based on the CTI printer filters. * See COPYRIGHT for details. Most of the source files are marked like this. This is improperly labelled because it does not refer to the actual license name. If the author is active then perhaps you could ask for a new release with the license headers clarified. http://www.fsf.org/licensing/licenses/gpl-howto.html Have him follow the directions here. > >> Fedora tends to have as-strict or stricter copyright/license compliance >> requirements than other distros so we likely cannot ship this either. >> >> While lp_server cannot be shipped in Fedora directly, perhaps you could >> convince upstream to make a standard lts.conf option to allow using 3rd >> party print servers other than the standard jetpipe. > How I can do it, please? > For me, it appears that LTSP development team laid some groundwork for > LTSP 5, and then next active development is at Debian and Ubuntu distros. https://code.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk These days it is very much a joint effort. Fedora shares leadership in LTSP upstream with Debian and Ubuntu. Warren Togami wtogami at redhat.com From franta at hanzlici.cz Mon May 19 01:18:24 2008 From: franta at hanzlici.cz (Frantisek Hanzlik) Date: Mon, 19 May 2008 03:18:24 +0200 Subject: getltscfg for individual thin clients Message-ID: <4830D560.8080301@hanzlici.cz> Hello, in little connection with lp_server, I forgot one thing - F9 ltsp-1.5.7 scripts nowhere calls 'getltscfg -n' for thin clients individual settings, thus only [default] section of lts.conf is processed - it is by calling 'getltscfg -a' at beginning of "ltsp_config" script (which is then included in several others scripts). My workaround about this was put "getltscfg -n" command at start of "ltsp-init-common" script: --- ltsp-init-common.OLD 2008-05-07 23:13:50.000000000 +0200 +++ ltsp-init-common 2008-05-19 03:13:56.000000000 +0200 @@ -7,6 +7,7 @@ msg="$1" logger -p user.warning -t ltsp-client "warning: $msg" } +getltscfg -n # get client specific settings start_sound() { if boolean_is_true "$SOUND" ; then -- Regards, Frantisek Hanzlik == Lucni 502 Linux/Unix/Novell/Inter-/Net Tel: +420-373729699 == == 33209 Stenovice e-mail:franta at hanzlici.cz Fax: +420-373729699 == == Czech Republic http://hanzlici.cz/ GSM: +420-604117319 == From wtogami at redhat.com Mon May 19 01:37:24 2008 From: wtogami at redhat.com (Warren Togami) Date: Sun, 18 May 2008 21:37:24 -0400 Subject: getltscfg for individual thin clients In-Reply-To: <4830D560.8080301@hanzlici.cz> References: <4830D560.8080301@hanzlici.cz> Message-ID: <4830D9D4.6060403@redhat.com> Frantisek Hanzlik wrote: > Hello, > > in little connection with lp_server, I forgot one thing - F9 ltsp-1.5.7 > scripts nowhere calls 'getltscfg -n' for thin clients individual > settings, thus only [default] section of lts.conf is processed - it > is by calling 'getltscfg -a' at beginning of "ltsp_config" script > (which is then included in several others scripts). > > My workaround about this was put "getltscfg -n" command at start > of "ltsp-init-common" script: > > --- ltsp-init-common.OLD 2008-05-07 23:13:50.000000000 +0200 > +++ ltsp-init-common 2008-05-19 03:13:56.000000000 +0200 > @@ -7,6 +7,7 @@ > msg="$1" > logger -p user.warning -t ltsp-client "warning: $msg" > } > +getltscfg -n # get client specific settings > > start_sound() { > if boolean_is_true "$SOUND" ; then > Grepping through ltsp-trunk I don't see Debian doing anything like this. How is Debian's LTSP using individual client settings? Warren Togami wtogami at redhat.com From franta at hanzlici.cz Mon May 19 01:58:55 2008 From: franta at hanzlici.cz (Frantisek Hanzlik) Date: Mon, 19 May 2008 03:58:55 +0200 Subject: getltscfg for individual thin clients In-Reply-To: <4830D9D4.6060403@redhat.com> References: <4830D560.8080301@hanzlici.cz> <4830D9D4.6060403@redhat.com> Message-ID: <4830DEDF.6060107@hanzlici.cz> Warren Togami wrote: > Frantisek Hanzlik wrote: >> Hello, >> >> in little connection with lp_server, I forgot one thing - F9 ltsp-1.5.7 >> scripts nowhere calls 'getltscfg -n' for thin clients individual >> settings, thus only [default] section of lts.conf is processed - it >> is by calling 'getltscfg -a' at beginning of "ltsp_config" script >> (which is then included in several others scripts). >> >> My workaround about this was put "getltscfg -n" command at start >> of "ltsp-init-common" script: >> >> --- ltsp-init-common.OLD 2008-05-07 23:13:50.000000000 +0200 >> +++ ltsp-init-common 2008-05-19 03:13:56.000000000 +0200 >> @@ -7,6 +7,7 @@ >> msg="$1" >> logger -p user.warning -t ltsp-client "warning: $msg" >> } >> +getltscfg -n # get client specific settings >> >> start_sound() { >> if boolean_is_true "$SOUND" ; then >> > > Grepping through ltsp-trunk I don't see Debian doing anything like this. > How is Debian's LTSP using individual client settings? > > Warren Togami > wtogami at redhat.com > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/k12linux-devel-list > Sorry for my shortage, after looking to getltscfg.c source, I see when getltscfg is called with "-n" option, then output only station specific settings. And when is called with "-a", then getltscfg output ALL: station specific and these from [default] too. Thus calling getltscfg with -a is quite sufficient. This my mistake was comming from bad named client-specific sections, grrr. Franta H From gideon at symbio-technologies.com Mon May 19 13:32:21 2008 From: gideon at symbio-technologies.com (Gideon Romm) Date: Mon, 19 May 2008 09:32:21 -0400 Subject: [Ltsp-developer] getltscfg for individual thin clients In-Reply-To: <4830D9D4.6060403@redhat.com> References: <4830D560.8080301@hanzlici.cz> <4830D9D4.6060403@redhat.com> Message-ID: <3d626ed0805190632h1de29792y3efbb3cc5e7491ba@mail.gmail.com> getltscfg -a does not only process the [default] section. It processes the individual workstation configuration. The '-a' simply means report all parameters (as opposed to just a single parameter). I hope this clears up the confusion. You should never need anything but "getltscfg -a" -Gadi On Sun, May 18, 2008 at 9:37 PM, Warren Togami wrote: > Frantisek Hanzlik wrote: >> Hello, >> >> in little connection with lp_server, I forgot one thing - F9 ltsp-1.5.7 >> scripts nowhere calls 'getltscfg -n' for thin clients individual >> settings, thus only [default] section of lts.conf is processed - it >> is by calling 'getltscfg -a' at beginning of "ltsp_config" script >> (which is then included in several others scripts). >> >> My workaround about this was put "getltscfg -n" command at start >> of "ltsp-init-common" script: >> >> --- ltsp-init-common.OLD 2008-05-07 23:13:50.000000000 +0200 >> +++ ltsp-init-common 2008-05-19 03:13:56.000000000 +0200 >> @@ -7,6 +7,7 @@ >> msg="$1" >> logger -p user.warning -t ltsp-client "warning: $msg" >> } >> +getltscfg -n # get client specific settings >> >> start_sound() { >> if boolean_is_true "$SOUND" ; then >> > > Grepping through ltsp-trunk I don't see Debian doing anything like this. > How is Debian's LTSP using individual client settings? > > Warren Togami > wtogami at redhat.com > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _____________________________________________________________________ > Ltsp-developer mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-developer > For additional LTSP help, try #ltsp channel on irc.freenode.net > From franta at hanzlici.cz Tue May 20 12:55:45 2008 From: franta at hanzlici.cz (Frantisek Hanzlik) Date: Tue, 20 May 2008 14:55:45 +0200 Subject: [Ltsp-developer] getltscfg for individual thin clients In-Reply-To: <3d626ed0805190632h1de29792y3efbb3cc5e7491ba@mail.gmail.com> References: <4830D560.8080301@hanzlici.cz> <4830D9D4.6060403@redhat.com> <3d626ed0805190632h1de29792y3efbb3cc5e7491ba@mail.gmail.com> Message-ID: <4832CA51.1020303@hanzlici.cz> Agree, I found it, see my previous post. This my bad assumption was because LTSP 5 in Fedora is naming clients as "client-IP_ADDR" in contrast with LTSP 4-, where client hostname was taken from resolver. I had lts.conf from LTSP 4, where individual client entries was in form "WSName.mysite.com". I then rewrite them to "client-$IPADDR", but in process solving this problem I wrongly thought about getltscfg behavior. I know entries in lts.conf may be specified as MAC addresses, IP addresses or FQDN names. I'm not sure when above Fedora 9 client naming behavior is by any way configurable, but IMHO setting client hostname from resolver (if it is possible) is better then hard setting to client-$IPADDR. Franta Hanzlik Gideon Romm wrote: > getltscfg -a does not only process the [default] section. It > processes the individual workstation configuration. The '-a' simply > means report all parameters (as opposed to just a single parameter). > > I hope this clears up the confusion. You should never need anything > but "getltscfg -a" > > -Gadi > > On Sun, May 18, 2008 at 9:37 PM, Warren Togami wrote: >> Frantisek Hanzlik wrote: >>> Hello, >>> >>> in little connection with lp_server, I forgot one thing - F9 ltsp-1.5.7 >>> scripts nowhere calls 'getltscfg -n' for thin clients individual >>> settings, thus only [default] section of lts.conf is processed - it >>> is by calling 'getltscfg -a' at beginning of "ltsp_config" script >>> (which is then included in several others scripts). >>> >>> My workaround about this was put "getltscfg -n" command at start >>> of "ltsp-init-common" script: >>> >>> --- ltsp-init-common.OLD 2008-05-07 23:13:50.000000000 +0200 >>> +++ ltsp-init-common 2008-05-19 03:13:56.000000000 +0200 >>> @@ -7,6 +7,7 @@ >>> msg="$1" >>> logger -p user.warning -t ltsp-client "warning: $msg" >>> } >>> +getltscfg -n # get client specific settings >>> >>> start_sound() { >>> if boolean_is_true "$SOUND" ; then >>> >> Grepping through ltsp-trunk I don't see Debian doing anything like this. >> How is Debian's LTSP using individual client settings? >> >> Warren Togami >> wtogami at redhat.com >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _____________________________________________________________________ >> Ltsp-developer mailing list. To un-subscribe, or change prefs, goto: >> https://lists.sourceforge.net/lists/listinfo/ltsp-developer >> For additional LTSP help, try #ltsp channel on irc.freenode.net >> > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/k12linux-devel-list > > !DSPAM:4831979789059012215599! > From lnkemp at bolivar.k12.mo.us Wed May 21 17:47:49 2008 From: lnkemp at bolivar.k12.mo.us (Kemp, Levi) Date: Wed, 21 May 2008 12:47:49 -0500 Subject: Setting up with two NICS Message-ID: I just joined this list knowing that I'm going to need help very soon setting up Fedora 9 with LTSP 5. I've got to decide this soon if I want to use Ubuntu 8.04 or Fedora 9 for my computer lab this fall. I've successfully setup Ubuntu 8.04 with LTSP, works great aside from the fact that getting it integrated into AD is more complicated. They've got likewise and SADMS, and I can get them to work to some degree but always fail at pam_mount. With Fedora I can easily integrate into AD, it just works, and getting pam_mount to work is pretty simple. But I haven't successfully installed LTSP 5 into it yet. I followed the install directions as best I could, but I fear I'm lost when it comes to configuring the second nic. I see the bridge is setup, but only one nic is active (outside network). It seems like this might be a simple step, and since everything else may already be configured correctly if I could get some assistance I'm likely to go with Fedora again this year, I'm more used to it because of Eric Harrison anyways. Thanks. Let me know what info you need because I know I'm being vague here, but I'm unsure where to troubleshoot at the moment. Levi -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtogami at redhat.com Wed May 21 19:22:56 2008 From: wtogami at redhat.com (Warren Togami) Date: Wed, 21 May 2008 15:22:56 -0400 Subject: Setting up with two NICS In-Reply-To: References: Message-ID: <48347690.7040503@redhat.com> Kemp, Levi wrote: > I just joined this list knowing that I'm going to need help very soon > setting up Fedora 9 with LTSP 5. I've got to decide this soon if I want > to use Ubuntu 8.04 or Fedora 9 for my computer lab this fall. I've > successfully setup Ubuntu 8.04 with LTSP, works great aside from the > fact that getting it integrated into AD is more complicated. They've > got likewise and SADMS, and I can get them to work to some degree but > always fail at pam_mount. With Fedora I can easily integrate into AD, it > just works, and getting pam_mount to work is pretty simple. But I > haven't successfully installed LTSP 5 into it yet. I followed the > install directions as best I could, but I fear I'm lost when it comes to > configuring the second nic. I see the bridge is setup, but only one nic > is active (outside network). It seems like this might be a simple step, > and since everything else may already be configured correctly if I could > get some assistance I'm likely to go with Fedora again this year, I'm > more used to it because of Eric Harrison anyways. Thanks. Let me know > what info you need because I know I'm being vague here, but I'm unsure > where to troubleshoot at the moment. ifconfig shows eth0 and eth1? Make sure you turned off NetworkManager and you are using service network instead. chkconfig NetworkManager off; chkconfig network on; Then reboot. Your eth device to be added to the bridge must have no IP address assigned to it. Could you please join our IRC chat and ask for help there? It would be easier to help you in live chat. Warren From balmquist at mindfirestudios.com Wed May 21 21:58:02 2008 From: balmquist at mindfirestudios.com (Almquist Burke) Date: Wed, 21 May 2008 16:58:02 -0500 Subject: Setting up with two NICS In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Take a look at this. If any of it looks confusing, let me know. https://fedorahosted.org/k12linux/wiki/NetworkSetup On May 21, 2008, at 12:47 PM, Kemp, Levi wrote: > I just joined this list knowing that I'm going to need help very > soon setting up Fedora 9 with LTSP 5. I've got to decide this soon > if I want to use Ubuntu 8.04 or Fedora 9 for my computer lab this > fall. I've successfully setup Ubuntu 8.04 with LTSP, works great > aside from the fact that getting it integrated into AD is more > complicated. They've got likewise and SADMS, and I can get them to > work to some degree but always fail at pam_mount. With Fedora I can > easily integrate into AD, it just works, and getting pam_mount to > work is pretty simple. But I haven't successfully installed LTSP 5 > into it yet. I followed the install directions as best I could, but > I fear I'm lost when it comes to configuring the second nic. I see > the bridge is setup, but only one nic is active (outside network). > It seems like this might be a simple step, and since everything > else may already be configured correctly if I could get some > assistance I'm likely to go with Fedora again this year, I'm more > used to it because of Eric Harrison anyways. Thanks. Let me know > what info you need because I know I'm being vague here, but I'm > unsure where to troubleshoot at the moment. > > Levi > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/k12linux-devel-list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iEYEARECAAYFAkg0muoACgkQxWV7OPa/g5GXTQCfbTGJN0WOawqstB5Xv+D3Ajbq CioAniAznn7gJkyEBqk6AEGUgcH4P3VL =DaIh -----END PGP SIGNATURE----- From wtogami at redhat.com Wed May 21 23:30:33 2008 From: wtogami at redhat.com (Warren Togami) Date: Wed, 21 May 2008 19:30:33 -0400 Subject: Setting up with two NICS In-Reply-To: References: Message-ID: <4834B099.8080608@redhat.com> Almquist Burke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Take a look at this. > If any of it looks confusing, let me know. > > https://fedorahosted.org/k12linux/wiki/NetworkSetup Hi Almquist, thanks for working on the documentation. Have you tried NM_CONTROLLED=no in the ifcfg-ethX file? It hasn't been behaving entirely correctly so it might not be usable for LTSP with a hybrid NetworkManager and service network configuration. We might be best off just advising all permanent LTSP server users to turn NetworkManager off completely in order to reduce confusion. Move all the NetworkManager related stuff into an "AdvancedNetworkSetup" page. Warren Togami wtogami at redhat.com From weba at ancollege.org Fri May 23 16:53:48 2008 From: weba at ancollege.org (nilakhya chatterjee) Date: Fri, 23 May 2008 22:23:48 +0530 Subject: I am here 2 volunteer with the website's logo and design Message-ID: <32a1284d0805230953k9878765m57ee725a18511b4b@mail.gmail.com> warren and others please let me know if i am somehow needed here ........... i hope i can give back 2 the ltsp i had been using for last few years thanks n. chatterjee -------------- next part -------------- An HTML attachment was scrubbed... URL: From PNelson at nwresd.k12.or.us Sat May 24 23:47:08 2008 From: PNelson at nwresd.k12.or.us (Paul Nelson) Date: Sat, 24 May 2008 16:47:08 -0700 Subject: Logo for K12Linux Message-ID: <8215CF8A27315F4A8F1A4A8DD65813643C96D3@wsc-mail-01.nwresd.k12.or.us> Hello Folks, I created a logo for https://fedorahosted.org/k12linux/ Here are links to png and xcf versions. http://k12ltsp.org/mediawiki/images/a/ad/K12linux_logo.png http://pnelson.us/k12linux_logo.xcf I installed FC9 and LTSP and now have clients booting. I'm working on a simple walkthrough for th eK12LTSP wiki site but the documentation on fedorahosted.org/k12linux was enough to get me going. ;-) Paul Nelson From wtogami at redhat.com Sun May 25 02:54:32 2008 From: wtogami at redhat.com (Warren Togami) Date: Sat, 24 May 2008 22:54:32 -0400 Subject: No Warren in meetings for 3 weeks Message-ID: <4838D4E8.5020009@redhat.com> https://fedorahosted.org/k12linux/wiki/Meetings I will not be able to attend the meetings on May 25th, June 1st and June 8th because I am travelling. I am still working on K12Linux during this time. It is just my schedule just does not line up with Internet access during the meeting times. =( If anything is discussed please write notes in the meeting page above. Warren From wtogami at redhat.com Sun May 25 03:28:43 2008 From: wtogami at redhat.com (Warren Togami) Date: Sat, 24 May 2008 23:28:43 -0400 Subject: X Keyboard layout problem Message-ID: <4838DCEB.3050700@redhat.com> https://bugzilla.redhat.com/show_bug.cgi?id=448196 This is a critical problem for anybody using a non-US keyboard layout with LTSP. LTSP on Debian uses ltsp-trunk/client/configure-x.sh to generate an xorg.conf and mangle it to use an explicit keyboard layout before running the actual X. Fedora LTSP uses X autoconfiguration without an xorg.conf. This seems to be working extremely well, except for cases like this where we need a specific configuration option that differs from the X autoconfiguration. Any ideas of what we can do? Warren Togami wtogami at redhat.com From dbond at nrggos.com.au Sun May 25 07:19:55 2008 From: dbond at nrggos.com.au (Bond, Darryl) Date: Sun, 25 May 2008 17:19:55 +1000 Subject: X Keyboard layout problem In-Reply-To: <4838DCEB.3050700@redhat.com> Message-ID: I think we need to be able to generate a special xorg.conf. What if we need a lower/higher resolution than the one the auto configurator determines. My site (with 300 LTSP clients) has lots of special needs in the xorg.conf, ie resolution, extra fonts, dual screen etc. Xrandr may be the way to handle resolution after the X server starts. Darryl -----Original Message----- From: k12linux-devel-list-bounces at redhat.com [mailto:k12linux-devel-list-bounces at redhat.com] On Behalf Of Warren Togami Sent: Sunday, 25 May 2008 1:29 PM To: k12linux-devel-list at redhat.com; Development discussions related to Fedora Core Subject: X Keyboard layout problem https://bugzilla.redhat.com/show_bug.cgi?id=448196 This is a critical problem for anybody using a non-US keyboard layout with LTSP. LTSP on Debian uses ltsp-trunk/client/configure-x.sh to generate an xorg.conf and mangle it to use an explicit keyboard layout before running the actual X. Fedora LTSP uses X autoconfiguration without an xorg.conf. This seems to be working extremely well, except for cases like this where we need a specific configuration option that differs from the X autoconfiguration. Any ideas of what we can do? Warren Togami wtogami at redhat.com _______________________________________________ K12Linux-devel-list mailing list K12Linux-devel-list at redhat.com https://www.redhat.com/mailman/listinfo/k12linux-devel-list The contents of this electronic message and any attachments are intended only for the addressee and may contain legally privileged, personal, sensitive or confidential information. If you are not the intended addressee, and have received this email, any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. Any legal privilege or confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of delivery to any person other than intended addressee. If you have received this message and are not the intended addressee you should notify the sender by return email and destroy all copies of the message and any attachments. Unless expressly attributed, the views expressed in this email do not necessarily represent the views of the company. From wtogami at redhat.com Sun May 25 15:20:08 2008 From: wtogami at redhat.com (Warren Togami) Date: Sun, 25 May 2008 11:20:08 -0400 Subject: X Keyboard layout problem In-Reply-To: References: Message-ID: <483983A8.2030809@redhat.com> I think xorg.conf should be optional. The default no xorg.conf should be able to handle simpler options overlayed on top of the autoconfiguration. Keyboard layout and resolution should be overridable. Extra fonts should be detected automatically (you need xorg.conf options for this? huh?) Dual screen might be a legitimate case where you need your own xorg.conf. Warren Togami wtogami at redhat.com Bond, Darryl wrote: > I think we need to be able to generate a special xorg.conf. > What if we need a lower/higher resolution than the one the auto configurator determines. > > My site (with 300 LTSP clients) has lots of special needs in the xorg.conf, ie resolution, extra fonts, dual screen etc. > > Xrandr may be the way to handle resolution after the X server starts. > > Darryl > > > -----Original Message----- > From: k12linux-devel-list-bounces at redhat.com [mailto:k12linux-devel-list-bounces at redhat.com] On Behalf Of Warren Togami > Sent: Sunday, 25 May 2008 1:29 PM > To: k12linux-devel-list at redhat.com; Development discussions related to Fedora Core > Subject: X Keyboard layout problem > > > https://bugzilla.redhat.com/show_bug.cgi?id=448196 > This is a critical problem for anybody using a non-US keyboard layout with LTSP. > > LTSP on Debian uses ltsp-trunk/client/configure-x.sh to generate an xorg.conf and mangle it to use an explicit keyboard layout before running the actual X. > > Fedora LTSP uses X autoconfiguration without an xorg.conf. This seems to be working extremely well, except for cases like this where we need a specific configuration option that differs from the X autoconfiguration. > > Any ideas of what we can do? > > Warren Togami > wtogami at redhat.com > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com https://www.redhat.com/mailman/listinfo/k12linux-devel-list > > The contents of this electronic message and any attachments are intended only for the addressee and may contain legally privileged, personal, sensitive or confidential information. If you are not the intended addressee, and have received this email, any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. Any legal privilege or confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of delivery to any person other than intended addressee. If you have received this message and are not the intended addressee you should notify the sender by return email and destroy all copies of the message and any attachments. Unless expressly attributed, the views expressed in this email do not necessarily represent the views of the company. > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/k12linux-devel-list From balmquist at mindfirestudios.com Sun May 25 16:01:12 2008 From: balmquist at mindfirestudios.com (Almquist Burke) Date: Sun, 25 May 2008 11:01:12 -0500 Subject: Setting up with two NICS In-Reply-To: <4834B099.8080608@redhat.com> References: <4834B099.8080608@redhat.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Have you tried NM_CONTROLLED=no in the ifcfg-ethX file? It hasn't > been behaving entirely correctly so it might not be usable for LTSP > with a hybrid NetworkManager and service network configuration. > Nope, haven't tried this. I just went and killed Network manager. I figured for a permanent setup it wouldn't be that important anyway. The network service would be just fine. Network manager looks much more useful for portable devices. > We might be best off just advising all permanent LTSP server users > to turn NetworkManager off completely in order to reduce > confusion. Move all the NetworkManager related stuff into an > "AdvancedNetworkSetup" page. > > Warren Togami > wtogami at redhat.com > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/k12linux-devel-list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iEYEARECAAYFAkg5jUgACgkQxWV7OPa/g5HWRACfbT2foPhK5SjNoWNV81+vCncP lQgAnRp3AZG+GNcig7cExv3OwOOtcyMx =TTSP -----END PGP SIGNATURE----- From weba at ancollege.org Sun May 25 20:34:23 2008 From: weba at ancollege.org (nilakhya chatterjee) Date: Mon, 26 May 2008 02:04:23 +0530 Subject: Logo for K12Linux In-Reply-To: <8215CF8A27315F4A8F1A4A8DD65813643C96D3@wsc-mail-01.nwresd.k12.or.us> References: <8215CF8A27315F4A8F1A4A8DD65813643C96D3@wsc-mail-01.nwresd.k12.or.us> Message-ID: <32a1284d0805251334p7d6f6c47w8ad08dd7237ce5c0@mail.gmail.com> just a few drop shadows ..........hmmmmm clever ........!!! On Sun, May 25, 2008 at 5:17 AM, Paul Nelson wrote: > > Hello Folks, > > I created a logo for https://fedorahosted.org/k12linux/ Here are links to > png and xcf versions. > > http://k12ltsp.org/mediawiki/images/a/ad/K12linux_logo.png > http://pnelson.us/k12linux_logo.xcf > > I installed FC9 and LTSP and now have clients booting. I'm working on a > simple walkthrough for th eK12LTSP wiki site but the documentation on > fedorahosted.org/k12linux was enough to get me going. > > > ;-) Paul Nelson > > > _______________________________________________ > K12Linux-devel-list mailing list > K12Linux-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/k12linux-devel-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew at mobileitsolutions.co.uk Sat May 31 13:01:26 2008 From: andrew at mobileitsolutions.co.uk (Andrew Osborne) Date: Sat, 31 May 2008 14:01:26 +0100 Subject: LDM ' changing the default session' Message-ID: <000001c8c31e$706a29a0$5a02a8c0@kim> I have installed Fedora 9/LTSP 5 with no problems (except using a terminal with printer connected), and must congratulate all involved for the best K12 yet. Is it possible to change the default from Gnome to KDE or something else, may be in xsession? I'm aware that work is been done on LDM but is there a workaround for the moment? Thanks in advance Andrew Osborne -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew at mobileitsolutions.co.uk Sat May 31 13:01:26 2008 From: andrew at mobileitsolutions.co.uk (Andrew Osborne) Date: Sat, 31 May 2008 14:01:26 +0100 Subject: (no subject) Message-ID: <000501c8c31e$70dc9a80$5a02a8c0@kim> -------------- next part -------------- An HTML attachment was scrubbed... URL: