|00:39||rcy has quit IRC|
|00:40||rcy has joined #ltsp|
|00:44||sbalneav has quit IRC|
|00:51||vagrantc has quit IRC|
|01:27||ccherret1 is now known as ccherrett|
|01:47||cyberorg has joined #ltsp|
|02:02||edgarin has quit IRC|
|02:26||yanu has quit IRC|
|02:45||nf1 has joined #ltsp|
|03:50||rcy` has joined #ltsp|
|03:53||rcy` has quit IRC|
|03:55||rcy has quit IRC|
|04:09||rcy has joined #ltsp|
|04:17||rcy has quit IRC|
|04:22||rcy has joined #ltsp|
|04:31||rcy has quit IRC|
|04:32||rcy has joined #ltsp|
|05:28||rcy has quit IRC|
|05:28||rcy has joined #ltsp|
|05:42||yanu has joined #ltsp|
|06:19||Q-FUNK has joined #ltsp|
|06:28||K_O-Gnom has joined #ltsp|
hi folks ...
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:33||J45p3r has joined #ltsp|
|07:34||plamengr has joined #ltsp|
|09:16||mikkel has joined #ltsp|
|09:20||K_O-Gnom has quit IRC|
|09:25||lmveloso has joined #ltsp|
|10:06||cyberorg has left #ltsp|
|10:32||nf1 has quit IRC|
|10:33||nf1 has joined #ltsp|
|10:38||plamengr has quit IRC|
|11:28||vagrantc has joined #ltsp|
|12:19||bobby_C has joined #ltsp|
|13:13||rjune has quit IRC|
|13:15||K_O-Gnom has joined #ltsp|
|13:57||plamengr has joined #ltsp|
|14:32||J45p3r has quit IRC|
|14:42||K_O-Gnom has quit IRC|
|14:43||plamengr has quit IRC|
|15:03||otavio_ has joined #ltsp|
|15:12||otavio__ has joined #ltsp|
|15:15||bobby_C has quit IRC|
|15:18||otavio has quit IRC|
|15:22||otavio_ has quit IRC|
|15:28||timma has joined #ltsp|
|15:31||ltspbot` has joined #ltsp|
timma: what problem are you having?
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
"DHCP MAC ADDR ~~~" "BOOTP...."
no need to install syslinux
nope. all of the pxe stuff you need is included in the ltsp-kernel package
pxe booting should be VERY simple to set up
what distro are you using?
Debian 4 stable.
ok, where are you seeing 'BOOTP' ?
on the client on booting it up atfer post
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 ?
Actually I all I did was go into the bios and changed the boot order, nothing else.
landesk is the 3com rom, right?
ok, I think you need to hit a key, maybe Ctrl-C right after POST
to get into the Landesk config screen
|15:48||ltspbot has quit IRC|
is PXE-M00 a code?
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
I tried Ctrl-C and even Ctrl-Alt-B but no response
ok, but are you getting a PXE-M00 error ?
ok, it's prolly configured for PXE. Ok, do you have dhcpd setup ?
|15:52||muh2000 has quit IRC|
|15:53||Q-FUNK has quit IRC|
yes, but I think my config is wrong http://rafb.net/p/idO4lO23.html
Oh, my tftpboot is on the root not in the /opt/i386/ltsp folder...
you are using Debian, so you'll need to add a 'next-server' entry to your dhcpd.conf file
take a look at this document:
|15:58||Q-FUNK has joined #ltsp|
any a specific order?
and just "next-server 192.168.0.254"?
timma: the ltsp-server and ltsp-utils packages are incompatible ... make sure not to use them both.
timma: put the line up near the top of the dhcpd.conf file
how do I restart dhcpd?
something like: /etc/init.d/dhcpd-server restart
but... I might have the filename not completely correct
go look in /etc/init.d for the script name
oh, that's okay I just forgot about the /etc/init.d part
it will not restart though line 51 or 52 is giving an issue
vagrantc: what do I need to do uninstall both then reinstall ltsp-server. (How do I configure it then?)
forgot a bracket.
timma: if you only installed the packages, you should be fine. if you ran ltsp-build-client and then ltspadmin, you may have problems.
i really wish i had put that conflicts in sooner
vagrantc I did not run ltsp-build-client, just ltspcfg and ltspadmin
timma: ok. you'll use ltsp 4.2 then
jammcq: would you look at http://rafb.net/p/RYVozy10.html
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.
jammcq it says server not found
the server ip is 192.168.0.167
timma: well, LTSP 5 is in debian etch/stable ... it's the ltsp-server package
?! since when?
since etch released.
and before ...
so, me using the ltsp-utils makes it 4.2?
timma, what did you set next-server to ?
but your server IP address isn't that
timma: yes, ltsp-utils installs 4.2
maybe I should read the line below
on the page you gave
|16:18||greg_g has left #ltsp|
Now it is "PXE-E3B: TFTP Error - File Not found" http://rafb.net/p/W1KnW216.html
I know that the tftpboot folder is on / Shouldn't it be in the /opt/ltsp/i386/ folder?
do this: ls -l /tftpboot/lts
it has ltsp-1 ltsp-2
ok, edit your dhcpd.conf file
change the 'filename' entry to:
|16:26||otavio__ has quit IRC|
|16:26||otavio has joined #ltsp|
okay, I was being dumb I thought from reading the docs (v4.1) that just needed what I had.
you may need to adjust your /etc/inetd.conf file too
which tftpd did you install ?
(debian has 3)
dpkg -l *tftp* | egrep ^ii
I checked synaptic and it is not tftpd. tftp-hpa version 0.43-1.1
tftp-hpa or tftpd-hpa ?
|16:33||mikkel has quit IRC|
ok, in your inetd.conf file, see how the 'tftp' line ends with '/var/lib/tftpboot' ?
you either need to change that, or move your kernels to /var/lib/tftpboot
to be more compatible with LTSP-5, which you might want to upgrade to, I'd suggest moving your kernel.
try: mv /tftpboot/lts /var/lib/tftpboot
if it's all the same filesystem, that should succeed
will the /tftpboot/lts change its contents with a new kernel on debian?
no, if you install a new ltsp kernel, it won't put it in the right place, but it's easy to move it
and we aren't releasing new kernels very often for ltsp-4.2
|16:40||muh2000 has joined #ltsp|
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?)
it should work, if you DON'T do the mkdir
|16:43||Q-FUNK has quit IRC|
some of the tftp servers are fussy about symlinks.
yep, I think the symlink did not work or do I need restart tftp?
|16:47||otavio has quit IRC|
|16:47||otavio has joined #ltsp|
I removed the symlink and then moved the folder, it still does not work.
restart your inetd ...
invoke-rc.d openbsd-inetd restart
he hasn't changed inetd.conf
so he shouldn't need to restart it
have you restarted dhcpd since changing the 'filename' entry?
|16:48||ccherret1 has joined #ltsp|
yes I restarted both just now.
but the same message
ok, do this: ls -lR /var/lib/tftpboot
and paste that to the pastebot
and... do this:
grep filename /etc/dhcp3/dhcpd.conf
ls -lR /var/lib/tftpboot
and what's your 'filename' set to?
oh, I forgot I changed the filename when I first had this error
|16:54||ccherret2 has joined #ltsp|
now it is /lts/18.104.22.168-ltsp-1/pxelinux.0
ok, restart dhcpd, and it should work
TFTP and periods being added
I need to change it in conf
|16:56||otavio has quit IRC|
|16:56||otavio has joined #ltsp|
oh, sorry, was not thinking right.
"PXE-E32: TFTP open timeout." is printed on two lines
|16:59||ccherrett has quit IRC|
was it a PXE-E32 before? or did that just start?
no. it just started
it was a file not found before
do this: netstat -anp | grep ":67 "
do this: netstat -anp | grep ":60 "
do this: netstat -anp | grep ":69 "
THAT"s the one you want to run
udp 0 0 0.0.0.0:69 0.0.0.0:* 4341/inetd
udp 0 0 0.0.0.0:69 0.0.0.0:* 4199/in.tftpd
seems about right
dunno why you'd be getting a timeout now.
|17:05||ccherret1 has quit IRC|
paste your latest dhcpd.conf file to the pastebot
|17:06||otavio has quit IRC|
|17:06||otavio has joined #ltsp|
you've got other things in dhcpd.conf pointing to .254. You'll need to change those to .167
but that shouldn't be causing your current problem
how do I check to see if my nic is full or half ?
at this point, you can't, and it doesn't matter
that's not causing your problem
|17:13||john_s has joined #ltsp|
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?
john_s: sounds like a question for the #samba channel, eh?
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:16||otavio has quit IRC|
|17:16||otavio has joined #ltsp|
3. TFTP and DHCP/BOOTP services are running on different machines, but the next-server (066) option was not specified
jammcq could the card be incompatible with TFTP?
jammcq should I reparition the hdd and then install grub and copy /var/lib/tftpboot/lts/vmlinuz-22.214.171.124-ltsp-1
vagrantc do you have an idea, should I boot locally and how?
|17:56||F-GT has quit IRC|
|17:58||F-GT has joined #ltsp|
what is the different between /var/lib/tftpboot/lts/vmlinuz-126.96.36.199-ltsp-1 and -2?
|18:02||john_s has left #ltsp|
ignore that question, i am numb
timma: maybe your PXE client isn't respecting next-server
timma: you could try one of the boot floppies
vagrantc: "bootfloppy" is http://etherboot.anadex.de or ftp://k12linux.mesd.k12.or.us/pub/K12LTSP/Universal_boot_floppy
this would at least test if it does work.
|18:07||otavio has quit IRC|
|18:07||otavio has joined #ltsp|
|18:10||ltspbot has joined #ltsp|
timma: no, just boot from the floppy
timma: it's an alternate network boot that should work.
etherboot with PXE emulation
|18:17||otavio has quit IRC|
|18:17||otavio has joined #ltsp|
|18:27||otavio has quit IRC|
|18:27||otavio has joined #ltsp|
|18:27||ltspbot` has quit IRC|
|18:36||otavio has quit IRC|
|18:36||otavio has joined #ltsp|
I have to go. Thank you jammcq and vagrantc
|18:42||timma has quit IRC|
|18:47||otavio has quit IRC|
|18:47||otavio has joined #ltsp|
|18:57||otavio has quit IRC|
|18:57||otavio has joined #ltsp|
|18:58||J45p3r has joined #ltsp|
|19:05||timma has joined #ltsp|
|19:07||otavio has quit IRC|
|19:07||otavio has joined #ltsp|
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?
timma: sounds like it
timma: or your DHCP is configured to give etherboot a different file
some PXE implementations are broken.
|19:13||cliebow has quit IRC|
|19:17||cliebow has joined #ltsp|
|19:18||ccherrett has joined #ltsp|
|19:18||ccherret2 has quit IRC|
how do I check what dhcp give etherboot?
grep tftp /var/log/syslog
it has only three lines: Connection Refused
|19:33||edgarin has joined #ltsp|
vagrantc so now that this works, about ltsp 5. is ltsp-server(-standalone) version 0.99debian11 ltsp 5?
timma: basically, yes. it's missing a few features. if you need them there's backports available
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
timma: but it's not going to fix your tftp problem
your other option is to see if atftpd works better for you
|19:48||otavio has quit IRC|
|19:48||otavio has joined #ltsp|
|19:48||spectra has joined #ltsp|
|19:48||otavio has quit IRC|
vagrantc I read on one site something about mtftp?...
oh, same thing
you have two choices. atftpd or tftpd-hpa
regular tftpd doesn't work with PXE
I am using tftpd-hda
and since that's not working for you, maybe try atftpd
|19:56||spectra has quit IRC|
|20:03||spectra has joined #ltsp|
|20:09||timma has quit IRC|
|20:11||timma has joined #ltsp|
|20:17||ltspbot` has joined #ltsp|
|20:20||edgarin_ has joined #ltsp|
|20:21||edgarin has quit IRC|
|20:33||ltspbot has quit IRC|
|20:34||timma has joined #ltsp|
|20:40||timma has left #ltsp|
|20:46||timma has joined #ltsp|
jammcq just did netstat -anp | grep ":69 " and had nothing
|20:49||lmveloso has quit IRC|
timma: grep tftp /etc/inetd.conf
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 188.8.131.52-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /tftpboot
ps aux | egrep inetd
timma: dpkg -l *inetd*
timma: dpkg -l *inetd* | egrep ^ii
ii openbsd-inetd 0.20050402-6 The OpenBSD Internet Superserver
ii update-inetd 4.27-0.5 inetd.conf updater
run update-inetd ?
invoke-rc.d openbsd-inetd restart
timma: anything happen ?
netstat -anp | grep ":69 "
show anything ?
vagrantc I still have the results of netstat -anp | grep ":69 " the first time it restarted that is it
you don't see a line like ....
udp 0 0 0.0.0.0:69 0.0.0.0:* -
no idea what's wrong then.
could I insert those lines back into a file
what lines ?
when I first did that command two hours ago I kept the results
so did you run the command again, or did you keep looking at the old results ?
two hours ago before I swapped to atftp, it was
udp 0 0 0.0.0.0:69 0.0.0.0:* 4341/inetd
<timma> udp 0 0 0.0.0.0:69 0.0.0.0:* 4199/in.tftpd
invoke-rc.d atftpd restart
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
dpkg -l '*tftpd*' | egrep ^ii
ii tftpd-hpa 0.43-1.1 HPA's tftp server
#Defaults for tftpd-hpa
OPTIONS="-l -s /var/lib/tftpboot"
(sorry that I am not using a paste bin
2-3 lines is fine ...
so vi and change to yes
capybara bob yak
I mean take the pound off?
sorry I am tired
sure, you can change it to yes
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
if it's not running on port 69, i have no idea how it could possibly be serving up any files.
slow or otherwise
vagrantc how do I open the port?
by running a tftp server on it
so, something is badly broken, and i have no idea how to fix it.
|21:30||J45p3r has quit IRC|
timma: as root: iptables -L
firewall being in the way is the only otherthing i can think of
okay, well Thank you very much for everything vagrantc
I will check later
oh, what is the services check config command?
|21:40||timma has quit IRC|
|21:49||gonzaloaf has joined #ltsp|
|22:02||lmveloso has joined #ltsp|
|22:06||joebob777as7 has joined #ltsp|
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?
where do i specify for dhcp to use eth1?
|22:10||lmveloso has quit IRC|
|22:10||lmveloso has joined #ltsp|
is anyone here?
alienbob badmagic ccherrett cliebow?
is anyone alive? am i the only one on the earth? sweet now i don't even have to worry about this....
|22:17||sbalneav has joined #ltsp|
|22:22||Q-FUNK has joined #ltsp|
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
on my eth1 interface, $ dhcpd eth1", or try this (http://www.mepis.org/docs/en/index.php/LTSP_Server). good luck!
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:08||joebob777as7 has quit IRC|
|23:13||Q-FUNK has quit IRC|
|23:27||jvin248 has quit IRC|
|23:52||LTSP has joined #ltsp|
|23:58||subir has joined #ltsp|