sorry, i have to go
|00:05||asmok has left IRC (email@example.com, Quit: Lähdössä)|
vagrantc: I synced ltsp-docs 1.0 in Ubuntu. Thanks for the release and upload
|01:05||monteslu has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|01:28||vagrantc has left IRC (email@example.com, Ping timeout: 255 seconds)|
|01:30||vagrantc has joined IRC (firstname.lastname@example.org)|
vagrantc: I plan on spending part of tomorrow dealing with LTSP in Ubuntu. Starting by trying to reduce the packaging delta on ldm, I might have some patches for you if I find some ways to bring Debian and Ubuntu even closer on ldm's packaging
|01:46||monteslu has joined IRC (email@example.com)|
|01:47||Parker955_Away is now known as Parker955|
stgraber: i've been meaning to get a new upload of ltsp into debian ... if we have aufs for the forseeable future, i can switch to NFS+aufs ...
stgraber: any idea if overlayfs works with NFS ?
vagrantc: haven't tried. overlayfs is supposed to be much closer to a proper VFS overlay so it's more likely to work than the previous iterations
I also want to spend some time tomorrow testing the current trunk and see if it's in an uploadable state (as in, installs, boots, lets me login), if it's, I'll upload that and deal with the issues as they show up
|02:00||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
stgraber: i managed to get trunk as of a few weeks ago working for debian, at least
good, that's a bit reassuring :)
is that currently in Debian?
argh, just confirmed my fear, LTSP doesn't really work with resolvconf, now the default in Ubuntu ... looks like I'll need to hack our udhcp init script to deal with resolvconf :)
|02:16||* stgraber adds that to the TODO for tomorrow|
|02:25||Mobe_ has left IRC (Mobe_!~Mobe@adsl-82-141-65-229.kotinet.com, Ping timeout: 276 seconds)|
anyone gonna be at fosdem?
|04:48||Parker955 is now known as Parker955_Away|
|04:52||freedomrun has joined IRC (email@example.com)|
|05:12||lifeboy_ has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|05:46||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
dberkholz: i plan to be at fosdem on saturday
At many places we're trying to discover the ssh pid, the ltsp client hostname, ip address, the client $DISPLAY etc, and we go through hoops to get them.
Wouldn't it be easier instead of just "echo LTSPROCKS; /bin/sh -", to do something like:
"echo LTSPROCKS; echo ...a bunch of useful vars > ~/.ltsp-connection-$IP; exec /bin/sh -" ?
Then we'd just look at the user's home dir and have everything ready... (btw shouldn't we put the "exec" there anyway, to save a bash process?)
We could then easily implement an "ltsp-connections-info" script, or an "ltsp-exec" script, and LDM_LIMIT_ONE_SESSION could be rewritten better, etc etc
|06:55||loather-work has left IRC (email@example.com, Quit: This computer has gone to sleep)|
|07:16||Damianos has left IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net, Remote host closed the connection)|
|07:41||killermike has joined IRC (firstname.lastname@example.org)|
|08:02||map7_ has joined IRC (email@example.com)|
alkisg, I got the fat client working last night. Think I'll use that and just install mythfrontend in the image.
map7_: nice, any problems aside from applying the patch?
I think fat clients is the way to go, and even with a vbox frontend for managing the chroot ;)
no problems, I just edited the files manually. I might do separate patches so I can apply them in a auto build script
alkisg: win32-loader: win32-loader.exe can be used to add a "PXE - Network boot" option to the Windows boot manager. It's developed for Debian and it uses gPXE/iPXE for the network booting. You can download a binary from http://ts.sch.gr/docs/kanonismoi-diadikasies/doc_download/327-ltsp-loader - (if someone can write a wiki page about it it'd be nice :))
|08:20||freedomrun has left IRC (firstname.lastname@example.org, Read error: Connection reset by peer)|
|08:40||loather has left IRC (email@example.com, Quit: This computer has gone to sleep)|
|09:06||vagrantc has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
|09:09||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)|
|09:13||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
|09:28||loather-work has joined IRC (email@example.com)|
|09:40||loather-work has left IRC (firstname.lastname@example.org, Quit: This computer has gone to sleep)|
|10:00||Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)|
|10:22||freedomrun has joined IRC (freedomrun!~quassel@BSN-142-163-74.dial-up.dsl.siol.net)|
|10:30||adrianorg has joined IRC (email@example.com)|
|10:32||Yet_another_Bill has left IRC (Yet_another_Bill!billy@nat/redhat/x-dkqxdanbnnnlislt, Ping timeout: 240 seconds)|
|10:32||Yet_another_Bill has joined IRC (Yet_another_Bill!billy@nat/redhat/x-hvqxsutevkghnigm)|
|10:38||ogra_ has joined IRC (firstname.lastname@example.org)|
|10:49||dobber has joined IRC (email@example.com)|
|11:15||freedomrun_ has joined IRC (freedomrun_!~quassel@BSN-142-161-119.dial-up.dsl.siol.net)|
|11:16||xsl has joined IRC (xsl!~silence@unaffiliated/xsl)|
|11:16||freedomrun has left IRC (freedomrun!~quassel@BSN-142-163-74.dial-up.dsl.siol.net, Ping timeout: 272 seconds)|
|11:44||killermike_ has joined IRC (firstname.lastname@example.org)|
|11:45||killermike has left IRC (email@example.com, Ping timeout: 252 seconds)|
|11:50||killermike_ has left IRC (firstname.lastname@example.org, Ping timeout: 252 seconds)|
|11:51||killermike_ has joined IRC (email@example.com)|
|11:57||killermike_ has left IRC (firstname.lastname@example.org, Ping timeout: 252 seconds)|
|12:00||killermike_ has joined IRC (email@example.com)|
|12:02||[GuS] has joined IRC ([GuS]!~MysT@18.104.22.168)|
|12:02||[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)|
|12:04||killermike_ has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|12:04||killermike_ has joined IRC (email@example.com)|
|12:12||khildin has joined IRC (firstname.lastname@example.org)|
|12:18||Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Remote host closed the connection)|
|12:30||bengoa has joined IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9)|
|12:39||Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)|
|12:53||bobby_C has joined IRC (bobby_Cemail@example.com)|
|12:58||monteslu has left IRC (firstname.lastname@example.org, Ping timeout: 252 seconds)|
|13:10||monteslu has joined IRC (email@example.com)|
|13:22||ncd209_ has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|13:29||mgariepy has joined IRC (mgariepy!mgariepy@ubuntu/member/mgariepy)|
|13:49||Parker955_Away is now known as Parker955|
|13:54||adrianorg has left IRC (email@example.com, Ping timeout: 245 seconds)|
|14:08||Parker955 is now known as Parker955_Away|
|14:11||Trixboxer has joined IRC (Trixboxer!~Trixboxer@22.214.171.124)|
|14:44||alexqwesa has left IRC (firstname.lastname@example.org, Quit: Š„Š°Š½Š° X'Š°Š¼ !!!)|
|14:48||brunolambert has joined IRC (brunolambert!bruno@nat/revolutionlinux/x-wydnkygqikuzbwqc)|
|14:54||dead_inside has joined IRC (email@example.com)|
|15:15||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)|
|15:19||mmetzger has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|15:40||darkpixel_ has joined IRC (email@example.com)|
|15:41||darkpixel_ has joined IRC (darkpixel_!~darkpixel@curetheitch/staff/darkpixel)|
|15:42||ogra_ has left IRC (firstname.lastname@example.org, Excess Flood)|
|15:44||ogra_ has joined IRC (email@example.com)|
|15:49||alexqwesa has joined IRC (firstname.lastname@example.org)|
|15:53||adrianorg has joined IRC (email@example.com)|
|16:04||adrianorg has left IRC (firstname.lastname@example.org, Read error: Operation timed out)|
|16:10||mmetzger has joined IRC (email@example.com)|
|16:14||staffencasa has joined IRC (firstname.lastname@example.org)|
|16:20||loather has joined IRC (email@example.com)|
|16:31||freedomrun_ has left IRC (freedomrun_!~quassel@BSN-142-161-119.dial-up.dsl.siol.net, Remote host closed the connection)|
|16:35||toscalix has joined IRC (firstname.lastname@example.org)|
|16:37||toscalix has left IRC (email@example.com, Remote host closed the connection)|
|16:38||toscalix has joined IRC (firstname.lastname@example.org)|
|17:08||toscalix has left IRC (email@example.com, Excess Flood)|
|17:09||toscalix has joined IRC (firstname.lastname@example.org)|
|17:13||dobber has left IRC (email@example.com, Remote host closed the connection)|
|17:36||freedomrun has joined IRC (firstname.lastname@example.org)|
|17:50||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
|17:56||Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Ping timeout: 244 seconds)|
|17:57||xsl has left IRC (xsl!~silence@unaffiliated/xsl, Quit: Connection reset by fear)|
|18:04||ogra_ has left IRC (email@example.com, Excess Flood)|
|18:05||ogra_ has joined IRC (firstname.lastname@example.org)|
|18:11||khildin has left IRC (email@example.com, Quit: I'm gone, bye bye)|
|18:15||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)|
|18:41||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
|18:51||artista_frustrad has joined IRC (firstname.lastname@example.org)|
|18:52||vagrantc has joined IRC (email@example.com)|
stgraber: the dependencies and recommends are clearly from a different interpretation of what ldm-server provides...
stgraber: i.e. it depends on openssh-server because i cannot think of a use-case that doesn't require ssh... it recommends xauth so that LDM_DIRECTX=true works, it recommends ltspfs so that the client-side ltspfs stuff works, and libasound2-plugins so that remote audio works...
it is a package to install to ensure that a machine can function with the LTSP defaults.
(and commonly used features)
which is exactly what recommends are for
We don't have recommends on in debian/ubuntu ltsp chroots, do we?
y'all fly by different rules
but according to debian policies and best practices, i think i have those things set properly.
vagrantc: yeah, I can see where these come from, would have preferred some ltsp-server-minimal or similar bringing these AND ldm-server
|18:58||Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)|
but those features are specific to a working LDM+LTSP environment, not the LTSP server.
we've got ltsp-server (which provides the minimalist functionality) and ltsp-server-standalone (which provides complete functionality)
and depends on ldm-server
the most common use-case (or at least, our default use-case) is an LTSP+LDM environment, and you get that by installing ltsp-server-standalone
but it's not unheard of to have an LTSP server that only exports the rootfs, and separate LDM servers that include applications and such without any rootfs stuff.
although i wish we could rename ltsp-server-standalone to ltsp-server and ltsp-server to ltsp-server-core or something like that ... but the names are pretty much impossible to reconcile.
we should maybe also think of spliting out the server-side localapps stuff into a separate package
since that should be installable in an LDM server without LTSP installed.
|19:06||* vagrantc hopes vagrantc hasn't flooded the channel|
stgraber: you think it's feasible to go for gtk3 in the near future? the gtk maintainers in debian would be happy to get the conversion out of the way.
|19:07||adrianorg has joined IRC (firstname.lastname@example.org)|
stgraber: we might also want to make the autogen.sh stuff more forcefull, so that autoreconf stuff works "properly"
stgraber: or at least have a "really, go ahead and re-do everything" flag.
vagrantc: sorry, got pulled into an IRC meeting
vagrantc: I'm 90% done porting to gtk3, the only broken code is the bit that sets the background
vagrantc: well, that an porting all the themes ;)
stgraber: oh, regarding gtk2-engines-ubuntulooks vs. gtk2-engines ... the only reason i stuck with ubuntulooks all these years is the size of the package.
stgraber: installed size of 1m vs. 160k
but it would probably be better to switch the theme back
vagrantc: yeah, I seem to remember you mentioning a dependency on clearlooks would pull quite a few packages in. I guess that's fine for Debian, it's just not doable in Ubuntu as ubuntulooks simply doesn't exist here ;)
stgraber: i'd rather sync than diverge at this point though.
stgraber: i'd really like to go with gtk2-engines-murrine, but that has a stupid recommends on murrine-themes, which is *huge*
highvoltage created ldm-themes which uses murrine, and i like it better ... just wish there was a Conflicts-Recommends
so i could exclude murrine-themes
but allow it to install if they really wanted it
murrine-themes is a suggests of gtk2-engines-murrine in Ubuntu
wontfixed and closed.
stgraber: you lucky punks!
well, we didn't want murrine-themes promoted to main apparently ;)
|19:16||* highvoltage emerges|
|19:16||* vagrantc waves to highvoltage|
stgraber: ah, so you wouldn't go with that either
|19:17||* highvoltage waves too|
stgraber: oh! you mean gtk2-engines-murrine is in main, but the themes aren't
it doesn't make any sense to me to have an engine recommend a theme
stgraber: if i can convince the maintainer otherwise, would you be willing to sync on murrine?
vagrantc: yep, I don't mind going with murrine, it's in main and probably lighter than our current gtk2-engines (that's probably pretty big)
stgraber: i'll poke em on irc and see if i can't get them to reconsider
|19:22||* Hyperbyte waves to everybody|
highvoltage: time to probably stir the muck with ldm-themes again, with freeze in a few months
highvoltage: dunno what the wheezy artwork scene is like
vagrantc: I've been following the lists
highvoltage: ah good, i haven't :)
vagrantc: the calls for artwork is only being announced now, so there's nothing yet to package
|19:25||Parker955_Away is now known as Parker955|
highvoltage: that's the sort of thing that's generally freeze exception worthy, given that it's not generally technically difficult
vagrantc: great. I'd hope so :)
highvoltage: and the artwork isn't usually selected till pretty late in the cycle
So, does anyone have a script that can fix "stupid" ?
depends on the context
|19:34||* shawnp0wers has had a long day of "oh noes, when I minimize an application it dissappears because I apparently deleted the window selector|
|19:37||Kens has joined IRC (Kens!c67def69@gateway/web/freenode/ip.126.96.36.199)|
how to set up kiosk mode? Anyone?
|19:40||bengoa has left IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9, Quit: Leaving.)|
|19:40||brunolambert has left IRC (brunolambert!bruno@nat/revolutionlinux/x-wydnkygqikuzbwqc, Quit: brunolambert)|
|19:43||brunolambert has joined IRC (brunolambert!bruno@nat/revolutionlinux/x-crvxulsripjbphck)|
alkisg: if epoptes client doesn't handle openssl being missing, we may as well depend or at least recommend it.
vagrantc: epoptes-client doesn't need openssl
alkisg: then it should gracefully error out when it tries to use it
alkisg: rather than spitting out command not found...
Sure, I'll do that. The -c switch is just there to help the users, it's a "run-time" dependency
They may use "cp" instead
alkisg: doesn't seem an unreasonable recommends, to me.
(italc doesn't even have an option like that, it suggests transfering the keys using usb sticks :P)
I was planning to put it to Suggests
suggests is close to pointless
But no problem with recommends either
reccommends pulls it in by default usually, but allows them to not have it installed if they really don't want it
It's not used by epoptes-client though... just by the user, and only once, and only if he isn't using the ltsp-build-client plugin that copies the keys, etc etc
alkisg: perfect case for recommends.
Recommends it is then :)
or does it pull in a lot of cruft?
No idea it's usually preinstalled in ltsp chroots
I don't know why it wasn't there for him
|19:48||* vagrantc is surprised a full LTSP chroot wouldn't have it|
|19:49||* alkisg is optimizing the thumbnails logic in epoptes... will be ready for a new release in a couple of days|
|19:49||* vagrantc wonders if debian-edu knows about epoptes|
A couple of them do, we mentioned it in some edubuntu meeting when they were attending
i know they've been fighting with italc for years
|19:57||[GuS] has left IRC ([GuS]!~MysT@unaffiliated/gus/x-663402, Remote host closed the connection)|
|20:00||ogra_ has left IRC (email@example.com, Excess Flood)|
|20:02||ogra_ has joined IRC (firstname.lastname@example.org)|
|20:05||adrianorg has left IRC (email@example.com, Ping timeout: 272 seconds)|
|20:08||Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)|
stgraber: well, the gtk2-engines-murrine maintainer doesn't really seem willing to consider the issue. ugh.
what's his reason for having a gtk engine pull themes at install?
stgraber: i haven't seen one yet, other than "we disagree"
|20:20||toscalix has left IRC (firstname.lastname@example.org, Read error: Connection reset by peer)|
alkisg: when can we do an edubuntu blog post on epoptes?
highvoltage: I think it'd be best when the new version is published in precise... so maybe in a week?
stgraber: and 12:15 < Corsac> vagrantc: this is a *recommends*, not a depends
alkisg: ok, I'll poke you again in a week :)
stgraber: which doesn't seem to justify it any better to me
vagrantc: yeah and with Recommends being installed by default it's still wasting space...
stgraber: for, as far as i can tell, no reason.
stgraber: given that the only things that depend/recommend gtk2-engines-murrine are ... other themes.
vagrantc: you could create a package that Conflicts with murrine-themes and is itself a Recommends of ldm? That'd give you a Conflict-Recommends :)
stgraber: that would be heinously ugly, but it would work.
stgraber: didn't we at some point did that in Edubuntu :)
highvoltage: kind-of, edubuntu-live does something like that ;) It's a package present at DVD build time but not present post-install, so we can blacklist stuff without preventing the user from installing them later one
stgraber: given all that, i think we should just stick with clearlooks.
stgraber: which on debian is shipped in gtk2-engines
|20:28||* vagrantc wishes clearlooks was still packaged independently.|
right, same as Ubuntu, then, so we'd be in sync for that bit. I pushed the ltsp-cluster-info fix upstream, so that's another delta we get rid of. So the only thing left is debian/watch which I don't care about if we're in sync anyway
so with switching to gtk2-engines and dropping the current patch + using the latest upstream, Ubuntu could simply sync ldm from Debian
stgraber: well, the watch file was simply (maybe ubuntu shipped a newer upstream version) and (maybe debian shipped a new upstream version)
stgraber: that sounds great!
stgraber: so the security risk with the ssh-hostchecker scripts is that one server could impersonate another
I already got Colin to unblacklist ldm in the package importer, so now it's like any other package in the archive, people are asked to merge as long as we have an Ubuntu delta and as soon as we don't, it gets directly imported from Debian
stgraber: how do you upload delta-less?
Launchpad lets us "sync" from Debian, that basically copy the source package as-is from Debian and builds it, so we loose our Ubuntu changelog but from that point, any change in Debian is automatically imported (until the auto-import freeze)
after that, we can do manual syncs using "syncpackage -d sid ldm" (or experimental if we know it's what we want)
stgraber: you think it'll be synced for precise?
stgraber: or post-precise?
|20:35||adrianorg has joined IRC (email@example.com)|
if we get a new upstream ldm by FeatureFreeze (mid-February IIRC) and you change to use clearlooks, yes, no reason we wouldn't sync
feature freeze is on the 16th of February
think it's almost time for ltsp 5.3.0 ?
well, I'd prefer to make sure it works before we do that ;)
heh, well sure
other than that, yes I think we may want to bump ltsp's version in the near future (still keeping LTSP 6 for when we have all of sbalneav new magic)
with the initramfs-scripts.d code, it pretty much assumes writeable / ... which i'd like to put off a little longer
for ldm, I want to wait for it to be on gtk3 before doing any major version bump
stgraber: and alkis's boot the chroot to maintain the chroot stuff
although with the initramfs-scripts.d code, i think we're close with that.
highvoltage: i'm tempted to push a gtk2-engine-murrine-without-murrine-themes package doing what stgraber suggested.
it seems stupid, but it'd work...
it comes down to ubuntulooks being a few hundred k, clearlooks amounting to 1m, murrine (with murrine themes) 5m, murrine (without murrine themes) a few hundred k.
vagrantc: how about forking it to gtk2-engine-ltsp? then we can change it further?
|20:55||map7_ has left IRC (firstname.lastname@example.org, Ping timeout: 252 seconds)|
(not sure if that's a good idea, but just throwing it out there anyway)
highvoltage: kind of want to avoid maintaining more than we have to
|20:56||killermike_ has left IRC (email@example.com, Remote host closed the connection)|
gtk2-engines/clearlooks seems to be a reasonable middle ground
stgraber: so should i package up trunk as ldm 2.2.5 today and get that rolling?
vagrantc: sounds good. I haven't tested the current trunk with the new ssh stuff, but if that looks good to you, go ahead
|21:04||asmok has joined IRC (firstname.lastname@example.org)|
stgraber: i think the big difference with ubuntu and debian in the dependencies is how we treat ltsp-server vs. ldm-server ... i think debian makes it possible to use the LDM server vs. LTSP server functionality where appropriate, rather than assuming all LTSP servers provide all the ldm-server functionality.
|21:11||Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)|
In ldm: "echo LTSPROCKS; /bin/sh -"
==> we could at least save a bash process by using "exec /bin/sh -", stgraber if you're checking the ldm code, could you try to put it there so that we have it for precise?
alkisg, booting with win32 loader and gpxe is terribly slow and sometimes hangs in kernel loading.
alkisg: Pushed up to revision 1407.
stgraber: thanks :)
alkisg: you know you could have done it yourself right? :)
stgraber: not the testing, not easily
I don't have the build-deps handy for precise
alkisg: you've tested that, right? :)
alkisg: well, I consider most of the current changes in current ldm-trunk to be untested anyway
Nope, not at all,it's just an idea
alkisg: at least this one is going to be pretty visible and obvious if it fails ;)
It should save us one bash process per user
muppis: I have a new one with fresh ipxe from git, here: http://people.ubuntu.com/~alkisg/boot/win32-loader.exe
actually, dash, no?
which is a much smaller savings
yeah, dash in this case
vagrantc: no, it's the ssh shell we're saving
And we're keeping dash
ah yeah, we get rid of a bash instead of having bash + dash
alkisg, I'll try to member to try that tomorrow.
I don't know if anyone saw a question I did some hours ago...
Exactly after echoing LTSPROCKS, we could write some env vars in a file in the user's home dir
E.g. in ~/.ltsp-connection.$PPID
For example, the ssh pid, the user's $DISPLAY, client hostname etc
So we could easily implement LDM_LIMIT_ONE_SESSION etc without going through hoops to get those vars
muppis: you're using local network and tftp, not downloading the kernel over http, right?
It should have the same speed as using gpxe from any other media, i.e. it should download the kernel in a couple of seconds
alkisg: yeah, I suppose we could do something like that. I'd rather have one file containing one PID per line where the PID is the one of sshd. We could probably have that file generated at each login using pgrep.
alkisg: then the rc.d hook can simply check if it's more than one line long and exit if it's
stgraber: I'd like to have more info for the client there, not just the pid
E.g. "you are already logged in at $HOSTNAME, $VT..."
alkisg, yes. Using nic pxe everything works as should, but with gpxe it mostly hangs or is unusable slow.
|21:27||Trixboxer has left IRC (Trixboxer!~Trixboxer@188.8.131.52, Quit: "Achievement is not the end, its the beginning of new journey !!!")|
muppis: the win32-loader shouldn't affect the gpxe speed. So for any bad driver performance, you should mention that in #ipxe, after testing with the latest version
The ipxe speed isn't at all related to the boot loader
Now need catch some sleep.
|21:45||Parker955 is now known as Parker955_Away|
|21:45||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)|
|21:46||asmok has left IRC (email@example.com, Quit: Lähdössä)|
|21:56||asmok has joined IRC (firstname.lastname@example.org)|
|22:12||asmok has left IRC (email@example.com, Quit: Lähdössä)|
stgraber: darn. ldm fails to build :(
vagrantc: weird, can you paste the build log?
stgraber: something to do with AM_GLIB_GNU_GETTEXT not found in library
i first tried without mkdst, and then i tried with, and both fail
trying a test build here
maybe somethinng new in sid
it builds fine here, though I haven't tried in a clean way
I did: bzr export /tmp/blah && cd /tmp/blah && apt-get build-dep ldm && sh autogen.sh && ./configure && make
|22:30||muppis has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|22:34||brunolambert has left IRC (brunolambert!bruno@nat/revolutionlinux/x-crvxulsripjbphck, Quit: brunolambert)|
no luck with wheezy either...
|23:05||ogra_ has left IRC (email@example.com, Excess Flood)|
|23:06||Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Quit: Leaving)|
so i tried a rebuild of 2.2.4 and that worked fine.
|23:08||ogra_ has joined IRC (firstname.lastname@example.org)|
stgraber: what versions of auto* are you running?
vagrantc: autoconf 2.68, automake 1.11.1
|23:16||freedomrun has left IRC (email@example.com, Remote host closed the connection)|
automake 1.11.2 here ...
that's not likely to be significantly different
|23:17||Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)|
here i was thinking to tackle the low-hanging fruit
config.status: error: cannot find input file: 'po/Makefile.in.in'
maybe my autoreconf stuff isn't calling the po stuff that mkdst did?
which was removed well before 2.2.4 ... so that's not really it
|23:25||Parker955_Away is now known as Parker955|
|23:25||bobby_C has left IRC (bobby_Cfirstname.lastname@example.org, Ping timeout: 244 seconds)|
|23:35||Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Ping timeout: 276 seconds)|
stgraber: build log: http://people.debian.org/~vagrant/ldm/
ok, good to go, if you've got a moment to look...
stgraber: maybe it's the new ltsp-cluster stuff you added?
vagrantc: could be but my test run was on current trunk
|23:52||dead_inside has left IRC (email@example.com, Quit: Leaving...)|
|23:53||* vagrantc tries without|
vagrantc: did you try calling autogen.sh instead of calling autoreconf? they seem to have a pretty different result here
(as in, autoreconf fails, autogen.sh doesn't)
i did that with something else, and don't think i'm getting it right here...
ok, I think I got autoreconf to work but it takes some convincing
hmm, actually, not it doesn't work
config.status: error: cannot find input file: `po/Makefile.in.in'
I definitely don't get this one when running autogen.sh
i'm having dh_autoreconf call autogen.sh ... should work.
that did it!
doh! i had that problem with another build.