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


Channel log from 15 July 2007   (all times are UTC)

00:39rcy has quit IRC
00:40rcy has joined #ltsp
00:44sbalneav has quit IRC
00:51vagrantc has quit IRC
01:27ccherret1 is now known as ccherrett
01:47cyberorg has joined #ltsp
02:02edgarin has quit IRC
02:26yanu has quit IRC
02:45nf1 has joined #ltsp
03:50rcy` has joined #ltsp
03:53rcy` has quit IRC
03:55rcy has quit IRC
04:09rcy has joined #ltsp
04:17rcy has quit IRC
04:22rcy has joined #ltsp
04:31rcy has quit IRC
04:32rcy has joined #ltsp
05:28rcy has quit IRC
05:28rcy has joined #ltsp
05:42yanu has joined #ltsp
06:19Q-FUNK has joined #ltsp
06:28K_O-Gnom has joined #ltsp
06:30
<K_O-Gnom>
hi folks ...
06:31
one little question .. can i change the std. ltsp kernel against every other? if yes what do i have to consider when i create a other kernel?
07:33J45p3r has joined #ltsp
07:34plamengr has joined #ltsp
09:16mikkel has joined #ltsp
09:20K_O-Gnom has quit IRC
09:25lmveloso has joined #ltsp
10:06cyberorg has left #ltsp
10:32nf1 has quit IRC
10:33nf1 has joined #ltsp
10:38plamengr has quit IRC
11:28vagrantc has joined #ltsp
12:19bobby_C has joined #ltsp
13:13rjune has quit IRC
13:15K_O-Gnom has joined #ltsp
13:57plamengr has joined #ltsp
14:32J45p3r has quit IRC
14:42K_O-Gnom has quit IRC
14:43plamengr has quit IRC
15:03otavio_ has joined #ltsp
15:12otavio__ has joined #ltsp
15:15bobby_C has quit IRC
15:18otavio has quit IRC
15:22otavio_ has quit IRC
15:28timma has joined #ltsp
15:28
<timma>
hello
15:31ltspbot` has joined #ltsp
15:31
<jammcq>
timma: what problem are you having?
15:34
<timma>
I am dumb on using ltsp, but I installed syslinux and run ltspcfg. Also, set the client to boot order to the nic (LANDesk which uses PXE). But I how no respone on the client except
15:35
"DHCP MAC ADDR ~~~" "BOOTP...."
15:35
<jammcq>
no need to install syslinux
15:35
<timma>
really
15:35
<jammcq>
nope. all of the pxe stuff you need is included in the ltsp-kernel package
15:36
pxe booting should be VERY simple to set up
15:36
what distro are you using?
15:36
<timma>
Debian 4 stable.
15:37
<jammcq>
ok, where are you seeing 'BOOTP' ?
15:37
<timma>
on the client on booting it up atfer post
15:38
<jammcq>
ok, Landesk actually supports 4 different boot methods. PXE is just one of them. Are you sure you have the Landesk rom configured for PXE ?
15:39
<timma>
Actually I all I did was go into the bios and changed the boot order, nothing else.
15:39
<jammcq>
landesk is the 3com rom, right?
15:39
<timma>
yes
15:40
<jammcq>
ok, I think you need to hit a key, maybe Ctrl-C right after POST
15:40
to get into the Landesk config screen
15:48ltspbot has quit IRC
15:49
<timma>
is PXE-M00 a code?
15:50
<jammcq>
sounds like it, but I don't know what the codes mean. If you are getting that, at least it tells us that you are using PXE
15:51
<timma>
I tried Ctrl-C and even Ctrl-Alt-B but no response
15:51
<jammcq>
ok, but are you getting a PXE-M00 error ?
15:51
<timma>
yes
15:51
<jammcq>
ok, it's prolly configured for PXE. Ok, do you have dhcpd setup ?
15:52muh2000 has quit IRC
15:53Q-FUNK has quit IRC
15:54
<timma>
yes, but I think my config is wrong http://rafb.net/p/idO4lO23.html
15:55
Oh, my tftpboot is on the root not in the /opt/i386/ltsp folder...
15:55
<jammcq>
that's ok
15:56
you are using Debian, so you'll need to add a 'next-server' entry to your dhcpd.conf file
15:56
take a look at this document:
15:56
http://wiki.ltsp.org/twiki/bin/view/Ltsp/DhcpdSiaddr
15:58Q-FUNK has joined #ltsp
15:58
<timma>
any a specific order?
15:59
and just "next-server 192.168.0.254"?
15:59
<vagrantc>
timma: the ltsp-server and ltsp-utils packages are incompatible ... make sure not to use them both.
16:00
<jammcq>
timma: put the line up near the top of the dhcpd.conf file
16:01
<timma>
how do I restart dhcpd?
16:01
<jammcq>
something like: /etc/init.d/dhcpd-server restart
16:01
but... I might have the filename not completely correct
16:01
go look in /etc/init.d for the script name
16:04
<timma>
oh, that's okay I just forgot about the /etc/init.d part
16:04
it will not restart though line 51 or 52 is giving an issue
16:05
vagrantc: what do I need to do uninstall both then reinstall ltsp-server. (How do I configure it then?)
16:06
forgot a bracket.
16:07
<vagrantc>
timma: if you only installed the packages, you should be fine. if you ran ltsp-build-client and then ltspadmin, you may have problems.
16:08
i really wish i had put that conflicts in sooner
16:12
<timma>
vagrantc I did not run ltsp-build-client, just ltspcfg and ltspadmin
16:12
<vagrantc>
timma: ok. you'll use ltsp 4.2 then
16:13
<timma>
jammcq: would you look at http://rafb.net/p/RYVozy10.html
16:14
vagrantc do you mean instead of ltsp 5? I knew that. I am not good with linux administration yet and want to stay with Debian stable. Later I do want to use 5.
16:14
jammcq it says server not found
16:15
the server ip is 192.168.0.167
16:15
<vagrantc>
timma: well, LTSP 5 is in debian etch/stable ... it's the ltsp-server package
16:15
<timma>
?! since when?
16:15
<vagrantc>
since etch released.
16:15
and before ...
16:16
<timma>
so, me using the ltsp-utils makes it 4.2?
16:16
<jammcq>
timma, what did you set next-server to ?
16:16
<timma>
192.168.0.254
16:16
<jammcq>
but your server IP address isn't that
16:16
<vagrantc>
timma: yes, ltsp-utils installs 4.2
16:17
<timma>
maybe I should read the line below
16:17
on the page you gave
16:18greg_g has left #ltsp
16:22
<timma>
Now it is "PXE-E3B: TFTP Error - File Not found" http://rafb.net/p/W1KnW216.html
16:24
I know that the tftpboot folder is on / Shouldn't it be in the /opt/ltsp/i386/ folder?
16:24
<jammcq>
timma: no
16:24
do this: ls -l /tftpboot/lts
16:26
<timma>
http://rafb.net/p/SqQkQi95.html
16:26
it has ltsp-1 ltsp-2
16:26
<jammcq>
ok, edit your dhcpd.conf file
16:26
change the 'filename' entry to:
16:26otavio__ has quit IRC
16:26otavio has joined #ltsp
16:27
<jammcq>
"/lts/2.6.20.9-ltsp-1/pxelinux.0"
16:28
<timma>
okay, I was being dumb I thought from reading the docs (v4.1) that just needed what I had.
16:28
<jammcq>
nope
16:28
you may need to adjust your /etc/inetd.conf file too
16:28
which tftpd did you install ?
16:28
(debian has 3)
16:31
<vagrantc>
dpkg -l *tftp* | egrep ^ii
16:32
<timma>
I checked synaptic and it is not tftpd. tftp-hpa version 0.43-1.1
16:32
<jammcq>
tftp-hpa or tftpd-hpa ?
16:33mikkel has quit IRC
16:33
<timma>
http://rafb.net/p/vZCMA226.html inetd.conf
16:34
tftpd-hpa
16:34
sorry
16:34
<jammcq>
ok, in your inetd.conf file, see how the 'tftp' line ends with '/var/lib/tftpboot' ?
16:35
<timma>
yes
16:35
<jammcq>
you either need to change that, or move your kernels to /var/lib/tftpboot
16:36
to be more compatible with LTSP-5, which you might want to upgrade to, I'd suggest moving your kernel.
16:36
try: mv /tftpboot/lts /var/lib/tftpboot
16:36
if it's all the same filesystem, that should succeed
16:38
<timma>
will the /tftpboot/lts change its contents with a new kernel on debian?
16:39
<jammcq>
no, if you install a new ltsp kernel, it won't put it in the right place, but it's easy to move it
16:39
and we aren't releasing new kernels very often for ltsp-4.2
16:40muh2000 has joined #ltsp
16:41
<timma>
would doing this "mkdir /var/lib/tftpboot/ltp" then "ln -s /tftpboot/lts /var/lib/tftpboot/lts" be okay or am I thinking wrong? (for theory?)
16:41
<jammcq>
it should work, if you DON'T do the mkdir
16:43Q-FUNK has quit IRC
16:43
<vagrantc>
some of the tftp servers are fussy about symlinks.
16:46
<timma>
yep, I think the symlink did not work or do I need restart tftp?
16:47otavio has quit IRC
16:47otavio has joined #ltsp
16:47
<timma>
I removed the symlink and then moved the folder, it still does not work.
16:47
<vagrantc>
restart your inetd ...
16:47
invoke-rc.d openbsd-inetd restart
16:47
<jammcq>
he hasn't changed inetd.conf
16:47
so he shouldn't need to restart it
16:48
have you restarted dhcpd since changing the 'filename' entry?
16:48
<vagrantc>
ah, yes.
16:48ccherret1 has joined #ltsp
16:49
<timma>
yes I restarted both just now.
16:50
but the same message
16:50
<jammcq>
ok, do this: ls -lR /var/lib/tftpboot
16:50
and paste that to the pastebot
16:50
and... do this:
16:50
grep filename /etc/dhcp3/dhcpd.conf
16:51
<timma>
ls -lR /var/lib/tftpboot
16:52
http://rafb.net/p/hFIdFm34.html
16:53
<jammcq>
and what's your 'filename' set to?
16:53
<timma>
oh, I forgot I changed the filename when I first had this error
16:54ccherret2 has joined #ltsp
16:54
<timma>
now it is /lts/2.6.20.9-ltsp-1/pxelinux.0
16:54
<jammcq>
ok, restart dhcpd, and it should work
16:55
<timma>
TFTP and periods being added
16:56
timed out
16:56
I need to change it in conf
16:56otavio has quit IRC
16:56otavio has joined #ltsp
16:57
<jammcq>
change what?
16:57
<timma>
oh, sorry, was not thinking right.
16:58
"PXE-E32: TFTP open timeout." is printed on two lines
16:59ccherrett has quit IRC
16:59
<jammcq>
was it a PXE-E32 before? or did that just start?
16:59
<timma>
no. it just started
17:00
it was a file not found before
17:00
<jammcq>
do this: netstat -anp | grep ":67 "
17:00
err
17:00
do this: netstat -anp | grep ":60 "
17:00
err
17:00
dammit
17:00
do this: netstat -anp | grep ":69 "
17:00
THAT"s the one you want to run
17:01
<timma>
udp 0 0 0.0.0.0:69 0.0.0.0:* 4341/inetd
17:01
udp 0 0 0.0.0.0:69 0.0.0.0:* 4199/in.tftpd
17:03
<jammcq>
seems about right
17:04
dunno why you'd be getting a timeout now.
17:05ccherret1 has quit IRC
17:05
<jammcq>
paste your latest dhcpd.conf file to the pastebot
17:06
<timma>
http://rafb.net/p/P1LEGK36.html
17:06otavio has quit IRC
17:06otavio has joined #ltsp
17:07
<jammcq>
you've got other things in dhcpd.conf pointing to .254. You'll need to change those to .167
17:07
but that shouldn't be causing your current problem
17:10
<timma>
how do I check to see if my nic is full or half ?
17:11
<jammcq>
at this point, you can't, and it doesn't matter
17:11
that's not causing your problem
17:13john_s has joined #ltsp
17:13
<john_s>
hello all: can samba handle non-flat /homes? can the smb.conf Global Option "template homedir =" be used to allow users to log in to their home dir if /home isn't flat? I.e if I have /home/groupa and /home/groupb/ can I use smb.conf to make sure that users end up logging into /home/groupa/bob or /home/groupb/janet?
17:15
<jammcq>
john_s: sounds like a question for the #samba channel, eh?
17:16
<john_s>
I agree, I have it there too they are a little sleepy so I hoped one of the LTSP folks had been here before
17:16otavio has quit IRC
17:16otavio has joined #ltsp
17:29
<timma>
http://www.bootix.com/support/problems_solutions/pxe_e32_tftp_open_timeout.html
17:29
3. TFTP and DHCP/BOOTP services are running on different machines, but the next-server (066) option was not specified
17:33
jammcq could the card be incompatible with TFTP?
17:48
jammcq should I reparition the hdd and then install grub and copy /var/lib/tftpboot/lts/vmlinuz-2.6.20.9-ltsp-1
17:55
vagrantc do you have an idea, should I boot locally and how?
17:56F-GT has quit IRC
17:58F-GT has joined #ltsp
18:00
<timma>
what is the different between /var/lib/tftpboot/lts/vmlinuz-2.6.20.9-ltsp-1 and -2?
18:02john_s has left #ltsp
18:04
<timma>
ignore that question, i am numb
18:05
<vagrantc>
timma: maybe your PXE client isn't respecting next-server
18:05
timma: you could try one of the boot floppies
18:05
!bootfloppy
18:05
<ltspbot`>
vagrantc: "bootfloppy" is http://etherboot.anadex.de or ftp://k12linux.mesd.k12.or.us/pub/K12LTSP/Universal_boot_floppy
18:07
<timma>
this would at least test if it does work.
18:07otavio has quit IRC
18:07otavio has joined #ltsp
18:10ltspbot has joined #ltsp
18:11
<vagrantc>
timma: no, just boot from the floppy
18:11
timma: it's an alternate network boot that should work.
18:11
etherboot with PXE emulation
18:17otavio has quit IRC
18:17otavio has joined #ltsp
18:27otavio has quit IRC
18:27otavio has joined #ltsp
18:27ltspbot` has quit IRC
18:36otavio has quit IRC
18:36otavio has joined #ltsp
18:42
<timma>
I have to go. Thank you jammcq and vagrantc
18:42timma has quit IRC
18:47otavio has quit IRC
18:47otavio has joined #ltsp
18:57otavio has quit IRC
18:57otavio has joined #ltsp
18:58J45p3r has joined #ltsp
19:05timma has joined #ltsp
19:07otavio has quit IRC
19:07otavio has joined #ltsp
19:09
<timma>
vagrantc I accidentally rm /dev/fd0, but the floppy image you gave work on booting to ltsp. But why would that work? the client's pxe does not work right?
19:09
<vagrantc>
timma: sounds like it
19:09
timma: or your DHCP is configured to give etherboot a different file
19:10
some PXE implementations are broken.
19:13cliebow has quit IRC
19:17cliebow has joined #ltsp
19:18ccherrett has joined #ltsp
19:18ccherret2 has quit IRC
19:25
<timma>
how do I check what dhcp give etherboot?
19:26
<vagrantc>
grep tftp /var/log/syslog
19:30
<timma>
it has only three lines: Connection Refused
19:33edgarin has joined #ltsp
19:44
<timma>
vagrantc so now that this works, about ltsp 5. is ltsp-server(-standalone) version 0.99debian11 ltsp 5?
19:44
<vagrantc>
timma: basically, yes. it's missing a few features. if you need them there's backports available
19:44
!debian
19:44
<ltspbot>
vagrantc: "debian" is is a GNU/Linux based operating system that makes an excellent LTSP server. You can find it at http://www.debian.org. for information about LTSP on debian see http://wiki.debian.org/LTSP
19:45
<vagrantc>
timma: but it's not going to fix your tftp problem
19:46
your other option is to see if atftpd works better for you
19:48otavio has quit IRC
19:48otavio has joined #ltsp
19:48spectra has joined #ltsp
19:48otavio has quit IRC
19:48
<timma>
vagrantc I read on one site something about mtftp?...
19:49
oh, same thing
19:49
<vagrantc>
you have two choices. atftpd or tftpd-hpa
19:49
regular tftpd doesn't work with PXE
19:50
<timma>
I am using tftpd-hda
19:50
<vagrantc>
right.
19:50
and since that's not working for you, maybe try atftpd
19:50
<timma>
okay
19:56spectra has quit IRC
20:03spectra has joined #ltsp
20:09timma has quit IRC
20:11timma has joined #ltsp
20:17ltspbot` has joined #ltsp
20:20edgarin_ has joined #ltsp
20:21edgarin has quit IRC
20:33ltspbot has quit IRC
20:34timma has joined #ltsp
20:40timma has left #ltsp
20:46timma has joined #ltsp
20:48
<timma>
jammcq just did netstat -anp | grep ":69 " and had nothing
20:49lmveloso has quit IRC
20:59
<vagrantc>
timma: grep tftp /etc/inetd.conf
21:01
<timma>
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /tftpboot
21:01
<vagrantc>
ps aux | egrep inetd
21:02
<timma>
http://rafb.net/p/xxnBiV58.html
21:03
<vagrantc>
timma: dpkg -l *inetd*
21:04
er
21:04
timma: dpkg -l *inetd* | egrep ^ii
21:04
<timma>
http://rafb.net/p/9ftNnL46.html
21:05
ii openbsd-inetd 0.20050402-6 The OpenBSD Internet Superserver
21:05
ii update-inetd 4.27-0.5 inetd.conf updater
21:06
run update-inetd ?
21:06
<vagrantc>
no
21:07
invoke-rc.d openbsd-inetd restart
21:07
<timma>
okay
21:12
<vagrantc>
timma: anything happen ?
21:13
netstat -anp | grep ":69 "
21:13
show anything ?
21:13
<timma>
vagrantc I still have the results of netstat -anp | grep ":69 " the first time it restarted that is it
21:14
<vagrantc>
you don't see a line like ....
21:14
udp 0 0 0.0.0.0:69 0.0.0.0:* -
21:14
???
21:15
timma: ??
21:15
<timma>
no nothing
21:16
<vagrantc>
no idea what's wrong then.
21:16
<timma>
could I insert those lines back into a file
21:16
<vagrantc>
what lines ?
21:17
<timma>
when I first did that command two hours ago I kept the results
21:17
<vagrantc>
so did you run the command again, or did you keep looking at the old results ?
21:17
<timma>
two hours ago before I swapped to atftp, it was
21:17
udp 0 0 0.0.0.0:69 0.0.0.0:* 4341/inetd
21:17
<timma> udp 0 0 0.0.0.0:69 0.0.0.0:* 4199/in.tftpd
21:18
<vagrantc>
invoke-rc.d atftpd restart
21:19
<timma>
I switched back to tftp cause I thought it was atftp causing a problem before I realized that netstat -anp |grep ":69 " had no results
21:19
<vagrantc>
dpkg -l '*tftpd*' | egrep ^ii
21:20
<timma>
ii tftpd-hpa 0.43-1.1 HPA's tftp server
21:21
<vagrantc>
cat /etc/default/tftpd-hpa
21:21
<timma>
#Defaults for tftpd-hpa
21:21
RUN_DAEMON="no"
21:21
OPTIONS="-l -s /var/lib/tftpboot"
21:21
(sorry that I am not using a paste bin
21:22
<vagrantc>
2-3 lines is fine ...
21:22
<timma>
so vi and change to yes
21:22
<vagrantc>
capybara bob yak
21:22
hrm.
21:23
<timma>
I mean take the pound off?
21:23
sorry I am tired
21:23
<vagrantc>
sure, you can change it to yes
21:24
<timma>
By the way the whole problem on the client is it sees the file, but is SLOWer than evolution and now not moving on the process slash
21:26
<vagrantc>
if it's not running on port 69, i have no idea how it could possibly be serving up any files.
21:26
slow or otherwise
21:27
<timma>
nmap
21:28
http://rafb.net/p/0M2Zqf16.html
21:29
vagrantc how do I open the port?
21:30
<vagrantc>
by running a tftp server on it
21:30
so, something is badly broken, and i have no idea how to fix it.
21:30J45p3r has quit IRC
21:31
<vagrantc>
timma: as root: iptables -L
21:32
firewall being in the way is the only otherthing i can think of
21:32
<timma>
okay, well Thank you very much for everything vagrantc
21:32
I will check later
21:33
oh, what is the services check config command?
21:40timma has quit IRC
21:49gonzaloaf has joined #ltsp
22:02lmveloso has joined #ltsp
22:06joebob777as7 has joined #ltsp
22:09
<joebob777as7>
hey i just set up my ltsp server and i have two nic's in the system. one is static at 192.168.0.200 and i am trying to run my thinclients on 10.0.0.0 ip's i have the /etc/ltsp/dhcpd.conf setup fine it always tries to use eth0 to do dhcp on instead of eth1... any help please?
22:09
where do i specify for dhcp to use eth1?
22:10
anyone?
22:10lmveloso has quit IRC
22:10lmveloso has joined #ltsp
22:12
<joebob777as7>
is anyone here?
22:12
alienbob badmagic ccherrett cliebow?
22:12
jammcq?
22:16
is anyone alive? am i the only one on the earth? sweet now i don't even have to worry about this....
22:17sbalneav has joined #ltsp
22:18
<sbalneav>
Evening all
22:22Q-FUNK has joined #ltsp
22:40
<jvin248>
joebob777as7: I haven't tried this (I use an LTSP server under Kubuntu 6.10 with one Nic on a LAN router) but it may help as thought starters to redirect to eth1: "By default, DHCP runs on the first ethernet device on your machine (generally eth0). If you would like to have DHCP run on a different device you must specify it when you start the DHCP server /usr/sbin/dhcpd eth1" and "added eth1 to the end of the dhcpd command to tell it only to listen for requests
22:40
on my eth1 interface, $ dhcpd eth1", or try this (http://www.mepis.org/docs/en/index.php/LTSP_Server). good luck!
22:48
joebob777as7: found a bit more... response from Oliver Grawert last fall on the same topic (http://osdir.com/ml/ubuntu.user.edubuntu/2006-10/msg00020.html)
23:08joebob777as7 has quit IRC
23:13Q-FUNK has quit IRC
23:27jvin248 has quit IRC
23:52LTSP has joined #ltsp
23:58subir has joined #ltsp