stgraber: cisco routers do not work with clientid='', i.e. they don't send a dhcp offer so the clients won't boot

04:11

Are you sure that's the only way to prevent dhcp3-server from needing 2 IPs per client?

04:41

highvoltage has joined #ltsp

05:03

highvoltage has quit IRC

05:05

highvoltage has joined #ltsp

05:14

<alkisg>

stgraber: I tested here locally with dhcp3-server and *without* sending a clientid (i.e. the default udhcpc behavior) and my client used the same IP address that it had in PXE...

05:15

So I think we should ditch the clientid hack altogether...

05:17

johnny has joined #ltsp

05:21

klausade has joined #ltsp

05:28

cyberorg has joined #ltsp

05:36

gnunux has quit IRC

05:37

<alkisg>

Uhm, and maybe we can send a patch for udhcpc so that it doesn't send a clientid at all (not send an empty one)

06:03

hersonls has joined #ltsp

06:24

Selveste1_ has quit IRC

06:28

pmatulis has joined #ltsp

06:34

Barbosa has joined #ltsp

06:35

ogra_cmpc has quit IRC

06:42

scottmaccal has joined #ltsp

07:07

gnunux has joined #ltsp

07:18

Selveste1_ has joined #ltsp

07:29

Selveste1_ has quit IRC

07:30

Selveste1_ has joined #ltsp

07:34

scottmaccal has quit IRC

07:34

Selveste1__ has joined #ltsp

07:35

Selveste1_ has quit IRC

07:35

ogra has quit IRC

07:36

Faithful has quit IRC

07:36

ogra has joined #ltsp

07:37

alkisg has quit IRC

07:47

Barbosa has quit IRC

08:08

alkisg has joined #ltsp

08:16

Selveste1__ has quit IRC

08:16

Selveste1__ has joined #ltsp

08:21

Gadi has joined #ltsp

08:22

komunista has joined #ltsp

08:23

Selveste1__ has quit IRC

08:23

<komunista>

hi

08:30

vbundi has quit IRC

08:36

komunista has quit IRC

08:38

Selveste1__ has joined #ltsp

08:39

ogra_cmpc has joined #ltsp

08:45

Nikratio has joined #ltsp

08:45

komunista has joined #ltsp

08:48

<Nikratio>

On my Ubuntu karmic ltsp clients, the /etc/hosts file is always garbled. After the server ip, I have about 30 "-f\n" entries, before the final "-f server" line. If I restart /etc/init.d/ltsp-client-setup, the file is generated correctly. Anyone has an idea where to look for the problem?

08:51

yodan has joined #ltsp

08:52

<alkisg>

Nikratio: can you try to specify SERVER=ip in lts.conf?

08:52

I think that bug was solved some months ago, but I don't remember the exact details

08:52

<Nikratio>

Which BTS was it in?

08:53

<alkisg>

BTS==??

08:53

<Nikratio>

Bug Tracking System

08:53

So I can look it up

08:53

<alkisg>

I'm not sure if it was in any BTS, but if it was, it was in launchpad

08:54

Selveste1__ has quit IRC

08:54

<alkisg>

We may have fixed it without filing any bug reports, though

08:54

<Nikratio>

ah, ok. I'll try the lts.conf change then

08:56

vmlintu has joined #ltsp

09:00

<Nikratio>

yes, that fixed it

09:00

Thanks!

09:01

<alkisg>

OK, don't bother with it anymore, it was fixed for Lucid (even though I don't remember the commit #)

09:03

<Nikratio>

great, thanks again

09:05

Nikratio has left #ltsp

09:06

pmatulis has quit IRC

09:10

pmatulis has joined #ltsp

09:22

Faithful has joined #ltsp

09:24

alkisg has quit IRC

09:25

vmlintu has quit IRC

09:26

alkisg has joined #ltsp

09:30

vmlintu has joined #ltsp

09:35

pmatulis has quit IRC

09:36

mikkel has quit IRC

09:37

pmatulis has joined #ltsp

09:37

mischko has joined #ltsp

09:38

bobby_C has joined #ltsp

10:18

lipinski has joined #ltsp

10:19

<lipinski>

How can I troubleshoot a hanging client? It starts up fine, and I can log in, start applications, but eventually it hangs and the screen is semi-frozen. Mouse still moves, but can't click on anything or do anything.

10:19

