good morning is there some where a up to date list of all values that a supported by the ltsp.conf file? for example is the Value LTSP_FATCLIENT=false still supported found it in an blog article from 2010

08:53

?

08:58

<otwieracz>

knipwim: date +%s

08:58

1358416682

09:06

komunista has joined IRC (komunista!~slavko@adsl-195-168-235-217.dynamic.nextra.sk)

My client is booting to busybox, here is a pic of the end of boot process... http://picpaste.com/pics/2013-01-17_07-47-21_41-RYFwrDhw.1358427034.jpg

13:12

I tried restarting nbd-server manually and booting client, but same problem

13:14

<Hyperbyte>

Okay, hi :)

13:19

* Hyperbyte pokes JuJuBee

13:20

[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)

13:23

<Hyperbyte>

!quiet-splash

13:23

<ltsp>

quiet-splash: to disable the splash screen in Ubuntu, in order to see any boot error messages, run sudo gedit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default and remove quiet splash plymouth:force-splash vt.handoff=7

13:25

mgariepy has joined IRC (mgariepy!mgariepy@ubuntu/member/mgariepy)

13:25

<Hyperbyte>

Question for developers: in 12.04, there is an nbdroot argument in the /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default file

13:26

With 12.10 this nbdroot argument isn't there. How does the client know which NBD image it should mount?

13:34

bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)

Hyperbyte: previously we were using ltsp-specific scripts to parse the kernel command line

14:17

In 12.04+ we switched to letting nbd handle them itself

14:17

(I did sent some patches in nbd for better parsing though)

14:17

So, to define a different nbdroot, you use the nbd syntax

14:18

Let me give you links to the file + the bug report...

14:18

<Hyperbyte>

:)

14:18

<alkisg>

Hyperbyte: script: /usr/share/initramfs-tools/scripts/local-top/nbd

14:19

<Hyperbyte>

But how does this script know whether to pick ltsp_i386 or ltsp_amd64?

14:20

If I have two chroots, and it's not specified in pxelinux.cfg/default

14:22

<alkisg>

Hyperbyte: that's via ROOTPATH

14:22

That's an additional change

14:22

$ head -n 1 /etc/nbd-server/conf.d/ltsp_i386.conf

14:22

[/opt/ltsp/i386]

14:23

And, your dhcpd sends /opt/ltsp/i386 as the rootpath

14:23

<Hyperbyte>

Ah

14:23

<alkisg>

I did that so that it works with either nfs or nbd

14:23

<Hyperbyte>

That's pretty clever. :)

14:23

Here I was thinking the root-path option is only for nfs :)

14:23

<alkisg>

And that way you can point different clients to different chroots without modifying pxelinux.cfg/default

14:24

That's one of the nbd patches I sent ;)

14:24

https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/593227

14:24

<Hyperbyte>

:-D

14:24

Nice work man. :)

14:25

<alkisg>

The problems with those changes is the upgrade path...

14:25

We need better scripts to update the configuration files

14:26

<Hyperbyte>

Fedora has a wiki page where they document all problems upgrading from version to version

14:26

I always check it when upgrading

14:26

Maybe this is an idea for the wiki

14:26

LTSP 5.3 (Ubuntu 12.04) -> LTSP 5.4 (Ubuntu 12.10)

14:26

<alkisg>

Nah... if we had the manpower for either the wiki or actual upgrade scripts, I'd go for the second one

14:26

<Hyperbyte>

- dhcp root-path is no longer only for NFS and must be specified

14:26

<alkisg>

It doesn't need to be specified

14:27

<Hyperbyte>

What I've just written I could place on the wiki

14:27

<alkisg>

If it isn't, our udhcpc script uses the current architecture there

14:27

<Hyperbyte>

I couldn't write your config update script

14:27

Plus, if you're using an external dhcp server (like me) you'd have been screwed. :)

14:27

<alkisg>

Sure, but you could test though

14:27

Why? It's client side

14:27

