00:00 | <vagrantc> eddytv: although earlier, you didn't have any problem with X starting ... what changed since then?
| |
00:01 | <eddytv> No, X never started -- it always errored out because it couldn't find any matching modes for this client's TV display
| |
00:02 | So putting my custom xorg.conf in (which I figured was the easiest way to get X working, rather than trying to figure out what lts.conf option I needed to set appropriate modelines, etc.) was the simplest solution for now
| |
00:08 | Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas) | |
00:11 | <vagrantc> ah, ok.
| |
00:15 | Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas) | |
01:32 | vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 265 seconds) | |
02:45 | vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc) | |
03:03 | adrianorg has left IRC (adrianorg!~adrianorg@177.18.169.90, Remote host closed the connection) | |
03:30 | adrianorg has joined IRC (adrianorg!~adrianorg@177.18.169.90) | |
03:33 | bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) | |
03:39 | shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com, Read error: Connection reset by peer) | |
04:10 | adrianorg has left IRC (adrianorg!~adrianorg@177.18.169.90, Ping timeout: 256 seconds) | |
04:18 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
04:22 | <alkisg> vagrantc: hi, I'm thinking that shipping an /etc/ltsp/update-kernels.conf file as part of ltsp-client is the best way to (a) allow the users to edit the command line (b) preserve their changes on updates (c) work with older chroots or chroots of a different distro. Example content:
| |
04:22 | NBD_CMDLINE='ro initrd=$INITRD root=/dev/nbd0 init=/sbin/init-ltsp nbdroot=$SERVER:$PORT$NBD_NAME'
| |
04:22 | NFS_CMDLINE='ro initrd=$INITRD root=/dev/nfs init=/sbin/init-ltsp'
| |
04:22 | If you don't mind shipping such a file (or generating it on postinst), I'd prefer to have ltsp-update-kernels and update-kernels rely on its existence, makes the code saner too
| |
04:33 | <eddytv> Hi alkisg. Did you see my comment above about /tmp being mode 755 on my diskless clients? Just curious if you know why that is happening (it's correct in the /opt/ltsp/amd64 tree itself).
| |
04:34 | <alkisg> eddytv: is that a newly built chroot, or the old 11.04 one?
| |
04:34 | <eddytv> New.
| |
04:34 | Built with 12.04
| |
04:35 | It prevents X from starting
| |
04:35 | If I ssh in to the diskless client and 'chmod 1777 /tmp', X starts up
| |
04:36 | I'm heading off to bed, but if you can think of anything to check, I'll look for ideas in the morning. I hate to put in a hack in rc.local if it can be fixed properly.
| |
04:36 | <alkisg> Does /tmp/ show up in `cat /proc/mounts` on the client?
| |
04:39 | <vagrantc> alkisg: hm.
| |
04:41 | alkisg: encoding the server and port and NBD_NAME seems like a bad idea ... but otherwise sure, i guess.
| |
04:41 | <cyberorg> alkisg, we use another script to configure pxelinux.cfg/default, "root=..." is not required on suse
| |
04:41 | <alkisg> cyberorg: you'd just ship a different command line in the client /etc/ltsp/update-kernels.conf, like all other distros
| |
04:42 | Each distro would ship the command line it needs, there's no need to have different scripts, it's just a configuration file
| |
04:42 | vagrantc: are you talking in general about the presence of variables in those NBD_CMDLINE etc lines?
| |
04:42 | Or about the server parts specifically?
| |
04:43 | <vagrantc> alkisg: ah, you used '' instead of "" ... so the variables are meant to be updated on the server?
| |
04:43 | <alkisg> update-kernels in the chroot will still generate a correct command line, i.e. it'll replace NBD_NAME with the chroot arch like it does now
| |
04:43 | vagrantc: here's the long version:
| |
04:43 | <vagrantc> might be useful to have an $NFSROOT as well, then.
| |
04:44 | <alkisg> Of course
| |
04:44 | The chroot is generated, update-kernels (should) run at the end of ltsp-build-client, and at that point it tries to generate pxelinux.cfg/default, .nbi kernels etc
| |
04:44 | <cyberorg> alkisg, here is an example of what it looks like http://cyberorg.co.in/default
| |
04:44 | <vagrantc> update-kernels client-side?
| |
04:45 | <alkisg> Client side, yes
| |
04:45 | cyberorg: yes in order to generate that you'd ust need to provide NBD_CMDLINE and NFS_CMDLINE in client's /etc/ltsp/update-kernels.conf
| |
04:45 | And you'd automatically get NFS or/and NBD entries as the server supports them
| |
04:46 | <cyberorg> alkisg, we dont use NBD_CMDLINE and NFS_CMDLINE
| |
04:46 | user's customization goes in default.local
| |
04:46 | <alkisg> cyberorg: ubuntu server / opensuse chroot, don't you want it to work at this case?
| |
04:47 | vagrantc: at that point, update-kernels doesn't know about SERVER, NFSROOT etc, but it can at least replace EXPORT_NAME with $arch
| |
04:47 | vagrantc: so the generated command line then will be the same as it is now, no difference
| |
04:48 | <vagrantc> what about things that are shared between NFS and NBD and something as yet undefined ... do we duplicate them?
| |
04:49 | alkisg: so what replaces $SERVER, $NFSROOT, etc?
| |
04:49 | <alkisg> vagrantc: then on the server part, ltsp-update-kernels runs. This has more info; it knows if the server needs IPAPPEND or not, the server IP, PORT, EXPORT_NAME (scratch NBD_NAME, not a good variable name). So it can generate a better pxelinux.cfg/default than update-kernels in the chroot
| |
04:50 | <vagrantc> so the chroot would generate a best-effort pxelinux.cfg/default, but server-side it would generate an alternate one?
| |
04:51 | <alkisg> Yup, but then ltsp-update-kernels writes the new info it knows in the chroot /var/lib/ltsp/update-kernels.conf too, so that the next time, the client update-kernels will use it to generate better .nbi images which need embedded command line
| |
04:51 | E.g. the EXPORT_NAME
| |
04:52 | So both tools share the same pxelinux.cfg/default generation code
| |
04:52 | Parker955_Away is now known as Parker955 | |
04:53 | <vagrantc> ltsp-update-kernels dumps into $CHROOT/var/lib/ltsp/update-kernels.conf ?
| |
04:53 | <alkisg> Yes, but only the related variables
| |
04:54 | <vagrantc> maybe that should get created before update-kernels ever runs ...
| |
04:55 | (client update-kernels)
| |
04:55 | so that it can get it right the first time
| |
04:55 | <alkisg> That file can be overriden by the user from /etc/ltsp/update-kernels.conf
| |
04:55 | It contains server info, the chroot can't autodetect it
| |
04:56 | <vagrantc> right, that's why we should create that information at chroot build time ... ?
| |
04:56 | it might need to get updated when relocating the chroot
| |
04:56 | <alkisg> Ah, sure, yes ltsp-build-client will at least know the EXPORT_NAME which is the most important part
| |
04:57 | <vagrantc> if possible, it saves having to re-run some code.
| |
04:57 | and ltsp-update-image should know that too
| |
04:57 | ltsp-update-image --export=/ ?
| |
04:58 | <alkisg> I think that those shouldn't be allowed to be provided as parameters to ltsp-update-image/kernels, but only inside the configuration files (or in the environment)
| |
04:58 | Otherwise ltsp-update-image just takes those and passes them to ltsp-update-kernels without doing anything with them,
| |
04:59 | and it also gets complicated with the big cmdlines that have embedded '$' etc
| |
04:59 | <vagrantc> sure does...
| |
04:59 | might need to use templating instead of $
| |
04:59 | <alkisg> CMDLINE can be defined in $CHROOT/etc/ltsp/update-kernels.conf, period, no parameters :)
| |
04:59 | <vagrantc> some other replaceable value
| |
04:59 | <cyberorg> alkisg, you can go ahead with whatever you are planning, we do not use any ltsp image creation scripts, that part is taken care by kiwi and kiwi-ltsp-setup script
| |
05:00 | <alkisg> cyberorg: ok, ty
| |
05:01 | vagrantc: if we use eval, we have a bit more flexibility, for the case where one wants ${VAR+:other value}, dunno if that is needed anywhere though
| |
05:01 | <vagrantc> alkisg: so the big difference you're proposing is instead of having the defaults shipped in the script, they're actuaally written to a file, which allows the server-side scripts to read that file when needed... ?
| |
05:01 | <alkisg> E.g. we wouldn't want ip=dhcp when IPAPPEND=3 is defined, right?
| |
05:02 | <vagrantc> right
| |
05:02 | <alkisg> vagrantc: yes, they're written to a file, and that file always exists, so that the server can work with chroots of different versions or distros. And they also contain embedded variables for easier evaluation
| |
05:03 | So it would be a conffile or a postist-generated file
| |
05:03 | Not built by ltsp-build-client or so
| |
05:03 | (as e.g. one might not use ltsp-build-client at all)
| |
05:03 | <vagrantc> if people are *likely* to need to edit it, it should be generated... if the defaults will likely work in most cases, we should go with a conffile.
| |
05:04 | <alkisg> I think it should be a conffile
| |
05:04 | <vagrantc> alkisg: what about an arbitrary number of types ... rather than NFS_CMDLINE have a CMDLINE_0 ... CMDLINE_9
| |
05:05 | alkisg: and could we have a update-kernels.conf.d ?
| |
05:05 | <alkisg> vagrantc: the server decides between NBD or NFS based on what it sees when ltsp-update-kernels runs
| |
05:05 | With arbitrary CMDLINEs, we'd need a way to autodetect which of them are valid or not
| |
05:05 | <vagrantc> alkisg: but i might have 3 different NBD variants
| |
05:05 | <alkisg> For the same chroot?
| |
05:05 | <vagrantc> it's possible.
| |
05:06 | i tested using ext2 squashfs with bindmounts and with aufs overlays for a while.
| |
05:06 | same NBD image, different commandlines
| |
05:06 | (i know bindmounts are all but gone, but the example is feasible...)
| |
05:08 | <alkisg> In general the problem is to see when those CMDLINES are valid (e.g. you don't want NBD cmdlines on debian if the user never ran ltsp-update-image), so it can't support arbitrary types
| |
05:08 | highvolt1ge has joined IRC (highvolt1ge!~highvolta@modemcable104.153-23-96.mc.videotron.ca) | |
05:08 | <alkisg> We can have any number of them, sure, if there's need for it, NBD_CMDLINE_0, NFS_CMDLINE_9...
| |
05:09 | <vagrantc> ISCSI ? AOE ?
| |
05:09 | how will we grow?
| |
05:09 | alkisg: what about a dir with differnt files for different types ...
| |
05:10 | <alkisg> Suppose the new ltsp-update-kernels will have AOE support, then it will check the chroot's /etc/ltsp/update-kernels.conf for AOE_CMDLINE. If it's not there, the chroot doesn't support it, so it doesn't include the AOE in pxelinux.cfg/default
| |
05:10 | highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Read error: Connection reset by peer) | |
05:11 | <alkisg> So each new method needs both chroot support (initrd scripts, kernel cmdline) and server-side support (check if the server supports AOE or not)
| |
05:11 | <vagrantc> that could be the first part of an arbitrary CMDLINE argument ... i.e. CMDLINE_0="NBD: ..."
| |
05:11 | <alkisg> We could have "USER_PROVIDED_CMDLINE_x" for cases like the one you mentioned with you testing
| |
05:12 | And those would be generated unconditionally, without the server checking if they're supported or not
| |
05:13 | <vagrantc> if we're going with a conffile, i think we'll want a conf.d dir
| |
05:13 | maybe these are such corner cases ...
| |
05:13 | highvolt1ge has left IRC (highvolt1ge!~highvolta@modemcable104.153-23-96.mc.videotron.ca, Ping timeout: 248 seconds) | |
05:14 | highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage) | |
05:15 | <vagrantc> alkisg: so, it seems at least for debian/ubuntu that the different methods will share pieces ... COMMON_OPTS="init=/sbin/init-ltsp ro" ?
| |
05:15 | <alkisg> vagrantc: why? It's just a line, each distro should ship all of it
| |
05:16 | NBD_CMDLINE='ro initrd=$INITRD root=/dev/nbd0 init=/sbin/init-ltsp nbdroot=$SERVER:$PORT$NBD_NAME quiet splash vt_handoff=7 etc'
| |
05:17 | That vt_handoff part wasn't there in previous versions, and maybe it won't be there in the future either... so ltsp in precise should ship just that, unrelated to any debian parameters or even to other ubuntu version parameters
| |
05:18 | <vagrantc> overall, sounds fine, though i'm suspicious of the included $SERVER:$PORT$NBDNAME business
| |
05:18 | <alkisg> SERVER and PORT are empty by default
| |
05:18 | The user only needs to specify them on custom installations
| |
05:18 | s/NBD_NAME/EXPORT/
| |
05:18 | <vagrantc> and that's specified server-side?
| |
05:19 | <alkisg> Yes, in /etc/ltsp/ltsp-update-kernels.conf (not provided by default)
| |
05:19 | <vagrantc> to get the variables to register, it'll have to eval it?
| |
05:20 | <alkisg> Yes. We source the configuration files anyway so there's no security change there
| |
05:20 | (we don't parse configuration files, we source them)
| |
05:20 | (and they're in /etc already, so...)
| |
05:20 | ===> err no, we don't _have_ to eval it, but I think it'd be better, to provide for more complicated cases we haven't yet thought of
| |
05:21 | Like e.g. "don't include ip=dhcp if IPAPPEND is defined"
| |
05:21 | Btw, isn't ip=dhcp the default? Why include it?
| |
05:21 | <vagrantc> i might be the default, yes.
| |
05:22 | root=/dev/nfs is no longer really needed either
| |
05:22 | boot=nfs takes care of both of those, i thinkk.
| |
05:22 | <alkisg> Cool
| |
05:23 | My other thought was for ltsp-update-kernels to try to parse the chroot's pxelinux.cfg/default, and only replace the bits it knows
| |
05:23 | Like, nbdroot=
| |
05:23 | nbdport=, etc
| |
05:23 | But that way it can't automatically add support for NFS/NBD etc
| |
05:23 | <vagrantc> right
| |
05:23 | <alkisg> Hmmm
| |
05:23 | Here's another thought
| |
05:24 | What if we didn't try to do NFS/NBD detection, and left that up to the sysadmin, i.e.:
| |
05:24 | Debian would ship $chroot/etc/ltsp/update-kernels.conf with:
| |
05:24 | #NBD_CMDLINE=xxx (commented out)
| |
05:24 | NFS_CMDLINE=xxx
| |
05:24 | And Ubuntu with the opposite
| |
05:25 | Meh no, that's a server option, not a chroot option :(
| |
05:25 | <vagrantc> right
| |
05:25 | <alkisg> (enabling nbd or not)
| |
05:26 | <vagrantc> at this point, chroots should essentially support both, as long as the NBD image was there.
| |
05:26 | i might just have to sleep on it a bit
| |
05:27 | * vagrantc yawns | |
05:27 | <alkisg> OK
| |
05:27 | I'll try to do unrelated parts of the code for now :)
| |
05:27 | <vagrantc> i mean, you could run with what you've got, too.
| |
05:28 | <alkisg> So I can assume that Nxx_CMDLINE exist in the chroot/etc/ltsp/update-kernels.conf, otherwise ltsp-update-kernels will die with "I don't know how to handle this chroot?"
| |
05:29 | <vagrantc> wouldn't you be able to just have an include line for the generated pxelinux.cfg/default ?
| |
05:29 | <alkisg> No, because it requires variables from the server side
| |
05:30 | <vagrantc> i.e. /srv/tftp/pxelinux.cfg/default has a sub-menu for each /srv/tftp/*/pxelinux.cfg/default ?
| |
05:30 | <alkisg> The "just include this line in the menu" part isn't related to ltsp-update-kernels, but to the pxelinux menus package
| |
05:30 | <vagrantc> debian's default doesn't require any variables- it's usually passed via dhcp.
| |
05:30 | <alkisg> Ubuntu's too
| |
05:31 | shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com) | |
05:31 | <alkisg> But the line needs to be there (a) for the sysadmin to be able to easily modify it, (b) for the chroot to declare "yes I support nbd booting", etc etc
| |
05:31 | <vagrantc> so what would ltsp-update-kernels do if not generate a pxelinux config?
| |
05:32 | <alkisg> It would generate a single pxelinux.cfg just for the specific ltsp chroot
| |
05:32 | <vagrantc> so replacing the functionality of the old-style client-side update-kernels ?
| |
05:32 | <alkisg> It doesn't need support for e.g. a localboot option there
| |
05:34 | The pxelinux.cfg/default generation code would be in ltsp-update-kernels for sure, but it can also be in update-kernels too (shared from some function) if there's need for it
| |
05:35 | <vagrantc> it's hard to think about this without thinking about the pxemenus integration
| |
05:37 | alkisg: if we used a .d infrastructure for it, it would be easier to integrate the /var/lib/ltsp/update-kernels.conf in one visible structure.
| |
05:37 | <alkisg> For me, pxelinux-menus just gathers all pxelinux.inc files in /var/lib/tftpboot, and sets a default, nothing more, it doesn't get involved with specific cmdlines etc
| |
05:38 | <vagrantc> ah, so other things will have to generate pxelinux.inc files...
| |
05:38 | <alkisg> Or ship /etc/pxelinux.d/scripts instead
| |
05:38 | (08:37:28 πμ) vagrantc: alkisg: if we used a .d infrastructure for it, it would be easier to integrate the /var/lib/ltsp/update-kernels.conf in one visible structure. ==> I didn't get that one
| |
05:39 | That would be written by the server ltsp-update-kernels, and would contain EXPORT=xx, SERVER=xx, PORT=xx, if they're defined server-side by the sysadmin
| |
05:40 | <vagrantc> alkisg: so instead of /var/lib/ltspp/update-kernels.conf and /etc/ltsp/update-kernels.conf, we could have /etc/ltsp/update-kernels.conf.d/00-server-vars.conf (and nbd.conf, nfs.conf, etc.)
| |
05:41 | <alkisg> ltsp-update-kernels would write and update files in /etc every time it runs? Isn't that against the policy or something?
| |
05:42 | <vagrantc> maybe a bad idea, yes.
| |
05:42 | <alkisg> ltsp-update-kernels "caches" the last server info it knows about in $chroot/var, but only the sysadmin should write specific info in $chroot/etc imho
| |
05:42 | <vagrantc> makes sense.
| |
05:42 | <alkisg> So /etc/ would always take precedence over /var/
| |
05:44 | ...maybe I should postpone all that part for when we start the pxelinux menu package :)
| |
05:45 | ...and minimize changes in ltsp-update-kernels/update-kernels for now
| |
05:48 | komunista has joined IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk) | |
05:54 | <alkisg> Sysadmins don't currently have an easy way to permanately change the cmdline though, editing /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default is only temporary
| |
06:04 | * alkisg thinks he'll postpone most of it for the pxelinux menus package, minimize changes and keep things simple for now | |
06:11 | bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 260 seconds) | |
06:20 | <alkisg> So in Ubuntu, by setting rootpath=":ltsp_i386", we can omit "nbdroot=:ltsp_i386" from the command line, thus making the chroot option updating unnecessary for the default case not involving pxe menus
| |
06:22 | vagrantc: $ head -n1 /etc/nbd-server/conf.d/ltsp_i386.conf
| |
06:22 | [ltsp_i386]
| |
06:22 | ==> if that there was [/opt/ltsp/i386] instead, we wouldn't have to change the dhcp rootpath when we switch from nfs to nbd, and we wouldn't need to ship a different dnsmasq-ltsp.conf configuration file for nbd either (for option root-path)
| |
06:39 | Parker955 is now known as Parker955_Away | |
06:41 | stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, *.net *.split) | |
06:41 | shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com, *.net *.split) | |
06:41 | wafflecone has left IRC (wafflecone!~caliel@70.150.196.98, *.net *.split) | |
06:41 | [GuS] has left IRC ([GuS]!~gustavo@unaffiliated/gus/x-663402, *.net *.split) | |
06:41 | monteslu has left IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net, *.net *.split) | |
06:41 | mnemoc has left IRC (mnemoc!~amery@shell.opensde.net, *.net *.split) | |
06:41 | Hyperbyte has left IRC (Hyperbyte!jan@middelkoop.cc, *.net *.split) | |
06:41 | highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, *.net *.split) | |
06:41 | mgariepy has left IRC (mgariepy!mgariepy@ubuntu/member/mgariepy, *.net *.split) | |
06:41 | JesseC has left IRC (JesseC!JesseCW@wsip-98-175-20-126.br.br.cox.net, *.net *.split) | |
06:41 | TatankaT has left IRC (TatankaT!~tim@peno.cwlab.kotnet.org, *.net *.split) | |
06:41 | spectra has left IRC (spectra!~spectra@debian/developer/spectra, *.net *.split) | |
06:41 | sideffect has left IRC (sideffect!sideffect@gateway/shell/bshellz.net/x-mwvmfmqjclwlohml, *.net *.split) | |
06:41 | slackish has left IRC (slackish!amcphall@mcphall.org, *.net *.split) | |
06:41 | Mava has left IRC (Mava!~Mava@ip-45-224.dhcp.opintanner.fi, *.net *.split) | |
06:41 | sutula has left IRC (sutula!sutula@nat/hp/x-rxmgbatzxkgbynte, *.net *.split) | |
06:41 | sep has left IRC (sep!~sep@40.211.jostedal.no, *.net *.split) | |
06:41 | cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, *.net *.split) | |
06:41 | gentgeen__ has left IRC (gentgeen__!~kevin@c-98-236-71-64.hsd1.pa.comcast.net, *.net *.split) | |
06:41 | awilliams has left IRC (awilliams!mistik1@unaffiliated/mistik1, *.net *.split) | |
06:41 | wcchandler has left IRC (wcchandler!wcchandler@pilot.trilug.org, *.net *.split) | |
06:41 | yanu has left IRC (yanu!~yanu@lugwv/member/yanu, *.net *.split) | |
06:41 | SmallR2002 has left IRC (SmallR2002!~quassel@c-98-253-173-240.hsd1.il.comcast.net, *.net *.split) | |
06:41 | eddytv has left IRC (eddytv!~anonymous@slashdev.com, *.net *.split) | |
06:41 | leio has left IRC (leio!~leio@gentoo/developer/leio, *.net *.split) | |
06:41 | enyc has left IRC (enyc!~enyc@muddle.enyc.org.uk, *.net *.split) | |
06:41 | knipwim has left IRC (knipwim!~wim@ip4da83870.direct-adsl.nl, *.net *.split) | |
06:41 | Patina has left IRC (Patina!~tomas@1385158770.dhcp.dbnet.dk, *.net *.split) | |
06:41 | Lumiere has left IRC (Lumiere!~jstraw@unaffiliated/jstraw, *.net *.split) | |
06:41 | alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, *.net *.split) | |
06:41 | joat has left IRC (joat!~freenode@ip70-160-216-251.hr.hr.cox.net, *.net *.split) | |
06:41 | risca has left IRC (risca!~risca@wnpgmb0903w-ds01-249-233.dynamic.mtsallstream.net, *.net *.split) | |
06:41 | Llama_be_ has left IRC (Llama_be_!~tom@94-226-90-169.access.telenet.be, *.net *.split) | |
06:41 | dberkholz has left IRC (dberkholz!user23920@gentoo/developer/dberkholz, *.net *.split) | |
06:41 | ||cw has left IRC (||cw!~chris@phpgroupware/cw, *.net *.split) | |
06:41 | mmetzger has left IRC (mmetzger!~mmetzger@99-71-214-196.lightspeed.mdldtx.sbcglobal.net, *.net *.split) | |
06:41 | zamba has left IRC (zamba!marius@flage.org, *.net *.split) | |
06:41 | Kevin` has left IRC (Kevin`!~kevin@router.kwzs.be, *.net *.split) | |
06:41 | zevlag has left IRC (zevlag!~zevlag@intranetgateway.etv.net, *.net *.split) | |
06:41 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, *.net *.split) | |
06:41 | vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, *.net *.split) | |
06:41 | NeonLicht has left IRC (NeonLicht!~NeonLicht@darwin.ugr.es, *.net *.split) | |
06:41 | komunista has left IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk, *.net *.split) | |
06:41 | loather has left IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net, *.net *.split) | |
06:41 | F-GT has left IRC (F-GT!~phantom@ppp121-44-125-132.lns20.syd6.internode.on.net, *.net *.split) | |
06:41 | DIoX|DaZ has left IRC (DIoX|DaZ!~KaKa@server.civicclub.lt, *.net *.split) | |
06:41 | shawnp0wers has left IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers, *.net *.split) | |
06:41 | muppis has left IRC (muppis!muppis@viuhka.fi, *.net *.split) | |
06:41 | shamino has left IRC (shamino!shamino@hilla.kapsi.fi, *.net *.split) | |
06:41 | LoveStorm has left IRC (LoveStorm!Storm@gateway/shell/trekweb.org/x-ndicnndczcvfmuho, *.net *.split) | |
06:41 | Parker955_Away has left IRC (Parker955_Away!~parker@74.112.203.151, *.net *.split) | |
06:41 | primeministerp has left IRC (primeministerp!~ppouliot@static-71-174-244-28.bstnma.fios.verizon.net, *.net *.split) | |
06:41 | andygraybeal has left IRC (andygraybeal!~andy.gray@obsidian.casanueva.com, *.net *.split) | |
08:11 | ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz) | |
08:11 | komunista has joined IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk) | |
08:11 | shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com) | |
08:11 | highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage) | |
08:11 | loather has joined IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net) | |
08:11 | [GuS] has joined IRC ([GuS]!~gustavo@unaffiliated/gus/x-663402) | |
08:11 | SmallR2002 has joined IRC (SmallR2002!~quassel@c-98-253-173-240.hsd1.il.comcast.net) | |
08:11 | eddytv has joined IRC (eddytv!~anonymous@slashdev.com) | |
08:11 | stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber) | |
08:11 | monteslu has joined IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net) | |
08:11 | F-GT has joined IRC (F-GT!~phantom@ppp121-44-125-132.lns20.syd6.internode.on.net) | |
08:11 | LoveStorm has joined IRC (LoveStorm!Storm@gateway/shell/trekweb.org/x-ndicnndczcvfmuho) | |
08:11 | leio has joined IRC (leio!~leio@gentoo/developer/leio) | |
08:11 | DIoX|DaZ has joined IRC (DIoX|DaZ!~KaKa@server.civicclub.lt) | |
08:11 | cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg) | |
08:11 | enyc has joined IRC (enyc!~enyc@muddle.enyc.org.uk) | |
08:11 | awilliams has joined IRC (awilliams!mistik1@unaffiliated/mistik1) | |
08:11 | mgariepy has joined IRC (mgariepy!mgariepy@ubuntu/member/mgariepy) | |
08:11 | gentgeen__ has joined IRC (gentgeen__!~kevin@c-98-236-71-64.hsd1.pa.comcast.net) | |
08:11 | Parker955_Away has joined IRC (Parker955_Away!~parker@74.112.203.151) | |
08:11 | primeministerp has joined IRC (primeministerp!~ppouliot@static-71-174-244-28.bstnma.fios.verizon.net) | |
08:11 | JesseC has joined IRC (JesseC!JesseCW@wsip-98-175-20-126.br.br.cox.net) | |
08:11 | wafflecone has joined IRC (wafflecone!~caliel@70.150.196.98) | |
08:11 | andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com) | |
08:11 | TatankaT has joined IRC (TatankaT!~tim@peno.cwlab.kotnet.org) | |
08:11 | sutula has joined IRC (sutula!sutula@nat/hp/x-rxmgbatzxkgbynte) | |
08:11 | ||cw has joined IRC (||cw!~chris@phpgroupware/cw) | |
08:11 | shawnp0wers has joined IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers) | |
08:11 | knipwim has joined IRC (knipwim!~wim@ip4da83870.direct-adsl.nl) | |
08:11 | Llama_be_ has joined IRC (Llama_be_!~tom@94-226-90-169.access.telenet.be) | |
08:11 | muppis has joined IRC (muppis!muppis@viuhka.fi) | |
08:11 | sep has joined IRC (sep!~sep@40.211.jostedal.no) | |
08:11 | spectra has joined IRC (spectra!~spectra@debian/developer/spectra) | |
08:11 | mnemoc has joined IRC (mnemoc!~amery@shell.opensde.net) | |
08:11 | Patina has joined IRC (Patina!~tomas@1385158770.dhcp.dbnet.dk) | |
08:11 | Kevin` has joined IRC (Kevin`!~kevin@router.kwzs.be) | |
08:11 | zamba has joined IRC (zamba!marius@flage.org) | |
08:11 | mmetzger has joined IRC (mmetzger!~mmetzger@99-71-214-196.lightspeed.mdldtx.sbcglobal.net) | |
08:11 | yanu has joined IRC (yanu!~yanu@lugwv/member/yanu) | |
08:11 | Hyperbyte has joined IRC (Hyperbyte!jan@middelkoop.cc) | |
08:11 | Mava has joined IRC (Mava!~Mava@ip-45-224.dhcp.opintanner.fi) | |
08:11 | slackish has joined IRC (slackish!amcphall@mcphall.org) | |
08:11 | dberkholz has joined IRC (dberkholz!user23920@gentoo/developer/dberkholz) | |
08:11 | joat has joined IRC (joat!~freenode@ip70-160-216-251.hr.hr.cox.net) | |
08:11 | wcchandler has joined IRC (wcchandler!wcchandler@pilot.trilug.org) | |
08:11 | alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47) | |
08:11 | Lumiere has joined IRC (Lumiere!~jstraw@unaffiliated/jstraw) | |
08:11 | sideffect has joined IRC (sideffect!sideffect@gateway/shell/bshellz.net/x-mwvmfmqjclwlohml) | |
08:11 | zevlag has joined IRC (zevlag!~zevlag@intranetgateway.etv.net) | |
08:11 | NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es) | |
08:11 | shamino has joined IRC (shamino!shamino@hilla.kapsi.fi) | |
08:21 | bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) | |
08:22 | ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) | |
08:40 | komunista has left IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk, Quit: Leaving.) | |
08:46 | komunista has joined IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk) | |
09:21 | ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz) | |
09:35 | bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 244 seconds) | |
09:53 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
10:07 | <knipwim> alkisg: i think i've come to a good server config distinction:
| |
10:07 | /server/configs contains ltsp specific configs for in /etc/ltsp, distro specific ones in /server/configs/$DISTRO
| |
10:08 | /server/docs/examples contains other tool configs, also with a /server/docs/examples/$DISTRO
| |
10:08 | alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg) | |
10:09 | <knipwim> we can also move /server/configs to /server/etc, /server/etc.Ubuntu etc
| |
10:09 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Read error: Operation timed out) | |
10:10 | <knipwim> alkisg1: did you catch my last 4 lines?
| |
10:10 | <alkisg1> knipwim: nope, let me see the logs...
| |
10:10 | alkisg1 is now known as alkisg | |
10:13 | <knipwim> btw, i'd rather have subdirs for distro's in /client/share
| |
10:13 | <alkisg> knipwim: I think we should unity the trunk layout to use the same scheme for all dirs. E.g. now we have init-ltsp.d/common and init-ltsp.d/distro, it would be the same in etc/, however we'd do it
| |
10:14 | client/share and client/share.distro? etc and etc.distro? they should be similar though
| |
10:14 | But I don't think that we'll have many common etc/ files, so unless we do find some, we could put them in examples/ till then
| |
10:14 | <knipwim> sure, but we still get a lot of dirs in the tree
| |
10:14 | in /client and /server
| |
10:15 | <alkisg> For share/, we only need one, so that will cover init-ltsp.d too
| |
10:15 | E.g. share/init-ltsp.d (common scripts there) and share/init-ltsp.d.Ubuntu
| |
10:15 | Sorry
| |
10:15 | share.Ubuntu/init-ltsp.d
| |
10:16 | So we'd only have different distro dirs for share, not for subfolders
| |
10:17 | But for /etc I don't know... e.g. if an ubuntu user wants to use xinetd, he could just use the example provided by fedora or gentoo
| |
10:17 | <knipwim> i think i would rather see /share/common/init-ltsp.d and /share/Ubuntu/init-ltsp.d
| |
10:17 | <alkisg> And even in Ubuntu, ltsp-server-standalone would use different etc/ files than ltsp-server-dnsmasq
| |
10:17 | OK, sure, no problem there
| |
10:17 | psybi has joined IRC (psybi!546a3508@gateway/web/freenode/ip.84.106.53.8) | |
10:18 | <alkisg> So for configuration files I'm not sure how much sense it has. Maybe an examples/common dir, and examples/distro dirs?
| |
10:18 | And packages can reuse the examples provided there
| |
10:18 | Currently ltsp-server in Ubuntu ships: /etc/X11/Xsession.d/80_ltsp-sound /etc/network/if-up.d/ltsp-keys ==> and the second one is not even needeed anymore
| |
10:19 | <knipwim> you're probably right on configuration files not being shared throughout distro's
| |
10:19 | doc/examples/$tool would be better
| |
10:19 | <alkisg> ltsp-client-core ships more: /etc/init/ltsp-client-core.conf /etc/kernel/postrm.d /etc/kernel/postinst.d /etc/init.d/ltsp-client-core /etc/kernel/postrm.d/ltsp-update-kernels /etc/kernel/postinst.d/ltsp-update-kernels
| |
10:20 | <knipwim> like doc/examples/xinetd.d/nbdswapd and doc/examples/dnsmasq/dnsmasq.conf
| |
10:20 | <alkisg> Right, as long as they're not completely distro-specific, when they'd go under examples/distro instead
| |
10:21 | To simplify packaging, maybe the $tool/ folder can be omitted
| |
10:21 | So as to copy everything under examples/common and everything under examples/$distro
| |
10:21 | <knipwim> packagers wouldn't select all examples, just pick to appropriate ones
| |
10:21 | <alkisg> Why not all common/ and $distro/ examples?
| |
10:22 | (with symlinks where appropriate)
| |
10:22 | <knipwim> perhaps some distro's share the same tools
| |
10:22 | like gentoo and fedora could share dracut configs
| |
10:22 | <alkisg> Derivatives like ubuntu can copy common/, debian/ and ubuntu/
| |
10:22 | Similar distros can use symlinks
| |
10:23 | <knipwim> hehe, again the symlinks
| |
10:23 | <alkisg> (same would be for /usr/share/ltsp, the share/ trunk folder)
| |
10:23 | There would only be a few symlinks in this case though
| |
10:24 | <knipwim> ok, sound like plan then, doc/examples/common and doc/examples/$distro
| |
10:25 | <alkisg> I'm no packager though, vagrantc is probably a better person to talk about this
| |
10:25 | <knipwim> now figure out who uses what
| |
10:25 | <alkisg> Yeah, that would be solved with symlinks
| |
10:25 | Now one would have to look at each distro packaging to see if it uses it
| |
10:26 | <knipwim> i could do that for debian and ubuntu
| |
10:26 | but i've no idea about suse or fedora
| |
10:26 | <alkisg> No complains at all from me :)
| |
10:27 | <knipwim> or even if altlinux is using the latest upstream code
| |
10:27 | <alkisg> Maybe a mail in the ltsp-developers list is good enough to get feedback, if no feedback comes then we're good to go :)
| |
10:28 | We could have dirs for bin and sbin too
| |
10:31 | <knipwim> hmm, an sbin just for init-ltsp?
| |
10:31 | seems overkill
| |
10:31 | <alkisg> /usr/sbin/inventory
| |
10:31 | /usr/sbin/jetpipe
| |
10:31 | /usr/sbin/ltsp-remoteappsd
| |
10:31 | /usr/sbin/nbd-client-proxy
| |
10:31 | /usr/sbin/nbd-proxy
| |
10:32 | <knipwim> ah, usr sbin :)
| |
10:33 | <alkisg> Maybe it would be better to assume that ltsp-trunk/client/ means <common>, so it would have a share/ subdir etc, and ltsp-trunk/client/$distro/ follows the exact same structure, overriding ltsp-trunk/client/
| |
10:33 | So the Ubuntu packaging for share/* would be:
| |
10:33 | client/share/*
| |
10:33 | client/Debian/share/*
| |
10:33 | client/Ubuntu/share/*
| |
10:34 | psybi has left IRC (psybi!546a3508@gateway/web/freenode/ip.84.106.53.8, Ping timeout: 245 seconds) | |
10:35 | <alkisg> Or maybe even the distro dirs could be in ltsp-trunk/distro, and have client/ and server/ etc subdirs. Anyway my point is that it might be better to only have 1 distro specific dir per distro.
| |
10:35 | We'd easily know who maintains what then
| |
10:35 | And it'd probably be much easier for packaging
| |
10:37 | <knipwim> agreed
| |
10:37 | but then i like the client/share/* client/Debian/share/* option best
| |
10:37 | ideally, everything in client should be common
| |
10:38 | so we can do client/k12linux/templates and client/k12linux/scripts
| |
10:38 | <alkisg> client/template/k12linux/ => client/k21linux/template/, hehe that's what I was writing :D
| |
10:38 | ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Ping timeout: 260 seconds) | |
10:39 | <knipwim> great minds ... :)
| |
10:40 | <alkisg> The dirs other than server/ and client/ don't seem to have much distro-specific code
| |
10:40 | So yeah, server/$distro and client/$distro dirs sound good
| |
10:41 | And other than those, server/* and client/* would be considered "common"
| |
10:41 | <knipwim> shall i reply to your topic in the mailinglist
| |
10:41 | with a summary of this discussion
| |
10:41 | <alkisg> Yup
| |
10:42 | You could even write it to the wiki first
| |
10:42 | <knipwim> and wait a week or so before implementing it
| |
10:42 | <alkisg> And mail the link
| |
10:42 | <knipwim> good idea
| |
10:42 | <alkisg> That way we can update the proposal when needed or when we have new ideas
| |
10:46 | http://wiki/source-layout (or SourceLayout) might be OK for the URL. We could even put that as a text file in trunk...
| |
10:48 | ltsp-trunk/server/doc/CodingStyle => similar to what we're saying now, those docs should be in common/* instead, as they're valid for both server and client
| |
10:48 | Trixboxer has joined IRC (Trixboxer!~Trixboxer@115.124.115.71) | |
11:36 | garymc has joined IRC (garymc!~chatzilla@host81-148-105-13.in-addr.btopenworld.com) | |
12:21 | <Hyperbyte> Hey Gary!
| |
12:29 | Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas) | |
12:35 | <knipwim> alkisg: i would want a doc/examples/tools/xinetd.d/nbdwapd and a symlink to doc/examples/Gentoo/xinetd.d/nbdwapd for instance
| |
12:35 | to have a better distinction of total available tools and distro supporting them
| |
12:35 | erm
| |
12:36 | symlink to /server/Gentoo/doc/examples/xinetd.d/nbdswapd
| |
12:36 | the doc/examples/tools is common code
| |
12:57 | adrianorg has joined IRC (adrianorg!~adrianorg@187.115.104.79) | |
13:34 | garymc has left IRC (garymc!~chatzilla@host81-148-105-13.in-addr.btopenworld.com, Ping timeout: 244 seconds) | |
13:34 | garymc has joined IRC (garymc!~chatzilla@host81-139-153-20.in-addr.btopenworld.com) | |
14:05 | mikkel has joined IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk) | |
14:12 | adrianorg has left IRC (adrianorg!~adrianorg@187.115.104.79, Ping timeout: 265 seconds) | |
14:14 | Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Read error: Operation timed out) | |
14:22 | komunista has left IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk, Quit: Leaving.) | |
14:24 | alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg) | |
14:24 | <alkisg1> (03:35:43 μμ) knipwim: to have a better distinction of total available tools and distro supporting them => my thought is, if it's common, it's supported everywhere, otherwise it should be in a distro dir
| |
14:24 | (in) common
| |
14:26 | xinetd runs on ubuntu too, it works with ltsp if someone manually configures it
| |
14:26 | The defaults that each distro ltsp packages use doesn't matter much, e.g. ltsp-server-standalone uses different tools from ltsp-server-dnsmasq on Ubuntu
| |
14:27 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 244 seconds) | |
14:28 | alkisg1 is now known as alkisg | |
14:28 | komunista has joined IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk) | |
14:28 | <alkisg> knipwim: /client/share/xinitrc.d => does this go in /usr/share/ltsp/xinitrc.d/ on Gentoo?
| |
14:29 | Meh sorry I read "xinetd.d" :P
| |
14:31 | Looks good, send the mail :)
| |
14:32 | <knipwim> nothing on the bins and sbins ?
| |
14:32 | or leave that for a later discussion :)
| |
14:32 | Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas) | |
14:34 | <alkisg> Let's make a small list of stuff that needs to be moved:
| |
14:34 | client/chroot-setup => in client/k12linux/chroot-setup
| |
14:34 | client/functions/$distro => in client/$distro/share/ltsp-client-vendor-functions
| |
14:35 | client/init-ltsp.d/$distro => client/$distro/init-ltsp.d
| |
14:35 | initramfs ==> maybe in client/debian/initramfs, if only debian/ubuntu use it?
| |
14:36 | client/initscripts/$distro => client/$distro/initscripts
| |
14:36 | client/initscripts/ltsp-core.upstart => client/ubuntu/initscripts
| |
14:36 | <knipwim> yes on the initramfs
| |
14:37 | <alkisg> client/rwtab.d => client/k12linux/rwtab.d/
| |
14:38 | client/screen.d => client/share/screen.d, and also for the others I forgot, init-ltsp.d and ltsp_config.d
| |
14:38 | And screen-session.d too
| |
14:38 | <knipwim> client/scripts/k12linux/ => client/k12linux/scripts
| |
14:38 | client/template/k12linux/ => client/k12linux/template
| |
14:38 | <alkisg> client/xinitrc.d => client/share/xinitrc.d
| |
14:39 | configure-x.sh => share/configure-x.sh
| |
14:39 | init-ltsp => sbin/init-ltsp ? TODO
| |
14:39 | kioskSession => share/kioskSession
| |
14:39 | ltsp-client-common-functions, ltsp-client-functions => client/share/
| |
14:40 | <knipwim> screen_session => share/screen_session
| |
14:40 | <alkisg> ltsp_config => lib/ltsp_config ? TODO
| |
14:40 | <knipwim> update-kernels => share/update-kernels
| |
14:40 | <alkisg> nbd-disconnect => share/nbd-disconnect
| |
14:42 | <knipwim> screen-x-common => share/screen-x-common
| |
14:42 | <alkisg> (05:40:29 μμ) alkisg: ltsp_config => lib/ltsp_config ? ==> don't know why that's also symlinked in lib, sorry, it should go in share/
| |
14:43 | Ubuntu has some symlinks in /usr/lib/ltsp, dunno why, we can probably drop them
| |
14:43 | <knipwim> i think that was the old location
| |
14:44 | there are a couple of scripts also loooking in /usr/lib/ltsp, for backward compatability
| |
14:45 | <alkisg> bin/ makes no sense, the binaries that go there are all over the place
| |
14:45 | So I withdraw my proposal about it :)
| |
14:46 | We may put init-ltsp to scripts/ if we want
| |
14:46 | Or leave it as is
| |
14:46 | <knipwim> and jetpipe and getltscfg
| |
14:49 | <alkisg> Why aren't localapps in client/ ?
| |
14:49 | And nbd-proxy in client/Ubuntu/nbd-proxy
| |
14:51 | I think the best way to represent all that is... to clone the branch and do the renames and make a merge request
| |
14:51 | One can navigate to see the final structure, and there's no overhead for us to write the same things twice when the branch is merged, it's just 1 command
| |
14:52 | And one can look at the diff for the moves
| |
14:52 | * knipwim likes | |
14:53 | <knipwim> and i can do this
| |
14:53 | <alkisg> Cool
| |
14:54 | vagrantc mentioned that he liked the shared/ idea, so extending it wouldn't make him object, I presume
| |
14:55 | <knipwim> shall i do the client/localapps and client/Ubuntu/nbd-proxy as well
| |
14:55 | ?
| |
14:55 | <alkisg> I'd vote yes
| |
14:56 | <knipwim> hehe :)
| |
15:13 | komunista has left IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk, Quit: Leaving.) | |
15:18 | komunista has joined IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk) | |
15:28 | <knipwim> alkisg: is ltsp-core.upstart only for ubuntu? or can i put it in the debian dir
| |
15:28 | same for nbdproxy
| |
15:29 | <alkisg> knipwim: http://packages.debian.org/sid/i386/ltsp-client-core/filelist
| |
15:29 | Not there
| |
15:31 | (vs http://packages.ubuntu.com/quantal/i386/ltsp-client-core/filelist ==> /etc/init/ltsp-client-core.conf)
| |
15:31 | nbd-proxy is in debian, so I'd put it in Debian/, yeah
| |
15:41 | vagrantc has joined IRC (vagrantc!~vagrant@c-76-115-60-19.hsd1.or.comcast.net) | |
15:41 | vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc) | |
15:52 | <knipwim> alkisg vagrantc : https://code.launchpad.net/~wimmuskee/ltsp/ltsp-restructure-the-tree
| |
15:52 | vagrantc: alkisg and i just discussed these changes
| |
15:59 | <vagrantc> knipwim: so the idea is that share goes into /usr/share/ltsp, basically?
| |
15:59 | (and other dirs go similarly)
| |
15:59 | might bee worth making upstream makefiles
| |
16:01 | loather has left IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net) | |
16:02 | Parker955_Away is now known as Parker955 | |
16:05 | <vagrantc> knipwim: no real objection.
| |
16:06 | i presume that's only the beginning?
| |
16:08 | mikkel has left IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk, Quit: Leaving) | |
16:09 | vmlintu__ has joined IRC (vmlintu__!~vmlintu@nblzone-240-143.nblnetworks.fi) | |
16:10 | <alkisg> Is anyone still using ltsp-bindmounts? Gentoo?
| |
16:11 | Thanks knipwim looks good to me
| |
16:13 | vagrantc: I guess the server/ dir also needs some restructuring
| |
16:14 | But other than that, that's pretty much it... afaik
| |
16:16 | <vagrantc> we've made so many changes that assume a writeable /, i wonder if it would even be feasible to try ltsp-bindmounts
| |
16:17 | i think i don't even ship it in debian's packages anymore
| |
16:18 | oh, i guess i do ship it
| |
16:19 | <alkisg> I think gentoo's still using it...
| |
16:20 | <vagrantc> knipwim: i'd go ahead and merge your branch changes in
| |
16:20 | <alkisg> I think we should wait for the server/ dir too
| |
16:20 | E.g. /server/doc/CodingStyle goes in common/ or in common/docs
| |
16:21 | And functions/$distro in $distro/share/*
| |
16:23 | <vagrantc> that's what i meant when i said i presumed there were more changes
| |
16:24 | <alkisg> Yeah we only discussed the client/ dir so far, but the server/ dir needs similar changes
| |
16:24 | config/$distro => $distro/config
| |
16:25 | plugins => share/plugins
| |
16:25 | scripts/$distro => $distro/scripts
| |
16:28 | <vagrantc> will this be ltsp 5.4.x? :)
| |
16:28 | not really code changes, but patches for 5.3.x aren't going to apply anymore
| |
16:29 | * vagrantc finds the ltsp-*-common symlinks to be silly | |
16:30 | <alkisg> An ltsp-common package would solve that problem, but it sounds like overkill...
| |
16:30 | adrianorg has joined IRC (adrianorg!~adrianorg@187.115.104.79) | |
16:30 | * vagrantc would also like to find an excuse to put ltsp-localapps into it's own package | |
16:30 | <alkisg> Does the code work without that? Don't other parts rely on localapps?
| |
16:30 | Parker955 is now known as Parker955_Away | |
16:31 | <vagrantc> i frequently have application servers that do not have LTSP installed.
| |
16:31 | i.e. ldm-server is installed, ltsp-server is not.
| |
16:31 | localapps still work fine- it's just a call to xprop ... it's mostly handledn client side
| |
16:32 | <alkisg> X99-ltsp-logout-action => that shouldn't be in localapps, should it?
| |
16:33 | <vagrantc> that is weird.
| |
16:34 | <alkisg> And fat clients wouldn't work with localapps disabled, due to user accounts handling...
| |
16:34 | <vagrantc> and it's my fault ...
| |
16:34 | mostly, i want the server-side localapps functionality split into a separate package ... but it might not be worth it.
| |
16:35 | probably just shunted the ldm-rc.d in there because it needed to go there, but it really probably belongs in client/share/ldm/rc.d/
| |
16:36 | <alkisg> That sounds better
| |
16:38 | <vagrantc> if upstream had a Makefile to handle the ltsp-common-functions -> ltsp-server-common-functions/ltsp-client-common-functions magic, the stupid symlinks could go away
| |
16:40 | * vagrantc suspects ltsp-trunk/TODO can go away | |
16:41 | <knipwim> alkisg: gentoo doesn't use ltsp-bindmounts
| |
16:42 | vmlintu__ has left IRC (vmlintu__!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 260 seconds) | |
16:49 | <vagrantc> probably should kill it then
| |
16:49 | * vagrantc doesn't look back | |
16:57 | vmlintu__ has joined IRC (vmlintu__!~vmlintu@nblzone-240-143.nblnetworks.fi) | |
17:05 | <alkisg> TODO can go in a wiki roadmap page
| |
17:10 | Till now, ltsp-update-image had a --options parameter, which wrote the info to $chroot/etc/ltsp/update-kernels.conf, then ran `chroot $chroot update-kernels`, which generated boot/pxelinux.cfg/default, and then it ran ltsp-update-kernels to copy that file into TFTP.
| |
17:10 | I think I'll kill that, while it's convinient to be able to do it with a single parameter, it's so messed up that noone knows how to use it
| |
17:11 | For now I think I'll go with update-kernels generating a proper config. The sysadmin will be responsible to put the info in $chroot/etc/update-kernels.conf,
| |
17:12 | garymc has left IRC (garymc!~chatzilla@host81-139-153-20.in-addr.btopenworld.com, Ping timeout: 272 seconds) | |
17:12 | <alkisg> and for the future, ltsp-server will ship a pxelinux-menus script that will check the chroot and generate appropriate sections (or include files) in the master pxelinux.cfg/default
| |
17:12 | So only small changes for now
| |
17:35 | garymc has joined IRC (garymc!~chatzilla@host81-139-153-20.in-addr.btopenworld.com) | |
17:39 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
17:44 | bieb has joined IRC (bieb!~Me@99-2-101-23.lightspeed.tukrga.sbcglobal.net) | |
17:55 | <vagrantc> hm.
| |
18:03 | knipwim: does gentoo publish versions of ltsp, ldm and ltspfs, or do users always build right from bzr?
| |
18:11 | just wondering if it'd be useful to monitor gentoo's uploaded versions for me.
| |
18:19 | bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) | |
18:48 | <knipwim> vagrantc: gentoo builds versions from bzr, based on the tags
| |
18:55 | the package files are uploaded here: http://git.overlays.gentoo.org/gitweb/?p=proj/ltsp.git;a=summary
| |
19:07 | awilliams has left IRC (awilliams!mistik1@unaffiliated/mistik1, Quit: Lost terminal) | |
19:08 | garymc has left IRC (garymc!~chatzilla@host81-139-153-20.in-addr.btopenworld.com, Ping timeout: 244 seconds) | |
19:09 | awilliams has joined IRC (awilliams!mistik1@unaffiliated/mistik1) | |
19:14 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
19:17 | <vagrantc> knipwim: ok, well, that probably won't be a useful view to poll for new versions, then. no worries.
| |
19:20 | <alkisg> knipwim: since vagrantc also agrees, I think there's no need to wait a whole week for feedback, a couple of days would be fine (so that we start the ltsp-server-dnsmasq packaging after that commit)
| |
19:23 | highvolt1ge has joined IRC (highvolt1ge!~highvolta@modemcable104.153-23-96.mc.videotron.ca) | |
19:24 | <vagrantc> knipwim: yes, go for the restructure
| |
19:24 | sooner is better, as i need to have it all sorted out by end of may
| |
19:26 | highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Read error: Connection reset by peer) | |
19:27 | <knipwim> okay, i can get some server stuff done tonight
| |
19:28 | but tomorrow is my last day being able to work on it till next weekend
| |
19:29 | so it has to be done tomorrow, or next weekend
| |
19:29 | bieb has left IRC (bieb!~Me@99-2-101-23.lightspeed.tukrga.sbcglobal.net, Quit: Leaving.) | |
19:29 | highvolt1ge has left IRC (highvolt1ge!~highvolta@modemcable104.153-23-96.mc.videotron.ca, Ping timeout: 244 seconds) | |
19:30 | highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage) | |
19:40 | Trixboxer has left IRC (Trixboxer!~Trixboxer@115.124.115.71, Quit: "Achievement is not the end, its the beginning of new journey !!!") | |
19:44 | <alkisg> knipwim: commit whatever you have tomorrow, and we can continue if there are any things left
| |
19:44 | <knipwim> kk
| |
19:44 | i'm still not fully confident the tool examples shouldn't go in a generic tool dir
| |
19:45 | what if no distro uses the tool configs anymore
| |
19:45 | couldn't they still be useful for other distro's?
| |
19:46 | <alkisg> If configuration examples are useful, they should be there in case some user needs them, not in case some distro needs them
| |
19:46 | E.g. a dnsmasq config is there now, even if no distro uses dnsmasq in its ltsp packaging
| |
19:46 | So, xinetd configuration should be in "common", even if debian and ubuntu don't use it
| |
19:59 | ddave7 has joined IRC (ddave7!~Miranda@ip-89-176-9-128.net.upcbroadband.cz) | |
19:59 | komunista has left IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk, Quit: Leaving.) | |
20:02 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
20:07 | Parker955_Away is now known as Parker955 | |
20:38 | ddave7 is now known as dsorf | |
20:53 | alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Ping timeout: 272 seconds) | |
20:54 | bieb has joined IRC (bieb!~Me@99-2-101-23.lightspeed.tukrga.sbcglobal.net) | |
21:07 | bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 250 seconds) | |
22:10 | shawnp0wers has left IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers, Read error: Operation timed out) | |
22:13 | shawnp0wers has joined IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers) | |
22:32 | bieb has left IRC (bieb!~Me@99-2-101-23.lightspeed.tukrga.sbcglobal.net, Quit: Leaving.) | |
22:38 | bieb has joined IRC (bieb!~Me@99-2-101-23.lightspeed.tukrga.sbcglobal.net) | |
22:39 | raven has joined IRC (raven!~raven@114.79.16.121) | |
23:00 | Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Ping timeout: 256 seconds) | |
23:02 | alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47) | |
23:15 | Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas) | |
23:57 | highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Ping timeout: 260 seconds) | |
23:58 | andygraybeal_ has joined IRC (andygraybeal_!~andy@h174.212.22.98.dynamic.ip.windstream.net) | |
23:59 | highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage) | |