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


Channel log from 26 June 2016   (all times are UTC)

00:06epoptes_user1 has joined IRC (epoptes_user1!ba4e5e2a@gateway/web/freenode/ip.186.78.94.42)
01:32cor_geeks_eadthe has left IRC (cor_geeks_eadthe!~cor@cpe-76-92-215-174.kc.res.rr.com, Quit: Leaving)
04:01sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0412w-ds01-45-12-121.dynamic.mtsallstream.net)
04:33zamba has left IRC (zamba!marius@flage.org, Ping timeout: 244 seconds)
05:48vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
06:05ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:35robb_nl has joined IRC (robb_nl!~robb_nl@ip-80-236-223-127.dsl.scarlet.be)
07:57vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 250 seconds)
09:06robb_nl has left IRC (robb_nl!~robb_nl@ip-80-236-223-127.dsl.scarlet.be, Remote host closed the connection)
13:21vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
13:53robb_nl has joined IRC (robb_nl!~robb_nl@ip-80-236-223-127.dsl.scarlet.be)
14:10tharkun_ has left IRC (tharkun_!~0@201.157.71.45, Ping timeout: 272 seconds)
14:11tharkun has joined IRC (tharkun!~0@201.157.71.45)
14:15vagrantc_ has joined IRC (vagrantc_!~vagrant@unaffiliated/vagrantc)
14:16robb_nl has left IRC (robb_nl!~robb_nl@ip-80-236-223-127.dsl.scarlet.be, Quit: I'm gone, bye bye)
14:32Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
15:19vagrantc_ has left IRC (vagrantc_!~vagrant@unaffiliated/vagrantc, Quit: leaving)
15:29vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 276 seconds)
15:36vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:11Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
16:33vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
17:11vmlintu has joined IRC (vmlintu!~vmlintu@dsl-jnsbrasgw2-58c07e-86.dhcp.inet.fi)
19:25vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
19:55vmlintu has left IRC (vmlintu!~vmlintu@dsl-jnsbrasgw2-58c07e-86.dhcp.inet.fi, Ping timeout: 260 seconds)
20:06vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
20:22lifeboy has joined IRC (lifeboy!~roland@196.32.234.206)
20:27ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:02book` has left IRC (book`!~book`@68.ip-149-56-14.net, Ping timeout: 244 seconds)
21:04book` has joined IRC (book`!~book`@68.ip-149-56-14.net)
21:32james1 has joined IRC (james1!~james@97.85.17.165)
21:33
<james1>
Hey everyone. I've just installed LTSP and am attempting to boot a fat client laptop. PXE works but times out. The server and the client can communicate with each other using ping. What might be causing this?
21:53
<Hyperbyte>
james1, PXE is two steps.
21:53
1. dhcp. 2. tftp.
21:54
If PXE times out, it's either dhcp or tftp problem.
21:55linuxfool has joined IRC (linuxfool!~james@71-45-66-171.res.bhn.net)
21:55
<linuxfool>
Hello all
22:01
If an LTSP setup is going to be strictly on a local area network without any need or desire for access to the Internet, are there certain steps or precesses that can be left out to simplify the setup?
22:04
<Hyperbyte>
linuxfool, depends on what howto you're following.
22:05
Practically, no, everything that is needed to configure LTSP is needed wether you want to have the clients on the internet or not.
22:06
<linuxfool>
Hyperbyte: yeah, I've noticed that. There seem to be a bunch of them. I followed the one that's in the ubuntu community help forum.
22:07
One guide says something about not using the standalone package bcause of something about dhcp and the other says to use the standalone version.
22:08
Is there a command to actually be running the server? Or should having the package downloaded and a client image created mean anything that logs onto the LAN with PXE should boot up the client image?
22:20
<Hyperbyte>
linuxfool, LTSP consists of basically these parts:
22:21
1. dhcp server, that points network boot to the correct tftp image. this can be any dhcp server, but since it's a local network without router I presume, this would be installed on the ltsp server
22:21
2. tftp server that contains basic linux kernel and boot routines
22:21
3. nbd server that provides the full harddisk image for the client (this is mounted from the tftp boot image)
22:22
4. ssh server that enables thin clients to log in
22:23
Basically if you install ltsp-server package, run ltsp-build-client and make sure all the services are started, ltsp should work.
22:23
(this is for Ubuntu)