**** BEGIN LOGGING AT Mon Jan 29 02:59:59 2007 Jan 29 03:02:19 you can flash anything onto any slug Jan 29 03:02:33 (as long as it is able to enter upgrade mode) Jan 29 06:54:10 03bzhou * r5336 10optware/trunk/make/ (libtorrent.mk rtorrent.mk): libtorrent: 0.11.1 -> 0.11.2; rtorrent: 0.7.1 -> 0.7.2 Jan 29 08:30:02 03oleo * r5337 10optware/trunk/ (make/transmission.mk sources/transmission/transmission.cgi): transmission: r1428->1445 - add checking against syslog in CGI Jan 29 08:35:44 03oleo * r5338 10optware/trunk/ (10 files in 3 dirs): kismet: 802.11 layer2 wireless network detector, sniffer - added Jan 29 08:42:22 eno, you forgot src-data-socket_file.cc.patch Jan 29 09:17:56 03oleo * r5339 10optware/trunk/make/transmission.mk: transmission: downgrade to r1444 Jan 29 10:24:11 03oleo * r5340 10optware/trunk/ (Makefile make/scsi-idle.mk): scsi-idle: SCSI disks and a daemon that spins down drives when idle - initial import Jan 29 13:19:29 03oleo * r5341 10optware/trunk/make/transmission.mk: transmission: r1444->r1446 Jan 29 15:42:46 03bzhou * r5342 10optware/trunk/make/libtorrent.mk: libtorrent: removed src-data-socket_file.cc.patch Jan 29 15:58:06 03osas * r5343 10optware/trunk/make/openser.mk: openser: now with radius and cpl-c support + conf files Jan 29 17:47:21 03bzhou * r5344 10optware/trunk/ (3 files in 2 dirs): scsi-idle: patched to build on slugosbe with 2.6 kernel header Jan 29 18:34:47 hi Jan 29 18:35:58 http://pastebin.ca/332114 - do you know what's the reason for this error? Jan 29 18:36:18 i use the make-script for openslug 3.10 Jan 29 18:36:52 (just downloaded the intel stuff and started "make openslug-image" Jan 29 18:41:41 03gda * r5345 10optware/trunk/ (make/amavisd-new.mk sources/amavisd-new/rc.amavisd): amavisd-new: remove stale pid file during start Jan 29 18:43:07 btw, is it possible to tftp/nfs-boot a nslu2 without flashing it? Jan 29 19:01:15 I'm trying to cross compile mysql on a debian box Jan 29 19:01:40 the make file is asking for automake-1.9 Jan 29 19:02:03 the official version of automake is 1.4-p6 Jan 29 19:02:15 anf therefore, mysql doesn't build :-( Jan 29 19:02:31 s/anf/and/ Jan 29 19:02:32 osas meant: and therefore, mysql doesn't build :-( Jan 29 19:03:01 this is for optware Jan 29 19:04:14 $ dpkg -S /usr/bin/automake-1.9 Jan 29 19:04:14 automake1.9: /usr/bin/automake-1.9 Jan 29 19:06:12 on my box I have only 1.4 Jan 29 19:06:31 apt is not able to find 1.9 Jan 29 19:09:57 osas: maybe search debian backport Jan 29 19:10:34 k Jan 29 19:10:46 eno: have you had a chance to work on the optware slugos wiki page? Jan 29 19:11:41 osas: it's here http://www.nslu2-linux.org/wiki/Optware/SlugosbeDevel Jan 29 19:11:52 still work in progress though Jan 29 19:11:54 k Jan 29 19:11:56 :-) Jan 29 19:12:09 feel free to edit Jan 29 19:12:13 ok Jan 29 19:28:03 `apt-get install automake1.9` did it Jan 29 20:40:36 eno: you there? Jan 29 20:53:33 osas: yes Jan 29 20:53:41 one sec Jan 29 20:53:47 I will post something for you Jan 29 20:53:57 I want you to check something for me :-) Jan 29 20:55:09 http://pastebin.ca/332266 Jan 29 20:55:19 I want to add db support for openser Jan 29 20:55:28 03bzhou * r5346 10optware/trunk/make/rtorrent.mk: rtorrent: added zlib-stage and zlib to DEPENDS Jan 29 20:55:38 and mysql doesn't work on ts72xx Jan 29 20:56:06 is it ok to build like I posted? Jan 29 20:57:16 eno: I want to skip mysql for ts72xx target Jan 29 20:58:18 I am able to build ok for nslu2 Jan 29 20:58:25 the overall idea is sound, it can be improved a little bit. Look at e.g. make/svn.mk to see how we exclude openldap Jan 29 20:58:55 k Jan 29 20:59:59 OTOH, when someone get mysql working on ts72xx, we'll need to remember to increment IPK_VERSION of make/openser.mk Jan 29 21:00:20 got it Jan 29 21:03:22 good plan Jan 29 21:05:45 heh Jan 29 21:05:59 03bzhou * r5347 10optware/trunk/make/nano.mk: nano: 2.0.2 -> 2.0.3 Jan 29 21:07:55 03gda * r5348 10optware/trunk/ (make/fetchmail.mk sources/fetchmail/rc.fetchmail): fetchmail: better start script, logging with syslog on ds101g Jan 29 21:09:30 * ka6sox-office looks at mysql for my TS72XX Jan 29 21:20:26 the optware packages cyrus-imapd and postfix and in my opinion fetchmail need the user and group mail, but don't create them Jan 29 21:20:45 on the ds101g the user doesn't exist Jan 29 21:21:24 nobody has complained till now, is this why the other targets have this user by default? Jan 29 21:21:50 s/why/because/ Jan 29 21:21:50 gda_ meant: nobody has complained till now, is this because the other targets have this user by default? Jan 29 21:24:27 gda_: quite difficult to create user/group in a cross platform way Jan 29 21:25:17 actually, unslung has mail user and group Jan 29 21:25:23 but this happens in the postfix ipk, but only for maildrop Jan 29 21:25:45 so does slugosbe Jan 29 21:26:13 currently the postfix ipk is garbage without creating the mail user before installation Jan 29 21:26:55 it is not that hard to search whether this user already exist and if not create it Jan 29 21:27:40 understand, i think i've done something like that in make/postgresql.mk Jan 29 21:28:27 maybe in this case, you need to have postinst take different actions based on OPTWARE_TARGET Jan 29 21:28:46 eno: I try only to understand why it is like it is Jan 29 21:29:02 does this work for most of the people? Jan 29 21:29:14 does nobody use this ipks? Jan 29 21:29:29 are the targets so different? Jan 29 21:29:56 as i said, unslung and slugosbe have mail user/group Jan 29 21:30:01 user/group creation has always been a stumbling block for ipkgs Jan 29 21:30:14 *always* Jan 29 21:30:42 and remember that not every developer has *every* target Jan 29 21:30:57 eno: I understand, does this mean nobody is using optware? Jan 29 21:31:37 ByronT: and I have only the most exotic one, this is why I ask Jan 29 21:31:41 no, it means that either the ppl who ran into the problem that you are experiencing fixed it for themselves - or they didn't run into the problem Jan 29 21:32:16 (meaning they don't have the same target as you...) Jan 29 21:33:11 to fix, you can either request that someone correct the ipkg (such that it works for your target specifically - as eno has suggested) or if you have permission, fix it yourself... Jan 29 21:33:57 if no one else has reported the problem - then those of us without your target wouldn't know that the problem exists Jan 29 21:34:11 gda_ is more than capable and has commit access to optware Jan 29 21:34:34 ah! then this is a discussion on how to fix... :) Jan 29 21:38:46 ByronT: exactly, what would be the optware way and why has nobody fixed it till now? Jan 29 21:40:10 gda_: even before i joined optware development, the consensus regarding user/group seems to have it either be root or nobody Jan 29 21:40:37 eno: that doesn't work for all packages Jan 29 21:40:46 I can only answer "why has nobody fixed it till now?" authoritatively.... which is nobody got bothered enough to fix it - or it wasn't reported as a problem.... Jan 29 21:40:57 that's right Jan 29 21:41:40 so you're more than welcome to fix it (without affecting those platforms that are working) Jan 29 21:42:04 ByronT: this is what I want to know. Why does nobody report it, because nobody is using it? Jan 29 21:42:08 I've dealt with an cups ipkg issue that missing dependancies weren't installed for unslung... ppl worked their way around it for a loong time Jan 29 21:42:37 because the workaround for it was shorter than reporting it? Jan 29 21:42:57 on the ds101-linux ml I usually see people that are not experienced enough to know what vi means, they can't have fixed it themseld Jan 29 21:43:03 at least that was the case with cups... and I'm sure that it is/was a very popular package Jan 29 21:43:43 so maybe they just gave up? who can really tell? I'm glad that you do care enough to fix the ipkg though Jan 29 21:43:51 we all benefit Jan 29 21:44:29 eno: this is why I ask, so checking that the user/group already exist before I create them should be enough Jan 29 21:45:12 gda_: let's say 80% optware users use nslu2, they don't have the problem since user/group already exists Jan 29 21:45:41 eno: I fear I am really exotic Jan 29 21:45:42 out of the 20%, maybe 50% need to use mail Jan 29 21:46:07 maybe 50% knows the workaround, you get the idea ... Jan 29 21:46:23 the biggest problem optware has currently that there is no controlled shutdown Jan 29 21:46:32 nah... gda_ - you're only exotic if you want to be.... Jan 29 21:47:24 without the last fix for amavisd it would only very seldom surive reboot Jan 29 21:47:46 s/surive/survive/g Jan 29 21:47:48 gda_ meant: without the last fix for amavisd it would only very seldom survive reboot Jan 29 21:47:51 I'm probably "exotic" in that I have four slugs and only one running right now Jan 29 21:47:54 imo, the biggest problem of optware: no separate unstable and stable feeds Jan 29 21:48:42 eno: for me not ;), I would anyway always use unstable Jan 29 21:49:57 had some discussion about that some weeks ago, i just don't have enough time to implement a solution Jan 29 21:50:11 the diskstation makes a e2fsck on every boot because the /opt mount didn't get unmounted properly on the last shutdown Jan 29 21:50:49 is this shutdown problem specific to ds101g or general to optware? Jan 29 21:51:37 eno: wait some seconds, please Jan 29 21:57:30 eno: I don't know, as I have only a diskstation, somebody here that would like to donate me a nslu2 ;) Jan 29 21:58:26 eno: optware gets started via a rc.local script, but there is nothing that stops the optware processes Jan 29 21:58:36 how is it done on the nslu2? Jan 29 22:01:41 i dunno there's any global script to stop all optware daemons Jan 29 22:02:18 but with a proper shutdown, all processes should be terminated Jan 29 22:06:19 the shutdown is not the only thing that is not proper on the diskstation Jan 29 22:15:10 n8 **** ENDING LOGGING AT Tue Jan 30 02:59:57 2007