Looking for some insight on how to start troubleshooting....

10:21

<vmlintu>

Does it answer to ping?

10:24

<lipinski>

yes

10:24

yodan has quit IRC

10:24

<lipinski>

I'm trying a new test where I start up firefox and just let it sit at the home page. I'm thinking maybe Facebook or some page like that is causing a problem.

10:25

I just don't know how to start troubleshooting it. Where would logs be? Do I have to add sshd to the client to be able to get in and check things out? , etc..?

10:26

thunsucker has joined #ltsp

10:29

<vmlintu>

Having sshd on the client helps a lot

10:30

To get logs, you have to enable remote logging on the server. Which distro are you running?

10:33

pmatulis has quit IRC

10:33

pmatulis has joined #ltsp

10:36

vagrantc has joined #ltsp

10:44

Selveste1__ has joined #ltsp

10:45

gnunux has quit IRC

10:46

pmatulis has quit IRC

10:46

pmatulis has joined #ltsp

11:09

<lipinski>

vmlintu: Sorry, got pulled away... I'm currently running Ubuntu 9.10. I'm going to be upgrading to 10.04 LTS in the next week or so (maybe Beta 2, maybe wait for official release)..

11:09

So, I really am trying to "band-aid" this hang problem to late me until I can get the server on 10.04

11:12

<vmlintu>

Try first installing sshd in the chroot

11:13

Once you can login to the client, try running at least top or some similar tool to see if there's something unusual when it freezes

11:14

<Gadi>

lipinski: how much memory does the client have?

11:15

<vmlintu>

I haven't run 9.10 in production so I cannot say much about its quirks

11:17

<thunsucker>

lipinski: is it all your clients or just a few? if it's more than 1 how much memory does the server have and how many clients you running

11:17

i have an issue right now at one of my installs, the server doesn't have enough memory (i'm guessing) because sound is choppy on when using the rdesktop script

11:17

i connect from a ubuntu laptop to the same terminal servers and all is well

11:18

but if less than 5 clients are on, there are no sound issues

11:19

<Gadi>

thunsucker: rdesktop from a launcher on the linux desktop or as a screen script?

11:22

epaphus has joined #ltsp

11:22

<epaphus>

hello all

11:28

<komunista>

lipinski: I have one clinet with the same problem

11:29

and it seems to graphic card related

11:29

when I kill frozen GUI apps, the client works...

11:30

it has problem for example with wbar, lxsession-logout and sometime with other apps too

11:31

no messages in any log, no problem by ssh to client... only apps do not works...

11:37

staffencasa has joined #ltsp

11:40

emence has quit IRC

11:50

<lipinski>

The client was working fine for a long time. I had server problems, so upgraded. Server is now running an Intel i3 with a new MB and 4GB RAM. I have only 1 client.

11:51

The primary use of the client if for Firefox. If I kill Firefox process on the server, the client "unfreezes".

11:51

<alkisg>

How much ram does the client have?

11:51

<lipinski>

I think only 256MB.

11:51

<alkisg>

and, is firefox running as a localapp?

11:52

<lipinski>

no

11:52

<alkisg>

Any other localapps? 256 should be plenty for only thin client use...

11:52

<lipinski>

no localapps at all. This is a "straightforward" ltsp install.

11:52

client is a dumb as can be :)

11:52

<alkisg>

Hmmm and if you kill firefox and it unfreezes, then it shouldn't be ram related

11:53

<lipinski>

alkisg: I rebuild the image and that's how I fixed the eth problem I was having the other evening (when you were helping me)..

11:53

Now, client runs great - except for this annoying hang.

11:53

mikeshultz has joined #ltsp

11:53

<lipinski>

Let me try a different app, i.e., OpenOffice or something and see if that hangs.

11:54

sahil has joined #ltsp

11:54

<sahil>

After adding local firefox on ubuntu 9.10 and doing the thin-client nat setup, my clients will boot and display the login manager but I am unable to login, what gives?

11:55

<lipinski>

It's almost like it's causing the entire desktop on the client to hang. mouse still responds, but I can't click on anything.

11:56

<alkisg>

sahil: try `sudo ltsp-update-sshkeys && sudo ltsp-update-image`

11:56

<sahil>

thanks alksig

11:56

Faithful has quit IRC

12:00

<lipinski>

I never looking into LTSP processes before:

