IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 22 April 2013   (all times are UTC)

00:08
<viniciusferrao>
Noone here?
00:20JesseCW has joined IRC (JesseCW!~JesseCWor@wsip-98-175-20-126.br.br.cox.net)
00:29JesseC has left IRC (JesseC!~JesseCWor@wsip-98-175-20-126.br.br.cox.net, *.net *.split)
01:14vagrantc has joined IRC (vagrantc!~vagrant@c-24-22-123-61.hsd1.or.comcast.net)
01:14vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
01:35ball has joined IRC (ball!~ball@c-98-212-160-120.hsd1.il.comcast.net)
02:09ball has left IRC (ball!~ball@c-98-212-160-120.hsd1.il.comcast.net, Quit: leaving)
03:41alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
03:56sha_ has joined IRC (sha_!~sha@e177116095.adsl.alicedsl.de)
03:56sha has left IRC (sha!~sha@e177174157.adsl.alicedsl.de, Read error: Connection reset by peer)
03:57alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
04:06vnc786 has joined IRC (vnc786!~chatzilla@49.248.129.178)
04:22miup has left IRC (miup!~rcerny@84-75-21-171.dclient.hispeed.ch, Remote host closed the connection)
04:25rcerny has joined IRC (rcerny!~rcerny@84-75-21-171.dclient.hispeed.ch)
04:26rcerny has left IRC (rcerny!~rcerny@84-75-21-171.dclient.hispeed.ch, Read error: Connection reset by peer)
04:26miup has joined IRC (miup!~rcerny@84-75-21-171.dclient.hispeed.ch)
04:31vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
05:18alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
05:23miup has left IRC (miup!~rcerny@84-75-21-171.dclient.hispeed.ch, Ping timeout: 264 seconds)
05:33
<vnc786>
my fat clients is affected with this bug https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1020048/ and i did the said changes in cupsd.conf in chroot but still the persists i have made changes in <chroot> /etc/cups/cupsd.conf this is my cupsd.conf http://pastebin.com/ai2H2PCE
05:36
whereas i have one local ubuntu box ubuntu 12.04 in which i added printer like this: show shared printer by other systems in which the printer never lost connections with cups
05:49khildin has joined IRC (khildin!~khildin@ip-83-134-213-112.dsl.scarlet.be)
06:01
<work_alkisg>
cupsd.conf on the server, not on the client
06:02
Not in chroot
06:25highvolt1ge is now known as highvoltage
06:31
<vnc786>
work_alkisg: first i made changes in LTSP server file i kept "Timeout 1d" in LTSP server but still that didnt help so i tried in chroot..!!
06:44stefano-k has left IRC (stefano-k!~stefano@host19-224-static.51-82-b.business.telecomitalia.it, Quit: Ex-Chat)
06:46
<work_alkisg>
Timeout seconds
06:46
Specifies the HTTP request timeout in seconds.
06:46
Is the "d" syntax supported?
06:46work_alkisg is now known as alkisg
06:48dievel has joined IRC (dievel!~dievel@2-229-104-66.ip196.fastwebnet.it)
06:50
<vnc786>
yes but wait i will check with seconds now http://www.cups.org/documentation.php/ref-cupsd-conf.html
06:50sep has joined IRC (sep!~sep@40.211.jostedal.no)
06:55
<alkisg>
Remember to restart cups as well
07:00gbaman has joined IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com)
07:10gbaman has left IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com, Remote host closed the connection)
07:14mikkel has joined IRC (mikkel!~mikkel@80-198-36-38-static.dk.customer.tdc.net)
07:18
<vnc786>
alkisg: just wondering local installed ubuntu having no problem in which i keep open LO for an hour but in fat clients it gets connection closed in exact 5 minutes
07:18
<alkisg>
Yup, as I said last time, that's because in local installations, the cups server runs locally, while fat clients default to CUPS_SERVER=server
07:19
If you change that to CUPS_SERVER=localhost, then you make them the same as local installations
07:19
But then you'd have to manage printers in printers.conf
07:41vector has joined IRC (vector!~vector@host-44-180-230-24.midco.net)
07:47develo has joined IRC (develo!~naboo__@aflc132.neoplus.adsl.tpnet.pl)
07:51naboo has left IRC (naboo!~naboo__@afln127.neoplus.adsl.tpnet.pl, Ping timeout: 248 seconds)
07:52
<vnc786>
it seems that seconds is working because till now it has not lost connection with printer i have kept 5400 seconds (1 hour 30 minutes) it has already past 22 minutes ..!!
08:06ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 255 seconds)
08:06ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
08:37bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
08:51gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
09:18mar77i has joined IRC (mar77i!~mar77i@213.221.253.66)
09:22
<mar77i>
hello #ltsp. I have identified a bug with the software "scratch" which is based on squeak, though the problem may likely stem ltsp. scratch is using some xshm flag on squeak, which in turn tries to allocate memory in /dev/shm, and that doesn't seem accessible on ltsp clients...
09:24
it may have to do with the security on the mounted /dev or something, I'm not exactly sure where to look.
09:25
<alkisg>
https://bugs.launchpad.net/debian/+source/scratch/+bug/1076036
09:25
There's a fixed version available...
09:26
<mar77i>
well, I did that manually already.
09:27
but I'm not sure that's the 'proper' fix. why is xshm not an option on thin clients?
09:27highvoltage has left IRC (highvoltage!~highvolta@196-215-30-140.dynamic.isadsl.co.za, Ping timeout: 276 seconds)
09:27gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
09:27
<alkisg>
Because the xserver is on a separate machine than the x client
09:28
But they disabled it because of unity anyway, not because of thin clients...
09:28
So new scratch versions won't have -xshm anymore
09:30
<gvy>
and someone would call that "progress"
09:31
<mar77i>
when does that patch hit edubuntu?
09:32
<alkisg>
It already has, raring has it
09:33
<mar77i>
oh. so now only my management is the problem?
09:34
<alkisg>
What management?
09:34
Which edubuntu version do you have?
09:34
<mar77i>
I don't use edubuntu. my boss wants to deploy it for a customer.
09:37
and he usually avoids using the newest shiniest stuff because it's "unstable" - which is imho very antisocial. otoh he's unable to report a bug due to the language barrier.
09:39
it has benefits. eg, I can talk openly here :)
09:41miup has joined IRC (miup!~rcerny@imap.revamp-it.ch)
09:46
<elias_a>
mar77i: Which country do you live in if I may ask?
09:47
<vnc786>
it seems Timeout in seconds works thanks for this !!! will confirm tomorrow
09:48
1. LTSP server 2. ubuntu12.04 fat clients 64 bit 3. ubuntu stand alone box
09:48highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
09:49
<vnc786>
i installed epoptes server pacakage in (3)ubuntu stand alone box and epoptes client in chroot (1) but cannot see clients still in (3)epoptes(server) what else i have to rather than this http://www.epoptes.org/installation
09:49
right now i dont have DNS and i did <chroot> /etc/hosts > 172.16.0.8 server but the file says it will be rewritten ..so ...??
09:50miup has left IRC (miup!~rcerny@imap.revamp-it.ch, Ping timeout: 256 seconds)
09:50
<elias_a>
mar77i: You have a finnish ircname (martti). Are you a Finn by any chance?
09:52Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
09:55
<alkisg>
vnc786: the teacher will always work no the standalone box?
09:57bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 256 seconds)
10:04miup has joined IRC (miup!~rcerny@imap.revamp-it.ch)
10:13laurense has left IRC (laurense!~laurens@nerd-herd.nl, Ping timeout: 256 seconds)
10:19laurense has joined IRC (laurense!~laurens@nerd-herd.nl)
10:23
<vnc786>
alkisg: sorry but i didnt get you ? but epoptes server package can be installed anywhere from which you can control fat clients..m i right ?
10:25
<alkisg>
vnc786: each client can only be controlled by a single epoptes *daemon* (not the GUI)
10:26
That daemon is best located in the same pc where the teacher works
10:31
<vnc786>
okay till now what i have done : i have installed epoptes-client in chroot, epoptes in the local machine(with Hard Disk) not in the LTSP server so this is WRONG what i have done ?
10:32alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Quit: Хана X'ам !!!)
10:32alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
10:38
<alkisg>
vnc786: you didn't answer me about where the teacher will be working on... so I can't answer if it's the best option or not
10:38
So you have 3 standalone clients, and you want the teacher to be able to use epoptes on any of them
10:38
?
10:39
Do you also want the teacher to be able to work on thin clients as well?
10:40
Finally, thin or fat clients? If they're thin, you need epoptes-client in the server too
10:40alkisg is now known as work_alkisg
10:46Da-Geek has joined IRC (Da-Geek!~Da-Geek@exch.imparando.com)
10:49alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Quit: Хана X'ам !!!)
10:49alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
11:00vector has left IRC (vector!~vector@host-44-180-230-24.midco.net, Quit: No Ping reply in 180 seconds.)
11:00vector has joined IRC (vector!~vector@host-44-180-230-24.midco.net)
11:08
<mar77i>
elias_a: where I live every fifth guy is named martin. I'll just go there on vacation in summer. :)
11:09
<elias_a>
mar77i: Ok. But why the finnish version "martti"?
11:09
<mar77i>
for distinction, as my first sentence implied.
11:09
<elias_a>
That's Martin in Finnish ;-)
11:09
Ok.
11:11
<mar77i>
also, it's funny, people came across this version when they read about the nobel prize a few years ago, and told me. I like, see?
11:12
<elias_a>
mar77i: Oh - you mean Martti Ahtisaari?
11:12
<mar77i>
yup
11:13
<elias_a>
mar77i: Nice story! :)
11:15
<mar77i>
as for the "modification" I started using it when I learned about a bit of the Finnish grammar and syllable mechanics prolly >5y ago.
11:23
or word mechanics, maybe still a misnomer. vowel harmony, strong and light consonants and such.
11:24
<vnc786>
1 LTSP server(0.1), 25 Fat clients(0.30-100) and 1 Ubuntu (which is installed on HDD)(0.8), all are in one network. I want to monitor 25 fat clients(0.30-100) from 0.8 in which i have installed epoptes server package.
11:30andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
11:32Gremble has joined IRC (Gremble!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com)
12:15Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 240 seconds)
12:32Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
12:33brunolambert has joined IRC (brunolambert!bruno@nat/revolutionlinux/x-vwprrrutcalgeluf)
12:49vector has left IRC (vector!~vector@host-44-180-230-24.midco.net, Ping timeout: 272 seconds)
13:23Gremble has left IRC (Gremble!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com, Quit: I Leave)
13:26Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
13:40
<vnc786>
is that doable ?
14:05brunolambert has left IRC (brunolambert!bruno@nat/revolutionlinux/x-vwprrrutcalgeluf, Ping timeout: 245 seconds)
14:17brunolambert has joined IRC (brunolambert!bruno@nat/revolutionlinux/x-tarpdsfkxgcwenfl)
14:23work_alkisg has left IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr, Ping timeout: 246 seconds)
14:30staffencasa_ has joined IRC (staffencasa_!~staffenca@8-220.ptpg.oregonstate.edu)
14:31bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
14:40Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
15:00brunolambert has left IRC (brunolambert!bruno@nat/revolutionlinux/x-tarpdsfkxgcwenfl, Quit: Leaving.)
15:00brunolambert has joined IRC (brunolambert!bruno@nat/revolutionlinux/x-qooigmaazustjpad)
15:08mikkel has left IRC (mikkel!~mikkel@80-198-36-38-static.dk.customer.tdc.net, Quit: Leaving)
15:08gbaman has joined IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com)
15:12miup has left IRC (miup!~rcerny@imap.revamp-it.ch, Remote host closed the connection)
15:38
<gbaman>
getting an interesting ltsp error, client tries to connect and gets nfsmount: needs a path
15:38
any ideas?
15:44adrianorg has left IRC (adrianorg!~adrianorg@177.132.223.183, Ping timeout: 272 seconds)
15:45adrianorg has joined IRC (adrianorg!~adrianorg@177.132.223.183)
15:49develo has left IRC (develo!~naboo__@aflc132.neoplus.adsl.tpnet.pl, Ping timeout: 272 seconds)
15:50
<gbaman>
anyone?
15:50
<andygraybeal>
aye, maybe wait till alkisg gets in and active
15:51
i can't help, i know that.. i barely understand how any of this wizardry works.
15:51alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Quit: Хана X'ам !!!)
15:51
<gbaman>
:)
15:55
<andygraybeal>
he's here daily, but he's busy.. i hope you understand :)
15:56
he's very helpful and is the universes's little angel
15:56
<gbaman>
i know, he has helped me many times
15:59
<andygraybeal>
;)
16:04cliebow has left IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us, Read error: Operation timed out)
16:04komunista has joined IRC (komunista!~slavko@87.244.209.121)
16:05dievel has left IRC (dievel!~dievel@2-229-104-66.ip196.fastwebnet.it, Ping timeout: 272 seconds)
16:05mar77i has left IRC (mar77i!~mar77i@213.221.253.66, Quit: bye basterds)
16:09Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 264 seconds)
16:09vector has joined IRC (vector!~vector@host-44-180-230-24.midco.net)
16:11Da-Geek has left IRC (Da-Geek!~Da-Geek@exch.imparando.com, Quit: Leaving)
16:12dievel has joined IRC (dievel!~dievel@2-229-104-66.ip196.fastwebnet.it)
16:13komunista has left IRC (komunista!~slavko@87.244.209.121, Quit: Leaving.)
16:23unkmar has joined IRC (unkmar!~unkmar@host-68-169-152-128.AMNOLT1.epbfi.com)
16:23gbaman has left IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com, Remote host closed the connection)
16:24
<unkmar>
I'm trying to get ltsp to work.
16:24
Not trolling. Why state my problem if noones listening?
16:25
<muppis>
!ask
16:25
<ltsp>
ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least a full hour after asking a question, as not everybody constantly monitors the channel.
16:25miup has joined IRC (miup!~rcerny@84-75-21-171.dclient.hispeed.ch)
16:26
<unkmar>
good, the channel was ignored last time.
16:26Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
16:26
<unkmar>
Great, its been a weekend and I have to get back to where I was. :(
16:34
<muppis>
Probably not ignored, but no one was around to help you out. I saw your problem, but you weren't around and, to be honest, I don't know much about Debian anymore. So throw out your problem again and please be more patient. :D
16:41
<unkmar>
seriously, I busy trying to get it back into the broken state I had on a new system. Not sure where the old one went. Don't recall if I last using a VM, the nettop, or the laptop.
16:42
It appears that I like dropping verbs.
16:50naboo has joined IRC (naboo!~naboo__@aflc132.neoplus.adsl.tpnet.pl)
17:07
<unkmar>
http://pastebin.com/X8x0uZH4
17:07
I had to fight with pastebin. :(
17:14
<viniciusferrao>
Dudes, someone had problems with the mailing list? I'm writing to ltsp-discuss and my messages won't get delivered… Someone know the listadmin?
17:14stefano-k has joined IRC (stefano-k!~stefano@host19-224-static.51-82-b.business.telecomitalia.it)
17:33yalu has left IRC (yalu!~yalu@91.180.127.31, Read error: Connection reset by peer)
17:35gbaman has joined IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com)
17:42yalu has joined IRC (yalu!~yalu@109.134.173.68)
17:47dievel has left IRC (dievel!~dievel@2-229-104-66.ip196.fastwebnet.it, Read error: Operation timed out)
17:51vagrantc has joined IRC (vagrantc!~vagrant@c-98-232-129-196.hsd1.or.comcast.net)
17:51vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
17:56dievel has joined IRC (dievel!~dievel@2-229-104-66.ip196.fastwebnet.it)
18:09gbaman has joined IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com)
18:09
<gbaman>
evening all
18:10
vagrantc heres one for you when i try booting a normal thin client off the debian machine i get "nfsmount: need a path" spamming on it
18:22bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Quit: Goin' down hard)
18:22bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
18:28bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
18:45bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Quit: Goin' down hard)
18:46bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
18:56
<unkmar>
nfsmount: need a path
18:57ltspuser_80 has joined IRC (ltspuser_80!401a8e82@gateway/web/freenode/ip.64.26.142.130)
18:58
<ltspuser_80>
Hey I just have a quick question. What OS'es can I use LTSP with. I don't mean install on, I mean configure for the thin clients to use. Can I have a choice at each boot?
19:00
<unkmar>
I can't properly ask my question anymore. nfsmount: need a path. What am I doing wrong?
19:00Gremble has joined IRC (Gremble!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com)
19:02bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Quit: Goin' down hard)
19:07
<vagrantc>
gbaman: sounds like you haven't configured dhcp
19:07
<gbaman>
i am using the proxydhcp guide again
19:08
<vagrantc>
ltspuser_80: not really understanding what you mean...
19:08
<gbaman>
https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
19:08
he means what os's can he set up as thin clients that get pushed out to the thin client
19:09
and can he select them at that thin client bootup option timer thing
19:09
<vagrantc>
unkmar: you need to configure dhcp to tell it what your root-path is
19:09
<ltspuser_80>
Thanks gbaman, yes that what I meant.
19:09
<vagrantc>
ltspuser_80: do you mean what OSes can an LTSP thin client log into?
19:10
<gbaman>
isnt that tftp-root=/var/lib/tftpboot
19:10
<vagrantc>
gbaman: that's the tftp dir, not NFS
19:10
<ltspuser_80>
Yes essentially, and can I have multiple configured for the user to choose when they boot the thin client.
19:10
<gbaman>
dhcp-option=17,/opt/ltsp/i386
19:10
?
19:10
<vagrantc>
gbaman: that's the one
19:10
<gbaman>
thats what it is...
19:11
<vagrantc>
gbaman: although with proxydhcp, you may have to specify it in the pxelinux.cfg files
19:11
proxydhcp is great, but it does add a layer of complication
19:11
<unkmar>
vagrantc: you mean tftp? cause my dhcp server is separate and not overly configurable.
19:11
<gbaman>
sadly i cant modify the DHCP server
19:12alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
19:12
<vagrantc>
unkmar: well, typically it's relayed via DHCP, in that case, you'll need to configure it with pxelinux
19:12
sounds like unkmar and gbaman are having similar issues
19:13
<unkmar>
vagrantc: exactly, so... how would I configure it with pxelinux? That is the current missing piece I'm hung on.
19:13
I say current, because at one point I got past that error only to reach the login loop. :(
19:14
<vagrantc>
alkisg: does ipappend 3 pass the root-server option?
19:14
er, root-path ?
19:14* vagrantc notes that the instructions at https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
19:14
<alkisg>
No, but we had some code to fallback to using some sane defaults there... not sure if that was for nbd only
19:14
<vagrantc>
suggest doing things that would get overridden when re-running ltsp-update-kernels
19:14
<unkmar>
vagrantc: I've seen settinggs that mentions root= and nfsroot= depending on where I look. Overall confusion. :(
19:15* alkisg stopped writing at the ubuntultsp wiki because people would overwrite valid instructions with either invalid ones or with bug reports about unrelated things etc etc
19:15
<vagrantc>
unkmar: what distro and release?
19:16
alkisg: thats sad :(
19:16
<unkmar>
debian squeeze. v6.x
19:16* gbaman is on debian wheezy
19:16
<gbaman>
worked perfectly fine whatever i did on edubuntu
19:16
:)
19:16
<unkmar>
gbaman: I feel ya. I had the same problems in wheezy too. :/
19:16
<vagrantc>
unkmar: ok, it'll take a bit to get my brain rolled back that far :)
19:16
<alkisg>
vagrantc: that's what you're missing on debian : /usr/share/initramfs-tools/scripts/init-premount/udhcp:ROOTPATH='$rootpath'
19:17
We should move that to some other script that runs on both distros...
19:17
<vagrantc>
we have that on Debian too...
19:17
<alkisg>
You're using ipconfig by default though, right?
19:17
Not copying the udhcp busybox binary...
19:17
<vagrantc>
yeah, but udhcp still uses the stuff passed on the commandline
19:17
er, your udhcp script
19:17
<Gremble>
heya all
19:17
<gbaman>
btw, /var/lib/tftpboot/ltsp and /opt/ltsp have a symlink, dont they?
19:18
<vagrantc>
gbaman: what do you mean?
19:18
<gbaman>
if i modify it in one, it will be the same on the other?
19:18
<alkisg>
(btw that was my first contribution for ltsp, and it was meant for review, not to be committed... :D)
19:18* gbaman = still new to all this
19:18
<Gremble>
I want to run a script as a user on login, how is that possible?
19:18
gbaman, I don't think they can be, tft daemons don't follow symlinks
19:18
<unkmar>
gbaman: no. not symlinked. and appear to have different things.
19:19
<Gremble>
the debian scripts should put things in both places
19:19
<gbaman>
oh...
19:19
<Gremble>
the ubuntu ones just put them in one place
19:19
<gbaman>
..
19:19
<Gremble>
its configurable iirc
19:19
<unkmar>
gbaman: tftpboot appears to have the bare min. to get booting started. Kernel things. /opt/ltsp is where the system appears to reside. At least from what I can tell.
19:20
<gbaman>
oops, forgot about that
19:20
<vagrantc>
alkisg: we put you on the hook by including your contributions, and look how well it worked!
19:20
<gbaman>
i discovered that yesterday and thought to myself i must remember this :)
19:21
<alkisg>
Gremble: to run something at login, you can for example call it from an /etc/xdg/autostart/*.desktop file (not related to LTSP)
19:21
<vagrantc>
unkmar: i think you'll need to edit or create /opt/ltsp/i386/etc/ltsp/update-kernels.conf and set an appropriate BOOTPROMPT_OPTS value
19:21
<Gremble>
ah, okay alkisg
19:21
<alkisg>
gbaman and unkmar, if you're getting nfs path not found errors, put the server in the kernel command line
19:22
<vagrantc>
unkmar: and what appropriate is ... well, working on that
19:22
<alkisg>
To verify that this is your problem
19:22
<Gremble>
there's a place for startup scripts though isn't there alkisg, within LDM ?
19:22
<alkisg>
Also, in the initramfs, `cat /proc/cmdline` will tell you the kernel command line, and `cat /run/net-eth0.conf` will show you the ROOTSERVER/ROOTPATH used
19:22
<vagrantc>
gbaman: you'll want to edit /opt/ltsp/i386/etc/ltsp/update-kernels.conf and append nfsroot=/opt/ltsp/i386 to the appropriate place.
19:23
<gbaman>
/opt/ltsp/i386 is the correct place though, isnt it?
19:23
<vagrantc>
gbaman: you will also want to specify IPAPPEND=2 in /opt/ltsp/i386/etc/ltsp/update-kernels.conf
19:23
<alkisg>
Gremble: not exactly. If you want to run something inside the session, you can't easily do it from the LDM scripts. So if you want to have e.g. DBUS_SESSION_BUS_ADDRESS set, use /etc/xdg/autostart
19:23
<unkmar>
gbaman: in my case it is amd64. So, maybe. :)
19:23
<vagrantc>
gbaman: does /opt/ltsp/i386 exist?
19:23
<Gremble>
cheers alkisg
19:24
<gbaman>
yes
19:24
it exists
19:24
<vagrantc>
gbaman: and you're trying to boot an i386 thin client?
19:24
<gbaman>
along with amd64 and of course armhf
19:24
yes, testing
19:24
i have not actually booted a normal thin client off this install yet
19:24
and you said get that working first
19:25
<vagrantc>
gbaman: but you'll also need to do more, just editing update-kernels.conf won't fix it.
19:25bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
19:25* gbaman sighs
19:25
<vagrantc>
gbaman: i thought you said you were getting nfsmount: need a path ???
19:25
<alkisg>
in udhcpc we have a hardcoded fallback of `rootpath=${rootpath:-/opt/ltsp/i386}` - that should default to <arch> there instead...
19:25
<gbaman>
i was getting that
19:25
<alkisg>
Ah sorry no we put it there
19:25
<vagrantc>
gbaman: so you have booted one... ?
19:26
<gbaman>
well, it booted and latched onto the proxy dhcp server then failed to connect
19:26
<unkmar>
what the? i have a lts.conf but not ltsp.conf. SO... Typo?
19:26
<vagrantc>
unkmar: ancient conceptual typo
19:26
we should've fixed that when we made ltsp 5, but we didn't
19:27
with ltsp 6, we may throw the whole thing away, so we'll fix it then.
19:27
<gbaman>
but it could reach though the initrd.img and that stuff though
19:27
<vagrantc>
although i should've moved it to a symlink ages ago.
19:27
<gbaman>
for LTSP 6, make it all easier :)
19:27
and keep everything in one folder....
19:27
not spread over the entire filesystem
19:28
anyways, back on topic :)
19:28
<vagrantc>
gbaman: so, after you've edited update-kernels.conf to add the nfsroot= and IPAPPEND=3 (or will 2 suffice?) you need to: ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels
19:29
unkmar: the stuff you need to do is similar to what gbaman is doing, but doesn't have the already existing update-kernels.conf ... you'll probably have to write it from scratch.
19:29
<alkisg>
ipappend 2 only suffices if the server ip is given in the command line
19:29
(with proxydhcp)
19:29
Otherwise ipappend 3 is needed
19:29
<gbaman>
wipe the entire update-kernels file?
19:29
<vagrantc>
gbaman: huh?
19:30
<gbaman>
it is already full of stuff
19:30
<vagrantc>
gbaman: no, edit it.
19:30
gbaman: look for a line that has boot=nfs, and add nfsroot=/opt/ltsp/i386 to that.
19:31
<gbaman>
BOOT_METHODS="NFS NBD"?
19:31* vagrantc doesn't see boot=nfs there.
19:32
<vagrantc>
ok, i'll go get my spoon :P
19:32
<gbaman>
i dont see it :) http://pastebin.com/ygZHAx00
19:32
that would be a good idea
19:32
<vagrantc>
gbaman: CMDLINE_NFS="root=/dev/nfs ip=dhcp boot=nfs nfsroot=/opt/ltsp/i386" ??
19:32
<gbaman>
..
19:32
sorry :)
19:33
<ltspuser_80>
@vagrantc any answer to my question?
19:33
<vagrantc>
ltspuser_80: i've been working on answering three questions at once, i guess i missed your respond
19:33
response
19:34
ltspuser_80: ah, you can configure LDM_SERVER="server1 server2 server3" in lts.conf
19:34
ltspuser_80: you'll also have to configure each of the ssh keys for those servers
19:35
ltspuser_80: if you want to connect to windows servers, you can use SCREEN_07=xfreerdp and configure that, but i'm not very experienced with that.
19:35adrianorg has left IRC (adrianorg!~adrianorg@177.132.223.183, Read error: Connection reset by peer)
19:35Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 276 seconds)
19:36adrianorg has joined IRC (adrianorg!~adrianorg@187.113.216.240)
19:36
<vagrantc>
gbaman: ok, so after you've added that, and set IPAPPEND=3 ... echo IPAPPEND=3 >> /opt/ltsp/i386/etc/ltsp/update-kernels.conf ...
19:36
<ltspuser_80>
so it is possible, but I have to have server running for each one?
19:36
<gbaman>
did do that, does anything need restarted after running ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels
19:36
?
19:36
<vagrantc>
gbaman: then: ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels ; ltsp-update-kernels
19:37
gbaman: then reboot and we'll see what goes wrong next
19:37kev_j has joined IRC (kev_j!~Kevin@63.225.43.68)
19:37
<vagrantc>
ltspuser_80: i don't understand what you mean about a server running for each one ...
19:37
ltspuser_80: that's for connecting to multiple different servers, so you need a different server to connect to ...
19:38
<gbaman>
it seems happy
19:38
<vagrantc>
whew.
19:38
<gbaman>
so, now i have a normal thin client...
19:38
<vagrantc>
gbaman: you'll need to do the same thing with the raspbian one, only replace i386 with armhf in all the instructions.
19:38
unkmar: so, you need to do something similar, but not exactly the same...
19:39
<gbaman>
ok, how hard could it be....
19:40
<vagrantc>
unkmar: just to be clear, you have a tftp server separate from the NFS server? where's your DHCP server?
19:40
<gbaman>
it also worked perfectly when i logged in, unlike edubuntu
19:40
<vagrantc>
gbaman: what desktop environment are you using?
19:40
<gbaman>
oh, of course
19:40
not unity :)
19:40
ignore that
19:41* vagrantc just asked out of curiosity
19:42
<gbaman>
ok, time to test a pi...
19:45
success, sort of
19:45
boots but no nice login screen, just a commandline login that does not work, i am sure turning on the gui is rather easy
19:45
and i think i even know how to do it, just have forgotten how :)
19:46
<vagrantc>
gbaman: maybe there's a howto somewhere that describes a fix...
19:46
<gbaman>
:)
19:46
<vagrantc>
i'm pretty sure it's a bug with the fact that plymouth is installed, but not used
19:46
<gbaman>
already checking that i have done what the howto says
19:47
<vagrantc>
gbaman: two workarounds, append "|| true" to the plymouth line in /opt/ltsp/armhf/etc/init.d/ltsp-client-core
19:47
gbaman: another option might be: ltsp-chroot --arch armhf apt-get --purge remove plymouth
19:47
hopefully i can get that fixed in the first point release of wheezy
19:48
<gbaman>
was sure i had already done that... fixed now, do i need to restart anything?
19:48
<ltspuser_80>
maybe if I take this from a different stance. I want to have 5 thin clients set up, when the user sits down, they can choose to boot into WIN 7, WIN 8, Ubuntu or OpenSuse. Is this possible?
19:50
<alkisg>
ltspuser_80: you can't boot windows remotely. You can only connect to windows servers from ltsp clients, with remote desktop
19:51Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
19:51
<alkisg>
(at least, from the ltsp implementation, it's possible to boot windows remotely with iscsi, ipxe etc but it's a whole different thing)
19:51
<vagrantc>
unkmar: you'll want to create /opt/ltsp/i386/etc/ltsp/update-kernels.conf with BOOTPROMPT_OPTS="quiet root=/dev/nfs ip=dhcp boot=nfs nfsroot=192.168.67.1:/opt/ltsp/i386" and IPAPPEND=3
19:52
<unkmar>
I have a dhcp server. (pfsense firewall) My nfs and tftp are the same machine.
19:52
<vagrantc>
unkmar: then: ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels ; ltsp-update-kernels
19:52
<alkisg>
ltspuser_80: So the users can choose if they want to connect to win7, win8, ubuntu, opensuse servers at login time, not on boot time. They'll always boot to linux, and select the server to connect at login.
19:52
<vagrantc>
unkmar: oh good. then it's easier.
19:52
unkmar: you'll want to replace 192.168.67.1 with the ip address of your ltsp server.
19:53
<gbaman>
vagrantc, is it meant to configured as a thin client?
19:53
<vagrantc>
gbaman: is what meant to be configured as a thin client?
19:53
<gbaman>
currently the pi does seem to be running as a thin client
19:53
instead of a fat client
19:54
<vagrantc>
gbaman: by default, it will configure as a thin client, unless you have lots of ram
19:54
gbaman: from here on out, there's nothing different with the rpi as any other thin client, really.
19:54
<gbaman>
thought the whole point was the pi was a fat client but grabbed its image from the server
19:54
oh, well in that case :)
19:55* gbaman hopes vagrantc can now put away his spoon and relax
19:55
<unkmar>
vagrantc: to be certain I was clear. The nfs and tftp are the same machine. The DHCP is separate.
19:55
<vagrantc>
gbaman: so you can: ltsp-chroot --arch armhf apt-get install <packages you want installed>
19:55
gbaman: and you'll want to set LTSP_FATCLIENT=true in /opt/ltsp/armhf/etc/lts.conf
19:55
gbaman: and marvel at the slowness
19:56
<ltspuser_80>
Ok so I have to set up a server for each OS I want them to be able to use, then They get the option at logon wich server to connect to?
19:56
<vagrantc>
unkmar: yeah, those instructions should hopefully work in your case :)
19:56
ltspuser_80: using LTSP, yes.
19:56
ltspuser_80: if you want to just network boot a bunch of different OSes, then it's not really LTSP.
19:57
unkmar: though at this point in time, you might want to try the newer version of LTSP in wheezy ... should be released early May.
19:57
<unkmar>
vagrantc: I don't have the ltsp directory. Stops at etc. /opt/ltsp/amd64/etc/
19:58
<vagrantc>
unkmar: ok, mkdir -p /opt/ltsp/amd64/etc/ltsp/
20:00
<ltspuser_80>
Vagrantc: what would a better option other then LTSP be?
20:03
<unkmar>
I'm not sure what is right. but those instructions can't be. the folder you said to ltsp chroot to doesn't exist.
20:03
<vagrantc>
ltspuser_80: depends on what you want
20:04
<gbaman>
well... it sort of worked...
20:04
again
20:04
<vagrantc>
unkmar: then: ltsp-chroot --arch amd64 /usr/share/ltsp/update-kernels ; ltsp-update-kernels
20:04
unkmar: sorry.
20:05
<ltspuser_80>
I want 5 diskless systems that the user can get a fully functions OS environment on, and chose it at some point.
20:05
<vagrantc>
ltspuser_80: define "fully function" ??
20:05
<gbaman>
i am now just getting https://dl.dropboxusercontent.com/u/1122948/temp/2013-04-22%2021.03.16.jpg
20:06
no lxde...
20:07
ah, lxde may not even be installed
20:08
<vagrantc>
gbaman: you'll need to install whatever software you want for the fat client into the chroot ...
20:08
gbaman: so you can: ltsp-chroot --arch armhf apt-get install <packages you want installed>
20:08
gbaman: and you'll want to set LTSP_FATCLIENT=true in /opt/ltsp/armhf/etc/lts.conf
20:08
<gbaman>
just did that to discover hundreds of packages :)
20:09
using qemu seems nearly as slow as doing it on the pi
20:09
<vagrantc>
what's your server?
20:09
<gbaman>
an old mac mini
20:10
<vagrantc>
yeah, it isn't particularly fast
20:10
though filesystem operations should be at native speeds, at least.
20:10
<gbaman>
in theory, if i wanted to move this entire OS to another machine, would that be as simple as cloning the file system and moving it?
20:11
<vagrantc>
gbaman: what do you mean by "move this entire OS" and and "cloning the file system and moving it" ?
20:12
<gbaman>
aka, set up perfect install on the mac mini but i want to move it to a machine with more power
20:13
just out of curiosity
20:13
<vagrantc>
why not build it on the machine with more power, if you're complaining about slowness?
20:13
<gbaman>
because i would have to do this all again :D
20:13
<vagrantc>
but yes, you can pretty much just move the directories around
20:14
<gbaman>
well, i guess that would work
20:14
<vagrantc>
gbaman: how are you going to learn it if you don't redo it dozens of times? :)
20:14
<gbaman>
that is also a good point
20:14
that goodness for IRC logs
20:14
*thank
20:15telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
20:16
<unkmar>
is there a default login user/pass combo?
20:16telex has joined IRC (telex!~telex@freeshell.de)
20:16
<gbaman>
isnt it just the login you use for normal server login
20:17
<ltspuser_80>
Access to network drives, and applications. Installing applications is not required
20:17
<unkmar>
gbaman: if so, it isn't working. And I get a refused connection error.
20:17
<vagrantc>
unkmar: did you get to a GUI login?
20:17
<unkmar>
You know. the login error loop.
20:17
vagrantc: yes.
20:18
<gbaman>
change the desktop environment!
20:18
<vagrantc>
unkmar: what desktop is default on the server?
20:18
unkmar: tail -F /home/USERNAME/.xsession-errors
20:18
<unkmar>
desktop, default on server? servers aren't supposet to have desktops.
20:19
<vagrantc>
unkmar: and see if that has anything new after loggin in?
20:19
unkmar: LTSP servers are essentially desktop servers.
20:19
unkmar: they serve desktops...
20:19
unkmar: and desktop applications
20:19
<unkmar>
....
20:19
<vagrantc>
unkmar: do you want a fat client install instead?
20:20
unkmar: how powerful are your thin clients?
20:20
<unkmar>
your are talking about the ltsp server, not the server machine that the .. sheesh.
20:20
<vagrantc>
unkmar: yes, the LTSP server.
20:21
<unkmar>
I don't see users in the /home of the ltsp server. so... I assume its currently empty.
20:21
<vagrantc>
unkmar: a typical LTSP server has at least tftp, NFS and whatever desktop applications you want to run on the thin client installed.
20:21
unkmar: can you SSH to your LTSP server with the same username and password?
20:22
unkmar: or do you want to set up a separate application server?
20:23
there are features of LTSP that can essentially be split into several parts ... DHCP server, TFTP + NFS or NBD server, application/desktop server
20:23
<unkmar>
Wait, wait. Yes, I need a desktop. No, I don't know what it crammed in there by default. and provided a script that I have been using to do this OVER and OVER again. Trying to work the bugs out so that MAYBE, someones won't fight all the same problems.
20:23
*I provided a script.
20:23
http://pastebin.com/X8x0uZH4
20:24
and I'm running TFTP and NFS.
20:25gentgeen__ has joined IRC (gentgeen__!~kevin@c-98-239-202-150.hsd1.pa.comcast.net)
20:25
<vagrantc>
unkmar: i don't really understand what you're doing in the "PXE - tftp daemon settings" section
20:25
<unkmar>
the clients are amd64 with at about 2Gb of RAM.
20:25
<vagrantc>
namely cp -r $tftp/amd64/pxelinux.* $tftp sed -i "s:kernel \|initrd=:&$os/:" $pxecf
20:26
unkmar: so you could very realistically do fat clients instead of thin clients, if you wanted to.
20:27
<unkmar>
the cp -r is copying the files from one level deeper down. Then I modify them.
20:27
<vagrantc>
unkmar: it looks like you're mangling the pxelinux configuration files rather than making sure they get generated correctly the first time...
20:28
<unkmar>
The modifications set nfsroot=/opt/ltsp/amd64 and fix the kernel and initrd path.
20:28
vagrantc: that is the problem. they DON'T get generated correctly to begin with.
20:29
<vagrantc>
unkmar: then something else must be failing much earlier...
20:29
<unkmar>
if th... (must calm down.) Um. I really appreciate your patients and assistance.
20:29
the slightly more blunt version would be. It ain't working out of the gate.
20:30alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
20:30
<unkmar>
if it had been working, I wouldn't be here. I would be happily configuring the clients from a successful setup as of wednesday of last week.
20:30
<vagrantc>
unkmar: i've done countless default installs and i've never seen the need to modify the initrd path...
20:31
adding nfsroot= is needed in cases where you're not able to specify the root-path via DHCP
20:32gbaman has left IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com, Remote host closed the connection)
20:32
<unkmar>
well, with my initial clean server only install. it didn't even see pxelinux.0 to do its booting.
20:32
vagrantc: so yeah, I've mangled the heck out of it to get it working at all.
20:32
<vagrantc>
but adding commandline options should be done by editing /opt/ltsp/<arch>/etc/ltsp/update-kernels.conf and setting BOOTPROMPT_OPTS= appropriately (and your version)
20:33
unkmar: so, what confuses me is what's different about your setup than a default setup, other than the DHCP server handled by something else
20:33gbaman has joined IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com)
20:34
<unkmar>
vagrantc: no sarcasm here. I'd be happy to go through another CLEAN install and start from there. so we can hash out the problem. I don't simply want it working. I want it fixed. I want us ALL to know where and why it isn't working. Which is one of the main reasons I came here.
20:34
<ltspuser_80>
Vagrantc: Access to network drives, and applications. Installing applications is not required
20:36
<vagrantc>
unkmar: i've got a few more hours to be around, although i was planning on doing other things today
20:37otwieracz has left IRC (otwieracz!~gonet9@v6.gen2.org)
20:37
<vagrantc>
ltspuser_80: the short of it is, you can do some of that with LTSP. you could also with some OSes network boot a "live" version of the OS. if you have thin clients with lots of RAM and processor, you can run applications on the local client hardware...
20:38
unkmar: or you could file a bug report against ltsp-server with the exact details of what you did, what wasn't right (i.e. i'd want to see a cut-and-paste of the generated pxelinux.cfg/default, then i could get to that way
20:38
<unkmar>
vagrantc: starting debian install, I'll be back in about 30-60 minutes
20:40
vagrantc: I'm guessing a bug report comes with creating an account with login and... well, you get the idea.
20:42
<vagrantc>
unkmar: no, just an email
20:46naboo has left IRC (naboo!~naboo__@aflc132.neoplus.adsl.tpnet.pl, Remote host closed the connection)
20:46naboo has joined IRC (naboo!~naboo__@aflc132.neoplus.adsl.tpnet.pl)
20:51ltspuser_80 has left IRC (ltspuser_80!401a8e82@gateway/web/freenode/ip.64.26.142.130, Ping timeout: 245 seconds)
20:53alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
21:00
<unkmar>
okay. so.. I have a clean install of debian squeeze. deselected Graphical Desktop and selected Web server, SQL, and SSH.
21:04
vagrantc: I would assume my next step is to aptitude install tftpd-hpa ltsp-server
21:07
<vagrantc>
unkmar: that'd work, sure ... though you will eventually want to install some desktop environment...
21:08
<unkmar>
vagrantc: No. I don't want a desktop on the server it self. Only on the clients. I have zero need for a desktop at the server level.
21:08
<vagrantc>
unkmar: ok, then you want fat clients
21:08
<unkmar>
right
21:08
<vagrantc>
unkmar: so once the ltsp-build-client completes, you'll want to install a few things.
21:09
unkmar: though honestly, fatclient support is far better on wheezy
21:09
unkmar: it was pretty rough around the edges for squeeze
21:09
unkmar: you might be able to use squeeze backports for the ltsp components
21:09
if you really need squeeze rather than wheezy
21:09
<unkmar>
ok, fine. I'll reinstall again. This time with wheezy.
21:10
<vagrantc>
dist-upgrade should be fine
21:10
<unkmar>
It'll only be my first wheezy install because it was so freaking hard to find the installer.
21:10
freaking CD hybrid instal to usb crap.
21:10
<vagrantc>
ok, i have a fair amount of patience, and i understand you're frustrated, but please keep the attitude in check
21:11
helping people is a hobby i enjoy, but only so far as they help keep it fun
21:11gbaman has left IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com, Remote host closed the connection)
21:13Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Quit: Leaving.)
21:14
<unkmar>
I hate upgrades. I've almost never had one go well. My most successful upgrades have been fresh installs and copy data over.
21:14bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 252 seconds)
21:15* vagrantc has upgraded debian machines over the course of 4 releases without much trouble
21:16
<vagrantc>
which spanned nearly a decade...
21:16
<unkmar>
I can't speak for Debian. the last time I attempted an upgrade was Ubuntu and it went horribly wrong.
21:17* vagrantc nods
21:17
<vagrantc>
they do some things differently
21:18
<unkmar>
It was 8.04 to 10.04. Since then. I now have one 6.06 system that has never been upgraded and another 8.04 that will not be upgraded.
21:18
<vagrantc>
unkmar: so now you're trying Debian?
21:18
<unkmar>
Eventually, I'll do a fresh install on both those Ubuntu systems. And they will not get ubuntu.
21:19
yes. been using debian for a few years and it hasn't been perfect peaches. Always feels a bit out dated. however...
21:19
Everything that works. Just works.
21:19
With Ubuntu things would sometimes sorta, kinda half work and destroy other things.
21:20
I've had my struggles and have been much happier with Debian.
21:20Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
21:20
<vagrantc>
well, hopefully it will continue to work for you...
21:21
<unkmar>
most of my problems with debian have been from us both being of a similar mindset. Obstinate to bow down to the DRM and other power monger overlord. Sun, Adobe, and the like.
21:22Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Client Quit)
21:22
<unkmar>
It is unfortunate that gnash has been so horrible. I've been rather forced to use the adobe flash or not at all.
21:23
Don't get me wrong. It sorta works and is far more than I could ever dream to accomplish with it.
21:23
And I have faith they will get it there. So, there is hope. Along with the hopeful moves towards the other HTML5 standards.
21:24* vagrantc nods
21:24
<unkmar>
vagrantc: okay, so the dist-upgrade is finished.
21:24
<vagrantc>
rebooted and everything?
21:25
<unkmar>
nope, that would have required me to think. :) LOL
21:25
It's rebooting now. :D
21:25
<vagrantc>
ok, so install ltsp-server (should pull in tftpd-hpa by default)
21:25
and then ltsp-build-client
21:26
i'd also recommend using approx for a local mirror, to minimize the need to re-download things
21:26
<unkmar>
well, it was already installed. before the upgrade
21:26
I'll check my history. I'm fairly sure I haven't run ltsp-build-client yet.
21:26
<vagrantc>
or use: ltsp-build-client --mount-package-cache
21:27
or use: ltsp-build-client --mount-package-cache --keep-packages
21:27
that way if you have to reinstall, you won't have to re-download the packages
21:27
<unkmar>
yeah, that's funny. install ltsp-server didn't pull in tftpd-hpa in squeeze. :(
21:27
<vagrantc>
might have had recommends disabled?
21:29
i think it's a recommends, not a depends
21:31
<unkmar>
.....
21:31
aptitude reinstall.... not currentlly installed.... pi ltsp-server... so It is both installed and not installed.....
21:32
aptitude install ltsp-server... following packages, blah blah... rpcbind: Conflicts: portmat...
21:32sunweaver has left IRC (sunweaver!~mike@fylgja.das-netzwerkteam.de, Ping timeout: 252 seconds)
21:32lee has left IRC (lee!~lee@loathe.ms, Ping timeout: 252 seconds)
21:32sunweaver has joined IRC (sunweaver!~mike@fylgja.das-netzwerkteam.de)
21:33lee has joined IRC (lee!~lee@loathe.ms)
21:33
<unkmar>
so, yeah. I'm ready to do a CLEAN install of wheezy. "I told you I don't like upgrades"
21:34
It appears the, its best suggestion is to remove portmap
21:35
This has been my first experience with ltsp, portmap, rpcbind, and nfs. So, I'm kinda flying blind.
21:36Parker955_Away is now known as Parker955
21:37
<unkmar>
I just ran ltsp-build-client. I'll see where that gets me and I guess I'll be back at this tomorrow. whether it works or not.
21:38vbkoqorbxki has joined IRC (vbkoqorbxki!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
21:39|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Read error: Connection reset by peer)
21:39vbkoqorbxki is now known as |Paradox|
21:46
<vagrantc>
unkmar: make sure all your packages are in a proper state ... there's no sense running ltsp-build-client from an unclean state
21:46
oh, aptitude ... i never touch that.
21:48Gremble has left IRC (Gremble!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com, Quit: I Leave)
21:49
<unkmar>
vagrantc: okay, so.... tftpd is running and.... pxelinux.0 TFTP error 1 (File not found)
21:50
and.. Yet again I got errors about /etc/exports not being setup. soo... Either the built-in scripts don't handle that for me OR. I did a dist-upgrade instead of a CLEAN install and... it got me again.
21:51
vagrantc: don't get me wrong. I use to be the upgrade king. I'd battle the messes and get'r done. Ain't no sense it running around in circles and possibly leaving unknown messes when you can just do it right from a clean install.
21:54
vagrantc: and my computer just when down. If I weren't logged in via remote through irssi in a cli. I couldn't type to you now over the dist-upgraded system.
21:54
<vagrantc>
unkmar: /etc/exports needs manual configuration
21:55
i doubt your problems are relating to dist-upgrading
21:55
<unkmar>
Every watch hee haw? "If it weren't for bad luck, I'd have no luck at all. Gloom dispare and agony on me, Wooo." :D
21:56
I jest a little there. I wouldn't have a prayers chance or hope of getting this fixed if you weren't here. You're my silver lining in some dismel clouds.
21:56
<vagrantc>
unkmar: so you still have some packages in an unclean sate?
21:56
state
21:59
unkmar: and had you completed ltsp-build-client ?
21:59
<unkmar>
heck if I know. I haven't done the /etc/exports thing yet. Waiting on vim
21:59
I previously had NOT done the build. I did the build only AFTER the dist-upgrade.
22:00
<vagrantc>
but it sounded like your dist-upgrade didn't go cleanly ... you had some packages in an unfinished state
22:01
<unkmar>
vagrantc: do I *normally* need to manually configure /etc/exports?
22:02
<vagrantc>
unkmar: yes
22:03
hrm. i seem to have the same problem as alkisg ... people littering https://wiki.debian.org/LTSP/Howto with bad information, or obscuring good information...
22:03
*sigh*
22:03
<unkmar>
okay, then I either need to know what the manual setting is suppose to be or... I need to logout of this screen long enough to discover what it suggested.
22:04
<vagrantc>
although, overall, it's not looking *too* terrible.
22:04
/etc/exports: /opt/ltsp *(ro,no_root_squash,async,no_subtree_check)
22:04
<unkmar>
Thank you.
22:05
<vagrantc>
i need to probably just re-write the howto from scratch
22:07
with wheezy, "ltsp-config" is a really useful helper for configuring some services ... although i completely spaced getting /etc/exports.d configuration in there... ugh.
22:07
i've mostly been using dnsmasq for tftp and dhcp lately, though have a few setups still using isc-dhcp-server and atftpd or tftpd-hpa
22:08
<kev_j>
what is the diff between atftpd and tftpd-hpa?
22:09
<unkmar>
vagrantc: it still doesn't work.
22:09
<kev_j>
or is there any significant difference?
22:10
<unkmar>
you know. the exports problem won't come into play until after it starts booting the pxelinux image that it doesn't find.
22:15
. /etc/default/tftpd-hpa appears to be configured properly.
22:17alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, *.net *.split)
22:17laurense has left IRC (laurense!~laurens@nerd-herd.nl, *.net *.split)
22:17Parker955 is now known as Parker955_Away
22:17alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
22:17laurense has joined IRC (laurense!~laurens@nerd-herd.nl)
22:18
<vagrantc>
kev_j: the big difference is supporting symlinks and more useful logging
22:18
<kev_j>
unkmar: is there a pxelinux file/folder in /srv/tftp/ltsp/i386? (or other arch)
22:18
<vagrantc>
kev_j: atftpd seemed better at those, although dnsmasq is better
22:18
at least, i like it better
22:18
unkmar: do you have next-server configured on your DHCP server?
22:19
unkmar: otherwise, it'll try to download tftp from your DHCP server
22:19
unkmar: or did you get past pxelinux.0 not downloading?
22:20
<unkmar>
The DHCP server isn't the problem. I'm not getting past pxelinux.0. Keeps giving me file not found. as if tftp is pointing to a directory that doesn't have one.
22:20
and I say as if. Cause I'm see a pxelinux.0 ...
22:21
that's it. There it is again. I am unforntunately seeing EXACTLY what I expect to see. It's pointing to /srv/tftp and there is a ltsp/amd64 with the files I need and...
22:21
Well, it isn't pointing to either of those.
22:22
In other words. ltsp-server doesn't setup /etc/exports for me. And apparently doesn't setup /etc/default/tftpd-hpa for me.
22:26
<kev_j>
my /etc/default/tftpd-hpa is pointing to /srv/tftp as well, then the dhcp config file seems to point to the folder/file for pxelinux
22:27
so altogether the client goes through /srv/tftp/ltsp/i386/pxelinux.0
22:27
as far as I can tell anywho
22:28
<unkmar>
kev_j: and I'm not running dhcp on this machine so... I would have to specify the other location at pfsense and.. I suspect all the setting simply won't work in that configurations but. What do I know. I'm following instructions. Not writing them.
22:29
<kev_j>
which is why vagrantc mentioned the next-server option needing to be configured
22:29
otherwise it is going to be looking for the pxe files on the dhcp server
22:29
which you said isn't the same server
22:30
<unkmar>
no, it looks on the tftp server for pxelinux.0. NOT some/path/pxelinux.0 That I did not expect and it appears wrong, odd and strange.
22:32
<kev_j>
it uses to dhcp configuration file to tell it where the pxelinux.0 file is using the option 'filename "/ltsp/i386/pxelinux.0";'
22:33
<unkmar>
okay. its loading the pxelinu.... nfsmount: need a path
22:35
<vagrantc>
unkmar: by default, it will attempt to download tftp from the same server that handed out the DHCP request. have you configured DHCP to tell it to look for a different tftp server?
22:36
unkmar: are there files in /srv/tftp/ltsp/amd64 and/or /var/lib/tftpboot/ltsp/amd64 ?
22:36
<unkmar>
vagrantc: yes, and it now loads the .... ltsp/amd64/pxelinux.0 file Instead of my previous settings of pxelinux.0 at the DHCP server.
22:37
vagrantc: I am back to the nfsmount: need a path error.
22:37
<vagrantc>
ok.
22:38
<unkmar>
This time, I already have a /opt/ltsp/amd64/etc/ltsp/update-kernels.conf file.
22:38
<vagrantc>
unkmar: good, edit that to append nfsroot=192.168.67.1:/opt/ltsp/amd64 to the CMDLINE_NFS= line
22:39
changing 192.168.67.1 to the ip address of your LTSP server
22:39
<unkmar>
so, that is now. Not one but 2 files it could have done for me.
22:39
<vagrantc>
?
22:39
<unkmar>
ip's can be gathered at boot.
22:39
<vagrantc>
or, configure your DHCP server to specify root-path a.k.a. option 17
22:40
unkmar: does your LTSP server have a static ip address?
22:40
<unkmar>
I don't see any form of append option in my DHCP server settings. Only an ip and file name.
22:40
vagrantc: yes, it has a static ip that comes from the DHCP, preconfigured based on MAC.
22:41
<vagrantc>
unkmar: ok, then you'll need to add it to the boot config, i.e. edit update-kernels.conf, run update-kernels, run ltsp-update-kernels
22:41
unkmar: ok, that should be fine.
22:42
unkmar: so ... have you edited update-kernels.conf ?
22:43
<unkmar>
yeah, trying to think of what the re.. there it is 2 lines up ^^^
22:44
so, if this works it is. It doesn't work.
22:45
nfsmount: need a path. so, what am I still missing?
22:45khildin has left IRC (khildin!~khildin@ip-83-134-213-112.dsl.scarlet.be, Quit: I'm gone, bye bye)
22:46
<unkmar>
I was gonna say that if it works, it is much easier than I had been battling. And could still use a few more tweaks.
22:47
<vagrantc>
unkmar: we're not done yet...
22:47
unkmar: so what were the last steps you did?
22:48losjl has joined IRC (losjl!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
22:48
<unkmar>
nfsroot=blah:blah and ltsp-update-kernels (without options)
22:48
Hmm, I missed a step.
22:48
<vagrantc>
yup
22:49
ltsp-chroot --arch amd64 /usr/share/ltsp/update-kernels
22:49
*then* ltsp-update-kernels
22:49
and then, before booting, make sure the append line looks right in /srv/tftp/ltsp/amd64/pxelinux.cfg/default
22:49
i.e. contains the nfsroot= entry
22:51|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Ping timeout: 276 seconds)
22:51
<unkmar>
yeah, but I'm in the login loop.
22:52
so, now I need to addusers to the nfs client system?
22:52
<vagrantc>
well, you wanted fat clients, right?
22:52losjl is now known as |Paradox|
22:52
<unkmar>
yes
22:52
<vagrantc>
unkmar: are these anonymous logins, or logins with passwords and such?
22:53
<unkmar>
uh, I haven't asked my boss yet. I know what I prefer but... well, bosses can be weird about things like that. :P
22:54
<vagrantc>
well, you've got a variety of options ... the default option for fat clients would be to give them an account accessible via ssh on the server
22:55
<unkmar>
I'd prefer separate logins per user with a proper skeleton. They clients are all CSR's so.. the boss may just have them all use a single standard anon.
22:55
In fact, I really think that is what he wants. :/
22:56
vagrantc: describe the account via ssh a little more.
22:56
sounds like the gui would be almost completely locked and the same for all with separate accounts, drive space and some configurability thereafter.
22:57
<vagrantc>
unkmar: let me redescribe it a bit ... do the accounts need to save documents, or is it ok if everything is deleted at login?
22:58
if the latter, you can just set up the users without any accounts on the server
22:59
you can set up the users essentially at boot or login time
22:59
<unkmar>
so, um. Sounds like they don't need storage.
22:59
<vagrantc>
if you need persistance, you'll need to set up the accounts on the server so that they can store their homedirs on the server.
23:00
<unkmar>
Just asked one of the CSR's. If I wiped her system and gave her a new one if she would lose anything. Any settings or anything. She said no. We share stuff over net.
23:00
<vagrantc>
CSR?
23:01
<unkmar>
Customer Service Representive.
23:01
Phone answering people that talk to people to keep us in business. :)
23:01
<vagrantc>
so you might be able to do something using the kiosk mode.
23:02
typically, it's just a web browser and nothing else, but you could run a full session if you wanted.
23:02
<unkmar>
yep, pretty much, They need a browser and an email client. Chrome and Thunderbird are preferred.
23:03
They share an email account among all the CSR's. its a really bad setup but... that's they way they work at the moment.
23:03
<vagrantc>
well, this is definitely getting into a pretty customized setup...
23:04
<unkmar>
oh, that's not an issue. I'll handle the customizing. I'm just looking to get the generic anon login going.
23:04
<vagrantc>
unkmar: just to test things a bit, i'd do something like ltsp-chroot --arch amd64 apt-get install lxde ; adduser testuser
23:04
<unkmar>
I should be able to handle it from there with chroot and such. :)
23:04
<vagrantc>
and play around with the fat client setup
23:05
i've tested the kiosk stuff fairly recently with debian wheezy, made some fixes and such, but it isn't the path most tread (as far as i know) so there may be glitches
23:06
<unkmar>
looks like there would be an alias for that ltsp-chroot thing.
23:06
<vagrantc>
?
23:06
it's a wrapper around plain chroot
23:06
unkmar: actually, you could probably get by with just ltsp-chroot apt-get install ...
23:07
but given we've had 3 architectures discussed today, i was being explicit with the --arch option.
23:07
<unkmar>
I know. it is is clever and easier. Ah, see that was more like I was expecting. I'm only doing one --arch.
23:07
<vagrantc>
if you have multiple chroots, sometimes it might not pick the one you think (though it should default to the same arch as the host server)
23:08
<unkmar>
vagrantc: so, can I buy a beer? I don't really drink the stuff, but I hear that is how the geeks tend to do their celebrating or saying thank you. :)
23:08
vagrantc: Yeah, I assumed it defaulted to the servers arch, and since the server is using the same and... is literally one of the thin clients repurposed. All should be good. :D
23:09
<vagrantc>
unkmar: haven't been drinking lately, but would happily take bitcoin or namecoin donations :)
23:10
<unkmar>
I don't have any of those fancy digital coin thingies. I do have a tiny bit in my paypal I could send your way
23:11
<vagrantc>
unkmar: haven't toyed with paypal at all ...
23:11
<unkmar>
I didn't put that argument in quotes. won't that adduser only run locally? no through the chroot?
23:11alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, *.net *.split)
23:11laurense has left IRC (laurense!~laurens@nerd-herd.nl, *.net *.split)
23:12alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
23:12laurense has joined IRC (laurense!~laurens@nerd-herd.nl)
23:12
<vagrantc>
unkmar: as long as you prefix it with ltsp-chroot, it'll run in one of the LTSP chroots (and sounds like you only have one)
23:13* vagrantc doesn't have any bitcoin/namecoin either
23:13
<unkmar>
vagrantc: LOL, not surprised. I've been wanting to get some as well.
23:14
<vagrantc>
figured giving tech advice in my area of expertise might be more productive than figuring out mining :)
23:14
<unkmar>
sweet. I'm a very happy camper. Its probalby useless to the minions as is at the moment. But it is framework with which I can work into shape.
23:15
<vagrantc>
exactly
23:15
LTSP is very flexible if you're willing to experiment a bit
23:15
<unkmar>
I can now aptitude, apt-get or whatever I wish to make it all copesetic.
23:15
<vagrantc>
unkmar: your DHCP server was a pfsense box?
23:16
<unkmar>
vagrantc: yes.
23:16
<vagrantc>
unkmar: do you know if it's running isc-dhcpd ?
23:16
unkmar: or dnsmasq?
23:16
<unkmar>
I don't know. Not sure how to ask it without enabling ssh. I didn't set it up and haven't use pfsense much so I haven't tangled with it much yet.
23:17
<vagrantc>
surely it has the capability to be configured to pass the root-path option over the network, even if the interface you were using didn't make it obvious
23:17
that would obviate the need to do all that mangling with update-kernels
23:17
<unkmar>
oh, yeah. I'm sure it does. It has ssh available. I could have done that.
23:18
Wouldn't the /etc/exports edit still be required?
23:18
<vagrantc>
just figured i'd mention that ... often people come in with DSL routers or something and it's a little more hopeless
23:18Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
23:18
<vagrantc>
unkmar: yeah, /etc/exports edits are still required
23:19|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Remote host closed the connection)
23:19
<unkmar>
I wouldn't have even dreamed of trying to get this working withou.. well. I would have done double NAT and if they didn't like it. Tough. :)
23:19
<vagrantc>
unkmar: i really missed the ball on that one ... i had the idea of how to get it automated over a year ago, but for some reason forgot
23:19|Paradox| has joined IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
23:20
<unkmar>
heh. More like dropped the ball. Probably pulled away on one of 15 other projects.
23:20
<vagrantc>
unkmar: yeah, the two-NIC setup is the traditional LTSP recommended setup...
23:20
yes, dropped the ball, heh.
23:21
was caught half-way between missing the boat and dropping the ball
23:21
<unkmar>
Very easy to get sidetracked in our line of work. So much happens in tiny time spans.
23:21
LOL
23:21
<vagrantc>
anyways, glad we got somewhere
23:21
<unkmar>
You hang here all the time? got any other haunts I might sometimes catch you in?
23:22Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Client Quit)
23:22
<vagrantc>
i'm here when i'm online generally
23:22
<unkmar>
And thanks. I'll be heading home in a few. I new we would get it after my broken laptop was miraclous not broken.
23:22
<vagrantc>
i hang out in a number of debian channels on oftc, mostly
23:22
<unkmar>
At that point, I knew my horrible bad streak had shifted. These things have been beating me for weeks now.
23:23
<vagrantc>
unkmar: gotta roll. till next time!
23:23* vagrantc waves
23:23
<unkmar>
I haven't been battling the ltsp for weeks. I mean the several other computer related tasks have killing me.
23:23
later.
23:26brunolambert has left IRC (brunolambert!bruno@nat/revolutionlinux/x-qooigmaazustjpad, Quit: Leaving.)