(udhcpc)

14:27

<Hyperbyte>

Wait now I'm confused.

14:27

<alkisg>

The client asks the dhcp server for the rootpath

14:28

<Hyperbyte>

Before the DHCP server didn't need to provide root-path if you were using NBD, right?

14:28

<alkisg>

And it's the same now too

14:28

Because client side, our udhcpc initramfs script,

14:28

...defaults to /opt/ltsp/<arch> for the rootpath

14:28

...if the dhcp server doesn't send one

14:29

So the upstream nbd script always gets a rootpath

14:29

<Hyperbyte>

mmm

14:29

Well, again, clever. :)

14:29

So which configuration files would need updating?

14:30

<alkisg>

That's a biiiiig question

14:30

The nbd configuration files, for one,

14:30

and some of the /etc/ltsp files as well

14:30

<Hyperbyte>

mhm

14:31

<alkisg>

Normally when I want to upgrade 12.04 to the greek schools ppa version (something like 12.10),

14:31

I purge ltsp, nbd etc, remove all configuration files and the tftp dir, and then reinstall the newer ltsp version :D

14:32

Btw, for example, I could write upgrade scripts there, if someone did the big work of testing + reporting exactly the bits that are wrong

14:32

That would be more helpful than a wiki page

14:33

Although some of the scripts are part of the ubuntu packaging (while they should better be upstream ones), and it would need some collaboration with stgraber

14:33

<Hyperbyte>

Right.

14:43

|Paradox| has joined IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)

14:45

dievel has joined IRC (dievel!~diabo@2-229-104-66.ip196.fastwebnet.it)

14:49

Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)

14:49

<dievel>

Hi, I have a strange behavior in Epoptes in LTSP environment. I'm testing two clients and I run Epoptes from the server console. Both the client have the same name. If I add one client to a group, both are added. The other features instead works, like screen sharing and so on. What am I missing? :) Thanks!

15:03

otwierac1 has joined IRC (otwierac1!~gonet9@v6.gen2.org)

15:04

gothaggis|limbo has joined IRC (gothaggis|limbo!~gothaggis@corp.heavyhammer.com)

dievel has left IRC (dievel!~diabo@2-229-104-66.ip196.fastwebnet.it, Remote host closed the connection)

15:48

<lotharn>

?

15:50

diabo has joined IRC (diabo!~diabo@2-229-104-66.ip196.fastwebnet.it)

15:51

diabo is now known as dievel

15:51

<JuJuBee>

My ltsp server is an NIS client on my LAN. I used nfs to mount /home on the ltsp server. my users can log into a ltsp client computer but their /home is not mounting properly . They get a message that "Transport endpoint is not connected"

15:57

Gremble has left IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com, Quit: I Leave)

16:11

Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)

16:16

<JuJuBee>

If I want my users to get their home dirs from server2 and authenticate with server 2 and I run ltsp on server 1 and dhcp on server 1, do I need to install nfs/nis in the chroot and update-image? or do I install these on server 1 and let ltsp handle this?

16:19

<markit>

dievel: probably because "...Both the client have the same name"

16:19

<Hyperbyte>

JuJuBee, you don't need NIS on the clients, because LTSP handles user-creation on login. So NIS isn't needed on the client, only on the server.

16:20

As for NFS, you could mount it on the server and then let the clients get it from there with sshfs, but that creates quite some overhead.

16:20

<JuJuBee>

That is how it is currently set, but I am getting weird behavior. When I log in using my net account, I get my documents etc... fine but when a student logs in, no such luck

16:20

<Hyperbyte>

You could add an fstab line to the client configuration. This is done with the FSTAB_0=... variable in lts.conf

16:21

<||cw>

JuJuBee: thin or thick clients?

16:21

<Hyperbyte>

JuJuBee, something like FSTAB_0=server:/home /home nfs defaults 0 0

16:21

<JuJuBee>

||cw: fat

16:21

<||cw>

ah

16:21

<JuJuBee>