12:00

7028 7027 0 08:16 pts/0 00:00:00 bash -c echo LTSPROCKS; /bin/sh -

12:00

Nice :)

12:02

sahil has quit IRC

12:13

Selveste1___ has joined #ltsp

12:14

Selveste1__ has quit IRC

12:18

GodFather has joined #ltsp

12:20

<komunista>

lipinski: I have 15 the same clients and only one go to this problem

12:21

<lipinski>

komunista: odd. I'm trying a different Application besides firefox now. Next step would be to use sshd and see if I can tell what's going on on the client itself - maybe a stray process or something...

12:22

<johnny>

alkisg, ever heard of anything like this in karmic? try to play a sound and the volume just starts lowering itself until it is completely quiet?

12:22

it happens with flash player, exaile, and mplayer

12:22

or anywhere even..

12:22

not just karmic :)

12:22

<alkisg>

nah, never

12:23

does pulseaudio auto lower the volume on overdrive?

12:23

<johnny>

i have no idea

12:23

i have yet to see an overdrive setting :)

12:24

<alkisg>

Karmic allows you to overdrive your speakers... send more than 100% to them

12:24

(in gnome-mixer how's that applet called)\

12:26

<johnny>

gnome-mixer ? or gnome-alsamixer ?

12:26

<komunista>

lipinski: I find no solution :-(

12:27

I have dropbear in client's chroot, but when it freeze, I see nothing wrong on it...

12:27

<alkisg>

johnny: gnome-volume-control

12:27

ogra_cmpc has quit IRC

12:28

<johnny>

guess that doesn't work over ssh -X :)

12:28

lol

12:30

hmm.. i'm still getting freezes on my fat client setup

12:30

ogra_cmpc has joined #ltsp

12:30

<johnny>

even after nbd swap seems to be on

12:30

it shows swap on the terminal

12:30

but it doesn't seem to get used

12:31

<alkisg>

swapping is broken in karmic

12:31

It was fixed 1-2 months ago

12:31

<johnny>

broken in what way

12:31

i think i had fixed it

12:31

by upgrading to stgraber-ppa

12:32

some swap shows up when i run top on the fat client terminal

12:32

<alkisg>

Is that compcache?

12:32

slidesinger has quit IRC

12:33

<alkisg>

But if you upgraded AND updated the initramfs, yeah, it should be fixed

alkisg, i don't think the solution would be acceptable upstream is all

14:26

by gnome folks

14:26

it's too specific to one situation

14:27

<atkuepker>

grr. more dbus-daemon. I'd be happier if that thing didn't lock up so frequently

14:27

<alkisg>

johnny: so then what do you propose? To maintain an ltsp-specific branch of dbus?

14:28

GodFather has quit IRC

14:28

<johnny>

alkisg,

14:28

no..

14:29

it just seems more likely that a dbus proxy or router would be more generic and useful for ohter things

14:29

unlike the specific hacky way of logging out

14:30

<asmok>

stgraber: you are hero of the day ;-)

14:30

<stgraber>

asmok: it works correctly ?

14:30

<asmok>

atching file Admin/index.php

14:30

patching file Admin/util/functions.php

14:30

patching file Admin/util/setup.php

14:30

patch unexpectedly ends in middle of line

14:30

Hunk #2 succeeded at 198 with fuzz 2.

14:30

yes

14:30

<stgraber>

good, releasing a new version + uploading to lucid then

14:31

released (2.0.2)

14:31

<asmok>

great!

14:34

staffencasa has joined #ltsp

14:35

<asmok>

there are still messages in apache2's error.log, but admin page works now, this kind of

14:36

<alkisg>

vagrantc: one cleaner thing to propose is to have the applet reboot/shutdown entries hidden when the CK session is not active (e.g. in ltsp and nx sessions). That wouldn't be hackish at all. We'd lose the ability to shutdown from the menus, but it'd at least make sense.

14:37

<vagrantc>

alkisg: i thought that was already implemented in older versions?

14:37

<alkisg>

vagrantc: yes there was a patch in fusa for that, but fusa got dropped and the patch wasn't transfered to the new indicator applet

14:37

<asmok>

http://ltsp.pastebin.com/ixzkUTkj

14:38

<alkisg>

vagrantc: but this wouldn't be an ltsp - specific patch; it would check CK instead

14:38

<stgraber>

asmok: uploaded to lucid

14:38

asmok: seems like php 5.3 is quite verbose ;)

