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


Channel log from 21 December 2012   (all times are UTC)

00:05markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
01:05PhoenixSTF has left IRC (PhoenixSTF!~rudi@78.29.132.86, Quit: Leaving)
01:14dgeary2 has joined IRC (dgeary2!~david@2001:388:e001:1e00:914:40fb:752:d15)
01:34adrianorg has left IRC (adrianorg!~adrianorg@177.156.56.57, Ping timeout: 265 seconds)
02:00dgeary2 has left IRC (dgeary2!~david@2001:388:e001:1e00:914:40fb:752:d15, Ping timeout: 260 seconds)
02:09Parker955_Away is now known as Parker955
02:56ball has joined IRC (ball!~ball@c-24-14-239-108.hsd1.il.comcast.net)
02:58andygraybeal has left IRC (andygraybeal!~andy@h193.205.130.174.dynamic.ip.windstream.net, Quit: Ex-Chat)
03:30Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 260 seconds)
03:47Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
04:08Parker955 is now known as Parker955_Away
04:21Hyperbyte has left IRC (Hyperbyte!jan@middelkoop.cc, Ping timeout: 244 seconds)
04:21stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Ping timeout: 264 seconds)
04:28Hyperbyte has joined IRC (Hyperbyte!jan@middelkoop.cc)
04:28stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
04:32Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Read error: Operation timed out)
04:38cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 255 seconds)
04:55sha_ has joined IRC (sha_!~sha@e177116223.adsl.alicedsl.de)
04:58sha has left IRC (sha!~sha@e177167052.adsl.alicedsl.de, Ping timeout: 244 seconds)
05:23telex has left IRC (telex!~telex@freeshell.de, Read error: Connection reset by peer)
05:26ball has left IRC (ball!~ball@c-24-14-239-108.hsd1.il.comcast.net, Quit: leaving)
05:30telex has joined IRC (telex!~telex@freeshell.de)
06:21bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
07:17khildin has joined IRC (khildin!~khildin@ip-83-134-215-30.dsl.scarlet.be)
08:44DIoX|DaZ has left IRC (DIoX|DaZ!~KaKa@server.civicclub.lt, *.net *.split)
08:46DIoX|DaZ has joined IRC (DIoX|DaZ!~KaKa@server.civicclub.lt)
08:50adrianorg has joined IRC (adrianorg!~adrianorg@187.113.216.178)
08:52sep has joined IRC (sep!~sep@40.211.jostedal.no)
09:04bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
09:23bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
09:30cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
09:30staffencasa has left IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu, Ping timeout: 255 seconds)
09:34staffencasa has joined IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu)
10:24ltspuser_48 has joined IRC (ltspuser_48!bb32bfa3@gateway/web/freenode/ip.187.50.191.163)
10:24
<ltspuser_48>
oi
10:28ltspuser_48 has left IRC (ltspuser_48!bb32bfa3@gateway/web/freenode/ip.187.50.191.163, Client Quit)
10:32gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
11:07Gremble has joined IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com)
11:18profesor has joined IRC (profesor!d4e1a870@gateway/web/freenode/ip.212.225.168.112)
11:22work_alkisg has left IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr, Quit: Leaving.)
11:23markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
11:46Gremble has left IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com, Quit: I Leave)
11:51Gremble has joined IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com)
11:52Parker955_Away has left IRC (Parker955_Away!~parker@74.112.203.151, Ping timeout: 245 seconds)
11:56bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
11:57Parker955_Away has joined IRC (Parker955_Away!~parker@74.112.203.151)
12:09
<markit>
Hyperbyte: hi, a question about nfs4, are you here?
12:11
<Hyperbyte>
markit, no, sorry. I am currently travelling through time and will return five minutes ago.
12:14
(yeah, I'm here, what's up? :P)
12:17Gremble has left IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com, Quit: I Leave)
12:21sep has left IRC (sep!~sep@40.211.jostedal.no, Ping timeout: 260 seconds)
12:38artista_frustrad has joined IRC (artista_frustrad!~fernando@189.125.205.147)
12:41
<markit>
hi, sorry, dinner :)
12:41
Hyperbyte: still there?
12:41
<Hyperbyte>
I've been waiting here for half an hour!
12:41
:(
12:42
<markit>
Hyperbyte: I'm really sorry, but wife come and...
12:42
<Hyperbyte>
Prioritize man! Who puts their wife in front of anything... :/
12:42
<markit>
for nfs4, do you create a dir like /nfs4 on the serer and mount bin /home, right?
12:43
<Hyperbyte>
For home dirs, yes.
12:43
<markit>
what permissions do you have in that dir? I don't want students be able to go there from /
12:43sep has joined IRC (sep!~sep@40.211.jostedal.no)
12:44
<Hyperbyte>
You don't want students to access the /home/ dir?
12:44
<markit>
and also, does nfs4 respects ACL?
12:44
Hyperbyte: no, I don't want to go in /, find /nfs4 and go there through that route
12:45
<Hyperbyte>
Not entirely sure.
12:45
<markit>
or is perfectly equivalent of /home?
12:45
<Hyperbyte>
I don't see why you would have /nfs4 on a machine if you don't want to people to access it. Then why is it there?
12:45
<markit>
I mean, /home is mounted with nfs, while /nfs4/home is accessed through sshfs file system?
12:45
<Hyperbyte>
No?
12:46
Why would you use both sshfs and nfs?
12:46
<markit>
Hyperbyte: I want people access the MOUNTED home, not the root of the mount point
12:46
<Hyperbyte>
I don't understand again. The mounted home, with mount point /home I suppose you mean
12:47
And you don't want users to access /home ?
12:47
<markit>
yes, I love them to access it
12:47
don't want them to access FROM THEIR CLIENT /nfs4/home
12:47
but only the mounted /home
12:47
<Hyperbyte>
But explain this:
12:48
What is /nfs4/home and what is /home? And why do you want them both?
12:48
<markit>
I don't want them both, is something I want avoid like hell
12:48
mmmm ok, fat clients have their own /, so problem solved
12:48
<Hyperbyte>
Then why would you have them both?
12:49
<markit>
I'm confusing what sees thin and what sees fat, sorry
12:49
<Hyperbyte>
mount server:/home /home
12:49
On -all- clients, fat, thin, whatever.
12:49
And then you're done.
12:49
<markit>
ok, but THIN can do ls -l /nfs4/home, right?
12:49
<Hyperbyte>
So let me ask again
12:49
What is /nfs4/home ?
12:50
<markit>
is a server directory
12:50
so if you are in the server, you can see it
12:50
<Hyperbyte>
But why is it there?
12:50
<markit>
and is ALSO available with nfs
12:50
is there because, unfortunately, with nfs4 you have to provide a "virtual root" directory
12:51
while with nfs3 you just export /home
12:52
Hyperbyte: btw, I've changed no_root_squash with root_squash and fat works fine :) thanks
12:52
now I want to try to change from nfs3 to nfs4 and see if everything works fine and hope better
12:52
<Hyperbyte>
markit, are you sure about this?
12:53
Because I'm pretty sure I'm using NFS v4
12:53
It says so in mount points, as well as nfsstat
12:53
But I have no idea whatsoever about what you're talking about.
12:53
<markit>
well, the doc I've read tells about a different way of set exports with nfs4
12:53
you need a line with fsid=0
12:55
Hyperbyte: http://www.cyberciti.biz/faq/nfs4-server-debian-ubuntu-linux/
12:55
and http://www.crazysquirrel.com/computing/debian/servers/setting-up-nfs4.jspx
12:56
Hyperbyte: also if you do cat /etc/exports, nfs4 example has the "root" with fsid=0 and then subdir
12:57
<Hyperbyte>
I don't have fsid=0 and I don't have this pseudo file system that's described there.
12:57
my exports file: /data (192.168.20.0/24(rw,sync)0000000000000
12:57
(minus the zeroes)
12:58
This /data dir I mount on the clients, and do a mount --bind /data/home /home
12:59
Which kind of looks like what's described in your howto, but I've done it purely by chance.
12:59
I don't see why you couldn't just export your /home dir though.
12:59
<markit>
here maybe there is some more info: http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-nfs-server-config-exports.html
13:00
seems to be a new feature, and also you need to export the "root" virtual as "ro" for compatibility
13:00
but probably you can avoid that feature... wondering how do you specify what nfs version you are using then?
13:00
do you have a "mount nfs4" in fstab_0 ?
13:01
fstab_1?
13:01Da-Geek has joined IRC (Da-Geek!~Da-Geek@exch.imparando.com)
13:01
<markit>
I mean, how can you be sure that it's using nfs4 and not nfs3?
13:01
I thought was because of that fsid=0 stuff, but maybe I'm wrong
13:01
<Hyperbyte>
supportserver:/data on /data type nfs (rw,vers=4,addr=192.168.20.6,clientaddr=192.168.20.4)
13:03
Plus there are all pretty recent installations with as few tweaking as possible... I'm pretty sure they're just defaulting to v4
13:04
<markit>
vers=4
13:04
<Hyperbyte>
Have you -tried- to just export /home?
13:04
I'm pretty sure this pseudo dir that's being talked about in that howto is just the way the howto likes to do it, not something that NFS actually requires.
13:04
<markit>
Hyperbyte: I'm reading last url I gave you, seems that the fsid=0 is needed for compatibility if you want to mount in the client with nfs3 syntax
13:04
<Hyperbyte>
So, eliminate fsid=0 then
13:05
Just copy the /etc/export line for /data I gave you, change it to /home and see if it works
13:05
Will take you a whole of two minutes and it'll put an end to this discussion.
13:05
<markit>
Hyperbyte: I'll do some tests, thansk for the clarification, that also explains why we were unable to understand each other about my "/nfs4" dir problem
13:05
<Hyperbyte>
:)
13:06
Out of curiousity, why would you mind if users navigated to their home dirs via an alternate path?
13:06
<markit>
Hyperbyte: sure, but I thought you were doing thinks like in that tutorial, and the explaination of the /nfs4 stuff would have took 4 seconds ;P
13:07
Hyperbyte: they can be confused, and I fear that ACL can be ignored, or they save with one path and don't understand what they are doing... I mean, only one path = less troubleshoot on my side
13:08
I have to find a way to make Dolphin not list them as separate devices (in the future, now I've other stuff to do first)
13:12
<Hyperbyte>
:)
13:12
<markit>
exportfs: /etc/exports:3: unknown keyword "vers=4"
13:12
ops,my mistake
13:12
:)))
13:12
(I put it in exports lol)
13:13* markit needs more sleep
13:15bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
13:16
<Hyperbyte>
FYI, my /etc/fstab entry just contains "supportserver:/data /data nfs defaults 0 0"
13:16
The vers=4 is done automatically
13:16
But I'm using pretty recent versions of everything, so that might make the difference.
13:16Da-Geek has left IRC (Da-Geek!~Da-Geek@exch.imparando.com, Quit: Leaving)
13:19
<markit>
Hyperbyte: me too.. with ... /data nfs4 ... kde fails login
13:20
<Hyperbyte>
Oh... you're using KDE?
13:20
<markit>
yes
13:21PhoenixSTF has joined IRC (PhoenixSTF!~rudi@193.136.242.251)
13:23alexqwesa_ has left IRC (alexqwesa_!~alex@alexo-veto.broker.freenet6.net, Quit: Хана X'ам !!!)
13:23
<Hyperbyte>
I've read nothing but bad about KDE and NFS home dirs
13:24
I think there are workarounds though.
13:25
<markit>
Hyperbyte: I had a lot of problems until I changed sync with async, that alleviates the HUGE I/O
13:25
then there is the problem that ~.kde symlinks to /var/tmp and in sshfs does not work or something like that (don't remember)
13:26
with nfs3 and async is working, now I want to try with nfs4... using nfs4 "your way" does not
13:26
I try with the "root" virtual then, just for curiosity
13:26
maybe that makes possible a symlink among home and var/tmp, since I export both as NFS shares
13:34mikkel has joined IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk)
13:36
<Hyperbyte>
markit, first I'd try to find out exactly what the problem is.
13:37
<markit>
Hyperbyte: I know that the above problem is for startkde unable to create a symlink
13:39bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
13:52ltspuser_58 has joined IRC (ltspuser_58!324bb1d3@gateway/web/freenode/ip.50.75.177.211)
13:52
<ltspuser_58>
hello all
13:53
i'm having a problem with fat clients being able to load their local hard drives
13:54
in the respective stanza of lts.conf i have LOCALDEV_DENY_INTERNAL_DISKS = False
13:54
as a thin client, it mounts the drive OK but not when told to be a fat client. Any ideas?
13:55
<markit>
Hyperbyte: trying to move torward nfs4 syntax, before ldm login I get the error that /var/tmp (that I export) can't be mounted, so bad
13:55
I can mount it from a different host manually
13:56
hope alkisg will be here and have time to help in this
13:58
<ltspuser_58>
i believe the problem is with permissions/groups. When the client comes up as a fat client, the permissions/groups do not seem to be brought in as they do when they are thin
14:00
<markit>
Dec 21 15:00:03 gs1204 rpc.mountd[5257]: refused mount request from 192.168.20.103 for /vartmp (/vartmp): unmatched host
14:00
maybe I've done something worse... miss the * !
14:01* markit sleepy or stupid or both
14:01
<markit>
I'm victim of a copy and paste, lol
14:01
clients are in a different subnet from the one I used to experiment
14:12
mmm not, with nfs4 is not able to symlink from home to /var/tmp, both exported with nfs
14:12
with nfs3 it seem to work
14:13Gremble has joined IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com)
14:18Gremble has left IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com, Quit: I Leave)
14:20alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
14:26
<markit>
Hyperbyte: bottom of this article says you are right: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
14:26
"The linux implementation allows you..."
14:27
<Hyperbyte>
Yay!
14:30
<markit>
but example export with kubuntu 12.04 says the contrary
14:30
so I'm really confused
14:32
in another doc "Note: For security reasons, it is recommended to use an NFS export root which will keep users limited to that mount point only. The following example illustrates this concept."
14:33
<Hyperbyte>
Which, if you have only one directory to export, you already do.
14:39
<markit>
Hyperbyte: do you NEED_IDMAPD=yes in /etc/default/nfs-common ?
14:45
<Hyperbyte>
I use defaults for everything, although mine are Fedora defaults
14:46
But with ldap, I don't think nfs needs idmapd.
14:46
<markit>
Hyperbyte: ah, sorry, I remember you use ldap, we talked about it yesterday
14:48mnevans has joined IRC (mnevans!8008b09d@gateway/web/freenode/ip.128.8.176.157)
14:52bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
14:55
<mnevans>
Hello LTSP World. Having a problem getting isc-dhcp-server started.
14:55
<alkisg>
ltspuser_58: normal users don't have access to internal disks, neither on normal linux installations nor in fat clients
14:56
ltspuser_58: users in the admin group will have access, if they login on fat clients
14:56
<mnevans>
Error is " No subnet declaration for eth1".
14:56
<alkisg>
ltspuser_58: If you want to change that, you can do so from the policykit configuration
14:56
<mnevans>
I have the interface listed in /etc/defaults/isc-dhcp-server.
14:56
This is debian/wheezy beta 4 install.
14:58
Here is the subnet declaration in /etc/ltsp/dhcpd.conf: http://pastebin.com/STtMLWsF
14:59
I have only in /etc/dhcp3/dhcpd.conf, the line: include "/etc/ltsp/dhcpd.conf";
15:02
ifconfig eth1 shows: http://pastebin.com/6Ywde7d2
15:04
<Hyperbyte>
mnevans, what's in /etc/dhcp/dhcpd.conf?
15:04
(/etc/dhcp3 = dhcp3-server package, /etc/dhcp = isc-dhcp-server package)
15:05
<mnevans>
Solved it I think. :) In /etc/defaults/isc-dhcp-server, the default path is to /etc/dhcp/dhcpd.conf, but should be to /etc/dhcp3/dhcpd.conf. Setting DHCPD_CONF=/etc/dhcp3/dhcpd.conf solved the problem. At least the service started.
15:05
Just joining this chat makes me smarter! :)
15:06
<Hyperbyte>
Looks like you've succesfully got one DHCP server package running on the config of the other one. :)
15:08mip5 has joined IRC (mip5!~chatzilla@208.72.71.69)
15:13Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
15:13
<mnevans>
@ Hyperbyte, I think this is the way debian says to configure it. Now I'm on to a better problem.
15:13
<markit>
alkisg: you not expert of nfs4? I'm using /etc/export with compatible syntax, and if I put in FSTAB_1/2 the syntax for nfs3 (I force that protocol) everything is fine, if I try to use nfs4
15:14
then I got the infamous "call to lnusertemp..." problem after ldmlogin when kde tries to create symlink under .kde to /var/tmp (that I mount through nfs too)
15:14
probably a uid problem of who is running lnusertemp
15:15
<mnevans>
The client finds the assigned lan ip, but then says "NFS over TCP not available over 192.168.0.1. I thought debian default used NFS? If so, how do I start that service?
15:16
<alkisg>
markit: me, expert?! Nope, I'm not even a user of NFSv4!
15:16
<markit>
:) lucky man ;P
15:17
<mip5>
Morning - I tried adding 3.5 kernel to chroot by adding backports, and it worked for a while, but now the clients are failing. I edited default pxe config to show more output as clients boot. The clients hang here:
15:17
Product: USB Optical Mouse
15:17
Manufactureer: Logitech
15:17
USB disconnect, device number 11
15:17
new low speed USB device number 12 using using uhci_hcd
15:17
New USB device found, idVendor=046d, idProduct=c05a
15:17
New USB device strings: Nrf=1, Product=2, SerialNumber=0
15:18
<mnevans>
Maybe /etc/init.d/nfs-kernel-server start ? ...status says it's not running...
15:19
<Hyperbyte>
mnevans, yes.
15:23
<mnevans>
Hyperbyte, yes that worked. Now on to even better things, but a simple question. I've updated the server install with formware-linux-{free, nonfree}.
15:24
How to rebuild the ltsp images such that they reflect these new package installs to the server?
15:24
is it ltsp-chroot, then apt-get dist-upgrade?
15:25ltspuser_83 has joined IRC (ltspuser_83!c31772ca@gateway/web/freenode/ip.195.23.114.202)
15:25
<ltspuser_83>
Hi
15:26
<Hyperbyte>
Hi!
15:26
<ltspuser_83>
I need some help in two situations...
15:26
<Hyperbyte>
Shoot.
15:26
mnevans, are you using regular ltsp or ltsp-pnp?
15:27
<mnevans>
Thanks; Regular ltsp
15:28
I don't know what ltsp-pnp is...
15:28ltspuser_36 has joined IRC (ltspuser_36!c31772ca@gateway/web/freenode/ip.195.23.114.202)
15:29
<mnevans>
well, now I do, thanks to google.
15:29
<ltspuser_36>
Hi again! my connection went down
15:29
<mnevans>
Not using ltsp-pnp.
15:29
<Hyperbyte>
mnevans, in that case, ltsp-chroot will get you into the chroot... you can also modify /opt/ltsp/i386/ directly should you wish
15:29
<ltspuser_36>
I need to know if I can change the path of the chroot and of the tftpboot?
15:29
And teh other question is more complicated...
15:30
<Hyperbyte>
mnevans, after making changes, run ltsp-update-image. You might also want to run ltsp-update-kernels depending on what you've changed.
15:30ltspuser_83 has left IRC (ltspuser_83!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
15:30
<ltspuser_36>
I need to know if there is any broker that provides the possibility to open ldm sessions in different machine
15:30
<mnevans>
@Hyperbyte, so ltsp-chroot, and then apt-get dist-upgrade will update the chroot to any changes from the server install?
15:31
<ltspuser_36>
like put one user per machine
15:31
<Hyperbyte>
ltspuser_36, you probably can. Question is why would you want to do that?
15:31
<mnevans>
Or just: ltsp-build-client again?
15:31
<Hyperbyte>
mnevans, ltsp-build-client rebuilds the entire client, erasing all changes you've made in /opt/ltsp/i386
15:32
mnevans, ltsp-update-image updates the chroot from the changes made in /opt/ltsp/i386
15:32
<ltspuser_36>
so the idea is make a connection to a machine that has ltsp and the broker providing user details and then this machine tell the terminal to open session in the user's machine
15:32
<mnevans>
So then: ltsp-chroot and then apt-get update && apt-get dist-upgrade?
15:32
<Hyperbyte>
Assuming you're using NBD (which is default in Ubuntu), the clients don't actually load their stuff from /opt/ltsp/i386. They load it from an NBD image, which you have to update after making changes.
15:32
<ltspuser_36>
because I want to put in another server the chroot and the tftpboot
15:33
<Hyperbyte>
mnevans, you might run into problems with apt, but go ahead and try. If you're worried, make a backup of /opt/ltsp/i386 directory.
15:33
ltspuser_36, why would you want that?
15:33
<mnevans>
Hyperbyte, it's a fresh install, so nothing to lose, but I would like to know the right way to do this for the future.
15:34
<Hyperbyte>
mnevans, understandable.
15:35ltspuser_99 has joined IRC (ltspuser_99!c31772ca@gateway/web/freenode/ip.195.23.114.202)
15:37
<mnevans>
Hyperbye, I haven't found any documentation of how to do this; can you point me in the right direction?
15:37ltspuser_36 has left IRC (ltspuser_36!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
15:37ltspuser_51 has joined IRC (ltspuser_51!c31772ca@gateway/web/freenode/ip.195.23.114.202)
15:38
<ltspuser_51>
and I need to put the .img in my server and the tftpboot to provide to my terminals
15:38
and I saw that the ubuntu chroot works good
15:38
but I have a debian server
15:39
<mnevans>
@Hyperbyte, doing ltsp-chroot -p, apt-get update && apt-get dist-upgrade did nothing. So I'm
15:39
<ltspuser_51>
path*
15:39
it's possible to put the chroot in another pass?
15:39
<mnevans>
going to try ltsp-build-client and hope it picks up the firmware packages I need for my clients.
15:40ltspuser_99 has left IRC (ltspuser_99!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
15:41
<ltspuser_51>
can I change?
15:45
<mip5>
mnevans: I'm not sure exactly what you're trying to do, but if your clients need firmware, you'll have to install that in the chroot, and update the chroot. Installing it in the server won't necessarily have it show up in the chroot.
15:46
<ltspuser_51>
can I change the path of the chroot and tftpboot?
15:51bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 255 seconds)
15:52ltspuser_51 has left IRC (ltspuser_51!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
15:53ltspuser_82 has joined IRC (ltspuser_82!c31772ca@gateway/web/freenode/ip.195.23.114.202)
15:53
<ltspuser_82>
I need to open sessions per user and not per terminal
15:54
it's possible?
15:54
<mnevans>
mip5: yes, my clients need firmware. So I would do: ltsp-chroot, apt-get install firmware-linux-free, then ...?
15:54
<ltspuser_82>
I need to have a ldm session but per user...
15:54
<mnevans> then you exit the chroot and run ltsp-update-image
15:55
to update the filesystem
15:56
<mnevans>
ltspuser_82 & mip5: thanks, I'll give it a try.
15:57
<ltspuser_82>
;) no problem
15:59
I know that in lts.conf I can specify, providing MAC, options to each terminal but can I provide depending on the user?
16:05
<mnevans>
@ltspuser_82: ltsp-update-image complains that I am running nfs and not nbd. Is there a way to tell it to use nfs?
16:05
Or maybe alkisg can answer this one easily?
16:07
<ltspuser_82>
I think if you use NFS you don't need to run ltsp-update-image
16:07
becase this command is to generate the .img file
16:07
<markit>
ltspuser_82: exactly, the NBD image
16:07
<ltspuser_82>
and this file is only used when you work with nbd
16:08
I think... I'm not sure
16:08
<markit>
I am :)
16:08
<mnevans>
OK, looks like with nfs I don't need to run ltsp-update-image (there is no image in nfs, right?). Duh...
16:08
<ltspuser_82>
so if you are using NFS you only need to specify the chroot and the nfs mounts the path...
16:08
yes ;)
16:09
<markit>
mnevans: and also mind where lts.conf is, that is not the same position that is for NBD installation (for nbd is under /var/lib/tftp/i386...) AFAIR
16:12ltspuser_99 has joined IRC (ltspuser_99!c31772ca@gateway/web/freenode/ip.195.23.114.202)
16:12ltspuser_82 has left IRC (ltspuser_82!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
16:15
<ltspuser_99>
I know that in lts.conf I can specify, providing MAC, options to each terminal but can I provide depending on the user?
16:17
<markit>
ltspuser_99: no
16:17
<mnevans>
markit: I was just getting to that, in debian and nfs it is in /opt/ltsp/arch/etc/
16:18
<ltspuser_99>
thks
16:18
<markit>
ltspuser_99: those parameters are using BEFORE you are authenticated
16:18
so no one knows who you are at that stage, AFAIU
16:20
<mip5>
I added kernel 3.5 by adding backports. My clients wouldn't light up the display unless I ctrl-alt-f1. Once I do that, I can ctrl-alt-f7 and get the login screen.
16:21ltspuser_28 has joined IRC (ltspuser_28!c31772ca@gateway/web/freenode/ip.195.23.114.202)
16:21
<mip5>
someone, maybe Hyperbyte, suggested I edit my pxelinux.cfg/default file by removing quiet splash plymouth:force-splash vt.handoff=7, and that solved the problem. Any ideas?
16:22
<ltspuser_28>
I need to know if theres any way that, depending on the login, we make a ldm session to a certain machine
16:22
it's ossible?
16:22
possible?
16:22ltspuser_99 has left IRC (ltspuser_99!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
16:22
<ltspuser_28>
not depending on the machine...
16:22
depending on a login step...
16:22
<mip5>
ltspuser_28: you can specify parameters for specific machines in lts.conf by using mac address
16:22
<ltspuser_28>
for example when terminal starts...
16:23
yes...
16:23
but I don't want per machine
16:23
because the user has the same server...
16:23
but he can use all the terminals...
16:23
and I want that when is that user do a ldm session to a certain server...
16:24
like a local login...
16:24
<markit>
ltspuser_28: ldm is in that client BEFORE user as entered his username, so how can do that?
16:24
<ltspuser_28>
and lts.conf is field depending on this login...
16:24
yes I know...
16:25
It's difficult...
16:25
Is there any workaround?
16:25
<markit>
there should be a double pass...
16:25
generig ldm login, once authenticated re-login (automatically) with another server... far beyond my knowledge
16:25
<ltspuser_28>
could be two login steps...
16:25
<markit>
probably alkisg is the only one that can have an idea
16:26* markit fighting with his nobody nogroup in his nfs4 shared folder
16:27
<markit>
Hyperbyte: sorry to bug you, but now I've give up with export /var/tmp too, so performance apart, I just have /home exported. But if I open a terminal and I issue "ls -l" I see that all my files belong to "nobody nogroup", is it normal?
16:27ltspuser_49 has joined IRC (ltspuser_49!c31772ca@gateway/web/freenode/ip.195.23.114.202)
16:27
<ltspuser_49>
ok
16:28
but alkisg is here?
16:28
I understand
16:28
<mip5>
gotta run - thanks gang
16:28mip5 has left IRC (mip5!~chatzilla@208.72.71.69)
16:28
<markit>
ltspuser_49: well, probably sometime is busy with his own stuff and life
16:28
<ltspuser_49>
I understand...
16:29
<markit>
ltspuser_49: maybe later you can find some other "guru" around
16:30ltspuser_28 has left IRC (ltspuser_28!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
16:32ltspuser_31 has joined IRC (ltspuser_31!c31772ca@gateway/web/freenode/ip.195.23.114.202)
16:32
<ltspuser_31>
I have another question...
16:32ltspuser_49 has left IRC (ltspuser_49!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
16:33
<ltspuser_31>
so if I take the .img and the tftpboot folder and put in another path
16:37ltspuser_31 has left IRC (ltspuser_31!c31772ca@gateway/web/freenode/ip.195.23.114.202, Ping timeout: 245 seconds)
16:42sha_ has left IRC (sha_!~sha@e177116223.adsl.alicedsl.de, Remote host closed the connection)
16:58
<mnevans>
Thanks all - your help always appreciated. Have been documenting my ltsp/wheezy install and hopefully could give back by helping with updating documentation for this?
16:59komunista has joined IRC (komunista!~slavko@adsl-195-168-234-074.dynamic.nextra.sk)
17:18ltspuser_58 has left IRC (ltspuser_58!324bb1d3@gateway/web/freenode/ip.50.75.177.211)
17:28bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
17:32gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
18:04mnevans has left IRC (mnevans!8008b09d@gateway/web/freenode/ip.128.8.176.157, Quit: Page closed)
18:16leio_ is now known as leio
18:25
<markit>
dhcp passes the domain, but if in the fat client I do an hostname -f I don't see it... any clue?
18:25
in hosts in fact is not listed at all
18:28mikkel has left IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk, Quit: Leaving)
18:53Parker955_Away is now known as Parker955
19:01vagrantc has joined IRC (vagrantc!~vagrant@c-98-232-129-196.hsd1.or.comcast.net)
19:01vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
19:18PhoenixSTF has left IRC (PhoenixSTF!~rudi@193.136.242.251, Remote host closed the connection)
19:19gentgeen__ has joined IRC (gentgeen__!~kevin@c-98-236-71-64.hsd1.pa.comcast.net)
19:27
<alkisg>
markit: from the client, as root: sudo /usr/lib/klibc/bin/ipconfig -n eth0; cat /proc/cmdline
19:28
<markit>
hi alkisg :) if domain should be set, then is something wrong I did with my tests, I'm trying to "celan up" the VM and try again
19:29
alkisg: so from dhcp the fat client should have /etc/hosts with the FQDN?
19:30* markit struggles with nfs4 and nobody nogroup, but at least know that with nfs3 kde seem to work
19:36
<alkisg>
markit: yes I think it should work from DHCP, even though I've not tested it... Or, SEARCH_DOMAIN from lts.conf.
19:37
<markit>
seems fundamental for nfs4 user/id mapping, also should be a "good way of setup network" things
19:37
(I mean, have FQDN set)
19:37
I'll let you know what I discover
19:42adrianorg_ has joined IRC (adrianorg_!~adrianorg@187.113.216.178)
19:46adrianorg has left IRC (adrianorg!~adrianorg@187.113.216.178, Ping timeout: 250 seconds)
19:55
<Hyperbyte>
markit, everything with nobody/nogroup means idmapd isn't working properly
19:55
idmapd needs to be running on the server -and- the client
19:58Parker955 is now known as Parker955_Away
20:02Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
20:04
<alkisg>
Hyperbyte: is there any way to notify nfs4 that we don't need idmapd?
20:04
Because, by design, uids/gids are the same on the server as on the client?
20:05
<Hyperbyte>
alkisg, there is
20:06
<alkisg>
http://www.spinics.net/lists/linux-nfs/msg13217.html => "Is there an easy way to disable idmapd while still running nfs4 to determine if it is causing the hang?"
20:06
"Not that I know of."
20:06
<Hyperbyte>
Check /etc/default/nfs
20:06
There's some idmapd config there to disable it I believe.
20:07
Regardless, I think you need idmapd even if user ID's match.
20:07
Not entirely sure about that, but I think nfs4 and idmapd kind of go hand-in-hand
20:08
<alkisg>
I don't see an /etc/default/nfs file, and I don't see an idmapd entry in nfs-common nor in nfs-kernel-server
20:12
man idmapd => -S Server-only: perform no idmapping for any NFS client, even if one is detected.
20:13
The problem with ltsp clients and id mapping is that before logon, no users exist at all... numeric IDs there would make more sense than names
20:14
<Hyperbyte>
Why is it a problem?
20:15
<alkisg>
I'm not sure exactly, maybe the nfs client caches the uids/gids
20:16
But with my first tries I couldn't make nfs4 work, so after 10 minutes I gave up and used nfs3
20:16
...which worked on the first try
20:16
<Hyperbyte>
I've been using nfs4 without even trying
20:16
But then again, I'm also using ldap.
20:16
<alkisg>
Maybe fedora sets it up better, dunno
20:17
Ah, then the uids are already there
20:21komunista has left IRC (komunista!~slavko@adsl-195-168-234-074.dynamic.nextra.sk, Quit: Leaving.)
20:24telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
20:26telex has joined IRC (telex!~telex@freeshell.de)
20:27khildin has left IRC (khildin!~khildin@ip-83-134-215-30.dsl.scarlet.be, Quit: I'm gone, bye bye)
20:35alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
20:43sep has left IRC (sep!~sep@40.211.jostedal.no, Ping timeout: 255 seconds)
21:00Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
21:08sep has joined IRC (sep!~sep@40.211.jostedal.no)
21:10
<markit>
Hyperbyte: ah, on the client also? sigh
21:11* markit reading the log
21:11
<markit>
ups, so no hope to make nfs4 work without ldap?
21:11
<Hyperbyte>
markit, I don't see why you come to that conclusion
21:12
But, for NFS to work, a user on the client needs to match the user on the server
21:12
Which is the case with LTSP, so shouldn't be an issue (LTSP takes care of user creation during login)
21:12
Although for that scenario you do need idmapd
21:12
<markit>
[21:13] <alkisg> The problem with ltsp clients and id mapping is that before logon, no users exist at all... numeric IDs there would make more sense than names
21:13
<Hyperbyte>
With LDAP your user accounts already match
21:13
<markit>
[22:11] <markit> ups, so no hope to make nfs4 work without ldap?
21:13
<Hyperbyte>
markit, I'm pretty sure my clients at the radio station are not configured with ldap, just the server.
21:14
<markit>
Hyperbyte: ok, so I can now try to, in chroot, set /etc/default/nfs-common with NEED_IDMAPD=YES correct?
21:14
so it runs rpc.idmapd on the client also, I guess
21:14
<Hyperbyte>
markit, I have no idea. Like I said, I haven't messed with the config.
21:15
Well, I did enabled idmapd and the rpc services on the clients naturally
21:15
You don't do that via config, you do that via init.
21:15
update-rc.d Ubuntu uses if memory serves.
21:16
<markit>
wondering if is in rpcbind package
21:17
<Hyperbyte>
Yes, that is needed.
21:17
Wait, I'll boot a virtual client, peek around for you
21:17
Oh by the way
21:17
These kind of things you can also test on a running client
21:17
Just service idmapd start
21:17
service rpcbind start
21:17
etc...
21:17
<markit>
ok
21:18
<Hyperbyte>
I think NFS should update immediately when you next do ls -al
21:18
But maybe a remount is necessary
21:18
<markit>
idmapd start seems to work, but I've not found the /etc/init.d/imapd... I'm a debian guy, not yet got that upstart stuff and how mixes with old initd
21:19
I'll dig further, thanks
21:20
<Hyperbyte>
My fat clients have rpcbind, rpc.statd, rpciod and rpc.idmapd running
21:21
Also - my fat clients are -not- configured as LDAP clients
21:21
Only the server is.. so basically, I have the same setup as you
21:21
Ubuntu 12.04
21:21
<markit>
kubuntu 12.04
21:21
I try a clean install now
21:22
<Hyperbyte>
When I do ls -al /home/ I see numeric ID's for owner/group, which is what alkisg just said would be nice behaviour
21:22
<markit>
in these days I've added tests and configs in a cahotic way
21:22
<Hyperbyte>
:)
21:22
<markit>
Hyperbyte: oh, not user?
21:22
<Hyperbyte>
No
21:22
Because the users don't exist yet
21:22
:)
21:23
LTSP creates the user when it logs in, when I do ls -al /home then, I see numeric ID's except for the logged in user
21:23
<markit>
AH!
21:23
ok, the logged user sees himself
21:23
thanks a lot :)
21:24
<Hyperbyte>
Wait, it's working?
21:24
It's been working all along, you just didn't realize that the LTSP client doesn't have any user accounts until after you login?
21:25mgariepy has left IRC (mgariepy!mgariepy@ubuntu/member/mgariepy, Quit: Leaving)
21:25
<markit>
Hyperbyte: I have to test, I thanks a lot for the info
21:25
now I have to finish clean my server, reconfigure properly and troubleshoot if not working :)
21:26
<Hyperbyte>
Okay
21:26
<markit>
now I have the user with "nobody nogroup"
21:26
<Hyperbyte>
That's root
21:26
I believe.
21:26
<markit>
no no, I login as "marco"
21:26
<Hyperbyte>
It's either root, or idmapd not running.
21:26
<markit>
then I open a terminal and ls -l in the home
21:26
yep, the second ;P
21:26
<Hyperbyte>
Do a ps aux | grep idmapd
21:26
:)
21:26
<markit>
too late, I'm destroying my sever config
21:26
<Hyperbyte>
:o
21:27
How harsh.
21:27
<markit>
:)
21:41
mmm my pc is trasching, better reboot
21:41markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
21:50markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
22:39bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 265 seconds)
23:01awilliam1 has joined IRC (awilliam1!mistik1@unaffiliated/mistik1)
23:02awilliams has left IRC (awilliams!mistik1@unaffiliated/mistik1, Ping timeout: 244 seconds)
23:02awilliam1 is now known as awilliams
23:06vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)