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


Channel log from 27 May 2012   (all times are UTC)

00:38
<msignor>
vagrantc: seems like i broke it now
00:39
i get the ubuntu boot screen.. but never get a login, probably because i loaded updates and chose the wrong gdm or ldm
00:41
<vagrantc>
hm.
00:46
hrm. getltscfg is resistant to hardening....
00:46
probably need to switch to an autofoo makefile or something.
01:21Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
02:02Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
02:06
<vagrantc>
alright, managed to trick getltscfg into using hardening flags... would still be better to rewrite the Makefile or turn it into autofoo.
02:35Parker955_Away is now known as Parker955
02:41adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.179.2, Ping timeout: 244 seconds)
02:57Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Quit: Leaving.)
03:57alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
03:59
<vagrantc>
alkisg: whee!
03:59
alkisg: is it sunday yet?
03:59
<alkisg>
Heeelllo :)
03:59
Yup, work day for me!
03:59
So, want me to rewrite getltscfg in shell? :P
03:59
<vagrantc>
hah!
04:00
i got getltscfg sorted out
04:00
so, ltsp-update-image borks when using the create-fs-image plugin
04:00
<alkisg>
Let me see yesterday's logs, I read about the "solution" but not the problem
04:00
<vagrantc>
er, ltsp-update-kernels
04:01
alkisg: i made a patch for getltscfg's Makefile so that hardened build flags would work properly
04:01
<alkisg>
What does that mean? I haven't heard the "hardened" in programming... some restrictive gcc options?
04:01
*word
04:01
<vagrantc>
alkisg: yup
04:02
https://wiki.debian.org/Hardening
04:02
<alkisg>
Cool, since we're making changes to it, would anyone mind if I removed the restrictions that (1) [default] must be on top, and (2) sections must not be empty?
04:02
<vagrantc>
it's the cool new thing ... though in theory ubuntu's been doing it for ages
04:02
alkisg: first i need sanity restored to ltsp-update-kernels :P
04:02
<alkisg>
I mean, that if no section exists, [default] could be assumed
04:02
Hehe, ok
04:03
What's the problem there exactly?
04:03
<vagrantc>
alkisg: pullinng the kernels and pxelinux configs from thhe image hurts.
04:03
look, my typing's even off-kilter
04:03
<alkisg>
Lets prefer pulling them from the dir first
04:03
<vagrantc>
that'd fix it... i was thinking of committing them myself, but i wanted to ask you first
04:03
<alkisg>
Is the only problem pxelinux.cfg?
04:04
If we preserved user changes in pxelinux.cfg/default, would that be better?
04:04
<vagrantc>
it also breaks the create-fs-image plugin
04:04
becausse it tries to mount the image whiile it's already mounted
04:04
<alkisg>
...why would that hurt though?
04:04
It's possible to mount an image twice
04:04
Let me open it...
04:05
<vagrantc>
well, it causes mount to error out and ltsp-build-client fails
04:05
<alkisg>
What error message?
04:07* vagrantc re-runs to watch
04:07
<alkisg>
Whoo a lot of commits yesterday
04:07
<vagrantc>
very small, mostly
04:07
still today for me :)
04:08
<muppis>
vagrantc, it was 6.30 when my kids waas awake.. :)
04:08* alkisg refers to days in UTC time :P
04:09
<vagrantc>
alkisg: meh. all i get is "
04:09
"Command exited with non-zero status 1"
04:09
<alkisg>
...
04:10
Are you using any unsupported command line options?
04:10
<vagrantc>
unsupported by what?
04:11
<alkisg>
by ltsp-update-kernels
04:11
UPDATE_IMAGE_OPTIONS="-a ${CHROOT}" ==> could become: UPDATE_IMAGE_OPTIONS="${CHROOT}"
04:11
<vagrantc>
hmmmm... this time it woorked fine.
04:11
<alkisg>
...wait, 035-create-fs-image doesn't call ltsp-update-image nor ltsp-update-kernels now, does it?
04:12
<vagrantc>
alkisg: oh, i fixed that wrong ... i just removed the -a CHROOT stuff entirely.
04:12
alkisg: ltsp-update-kernels is called from common/095-update-kernels
04:13
<alkisg>
035? Is that late enough?
04:13
It should be after 035-create-fs-image
04:14
<vagrantc>
it used to be late enough
04:14
<alkisg>
mount -o loop $FS_IMAGE_FILE.new $ROOT ==> when does that get unmounted btw?
04:15
<vagrantc>
there is (was?!) a trap call to unmount stuff
04:15
<alkisg>
Only if you use mark_mount
04:15
...or not?
04:16
<vagrantc>
alkisg: server/ltsp-build-client: on_exit function
04:16
which is called with trap
04:17
alkisg: it seems it is ltsp-update-sshkeys that's killing it
04:17
<alkisg>
OK, although we should probably move to using "mark_mount" so that the unmount works even before you set CHROOT_MOUNTED
04:18
<vagrantc>
mark_mount is the new kid
04:18
<alkisg>
...why would ltsp-update-kernels interfere with ltsp-update-sshkeys though? :-/
04:19
<vagrantc>
i don't thinnk it's ltsp-update-kernels fault anymore
04:19
it spits out "No LTSP chroots found, please run ltsp-build-client"
04:19
which is kinda funny, cuz... well, i'm in the middle of running ltsp-build-client :)
04:21
it's running from 030-update-sshkeys
04:21
although, it should still be mounted at that point
04:21* vagrantc is confused
04:22
<vagrantc>
and on_exit fails to unmount...
04:22
ugh.
04:22
<alkisg>
I saw that "sync" is necessary sometimes before unmount
04:23
umount_marked should be more efficient
04:23
We could at least copy some of its code in the ltsp-build-client trap
04:23
<vagrantc>
hah.
04:23
i'm building a chroot without ssh
04:24
<alkisg>
Aaah ok :)
04:24
<vagrantc>
so ltsp-update-sshkeys fails if you don't install ssh (i.e. ltsp-client-core only)
04:24
seems like it ought to handle that a little better.
04:24
<alkisg>
We do need better error handling/messages in a lot of places...
04:25
<vagrantc>
this "set -e" business will improve the code, but at what cost to our sanity :)
04:26* vagrantc forgot about the --debug mode
04:26
<vagrantc>
which isn't hugely useful except to figure out exactly which plugin is failing
04:26
how hard would it be to specify a plugin name to run with "set -x"
04:26
<alkisg>
Should be quite easy
04:27
<vagrantc>
ok, back to my original problem...
04:28
mount: /dev/loop1 already mounted or /tmp/tmp.fsgsdgsh busy
04:28
"Could not mount /tmp/tmp.dgsdgsdgfsd
04:30
so mark_mount tried to mount it, and failed ...
04:30
<alkisg>
Hmm it seems that loop devices can't be mounted twice
04:30
<vagrantc>
ta-da.
04:30
<alkisg>
2 easy ways around it:
04:31
Either run ltsp-update-kernels at a later stage, when it's unmounted,
04:31
or have it prefer the dirs instead of the images
04:31
Let's do the second one for now?
04:31
<vagrantc>
if it preferred the dirs instead of the images, it would make testing updates not require running ltsp-update-image
04:33
and ltsp-update-kernels bailing when /etc/ssh isn't present ... hrm.
04:33
<alkisg>
...I don't think it checks /etc/ssh...
04:43
<vagrantc>
alkisg: by the way, successfully built an Ubuntu precise chroot by specifying "VENDOR=Ubuntu ltsp-build-client ..."
04:43
<alkisg>
Whoo!
04:43
I'll try to do the same for debian chroots from ubuntu
04:43
<vagrantc>
after a few fixes
04:43
now committed
04:44
alkisg: test -d "$chroot/etc/ssh" || continue
04:44
you'd think thata wouldn't kill it, though ...
04:45
ah, that's not what kills it
04:45
it's that there are no chroots ...
04:45
die "No LTSP chroots found, please run ltsp-build-client"
04:45
that's what kills it
04:45
<alkisg>
But why? Don't you mount the fs image under /opt/ltsp/<arch> ?
04:46
Or, why did it work before?
04:46
Or if you want to mount it in e.g. /tmp, you can run BASE=/tmp ltsp-update-sshkeys
04:47
<vagrantc>
alkisg: it is mounted, but it's just not got /etc/ssh ... so ltsp-update-sshkeys doesn't think it's a valid chroot, and it finds no valid chroots, and "exit 1" is the end result.
04:47
<alkisg>
Aah ok that's proper response then
04:47
<vagrantc>
sort of.
04:48
<alkisg>
Maybe ltsp-update-sshkeys || true ?
04:48
<vagrantc>
it's a valid use-case to install LTSP without ssh
04:48
<alkisg>
Sure, but ltsp-update-sshkeys should return 1
04:48
<vagrantc>
right.
04:48
<alkisg>
ltsp-build-client can just ignore the result
04:48
<vagrantc>
alkisg: yeah, that's the simplest workaround
04:48
<alkisg>
But please put a comment on why the || true is needed
04:49
Or check if etc/ssh exists before calling it
04:49
<vagrantc>
what about checking for something else, like /bin/true ?
04:50
and then just creating /etc/ssh in the chroot?
04:50
<alkisg>
I don't think so, ltsp-update-sshkeys shouldn't create /etc/ssh, it should fail, because it doesn't succeed in its purpose
04:51
Ah
04:51
Well we may consider that it succeeds if it copies the file even if ssh isn't installed, ok
04:51
The user might install ssh later on... sounds fine
04:52
<vagrantc>
heh. i just wrote up my rationale on using || true :)
04:55
alkisg: so, the other outstanding issue is ... do i have ltsp-build-client write BOOTPROMPT_OPTS to update-kernels.conf when using --create-fs-image or --squashfs-image ?
04:56
<alkisg>
vagrantc: for nbd booting in debian? I think so, yeah
04:59
<vagrantc>
now both varieties can at least use the same boot prompt options
05:04
<alkisg>
Are you using nbdroot=, or ROOTPATH?
05:04
(dhcp)
05:05
<vagrantc>
alkisg: i need to use nbdroot=/opt/ltsp/$ARCH
05:05
<alkisg>
vagrantc: why?
05:06
<vagrantc>
alkisg: i think there's a bug in the ldm screen script that i may have fixed ... so long-term, i probably don;t need it
05:06
<alkisg>
ok
05:06
<vagrantc>
or maybe worked around and forgot
05:07
alkisg: basically, if you don't specify nbdroot on the commandline, the "old NBD image, rebooting" feature kicks in
05:07
<alkisg>
Whoah
05:07
<vagrantc>
i tracked it down at one point, but i guess i didn't commit a fix
05:10
or i did, and some other issue is triggering it
05:10
<alkisg>
I don't like having to mount the nbd image to check if a reboot is required
05:10
Why don't we put that info in ldminfod?
05:12
<vagrantc>
yeah, i always thought that was a bit much
05:12
<alkisg>
People also see the disconnects in the server's syslog and think there's a problem there...
05:13
<vagrantc>
what would go in ldminfod?
05:14
<alkisg>
For minimal changes, it could echo the sha1sum of each image?
05:14
dd if=/dev/nbd9 of=/dev/stdout bs=64 count=1 2> /dev/zero | sha1sum - ==> for each image instead
05:14
<vagrantc>
those are kind of expensive to calculate for a large image, no?
05:14
<alkisg>
bs=64 count=1
05:14
<vagrantc>
ah, just the header
05:14
<alkisg>
It should have a lot less overhead than launching an nbd-server process
05:16
<vagrantc>
it also isn't just for ldm that that should happen
05:16
other screen scripts should also maybe reboot
05:16
<alkisg>
...the generic lts.conf+ldminfod+... daemon would help a lot in this case
05:18
<vagrantc>
although other scripts may or may not have a way to communicate what's happening to the usesr.
05:18
<alkisg>
OK let's go for a quick fix for now
05:19
So the problem is that ROOTPATH isn't saved as "NBD_ROOT_HOST" etc?
05:19
<vagrantc>
i'm trying to actually see the problem ...
05:19
<alkisg>
Also, "nbd-client $NBD_ROOT_HOST /dev/nbd9 -N $NBD_ROOT_NAME" ==> if that fails, the script should exit
05:19
E.g. nbd-client $NBD_ROOT_HOST /dev/nbd9 -N $NBD_ROOT_NAME || return 0
05:20
Does it actually mount the nbd image, or does it fail to do so because of missing vars?
05:20* vagrantc is having trouble reproducing it
05:21
<vagrantc>
i've troubleshot so many issues in the last week ... gah. here's another one.
05:23
so something's killing nbd-client on reboot...
05:26* alkisg starts with the ubuntu packaging so that he's able to actually test these things... :)
05:27dgeary2 has left IRC (dgeary2!~david@c114-77-214-254.rivrw3.nsw.optusnet.com.au, Quit: ĝis la)
05:33
<vagrantc>
alkisg: so, it's getting NBD_ROOT_NAME=/dev/nbd0
05:33
alkisg: instead of NBD_ROOT_NAME=/opt/ltsp/i386
05:33
i swear i had a patch for this
05:34komunista has joined IRC (komunista!~slavko@adsl-195-168-237-046.dynamic.nextra.sk)
05:35
<vagrantc>
2237 ...
05:35
<alkisg>
!ltsp-debian-packaging
05:35
<ltsp>
alkisg: Error: "ltsp-debian-packaging" is not a valid command.
05:35
<alkisg>
!pkg-debian
05:35
<ltsp>
alkisg: Error: "pkg-debian" is not a valid command.
05:35
<alkisg>
...
05:37
<vagrantc>
https://code.launchpad.net/~vagrantc/ltsp/ltsp-debian-packaging
05:37
which includes a link to the real location
05:37
<alkisg>
Ah ok
05:38
<vagrantc>
and it is out of date at the moment
05:38* alkisg was trying to see if there were any changes in the real location not yet synced to launchpad
05:38
<alkisg>
!pkg-ltsp-debian
05:38
<ltsp>
alkisg: pkg-ltsp-debian: https://code.launchpad.net/~vagrantc/ltsp/ltsp-debian-packaging is a mirror of http://anonscm.debian.org/loggerhead/pkg-ltsp/ltsp-debian-packaging/files
05:38
<alkisg>
Yey
05:43
<vagrantc>
that just gives you the browser view ...
05:44
<alkisg>
I do have a local copy of the launchpad branch, I just wanted to check the original tree for unsynced changes
05:44
<vagrantc>
nbd-disconnect is hosed.
05:45* vagrantc never liked it
05:47
<vagrantc>
bah.
05:53
<alkisg>
...patience!!!
05:53
<vagrantc>
if grep -q '\-N' /proc/$pid/cmdline; then
05:53
when i execute it manually from the shell, it works....
05:54
and but for some reason it's executing a different codepath
05:55
<muppis>
If I define a localapp in lts.conf and put it launching automatically in profile as normally done, does get launched as localapp?
05:56
<vagrantc>
alkisg: i've been working on this in all my spare moments for the last week :P
05:56
alkisg: i've mustered a bit of patience
05:56
<alkisg>
vagrantc: if ROOTPATH is set in the initramfs, and cmdline doesn't contain nbdroot= or nfsroot=, then we should be using that to store NBD_ROOT_HOST etc etc - don't know if we currently do, I'll start with the packaging first...
05:56
muppis: no
05:57
<vagrantc>
alkisg: there's a bug in init-ltsp.d/04-server that fails to get the right result
05:57cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
05:58cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
05:59
<vagrantc>
alkisg: oh... for some rreason the code in the chroot is not the code in bzr...
06:00
alkisg: doh! i'm running 5.3.7
06:00
<alkisg>
:)
06:00
<muppis>
alkisg, ok.
06:01
<vagrantc>
i knew i fixed that.
06:01
the nbd connection thing is still silly...
06:01
<alkisg>
We need a (long) TODO list
06:02
<vagrantc>
i think my nbd-disconnect issues are also likely related ...
06:02
i need to get something i can upload to debian soon so i can stop accidentallly testing old versions!
06:03
<alkisg>
I'll work most of the day in ltsp, so I should be of some help there...
06:11
vagrantc: in ubuntu's debian/control, ltsp-server depends on ${shlibs:Depends}, while debian's doesn't, which one's correct?
06:12
<vagrantc>
alkisg: there shouldn't be shared libraries in an arch: all package
06:12
<alkisg>
ty
06:13
<vagrantc>
or rather, dependencies on shared libraries
06:21* vagrantc sighs
06:21
<alkisg>
meh I really see no reason why ubuntu's packaging should have all those differences
06:22
Why can't we just include the doc/ dir?!
06:22* alkisg is temped to do a clean start from the debian's debian/ dir...
06:23
<vagrantc>
for reasons that totally perplex me... even creating update-kernels.conf very early in the process, it still defaulted to NFS ...
06:24
running update-kernels later manually still works
06:25
<alkisg>
vagrantc: I think it's because the kernel postinst script is not ran, there's no kernel update involved... or do we call that manually?
06:25
<vagrantc>
alkisg: it should still run on install
06:25
<alkisg>
Is the kernel installed after ltsp-client?
06:26
<vagrantc>
yup
06:29
it seemed to get created when ltsp-update-image was called
06:29
the pxelinux.cfg anyways
06:34
<Hyperbyte>
alkisg, doing a live broadcast from a sports park in Capelle today and tomorrow. :-) International youth (kids up to 13 year) football tournament. :-)
06:35
<alkisg>
Hyperbyte: you have 2 good jobs, time to look for someone to spend all the money you're making with :D
06:41* alkisg pushed an ltsp-config change to check with pgrep if nbd-server is running or not, as recent nbd-server versions ship an /etc/nbd-server/config so we can't rely on that anymore
06:41
<vagrantc>
alkisg: ok, so apparently, somehow running the kernel postinst ignores the BOOTPROMPT_OPTS
06:42
<alkisg>
...
06:43
vagrantc: ah it has a different name there
06:43
So the .conf file isn't sourced
06:43
<vagrantc>
the file is present ... running update-kernels directly works properly ... dpkg-reconfigure linux-image-FOO regenerates with the defaults...
06:43
<alkisg>
It tries to source /etc/ltsp/ltsp-update-kernels.conf instead
06:43
<vagrantc>
aha!
06:43
right.
06:45
i guess instead of symlinking, could put a wrapper at that point.
06:45
<alkisg>
Or just re-launch it:
06:45
case "$0" in
06:45
/etc/kernel/post*.d*) QUIET=true exec /usr/share/ltsp/... ;;
06:45
esac
06:45
"$@"
06:47
That case could also be moved a little above so that we don't source the functions etc twice
06:48
<Hyperbyte>
alkisg, actually, the radio presenting I do, and task as program director, for Radio Capelle is volunteer work. Radio Capelle is a local station, for the city I live in, with very low budget. :) So it's just a bunch of harmless fun, doesn't make me money. :P
06:48
alkisg, only the radio production work I do for Radio 1 (national radio) is paid.
06:49
<alkisg>
Ah, ok :)
06:49
<Hyperbyte>
So basically I have three jobs. :P Did I also mention I recently started my own company? :P
06:49
Where does he get the time!
06:49
<alkisg>
Hahaha
06:49
What kind of company?
06:50
<Hyperbyte>
Absence of a social life does wonders.
06:50
alkisg, basically some IT consulting/website development/radio production/whatever...
06:50
Mainly I just want to be able to send people bills for random jobs I do. :P
06:54* vagrantc heads out
06:54vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
07:08dgeary2 has joined IRC (dgeary2!~david@114.73.121.207)
07:09uskerine has joined IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net)
07:14vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi)
07:36
<uskerine>
hi
07:36
i am trying to get some thin clients working in xubuntu, i did:
07:36
apt-get install ltsp-server-standalone openssh-server
07:37
then ran ltsp-build-client and service nbd-server restart
07:37
what's next? any recommended website?
07:41alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)
07:42alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 252 seconds)
07:43alkisg1 is now known as alkisg
07:43
<alkisg>
uskerine: which xubuntu version, and what errors are you getting?
07:44
<uskerine>
xubuntu 12.04
07:44
i just get PXE-E53: No boot filename received in the screen of my thin client
07:44
i installed it few months ago in LUBUNTU but I lost my notes :(
07:45
<alkisg>
Which architecture is the server and the chroot? both i386?
07:45dgeary2 has left IRC (dgeary2!~david@114.73.121.207, Ping timeout: 256 seconds)
07:45
<uskerine>
both i386
07:45
so i did not use -arch while ltsp-build'ing
07:45
<alkisg>
Do you have another dhcp server in your network?
07:45
<uskerine>
yes i do
07:45
<alkisg>
In the same network where the ltsp clients are supposed to boot?
07:46
<uskerine>
unfortunatelly yes
07:46
<alkisg>
Then you shouldn't be using ltsp-server-standalone
07:46
Can you modify the other dhcp server to provide a boot filename?
07:46
Or is it e.g. an unconfigurable router?
07:46
<uskerine>
no, it is a simple router-based dhcp
07:46
<alkisg>
!proxydhcp
07:46
<ltsp>
alkisg: I do not know about 'proxydhcp', but I do know about these similar topics: 'proxy-dhcp'
07:46
<alkisg>
!proxy-dhcp
07:46
<ltsp>
alkisg: proxy-dhcp: https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
07:47
<alkisg>
Read that page so that you remove isc-dhcp-server and use dnsmasq instead
07:47
<uskerine>
alkisg, just in case it could be easier
07:47
i am just doing a test where both dhcp router and the ltsp box are on the same subnet
07:48
however, i will then install on a real server with more than one ethernet interface, so i could isolate the network segment
07:48
<alkisg>
Ah ok then
07:48
<uskerine>
what would you recommend?
07:48
<alkisg>
Configure your existing server to have 2 IPs from network manager
07:48
One == dhcp, and the second == static, 192.168.0.1
07:49
Or do you have 2 NICs already? (e.g. a wlan and a wired one, or 2 wired ones?)
07:50
Or, test with a virtualbox client in a virtual nic
07:50
That way you won't have to change your setup once you move to the real server
07:50
<uskerine>
no in this test server i only have one ethernet
07:51
i have read the web page you sent
07:51
it seems very difficult, plus it would allow me to put everything in the same network segment
07:51
it does not seem very difficult i mean
07:51
<alkisg>
Decide based on your final setup
07:52
If you want a 1-nic setup with an external, unmodifiable dhcp-server, then proxy-dhcp is the way to go
07:52
If you want a 2-nic setup, keep isc-dhcp-server
07:52
<uskerine>
i will try the proxydhcp, as there could be seats with laptops
07:52
<alkisg>
ok
07:53
<uskerine>
so no matter how many nics i have, at the end the laptop should be serverd by the "central" dhcp
07:54
<alkisg>
Yes in those cases if the "central" dhcp can't be configured to send a boot filename, a proxy-dhcp helps a lot
07:54
<uskerine>
another alternative would be to turn off the router dhcp and make the ltsp server being the main dhcp server
07:55
for both thin clients and regular computers
07:55
<alkisg>
Yes, but if your ltsp server's down, laptops won't have internet access
07:55
<uskerine>
yes i guess it is better to use proxy then
07:55
i will give it a try then
07:55
thanks alkisg
07:56
<alkisg>
uskerine: just be careful not to do the steps that refer to < 12.04 versions in that page
07:56
Many people have edited that page and it's a bit of mess now, it'll be much easier in 12.10
07:56
<uskerine>
ok i will pay attention to 12.04
07:56
thanks
07:58
https://launchpad.net/~ts.sch.gr/+archive/ppa
07:58
which dnsmasq should I download? there are three folders
07:59
<alkisg>
None, that's for <12.04 versions :)
07:59
<uskerine>
*Note: 12.04 users should have a good working dnsmasq program already in the repositories.
07:59
i saw it!
07:59
<alkisg>
(actually for < 9.10)
07:59
<uskerine>
ok thanks
07:59
so apt-get install dnsmasq will fit, right?
07:59
<alkisg>
Yup
08:00
<uskerine>
the web site suggest you to install ltsp-server and then remove purge ltsp-server-standalone
08:00
is that correct?
08:00
I mean the roder
08:01
<alkisg>
Yes
08:07
<uskerine>
/opt/ltsp/i386/boot/pxelinux.cfg
08:07
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg
08:07
what is in /opt and what is in /var
08:07
(i am in adjusting pxelinux.cfg step)
08:07
and what am I actually doing?
08:08
I mean by doing this: (cat <<EOF
08:08
ipappend 3
08:08
EOF
08:08
) | sudo tee -a /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
08:12
<muppis>
Adding line containing 'ipappend 3' to /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default as last line.
08:14
<uskerine>
i mean, why and what it does
08:14
i can live without knowing, but i like to know "why"
08:14
(i already knew the command was adding a line)
08:14
<muppis>
:D
08:15
IIRC, it tells to dhcp client not to rere
08:16
IIRC, it tells to dhcp client not to re-request the IP and instead use already obtained by pxe.
08:18
<uskerine>
ok
08:18
thanks
08:18
good
08:18
the thin client it is loading
08:18
:)
08:19
but i got busybox console
08:19
08:19
i saw the ubuntu screen loading
08:19
then i got a console
08:19
prompt is initramfs)
08:20
<alkisg>
cat /proc/cmdline
08:21
<uskerine>
where do i run it, server or thin client?
08:21
thin client:
08:22
<alkisg>
client
08:24
<uskerine>
ro initrd=initrd.img root=/dev/nbd0 init=/sbin/init-ltsp quiet splash plymouth:force-splash vt.handoff=7 nbdroot=:ltsp_i386 BOOT_IMAGE=vmlinuz ip=192.168.10.108:192.168.10.103:192.168.10.1:255.255.255.0 BOOTIF=01-0(MAC ADDRESS)
08:24
i didn't copy the mac-address
08:24
108 is the thin client, 103 is the server
08:24
what is /proc/cmdline btw?
08:26
<alkisg>
Sorry no time to help with generic knowledge I'm also programming now, but test if your nbd-server is running
08:26vmlintu has left IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 245 seconds)
08:26
<alkisg>
pgrep nbd-server on your ltsp server
08:27
<uskerine>
it is, i get pid
08:28
<alkisg>
ls -l /opt/ltsp/images/i386.img
08:29
<uskerine>
-rw-r--r-- 1 root root 265867264 May 27 09:16 /opt/ltsp/images/i386.img
08:29
<alkisg>
grep nbd /var/log/syslog
08:29
<uskerine>
i did the ltsp-build before the dnsmasq and the ltsp.conf file (just in case it could be relevant)
08:30epoptes_user5 has joined IRC (epoptes_user5!58dbc5a1@gateway/web/freenode/ip.88.219.197.161)
08:30
<uskerine>
http://pastebin.com/raw.php?i=AAMdprps
08:31
<alkisg>
uskerine: the problem is "permission denied"...
08:31
cat /etc/nbd-server/conf.d/ltsp_i386.conf
08:32
<uskerine>
[ltsp_i386]
08:32
exportname = /opt/ltsp/images/i386.img
08:32
readonly = true
08:32
<alkisg>
uskerine: run the `ls -l /opt/ltsp/images/i386.img` as a simple user, not root, to check for permission problems
08:33
<uskerine>
memmanuel@optiplex-alfa:~$ ls -l /opt/ltsp/images/i386.img
08:33
ls: cannot access /opt/ltsp/images/i386.img: Permission denied
08:33
<alkisg>
Right, so check the dirs, you have one of them not readable by users
08:33
<uskerine>
i will check permissions
08:33
<alkisg>
E.g. /opt
08:33
<uskerine>
ls -ld ltsp/
08:33
drwx------ 4 root root 4096 May 27 09:13 ltsp/
08:33
here it is
08:34
i guees that should be rwxr--r--
08:34
right?
08:34
<alkisg>
Why would that be? Do you have some weird umask?
08:34
No, it should be 755
08:34
"x" to "others"
08:34
<uskerine>
yes i changed umask as i was trying to get new users be created without being able to access to other folders
08:34
but i see there are collateral casualites
08:34
:(
08:35
<alkisg>
Just chmod 700 /home/*
08:35
<uskerine>
yes i will restore umask and do that
08:35
thanks
08:35
<alkisg>
uskerine: I'm not sure if that affected your existing chroot
08:36
<uskerine>
ok if there is somthing i will reinstall from scratch with correct umasj
08:36
ok if there is somthing i will reinstall from scratch with correct umask
08:36
<alkisg>
Check /opt/ltsp/i386/* for possible permissions problems, or run ltsp-build-client again after restoring the umask
08:36
<uskerine>
ok i will do that
08:39
fortunatelly changing the umask was the last thing i did on the server
08:39
as i guess it could mess up other packages
08:45
alkisg i can login now, thank you very much i will logout and login to ensure my umask is back again
08:45uskerine has left IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net, Quit: Leaving)
08:59uskerine has joined IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net)
09:01uskerine has joined IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net)
09:02
<uskerine>
hi again, for some reason only my previous user can login through the thin client, all other users (including freshly ones created that can perfectly log in locally) can not
09:09
i got the login screen
09:10
when i type user and password
09:10
i got verying password for a while
09:10
then "no response for server, restarting...
09:10
any idea on which log should I look?
09:18
I found answer in google: sudo ltsp-update-sshkeys and ltsp-update-image
09:18
i did it and restarted the thin client, but after the ubuntu load screen i got again the busybox console
09:19
this time cat /proc/cmdline returns no IPs or MACs
09:19
ro initrd=initrd.img root=/dev/nbd0 init=/sbin/init-ltsp quiet splash plymouth:force-splash vt.handoff=7 nbdroot=:ltsp_i386 BOOT_IMAGE=vmlinuz
09:19
alkisg any idea on where should I look for now?
09:20
<alkisg>
uskerine: you didn't follow all the proxydhcp page so you now need to put ipappend 3 manually in pxelinux.cfg/default every time you run ltsp-update-image
09:20
<uskerine>
oh
09:20
thanks
09:20
do i have to do that after or before
09:20
running ltsp-update-image?
09:21
<alkisg>
After
09:25
<uskerine>
did it, it works again
09:25
but i can not log in for other users :(
09:29
<alkisg>
uskerine: it still works for that one user?
09:30
<uskerine>
yes it does
09:30
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/567325
09:30
it seems it is something that has happened before :(
09:31
can i redo the install or something like that?
09:31
can i redo the image or something like that?
09:32
like sudo ltsp-build-client
09:43* uskerine any help is really welcomed, i have ten thin clients bought :(
09:47
<uskerine>
where could I have a look to the log of the ldm ran in the client (i understand it is ldm the logging manager)
09:47
?
09:52
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
09:52
May 27 11:52:03 optiplex-alfa sshd[5641]: User jdoe from 192.168.10.108 not allowed because not listed in AllowUsers
09:57
adding the users to sshd_config AllowUsers fixed the issue
10:20uskerine has left IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net, Remote host closed the connection)
10:55khildin has joined IRC (khildin!~khildin@5ED3EFC1.cm-7-4d.dynamic.ziggo.nl)
11:19khildin has left IRC (khildin!~khildin@5ED3EFC1.cm-7-4d.dynamic.ziggo.nl, Remote host closed the connection)
11:36Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
11:53map7 has left IRC (map7!~map7@teksup41.lnk.telstra.net, *.net *.split)
11:53knipwim has left IRC (knipwim!~wim@ip4da83870.direct-adsl.nl, *.net *.split)
11:53telex has left IRC (telex!~telex@freeshell.de, *.net *.split)
12:07Mava has left IRC (Mava!~Mava@ip-45-224.dhcp.opintanner.fi, Remote host closed the connection)
12:16adrianorg__ has joined IRC (adrianorg__!~adrianorg@177.18.179.2)
12:16map7 has joined IRC (map7!~map7@teksup41.lnk.telstra.net)
12:16telex has joined IRC (telex!~telex@freeshell.de)
12:16knipwim has joined IRC (knipwim!~wim@ip4da83870.direct-adsl.nl)
12:34Mava has joined IRC (Mava!~Mava@ip-45-224.dhcp.opintanner.fi)
13:00alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
13:05dgeary2 has joined IRC (dgeary2!~david@c114-77-214-254.rivrw3.nsw.optusnet.com.au)
13:50adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.179.2, Ping timeout: 240 seconds)
13:54alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Read error: Operation timed out)
13:55Parker955 is now known as Parker955_Away
14:02Phantomas1 has joined IRC (Phantomas1!~Phantomas@unaffiliated/phantomas)
14:02Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Disconnected by services)
14:02Phantomas1 is now known as Phantomas
14:05dgeary2 has left IRC (dgeary2!~david@c114-77-214-254.rivrw3.nsw.optusnet.com.au, Quit: ĝis la)
14:12alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
14:17F-GT has left IRC (F-GT!~phantom@ppp121-44-97-140.lns20.syd6.internode.on.net, Quit: Leaving)
14:18Trixboxer has joined IRC (Trixboxer!~Trixboxer@115.124.115.71)
14:24msignor has left IRC (msignor!~matt@24.115.67.19.res-cmts.sesp.ptd.net)
14:38msignor has joined IRC (msignor!~matt@24.115.67.19.res-cmts.sesp.ptd.net)
14:40
<msignor>
Hello All - I am trying to rebuild my ltsp client image from scratch. However, it is failing with an error that the installation ended abnormally
14:40
fails on "extracting adduser"
14:41
I am trying to build my chroot on my ubuntu installation, via NFS to my debian ltsp server
14:44Parker955_Away is now known as Parker955
14:46
<msignor>
Could anyone direct me in a direction with a link, etc. on how I can use a debian ltsp server with an ubuntu nbd image?
14:57F-GT has joined IRC (F-GT!~phantom@ppp121-44-97-140.lns20.syd6.internode.on.net)
15:04F-GT has left IRC (F-GT!~phantom@ppp121-44-97-140.lns20.syd6.internode.on.net, Ping timeout: 246 seconds)
15:05alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
15:06uskerine has joined IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net)
15:07
<uskerine>
hi all, I installed ltsp, but it seems that all the theme & menu configuration I did for the server is ignored by LTSP while serving the thin clients, is there any place where I could understand how and where ltsp actually reads configuration files?
15:08
<alkisg>
msignor: with the really latest updates to LTSP which _will_ be uploaded in unstable next week, you'll be able to do it with
15:08
VENDOR=Ubuntu ltsp-build-client ...
15:08
so if you're using wheezy, you might just want to wait 1 week
15:08
uskerine: how did you configure the theme and menu on the server for all users?
15:08
<uskerine>
using /etc/xdg/xdg-xubuntu mainly
15:08
<alkisg>
And you're using thin clients or fat?
15:09
<uskerine>
i guess thin clients, although i did not specify anywhere if they were thin or fat
15:09
<alkisg>
Thin then.
15:10
And the theme and menus work fine on the server if you login with other users?
15:10
<uskerine>
yes it works fine
15:10
actually i get different look&feel login from the server than login from the thin client
15:11
different menus too
15:11
<alkisg>
Strange. Can you run a ps aux from a thin client and upload it to pastebin?
15:11
<msignor>
alkisg: thanks - I had this working with Squeeze & ubuntu 10.04 nbd image.. but something broken on my debian server and I am trying to work backwards to see how I even had it set up in the first place.
15:11* uskerine miss the xdmcp days
15:11
<msignor>
I don't actually understand where I specify to be a NBD image compared to the NFS image that debian is set up as default
15:12
<alkisg>
uskerine: you can easily use xdmcp in ltsp if that's what you want
15:12
But you'll miss sound, local devices etc
15:12
<uskerine>
i guess xdmcp is no longer supported by xubuntu
15:12
and yes, i also need a sip phone client installed later on the thin client
15:12
<alkisg>
Xubuntu uses lightdm afaik and lightdm supports xdmcp
15:13
msignor: in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
15:13
<msignor>
alkisg - do the files in tftpboot get recreated when the image is made?
15:13
<alkisg>
msignor: when you run ltsp-update-image, yes
15:14
Or ltsp-update-kernels
15:14
<msignor>
alkisg - i have tftp-hda configured to use /tftpboot as the root
15:15
My server is a embedded device which has an attached SSD for long term / mass storage. so I have a simlink for /opt/ltsp to /mnt/ssd/ltsp and a symlink for /tftpboot to /mnt/ssd/tftpboot
15:16
on my ubuntu notebook - I just mapped the local /opt/ltsp to an nfs mount to /mnt/ssd/ltsp but not anything mapped to the /tftpboot - would that be an issue?
15:17
<alkisg>
msignor: not really, but after running ltsp-update-kernels on your ltsp server, what's your pxelinux.cfg/default like?
15:18
<msignor>
I am not sure really - I have not done an update kernels
15:19uskerine has left IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net, Remote host closed the connection)
15:19
<alkisg>
msignor: if you don't have the kernels in your tftp dir, how would the clients boot?
15:19uskerine has joined IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net)
15:20
<uskerine>
alkisg actually when i login in the thin client with a new user, i got a strange message:
15:20
Welcome to the first start of the panel
15:20
Choose belo which setuop you want for the first startup
15:20
"Use Default Config" and "One empty panel"
15:20
that does not happens when I log in directly into the server for the same new user
15:20
<alkisg>
A ps aux would be the first step to see what goes on in your setup, please upload it to pastebin
15:20
<msignor>
alksig - i do have the kernels there, unfortunately I do not know exactly how they got there... I presume that when i recovered from my backup they were part of that
15:21
<uskerine>
i will paste the psaux
15:21
<alkisg>
msignor: just run ltsp-update-kernels and paste your pxelinux.cfg/default to pastebin
15:21F-GT has joined IRC (F-GT!~phantom@ppp121-44-97-140.lns20.syd6.internode.on.net)
15:21
<msignor>
from the debian server or the ubuntu machine?
15:22
<alkisg>
From the debian server
15:22
You shouldn't need the ubuntu machine anymore
15:22
<msignor>
alkisg - okay, 1 min
15:23
<uskerine>
alkisg: pastebin.com/raw.php?i=z0vAXPeG
15:25
<alkisg>
uskerine: what's the username for uid=1000 ?
15:25
<msignor>
alkisg : http://pastebin.com/raw.php?i=BSeSqu5X
15:26
<uskerine>
alkisg, that's my account (memmanuel), the new user is 1001 (jdoe)
15:26
<alkisg>
msignor: and what do you get if you try to boot with that?
15:26
uskerine: so jdoe has logged in from the thin client, and you from the server?
15:26
<uskerine>
right
15:26
i am writing you from the server
15:26
and "jdoe" is the one on the thin client
15:27
which was a freshly recreated new user
15:27
<msignor>
alkisg - failed to connect to nbd server
15:27
<alkisg>
msignor: is your nbd server running on debian?
15:27
<msignor>
yes
15:27
i can restart it...
15:29
"message: no configured exports, quitting"
15:29
<alkisg>
So you're missing the nbd configuration
15:29
Ah
15:29
Sorry, squeeze
15:29
What's the output of `grep nbd /etc/inetd.conf` ?
15:29
<msignor>
12345 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /mnt/ssd/ltsp/images/i386.img
15:30
<alkisg>
The port is wrong there, you were supposed to use 2000
15:30
Change it and restart openbsd-inetd
15:31
<msignor>
okay, reboot client
15:32
nice - booted
15:32
brb 10 min - need to let my dog out, can't think with the barking.
15:39Trixboxer has left IRC (Trixboxer!~Trixboxer@115.124.115.71, Quit: "Achievement is not the end, its the beginning of new journey !!!")
15:42
<uskerine>
aliksg, it works if you put config under /home .config
15:42
i guess i will have to put everything in skel
15:43
so new users come with the standard installation
15:47
i will install another server from scratch in parallel
15:48
alkisg, how should i disable the ltsp server on this one?
15:48
just bring down masqdns?
15:48
additionally, in xubuntu, there is an "install an LTSP server" installation mode
15:48
is that recommended?
15:48
(instead of installing a regular one and then adding the packages)
16:00Parker955 is now known as Parker955_Away
16:03
<msignor>
aliksg: okay - booted in finally :) now, I assume I need to rebuild the image so I can properly configure the NFS homes correct?
16:51msignor has left IRC (msignor!~matt@24.115.67.19.res-cmts.sesp.ptd.net)
16:53msignor has joined IRC (msignor!~matt@24.115.67.19.res-cmts.sesp.ptd.net)
18:11vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi)
18:38alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)
18:39alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 260 seconds)
18:40alkisg1 is now known as alkisg
18:56risca has joined IRC (risca!~risca@81-233-43-131-no18.tbcn.telia.com)
19:11khildin has joined IRC (khildin!~khildin@5ED3EFC1.cm-7-4d.dynamic.ziggo.nl)
19:20alexqwesa_ has joined IRC (alexqwesa_!~alex@109.172.12.47)
19:20alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Ping timeout: 245 seconds)
19:28
<alkisg>
uskerine: yes, disabling dnsmasq would prevent the ltsp clients from booting from it. And, the ltsp server installation mode is about the same (yet a bit faster) as running ltsp-build-client
19:28
msignor: use tab to autocomplete user names correctly. No, you don't have to rebuild the image to configure nfs homes
20:00epoptes_user5 has left IRC (epoptes_user5!58dbc5a1@gateway/web/freenode/ip.88.219.197.161, Quit: Page closed)
20:19
<uskerine>
thanks alkisg, i reinstalled everything from scratch, and what i did is to set up the configuration of window manager and theme directly on one user account, i will replicate config files under .config in /etc/skel so hopefully settings will be replicated
20:19
btw, is it possible to force a given resolution?
20:19
i am getting an awful 1024x768 on a full-hd 1920x1080
20:20
and second question is, how can i customize ldm so the user can not select session?
20:21alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
20:23litlebuda has joined IRC (litlebuda!~litlebuda@204.0.166.178.rev.vodafone.pt)
20:26danishman has joined IRC (danishman!~kvirc@62.243.156.218)
20:40
<uskerine>
Hi, does anyone know how to fix a resolution issue in LTSP?
20:41
I have found the right resolution that can be applied on a terminal through xrandr
20:41
but now I would like to make this fix permanent
20:41adrianorg__ has joined IRC (adrianorg__!~adrianorg@177.18.179.2)
20:48msignor has left IRC (msignor!~matt@24.115.67.19.res-cmts.sesp.ptd.net, Ping timeout: 265 seconds)
20:56notori0us has joined IRC (notori0us!~notori0us@opensource.cse.ohio-state.edu)
20:57
<notori0us>
hello, #ltsp!
20:57paradigm has joined IRC (paradigm!~paradigm@osuosc/paradigm)
21:03
<uskerine>
hi, any web site to customize lightdm, including specific resolutions through xrandr?
21:04
that's one of the last things i am missing to complete my LTSP deployment :)
21:05khildin has left IRC (khildin!~khildin@5ED3EFC1.cm-7-4d.dynamic.ziggo.nl, Quit: I'm gone, bye bye)
21:18litlebuda has left IRC (litlebuda!~litlebuda@204.0.166.178.rev.vodafone.pt, Remote host closed the connection)
21:27alexqwesa_ has left IRC (alexqwesa_!~alex@109.172.12.47, Ping timeout: 240 seconds)
21:38alexqwesa_ has joined IRC (alexqwesa_!~alex@109.172.12.47)
21:38danishman has left IRC (danishman!~kvirc@62.243.156.218, Quit: KVIrc 4.0.4 Insomnia http://www.kvirc.net/)
22:03Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Ping timeout: 265 seconds)
22:05komunista has left IRC (komunista!~slavko@adsl-195-168-237-046.dynamic.nextra.sk, Quit: Leaving.)
22:17Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
22:23adrianorg_ has joined IRC (adrianorg_!~adrianorg@187.58.154.153)
22:24adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.179.2, Ping timeout: 256 seconds)
22:27F-GT has left IRC (F-GT!~phantom@ppp121-44-97-140.lns20.syd6.internode.on.net, Ping timeout: 245 seconds)
22:32uskerine has left IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net, Quit: Leaving)
22:53uskerine has joined IRC (uskerine!~uske@237.Red-95-122-134.staticIP.rima-tde.net)
22:53
<uskerine>
hi, my thin client is going to slow in 1920x1080 while browsing the web
22:53
can google chrome be moved to the thin client?
22:53
any recommended tutorial or doc page to do it?
23:00Parker955_Away is now known as Parker955
23:04Parker955 is now known as Parker955_Away
23:16staffencasa has joined IRC (staffencasa!~staffenca@128.193.8.220)
23:25staffencasa has left IRC (staffencasa!~staffenca@128.193.8.220, Ping timeout: 250 seconds)
23:41Parker955_Away is now known as Parker955
23:46highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Ping timeout: 260 seconds)
23:46highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
23:47elias_a_ has left IRC (elias_a_!elias@hilla.kapsi.fi, Ping timeout: 260 seconds)
23:47elias_a has joined IRC (elias_a!elias@hilla.kapsi.fi)