Hyperbyte: on new server in fstab?

16:21

<Hyperbyte>

That adds lines to /etc/fstab on client boot.

16:22

<JuJuBee>

Hyperbyte: strange that my account works fine and it is not in sudoers group

16:22

<||cw>

hm. then the client needs NIS too, or else the UID's won't match up on the NFS

16:22

<Hyperbyte>

||cw, actually, LTSP takes care of that.

16:23

Where this is going wrong is with the groups.

16:23

LTSP will make sure the logged in user exists on the client, but it won't copy over all of the groups I think.

Hyperbyte: Since I will eventually merge the 2 servers, I think I will NOT do this as it will install unnecessary item in the image. I may just look into some way of synchronizing the data for the time being.

dobber has left IRC (dobber!~dobber@213.169.45.222, Remote host closed the connection)

16:47

<dievel>

markit: sorry :) I didn't explained. They take different names from DHCP but inside the epoptes console they take same name, even if they have the correct and different username in parenthesis. This is odd.

jammcq has joined IRC (jammcq!~jam@c-69-245-75-255.hsd1.mi.comcast.net)

21:40

<Hyperbyte>

Enslaver, so, are you on the worldmap yet? :-)

21:40

!worldmap

21:40

<ltsp>

worldmap: If you're using LTSP, please let the world know and share your story at http://www.ltsp.org/stories/ Your can add a nice pin to our world map at your location, plus your setup will count towards the global LTSP usage statistics.

21:41

<Enslaver>

Hmmm, no, I could write up something

21:41

<Hyperbyte>

:-D

21:42

t

21:45

whyzzyrd has joined IRC (whyzzyrd!~grimreape@chon2-adsl.demon.co.uk)

21:45

<Enslaver>

Hi, i uze el tee ess pee and stuff

21:45

<whyzzyrd>

uuhuh

21:46

<otwieracz>

So, where I can set LDM_SESSION per user?

21:46

I want to start xterm after auth.

21:47

<whyzzyrd>

Evening, I've had a few goes at building with --fat-client. I've 2 questions. How do I make the cow filesystem be an nfs mount on the server?

otwieracz, LDM_SESSION can be set to any value that exists in /usr/share/xsessions/ on the server

22:23

Like ubuntu-desktop or gnome-fallback or whatever.

22:23

If you want a custom script, you could create it there

22:24

<otwieracz>

ok

22:24

but

22:24

<Hyperbyte>

I have a machine where I've made a custom /usr/share/xsessions/myscript.desktop

22:24

<otwieracz>

„Failsafe xterm” also does not work.

22:24

<Hyperbyte>

But, according the documentation you could also use LDM_XSESSION to link directly to a custom script

22:24

otwieracz, do you need the failsafe xterm?

22:25

<otwieracz>

I want anything at this moment :)

22:30

dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Quit: Computer has gone to sleep.)

22:30

andygraybeal_ has joined IRC (andygraybeal_!~andy@h117.195.213.151.dynamic.ip.windstream.net)

22:36

<Hyperbyte>

otwieracz, wrong answer.

22:36

You should figure out what you want, which session, and then start troubleshooting that.

22:36

If you want a failsafe xterm you'll have to find someone else, because I have no experience with that. Never used it, not sure if/how it works.

22:37

<otwieracz>

Ok.

22:37

If I have to compile something on my own in chroot.

22:37

Where should I place it?

22:38

I've placed it in /root but when booting thin client I was getting errors „not enough free space”.

22:40

<Hyperbyte>

otwieracz, preferably, you compile it on an installation identical to the chroot, but not the chroot itself, you don't need all the devel packages in your chroot (or at least that's how I always do it)

22:40

I make a copy of the chroot, do the compiling, move everything over to the clean chroot, do the installation

22:40

<otwieracz>

I do not undestand.

22:40

<Hyperbyte>

Either way... you do this on your server, by typing "ltsp-chroot" to 'go' into the LTSP chroot and then you compile.