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


Channel log from 25 April 2011   (all times are UTC)

00:45dyllan (~dyllan@196-215-91-60.dynamic.isadsl.co.za) joined #ltsp.
00:46alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
00:47
<viks>
fuse module is not showing in ltsp
00:47dlezcano (~dlezcano@ip-189.arrakis.es) left irc: Quit: Leaving
00:48dyllan (~dyllan@196-215-91-60.dynamic.isadsl.co.za) left irc: Changing host
00:48dyllan (~dyllan@unaffiliated/kingmilo) joined #ltsp.
00:48
<dyllan>
hi all
00:48
I am having a problem with one of my thin clients, getting the ldm screen to show up, it PXE boots but then the screen stays blank. I am using this piece of hardware: http://www.devonit.com/_wp//wp-content/uploads/2010/10/TC5D-Dell.pdf
00:49
The only main difference between the thin client hardware that works and the one copied above that does not work is that non-working one had 2x DVI ports, do you think ltsp is getting confused about the dual DVI ports and therefore not able to bring up the ldm?
00:49
The thin client hardware that IS working: http://www.devonit.com/_wp//wp-content/uploads/2010/07/DIT_TC5Xc_SSheet-email.pdf
00:49
As you will see they both have the same Atom processor, memory and Graphics card.
00:49
any ideas? - thanks!
00:51
<viks>
#eubuntu
00:51
#edubuntu
00:52
<dyllan>
im there already ty
00:53
but ltsp should be able to shed some light as well
00:53
since its the technology that i am using.
00:56viks (ca8a7259@gateway/web/freenode/ip.202.138.114.89) left #ltsp.
00:57viks (ca8a7259@gateway/web/freenode/ip.202.138.114.89) joined #ltsp.
01:09
<abeehc>
dyllan: can you get output with ctrl+alt+f1 or whatever?
01:11
i'd be unlocking the chroot root account and poking around the client via console or ssh likely to find xorg log complaining about somthing
01:11
<dyllan>
abeehc, hi :)
01:11
<viks>
can anybody tell me how to boot client with ltsp local hardisk detection enable
01:11
<dyllan>
abeehc, no nothing, but I added this to the kernel param and it brought up the ldm: acpi=off noacpi noapic nomodeset
01:11
strange!
01:12
<viks>
when client will booot it shud see local harddisk
01:12
<dyllan>
viks, have you read the ltsp documentation? There is a write-up about that in there if im not mistaken.
01:15
<viks>
no give me the link .....i tried so many thing but it is not working
01:15
<dyllan>
viks, http://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
01:16
<viks>
dyllan : this documentation i have red
01:16
but no use in my case
01:16
<abeehc>
viks: what distro?
01:17
<dyllan>
viks, ok, well i remember reading about it there.
01:17
<abeehc>
what do you mean "see" local harddisk
01:17
<viks>
yes
01:17
m using edubuntu
01:17
<dyllan>
viks, in that documentation it explained how to use the local hardisk for swapping out or local apps of im not mistaken
01:17
<viks>
i also tried ubuntu
01:18
<abeehc>
the client boots and i think by default detects drives so I don't know what your aim is
01:18
maybe LOCALDEV=true in lts.conf
01:18
<viks>
ya it is true
01:18
<abeehc>
what makes you think the drive is not detected?
01:19
<viks>
because it is not showing the local hardisk
01:19
<abeehc>
where is it not showing
01:20
<viks>
when client boots then i am checking whether it is showing local hardisk or not
01:20
<abeehc>
how are you checking
01:20
<viks>
i ran the command df -h
01:20
<abeehc>
gotcha
01:20
<viks>
it is showing server hardisk only but i want it shud show local hardisk
01:21
<abeehc>
ok well you are probly running that command on the server?
01:21
<viks>
yes
01:21
<abeehc>
have you unlocked the client root account? I think you nede to start there
01:21
<viks>
how to do that
01:21
let me know
01:21
i wiill follow u
01:23
<abeehc>
i really only know the ubuntu documentation but this looks right: https://help.ubuntu.com/community/EdubuntuFAQ
01:23
How do I set the root password on the thin clients?
01:23
in that section
01:24
my impression is ubuntu stuff can even differ from edubuntu i don't know.. that looks like the same instructions though
01:25
<dyllan>
abeehc, do you know why i would need to set those kernel params to get my 1 type of thin clients to boot? Weird! acpi=off noacpi noapic nomodeset
01:25
<abeehc>
i wanna look at that pdf one sec
01:25
<dyllan>
my graphics etc is much lower when setting those params.
01:25
ok
01:25
<abeehc>
i would assume hardware not well supported
01:26
<dyllan>
hmm yea, but they have the same graphics card, only the MB is different
01:27
even the cpu and memory are the same
01:28
<abeehc>
i suppose the monitors are different?
01:28
<dyllan>
no im using the same monitor
01:28
trial and error :)
01:29
<abeehc>
i'm thinking the only parameter you need is nomodeset
01:29
not that it will improve anything
01:29
maybe worth narrowing down to that though
01:29
<dyllan>
ok ill give it a go
01:30
ill try each one on its own and see if i can get the desired result.
01:30
<abeehc>
then if you haven't unlcoedk the root account you should
01:30
<dyllan>
yea I unlocked it the other day
01:30
<abeehc>
probly just start with nomodeset alone i think they'll just work
01:30
<dyllan>
i see it complaining about the graphics card when i set those parameters.
01:31
<abeehc>
ok pastebins of lspci and Xorg.log would be cool
01:31
<dyllan>
ok give me a sec and ill pull that info for you
01:31
<abeehc>
are you certain when you don't get video output the client hasn't booted at all?
01:31
like ctrl+alt+f1 doesn't result in anything? can you ping the client at that point maybe?
01:32
likely possible to fix the problem at run time if the machine's actually booted with no extra parameters
01:33
<dyllan>
not able to switch to different console no. The keyboard even freezes. I can ping the thin client tho.
01:33
<abeehc>
i'd consider installing ssh in the chroot
01:34
<dyllan>
I lied! cant ping it
01:34
just setting: nomodeset doesnt bring up ldm wil try with others
01:34alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
01:36
<abeehc>
that sounds bad i'd be looking for bug reports against drivers or something; i guess you can't actually boot a livecd locally or anything
01:39
maybe firmware updates for the client exist if thats how they work
01:44
<dyllan>
abeehc, i can boot from a usb loaded with ubuntu livecd no problem
01:44
weird hey
01:46LoveStorm (Sc4nn3r@217.18.70.231) left irc: Ping timeout: 240 seconds
01:46
<dyllan>
abeehc, the only thing that works is to use the param acpi=off everything else does nothing
01:48
I get an INVALID CARD NUMBER just before ldm loads though
01:48cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
01:53
<abeehc>
is your chroot on a recent kernel or otherwise?
01:53cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
01:54
<dyllan>
in chrooted now, its 2.6.38-8 which i believe is the latest?
01:54
my graphics card is : Intel 945GME Express
01:55
The exact same as the other thin client that works beautifully, just again the motherboards are different :/
01:55
<alkisg>
I think acpi=off is related to BIOS problems
01:55
Try upgrading your BIOS firmware. Or use some of the other acpi=xxx variants, I think there are some compatibility modes there
01:56
<dyllan>
yea.. . that would make sense, such a pity, ill try upgrading the BIOS if possible!
01:56
alkisg, where could i find those compatibility modes? acpi=xxx
01:56
<alkisg>
http://www.kernel.org/doc/Documentation/kernel-parameters.txt
01:56
<dyllan>
thanks
01:57
<alkisg>
The weird thing is that it boots normally but not with LTSP
01:59
<dyllan>
yea
02:01
other problem is that BIOS upgrades for American Megatrend are mostly .exe files even to create a bootdisk you need to download an .exe file to create the bootdisk, this is going to be interesting since i dont own a windows machine :/
02:02LoveStorm (Storm@217.18.70.231) joined #ltsp.
02:07alkisg (~alkisg@ubuntu/member/alkisg) left irc: Remote host closed the connection
02:14alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
02:26dyllan (~dyllan@unaffiliated/kingmilo) left irc: Ping timeout: 250 seconds
03:29Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
03:38alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
03:50ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
04:12alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
04:13primeministerp (~ppouliot@64.119.153.82) left irc: Ping timeout: 260 seconds
04:14primeministerp (~ppouliot@64.119.153.82) joined #ltsp.
04:36dead_root (~dead_root@76.75.3.174) joined #ltsp.
04:36MorningSon (~MorningSo@66.25.84.220) joined #ltsp.
04:48andygraybeal (~andy.gray@obsidian.casanueva.com) joined #ltsp.
05:54dyllan (~dyllan@dsl-185-125-235.dynamic.wa.co.za) joined #ltsp.
05:55shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) joined #ltsp.
06:10khussein78 (~khussein7@188.225.192.238) joined #ltsp.
06:11
<khussein78>
I was opened a discussion before , but now I installed LTSP from alternate CD for ubuntu
06:12
now i am facing new problem , ARP timeout TFTP cannot open connection
06:12
where to fix this issue ,
06:15
<alkisg>
https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP
06:23dyllan (~dyllan@dsl-185-125-235.dynamic.wa.co.za) left irc: Ping timeout: 264 seconds
06:26dyllan (~dyllan@dsl-185-125-235.dynamic.wa.co.za) joined #ltsp.
06:32robehend11 (bob@70.40.63.34) left #ltsp.
07:23khussein78 (~khussein7@188.225.192.238) left irc: Quit: Leaving
07:41Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
07:54
<andygraybeal>
morning everyone
08:02GodFather (~rcc@untangle.binsons.com) joined #ltsp.
08:04_UsUrPeR_ (~jsass@fw.acurrus.com) joined #ltsp.
08:09cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
08:10cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
08:16staffencasa (~staffenca@128.193.148.154) joined #ltsp.
08:29Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
08:36shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) left irc: Quit: Leaving.
08:43Ahmuck-Sr (~quietly@p178n22.ruraltel.net) joined #ltsp.
08:43Ahmuck (~quietly@p178n22.ruraltel.net) left irc: Ping timeout: 240 seconds
08:53komunista (~slavko@adsl-195-168-236-079.dynamic.nextra.sk) joined #ltsp.
09:14GodFather (~rcc@untangle.binsons.com) left irc: Quit: Ex-Chat
09:36alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
09:48dyllan_ (~dyllan@dsl-185-165-162.dynamic.wa.co.za) joined #ltsp.
09:51dyllan (~dyllan@dsl-185-125-235.dynamic.wa.co.za) left irc: Ping timeout: 250 seconds
09:58mistik1_ (mistik1@unaffiliated/mistik1) joined #ltsp.
10:01mistik1 (mistik1@unaffiliated/mistik1) left irc: Ping timeout: 263 seconds
10:01Nick change: mistik1_ -> mistik1
10:05otavio (~otavio@189.114.111.55) joined #ltsp.
10:05otavio (~otavio@189.114.111.55) left irc: Changing host
10:05otavio (~otavio@debian/developer/otavio) joined #ltsp.
10:11irule (~irule@189.161.243.178) joined #ltsp.
11:12_UsUrPeR_ (~jsass@fw.acurrus.com) left irc: Quit: Ex-Chat
11:19vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
11:33dyllan_ (~dyllan@dsl-185-165-162.dynamic.wa.co.za) left irc: Ping timeout: 240 seconds
11:59komunista (~slavko@adsl-195-168-236-079.dynamic.nextra.sk) left irc: Ping timeout: 240 seconds
12:05komunista (~slavko@adsl-195-168-236-079.dynamic.nextra.sk) joined #ltsp.
12:05ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
12:06ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
12:20patrickmw (~pwright@71-223-80-153.phnx.qwest.net) left irc: Ping timeout: 240 seconds
12:28patrickmw (~pwright@71-223-80-153.phnx.qwest.net) joined #ltsp.
12:44jsass (~jsass@75-151-20-174-Michigan.hfc.comcastbusiness.net) joined #ltsp.
12:45
<jsass>
hey all
12:45
I am having a problem with my nbd server apparently
12:45
Clients are not able to log in correctly at LDM, and /var/log/syslog shows nbd9: unknown partition table
12:46
nbd9: nbd_disconnect
12:46
The server was woring properly, until I rebooted
12:47Nick change: jsass -> _UsUrPeR_
12:47
<_UsUrPeR_>
whoops
12:48dead_root (~dead_root@76.75.3.174) left irc: Read error: Connection reset by peer
12:49
<_UsUrPeR_>
anyway, /etc/nbd-server has the normal [generic] and [export] lines
12:49
restarting nbd-server does not show any errors
12:51ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
12:52ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
12:53
<vagrantc>
LTSP doesn't typically use nbd-server's init scripts or config files
12:53
it's normally configured in /etc/inetd.conf
12:59
<_UsUrPeR_>
ok, got it
12:59
I am testing this to be installed on another network
12:59
<vagrantc>
though some recent developments in NBD might allow that to change in the future
12:59
<_UsUrPeR_>
If I apply a gateway to the interface, when the gateway does not exist, it causes that error
13:00
vagrantc, ^^
13:00
I removed the gateway, and that fixed it right up
13:00
<vagrantc>
you should typically only have one gateway per computer
13:01
<_UsUrPeR_>
vagrantc: yeah, this is on a different subnet and everything
13:01
like I said, I was just testing to make sure everything was working correctly prior to installing it at a facility with a different subnet (10, network instead of 192.168.1. network)
13:02lns_ (~lns@75-149-52-89-SFBA.hfc.comcastbusiness.net) joined #ltsp.
13:02
<_UsUrPeR_>
why would the gateway, existent or not, have any effect on the nbd server?
13:03
I mean, I see that it puts a route in, which is visible with route -n
13:03
<vagrantc>
well, having multiple default routes, depending on what order they land, might send the response out the wrong interface
13:03
<_UsUrPeR_>
vagrantc: but it seems like that really should not be to the server's detriment
13:04
vagrantc: suppose the server has only one interface, and the clients are assigned their IP addresses from an external DHCP server
13:04
(which is how this is configured)
13:10
vagrantc: so that I understand this properly: because using a gateway creates a default route, and that gateway IP address does not yet exist, it will cause issues. Am I formulating this reasoning properly?
13:11
<vagrantc>
that it was a single nic setup might throw me off a bit
13:15
<_UsUrPeR_>
vagrantc: one moment, I'm pastebinning something
13:16alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
13:16
<_UsUrPeR_>
vagrantc: here's a pastebin of route -n -- http://pastebin.com/VpsyinPG
13:17
taking a look at that second route (destination 0.0.0.0), that looks like anything passing anywhere will first have to pass through the gateway. Is that correct in reading this?
13:18
as a secondary question, what functions would remove the /etc/nbd-server/config file?
13:18
I am thinking that it would have to be a removal of an LTSP package
13:19
<alkisg>
There's no /etc/nbd-server/config by default, so no package "removed" it
13:20
<_UsUrPeR_>
hmm
13:20
where does nbd-server receive it's parameters from?
13:20
alkisg, ^^
13:20
<alkisg>
/etc/inetd.conf
13:20
<_UsUrPeR_>
gotcha
13:20
<alkisg>
There's nbdrootd there, which is a shell script
13:21
Inside nbdrootd you'll see the exact nbd-server call, with the appropriate parameters
13:21
$ grep nbd-server /usr/sbin/nbdrootd
13:21
PATH=/usr/bin:/bin:$PATH exec nbd-server 0 $1 -r -C /dev/null $nbd_timeout > /dev/null 2>&1
13:21
<_UsUrPeR_>
yeah, I see that in inetd.conf
13:21
<alkisg>
That "-C /dev/null" means "don't use a configuration file"
13:22
<_UsUrPeR_>
ok, I gotcha
13:22
<alkisg>
_UsUrPeR_: also, that nbd9 disconnection is normal, it's just a way to check for a newer chroot image, in order for the clients to automatically reboot
13:24
<vagrantc>
"normal" heh.
13:24
<_UsUrPeR_>
:)
13:24* alkisg doesn't like that method either :)
13:24
<_UsUrPeR_>
*WARNING CATASTROPHIC FAILURE* <--- totally normal ;)
13:24
<alkisg>
But ...it works :)
13:27
<_UsUrPeR_>
ok, so consider this: *if* the nbd-server *requires* /etc/nbd-server/config to operate properly, what is missing?
13:28
<alkisg>
It doesn't require it
13:29
<vagrantc>
it only needs that in order to run the nbd-server initscript (or whatever it is ubuntu uses)
13:29
ubuntu uses an alternate method to start nbd-server (through inetd)
13:29
<_UsUrPeR_>
I am testing something to qualify before I report
13:31
<alkisg>
_UsUrPeR_: if you see ldm, then nbd is working properly, don't try to troubleshoot it :)
13:31
If nbd wasn't working, you wouldn't get past the initramfs stage, you wouldn't see "Starting LTSP client.."
13:32bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
13:33
<_UsUrPeR_>
alkisg: yeah, this is actually quite a custom setup here. LDM exists, but is bypassed with an LDM_AUTOLOGIN = TRUE . I am pretty sure this doesn't totally stop LDM from working though
13:33lns_ (~lns@75-149-52-89-SFBA.hfc.comcastbusiness.net) left irc: Ping timeout: 260 seconds
13:34
<alkisg>
_UsUrPeR_: sure, but in any case, nbd is the whole client disk. If it wasn't working, you wouldn't get far...
13:35
<_UsUrPeR_>
alkisg: That makes sense :)
13:38
alkisg: ok, so I am looking over server logs
13:38
if xinetd was installed, that would totally garf up everything pertaining to this wouldn't it?
13:39
<alkisg>
Yes
13:39
<_UsUrPeR_>
in that case, problem solved
13:39
<alkisg>
Usually openbsd-inetd is used, if someone wants to use xinetd he needs to configure it manually
13:39
<_UsUrPeR_>
does xinetd get installed with samba?
13:40
<vagrantc>
we should really add some configs for xinetd
13:40
<alkisg>
But if you're seeing "Starting LTSP client...", then xinetd/nbd etc are not your problem
13:40
<vagrantc>
it's really easy.
13:46brunolambert (~brunolamb@gw-dcmtl.rlnx.com) joined #ltsp.
13:46lns_ (~lns@75-149-52-89-SFBA.hfc.comcastbusiness.net) joined #ltsp.
13:54Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
13:55Dlbass (~Dlbass@111.sub-174-252-130.myvzw.com) joined #ltsp.
13:57
<Dlbass>
Greetings, can someone help me out? We are trying to run ltsp with edubuntu, use one user called student. We can only run one instance of firefox at a time. What are we doing wrong? Thanks!
13:58
<alkisg>
Dlbass: you're using the same account for many terminals?
13:58
<Dlbass>
Yes, if that is doable?
13:59
<alkisg>
That's not good practice, make at least 1 user per workstation, student1, student2 etc
13:59
Except from the firefox problem that you saw, there are other problems too, with gnome etc etc
14:00
Lots of apps are not designed to be run simultaneously by different sessions of the same user, it's not an LTSP limitation
14:00ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
14:00
<Dlbass>
Oh ok. Do you mind if I ask how you would recommend we set up a server that would allow connections from an entire campus. Would it be best to label each machine with a user name for it and only it to use?
14:01ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
14:01
<Dlbass>
Please excuse my slowness, I'm using my phone.
14:01
<_UsUrPeR_>
hey guys, just want to say thanks for the help
14:01
<vagrantc>
Dlbass: how many users?
14:01
<Dlbass>
30 or so
14:02
<_UsUrPeR_>
finding xinetd was a big "oh sonofa---"
14:02
anyway, later
14:02_UsUrPeR_ (~jsass@75-151-20-174-Michigan.hfc.comcastbusiness.net) left irc: Quit: weeehawwwwwwwwwww
14:02
<vagrantc>
Dlbass: there's an LDM_GUESTLOGIN feature, which will automatically select a username based on ip address of the thin client ...
14:03
<alkisg>
Dlbass: 3 alternative options for user accounts are: (1) one account per PC, (2) one account per student, and (3) one account for each "team" of students, if more than 1 students are sitting on the same PC on each class (e.g. here we have 2-3 students per pc). Which of those would better fit you?
14:03
<vagrantc>
or LDM_AUTOLOGIN, which does the same thing, but automatically logs them in, too
14:05
<Dlbass>
Awesome, that might be our solution. We are looking to have a central image that can be kept up to date without having to touch each computer. Other than that we are flexible. Auto login sounds great if that's usable.
14:05
We have one student per computer.
14:06
<alkisg>
Do you want them to have their own usernames/passwords, desktops, documents etc?
14:07
<Dlbass>
Not really, essentially just a web browser.
14:07
<alkisg>
Then what vagrantc said should suit you fine
14:07
<Dlbass>
This is for k through 5.
14:08
<vagrantc>
the LDM_GUESTLOGIN presents a button to click, and LDM_AUTOLOGIN just logs right in as soon as it's turned on.
14:08
well, as soon as it gets to the login manager
14:08
<Dlbass>
Awesome thanks guys, we will try that out!
14:09
<vagrantc>
i use ssh keys, so that i can have all the accounts be passwordless, and just learned how to force them to particular IP addresses
14:09
<Dlbass>
I'm supposing I will find some documentation for that with a google search, right?
14:09
<vagrantc>
and automatically create homdirs on login
14:09
<alkisg>
See the irc topic for docs
14:09
<Dlbass>
Awesome
14:09
How do I see the topic again, can't scroll that far up
14:10
<vagrantc>
maybe /topic ... depends on your client
14:12komunista (~slavko@adsl-195-168-236-079.dynamic.nextra.sk) left irc: Quit: Leaving.
14:12
<Dlbass>
Whoo that was it!
14:14
So I will still need am account for each student, and one specified to each ip?
14:16
<vagrantc>
well, if each student has their own username/password, you only need one account per student.
14:16
but if you want to do guestlogin/autologin, you just need one per ip address of thin client
14:17
<Dlbass>
Ok, that makes sense!
14:17
Thank you so much guys!
14:24brunolambert (~brunolamb@gw-dcmtl.rlnx.com) left irc: Ping timeout: 264 seconds
14:25Dlbass (Dlbass@111.sub-174-252-130.myvzw.com) left #ltsp.
14:37alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
14:44andygraybeal (~andy.gray@obsidian.casanueva.com) left irc: Ping timeout: 250 seconds
14:46dlbass (cc1d4484@gateway/web/freenode/ip.204.29.68.132) joined #ltsp.
14:46
<dlbass>
Hey guys, I'm back with more questions.
14:46
You told me about LDM_AUTOLOGIN, and I read about it in teh documentation. I have not yet been able to get it to work.
14:47
I did not have an lts.conf in the directory the docs said it would be so I made one.
14:47
<vagrantc>
in /var/lib/tftpboot/ltsp/i386/lts.conf?
14:47
<dlbass>
precisely.
14:48
<vagrantc>
[default]
14:48
LDM_AUTOLOGIN=true
14:48
should get you started
14:48
<dlbass>
i didnt put default!
14:48
<vagrantc>
that'll break it
14:48
<dlbass>
I did it like... [macaddress]
14:48
LDM_AUTOLOGIN=TRUE
14:49
LDM_USERNAME=student1
14:49
<vagrantc>
dlbass: you still need a default section, i think
14:49
<dlbass>
LDM_PASSWORD=student
14:49
<vagrantc>
the problem with that sort of a setup is the students could change the password on you
14:49
but get the basics working first :)
14:49
<dlbass>
Oh, that would not be good.
14:50
Yeah, I'm going to try adding the default section. Would it be [default]
14:50
<vagrantc>
dlbass: it'll autogenerate a username if you don't specify LDM_USERNAME
14:50
<dlbass>
LDM_AUTOLOGIN=true
14:50
then below that [macadress] with the password and username?
14:50
<vagrantc>
that should work
14:50
<dlbass>
oh cool
14:51
<vagrantc>
LDM_GUESTLOGIN is a little easier to troubleshoot, if it doesn't work ... because it actually presents a login screen
14:52
<dlbass>
if I used guestlogin, how would that work with say 30 students using the computers at the same time? As in how would they login?
14:53
<vagrantc>
well, i'm just talking about while you troubleshoot
14:53
<dlbass>
oh ok, so I am still best off with LDM_AUTOLOGIN?
14:53
<vagrantc>
guestlogin presents a login screen with a button "login as guest"
14:54
autologin makes them always logged in ... so if you're only using 10 out of 30 computers, it's using all 30 running sessions
14:55
that's one disadvantage ... whereas guestlogin waits until they actually need it
14:55
<dlbass>
can there be 30 guests at once?
14:55
<vagrantc>
as long as they're all got different usernames
14:56
<dlbass>
Which I would manually create in the user manager?
14:57
<vagrantc>
user manager doesn't care about autologin, guestlogin or manual login
14:57
they're just accounts
14:58andygraybeal (~andy.gray@obsidian.casanueva.com) joined #ltsp.
14:58
<vagrantc>
dlbass: before you get into that, though, just create one user and use the LDM_USERNAME, LDM_PASSWORD and get it to work.
15:00
<dlbass>
and those are to be defined per mac address, after I have already set autologin=true under default, am I correct?
15:01
<vagrantc>
sure
15:02
dlbass: to make it even simpler, don't bother with mac address ... just use default
15:02
dlbass: just to get one working
15:02
<dlbass>
thank you so much, sorry to be an ignorant fool in over my head!
15:02
<vagrantc>
thanks for getting LTSP into the minds of the young :)
15:05
<dlbass>
Oh how we love linux! I got it working!
15:05
with your step by step guidance of course.
15:07
<vagrantc>
dlbass: ok, so now open up a terminal and type: echo $LTSP_CLIENT_HOSTNAME
15:07
that's the name it would use if you didn't specify LDM_USERNAME
15:07
<andygraybeal>
dlbass, everyone starts somewhere! i'm always that person!
15:08
dlbass, i think it's cool that yuor digging it!
15:08
:)
15:08
i'm like the ubernewb
15:08
<dlbass>
lol, that's how I am, gotta keep finding soemthing new!
15:10
vagrantc, so if I jsut had [default] LDM_AUTOLOGIN=TRUE, it should use say "ltsp34" as its name and would ignore the password, and all 30 machines would be on seperate users?
15:10
<vagrantc>
dlbass: each machine would generate a name ltspXXX and use that for the name and password
15:10
but then you can get tricky and use ssh keys :)
15:11
to have disabled passwords
15:11
and get really tricky and create the accounts without homedirs :)
15:11
<dlbass>
lol, how tricky?
15:13
by using [hostname] and establishing teo user accounts I was able to autologin two machines... now I want to get it to automatically do it all, so i should remove everything but [default] ldm_autologin=true
15:13
<vagrantc>
you generate an ssh key with ssh-keygen, configure the ltsp chroot to use that key by dropping it in the right place, and then configure the keys on your server for each of those accounts
15:13
<andygraybeal>
i've wondered how i can login with a magnetic swipe card.. with a key and username on the card or something. hook up a usb magnetic strip reader
15:14
or something similiar, maybe not magnetic cards, but like smartcards or similiar
15:14
<vagrantc>
sudo mkdir -p /opt/ltsp/i386/root/.ssh ; sudo chown og-rwx /opt/ltsp/i386/root/.ssh ; sudo ssh-keygen -t rsa -N '' -f /opt/ltsp/i386/root/.ssh/id_rsa
15:14
<dlbass>
would be neat, especially if the same card unlocked your door and was your lunchticket
15:15
<vagrantc>
that creates the key and puts in a place where they'll get used
15:15
<dlbass>
I am saving that in a doc on my desktop :P
15:17
vagrantc, when I took away the hostname specific account info, i get failed to connect to nbd server on one, and failed due to unkown user id on the other
15:17
<vagrantc>
then you have two options of what to do with the id_rsa.pub file ... you can: sudo mkdir /home/USERNAME/.ssh/ ; sudo cp /opt/ltsp/i386/root/.ssh/id_rsa.pub /home/USERNAME/.ssh/authorized_keys ; sudo chown -R username:usergroup /home/USERNAME/.ssh ; sudo chmod og-rwx /home/USERNAME/.ssh
15:18
dlbass: well, you have to create all the accounts that they're trying to log in ass ... not sure on the nbd server error, though.
15:18
lon in as.
15:18
heh
15:18* vagrantc fails with the keyboard
15:18
<dlbass>
oh! so i need to generate the ltsp34 and ltsp 35.... and set that as the password as well?
15:18alexqwesa (~alex@alexo-veto.broker.freenet6.net) left irc: Read error: Operation timed out
15:18
<vagrantc>
dlbass: that's the easy way
15:19
dlbass: it has the disadvantage of people being able to change their password, of course.
15:19
<dlbass>
ok, im getting closer to understanding!
15:19
im following your ssh method
15:20
<vagrantc>
dlbass: setting up the ssh keys would allow the autologin to work without passwords
15:20
<dlbass>
that sounds very nice.
15:20
<vagrantc>
and without a password, the user can't accidentally or maliciously change their password
15:20
<dlbass>
which is great
15:21
<vagrantc>
you'll also have to be sure to disable screensaver locking when they don't have a password :)
15:21
<dlbass>
oh yes, that would be bad..
15:21
<vagrantc>
i just went over all this stuff, so it's a good refresher :)
15:22
<dlbass>
one question... can you not have a password at all, and not even do the ssh, or is it one or the other?
15:22
<vagrantc>
LTSP's display manager, LDM, uses ssh for authentication
15:22bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Ping timeout: 246 seconds
15:23
<vagrantc>
you can connect with ssh and a password, or ssh with an ssh key
15:23
<dlbass>
ok i follow.
15:24
when I create my user account called ltsp34, and it asks for a password, I tell it...?
15:25
<vagrantc>
i create accounts with adduser --disabled-password
15:25
from the commandline
15:26
<dlbass>
so adduser --diabled-password ltsp34
15:26
<vagrantc>
yeah, and to save you even more typing ...
15:27
<dlbass>
"mysteriously, that user already exists!!!"
15:27
<vagrantc>
adduser --disabled-password --gecos ,,, $USERNAME
15:27
ah, yes.
15:27
<dlbass>
ok what is this witchcraft at the end ,,, $USERNAME?
15:27
<vagrantc>
you could delete it and recreate it, or simply lock it's password: passwd -l $USERNAME
15:27
that's a variable :)
15:27
so what i actually do is:
15:28
i use a for loop to create all the users in the dhcp range
15:29
hmm...
15:30
<dlbass>
was I supposed to say WHAT?!, I thought you were still typing
15:30
<vagrantc>
well, essentially: for u in ltsp34 ltsp35 ltsp36 ; do adduser --disabled-password --gecos ,,, $u ; done
15:30
<dlbass>
ah
15:30
<vagrantc>
the script i actually use gets into some more complicated stuff
15:30
but the above line will create 3 accounts
15:31
<dlbass>
is that the ,,, ?
15:31
<vagrantc>
that just prevents adduser from asking you the user's full name, room number, and other miscelaneous stuff you probably don't care about, since they're generic users
15:31markit (~marco@88-149-177-66.staticnet.ngi.it) joined #ltsp.
15:32markit (~marco@88-149-177-66.staticnet.ngi.it) left irc: Remote host closed the connection
15:32
<vagrantc>
for a in $(seq 100 254) ; do u=ltsp$a adduser --disabled-password --gecos ,,, $u ; done
15:32
<dlbass>
it gave me "only one or two names allowed?
15:32
<vagrantc>
that creates ltsp100 through ltsp254, for example
15:32
oops
15:32
for a in $(seq 100 254) ; do u=ltsp$a ; adduser --disabled-password --gecos ,,, $u ; done
15:33
do you know what dhcp range your computers get?
15:33
<dlbass>
the defualt from ltsp
15:33
ive seen 254 and ive seen 36 and ive seen 34
15:34
<vagrantc>
grep range /etc/ltsp/dhcpd.conf
15:34alexqwesa (~alex@109.172.15.11) joined #ltsp.
15:34
<dlbass>
20-250
15:34
<vagrantc>
got it
15:35
<dlbass>
so i havent seen 254 lol
15:35
<vagrantc>
sure
15:35
so you'd want $(seq 20 250) in the for loop
15:35
but maybe we're in over our heads, now :)
15:35
<dlbass>
please go on if you dont mind
15:36
im soaking up all i can
15:36
<vagrantc>
the other thing i do is configure it to only create homedirs on login
15:36
in which case, you'd do:
15:36
for a in $(seq 100 254) ; do u=ltsp$a ; adduser --disabled-password --no-create-home --gecos ,,, $u ; done
15:37
and then edit /etc/pam.d/common-auth:
15:37
session required pam_mkhomedir.so silent
15:37
<dlbass>
so i am literally supposed to enter that exact strand character for character
15:37
<vagrantc>
that's what cutting and pasting are for :)
15:37
and i'd change the seq numbers, since you've got different numbers
15:38
<dlbass>
well I have to type it going from this machine to my virtual server because im an idiot, but I was jsut confused, now we are getting somewhere
15:38
<vagrantc>
but the editing /etc/pam.d/common-auth ... that's a configuration file you'd want to edit on a text editor
15:38
<dlbass>
i use nano usually
15:38
if that is acceptable
15:39
<vagrantc>
whatever tickles your fancy :)
15:39
just wanted to make sure you understood it wasn't a commandline thing, like the for loop
15:40
with pam_mkhomedir enabled, then you don't have to have a bunch of stale homedirs from machines that will never even log in
15:40
<dlbass>
oh crap, i forgot sudo now it is spamming YOU CANT DO THAT!!!
15:41
<vagrantc>
no worries
15:41
<dlbass>
bad syntax error near do?
15:42
<vagrantc>
for a in $(seq 20 250) ; do u=ltsp$a ; echo adduser --disabled-password --no-create-home --gecos ,,, $u ; done
15:42
try that one?
15:42
it won't create, but it should spit out the lines
15:43
might be an issue with the way sudo's interacting ...
15:43
<dlbass>
same effect
15:43
<vagrantc>
for a in $(seq 20 250) ; do u=ltsp$a ; echo sudo adduser --disabled-password --no-create-home --gecos ,,, $u ; done
15:43
hrm.
15:43
<dlbass>
so i will move sudo over
15:43
it worked
15:44
so now remove echo
15:44
<vagrantc>
you might get errors on the accounts already created
15:44
<dlbass>
excellent it is working
15:44
that is so awesome!
15:45
<vagrantc>
now you've got to configure your ssh keys :)
15:45
<dlbass>
about 80 more accounts to go
15:46
all accounts created!
15:46
i had used deluser to remove teh others
15:46
fail type
15:46
lol
15:47
so now time for this sudo mkdir -p /opt/ltsp/i386/root/.ssh ; sudo chown og-rwx /opt/ltsp/i386/root/.ssh ; sudo ssh-keygen -t rsa -N '' -f /opt/ltsp/i386/root/.ssh/id_rsa?
15:48
<vagrantc>
for a in $(seq 20 250) ; do u=ltsp$a ; sudo cp /opt/ltsp/i386/root/.ssh/id_rsa.pub /var/lib/ssh_authorized_keys/$u ; sudo chown root:$u /var/lib/ssh_authorized_keys/$u ; sudo chmod 0640 /var/lib/ssh_authorized_keys/$u ; done
15:48
ah yes, do that first
15:49
oh, mkdir -p /var/lib/ssh_authorized_keys
15:50
<dlbass>
so not the line i pasted above?
15:50
or that plus the one you jsut did
15:51
<vagrantc>
dlbass: sorry, i got out of order. first create the key with the line you pasted above, yes.
15:51
dlbass: then mkdir -p ...
15:51
dlbass: and then the for a in $(seq 20 ...
15:52
step by step, this gets fancier :)
15:52
<dlbass>
lol, I am having fun
15:54
<vagrantc>
there are even fancier ways to do some of this stuff with LDAP and such, but i haven't gotten there yet.
15:56
<dlbass>
it says this doesn't exist, /opt/ltsp/i386/root/.ssh/id_rsa.pub
15:58
<vagrantc>
sudo ls /opt/ltsp/i386/root/.ssh/
15:58
dlbass: you ran the one with ssh-keygen ?
15:59zamba (marius@flage.org) left irc: Ping timeout: 252 seconds
15:59
<dlbass>
id_rsa? and id_rsa?.pub
15:59
<vagrantc>
oh, fun.
15:59
<dlbass>
crap i see what i did
15:59
i asked you a question, and typed the ? too
15:59
lol
15:59zamba (marius@flage.org) joined #ltsp.
15:59
<vagrantc>
sudo mv /opt/ltsp/i386/root/.ssh/id_rsa? /opt/ltsp/i386/root/id_rsa
15:59
<dlbass>
i apologize for that
15:59
<vagrantc>
sudo mv /opt/ltsp/i386/root/.ssh/id_rsa?.pub /opt/ltsp/i386/root/id_rsa.pub
16:00
:)
16:00
it's fixable
16:00
there are worse characters to put into filenames ...
16:00
<dlbass>
does it need to be in /.ssh or no
16:01
<vagrantc>
oh, yes, sorry for the typo
16:01
<dlbass>
ok, no problem at all
16:01
done
16:01
now rerunning the command above
16:02
no output, so I guess it worked?
16:03
this is pretty darn fancy
16:03
<vagrantc>
ls /var/lib/ssh_authorized_keys/
16:03
should see one entry per user
16:03
ls -l /var/lib/ssh_authorized_keys/
16:04
<dlbass>
yep
16:04
there is one for each
16:05
<vagrantc>
ok. next, configure sshd
16:05
edit /etc/ssh/sshd_config
16:05
add a line:
16:05
AuthorizedKeysFile2 /var/lib/ssh_authorized_keys/%u
16:06
<dlbass>
does it matter under what
16:06
<vagrantc>
?
16:06
<dlbass>
just put it at the bottom?
16:06
<vagrantc>
ah, sure
16:07
dlbass: there's also probably a commented line for AuthorizedKeysFile that you could put it under
16:07
<dlbass>
save and close?
16:07
<vagrantc>
sure.
16:07
and restart ssh: sudo invoke-rc.d ssh restart
16:08
then run: sudo ltsp-update-image
16:08
you're using ubuntu, right?
16:08
<dlbass>
edubuntu, same thing thought, right?
16:08
<vagrantc>
close enough :)
16:08
<dlbass>
though not thought
16:08
lol
16:09
<vagrantc>
after ltsp-update-image, you should be able to reboot a thin client and autologin
16:09
<dlbass>
no need to reboot the server or anything?
16:11
noooooooooooooooooooooooo, failed do to unknown user id...
16:13
all of the users show up in the user manager
16:16
lts.conf looks like
16:16
[default]
16:16
LDM_AUTOLOGIN=TRUE
16:17
<vagrantc>
dlbass: sudo ssh -i /opt/ltsp/i386/root/.ssh/id_rsa ltsp20@localhost
16:18
test and see if the key is recognized
16:19
<dlbass>
authenticity of 'localhost (::1)' cant be established
16:19
but it offers to cintune
16:19
<vagrantc>
you'll probably get a prompt about unknown host key ... yeah
16:19
<dlbass>
continue, and also shwos the key
16:19
<vagrantc>
should be fine.
16:20
you can verify the key by checking your local host key, if you really want:
16:20
<dlbass>
i continued, and it asks for password
16:20
<vagrantc>
hrm.
16:20
<dlbass>
for ltsp20@localhost
16:20
<vagrantc>
dlbass: you restarted ssh?
16:20
ls -l /var/lib/ssh_authorized_keys/ltsp20
16:21
<dlbass>
I did
16:21irule (~irule@189.161.243.178) left irc: Ping timeout: 276 seconds
16:21
<vagrantc>
what version of edubuntu?
16:22
<dlbass>
10.10
16:22
that command shows one directory
16:22
<vagrantc>
one file?
16:22
<dlbass>
possibly
16:22
i wouldnt know the difference lol
16:23
<vagrantc>
could you cut and paste it?
16:23* vagrantc has to go fairly soonish
16:23
<dlbass>
i can type it slowly.
16:23
ah well if you have to go, lets call it quits for today, I was supposed to leave over an hour ago
16:23
but im having fun
16:24
<vagrantc>
oh.
16:24
worst case, delete all the accounts, set them up with username/password the same, and can fix the ssh keys later
16:24
i.e. ltsp20/ltsp20, ltsp21/ltsp21 ... ltsp250
16:24
<dlbass>
-rw-r--r-- 1 root ltsp20 407 2011-04-25 18:01
16:24
<vagrantc>
dlbass: aha
16:25
<dlbass>
it syas more...
16:25
if you need it
16:25
<vagrantc>
dlbass: sudo chmod o-rwx /var/lib/ssh_authorized_keys/*
16:26
they should all be:
16:26
-rw-r-----
16:26
and then try again
16:26
hopefully that's it
16:27
<dlbass>
says no such file or directory.. what? lemm try again
16:27
it doesnt like the asterisk
16:27
will it work if I dont use it
16:28
<vagrantc>
dlbass: sudo chmod -R o-rwx /var/lib/ssh_authorized_keys/
16:28
add the recursive bit, then
16:28
the -R
16:28
<dlbass>
woohoo
16:28
now try booting again?
16:28
<vagrantc>
sure
16:28
<dlbass>
-R has been my friend in times past, used him to get my joomla going on my home server
16:29
stupid server thought it needed to be all secure and stuff, but i used -R to make it all public so my addons would work lol
16:29
no it is still broken with a new error
16:29
<vagrantc>
that doesn't sound good :P
16:30
<dlbass>
it goes away so fast
16:30
plymoth something killed by SEGV signal
16:30
<vagrantc>
odd
16:30
<dlbass>
restart ssh again?
16:31
<vagrantc>
i'm not too familiar with *ubuntu
16:31
<dlbass>
what is your favorite?
16:31ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
16:31
<vagrantc>
dlbass: sudo ssh -i /opt/ltsp/i386/root/.ssh/id_rsa ltsp20@localhost
16:31
try that again
16:32* vagrantc works on debian
16:32ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
16:32ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
16:32
<dlbass>
went straight to asking the password
16:32ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
16:33* vagrantc wonders if ubuntu doesnt' respect AuthorizedKeysFile2
16:33
<dlbass>
should change it to not have teh 2?
16:34
<vagrantc>
it's worth testing ... it'll break expectations about where the ssh keys are
16:34
<dlbass>
oh.
16:34
<vagrantc>
although if this is all you're doing, that should be fine
16:34
<dlbass>
are you going to be willing to test some more tomorrow?
16:34
<vagrantc>
probably won't have much time till friday
16:35
can sometimes get a little in over the week
16:35
i know this method works with ubuntu's lucid (10.04) and debian's squeeze release
16:35
but there might be some gotcha
16:35
<dlbass>
it shoudl still work if it works on 10.04
16:36
ive surely entered something in wrong
16:36
<vagrantc>
it's possible
16:36
computers are pretty fussy with details :)
16:36
<dlbass>
more like porbable
16:36
probable lol
16:37
maybe my boos can help me go over what you have taught me today and we can find what I did wrong, and If not I shall see you friday! Thank you so much for your help!!!!!!!
16:38
<vagrantc>
good luck!
16:38
<dlbass>
cya later guys
16:38
<vagrantc>
dlbass: one more thing
16:38
<dlbass>
im here
16:38
<vagrantc>
dlbass: sudo chmod o+rx /var/lib/ssh_authorized_keys
16:38
the sshd might need read access to the dir or something stupid like that
16:39
it's probably some sort of ssh being fussy about the permissions of the users.
16:39
<dlbass>
rx or rwx
16:39
<vagrantc>
just rx
16:39
<dlbass>
ok
16:39
<vagrantc>
rwx would be dangerous ... allowing anyone to write to anyone else's login keys :)
16:39
<dlbass>
lol oh yes
16:39
im letting my novice show
16:40
<vagrantc>
so it's good that ssh is particular about permissions... but that's probably what's biting you
16:40
<dlbass>
booting a computer
16:40
failed due to unkown user id (process: 304)
16:40
GAH!
16:41
getpwuid_r() is alos in there
16:41
<vagrantc>
there are also other clever folks in here ... though they might not understand exactly what i was trying to set up.
16:41
i ought to document it
16:42
dlbass: you did add the pam_mkhomedir stuff?
16:42
<dlbass>
(process:304): GLib-WARNING **: getpwuid_r(): failed due to an unkown user id (0)
16:42
umm
16:43
i dont think so
16:43
i cant find that line
16:43
<vagrantc>
in /etc/pam.d/common-auth:
16:43
session required pam_mkhomedir.so silent
16:44
<dlbass>
is that supposed to be a blank file?
16:45
<vagrantc>
don't know on ubuntu ... there's a lot of comments on debian
16:46
<dlbass>
i typed in sudo nano /etc/pam.d/common-auth:
16:46
is that right?
16:46
<vagrantc>
no ":"
16:46
<dlbass>
ah thats better!
16:46
sorry
16:46
<vagrantc>
sometimes the english and the code get confusing :)
16:47
<dlbass>
ok did that
16:48staffencasa (~staffenca@128.193.148.154) left irc: Read error: Connection reset by peer
16:49
<dlbass>
OMG IT WORKDED!
16:49
!!
16:49
!
16:49Last message repeated 2 time(s).
16:49
<dlbass>
lol workded
16:49
you are "teh 1337 LTSP man of teh dai"
16:50
booting up two more to see what happens!
16:50
now I will go get hit by a car since I missed two stinking lines and caused you all that!
16:51
37 and 36 work
16:52
they can both open web browsers!
16:52
34 is broken, but surely that is my fault also, and in the production server it willwork!
16:55
I've got to go, but again, and again, and again, thank you so much for your help! Hopefully this is going to give the breath of life to a lab of 12 year old Dell GX110s for an elementary school! Only if this worked over wireless!
16:55
<vagrantc>
yay!
16:56
<dlbass>
cya later!
16:56
<vagrantc>
there are tricks with wireless, but there's just not enough bandwidth, really
16:56dlbass (cc1d4484@gateway/web/freenode/ip.204.29.68.132) left irc: Quit: Page closed
16:57vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) left irc: Quit: leaving
17:00
17:16ry (~ry@static-71-183-64-28.nycmny.fios.verizon.net) joined #ltsp.
18:58artista_frustrad (~artista_f@189.75.201.155) joined #ltsp.
19:27Lumiere (~jstraw@72.83.232.11) left irc: Remote host closed the connection
19:45MorningSon (~MorningSo@66.25.84.220) left irc: Quit: WeeChat 0.3.0
21:12patrickmw (~pwright@71-223-80-153.phnx.qwest.net) left irc: Quit: Ex-Chat
21:26Roasted (~jason@unaffiliated/roasted) left irc: Ping timeout: 240 seconds
21:27Roasted (~jason@unaffiliated/roasted) joined #ltsp.
21:33cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
21:33cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
22:31alexqwesa (~alex@109.172.15.11) left irc: Remote host closed the connection
22:31alexqwesa (~alex@alexo-veto.broker.freenet6.net) joined #ltsp.
23:05alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
23:05viks_ (ca8a720f@gateway/web/freenode/ip.202.138.114.15) joined #ltsp.
23:06
<viks_>
tftp access violation error is getting ...how to resolve it
23:07
<muppis>
https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP#Verify%20that%20the%20tftp%20files%20are%20there
23:08
Specially pointing to permissions.
23:16
<viks_>
tftp 10.160.31.10 -v -m binary -c get /ltsp/i386/pxelinux.0 when i ran this command ...it is still giving access violation error
23:32viks_ (ca8a720f@gateway/web/freenode/ip.202.138.114.15) left irc: Ping timeout: 252 seconds
23:51wwx (~ww@raamat.polva.ee) left irc: Ping timeout: 258 seconds
23:53chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) left irc: Quit: WeeChat 0.3.3
23:58wwx (~ww@raamat.polva.ee) joined #ltsp.
00:00--- Tue Apr 26 2011