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


Channel log from 4 February 2011   (all times are UTC)

00:16alkisg has quit IRC
00:18datandrews has quit IRC
00:18drdata has joined #ltsp
00:20drdata has left #ltsp
00:23drdata has joined #ltsp
00:26drdata has left #ltsp
01:32alkisg has joined #ltsp
01:44Kicer86 has joined #ltsp
01:46shogunx has quit IRC
03:02dobber has joined #ltsp
03:30gnunux has joined #ltsp
04:12Kicer86 is now known as webczat_
04:12webczat_ is now known as Kicer86
04:57spectra has quit IRC
05:02toscalix has joined #ltsp
05:10alkisg has quit IRC
05:38
<simbulu>
Would someone tell us how we can put some load on more powerfull ltsp clients having 1GB RAM 3GHz CPU and 80GB empty diskspace?
05:40
<muppis>
simbulu, fat-client
05:41
But one of ideas of ltsp is no need for local hdd.
05:43
<simbulu>
muppis, I do not have to use the local disk, but can if I want to as it will be there anyway (What else could I do with 39 x 80GB disks?)
05:44
the idea is just to use local resources that happen to be available. and yes - I hate local disks :)
05:44
anyway - what is "fat-client" ?
05:45
<muppis>
simbulu, it is something between reqular thin client and local installation, meaning it started and used as thin, but everything is runned locally as like in local installation.
05:47
<simbulu>
I would love to create stations that would run everything on the server, but firefox and openoffice which should run locally.
05:47
<muppis>
Then it is thin with local-apps.
05:49
<simbulu>
is fat-client seems to be a ltsp-build-client plugin for Ubuntu, right?
05:50
<muppis>
I think so. Haven't used that.
05:50otavio has joined #ltsp
05:50
<simbulu>
anyway. I have something called ltsp-localapps ...
05:51
<muppis>
That's good to start.
05:52
<simbulu>
ohh - it has a manual!
05:52
I wonder how it is configured and used
05:54
there is also something called ltsp-genmenu ...
05:55spectra has joined #ltsp
05:56
<muppis>
I think that is used to generate Gnome -menus to automatically launch app as localapp instead of in server.
05:56MorningSon has joined #ltsp
05:57
<simbulu>
ok - but first challenge would be to start an app locally on a powerfull client. But how?
05:57
something with "xprop" ?
05:58
<muppis>
Yes.
05:59drdata has joined #ltsp
06:00root__ has joined #ltsp
06:00
<simbulu>
xprop: command not found :-(
06:00shogunx has joined #ltsp
06:00
<root__>
hi..
06:01
<simbulu>
seems I need xprop - should be in xorg-x11-utils
06:01
<root__>
can any one tell me what settings has to done for connecting tftp server..
06:02
i am getting err5or file not found
06:02
<muppis>
root__, if you get that, then connects ok, but asks wrong file or from wrong directory.
06:03
<root__>
is there any setings for that..
06:04
<muppis>
Which distro?
06:04
<root__>
ubuntu 10.04
06:05
<muppis>
Compare settings from /etc/ltsp/dhcpd.conf to directories under /var/lib/tftboot/
06:07
<root__>
/var/lib/tftpboot/ltsp/i386/pxelinux...
06:08
<muppis>
Sound correct. What your client requests?
06:09
<root__>
it requests for DHCP and after getting IP it gives error file not found
06:09
<muppis>
root__, fresh installation?
06:10alkisg has joined #ltsp
06:11
<root__>
is there any fault with this..
06:12Kicer86 has quit IRC
06:12
<muppis>
Yes, but it comes along with packages..
06:13
root__, does your /etc/ltsp/dhcpd.conf look like this? http://ltsp.pastebin.com/xsQqWuSk
06:13
(mind the # marks, that's not mine dhcpd.conf nor untouched one.)
06:15
<alkisg>
https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP
06:16
[04:47] [simbulu] I would love to create stations that would run everything on the server, but firefox and openoffice which should run locally. ==> just wondering, why not everything on the client? What's the benefit of running e.g. gimp or evolution on the server, if your clients are good enough?
06:18
<muppis>
alkisg, I wondered that too, but didn't minded after all.
06:19
<simbulu>
alkisg, Sure - let us let the clients run what they can run - and let them run whatever they can not run themselves on the server. Better?
06:19
<muppis>
simbulu, then I still suggest fat for those.
06:20
<simbulu>
thank you muppis.
06:22
is "fat-client" something you give to ltsp-build-client as an option ?
06:23
<alkisg>
!fatclients
06:23
<ltspbot>
alkisg: "fatclients" :: You may find some info about the Ubuntu/LTSP implementation of fat clients at https://help.ubuntu.com/community/UbuntuLTSP/FatClients
06:24
<alkisg>
See the plugin there, you may easily make something similar for your distro
06:24
<root__>
yes, muppis.. same.. as that one..
06:24
<simbulu>
(reading the 030-fat-client (for Ubuntu))
06:24
<alkisg>
simbulu: Basically you install a whole system (ubuntu-desktop package for ubuntu) and just remove some bits that prohibit it from properly booting, like network-manager or gdm
06:25
<simbulu>
yep - that looks like drdb and netboot
06:25
<alkisg>
Authentication still happens on the server with LDM like for regular thin clients
06:25
And other ltsp options apply, e.g. XRANDR_MODE* etc
06:27
<simbulu>
now I will have to convert that to F14 ...
06:30
seems like Ubunto folks say: "ltsp-build-client --arch i386 --chroot i386-fat --fat-client " on the server. Nice.
06:31
<muppis>
root__, then you can try this version of it: http://ltsp.pastebin.com/U6kxwjxc
06:31
Now, do mind those # marks.
06:43
<simbulu>
I have two types of PXE clients (thin and fat). So I would to run ltsp-build-client with two different configurations. Right?
06:43
<alkisg>
simbulu: for ubuntu, one can use the same chroot for both types of clients
06:43
thin, thin with localapps, and fat clients == 1 single chroot
06:43
I bet you can do that with fedora as well, with a little tweaking
06:46mistik1 has quit IRC
06:47
<simbulu>
Great! In that case I just have to configure /etc/ltsp/ltsp-build-client.conf, adapt the fat-client plugin and run ltsp-build-client.
06:47
<alkisg>
Right
06:48
<simbulu>
I was just afraid that the "fat" build would create boot stuff too big for the smaller clients.
06:49
<alkisg>
No, as the disk is not loaded in the client RAM. Only the needed sectors are fetched each time.
06:49
The weird thing is that a fat chroot needs a bit *less* RAM than a thin chroot, didn't find time to see exactly why...
06:50* alkisg boots 64 MB RAM clients from fat chroots with no problems...
07:04[GuS] has joined #ltsp
07:04[GuS] has joined #ltsp
07:27
<root__>
i am not able to login fron thin client in LTSP server ... any idea
07:28
hi muppis... are u there..???
07:28alkisg has quit IRC
07:29
<muppis>
root__, for a while.
07:30
root__, what happens when you try to login?
07:30toscalix has quit IRC
07:30
<root__>
not giving any error.. but i am unable to login..??
07:31
how to create LTSP useres... is there any specific procedure..???
07:31
<muppis>
root__, no, they are reqular users in server.
07:33
<root__>
ok.. it giving messege.. no responce from server restarting..
07:34
where r u from..??
07:34
<muppis>
Finland.
07:34
<root__>
r u a devloper???
07:35
<muppis>
Nope, just curious admin.
07:36
<root__>
ok.. in software company...?
07:39
<muppis>
Kind of. Basically we do wbsites, but those run on our own product.
07:39
websites..
07:40shawnp0wers has joined #ltsp
07:40
<root__>
ok.. thats great.. wht kind of product???
07:41
<muppis>
perl based application framework.
07:44
<root__>
all web based applications.. or any other???
07:46
<muppis>
Just for web.
07:47
<root__>
ok.. r u doing it induvidual???
07:49
<muppis>
Do you mean for persons?
07:52
<root__>
no.. i mean to say.. r u e freelancer... or doing job..???
07:53
<Nubae>
perl, ugh :p
07:53
j/k
07:56RiXtEr has quit IRC
07:57RiXtEr has joined #ltsp
07:58dgroos has joined #ltsp
07:58robehend1 has joined #ltsp
07:59
<robehend1>
dgroos: your running just plain-jane thin clients, right? not fat clients?
07:59dgroos has quit IRC
07:59dgroos has joined #ltsp
08:00
<dgroos>
good morning
08:00
<robehend1>
hello
08:01
<dgroos>
robehend1: How are you?
08:01
<robehend1>
dgroos: good, good. Say, your running normal thin clients, not fat clietns, right?
08:01alkisg has joined #ltsp
08:02
<dgroos>
Indeed though experimenting with fat-clients. Though at the moment my thin is dead :(
08:02
<robehend1>
oh? what happened
08:02
<dgroos>
And, I'm supposed to go to a meeting and the sub needs the 'puter for the lesson...
08:02
<robehend1>
gotta love mornings
08:03
<dgroos>
I added the 'sorenson' codec add-ons, and rebuilt the image.
08:03
:)
08:03
<robehend1>
and that killed the thin-clients?
08:04
<dgroos>
and now I get the message: "Error: failed to connect to NBD server 192.168.0.1:2000 Busybox... etc.
08:04
<robehend1>
oh, i've ran into that before
08:04
run greb nbd /etc/inetd.conf and check what port your images are exported on
08:04
<dgroos>
will try!
08:04
<robehend1>
then, go to /var/lib/tftpboot/ltsp/chroot-name/pxelinux.fcg/ and check that the port in the default file matches
08:05drdata has quit IRC
08:05drdata has joined #ltsp
08:05
<dgroos>
"greb not found"?
08:05
<robehend1>
er, grep
08:05
haven't finished my first cup of coffee today..
08:06
<dgroos>
:)
08:06
(sub just got here!)
08:06
<robehend1>
ack dont remind me, i've got 12 subs int he building today. flu is hitting us hard
08:07
<dgroos>
"/etc/inet.conf: No such file or directory"
08:07
?
08:07
<robehend1>
inetd.conf
08:08
ports should be on the far left, usually 200x series. Just find the one that coincides with the chroot your wanting to boot
08:08
<dgroos>
"grep: /etc/inetd.conf: no such file or directory"?
08:08
(should I be running this on the initramfs?)
08:08
<robehend1>
on the server
08:09
<dgroos>
ahh...
08:09
<robehend1>
my mistake ;)
08:09
<dgroos>
(my first message was something about no command called "breb"...)
08:10
<robehend1>
could be worse. i find myself trying to nano things much to often
08:13
<dgroos>
OK the grep gave:
08:13
greb nbd /etc/inetd.conf
08:13
oops...
08:15
2000 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/fatimage.img
08:15
there be the problem!
08:15
<robehend1>
yep. nbd ports are off. go into your /var/lib/tftpboot/ltsp/fatimage/pxelinux.cfg/default file, and change hte port number at the end to the right one. no need to rebuild the image or anything
08:16
<dgroos>
but the fatimage is the one I deleted?
08:16
<robehend1>
did you delete only the chroot, or the image file as well? nbd is just exporting the image file
08:17
<dgroos>
right, just the chroot
08:17
but I
08:17
only have the one i386.img...
08:17
<alkisg>
sudo ltsp-update-image --force, updates inetd.conf and pxelinux.cfg/default automatically
08:18
<robehend1>
hmm, thats good to know. i've just been going in and checking the ports after i update ;0
08:18
<dgroos>
thanks alkisg :)
08:19
in process...
08:20
<robehend1>
oh, has anyone thrown libreoffice onto a thin-client, instead of open office?
08:20
<Nubae>
robehend1 i installed natty alpha 2 yesterday
08:20
and its in there
08:21
but dont think it works as thin client yet
08:21
<robehend1>
oh? something with unity?
08:23
<Nubae>
unity, whatcha mean?
08:23
<robehend1>
wondered if it was the transistion to the unity enviroment in 11.04 was causing issues on the thin-client end, or if it was something else.
08:24
<Nubae>
think its something else, someone mentioned it the other day
08:24
<ogra>
it will fall back to a normal gnome desktop if it detects on GL support
08:24
<robehend1>
oh nice
08:24
<ogra>
*no
08:24
<alkisg>
Not so normal, the menu was changed when I tried it last week :)
08:24
<ogra>
but you can install unity-2d
08:25
that will even run on framebuffer devices
08:25
<robehend1>
i've played that, on a 10.10 box. wasn't bad at all
08:25
now if only i had a way to get rid of that darn places menu in it
08:25
<Nubae>
works ok here in my vm, but kinda strange when the menu loads up, first nice dark colour, then grey white
08:25
<alkisg>
I'm worried about the many years we'll need to spend with mixed desktops, until all of them can support 3d
08:25
We won't be able to write notes for lessons etc
08:25
<robehend1>
agreed
08:25
<alkisg>
We'll need 2 versions of them :-/
08:25
<ogra>
??
08:26
<robehend1>
espicially if your trying to go with low-power options, discreet graphics can eat up to much
08:26
<dgroos>
alkisg: I ran the command, tried rebooting and got the same--do I need to do something else?
08:26
<ogra>
at some point unity-2d will become the default fallback
08:26
it will look exactly the same as the 3D version just with no effects
08:26
<robehend1>
dgroos: go into your pxelinux.cfg/default file, and just double check the right ports are pointing to the right images. you should have the same port in the cfg file as defined in inetd.conf
08:26
<alkisg>
dgroos: sudo invoke-rc.d openbsd-inetd restart
08:27
<robehend1>
ogra: know of any plans on editing the unity menus, like Alacarte does currently for gnome menus? I haven't tried anything like it, so it could already be there
08:27
<ogra>
editing ?
08:27
<robehend1>
adding/removing launchers, etc
08:27
<ogra>
why would you ? there are no menus anymore
08:28
<robehend1>
policy adherence, mostly. We have some users who would, for example, need access to the Tsclient, while others wouldnt. So, ideally we'd be able to hide the TSclient icon for the ones who dont need it, so they dont stumble into things they shouldnt use
08:28
that, and my rule of k-12 computing: if the kids can see the icon, they will click it. multiple times.
08:29
<Nubae>
robehend1 the new menu is just the ubuntu symbol
08:29
no words
08:29
places and system are within the main menu
08:29
<dgroos>
alkisg: did and it restarted. Then I retried and got same results...
08:30
robehend1: will check...
08:30
<Nubae>
much cleaner
08:30
<alkisg>
dgroos: ok let's try manually, like robehend1 suggests:
08:30
grep nbd /etc/inetd.conf /var/lib/tftpboot/ltsp/*/pxelinux.cfg/default
08:30
<robehend1>
hmm, i'm gonna have to check it out then.
08:31
<dgroos>
yea, still the fat-image...
08:31Kicer86 has joined #ltsp
08:31
<Nubae>
love the integrated telepathy based comms
08:31fly23_ has left #ltsp
08:32
<robehend1>
Nubae: thats the kind of things we're looking to turn off, as im and such is not allowed
08:33
<Nubae>
not working yet, but I can see where its going, its gonna be super user friendly
08:33
well u have to add accounts, so if dont i guess it wont work :-)
08:33
<alkisg>
dgroos: paste the result here
08:33
<Nubae>
anyway easy enough to apt-get remove empathy gwibber
08:34
<robehend1>
Nubae: yep, thats what we currently do. my main concern, i guess, would be somehow removing the 'places' part of the interface.
08:34
<dgroos>
alkisg: paste doesn't work from nx right now...
08:34
<Nubae>
its just nice to see evolution, social broadcasting, microblogging, etc all intergrated in one interface
08:34
<dgroos>
but it's the same as before.
08:35
<Nubae>
places no longer exists
08:35
<robehend1>
oh? nice!
08:35
<Nubae>
its ony within the main menu
08:35
<robehend1>
hmm
08:35
<dgroos>
I typed sudo gedit /var/lib/tftpboot/ltsp/*/pxelinux.cfg/default
08:35
and it didn't say anything...
08:35
<robehend1>
and, if i turn said main menu off, will they still have a workable enviroment/
08:35
<dgroos>
or couldn't find the file>
08:35
.
08:35
<Nubae>
sure, just hide it from the pannel
08:35
<alkisg>
dgroos: erm, if you typed that correctly, it should work
08:36
Try nautilus /var/lib/tftpboot
08:36
And see the paths by yourself
08:36
<robehend1>
nice. my concern is they'll use that network browser to go adventuring. not that they'd get into things, i'd just prefer them not knowing how the servers are named and such
08:36
<Nubae>
ubuntu software center has featured content too... it all looks very nice, lots of changes
08:37
robehend1 sabayon might be worth looking into
08:37
<robehend1>
hmm. i may have to download natty and give it a shot. how's stability, due to its alpha status
08:37
Nubae: does sabayon work now? reliably/
08:37
<Nubae>
well certainly not stable
08:38
robehend1 supposedly it works... im not sure on reliability though
08:38
natty =! stable i mean
08:38
since its alpha 2
08:38
<robehend1>
well, i'll have to test it. i've had a mixed bag with sabayon in the past. sometimes it works, other times, not so much
08:38
<Nubae>
but usable to look at and explore, bug report
08:39
calibre looks good, anyone use that?
08:39
<robehend1>
took a look at it, but didnt jump in. all my ebooks are just folder structured ;0
08:39
<dgroos>
alkisg: I've got 3 files in /var/lib/tftpboot/ltsp... so I don't get how the wild card, * would work?
08:40
<alkisg>
dgroos: it should work simultaneously in all 3 files
08:40
<Nubae>
ill give it a go on natty, could be interesting
08:40
<alkisg>
dgroos: try using ssh instead of nx, it's easier to copy/paste from there
08:40
<Nubae>
i have to say i like unity, what ive seen of it so far
08:40
<robehend1>
i guess i just spent to much time sorting the folders and making the file names exactly how i wanted to hand it off to another serivce
08:40
<Nubae>
its a bit like working with osx
08:40
<dgroos>
right :)
08:41
<robehend1>
when i played with it, it seemed nice and easy to use. should make it super easy for my users to get used to it
08:41
and i liked it much, much better than gnome3
08:43
<dgroos>
alkisg: I sshed into server, copied and pasted with sudo nano and got an empty file.
08:43
<alkisg>
dgroos: copy and paste the grep nbd command I wrote above
08:44
(04:30:58 PM) alkisg: grep nbd /etc/inetd.conf /var/lib/tftpboot/ltsp/*/pxelinux.cfg/default
08:44
<Nubae>
so is it just ubuntu that is going with unity as their default?
08:44
<robehend1>
i think so, since unity is canonicals baby
08:45
<dgroos>
grep nbd /etc/inetd.conf
08:45
9572 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbinnbdswapd
08:45
2000 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/fat-image.img
08:45
<Nubae>
sure buts its OS, so who knows
08:45
<alkisg>
dgroos: no, *all* of the line:
08:45
nbd /etc/inetd.conf /var/lib/tftpboot/ltsp/*/pxelinux.cfg/default
08:45
grep
08:45
<robehend1>
well, thats the glory of linux. if we dont like it, we simply remove it and add something we do like ;)
08:45
<root__>
incorrect login.. message in LTSP login ...
08:46NeonLicht has quit IRC
08:47
<alkisg>
The "defaults" do make a reason to switch distros sometimes though...
08:47
<dgroos>
alkisg: sorry, I'm lost. what should I type in?
08:47
<robehend1>
agreed. out of the box easy is a big sell
08:47
<alkisg>
dgroos: grep nbd /etc/inetd.conf /var/lib/tftpboot/ltsp/*/pxelinux.cfg/default
08:47
All of it. In a single line.
08:48
<dgroos>
http://pastebin.ubuntu.com/562561/
08:50
<alkisg>
dgroos: and this one: grep nbd /opt/ltsp/*/boot/pxelinux.cfg/default; ls -l /opt/ltsp/images
08:50
<dgroos>
append ro initrd=initrd.img quiet splash nbd_proxy=false nbdport=2000
08:50
total 1406228
08:50
-rw-r--r-- 1 root root 1439973376 2011-02-04 08:24 i386.img
08:51
<alkisg>
Hmmm it's very strange that ltsp-update-image --force didn't update your inetd.conf
08:51
That's a recent ubuntu version you're using, right?
08:51
<dgroos>
10.04, just updated the server and the chroot last night.
08:52
<alkisg>
Ah, it's adviced to create new chroots instead of upgrading them
08:52ogra_ac has joined #ltsp
08:53
<alkisg>
So now you can run: sudo gedit /etc/inetd.conf
08:53ogra_ac has quit IRC
08:53ogra has quit IRC
08:53
<alkisg>
Change fat-image.img to i386.img
08:53
And run: sudo invoke-rc.d openbsd-inetd restart
08:53ogra has joined #ltsp
08:54ogra has joined #ltsp
08:54
<alkisg>
But if you upgraded your chroot, better delete + recreate it with ltsp-build-client
08:54
bbl
08:54
<dgroos>
thanks!
08:56NeonLicht has joined #ltsp
08:56
<simbulu>
it is a bit annoying that I have to remove /opt/ltsp/i386 before running ltsp-build-client. Perhaps I could just "mv i386 i386-old && ltsp-build-client && rm -rf i386-old" ?
08:57
<robehend1>
why not just use the --chroot tag and build the client with a different name/
08:58alkisg has quit IRC
08:59
<simbulu>
robehend1, "ltscp-build-client --chroot /opt/ltsp/new && mv /opt/ltsp/new/i386" ? mm that might work as well
09:00
<robehend1>
i'd assume so. i just go with ltsp-build-client --chroot newi386 , myself. as long as i know what the chroots are, its usually fine
09:01
<dgroos>
robehend1 THANKS for getting things going and I'm off to my meeting! works great. Wish I could remember all that I just did...
09:02
<robehend1>
dgroos: heh, i've added it to my book of things to check, after i clean up some edits, ill get ya a link
09:02
<dgroos>
take it easy :)
09:03dgroos has quit IRC
09:09robehend1 has left #ltsp
09:20root__ has quit IRC
09:33bobby_C has joined #ltsp
10:25staffencasa has joined #ltsp
10:29alkisg has joined #ltsp
10:35komunista has joined #ltsp
10:35gnunux has quit IRC
10:39dobber has quit IRC
11:04xet7 has joined #ltsp
11:23litlebuda has joined #ltsp
11:27rpm_ has quit IRC
11:28[GuS] has quit IRC
11:30mistik1 has joined #ltsp
11:38litlebuda has quit IRC
11:39[GuS] has joined #ltsp
11:56otavio has quit IRC
12:09NeonLicht has quit IRC
12:16klausade has quit IRC
12:18NeonLicht has joined #ltsp
12:24alkisg has quit IRC
12:24alkisg1 has joined #ltsp
12:44vagrantc has joined #ltsp
12:53shawnp0wers has quit IRC
12:55robehend1 has joined #ltsp
12:56Gibby has joined #ltsp
12:58
<Gibby>
I am trying to add another nfs mount to my fat clients /etc/fstab, however the server will not boot with it in, even with _netdev it seems to want to try to mount it before the network is ready, it seems like a package is missing to understand the _netdev option in /etc/fstab... am I on the right track?
12:59
<alkisg1>
Distro/version?
13:01
<Gibby>
ltsp server is ubuntu 10.04.1 and fatclient is mythtbuntu 10.04.1
13:01
<alkisg1>
How are you adding the entry to fstab?
13:02
<Gibby>
xxx.xxx.xxx.xxx:/export/fs /mnt/fs nfs _netdev,defaults 0 0
13:02drdata has quit IRC
13:02
<alkisg1>
No I mean how did you put it there. You're just editing the chroot fstab?
13:02drdata has joined #ltsp
13:03
<alkisg1>
Normally, fstab is autogenerated on boot
13:03
<Gibby>
yes i shutdown the fatclient, edit the chroot, exit update image and boot
13:03
<alkisg1>
And if you cat /etc/fstab from the fat client, do you see your changes?!
13:03
<Gibby>
yes
13:05robehend1 has quit IRC
13:05komunista has quit IRC
13:06
<Gibby>
i am working with another user having the same issue, i have tested this in the last 3 weeks, I have new hardware coming today so I will be able to test more, I was just wondering if this was a common issue and/or it was because of a missing package
13:06
<vagrantc>
have you disabled auto-generation of /etc/fstab?
13:06
<Gibby>
meant haven't tested this in the last 3 weeks
13:06
vagrantc: no I have not
13:06
<vagrantc>
then i don't see how it would possibly contain your changes
13:06
because it gets generated on boot, as alkisg1 said
13:07
<Gibby>
this is a fat client and not a thin client, does that matter?
13:07alkisg1 is now known as alkisg
13:07
<vagrantc>
i don't think so
13:07
<alkisg>
Gibby: is this the "stock" ubuntu fat client implementation, or a custom one of your own?
13:07
<Gibby>
this is the "stock" mythbuntu fat client
13:08
<alkisg>
Gibby: so you used "ltsp-build-client --fat-client-desktop"?
13:08
!fatclients
13:08
<ltspbot>
alkisg: "fatclients" :: You may find some info about the Ubuntu/LTSP implementation of fat clients at https://help.ubuntu.com/community/UbuntuLTSP/FatClients
13:09
<Gibby>
nope, used ltsp-build-client --mythbuntu
13:09
<Nubae>
mythbuntu is not the same
13:09
mythbuntu is ancient
13:09
<alkisg>
Ah, ok, never saw that one, something like the kiosk setup I imagine
13:09
<Nubae>
similar to mine
13:09
right, based on kiosk
13:10
very much doubt it works at all
13:10
<Gibby>
i can't bounce the box right now, since my wife is using it to watch TV and I am at work, but i will try playing with it again in a few hours
13:10
<alkisg>
Gibby: do you have CONFIGURE_FSTAB=False in lts.conf?
13:11
<Gibby>
it works wonderfully, just rebuilt the image last weekend and about once a month, update all the packages
13:13
alkisg, yes it is in there
13:13
<alkisg>
So the answer to " (09:06:56 PM) vagrantc: have you disabled auto-generation of /etc/fstab?" is "yes"...
13:14
<Gibby>
ahh but i did not
13:14
so maybe on the mythbuntu fatclient build it changes it to false,
13:15
<alkisg>
"disabling auto-generation of /etc/fstab" means "adding CONFIGURE_FSTAB=False" in lts.conf
13:15
lts.conf doesn't exist by default, so if it's there, you put it there...
13:16
<Gibby>
no i did not put it in there nor ever touch lts.conf, didn't even know where it was located, it is probably done by ltsp-build-client --mythbuntu
13:16
<alkisg>
Ah. OK, that's possible.
13:17
<vagrantc>
mythbuntu may have put it there
13:17
<alkisg>
...althought I don't see it in the sources
13:17
The only mention of CONFIGURE_FSTAB in the ltsp source tree is in ltsp-init-common. Anyway.
13:18
Gibby: if, after the client boots, you try on the client as root: mount /mnt/fs, does it work?
13:18
<Gibby>
that brings me to another question.... how/who/is the --mythbuntu option maintained?
13:18
yes, if i add noauto to the line, it boots fine, than i just run mount /mnt/fs and it works
13:19
logs show it trying to mount it prior to the network being up
13:20
<alkisg>
Gibby: you're correct for lts.conf, 030-mythbuntu put CONFIGURE_FSTAB there
13:20
It appears to be an ubuntu-specific plugin, not in the upstream tree, so it's probably maintained in launchpad by the ubuntu/ltsp maintainer, stgraber
13:21
The network is up from the initramfs and on. So maybe upstart doesn't trigger the "network up" event.
13:22
<Gibby>
that is a possibility, i could try building a ubuntu desktop fatclient and adding the myth packages and try it that way i guess too
13:22
<alkisg>
Try omitting the _netdev completely
13:23
<Gibby>
tried that too
13:23
<alkisg>
what was the result?
13:23
<Gibby>
same thing
13:23
<alkisg>
Hmm it doesn't make sense then
13:23
<Gibby>
i know, but it works on a regular ubuntu desktop/server
13:24
<alkisg>
You can use NFS_HOME if it helps, and have /home mounted by nfs instead of /mnt/fs
13:24
(in lts.conf)
13:24
<Gibby>
they only thing i am trying to mount is my music folder so myth can access it
13:25
i have a script that works, it is just a why doens't this work right thing, that i am trying to fix so others won't have the issue
13:26
<alkisg>
Ah. Mythbuntu even blacklists ltsp-client-core?
13:27
<Gibby>
i don't know, where would i check that? don't see it in modprobe.d
13:27komunista has joined #ltsp
13:28
<alkisg>
I'm reading /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu/030-mythbuntu
13:29
<Gibby>
ahhhh so this is what it does while building cool
13:29
<alkisg>
Also I see that it messes with the RC_WHITELISTS
13:29
Maybe it deletes the necessary /etc/init/* files that bring up fstab (like mountall or something)
13:30
<Gibby>
ltsp-client-core is in my /etc/init.d folder
13:32
<alkisg>
There are symlinks for those in rc dirs
13:32
rc2.d/S25ltsp-client-core
13:33
<Gibby>
nope
13:33
just a kill for it
13:33
<simbulu>
I was told that the clients connect to the server using something like "ssh -X user@ltspserver CMD". Which CMD is used ?
13:35
<alkisg>
ssh -Y -t -S $LDM_SOCKET -l $LDM_USERNAME $LDM_SERVER "$CLIENT_ENV $MY_LANG $MY_DISP $MY_SCANNER $MY_SOUND $LDM_XSESSION $LDM_SESSION < /dev/null > /dev/null $MY_LOCALDEV"
13:35
From X95-run-x-session
13:38
<Gibby>
looks like it is using /etc/init.d/networking to start network instead of the upstart job /etc/init.d/network-interface
13:38
<alkisg>
Gibby: btw I didn't mean that you need to put ltsp-client-core in rc.d, I meant that the mythbuntu plugin changes a lot in the standard ltsp chroot installation, so that I can't help you in troubleshooting the problem...
13:38
<Gibby>
i will be back in a few hours anyway, kinda hard to troubleshoot when i can't bounce a client
13:39
<alkisg>
No networking scripts should be called as the connection is already up from the initramfs
13:40
<Gibby>
thats in initramfs-tools?
13:40
<alkisg>
in $CHROOT/boot/initrd
13:41
(which is generated by initramfs-tools)
13:41
<simbulu>
alkisg, Thanks.
13:41
<Gibby>
hmm only have a initrd.img
13:43
<alkisg>
Yes, that's the initramfs.
13:45
<Gibby>
ahh ok
13:46
is there away to suspend to ram a fat client?
13:47
<vagrantc>
same way you would do on any other computer, no?
13:48
<Gibby>
not exactly, since it shut downs the network
13:51
<vagrantc>
yes, i suppose some network timeouts might cause issues...
13:52robehend1 has joined #ltsp
13:54
<Gibby>
it will suspend to ram, just doesn't wake up
13:56
<alkisg>
adding -persist to nbd-client and disabling any network swap might help...
14:00
<Gibby>
i might attempt it again, would rather work on my pxelinux.cfg so i can network boot multi images/boot cd's
14:00
<robehend1>
grr, wish i had a 10.10 machine around. now iw ant to try this 2d Unity
14:01
<alkisg>
That's 11.04 then ;)
14:01
<robehend1>
theres a ppa for 10.10
14:02komunista has quit IRC
14:02
<robehend1>
ppa:unity-2d-team/unity-2d-daily
14:04komunista has joined #ltsp
14:05robehend1 has left #ltsp
14:05simbulu has quit IRC
14:05Gremble has joined #ltsp
14:07Gremble has quit IRC
14:22brendan`- has joined #ltsp
14:24
<brendan`->
anyone ever have an issue with thin clients seemingly not waking up after going into screensaver? by seemingly i mean, the mouse is there and can move around, but no unlock window comes up. if user carefully types their password it will unlock and come back. but it's very confusing to most of my users
14:24
i'm on ubuntu
14:24
10.04
14:25
this actually coninsides with upgrading to 10.04
14:31cliebow has joined #ltsp
14:50komunista has quit IRC
14:50komunista has joined #ltsp
14:57Elevator has joined #ltsp
14:57
<Elevator>
I need assistance with a little test. I need a phone number to call, so that I can check whether my caller ID is hidden or not. Could someone give me theirs?
14:59cliebow has quit IRC
15:02[GuS] has quit IRC
15:02Elevator has quit IRC
15:14brendan`- has quit IRC
15:18Kicer86 has quit IRC
15:26NeonLicht has quit IRC
15:27RiXtEr has quit IRC
15:28RiXtEr has joined #ltsp
15:32RiXtEr has quit IRC
15:32RiXtEr has joined #ltsp
15:37mgariepy has quit IRC
15:38NeonLicht has joined #ltsp
16:21litlebuda has joined #ltsp
16:30drdata has quit IRC
16:30drdata has joined #ltsp
16:31drdata has left #ltsp
16:36litlebuda has quit IRC
16:51alkisg has quit IRC
16:51alkisg has joined #ltsp
17:12Nubae has quit IRC
17:13Nubae has joined #ltsp
17:20robehend1 has joined #ltsp
17:20
<robehend1>
which would be better for LTSP, Raid0, 1, or 5? I'm leaning Raid 1, with 1 volume for OS, 1 for home
17:21
<vagrantc>
depends on what you need.
17:21
<robehend1>
ah, the fun question. as always, the best mix of speed + reduncy
17:21
er, redundancy*
17:21
<vagrantc>
raid0 is good for fast writes and fast reads, but prone to failure (i.e. 1 disk failure fails the whole thing)
17:22
raid1 is good for fast reads, slow writes, and is fault tolerant
17:22bobby_C has quit IRC
17:22
<robehend1>
is raid1 still that slow? i thought performance had increased
17:22
<vagrantc>
it's as fast as the slowest disk
17:22
it's impossible for it to be faster
17:22
<robehend1>
hmm. well, luckily their all identical 10k scsi
17:22
<vagrantc>
but reads are as fast as the fastest disk
17:23
(and concurrent reads means that multiple reads can happen simultaneously
17:23
)
17:24
<robehend1>
hmm
17:24
think i'll go with raid1. I dont have enough disks to make an effective raid5, sadly. only 4, and I cant afford to lose the space
17:26
so, heres my plan, let me know if you think its a decent one: install kvm on a 64 bit 10.04 box, then throw edubuntu in as a virtual machine for ltsp. take the /home raid volume, and mount it as the Vm's home. so, the OS will be on one raid1 array, while /home will be on another raid1 array. does it sound decent, or jsut plain foolish?
17:39
<vagrantc>
raid5 will get you more space than raid1
17:39
or raid6
17:40
i.e. raid1 has as much space as the smallest disk
17:40
but i guess two raid1 arrays would, one for the OS, one for /home, is not unreasonable
17:41
though at that point i'd recommend using lvm on top of raid10 or raid6
17:42
<robehend1>
sadly, raid controller wont support raid10
17:42
<vagrantc>
ah, hardware raid
17:42komunista has quit IRC
17:43
<robehend1>
now i just have to figure out how to make the LTSP vm see the /home volume, so i can mount it..
17:45
or would it make more sense to use nfs to export it from the kvmhost box, and just mount it via that on the LTSP vm
17:48xet7 has quit IRC
17:56vagrantc has quit IRC
17:59
<robehend1>
alkisg: is it possible to run sch-scripts with full functionality on a different machine than the LTSP server?
18:02Nubae has left #ltsp
18:03
<alkisg>
robehend1: from thin clients, sure. From fat clients, not easily, as the socket for the communication with the daemon is on the server, at /var/run/sch-scripts/sch-daemon.socket
18:03
<robehend1>
how about from a stand-alone ubuntu 10.10 box?
18:04
<alkisg>
The same as with fat clients
18:04
A few lines need to be changed in the sources for this to be possible
18:04
I.e. to change the socket with a tcp/ip communication
18:04
<robehend1>
hmm, ok. it runs nicely in virt-manager, so that'll work for me for now ;)
18:04
figured i'd check if i could save myself a few clicks is all
18:04
<alkisg>
(it was tcp/ip initially, but we switched to socket-based for security :D)
18:04
<robehend1>
agreed
18:05
i had the fun of discovering a kid with Wireshark on his thumbdrive today, so i have a refreshed view of encryption :D
18:05
<alkisg>
Heh, I hope I'll see that here too someday
18:05
It'll mean that we've done a good job educating them :D
18:05
<robehend1>
now if only I could figure out why my freshly installed 10.04 server is only downloading at 25 kB/s... when its on a direct gig ;)
18:05
heh, the kids my new teachers assistant
18:06
<alkisg>
Late here, night all...
18:06
<robehend1>
see ya!
18:06alkisg has quit IRC
18:35staffencasa has quit IRC
19:31mordocai has joined #ltsp
20:04
<robehend1>
is there any reason why all my commands through apt-get would be horrendously slow, but browsing the internet would be normal/
20:16
<HrdwrBoB>
yep
20:16
lots of reasons
20:16
probably because you're using a proxy in your browser and not from apt-get
20:18
<robehend1>
actually, no proxy. it's running just like it did out of the box
20:19
i hopped into my firewall for my lan, saw nothing that'd be holding it back, and speedtests from multiple machines are showing i've got my full 6 megs wide open. its a dedicated 6 megs, btw, so not one of those lovely cable things
20:19
but i'm still pulling 20-50 kb/s max on apt-get
20:20
<HrdwrBoB>
then it's probably the server you're downloading from
20:22
<robehend1>
hmm. i thought that at first as well, but it did the same for 2 unrelated packages, ltsp-server and chromium-browser. chromium comes from a completely different ppa
20:39robehend1 has quit IRC
20:47NeonLicht has quit IRC
20:48mordocai has quit IRC
20:49mordocai has joined #ltsp
20:58mordocai has quit IRC
21:00mordocai has joined #ltsp
21:00NeonLicht has joined #ltsp
21:44MorningSon has quit IRC
22:19F-GT has quit IRC
22:21cyberorg has quit IRC
22:26RiXtEr has quit IRC
22:26RiXtEr has joined #ltsp
22:28RiXtEr has joined #ltsp
22:36F-GT has joined #ltsp
22:46NeonLicht has quit IRC
22:54NeonLicht has joined #ltsp
23:31root__ has joined #ltsp
23:32
<root__>
login incorrect .... in LTSP.. can anyone help???
23:39
hi...