|00:02||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
|00:29||cryptrat has left IRC (cryptrat!481f0c3c@gateway/web/freenode/ip.126.96.36.199, Quit: Page closed)|
|03:07||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 250 seconds)|
|03:09||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
|03:15||vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)|
hrm. so i accepted the patches to fix size displaying in ltspfs, but now they produce all sorts of build warnings...
anyone with a slight understanding of C able to take a look at it?
essentially the patch: https://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltspfs-trunk/revision/170
introduced warnings like this:
ltspfs.c:891:9: warning: unused variable 'f_namelen' [-Wunused-variable] int f_namelen = (int)stbuf->f_namelen;
ltspfsd_functions.c:906:18: warning: 'f_type' may be used uninitialized in this function [-Wmaybe-uninitialized] stbuf.f_type = (__SWORD_TYPE) f_type;
pxe: Preboot execution environment boots computers using a network interface and image. See http://en.wikipedia.org/wiki/Preboot_Execution_Environment
gpxe: the successor to etherboot (http://etherboot.org). To download bootable floppy, cd, usb, kernel etc images, visit http://rom-o-matic.net/
ipxe: iPXE is the successor to the etherboot/gPXE project, and can be used to netboot clients that don't have a NIC ROM with a PXE stack. To add it to grub, see !grub-ipxe. To add it to the Windows boot loader, see !win32-loader. To download floppy, CD or USB images, visit http://ipxe.org or install the ipxe package.
vagrantc: that code is weird, almost as if someone had put the code into the wrong function of that pair
SpComb: well, in the history there was some switch from "foo" to "stbuf.foo" and some things seem to only have gotten partially switched.
my attempts to cargo cult it only resulted in more issues
the ltspfsd function to output the stbuf, updates the value within the stbuf
which is on the function stack and should be completely ignored
and the ltspfs function to read in an stbuf, gets the existing value within the stbuf, before overwriting it and discarding the read value
makes no sense
|07:09||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 260 seconds)|
|08:09||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 272 seconds)|
|08:26||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
|08:26||bernste4 has joined IRC (firstname.lastname@example.org)|
i have a big problem
the pxe is no longer working
i get an PXE-E32: TFTP open timeout
the log says that nbdrootd can not be found
and indeed there is no /usr/sbin/nbdrootd anymore
any idea what is going on?
|09:09||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
bernste4: nbd is not related to pxe. nbd comes a lot of steps after pxe succeeds
So look elsewhere for the problem, maybe dhcpd
E.g. dhcpd may be pointing the clients to the wrong tftp server..
it was the tftpd configuration
somehow the /etc/default/tftpd-hpa had an error
|09:21||workingcats_ has joined IRC (email@example.com)|
|09:21||workingcats has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|09:26||staffencasa has joined IRC (email@example.com)|
|09:26||mealstrom has left IRC (mealstrom!~Thunderbi@188.8.131.52, Ping timeout: 246 seconds)|
|09:34||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|09:36||andygraybeal has left IRC (email@example.com, Ping timeout: 250 seconds)|
|09:52||mealstrom has joined IRC (mealstrom!~Thunderbi@184.108.40.206)|
|10:14||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)|
|10:38||bernste4 has left IRC (firstname.lastname@example.org, Quit: leaving)|
|12:09||vsuojanen has joined IRC (email@example.com)|
|12:15||boospy has joined IRC (firstname.lastname@example.org)|
|12:30||boospy has left IRC (email@example.com)|
|12:47||Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)|
|13:12||staffencasa has joined IRC (firstname.lastname@example.org)|
|13:14||mealstrom has left IRC (mealstrom!~Thunderbi@220.127.116.11, Ping timeout: 240 seconds)|
|13:18||ben_nabiy is now known as bennabiy]|
|13:19||bennabiy] is now known as bennabiy|
|13:19||TatankaT_ has left IRC (TatankaT_email@example.com, Ping timeout: 255 seconds)|
|13:20||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 264 seconds)|
|13:22||TatankaT has joined IRC (TatankaTemail@example.com)|
vagrantc: if you still need some looking over the code, I might be able to do it after the weekend. I am pretty much not going to be here until then. (although I will still be here...)
|13:23||Phantomas has joined IRC (Phantomas!~phantomas@ubuntu/member/phantomas)|
|13:24||NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)|
|13:29||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 255 seconds)|
|13:31||adrianorg has joined IRC (email@example.com)|
|13:39||TatankaT has left IRC (TatankaTfirstname.lastname@example.org, Ping timeout: 255 seconds)|
|13:39||TatankaT has joined IRC (TatankaTemail@example.com)|
|14:27||mealstrom has joined IRC (mealstrom!~Thunderbi@18.104.22.168)|
|14:34||staffencasa has joined IRC (firstname.lastname@example.org)|
|14:51||staffencasa has left IRC (email@example.com, Ping timeout: 246 seconds)|
|14:56||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 240 seconds)|
|14:58||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
|15:18||staffencasa has joined IRC (firstname.lastname@example.org)|
|15:24||vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)|
|15:34||championofcyrodi has joined IRC (email@example.com)|
|15:39||||cw has left IRC (||cw!~chris@phpgroupware/cw, Ping timeout: 245 seconds)|
|15:53||||cw has joined IRC (||cw!~chris@phpgroupware/cw)|
|16:07||staffencasa has left IRC (firstname.lastname@example.org, Read error: Connection reset by peer)|
|16:10||staffencasa has joined IRC (email@example.com)|
|16:19||telex has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|16:20||telex has joined IRC (email@example.com)|
|16:33||Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)|
|16:33||championofcyrodi has left IRC (firstname.lastname@example.org)|
|17:07||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
vagrantc: what are the deadlines wrt ltspfs? can you wait for the weekend for bennabiy, or do you need some help before that?
alkisg: that's a good question
|17:29||* vagrantc looks at the freeze timeline|
|17:29||* alkisg has a couple of hours now...|
(but, no libc nor gtk knowledge :))
alkisg: it's not *urgent*, although i have no idea what ltspfsd fails to start from udev...
alkisg: i have viable workarounds for the "mount --move" issue, i think
including a mount-directly to /media implementation
it'd be good to have it fully sorted out by october, though not resolving those RC bugs could get it removed from jessie temporarily... which would be unfortunate
|17:34||* vagrantc wonders if a newly created ltsp chroot defaults to systemd yet|
vagrantc: there are 2 issues currently, one with the warnings after the patch, and one with systemd/move, right?
alkisg: three issues
And the latest code is in the trunk? Or in your local tree?
alkisg: systemd breaks ltspfsd starting on client, systemd breaks "mount --move" on server-side, size issue patches issue lots of warnings
And if you run the service with systemd later on, does it start then?
alkisg: i've got a workaround for "mount --move" in trunk, no idea about ltspfsd on client, and the size issue patch is a bit much C for me.
alkisg: ltspfsd starts from udev on an as-needed basis, but systemd doesn't seem to like that.
might make sense to just start ltspfsd as a normal daemon or something...
|17:38||* vagrantc suspects systemd has soe feature enabled that prevents the udev rules from being abe to spawn daemons or bind to ports or something|
alkisg: i've got the mount-directly-to-media in my local chroot, also submitted a patch to the debian bug
Push it upstream :)
About udev, I think my last idea would make sense, i.e. to spawn a screen session instead of a daemon
And then attach to that session and try to launch ltspfsd manually
working out a couple last changes
alkisg: as a troubleshooting idea?
well, i'd like to wrap up the mount-directly-to-media patchset
alkisg: would you be able to look at the build warnings?
the patch actually works (at least on i386/amd64), but it introduces some unsettling warnings...
|17:42||championofcyrodi has joined IRC (email@example.com)|
vagrantc: that one? http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltspfs-trunk/revision/170
alkisg: and the launchpad bug referenced by it
|17:43||* alkisg tries...|
|17:46||championofcyrodi has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
well, this diffstat looks good:
scripts/ltspfsmounter | 57 ++++++++++++++++++++-------------------------------------
src/lbmount.c | 84 ------------------------------------------------------------------------------------
2 files changed, 20 insertions(+), 121 deletions(-)
|17:48||championofcyrodi has joined IRC (email@example.com)|
considering that lbmount is setuid root code...
pushing to ltspfs-trunk...
hrm, my commit message isn't quite right ... lbmount really just creates/removes /media/username now.
vagrantc: after pulling latest trunk, `debuild -tc` now complains: Makefile.am: error: required file './ChangeLog' not found
oh, the packaging needs to run autogen.sh
haven't switched it to use dh_autoreconf yet.
wait, i have...
|17:55||* alkisg ran ./autogen.sh and then debuild -tc, it compiles now...|
|17:55||* vagrantc doesn't know "debuild -tc"|
-tc Clean the source tree (using gain-root-command debian/rules clean) after the package has been built.
right, just found it
sbalneav did those changes for 64-bit compatibility
Now that they're reverted, do you think it'll break again?
Are you testing with 32 bit or with 64 bit?
i've tested with a 64 bit server, a 64 bit client, and a 32 bit client
guess i haven't tested 32 bit server
I don't think bugs have been reported about that use case, ok
But only a few lines are reverted in the recent patch, not all of them...
Anyways, /me reads on..
i get the impression the 64 bit fixes caused the size issues
alkisg: the changelog thing failed because dh_autoreconf wasn't actually calling ./autogen.sh, it was calling various commands directly.
It worked fine before I pulled the last version from trunk... dunno why
because there was an empty ChangeLog file
which i removed, as it's really annoying to have a placeholder file
i.e. i put content in there that has to be moved out of the way during development
|18:22||* vagrantc wonders if the ltspfs/mounter.d hooks should be run in different spots|
but where i think they *should* go causes the mounts to fail. hrm.
vagrantc: about the warnings, you can just delete the 3 lines that declare the variables:
int f_type = (int)stbuf->f_type;
int f_bsize = (int)stbuf->f_bsize;
int f_namelen = (int)stbuf->f_namelen;
BUT, only if it compiles and works fine in 32/64 bit
sbalneav put them there because supposedly (int) is different from statfs/__SWORD_TYPE on 64bit
I hope that doesn't depend on any library versions... i.e. that it would work now but cause problems if backported...
But sbalneav had indeed made an error, in that he initialized the variables instead of assigning them values at the end
So it's either "delete the 3 lines, if everything works", or "back to what sbalneav wrote, but with a couple of changes"
|18:31||* vagrantc deletes a few lines and builds|
that's in ltspfs.c only, right?
there was also something in ltspfsd_functions.c
or maybe one caused the other
alkisg: that generates a lot of incompatible pointer type errors
ltspfs.c: In function 'ltspfs_statfs':
ltspfs.c:907:5: warning: passing argument 2 of 'xdr_int' from incompatible pointer type xdr_int(&in, &stbuf->f_type); /* type of fs */
|18:44||championofcyrod1 has joined IRC (firstname.lastname@example.org)|
alkisg: well, thanks for taking a look at it ... gotta run...
|18:45||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
vagrantc: diff from the latest trunk: http://paste.ubuntu.com/8056040/
It compiles without errors here that way
We need to find the bug report about the 64bit errors though, to verify it's not still an issue
|18:59||championofcyrodi has left IRC (email@example.com, Quit: Leaving.)|
|19:35||sagi_ has joined IRC (sagi_!d5399408@gateway/web/freenode/ip.22.214.171.124)|
hello every, can someone told me if ltsp is supporting in ubuntu 14.04
its in there...
what's is mean?
like you can apt-get install ltsp-server and such
what about an iso file?
like was in 12.02
i was just need to press f4
and the installtion was chage
oh, the alternative installer
to lstp server
|19:38||talntid has left IRC (talntid!~talntid@173-160-189-58-Washington.hfc.comcastbusiness.net, )|
yeah, i haven't checked. they don't usually remove things like that
certainly woudn't be hard to find out
i dont find thing like this when i search all over the internt
why not just download the iso and check?
the regular one?
the alternative installer
there has no alternative installer to 14.04
there has no alternative installer to 14.04
there has no alternative installer to 14.04!
then i am clearly mistaken on it being there
|19:48||sagi_ has left IRC (sagi_!d5399408@gateway/web/freenode/ip.126.96.36.199, Quit: Page closed)|
slackish: it's true. http://mirror.anl.gov/pub/ubuntu-iso/DVDs/ubuntu/14.04/release/
however, the server installer is pretty close to being the same thing as the alternate
personally, I use apt-cacher-ng and the mini-iso
|20:15||vsuojane1 has joined IRC (firstname.lastname@example.org)|
Error: "alternate" is not a valid command.
!learn alternate as the ubuntu alternate CD was dropped in 12.04: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1042999
The operation succeeded.
|20:56||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)|
|21:49||highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Ping timeout: 272 seconds)|
|21:57||highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)|
|22:14||vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)|