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


Channel log from 14 August 2013   (all times are UTC)

00:09
<bennabiy>
Well, I booted my first vbox client and got a busybox, but I thnik it was because I did not restart the tftp daemon
00:09
!seen askisg
00:09
<ltsp>
I have not seen askisg.
00:32vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
00:5317WACBZBO <17WACBZBO!~paco@187-162-80-141.static.axtel.net> has left #ltsp
01:20Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
01:57
<Enslaver>
low all
02:34Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Read error: Connection reset by peer)
02:53Fenuks has joined IRC (Fenuks!~Fenuks@109.202.17.10)
02:56sbalneav has left IRC (sbalneav!~sbalneav@mail.legalaid.mb.ca, Ping timeout: 240 seconds)
03:09sbalneav has joined IRC (sbalneav!~sbalneav@mail.legalaid.mb.ca)
03:16sbalneav has left IRC (sbalneav!~sbalneav@mail.legalaid.mb.ca, Ping timeout: 264 seconds)
03:18sbalneav has joined IRC (sbalneav!~sbalneav@mail.legalaid.mb.ca)
03:24cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 264 seconds)
04:24Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Read error: Operation timed out)
05:32monteslu_ has left IRC (monteslu_!~monteslu@ip68-2-99-223.ph.ph.cox.net, Ping timeout: 246 seconds)
05:47monteslu_ has joined IRC (monteslu_!~monteslu@ip68-2-99-223.ph.ph.cox.net)
06:06wvsfxr has joined IRC (wvsfxr!~Thunderbi@77.119.227.112.static.drei.at)
06:41alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
08:58Gremble has joined IRC (Gremble!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com)
09:30Gremble has left IRC (Gremble!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com, Quit: I Leave)
09:55lifeboy has joined IRC (lifeboy!~roland@105-236-170-173.access.mtnbusiness.co.za)
09:57Gremble has joined IRC (Gremble!~Ben@bmex-gw.bristolwireless.net)
10:25alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
10:26adrianorg_ has left IRC (adrianorg_!~adrianorg@177.204.151.152.dynamic.adsl.gvt.net.br, Ping timeout: 276 seconds)
10:38adrianorg_ has joined IRC (adrianorg_!~adrianorg@177.204.151.152.dynamic.adsl.gvt.net.br)
10:45Tatanka_ has joined IRC (Tatanka_!~tim@193.190.253.107)
10:46boss has joined IRC (boss!~boss@218.248.24.19)
10:46
<boss>
hi all
10:47boss is now known as Guest55193
10:47Guest55193 is now known as prem1
10:47
<prem1>
when i connect a usb printer in LTSP client , its not getting detected
10:47
if i connect and configure the printer in server, then i can give print from the ltsp client
10:48
but on connecting the same printer in client end., its not working
10:48
how to make it work
10:50
<rickogden>
prem1: are you using fat or thin clients?
10:50
<prem1>
i guess thin clients only rickogden
10:51
i followed the wiki from debian , simply ran "ltsp-build-cleint" and the client booted
10:51
its as simple as that., awesome
10:51
but stuck only with this printer issue
10:54
<rickogden>
prem1: hmm, not done it with a thin client. Do you have local devices enabled in your lts.conf?
10:55
<prem1>
rickogden, by default it is enabled na
10:59
<rickogden>
what about if you put into the lts.conf something like:
10:59
PRINTER_0_DEVICE=/dev/usb/lp0
10:59
PRINTER_0_TYPE=U
11:00
(assuming it's a USB printer)
11:01
<prem1>
yes it is a usb printer,
11:01
rickogden, let me chk with this option and come back
11:01
rickogden, but before that., the printer itself is not getting detected when i connect it locally
11:02
so putting a value like "PRINTER_0_DEVICE=/dev/usb/lp0" will it work?
11:02
<mnemoc>
detected by whom?
11:02
<prem1>
its not detected by the client machine mnemoc
11:02
<mnemoc>
confirmed ssh-ing in?
11:03
<prem1>
lsusb doesnt show up the printer
11:03
<mnemoc>
lsusb run on the client interface will show you the server
11:03
not the client
11:03
<prem1>
mnemoc, so how can i see what are all the devices connected to the client
11:04
<mnemoc>
prem1: ssh in
11:04
or enable debugging consoles
11:04
but ssh is better
11:04
<prem1>
mnemoc, "ssh in" is it the full command
11:04
<mnemoc>
no.... it's and action, not a command
11:05
install openssh-server in the chroot, inject your ssh public key, recreate the image, reboot the client, connect to the client ip using ssh
11:05
and run lsusb
11:06
<prem1>
okey
11:06Gremble has left IRC (Gremble!~Ben@bmex-gw.bristolwireless.net, Disconnected by services)
11:06
<prem1>
in this way will i be able to view devices connected to the client
11:06GrembleBean has joined IRC (GrembleBean!~Ben@bmex-gw.bristolwireless.net)
11:06
<mnemoc>
yes
11:07
but you can also asume it is been detected and just blindly modify lts.conf
11:10GrembleBean has left IRC (GrembleBean!~Ben@bmex-gw.bristolwireless.net, Client Quit)
11:32
<prem1>
tried both the localdev and printer options in lts.conf., but of no use rickogden
11:35
still the printer is not configurable in client end
11:40
<mnemoc>
ssh in
11:40F-GT has left IRC (F-GT!~phantom@ppp59-167-136-109.static.internode.on.net, Ping timeout: 240 seconds)
11:51Fenuks has left IRC (Fenuks!~Fenuks@109.202.17.10, Ping timeout: 276 seconds)
11:53brunolambert has joined IRC (brunolambert!brunolambe@nat/revolutionlinux/x-rkkxihcvfkqqapws)
11:54F-GT has joined IRC (F-GT!~phantom@ppp59-167-136-109.static.internode.on.net)
11:54TatankaT has joined IRC (TatankaT!~tim@193.190.253.114)
11:54
<prem1>
mnemoc, yeah i installed openssh-server in the chroot environment, and trying to ssh to the client., but its not happening
11:55
my server ip is 192.168.1.5 and client ip is 192.168.1.22., in chroot am trying "ssh test1@192.168.1.22"
11:55
is that okey
11:57
<mnemoc>
prem1: do you have a test1 account in the chroot?
11:58
<prem1>
no
11:58
mnemoc, its in the server
11:58Tatanka_ has left IRC (Tatanka_!~tim@193.190.253.107, Quit: krista is back)
11:58
<mnemoc>
prem1: then it won't work.
11:59
<prem1>
okey., mnemoc i created a user "new" inside the chroot
11:59
<mnemoc>
prem1: easiest is to use root, and inject your public key in chroot's /root/.ssh/authorized_keys
11:59
<prem1>
even now "ssh new@192.168.1.22" is not working
11:59
<mnemoc>
also don't forget to recreate the image
12:11brunolambert has left IRC (brunolambert!brunolambe@nat/revolutionlinux/x-rkkxihcvfkqqapws, Ping timeout: 245 seconds)
12:22TatankaT has left IRC (TatankaT!~tim@193.190.253.114, Ping timeout: 276 seconds)
12:24brunolambert has joined IRC (brunolambert!brunolambe@nat/revolutionlinux/x-uejomdexujjqhaou)
12:28
<bennabiy>
!seen alkisg
12:28
<ltsp>
alkisg was last seen in #ltsp 17 hours, 8 minutes, and 32 seconds ago: <alkisg> No, I'm only using LTS releases
12:30prem1 has left IRC (prem1!~boss@218.248.24.19, Ping timeout: 264 seconds)
12:43TatankaT has joined IRC (TatankaT!~tim@193.190.253.114)
12:53jammcq has left IRC (jammcq!~jam@c-69-245-75-255.hsd1.mi.comcast.net, Quit: WeeChat 0.3.7)
12:55freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
13:05brunolambert has left IRC (brunolambert!brunolambe@nat/revolutionlinux/x-uejomdexujjqhaou, Ping timeout: 245 seconds)
13:10
<lifeboy>
Hi all, I have a quirk I can't pinpoint and not sure if it's due to LTSP or not. When a thin client starts Xsession (after booting succesfully), when the user select "Gnome classic" from the preferences menu on the LDM login screen, the error "Xsession: unsupported number of arguments (2); falling back to default session." is displayed.
13:12
I've traced the source to /etc/X11/Xsession.d/20x11-common_process-args, which check the number of arguments in /etc/X11/Xsession.options and if there is more than one option given (per line I think?), this error occurs.
13:12
However, there isn't more than one option per line in that file.
13:14
The strangeness of this is this: It works for all users, except for one of them. Previously I had this issue with another user, but because I couldn't trace it, I deleted the profile and restored the user's files but not the config and the problem didn't re-appear.
13:15
However, I want to solve this my finding the cause of it, since it's bound to happen with another user in future.
13:15
s/my finding/by finding/
13:16
If I log in as this user using NXclient, all is well. The error does not occur. It only happens from a thin client logon.
13:18brunolambert has joined IRC (brunolambert!brunolambe@nat/revolutionlinux/x-gqfyaehplbjrardz)
13:18PhoenixSTF has joined IRC (PhoenixSTF!~rudi@lidet.uac.pt)
13:18
<lifeboy>
and only for that one user
13:19
So it seems that there is something in that client's LTSP config that might be causing this, hence my question here.
14:11markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
14:39
<other_other_joe>
admittedly no expert on ltsp here but I could bounce some ideas off of you if you'd like
14:42
I'd say, if you're running thin rather than fat clients, see if you can start an x session with that user on the host server using startx
14:42
the error there may be a lot more helpful
14:43
I'd also make sure your client was able to log to your host so you can get a look at the logs
14:46
and finally,as a just figure out what file it's related to effort, I'd just move an X related file out of their home at a time until it works
14:46
then at least you'd know where to look
15:00PhoenixSTF has left IRC (PhoenixSTF!~rudi@lidet.uac.pt, Quit: Leaving)
15:13markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
15:47freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish)
15:48Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
16:08cliebow has left IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us, Ping timeout: 264 seconds)
16:32staffencasa has joined IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu)
16:48PhoenixSTF has joined IRC (PhoenixSTF!~rudi@lidet.uac.pt)
16:58mgariepy has left IRC (mgariepy!mgariepy@ubuntu/member/mgariepy, Ping timeout: 264 seconds)
16:59bennabiy has left IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com, Ping timeout: 256 seconds)
17:00bennabiy has joined IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com)
17:04mgariepy has joined IRC (mgariepy!mgariepy@ubuntu/member/mgariepy)
17:15
<bennabiy>
!seen alkisg
17:15
<ltsp>
alkisg was last seen in #ltsp 21 hours, 55 minutes, and 1 second ago: <alkisg> No, I'm only using LTS releases
17:15
<bennabiy>
bah
17:16
anyone know where all the PA config files are in ltsp?
17:16
PA = pulseaudio
17:18
<gvy>
might be in /usr/share, dunno about current situation
17:27
<bennabiy>
I have an install of 12.04 which the audio works fine, and an install of mint 15 where it doesnt
17:27
I want to compare configs
17:37vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
17:40
<bennabiy>
vagrantc: welcome
17:41* vagrantc waves
17:41
<bennabiy>
Do you know offhand where the system configs for pulseaudio would be under ltsp? (both for the client side and the server side )
17:42
I know on the client image, it is called in system mode
17:42
but where is that call made?
17:42* bennabiy is bug stomping!
17:48
<vagrantc>
on debian it's fired off from the ltsp-client* init script, i think.
17:52
<bennabiy>
what about ubuntu?
17:55
<digitalirony>
I am using ubuntu ltsp, and its acting straaaange
17:55
<bennabiy>
whats it doing?
17:55
<digitalirony>
I installed gnome, and unitity disapeared, and I re-installed unity, and now in the session menu it just says 'ubuntu' but if I choose that, it says its not defined?
17:56
also, in gnome, the little 'gear/power' button in the top right hand corner is missing....I tried adding it back from the applet menu, but its not even there
17:56
<bennabiy>
is this on your client, or on the server itself?
17:56
<digitalirony>
there is one that says 'null' 'check for out of date applets' but I am not sure whats going on
17:56
the client
17:57
<bennabiy>
Are you able to use the sessions normally on the server?
17:57
if you log into it?
17:57
<digitalirony>
yeah
17:57
hrmm
17:57
<bennabiy>
which ubu ?
17:57
<digitalirony>
I have ubuntu 12.04 image that I use for our system right now, just a regular desktop install
17:58
would it be difficult to just convert that to an image for ltsp to use?
17:58
ubuntu 12.04
17:59
<bennabiy>
I thought 12.04 came with gnome-default for those who didnt want to use unity.. I have 12.04 running in a VM server right now
18:00
<digitalirony>
it did for the desktop install
18:00
but on ltsp it only had unity
18:00
<bennabiy>
ever tried MATE?
18:00
<digitalirony>
that is, the ubuntu ltsp install from the alternatives cd
18:00
never tried mate
18:00
what is it
18:00
<bennabiy>
MATE is like gnome used to be
18:01
gnome2 fork which is becoming quite popular in the mint realm
18:01
<vagrantc>
i think sbalneav (one of the long-time LTSP developers) uses MATE
18:01
<bennabiy>
It is very nice
18:01
<digitalirony>
really, it would be awesome if I could just figure out how to take the existing image that I use for my pcs, and get ltsp to serve that
18:01
<bennabiy>
very fast too
18:02
are you trying to run thin or fat?
18:02
<digitalirony>
thin
18:02
<vagrantc>
!ltsp-pnp
18:02
<ltsp>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
18:02
<digitalirony>
the image I use is pretty much already thin
18:02
<vagrantc>
digitalirony: ^^
18:02
<digitalirony>
the home dirs and stuff are all nsf mounts
18:02
<bennabiy>
nice plug... ;)
18:02
<vagrantc>
oh, ltsp-pnp is fatclients
18:03
bug basically it builds an LTSP image of the server installation
18:03
<digitalirony>
it says thin and fat
18:03
<bennabiy>
for thin with fat ram
18:03
<vagrantc>
it does also work for thin clients, although then you may as well just do regular LTSP
18:04
<digitalirony>
oh
18:04
<vagrantc>
i would only recommend ltsp-pnp method if you were going to use fat clients primarily, and have a few thin clients
18:04
<digitalirony>
I just want to convert the image I use for my desktops to serve through tsp
18:04
ltsp
18:04
<vagrantc>
that's what ltsp-pnp does...
18:05
<digitalirony>
then im lost as to why I shouldn't use it
18:05
<vagrantc>
maybe you're not understanding the term thin vs. fat?
18:05
<bennabiy>
that is what I was thinking
18:06
<digitalirony>
fat == hard drive?
18:06
<vagrantc>
not in this case
18:06
<digitalirony>
or fat like, runs apps locally
18:06
<vagrantc>
yeah, running all applications locally on the client hardware, but booted off the network
18:06
<digitalirony>
yeah, I don't want that
18:07
<vagrantc>
what did you mean by "I just want to convert the image I use for my desktops to serve through tsp", then?
18:07
that's what the thin client model does.
18:07
<digitalirony>
I want the apps to run on the server instead?
18:07
<vagrantc>
i don't know what you want.
18:08
<bennabiy>
digitalirony: It sounds like you need to fix your server install. The client image basically only loads the essentials for using your local hardware, and ldm, everything after that point is on the server, including the session available
18:08
<digitalirony>
I have an image I built on ubuntu 12.04, that has a bunch of desktop modifications, and it would be a pain to do it again
18:08
<bennabiy>
It is your server which needs to be repaired
18:08
<vagrantc>
digitalirony: ok, if you want the apps to run on the server, then you want a thin client model.
18:09
digitalirony: so you would image your server just like the desktop image you want...
18:09
<digitalirony>
vagrantc: yes, but, I want it to serv all the modifications, and shit I made to gnome on the old pcs I am using right now that run from HDD
18:09
<vagrantc>
and hope that the programs you rely on aren't so buggy as to be unuseable over the network.
18:09
<digitalirony>
vagrantc: but I thought it served the image from /opt/ltsp/amd64/ ?
18:09
gah im confused now
18:10
the stuff in /opt/ltsp/amd64 isn't a full install?
18:10
<vagrantc>
correct.
18:10
<digitalirony>
oh
18:10
<vagrantc>
it's a minimal thin client os
18:10
which connects to the server to run applications
18:10
<digitalirony>
so, it doesn't work like a VM
18:10
<vagrantc>
(unless you're running fat clients)
18:11
it's unrelated to VM
18:11
<digitalirony>
ahh
18:11
<vagrantc>
i.e. you can run VM clients, VM servers, etc.
18:11
<digitalirony>
I was thinking this whole time, that I was building a VM type image, and serving it via PXE
18:11
<bennabiy>
digitalirony: It is only enough to be able to get you to a graphical login which then connects over ssh to the server where everything happens
18:11
<vagrantc>
VM clients connecting to baremetal servers, baremetal clients connecting to VM servers, etc...
18:11
<digitalirony>
and that it was modified somehow to use server resources
18:12
<vagrantc>
your imagination overengineered it :)
18:12
<digitalirony>
lol
18:12
<bennabiy>
heh
18:12
<digitalirony>
its waaaay easier than I thought
18:12
<vagrantc>
yes.
18:12
<digitalirony>
I guess thats what I fucked up
18:12
<vagrantc>
at least, we like to think so
18:12
<digitalirony>
I chrooted the ltsp
18:12
and installed gnome
18:13
instead of on the server
18:13
<bennabiy>
that would do it
18:13
<vagrantc>
it would probably default to fat clients then
18:13
if your clients had enough ram
18:13
<digitalirony>
heheh
18:13
ok
18:13
so imma just try and install the image that we use for desktops
18:13
update the hell out of it
18:13
<vagrantc>
digitalirony: think of the thin clients as extra monitor, mouse and keyboard for the server.
18:13
<digitalirony>
get rid of puppet, and then install tlsp
18:13
<bennabiy>
You might be best to just rm -rf /opt/ltsp/* and start your build over
18:13
<digitalirony>
vagrantc: I was thinking of it that way
18:13
vagrantc: I was just thinking of the build process wrong
18:14
<vagrantc>
sure
18:14
<digitalirony>
well, the serv process heh
18:14
<vagrantc>
digitalirony: typically, you only install your applications on the server itself... no need to mess with the chroot
18:14
<digitalirony>
ahhhh
18:14
its clear now
18:15
<vagrantc>
there are features to make it more complicated and confusing, but that's the basic model :)
18:15
<bennabiy>
The only time you really need to mess with the chroot is to update it after an IP change and doing ltsp-update-sshkeys then ltsp-update-image
18:15
<digitalirony>
yeah
18:15
I seeee
18:15
this is gonna bee waaaaaaaay quicker
18:15
<lifeboy>
other_other_joe: Thanks for the tips. My client logs to the server on the user's ~/.xsession-errors. The strange thing is that the file that supposedly has 2 arguments is in /etc/X11, so it applies to all clients, but none get the error. I'll try the startx option on the server and see what I get then
18:15
<bennabiy>
and even then, you dont need to actually mess with the chroot
18:15
<digitalirony>
I will totally just use my image
18:16
most of the apps we run run from an app server
18:16
we just mount mathapps:/share/bin /usr/msri/bin
18:16
and then have desktop icons made and menu items etc
18:16
<bennabiy>
Basically, set up the server with the image you want, and then install ltsp-server-standalone on it
18:17
do a few tweaks, and there you have your setupi
18:17
<digitalirony>
I don't even need dhcp on there
18:17
just pxe and ltsp serv
18:17
thanks guys!
18:17
<bennabiy>
good luck!
18:17
<digitalirony>
soooo much less work than rebuilding it all
18:21
<vagrantc>
bennabiy: recent versions shouldn't matter with ip address changes either
18:21
<bennabiy>
for your ssh keys? interesting
18:21
even if the server IP changes?
18:21
<vagrantc>
yes
18:22
<bennabiy>
hmm. Good to know
18:22
<vagrantc>
we disabled the hostip change detection in ldm
18:22
<bennabiy>
I really wish we could just trash ldm for something a little more configurable
18:22
<vagrantc>
just do matching of the ssh host key ... if someone's managed to steal your server's host key, the ip address being different won't matter all that much
18:23
ldm goes away in ltsp6
18:23
<bennabiy>
someone was saying that in 6 it would allow for choosing lightdm or some such
18:23
<vagrantc>
but ldm is *extremely* configurable
18:23
<bennabiy>
if you recompile?
18:23
<vagrantc>
that's not why we should get rid of it
18:23
bennabiy: it has dozens of hook scripts it runs that you can plug into, override, etc.
18:23* bennabiy must just not know what I am doing... or it is not documented
18:24
<vagrantc>
it is not well documented
18:24
but the plans for ltsp6 will be much cleaner ... though may actually be less flexible
18:24
allowing use of just about any display manager
18:25
though fewer places to hook into
18:25
<bennabiy>
vagrantc: do you know why my system would not read /opt/ltsp/i386/etc/ltsp/update-kernels.conf to keep changes in the pxelinux.cfg/default file?
18:25
<vagrantc>
bennabiy: i seem to recall ubuntu 12.04 making some last minute changes where it reads from the existing .img file rather than the chroot
18:25
<bennabiy>
Can you point me to any documentation on the hook scripts?
18:26
<vagrantc>
bennabiy: the scripts themselves...
18:26
<bennabiy>
I am using mint 15
18:26
<vagrantc>
bennabiy: look it up on mint's documentation :P
18:26
<bennabiy>
I am only running a 12.04 to try to pull some pulseaudio settings out
18:26
<vagrantc>
bennabiy: but in general, it should be in the chroot's /usr/share/ldm and /usr/share/ltsp dirs.
18:27
<bennabiy>
ok
18:27
I have a user that I need to perform a mount of a secure directory to his home folder, but only want it mounted there when he is logged in... could I hook into his login to perform that?
18:27
<vagrantc>
bennabiy: removing /opt/ltsp/images/* and re-running things might work
18:28
<bennabiy>
or would that be better suited for .bash_profile
18:28
<vagrantc>
bennabiy: did you run: ltsp-chroot /usr/share/ltsp/update-kernels ?
18:31
<bennabiy>
basically, I have a video issue with my thinclients which I need to append a video= to the kernel. If I run ltsp-update-image, it wipes the entry...
18:32
let me check
18:32
<vagrantc>
it may be pulling from the .img file, rather than from the chroot
18:34
bennabiy: but you also need to run: ltsp-chroot /usr/share/ltsp/update-kernels
18:35
bennabiy: otherwise it won't read the update-kernels.conf settings
18:38
<bennabiy>
02:52:17 PM - alkisg: So you should have an /opt/ltsp/i386/etc/ltsp/update-kernels.conf file, right?
18:38
02:52:44 PM - alkisg: With this in it: CMDLINE_LINUX_DEFAULT="init=/sbin/init-ltsp quiet splash plymouth:force-splash vt.handoff=7"
18:38
02:53:06 PM - alkisg: ...change that, then run /usr/share/ltsp/update-kernels in the chroot, and ltsp-update-kernels outside of it
18:38
<vagrantc>
yup
18:39
<bennabiy>
bah~! I think that is where I went wrong.. I never did the chroot part
18:39
<vagrantc>
alkisg tells no lies
18:39
<bennabiy>
I really appreciate his help
18:40
He was trying to help me with my audio issue, but so far it is still a mystery.. although now I am comparing config files between ubuntu 12.04 and mint 15 as far as pulse goes
18:43* vagrantc wishes mint developers would get involved with ltsp support
18:43
<bennabiy>
I know
18:43
<vagrantc>
though we don't get too many mint requests in here
18:43
but in general, i'd like to encourage all distros to be involved :)
18:43
<bennabiy>
probably because a lot of the ubuntu documentation covers mint issues
18:43
what aspect do you cover?
18:43
<vagrantc>
debian
18:43
really hope to get ltsp6 support ready in the coming year...
18:44
<bennabiy>
have you heard anything from the mint debian and ltsp?
18:48bobby_C has joined IRC (bobby_C!~bobby@188.20.161.210)
18:51
<bennabiy>
vagrantc: That worked... my issue was I didnt specify --arch=i386 for the ltsp-chroot
18:55PhoenixSTF has left IRC (PhoenixSTF!~rudi@lidet.uac.pt, Quit: Leaving)
19:07telex has left IRC (telex!~telex@freeshell.de, Ping timeout: 240 seconds)
19:07telex has joined IRC (telex!~telex@freeshell.de)
19:09
<vagrantc>
bennabiy: ah, yes.
19:10
bennabiy: haven't heard from mint in any formal capacity, other than mint users coming in asking support questions
19:21
<bennabiy>
that is a shame
19:22
<vagrantc>
my impression is it's a pretty small project without a lot of support
19:23
<digitalirony>
vagrantc: or bennabiy so, I just did that, and did ltsp-build-chroot
19:23
when it boots, its has an error
19:24
<vagrantc>
ltsp-build-client?
19:24
<digitalirony>
yeah that
19:24
<bennabiy>
what is the error?
19:24
<digitalirony>
the error on the client is socket error
19:24* vagrantc looks into the crystal ball
19:24
<digitalirony>
its basically complaining that the connection was refused when trying to mount the nbd0
19:24* bennabiy guesses you need to restart the nbd
19:24
<digitalirony>
imma reboot server after this update is done
19:24
but was just wondering
19:24wvsfxr has left IRC (wvsfxr!~Thunderbi@77.119.227.112.static.drei.at, Quit: wvsfxr)
19:25
<bennabiy>
rebooting the server will not do it,
19:25
<digitalirony>
that would restart nbd?
19:25
<bennabiy>
sudo service nbd-server restart works
19:25
I have pulled my teeth out over that one before
19:25
<digitalirony>
well, I just did a really big update, cause this image is old
19:26
<bennabiy>
I thought it was the tftp giving me issues, but it was because the nbd-server never initialized properly
19:26
<digitalirony>
well the tftp works heh
19:26
<bennabiy>
somehow you need to issue the command once, and it fixes it for good
19:26
<digitalirony>
cause the image boots
19:26
<bennabiy>
yeah, this was when I was a major ltsp newb
19:26
<digitalirony>
ahh
19:27
im new to ltsp, but not pxe/netboot
19:27
and I never even used nbd before
19:27
heh
19:27
<bennabiy>
I have been working with the ltsp environment for about 2 years
19:28
<digitalirony>
before I got here, they were running debian 5 on the workstations, and every one of them was administered manually :/
19:28
I said fuuuuck that
19:28
100 pcs
19:28
I built this ubuntu image I am using now, and threw puppet on it, and did it that way for the past year
19:28
but now its time to go TC
19:30mmetzger has left IRC (mmetzger!~mmetzger@99-71-214-196.lightspeed.mdldtx.sbcglobal.net, Remote host closed the connection)
19:46
<bennabiy>
Can someone tell me where the pulseaudio --system call happens ? I need to make the pulseaudio verbose to troubleshoot
19:46
on the client image
19:50
<digitalirony>
is there an option in LDM to disable the preferences menu
19:50
or the ability to change sessions
19:52* bennabiy bashes LDM
19:52
<digitalirony>
well, actually, I am pretty sure you can
19:52
I did it before
19:52
I just really don't remember how though
19:53
I think it was something that wasn't in the lts.conf documentation
20:03
hrmm, yeah I found where they said it was added
20:04
https://bugs.launchpad.net/ltsp/+bug/282884
20:04
but they never documented it
20:12||cw has left IRC (||cw!~chris@phpgroupware/cw, Remote host closed the connection)
20:14||cw has joined IRC (||cw!~chris@gateway.wilsonmfg.com)
20:14||cw has joined IRC (||cw!~chris@phpgroupware/cw)
20:19
<digitalirony>
LDM_FORCE_SESSION
20:19
that should be documented in the lts.conf
20:21
<bennabiy>
agree
20:21
I think that is one of my main issues with ltsp is the lack of documentation
20:22
that is why I hang out in here... logs = documentation ;)
20:22
<digitalirony>
well, apparently its in the weezy documentation
20:22
12.10
20:22
maybe that option isn't in 12.04
20:25* bennabiy is about to tome over xen/virt documentation...
20:26freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
20:26
<digitalirony>
ahh, yeah, thats what it is
20:26
that option isn't in 12.04 :/
20:26
I would have to dirty up my repos and install ppa or something
20:26
I kinda feel like doing that makes shit a mess though, and I really don't wanna
20:40
<vagrantc>
one of the easiest ways to help contribute back is documentation...
20:47
<digitalirony>
I will totally help when I learn more
20:49
<vagrantc>
even simply filing bugs that "feature X is not in the lts.conf manpage" would help.
20:49
i.e. LDM_FORCE_SESSION
20:49
<digitalirony>
it is
20:49
its in 12.10
20:49
its just not in 12.04
20:49
<vagrantc>
ah, newer version of docs.
20:49
<digitalirony>
yeah
20:49
the option isn't in the version of LDM with 12.04
20:49* vagrantc dreamed that the docs released with a given version are actually in sync with the software released
20:50bobby_C has left IRC (bobby_C!~bobby@188.20.161.210, Ping timeout: 245 seconds)
20:50
<digitalirony>
I would have to install the ppa repos, which I kinda don't want to
20:50
nah, its in sync as far I know
20:51
just the option isn't in 12.04 version
20:51* vagrantc knows for a fact it's not in sync
20:51
<digitalirony>
I found where I had this conversation before with someone
20:51
and I searched the chat logs
20:51
<vagrantc>
maybe that feature, but others definitely aren't
20:51
<digitalirony>
alkisg helped me a long time ago with that
20:52
<vagrantc>
another great project would be to document the ltsp/ldm/ltspfs versions in which a feature was introduced
20:52
that way newer documentation would still be useful if it was simply missed
20:52
<digitalirony>
would be better imo, to have one man page
20:53
and just list what versions it does/doesn't work in
20:53
or something
20:53
less confusing...cause at first I didn't even realize there was multiple versions of the man page
20:53
I just read the one that google found, which is old
20:53
<vagrantc>
it's impossible to have a single version of the manpage, we cannot change the past.
20:55
the idea was to ship the appropriate manpage in the ltsp-docs package shipped with a particular ltsp/ldm/ltspfs version
20:55
but as usual, docs are often not updated when features are introduced
20:56* vagrantc is as guilty as anyone for thatt
21:04vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
21:10Nilo has joined IRC (Nilo!bd10072e@gateway/web/freenode/ip.189.16.7.46)
21:10
<Nilo>
olá
21:10
posso teclar em portugues ?
21:12
I'm having trouble keyboard and video stations, how do I fix?
21:13
hello
21:16
<digitalirony>
you just said you are having a problem, and you asked how to fix it
21:16
but you never described the problem
21:16
we can not read your mind
21:23Parker955_Away is now known as Parker955
21:48
<digitalirony>
lts.conf goes in /opt/ltsp/arch/etc/lts.conf right?
21:58mmetzger has joined IRC (mmetzger!~mmetzger@99-71-214-196.lightspeed.mdldtx.sbcglobal.net)
21:59
<staffencasa>
digitalirony, '/var/lib/tftpboot/ltsp/<arch>
22:01
<digitalirony>
no, I don't think thats correct
22:01
thats where the image goes
22:01Parker955 is now known as Parker955_Away
22:03
<staffencasa>
that's where my lts.conf file is
22:19
<digitalirony>
weird, I don't think its read from there though
22:19
cause its read inside the client, and the tftp is just for serving the image
22:19mmetzger has joined IRC (mmetzger!~mmetzger@99-71-214-196.lightspeed.mdldtx.sbcglobal.net)
22:29vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
22:31
<digitalirony>
hrmm, yeah, the lts.conf file doesn't seem to get parsed for me, in either location
22:31
tis odd
22:32
staffencasa: ahhh
22:32
# With the introduction of the nbd/unionfs/squashfs structure
22:32
# the lts.conf file moved to the tftp root please create:
22:32
# /var/lib/tftpboot/ltsp/i386/lts.conf instead for your changes
22:33
<staffencasa>
are you using nfs?
22:33
<digitalirony>
nbd
22:33
ndb
22:33
blah
22:33
nbd lol
22:34
<staffencasa>
I gotta run, but if it's not parsing, you might want to make sure the section has a heading, ie. [default]
22:34
<digitalirony>
baaaahahahahaahahahaha
22:34
<staffencasa>
I'm pretty sure that matters
22:34
<digitalirony>
yeah
22:34
it doesn't have one by default
22:34
damn it
22:34
<vagrantc>
check to make sure it's actually downloading it from tftp
22:34
<digitalirony>
thanks
22:35
<staffencasa>
yup
22:37staffencasa has left IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu, Quit: Leaving)
23:18freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Ping timeout: 268 seconds)
23:33freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)