**** BEGIN LOGGING AT Tue Mar 13 02:59:56 2007 Mar 13 03:28:41 guess not Mar 13 07:42:03 03rwhitby * r772 10kernel/trunk/patches/ (2.6.20/defconfig 2.6.21/defconfig): Enabled some more BT modules, and made the 2.6.21 kernel config match the .20 config. Mar 13 16:17:05 03osas * r5778 10optware/trunk/ (make/openser.mk sources/openser/usrloc.patch): openser: usrloc patch Mar 13 16:46:25 Anyone here fatten their slugs? I'm curious if it is easier to remove the 16M chips and replace with bigger ones on or to piggyback additional 16MB ones on? I have the parts to do either. Mar 13 17:44:37 03bzhou * r5779 10optware/trunk/make/libidn.mk: libidn: 0.6.8 -> 0.6.11 Mar 13 19:31:21 03osas * r5780 10optware/trunk/platforms/ (packages-ddwrt.mk packages-mss.mk packages-oleg.mk): openser: marked as broken for mss ddwrt and oleg platforms Mar 13 19:44:06 hi all Mar 13 19:44:30 what do I need to do in order to compile for mss platform? Mar 13 19:44:36 heh Mar 13 19:44:50 how can I get the toolchain? Mar 13 19:44:57 from /opt/... Mar 13 19:45:19 what arch is mss? Mar 13 19:45:26 I want to fic the openser package for mss, but withou being able to build ... Mar 13 19:45:32 one sec Mar 13 19:45:47 mips Mar 13 19:46:11 I just went and type make all ... but it expects the toolchain from a specific location Mar 13 19:46:35 it is not like the regular nslu2 target which builds it's own toolchain Mar 13 19:47:09 it wants the compiler from here: /opt/brcm/hndtools-mipsel-linux/bin/mipsel-linux-gcc Mar 13 19:47:18 on nudi is there Mar 13 19:47:30 but on my machine I don't know how to get it Mar 13 19:47:32 :( Mar 13 19:48:04 hmm Mar 13 19:48:05 no idea Mar 13 19:49:04 well, I marked the packet as broken for now ... Mar 13 19:53:59 osas: things common to ddwrt, mss, and oleg -> they're all mips Mar 13 19:54:23 so what do I need to do in order to compile? Mar 13 19:54:51 how do i get the compiler in /opt/brcm/hndtools-mipsel-linux/bin/mipsel-linux-gcc ? Mar 13 19:54:56 not sure about mss, for ddwrt and oleg, just "make toolchain" Mar 13 19:55:24 I tried that for ddwrt and it asked to many questions Mar 13 19:55:35 kamicaze vs. stable ... Mar 13 19:55:50 how can I reproduce the env from nudi? Mar 13 19:55:51 really, it should not ask any question Mar 13 19:55:58 ok Mar 13 19:56:03 I will try again Mar 13 19:56:34 so .. in order to clone it, what do I need to pass to make from the main directory? Mar 13 19:56:35 make oleg-target; cd oleg; make directories ipkg-utils toolchain Mar 13 19:56:40 k Mar 13 19:57:19 inside the optware directory? Mar 13 19:57:38 yes Mar 13 20:01:28 it started to ask me about Buildroot Configuration Mar 13 20:01:39 with mipsel being the default one Mar 13 20:02:31 after that it is asking for Kernel Header Options Mar 13 20:07:02 eno: it's a no go :( Mar 13 20:31:05 Is there a more correct method for dealing with user creation as part of a package install? Mar 13 20:31:08 pkg_postinst_prepend() { Mar 13 20:31:08 grep -q openpbx ${sysconfdir}/passwd || adduser openpbx Mar 13 20:31:08 chown -R openpbx:openpbx /var/lib/openpbx.org /var/log/openpbx.org /run/log$ Mar 13 20:31:08 } Mar 13 20:31:24 no, atleast not yet Mar 13 20:31:37 K Mar 13 20:31:49 there should be a bbclass that handles user/group creation/deletion, but there isn't. Mar 13 20:31:59 ah Mar 13 20:32:19 I haven't fully tested this yet Mar 13 20:32:37 is it going to prompt for a password for this user if it needs to be created? Mar 13 20:32:53 quite probably Mar 13 20:33:00 and there's no portable way to make sure it doesn't Mar 13 20:33:11 might it be better to just insert lines into /etc/passwd and etc/group? Mar 13 20:33:12 since busybox and coreutils (?) adduser differ in options. Mar 13 20:33:32 busybox didn't seem to offer a no-prompts option Mar 13 20:33:35 I dunno. It sounds kinda... scary ;) Mar 13 20:33:51 heh Mar 13 20:35:11 One can assume that busybox always exists, and use "busybox adduser" Mar 13 20:35:40 yeah, but it doesn't seem to offer no-prompt options for adduser Mar 13 20:35:54 Prompting can be patched if it is necessary for a distro, with sufficient justification. Mar 13 20:36:19 a better idea would be to actually write the .bbclass ;) Mar 13 20:36:30 for example, I'd like to have the account created in a locked state, so I don't need passwords Mar 13 20:36:35 well, there's that Mar 13 20:36:44 that would require my learning python Mar 13 20:36:46 nno Mar 13 20:36:53 The bbclass is absolutely the best, for stuff in the rootfs creation. Mar 13 20:37:13 I thought we might be referring to postinstall scripting for ipkg. My mistake :( Mar 13 20:37:31 we are Mar 13 20:37:32 mwester: both Mar 13 20:37:41 well, I'm talking about both, actually ;) Mar 13 20:38:30 there are quite a few packages that needs a user to install properly Mar 13 20:38:32 eg. openssh Mar 13 20:38:44 openssh breaks on foonas atm. Mar 13 20:38:51 I have to add user sshd manually Mar 13 20:43:25 looking at the openssh recipe, there seem to be lots of adduser arguments Mar 13 20:43:32 just not well documented Mar 13 20:43:40 poking around busybox.net Mar 13 20:43:43 we'll see Mar 13 20:44:17 busybox might not support --long-options Mar 13 20:44:29 (depending on version and option) Mar 13 20:44:42 and the short options aren't always the same. Mar 13 20:44:56 (and may prompt when you don't expect it) Mar 13 20:45:10 I remember battling with this when I added openntpd to the oe repo Mar 13 20:45:43 I ended up with this: Mar 13 20:45:43 grep ntpd ${sysconfdir}/passwd || adduser --disabled-password --home=${localstatedir}/shared/empty --ingroup nogroup ntpd Mar 13 20:45:52 I'll keep reading Mar 13 20:45:55 (which doesn't work on foonas-current) Mar 13 20:46:02 ah Mar 13 20:46:24 foonas is rather young though, and noone is using it yet ;) Mar 13 20:47:45 where can I read about foonas? Mar 13 20:48:02 nowhere. You can ask me if there's anything you wonder about ;) Mar 13 20:48:28 it sounded cool when you described it a while back but I wanted to see a more detailed list of features/planned features Mar 13 20:48:43 It currently supports the QNAP Turbostation TS-101/TS-201. I'm working on Thecus N2100 support right now. Mar 13 20:49:30 If my current config is correct, it'll build for n2100 with arm eabi, glibc2.5+nptl Mar 13 20:49:59 (But I won't know that until my current build finishes) Mar 13 20:50:28 oh, random discovery. the build of ssmtp deems to be broken but the package in the feeds seems to work properly Mar 13 20:50:40 heh Mar 13 20:50:44 how does it break? Mar 13 20:51:01 * NAiL might add support for linkstations/kuroboxes at a later point in time. Mar 13 20:54:20 I forget Mar 13 20:54:28 this was early last week Mar 13 20:54:36 lemme compile and see Mar 13 20:54:57 osas: oleg toolchain builds fine here after i "rm -rf oleg" Mar 13 20:55:19 eno: one sec Mar 13 20:55:42 I did make oleg-target Mar 13 20:55:48 cd oleg Mar 13 20:56:04 make directories ipkg-utils toolchain Mar 13 20:56:13 and it started to ask questions Mar 13 20:56:30 and by default it will build the kamikaze version ... Mar 13 20:56:51 first question is about Buildroot Configuration Mar 13 20:57:28 you're sure your optware tree is up-to-date? Mar 13 20:57:57 I will start a clean one Mar 13 20:58:02 for mss, see http://www.openmss.org/Development/Optware Mar 13 20:58:08 do you have 5 min? Mar 13 20:58:21 only 2minutes Mar 13 20:58:29 :) Mar 13 20:58:35 need to go into another meeting Mar 13 20:58:48 np Mar 13 20:58:55 I will mess with mss Mar 13 20:59:17 I want to fix openser for those platforms and that's why I need to build Mar 13 20:59:20 thx Mar 13 20:59:24 follow http://www.openmss.org/Development/GettingStarted Mar 13 20:59:25 NAiL: http://www.pastebin.ca/393776 Mar 13 20:59:40 it shows you what to download Mar 13 20:59:51 NAiL: looks like it may be specific to my compile enviroment Mar 13 20:59:52 for /opt/ brcm toolchain Mar 13 21:00:12 NAiL: perhaps it's trying to use the wrong version of strip? Mar 13 21:00:19 hillct: likely Mar 13 21:00:59 bit too busy with foonas to do testing right now though Mar 13 21:01:09 K Mar 13 21:01:12 k Mar 13 21:03:20 the link for the hndtools-3.0 toolchain is broken ... :( Mar 13 21:15:24 NAiL: where are the tinylogin adduser arguments documented? This seems quite incomplete http://tinylogin.busybox.net/TinyLogin.html Mar 13 21:15:57 no idea Mar 13 23:08:28 hi **** ENDING LOGGING AT Wed Mar 14 03:00:00 2007