14:38

I won't spend too much time making it happy as we are simply rewritting everything at the moment ...

14:39

<asmok>

good to know

14:39

i finish now my lucid setup and them boot first test tc

14:41

GodFather has joined #ltsp

14:52

<asmok>

stgraber: HP Mini 2133 as a TC: http://ltsp.pastebin.com/WE1v7rHi

14:53

<stgraber>

great !

14:53

<asmok>

lucid works great now, only one app server ;-D

14:53

<stgraber>

and you got that super slick and fast flickerless boot ?

14:53

<asmok>

yes

14:54

GodFather has quit IRC

14:55

<thunsucker>

stgraber: wow that sounds nice

14:55

<stgraber>

thunsucker: here it's basically the pxelinux loading sequence, then a splash for 10s without any flicker/black screen, then directly the login prompt

14:56

pmatulis has quit IRC

14:57

<asmok>

i have lots of t5125/t5135, i hope i got them to work too, there is something bad after login, but now i can test them with lucid - t5125 drops after login to the login screen again, let's see if i find something. they work with hardy just fine...

14:58

i now boot t5125...

14:59

<stgraber>

the oldest HP I have here is a 5735

15:00

and I have some 5745

15:03

<vmlintu>

I noticed the same problem yesterday with lucid - after login my via based thin client just went back to login screen

15:05

After I set LDM_DIRECTX=false and X_COLOR_DEPTH=16, it started working ok, so I didn't investigate it further

15:05

<Gadi>

have you disabled compiz?

15:05

<vmlintu>

Removing compiz didn't help with my box

15:05

It's some via based box with 1GHz CPU and 512Mb of memory

15:09

<asmok>

vmlintu: i try your setup too

15:09

<vmlintu>

LDM_DIRECTX=true

15:09

sorry, my mind is mixed up

15:10

LDM_DIRECTX=Y and X_COLOR_DEPTH=16 were the working ones

15:10

<asmok>

ok

15:11

C_Tek has quit IRC

15:22

<alkisg>

asmok: for some clients, disabling compiz helps:

15:22

!compiz

15:22

<ltspbot>

alkisg: "compiz" :: if compiz is giving you problems, one way to disable it for all users is: sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity

15:23

<asmok>

yes i did it, it is in my/stephane howto ;-) wai a minute, some good news coming ;-)

this was really good session, now i really can start to plan how to turn my hardy dhcp-failover setup to the ltsp-cluster setup, i got over 100 t5125/t5135 at my daughter's school. thank you everybody and good night!

15:38

asmok has left #ltsp

15:46

Selveste1___ has joined #ltsp

15:47

ogra_cmpc has joined #ltsp

16:02

hersonls has quit IRC

16:20

thunsucker has left #ltsp

16:26

<vagrantc>

hrm. gpxe and recent versions of qemu don't play well together...

16:29

<Gadi>

tho, they are prolly worth a lot of points in the game of Scrabble

16:29

<vagrantc>

true enough!

16:29

<Gadi>

see, now isn't that all that matters?

16:31

<vagrantc>

hrm.

16:31

seems like ltsp-update-sshkeys is creating an empty file for me... but when i re-run it, it works fine.

16:32

<Gadi>

ssh running the first time?

16:32

<vagrantc>

running?

16:32

ah, yes. sshd is running.

16:32

<Gadi>

not with legs

16:32

odd

16:33

<vagrantc>

Gadi: when you re-wrote it, does it not use the local files at all? i.e. it always scans the network?

16:33

<Gadi>

I believe so

16:33

* Gadi can be so presumptuous

16:33

<Gadi>

lets have a look-see

16:33

<vagrantc>

reading directly from the files themselves is a lot safer...

16:34

also, doesn't require the local machine to have sshd running

16:34

also got some reports that it was taking an inordinate amount of time at boot

16:34

<Gadi>

ok ok ok

16:34

geesh

16:34

:)

16:34

<vagrantc>

heh

16:35

<Gadi>

is it too late to fix? is the party over?

16:35

:)

16:35

<vagrantc>

party?

16:35

* vagrantc plays a kazoo

16:35

<Gadi>

what? we're not at a party?

16:35

* Gadi puts his pants back on

16:36

<Lns>

