**** BEGIN LOGGING AT Wed Feb 14 02:59:57 2007
Feb 14 03:12:00 <CIA-19> 03bzhou * r5498 10optware/trunk/make/bluez-utils.mk: bluez-utils: worked around missing ENOKEY (only available in 2.6 asm/errno.h)
Feb 14 03:28:40 <jason0_> I recently ran into some troubles w/ rtorrent & safe_sync problems. Is it possible to upgrade/downgrade the kernel to get around these issues?
Feb 14 03:59:53 <drif> not much people around
Feb 14 04:38:12 <CIA-19> 03bzhou * r5499 10optware/trunk/make/rubygems.mk: rubygems: 0.9.1 -> 0.9.2
Feb 14 04:57:46 <CIA-19> 03bzhou * r5500 10optware/trunk/Makefile: bluez-utils: demote on wl500g
Feb 14 05:06:43 <rwhitby> bummer, I want to get bluetooth working on the wl500g ...
Feb 14 05:12:44 <eno> rwhitby: latest bluez-utils depends on dbus, which does not build for wl500g
Feb 14 05:12:52 <rwhitby> :-(
Feb 14 05:16:33 <CIA-19> 03rwhitby * r694 10kernel/trunk/ (6 files in 3 dirs): Enabled EABI compatibility, and dsmg600 shim.
Feb 14 05:40:35 <CIA-19> 03rwhitby * r695 10kernel/trunk/patches/arm-kernel-shim/ (config-dsmg600.h passthrough-atags.patch series): Added passthrough-atags support.
Feb 14 05:46:52 <CIA-19> 03bzhou * r5501 10optware/trunk/ (Makefile make/dbus.mk): dbus & bluez-utils: hacked to work on wl500g, promoted
Feb 14 05:49:59 <rwhitby> woohoo!
Feb 14 05:50:19 <rwhitby> now I wonder if the kernel modules will work for the wl500g ...
Feb 14 05:55:25 <mwester> How big is optware now?
Feb 14 05:56:40 <rwhitby> over 750 packages
Feb 14 05:57:00 <eno> $ w3m -dump http://ipkg.nslu2-linux.org/feeds/optware/nslu2/cross/unstable/Packages | grep -c ^Package:
Feb 14 05:57:03 <eno> 801
Feb 14 05:57:12 <mwester> nice job!
Feb 14 05:57:21 <eno> $ w3m -dump http://ipkg.nslu2-linux.org/feeds/optware/nslu2/native/unstable/Packages | grep -c ^Package:
Feb 14 05:57:24 <eno> 13
Feb 14 05:57:32 <rwhitby> at least half of those would be eno's work alone
Feb 14 05:58:03 <mwester> only 13 native?
Feb 14 05:58:25 <rwhitby> I think some of those have been obsoleted by cross packages too
Feb 14 05:59:20 <rwhitby> hmm - maybe not, looks like eno has kept that up to date too
Feb 14 05:59:26 <rwhitby> (in the Makefile at least)
Feb 14 06:00:01 <eno> was just testing libopensync with msynctool (file-sync), have some runtime problem
Feb 14 07:43:58 <CIA-19> 03oleo * r5502 10optware/trunk/make/perl-convert-uulib.mk: perl-convert-uulib: add alternate download source
Feb 14 08:28:20 <CIA-19> 03oleo * r5503 10optware/trunk/ (4 files in 2 dirs): transmission: chang to atomic signal type and fix watchdog message
Feb 14 09:16:01 <CoreDump|home> morning
Feb 14 18:58:28 <hillct> There seems to be some sort of redirection loop when attempting to download the intel hardware library files for the cross compile enviroment. is there any alternate method of downloding them?
Feb 14 19:51:06 <drif> hi shark
Feb 14 19:51:19 <drif> ups :D wrong nslu2-channel
Feb 14 19:59:43 <rwhitby> hillct: you have to manually go to the Intel site and download them yourself, cause you need to read the license and agree to it (it is *not* a normal license)
Feb 14 20:00:12 <hillct> I know
Feb 14 20:00:23 <hillct> problem seems to be the intel site is broken
Feb 14 20:00:35 <rwhitby> ah
Feb 14 20:00:39 <hillct> whenever I attempt to follow that procedure I end up in a redirection loop
Feb 14 20:01:58 <hillct> I can delete all cookies related to intel.com, then when I try again, I log back in then get one screen further (there are two intermediate screens after you acept the license) then after clicking downlaod, it goes back into the loop
Feb 14 20:02:11 <hillct> the site is just foobar
Feb 14 20:04:38 <hillct> I gather they changed their site recently
Feb 14 20:04:46 <hillct> doesn't seem to work at all in firefox
Feb 14 20:05:07 <hillct> the export info form uses some horribly broken ajaxy crap
Feb 14 21:11:42 <hillct> rwhitby: are the intel libraries only needed for the kernel build or for any cross-compiling? (since there currently appears to be no way to download them)
Feb 14 21:30:34 <eno> hillct: for packages, you can try "cd ~/slug/slugosbe; . ./setup-env; bb virtual/armeb-linux-gcc virtual/libc"
Feb 14 21:30:51 <eno> you should get the cross toolchains
Feb 14 21:31:17 <eno> then try "bb <other-package>"
Feb 14 21:33:09 <eno> or follow http://www.nslu2-linux.org/wiki/Optware/SlugosbeDevel for optware/slugosbe development
Feb 14 21:43:12 <hillct> eno: thanks. I was working from the directions on the MasterMakefile wiki page
Feb 14 21:53:27 <marjasin>  I'm trying to flash the device via the web interface with the unofficial debian image, but i get an error message "Upgrade: No enough free space.". What could be the problem? 
Feb 14 22:06:02 <hillct> marjasin: I believe you can only upgrade by the web interface, to UnSlung
Feb 14 22:06:42 <hillct> if you want to flash any other firmware, you need upslug2 or Sercomm for Windows
Feb 14 22:06:43 <NAiL> it's a known problem with the firmware. Use upslug2
Feb 14 22:07:15 <marjasin> I see
Feb 14 22:07:15 <marjasin> Thanx
Feb 14 22:08:10 <marjasin> That guy that has made the Debian howto should update the installation guide in that case, I was starting to think they had changed something in the hardware or so in order to prevent this kind of firmware updates
Feb 14 22:08:44 <hillct> eno: on some wiki page I saw a procedure to be used if setup-env causes the shell to be closed, but I can no longer find it
Feb 14 22:09:28 <drif> marjasin: the guide said to use web admin page?
Feb 14 22:10:29 <marjasin> drif: http://www.cyrius.com/debian/nslu2/install.html
Feb 14 22:10:53 <marjasin> It mentions all the possibilities
Feb 14 22:10:57 <NAiL> In earlier stock firmwares, there was no problem upgrading using the webinterface. It's a recent bug. 
Feb 14 22:15:14 <marjasin> Hmm
Feb 14 22:16:08 <marjasin> i probably shouldnt install debian... Seems like the installer is broken :/
Feb 14 22:27:36 <rwhitby> hillct: intel microcode is only required for building final image now
Feb 14 22:28:59 <hillct> cool. thanks
Feb 14 22:32:26 <hillct> trying to build the minimum toolchain as defined here http://www.nslu2-linux.org/wiki/Optware/SlugosbeDevel
Feb 14 22:32:41 <hillct> setup-env fauses the shell to exit every time
Feb 14 22:32:50 <hillct> er causes
Feb 14 22:33:30 <AdamBaker> marajsin: The debian installer was announced as broken on the ML, apparently it is a key expiry issue that has broken lots of release candidate installers, http://thread.gmane.org/gmane.comp.misc.nslu2.linux/17873
Feb 14 22:33:34 <hillct> the MasterMakefile page says do a 'make' in the openslug directory to resolve this
Feb 14 22:33:45 <hillct> but that has no impact
Feb 14 22:37:41 <CoreDump|home> hi
Feb 14 22:45:21 <rwhitby> hillct: does "make" in the slugosbe directory not build an image for you?
Feb 14 22:45:29 <rwhitby> or "make slugosbe" in the directory above?
Feb 14 22:48:04 <hillct> it would
Feb 14 22:48:18 <hillct> but it wants the intel microcode
Feb 14 22:48:23 <hillct> which I can't get my hands on due to Intel's broken website
Feb 14 22:48:46 <hillct> but all I really want to do is build additional packages, not the full image
Feb 14 22:50:51 <rwhitby> hillct: I just got it with Firefox
Feb 14 22:51:06 <rwhitby> from http://www.intel.com/design/network/products/npfamily/ixp400_current.htm
Feb 14 22:51:28 <rwhitby> you want NPE Microcode v2.3
Feb 14 22:51:51 <hillct> yes
Feb 14 22:51:55 <marjasin> hmm... Anyone that knows why I cant install upslug2 via apt-get install?
Feb 14 22:52:12 <hillct> as I said before, if you try to download it, you end up in a redirection loop 
Feb 14 22:52:53 <hillct> if you're able to grab it, that's great. I can't
Feb 14 22:53:01 <hillct> get a redirection loop every time
Feb 14 22:54:02 <hillct> their export infor form only works in IE, but once you get past that, you can get to the last step even in firefox but end up in a redirection loop
Feb 14 22:54:08 <hillct> at that step
Feb 14 22:54:26 <hillct> I've tried this at least 20 times in the past 5 hours
Feb 14 22:55:51 <rwhitby> hillct: get the one without crypto.
Feb 14 22:55:53 <CoreDump|home> hillct: I've just downloaded IPL_ixp400NpeLibrary-2_3.zip w/o problems
Feb 14 22:56:41 <CoreDump|home> hillct: I can upload it for you if you want
Feb 14 22:57:40 <hillct> I assumed the one with crypto was required
Feb 14 22:57:55 <rwhitby> nope
Feb 14 22:57:58 <hillct> perhaps that's the hangup
Feb 14 22:58:06 <hillct> lemme see if the other is acessible
Feb 14 22:58:08 <hillct> one sec
Feb 14 23:01:22 <hillct> this is the URL that results in the redirection error
Feb 14 23:01:24 <hillct> http://downloadfinder.intel.com/scripts-df-external/confirm.aspx?httpDown=http://aiedownload.intel.com/entitled/11190/eng/BSD_ixp400AccessLibrary-2_3.zip&agr=&ProductID=2100&DwnldId=11190&strOSs=&OSFullName=&lang=eng&ent=Y&url=/11190/eng/BSD_ixp400AccessLibrary-2_3.zip
Feb 14 23:02:32 <hillct> CoreDump|home: if you could put it up in a place I can get at it I'd really appreciate it. thanks
Feb 14 23:02:44 <CoreDump|home> hillct: sure, hold on
Feb 14 23:04:15 <hillct> rwhitby: do I need the access library, patch and NPE?
Feb 14 23:04:22 <rwhitby> nope, just the Npe
Feb 14 23:04:31 <hillct> K
Feb 14 23:04:37 <rwhitby> hillct: make sure you read and accept the license first.  It's not a standard one.
Feb 14 23:05:11 <hillct> I've read and accepted it 20 times today
Feb 14 23:05:18 <CoreDump|home> hillct: http://hentges.net/tmp/.upload/
Feb 14 23:05:19 <hillct> still can't download it :)
Feb 14 23:06:26 <hillct> wow
Feb 14 23:06:30 <hillct> those are tiny little files
Feb 14 23:06:34 <NAiL> rwhitby: the site is broken. We get to the download part (after accepting), and the site goes into a redirect loop
Feb 14 23:06:35 <hillct> CoreDump|home: thanks
Feb 14 23:06:40 <CoreDump|home> np
Feb 14 23:07:12 <NAiL> CoreDump|home: Be sure to remove those after he's downloaded them
Feb 14 23:07:13 <hillct> NAiL: thanks. I'm glad I'm not going nuts
Feb 14 23:07:21 <rwhitby> NAiL: I just downloaded it fine
Feb 14 23:07:26 <hillct> CoreDump|home: I'm all set
Feb 14 23:07:29 <NAiL> rwhitby: using firefox on linux?
Feb 14 23:07:39 <rwhitby> nope, firefox on XP
Feb 14 23:07:42 <hillct> ah
Feb 14 23:07:42 <NAiL> I've tried a dozen times. I had to give up and get them from nudi
Feb 14 23:07:48 <hillct> linux here
Feb 14 23:08:14 <hillct> also tried using IE6 under Wine
Feb 14 23:08:52 * NAiL tries to go back to sleep
Feb 14 23:08:52 <NAiL> nite 
Feb 14 23:36:23 <marjasin_> yay
Feb 14 23:36:37 <marjasin_> Now Im reflashing \o/
Feb 14 23:41:49 <rwhitby> marjasin_: missed you in #debian-arm
Feb 14 23:42:11 <marjasin_> rejoined now
Feb 15 00:19:01 <hillct> rwhitby: what distinguished optware from other OE or cross compiled packages for Openslug (other than placement within the file tree)? Is it just a matter of platform specific testing?
Feb 15 00:52:33 <eno> hillct: optware use gnu make, most optware packages are cross compiled
Feb 15 00:52:57 <eno> OE distros use bitbake
Feb 15 00:55:16 <eno> optware packages are all installed under /opt
Feb 15 00:55:55 <eno> while OE ipkgs use normal prefix
Feb 15 00:58:08 <eno> bitbake involves some learning curve, it is very powerful, but sometimes a bit too implicit IMO
Feb 15 00:58:49 <eno> makefiles are old makefiles you know
Feb 15 00:58:52 <hillct> but it has no bearing on package maturity or testing status?
Feb 15 00:59:38 <eno> that really varies depend on individual packages
Feb 15 00:59:45 <hillct> sure
Feb 15 01:00:04 <eno> oe covers a wide range of devices
Feb 15 01:00:15 <hillct> but the fact that something is optware, doesn't say anything definate about it's reliability
Feb 15 01:00:38 <eno> no
Feb 15 01:00:44 <hillct> K
Feb 15 01:01:01 <eno> same goes for oe ipk
Feb 15 01:02:59 <hillct> I see quite a few packages built for unslung but not for openslug. if I understand the docs correctly, I should be able to add a line to a a bb file for openslug and re-use the package bb file for unslung with few or no modifications to build the package for openslug.
Feb 15 01:03:09 <hillct> is that generally accurate?
Feb 15 01:03:29 <hillct> I still have lots of reading to do about Bitbake
Feb 15 01:03:57 <rwhitby> no, optware uses .mk files
Feb 15 01:04:06 <rwhitby> OE uses .bb files
Feb 15 01:04:08 <hillct> er
Feb 15 01:04:09 <hillct> sorry
Feb 15 01:04:16 <rwhitby> you can generally transfer the list of patches and stuff like that
Feb 15 01:04:17 <hillct> I didn't mean optware
Feb 15 01:04:23 <rwhitby> but it's a manual process
Feb 15 01:04:37 <hillct> I meant those packages built for unslung. Or are all unslung packages optware by definition?
Feb 15 01:04:55 <rwhitby> unslung only uses OE to build the base firmware.  All the packages that users download (except for kernel modules) come from Optware
Feb 15 01:05:10 <hillct> I see
Feb 15 01:05:26 <rwhitby> (since installing an OE package over the Unslung base rootfs would have unpredictable effects on the Linksys closed binaries and stuff
Feb 15 01:06:28 <hillct> ok
Feb 15 01:06:31 <hillct> makes sense
Feb 15 01:08:43 <hillct> the two packages I want to build for Openslug are both relatively trivial builds. Logrotate is single basic binary with no dependencies, and rMirror is just perl so should be simply an excercise in ipkg packaging
Feb 15 01:09:05 <rwhitby> or just add them to OE
Feb 15 01:09:16 <hillct> ultimately, yes
Feb 15 01:10:26 <hillct> hopefully they'll both make suitable learning builds
Feb 15 01:11:27 <hillct> oh, incidently, what package contains the ipkg config scripts for the OE package list?
Feb 15 01:12:01 <hillct> I browsed the list but didn't see the relevent package
Feb 15 01:13:26 <CoreDump|home> the package lists are integrated at image creation.
Feb 15 01:13:33 <CoreDump|home> s/at/during
Feb 15 01:13:59 <CoreDump|home> right before it is packaged up as .jffs2 or whatever
Feb 15 01:21:14 <hillct> I mean the ipkg conf files for the various repositories
Feb 15 01:21:58 <hillct> included in slugosBE are /etc/ipkg/cross.conf and /etc/ipkg/native.conf
Feb 15 01:22:31 <hillct> I assume, I can add a conf file that specifies the OE package repository
Feb 15 01:22:42 <hillct> granted I could just add one
Feb 15 01:23:29 <hillct> but I figure it'd be better to use an ipkg to add the conf file if one exists
Feb 15 01:24:33 <CoreDump|home> hillct: ahh, the DISTRO.conf usually, or inside the $IMAGE.bb
Feb 15 01:25:03 <CoreDump|home> there is no ipkg for these files
Feb 15 01:25:13 <hillct> there probably should be
Feb 15 01:25:39 <rwhitby> the distribution image comes with the fully supported feeds in place.
Feb 15 01:25:41 <hillct> modeling use of ipkg after typical use of other package managers such as yum/rpm
Feb 15 01:26:25 <rwhitby> the optware/slugosbe cross-distribution feed is a new thing which we're not sure whether to enable for Joe User easily or not yet.
Feb 15 01:27:19 <hillct> sure, what I'm saying is that the OE package repository for a given distro should include an ipk which contains only the /etc/ipkg/oe.conf file, for the simple reason that it provides upgrade consistency
Feb 15 01:27:38 <hillct> not saying it should be included in the image
Feb 15 01:29:20 <rwhitby> oh, I see.  Interesting idea.
Feb 15 01:30:03 <CoreDump|home> indeed.
Feb 15 01:30:35 <hillct> this is how secondary repositories for Fedora Core/Centos make use of Yum, the front end to RPM packge management
Feb 15 01:30:49 <rwhitby> hillct: we need to think carefully about how that links in with the reflash and turnup functionality for SlugOS.
Feb 15 01:31:07 <hillct> sure
Feb 15 01:34:15 <hillct> here's how the Livna repository handles repo releases as new OS releases are made http://rpm.livna.org/rlowiki/UsingLivna
Feb 15 01:35:28 <hillct> user is instructed to download the livna-release package which contains the repo config files (for Yum/RPM in this case) which contain metadata about the repository, for integration into yum much as could be done for the ipkg OE repository
Feb 15 01:37:09 <hillct> it also has the great advantage of allowing you to relocate the repository from release to release where you'd just have to include a new version of the oe-release.ipk file, which would be updated such that the user could subsequently retrieve from the new repository location, having just updated the relevent ipkg config file
Feb 15 01:40:21 <hillct> Are slugosbe and slugos-bag feed directories the same (ie: just name change)?
Feb 15 01:46:34 <rwhitby> yes, it's a symlink
Feb 15 01:59:38 <hillct> K
Feb 15 02:01:12 <hillct> Is ipkg suppost to read all the files in /etc/ipkg? or do I need to add the OE repository URL to one of the two existing config files in /etc/ipkg (cross or native)?
Feb 15 02:02:08 <hillct> or aparently I can indicate the config file on the ipkg command line, but that's less than ideal
Feb 15 02:06:27 <CoreDump|home> hillct: it should read all *.conf files in /etc/ipkg IIRC
Feb 15 02:06:44 <CoreDump|home> dropping your new file in there should work just fine
Feb 15 02:07:07 <hillct> doesn't seem to work
Feb 15 02:08:33 <CoreDump|home> ipkg update ignores your file? worked for me in the past
Feb 15 02:08:52 <hillct> seems to ingore my new file /etc/ipkg/oe-feed.conf
Feb 15 02:09:21 <hillct> I added it with one line
Feb 15 02:09:22 <hillct> src/gz cross http://ipkg.nslu2-linux.org/feeds/slugos-bag/oe
Feb 15 02:09:28 <hillct> er
Feb 15 02:09:28 <hillct> d'oh
Feb 15 02:09:30 <hillct> I see
Feb 15 02:09:32 <CoreDump|home> =)
Feb 15 02:09:40 <hillct> I blew it
Feb 15 02:18:25 <hillct> hmm
Feb 15 02:19:06 <hillct> am I going to regret upgrading /sbin/devio out of the OE repository?
Feb 15 02:22:30 * CoreDump|home dunnos
Feb 15 02:24:48 <hillct> the purpose of /sbin/devio is not clear
Feb 15 02:24:59 <hillct> reading OE commit notes
Feb 15 02:25:06 * hillct is not a kernel hacker
Feb 15 02:25:22 <rwhitby> hillct: why are you adding feeds?
Feb 15 02:25:54 <rwhitby> slugos-bag/oe is not a current feed.
Feb 15 02:26:22 <rwhitby> devio is a userland tool, not kernel related
Feb 15 02:26:51 <hillct> I figured it was something equivelent to linux udev
Feb 15 02:26:59 <hillct> userland but key to operation
Feb 15 02:27:49 <hillct> rwhitby:  re feeds, I'm just poking around. learning the structure of the project
Feb 15 02:28:21 <rwhitby> be aware there is a lot of dirs in the feeds are which are only there for backwards compatibility of very old versions
Feb 15 02:28:43 <hillct> I'm realizing that
Feb 15 02:28:51 <rwhitby> all the available feeds for SlugOS are already in your rootfs image (apart from the single Optware/slugosbe new feed)
Feb 15 02:29:39 <hillct> oh?
Feb 15 02:29:45 <hillct> http://ipkg.nslu2-linux.org/feeds/slugos-bag/oe/
Feb 15 02:29:52 <hillct> was not included
Feb 15 02:30:14 <hillct> is it not suitable for slug/os BE?
Feb 15 02:30:27 <rwhitby> no
Feb 15 02:30:37 <rwhitby> look at the dates on the files for a start
Feb 15 02:30:45 <hillct> yeah
Feb 15 02:30:46 <hillct> old
Feb 15 02:31:39 <rwhitby> For each slugos distro (be, le) there is a single cross feed and a single native feed.  for slugosbe, there is a single optware/slugosbe feed as well.
Feb 15 02:31:46 <rwhitby> that's *all*
Feb 15 02:31:56 <hillct> I see
Feb 15 02:32:45 <hillct> when a new package is built for slugOS and a .bb file added, in what feed would the package appear? Cross, I guess...
Feb 15 02:34:10 <rwhitby> cross/unstable
Feb 15 02:34:28 <rwhitby> (the set of packages is in packages/meta/slugos-packages.bb)
Feb 15 02:34:37 <rwhitby> the autobuilder runs every 15 minutes
Feb 15 02:40:42 <hillct> ah
Feb 15 02:51:47 <hillct> well, with all that in mind, my earlier comments regarding secondary repositories is meaningless
**** ENDING LOGGING AT Thu Feb 15 02:59:57 2007