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


Channel log from 28 May 2014   (all times are UTC)

00:06gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 245 seconds)
00:27monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.42.128, Ping timeout: 258 seconds)
00:28vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
00:37monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.42.128)
01:03gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
01:08gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 240 seconds)
01:13monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.42.128, Ping timeout: 252 seconds)
01:20PhoenixSTF has left IRC (PhoenixSTF!~rudiservo@78.29.147.214, Quit: Leaving)
02:04gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
02:07monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.42.128)
02:09gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 252 seconds)
02:48vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
03:05gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
03:09gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 245 seconds)
03:52monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.42.128, Ping timeout: 255 seconds)
04:06gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
04:11gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 264 seconds)
04:18monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.42.128)
04:27telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
04:28telex has joined IRC (telex!~telex@freeshell.de)
04:43work_alkisg has left IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr, Ping timeout: 255 seconds)
04:47work_alkisg has joined IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr)
05:07gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
05:11gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 265 seconds)
05:19mikkel has joined IRC (mikkel!~mikkel@93.176.85.50)
05:37vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi)
06:07gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
06:12gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 252 seconds)
06:14Ark74 has joined IRC (Ark74!~Ark74@189.214.42.128.cable.dyn.cableonline.com.mx)
06:27mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
06:28work_alkisg has left IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr, Quit: Leaving.)
06:46alexxtasi has joined IRC (alexxtasi!~alex@unaffiliated/alexxtasi)
07:00piet has joined IRC (piet!~piet@host-091-097-161-189.ewe-ip-backbone.de)
07:08mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 240 seconds)
07:08gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
07:09work_alkisg has joined IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr)
07:13gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 252 seconds)
07:32vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
07:36mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
08:04bennabiy has left IRC (bennabiy!~Thunderbi@96-37-209-0.dhcp.leds.al.charter.com, Ping timeout: 245 seconds)
08:05bennabiy has joined IRC (bennabiy!~Thunderbi@96-37-209-0.dhcp.leds.al.charter.com)
08:09gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
08:12khildin has joined IRC (khildin!~khildin@ip-213-49-86-58.dsl.scarlet.be)
08:14gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Ping timeout: 265 seconds)
08:23bobby__C has joined IRC (bobby__C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
08:24vmlintu has left IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 276 seconds)
08:27monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.42.128, Ping timeout: 255 seconds)
08:27AndChat|496496 has joined IRC (AndChat|496496!~AndChat49@24.114.27.253)
08:41AndChat|496496 is now known as monkwitdafunk
08:59vmlintu has joined IRC (vmlintu!~vmlintu@cs181214103.pp.htv.fi)
09:10gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
09:11gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
09:26bobby__C has left IRC (bobby__C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 252 seconds)
09:37monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.27.253, Read error: Connection reset by peer)
09:43flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
11:14flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Quit: Quitte)
12:19Faith has joined IRC (Faith!~paty@143.107.231.49)
12:24yanu has joined IRC (yanu!~yanu@178-117-230-250.access.telenet.be)
12:24yanu has joined IRC (yanu!~yanu@lugwv/member/yanu)
12:51Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
13:44PhoenixSTF has joined IRC (PhoenixSTF!~rudiservo@78.29.147.214)
13:46mikkel has left IRC (mikkel!~mikkel@93.176.85.50, Quit: Leaving)
14:02alexxtasi has left IRC (alexxtasi!~alex@unaffiliated/alexxtasi)
14:12Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
14:13adrianorg has left IRC (adrianorg!~adrianorg@177.204.151.180.dynamic.adsl.gvt.net.br, Ping timeout: 240 seconds)
14:14khildin has left IRC (khildin!~khildin@ip-213-49-86-58.dsl.scarlet.be, Quit: I'm gone, bye bye)
14:14adrianorg has joined IRC (adrianorg!~adrianorg@177.204.151.180.dynamic.adsl.gvt.net.br)
14:19mattcen has left IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au, Ping timeout: 240 seconds)
14:20mattcen has joined IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au)
14:26freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
14:36adrianorg has left IRC (adrianorg!~adrianorg@177.204.151.180.dynamic.adsl.gvt.net.br, Ping timeout: 240 seconds)
14:37adrianorg has joined IRC (adrianorg!~adrianorg@187.113.219.38)
14:37mattcen has left IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au, Ping timeout: 252 seconds)
14:48adrianorg has left IRC (adrianorg!~adrianorg@187.113.219.38, Ping timeout: 276 seconds)
14:49adrianorg has joined IRC (adrianorg!~adrianorg@179.180.175.65)
14:50dead_inside has joined IRC (dead_inside!~taylor@76.75.3.174)
14:55mattcen has joined IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au)
15:01vmlintu has left IRC (vmlintu!~vmlintu@cs181214103.pp.htv.fi, Ping timeout: 276 seconds)
15:36adrianorg has left IRC (adrianorg!~adrianorg@179.180.175.65, Ping timeout: 255 seconds)
15:38adrianorg has joined IRC (adrianorg!~adrianorg@179.187.27.8.dynamic.adsl.gvt.net.br)
15:41
<bennabiy>
alkisg: https://bugs.launchpad.net/bugs/1324145 should be easy to fix? I experienced the same thing recently.
15:45championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net, Quit: Leaving.)
15:46bucko has joined IRC (bucko!550a2640@gateway/web/freenode/ip.85.10.38.64)
15:47championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
15:49
<bucko>
did someone encounter such problem?
15:49
http://s29.postimg.org/xviqo3apz/error.png
15:49
server is gentoo in xen
15:59championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net, Quit: Leaving.)
16:16mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Ping timeout: 240 seconds)
16:21adrianorg has left IRC (adrianorg!~adrianorg@179.187.27.8.dynamic.adsl.gvt.net.br, Ping timeout: 240 seconds)
16:23adrianorg has joined IRC (adrianorg!~adrianorg@177.156.57.145)
16:28championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
16:32vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi)
17:17yanu has left IRC (yanu!~yanu@lugwv/member/yanu, Read error: Connection reset by peer)
17:28DanishMan has joined IRC (DanishMan!~kvirc@62-243-156-218-static.dk.customer.tdc.net)
17:53freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish.)
17:55mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
18:04vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
18:15yanu has joined IRC (yanu!~yanu@178-117-230-250.access.telenet.be)
18:15yanu has joined IRC (yanu!~yanu@lugwv/member/yanu)
18:20championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
18:23championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
18:29adrianorg has left IRC (adrianorg!~adrianorg@177.156.57.145, Ping timeout: 252 seconds)
18:30adrianorg has joined IRC (adrianorg!~adrianorg@177.156.57.145)
18:43dead_inside has left IRC (dead_inside!~taylor@76.75.3.174, Ping timeout: 252 seconds)
18:51dead_inside has joined IRC (dead_inside!~taylor@76.75.3.174)
19:01mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 240 seconds)
19:22mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.21.12)
19:24||cw has left IRC (||cw!~chris@phpgroupware/cw, Ping timeout: 264 seconds)
19:27||cw has joined IRC (||cw!~chris@phpgroupware/cw)
19:32vmlintu has left IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 264 seconds)
19:38championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
19:53mattcen has left IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au, Ping timeout: 252 seconds)
19:58PhoenixSTF has left IRC (PhoenixSTF!~rudiservo@78.29.147.214, Quit: Leaving)
19:58mattcen has joined IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au)
20:46Faith has left IRC (Faith!~paty@143.107.231.49, Quit: Byee!)
20:59championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
21:06
<championofcyrodi>
anyone know how to modify lts.conf to use the hostname derived from DHCP server for clients?
21:07
I believe I need to pass it as a kernel parameter in the pxelinux.cfg?
21:07
<vagrantc>
it should do that by default...
21:07
unless you've changed something
21:08
<championofcyrodi>
my LTSP server is not the DHCP server.
21:09
<vagrantc>
it doesn't care what your server is, the code just makes up a hostname "ltspXXX" based on the ip address assigned.
21:09
<gbaman>
vagrantc: for ltsp-build-client I am using a proxy (apt-cache-ng), for the http-proxy parameter is it just the address:port or the full "Acquire::http { proxy "http://10.0.5.190:3142"; };"
21:09
<vagrantc>
or it uses one assigned by the dhcp server
21:10
gbaman: --http-proxy http://10.0.5.190:3142
21:10
<championofcyrodi>
well the IP on the thick client im using now is : 192.168.2.43, while it's host name is ltsp550
21:10
<gbaman>
vagrantc: or seeing as I am using the config file, HTTP-PROXY=10.0.5.190:3142
21:10
awesome, thanks
21:10
<vagrantc>
cyberorg: what's your netmask?
21:10
<championofcyrodi>
I'm thinking perhaps the hostname was not specified in the dhcp entry
21:10
<gbaman>
after 20+ raspbian builds, think it is about time i set up apt-cache-ng :)
21:11
<vagrantc>
gbaman: export HTTP_PROXY= ...
21:11
gbaman: yes. probably well past due.
21:11
<championofcyrodi>
the entry is only in the DNS sever
21:11
<vagrantc>
cyberorg: what entry is in the DNS server?
21:11
<championofcyrodi>
for the IP 192.168.2.43
21:11
<vagrantc>
championofcyrodi: er ^^
21:12
<championofcyrodi>
the DHCP entry which assigns an IP to the client
21:12
<vagrantc>
championofcyrodi: if the DNS server has an entry, it should use that.
21:12
<championofcyrodi>
it doesnt seem to be
21:13
<vagrantc>
championofcyrodi: so, let's clarify ...
21:13
championofcyrodi: it has a DNS entry, and you would like it to use that?
21:13
<championofcyrodi>
yes
21:13
<vagrantc>
championofcyrodi: what distro?
21:13
<championofcyrodi>
ubuntu 14.04
21:14
The IP my thick client has is 192.168.2.38. nslookup of 192.168.2.38 resolves the host name 'nuc3.<domain>'
21:15
However, the host name that the thick client has is 'ltsp550'
21:15
<vagrantc>
right
21:16
<championofcyrodi>
reading: http://manpages.ubuntu.com/manpages/natty/man5/lts.conf.5.html implies my HOSTNAME is auto-generated if no hostname is set.
21:16
<vagrantc>
right
21:17
championofcyrodi: i think you need to get your DHCP server to pass the DNS entries
21:17
<championofcyrodi>
But I'm not sure how to set the HOSTNAME in a dynamic fashion, so that all thick clients on the network resolve their own hostname
21:17
that sounds reasonable
21:18
option host-name "nuc3.<domain>";
21:18
something like that should work, no?
21:18
<vagrantc>
you *might* be able to drop a snippet into ltsp_config.d that does a reverse-lookup of the ip address and sets HOSTNAME appropriately.
21:18
championofcyrodi: probably.
21:19
championofcyrodi: do you have a DNS entry for every machine?
21:19
<championofcyrodi>
yes
21:19
<vagrantc>
championofcyrodi: er, DHCP entry
21:19
<championofcyrodi>
yes
21:19
(to both)
21:19
<vagrantc>
ok, that makes it simple, then.
21:19
you just have to maintain it both in DNS and in DHCP
21:20
you might be able to auto-generate rules for them, if they fall into certain ranges...
21:20
both in DNS and in DHCP...
21:20
but for starters, see if it works setting it manually for that one
21:22
<championofcyrodi>
my understanding was that the DHCP server only points out the TFTP server with the kernel image for PXEBOOT. And after that, it's up to the nbd served image to resolve it's own host name during the boot process. Does that sound accurate to you?
21:22
<vagrantc>
no
21:23
it doesn't, by default, resolve it's hostname... it needs to get that information from somewhere
21:23
either through DHCP, or through lts.conf
21:23
you could add a hook that does that, if you wanted.
21:24
might be worth integrating upstream, actually...
21:24
heh. hostname configuration comes after resolv.conf configuration ... that'll be tricky.
21:24
<bucko>
hey :) can anybody help me with this problem: http://s29.postimg.org/xviqo3apz/error.png ... i have no clue what i'm doing wrong... server is gentoo under xen and client gets its kernel..
21:25
<championofcyrodi>
so the reason I'm trying to do this, is because I have an issue with 1 client, in that it takes a very long time for the ssh session to authenticate and then times out. SO i thought it was reverse dns lookup maybe
21:26
<bucko>
you could shut down in ssh?
21:26
<vagrantc>
though technically i don't think it needs to be that way...
21:26
championofcyrodi: yeah, that's probably reverse DNS lookups
21:26
championofcyrodi: sshing to or from the client?
21:26
<championofcyrodi>
from
21:27
<bucko>
then maybe your primari DNS is wrong and it's waiting for ttl to die and then resolves prom secundary?
21:27
<vagrantc>
championofcyrodi: although that sounds like the server is having issues with it's DNS servers, not what the client thinks it's hostname is.
21:28
<gbaman>
vagrantc: HTTP-PROXY=10.0.5.190:3142 inside the config file failed
21:28
<vagrantc>
gbaman: that's because you broke it.
21:28
<gbaman>
but --http-proxy http://10.0.5.190:3142 on the end of the command didnt
21:28
<vagrantc>
gbaman: "export HTTP_PROXY=10.0.5.190:3142"
21:29
<gbaman>
why is it down as an option in the man page?
21:29
is same format as all the other options
21:29
<vagrantc>
gbaman: note the difference between HTTP-PROXY and HTTP_PROXY ...
21:29
gbaman: one is valid shell variable name, the other is not.
21:30
<gbaman>
but why does HTTP-PROXY=10.0.5.190:3142 inside the config file not work and --http-proxy http://10.0.5.190:3142 works?
21:31
<vagrantc>
gbaman: please re-read the last two things i said.
21:32
<gbaman>
why use 2 different ones though when none of the other commands do?
21:32
<vagrantc>
huh?
21:32
<gbaman>
And using "export HTTP_PROXY=10.0.5.190:3142" would also export it for the main server
21:33
<vagrantc>
you cannot have a - in the variable name.
21:33
<gbaman>
which I dont want
21:33
as they both have the same package names
21:33
ubuntu and debian
21:33
<vagrantc>
ah, it's lower-case.
21:33
<gbaman>
so http-proxy=10.0.5.190:3142 in the config file would work?
21:33
<vagrantc>
that used to be a big problem with apt-cacher-ng ... you couldn't have identical packages from different distros...
21:34
gbaman: no, because "-" is not valid in a shell variable name
21:34
<gbaman>
Thats why I am not using it for the host OS, only the chroot being generated
21:34
so if I exported it, it would be exported for both
21:34
<vagrantc>
gbaman: you can put it in the ltsp-build-client.conf
21:35
gbaman: it needs to be exported, because it's not ltsp-build-client calling it.
21:35
it's a subcommand of ltsp-build-client that needs the variable set.
21:35
well, a variety of subcommands...
21:36
<gbaman>
ok, think I get it now
21:36
<vagrantc>
gbaman: so "export http_proxy=10.0.5.190:3142" in the ltsp-build-client.conf
21:36
<gbaman>
just noticing the other commands in the config file use _ instead of -
21:36
<vagrantc>
it's lower-case because that's the variable that apt, wget, etc. are looking for.
21:37
<gbaman>
I didn't know they were being taken has environmental variables from the config file
21:37
thought they were being parsed as options
21:37
<vagrantc>
gbaman: just type this on a commandline: test-variable=foo
21:37
gbaman: and then: test_variable=foo
21:38
<gbaman>
yeah, get it now
21:38
thought they were always meant to be caps?
21:38
<vagrantc>
caps and lower-case in shell variables is pretty arbitrary.
21:38
<gbaman>
:)
21:39
<vagrantc>
typically, globally exported variables are all caps, but that's by no means technically required.
21:39
<gbaman>
would assume then apt would like it caps?
21:39
<vagrantc>
or encforced... or consistant.
21:39
gbaman: for whatever reason, http_proxy is always lower-case, as far as i can tell.
21:40
<gbaman>
ok
21:40
am properly starting to flesh out Raspi-LTSP now
21:41
Added auto backups the other day
21:41
and user management inside it
21:41
Removed a lot of the options on setup
21:41
<vagrantc>
i guess the ltsp-build-client http-proxy plugin could export http_proxy if set, to simplify use in the configuration file...
21:42
as i dont think it will work if you just set it and don't export it...
21:42
<gbaman>
..
21:42
it is working
21:42mattcen has left IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au, Ping timeout: 276 seconds)
21:43
<gbaman>
stuff is getting downloaded in the log file
21:44* vagrantc wonders if apt-cacher-ng still has that bug of not supporting multiple distros
21:44
<vagrantc>
i really like that you can specify it as a proxy
21:45
i remember saying i would test out a bug a while back, but didn't ask for a bug report, and now i forgot...
21:45
was it bennabiy or gbaman who brought it up?
21:46
<gbaman>
dont think it was me?
21:46
<vagrantc>
i guess there were the bugs with --locale
21:46
<gbaman>
haha
21:46
i seem to break everything :)
21:47
anyways, going to leave that to hum away
21:47
thanks for help
21:47gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
21:49
<bucko>
@vagrantc ... could you look at my problem now? ;)
22:01mattcen has joined IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au)
22:01gbaman has joined IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com)
22:18DanishMan has left IRC (DanishMan!~kvirc@62-243-156-218-static.dk.customer.tdc.net, Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/)
22:22
<vagrantc>
bucko: i don't really know gentoo at all
22:23
bucko: and it's failing in a pretty gentoo-specific spot
22:25
<bucko>
yeah -.- there are good things about gentoo and there are this things :D i'm writing to ltsp-discuss list so hopefully somebody could help me there :)
22:29
<vagrantc>
my guess is perhaps some trouble connecting to the NBD server? or possibly with DHCP server settings
22:30telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
22:32telex has joined IRC (telex!~telex@freeshell.de)
22:36
<bucko>
i use nfs and it seems like it's getting kernel and initramfs files when PXE starts so dhcp should be ok
22:36
i uploaded a video of booting ... http://tinypic.com/r/30m74bc/8 ...
22:36
<vagrantc>
bucko: yes, but it may need to make a second DHCP request from the initramfs that might not be getting the correct NBD server information
22:36
or NFS
22:37
it seems like it's broken in the initramfs -> real root filesystem transition
22:37
at least from your first URL
22:43
<bucko>
will do some digging
22:57
<bennabiy>
vagrantc: 05:09:29 PM - gbaman: vagrantc: for ltsp-build-client I am using a proxy (apt-cache-ng), for the http-proxy parameter is it just the address:port or the full "Acquire::http { proxy "http://10.0.5.190:3142"; };"
22:57
is that the thing you were referring to?
22:57
It was not me :)
22:59
<vagrantc>
no
22:59
i think it was the --locale stuff
22:59
<bennabiy>
ah,
23:00
If I asked you to test something, I do not remember it... although I do have a vague memory of needing something from you.
23:00
Oh well, if I remember, I will ask
23:02mealstrom has left IRC (mealstrom!~Thunderbi@46.63.21.12, Ping timeout: 240 seconds)
23:03* vagrantc nods
23:58gbaman has left IRC (gbaman!~gbaman@host81-130-112-2.in-addr.btopenworld.com, Remote host closed the connection)