....wow.

16:40

that might be a good slogan... "SSH: Don't get caught with your pants down."

16:47

<vagrantc>

hrm.

16:48

ltspfs seems completely broken in testing :(

16:49

ah, false alarm... i haven't tested these other files yet...

16:54

<Gadi>

vagrantc: fixed, commited, pushed

16:54

please test

16:55

oh, and test while singing "pants on the ground" to Lns

16:55

<Lns>

lol

16:56

if you could guage the skills of an open source programmer to the personality quirks demonstrated on IRC...hahaha

16:56

gadi, you'd be a millionaire

16:58

<Gadi>

hehe

16:58

ciao, gang

16:58

Gadi has left #ltsp

16:59

<vagrantc>

just like gadi to fix something and disappear :)

17:01

<Lns>

hehe

17:01

at least he took his pants with him.

17:02

<highvoltage>

vagrantc: are you going to debconf?

17:03

<vagrantc>

seems to work

17:03

highvoltage: yes, you?

17:03

highvoltage: we met in sevilla years back, no?

17:03

<highvoltage>

vagrantc: yep, looking forward to seeing some familiar people and meeting new debian folk

17:03

vagrantc: yes, indeed

17:04

vagrantc: you are probably more memorable than I am, I thought you were interesting :)

17:07

<vagrantc>

i'm trying to concince some LTSP folks to crash debconf to do some ltsp hacking

17:07

<vmlintu>

what's next on the line for ltsp?

17:07

<highvoltage>

that would be great. stgraber is also going

17:09

komunista has quit IRC

17:09

<vagrantc>

stgraber: ah, didn't know you were going! :)

17:35

Lns has quit IRC

17:36

Lns has joined #ltsp

17:40

Lns has quit IRC

17:43

jammcq has quit IRC

17:48

alkisg has quit IRC

17:59

bobby_C has quit IRC

18:00

mikeshultz has quit IRC

18:07

mischko has joined #ltsp

18:10

Faithful has joined #ltsp

18:12

<stgraber>

vagrantc: it's only 5-6 hours away from here ;)

18:14

doh, would have liked that revert two weeks before ... now I'm starting sshd in d-i just to have ssh-keyscan do its magic :)

18:14

<vagrantc>

egads

18:14

<stgraber>

will be great to drop that in Maverick

18:16

<vagrantc>

stgraber: i'm sure you'e busy as all get-out right now, but was wondering if you might get a chance to update the ltsp-trunk/fr.po soonish?

18:25

<stgraber>

vagrantc: done

18:33

<vagrantc>

stgraber: thanks :)

18:34

i know folks have tried in the past, but i wonder if we could ever get a signle .po file for each language in ldm...

18:35

litlebuda has joined #ltsp

18:35

mischko has quit IRC

18:38

NeonLich1 has quit IRC

18:44

Faithful has quit IRC

18:46

staffencasa has quit IRC

18:52

NeonLicht has joined #ltsp

19:01

egghead has joined #ltsp

19:04

<egghead>

running ubuntu 9.10, using ltsp on a 64bit machine, tring to boot i386 clients (using usb drive) but get i think the i386 client trys to load in from /opt/ltsp/images/amd64 instead of the /opt/ltsp/images/i386 image, any one know if there is a config file to change the boot image for different clients?

19:04

epaphus has quit IRC

19:14

<johnny>

egghead, do you have both kinds of clients egghead ?

19:14

or just i386?

19:16

<egghead>

johnny, yes, both

19:17

is there a config file for ltsp that points to /opt/ltsp/images?

19:18

or maybe for tfpboot?

19:18

rjune has quit IRC

19:19

<egghead>

i think problem is i boot (from usb drive) i386 kernel and then it trys to load the amd64 image

Ryan52: gchar on the same line? or with the other gchar at the top of the function?

20:23

<johnny>

uggh :(

20:23

still having sound problems @ my store

20:23

<Ryan52>

no, guess not. do it like sec.

20:23

gchar * foo;

20:23

<johnny>

the volume starts at a normal level

20:24

<Ryan52>

foo = g_strconcat(.........);

20:24

epaphus has joined #ltsp

20:24

<johnny>

and then just gets quieter until tis gone

20:24

<Ryan52>

s/sec/this/

20:24

* Ryan52 is being rushed to leave by his dad...so cya.

20:26

egghead has left #ltsp

20:51

robbie_ has quit IRC

21:07

epaphus has quit IRC

21:09

waldo323 has quit IRC

21:11

pem725 has quit IRC

21:35

try2free has joined #ltsp

21:53

try2free has quit IRC

21:54

<vagrantc>

hmmm... the LDM_LOGIN_TIMEOUT doesn't seem to be working...

21:58

ah, it apparently needs to work in conjunction with LDM_GUESTLOGIN

21:59

* vagrantc is playing with ldm to randomly select a supported language to display and autologin/autologout

22:02

<vagrantc>

seems to be biased towards polish.

22:03

it would be tricky to implement... but would be cool if the language selection could also change the greeter language

22:08

<stgraber>

sounds tricky to implement (on the fly gettext language change)

22:09

<vagrantc>

a fairly brutal way would be to re-exec the greeter

22:10

but GDM changes the language when you select a different langauge, no?

22:13

well, ldm has decent support for 17 languages :)

22:17

i haven't done a very good job of asking folks to translate the rc.d and ltsp-cluster-info bits... the tools i use to send out the translations don't support multiple po files (as far as i know), and it would be confusing to send out multiple translation requests for a single package...

22:18

<Ryan52>

vagrantc: that sounds like a fun project.

22:19

<vagrantc>

Ryan52: oh, sparked your interest, have i? :)

22:19

Ryan52: changing the ldm UI to a new locale if the user selects a new locale?

22:21

ideally checking if it's a valid locale on the local system...

22:21

<Ryan52>

why?

22:21

doesn't hurt to try it anyway...it'll just fall back to the original string.

22:22

hm...one problem, tho. some of the text is translated on the server side by the ssh daemon.

22:23

<vagrantc>

Ryan52: none of that is translated anymore

22:23

any messages are just relayed through

22:23

<Ryan52>

exactly.

22:23

they are translated if the server's default language is a different language.

22:23

because then sshd would translate it.

22:24

* vagrantc doesn't see how that matters

22:24

<vagrantc>

Ryan52: regarding the fallback, if the default locale != C and they try to switch to an unsupported locale, then it will fall back to C ...

22:25

won't it?

22:25

<Ryan52>

if the servers language is spanish, and the ldm user selects french, half the interface would be in french and half in spanish.

22:25

and if the ldm translation for french isn't complete, some of the interface may even be english.

22:26

<vagrantc>

incomplete translations aren't anything we can do anything special about

22:26

Ryan52: but the server/thin-client language differences are already handled... it sets the locale variables when logging in via ssh...

22:27

<Ryan52>

that doesn't affect the strings relayed from sshd, tho.

22:27

does it?

22:27

<vagrantc>

no worse off than it is now.

22:27

in any case :)

22:27

<Ryan52>

I guess.

22:27

<vagrantc>

i'm not sure it ignores the locale variables...

22:29

currently, we can set the locale for the LDM UI with standard environment variables LANG, LC_ALL, etc. and LDM_LANGUAGE sets the user's locale for the logged in session, or alternately by selecting the language from the menu.,

22:30

but if the menu selection could both set the LDM UI and the user's soon-to-be logged in session, that would be nice.

22:32

* vagrantc wonders how GDM or KDM do it

22:33

<Ryan52>

it's really easy.

22:33

<vagrantc>

well then... :)

22:34

<Ryan52>

you just need to change the locale and set all of the strings again.

22:34

changing the locale is simple, generate_locale_list.py does it for example.

22:43

try2free has joined #ltsp

22:44

<Ryan52>

hm, GDM just restarts.

22:44

well that's kind of cheating. :P

22:49

Faithful has quit IRC

22:55

alkisg has joined #ltsp

23:01

rjune has quit IRC

23:02

<alkisg>

stgraber: turns out that we already have the latest udhcp version in Lucid, it's embedded in busybox!

23:03

So we can actually drop the udhcpc dependency, stop installing udhcpc, and just use busybox udhcpc -C

23:03

rjune has joined #ltsp

23:04

try2free has left #ltsp

23:07

Faithful has joined #ltsp

23:09

rjune has quit IRC

23:15

<alkisg>

Dah no there are 2 busybox versions, busybox-static has it, while busybox-initramfs doesn't. So maybe we should file a bug against busybox-initramfs and ask that they include udhcpc in their Makefile.