**** BEGIN LOGGING AT Fri Sep 09 02:59:56 2005 Sep 09 05:08:12 hi to all Sep 09 05:08:22 i ve just installed openslug Sep 09 05:08:36 but if i do "ipkg update" i get: Sep 09 05:08:58 ipkg: Cannot create directory `/var/lib/ipkg': File exists Sep 09 05:09:03 ipkg: Cannot create directory `/var/lib/ipkg': File exists Sep 09 05:09:09 An error ocurred, return value: 22. Sep 09 05:09:13 Collected errors: Sep 09 05:09:20 ipkg_update_cmd: ERROR: failed to make directory /var/lib/ipkg: File exists Sep 09 05:09:36 does someone knows how to fix it ? Sep 09 05:09:45 is /var/lib/ipkg a directory or file? Sep 09 05:10:17 it's a link Sep 09 05:10:24 ipkg -> /media/ram/var/lib/ipkg Sep 09 05:11:22 but in media/ram/var there are no lib directories ! Sep 09 05:16:10 <[g2]> andrea_ which version of openslug ? Sep 09 05:16:12 koen: can't you help me ? :-( Sep 09 05:16:24 <[g2]> and did you turnup to disk or flash ? Sep 09 05:16:34 <[g2]> flash being memstick Sep 09 05:16:40 it's a versione a built with makefile ~3 august Sep 09 05:16:45 yes Sep 09 05:16:55 memsticl Sep 09 05:16:57 memstick Sep 09 05:17:51 <[g2]> I think an old version (like aroundearly Aug) 5-6 weeks is old in slug time had an issue with that Sep 09 05:18:12 <[g2]> is /var/lib/ipkg empty ? Sep 09 05:18:49 yes Sep 09 05:19:09 as i said it's a link Sep 09 05:19:18 but i point to nowhere! Sep 09 05:19:37 <[g2]> well is a mount point Sep 09 05:19:44 <[g2]> well /media Sep 09 05:20:18 <[g2]> where does /var point ? Sep 09 05:21:06 just a minute Sep 09 05:21:11 i ve rebooted Sep 09 05:21:35 <[g2]> basically I think your ipkg directory is not useful and ipkg update bombs out on it Sep 09 05:22:01 <[g2]> I think you need to point it somewhere useful so the ipk info can get copied to your system Sep 09 05:22:38 and how can i modify it ? Sep 09 05:23:33 remove the link and create the dirs or change ipkg.conf Sep 09 05:23:41 <[g2]> iirc there were some changes that [cc]smart and others did awhile back for /var Sep 09 05:24:06 <[g2]> bascially for memstick you don't won't all the log file updates written to the flash as it'll wear out the media Sep 09 05:24:22 <[g2]> however, your ipkg file does need some persistent storage Sep 09 05:24:32 <[g2]> and right now it's pointing off in the weeds Sep 09 05:26:21 Mmmm Weed. Sep 09 05:26:37 Whoops, did I say that aloud? Sep 09 13:16:32 * ByronT is away -( The Lion King... oh, joy. )- at 03:15p -( P:On / L:Off )- Sep 09 23:14:50 hi, I'm trying to rebuild the 2.5 tarball, but things are not going as expected Sep 09 23:15:53 I'm using the master makefile and make indeed builds a lot of things before bailing out because xinetd cannot be downloaded Sep 09 23:16:16 ok, I knew that from the wiki and that is not really a problem to me Sep 09 23:16:44 However I want to be able to build individual parts. Sep 09 23:17:31 The BuildingTheSource page suggests to do make openslug-firmware-safe as a test. When I do that I get:[slug@Woonkamer OpenSlug2.5]$ make openslug-firmware-safe Sep 09 23:17:32 make: *** No rule to make target `openslug-firmware-safe'. Stop. Sep 09 23:17:47 puzzled. Anyone any idea? Sep 09 23:20:06 that isn't from master makefile that is from openslug makefile? Sep 09 23:25:07 nope, it is from the master makefile Sep 09 23:25:11 actually i tried both Sep 09 23:25:27 that is an error in the doco...thanks for pointing it out Sep 09 23:25:48 now to find out what it really should be. :) Sep 09 23:25:57 great Sep 09 23:26:20 i'm out of clues, monotone and bitbake and so are new to me. Sep 09 23:26:39 I'm from the make/sccs age ... Sep 09 23:27:24 brb (10 mins) Sep 09 23:41:00 how did you set this all up? Sep 09 23:41:18 the tarball is standalone. Sep 09 23:42:55 back Sep 09 23:43:25 I used the tarball; i can run make and get things build until I bail out on xinetd Sep 09 23:43:55 with the makefile in the tarball I cound not make individual elements (or at least I don't know how) Sep 09 23:45:10 then I tried the master makefile Sep 09 23:45:17 triggered by the following: Sep 09 23:45:31 I followed the link BuildingTheSource from the OpenSlug homepage Sep 09 23:45:49 this one says at the top: Sep 09 23:45:50 This has been obsoleted by Openslug 2.3. Please use the MasterMakefile. Sep 09 23:46:05 hence, i tried that as well (but to no avail) Sep 09 23:47:01 the BuildingTheSource wiki page also says: Sep 09 23:47:02 First try "make" with no arguments. If the simple make fails in some mysterious way try "make openslug-firmware-safe" (this requires that your shell support env -i). Sep 09 23:48:00 actually I am trying to find out how to set up a good cross dev env where I can cross compile individual packages and the kernel Sep 09 23:48:48 source setup-env Sep 09 23:48:54 bitbake openslug-image Sep 09 23:49:08 bitbake some_package_name Sep 09 23:50:00 # bitbake openslug-image Sep 09 23:50:00 bash: bitbake: command not found Sep 09 23:50:16 so i seem to be missing an installation step (the source command is fine). Sep 09 23:50:28 I am on fedora core 3 if that matters Sep 09 23:50:52 and I got a subdir bitbake Sep 09 23:50:59 but no executable Sep 09 23:51:18 I need to look at the tarball. Sep 09 23:51:21 which one did you use? Sep 09 23:51:49 OpenSlug-2.5-beta-source.tar.gz Sep 09 23:52:57 got it from https://developer.berlios.de/project/showfiles.php?group_id=3702 Sep 09 23:55:31 according to the readme file I'm between camp2 and 3 :-); I have quite some *nix knowledge and did a good amount of kernel hacking, but that was quite a while ago. Sep 10 00:01:48 Unpacking the tarball now Sep 10 00:02:11 dyoung is my hero ;) Sep 10 00:02:57 pity there are no photo's on the nslu2 website Sep 10 00:03:30 Sep 10 00:04:21 Theres no topdir.conf Sep 10 00:04:36 Oh wait thats generated. Sep 10 00:04:37 one moment Sep 10 00:05:10 Okay, so did you do "make firmware-safe" ? Sep 10 00:05:33 or "make firmware" ? Sep 10 00:05:41 nl, let me try Sep 10 00:06:27 it is now saying "handling bitbake files" Sep 10 00:06:38 i'll get back to you once this is done Sep 10 00:09:58 it's progressing, I am now at task do_rootfs started Sep 10 00:11:12 if its that far already, your original desire of having a cross compiler is accomplished. Sep 10 00:11:23 ok Sep 10 00:11:40 what about the bitbake thing? Sep 10 00:11:43 look in tmp/cross/bin Sep 10 00:12:07 Bitbake is there; but if you never ran a makefile target, your setup-env could not have run. Sep 10 00:12:50 oh, indeed now it can be started Sep 10 00:12:51 so actually if you want to make just a single package, you could in theory source setup-env; bitbake package . Sep 10 00:14:43 great, that would help me a lot Sep 10 00:16:33 I think the wiki need some changes; I'm more than happy to actually make them, but let me check if I got it right Sep 10 00:16:43 Please do. Sep 10 00:17:11 1. when building the source from the tarball one should use the makefile in the tarball not the master makefile Sep 10 00:18:21 Thats correct, using the master makefile implies that you are building from the current head; that is the latest bleeding edge available. Sep 10 00:19:54 so commands like "make openslug-firmware-safe" in BuildingTheSource do not apply if you want to build the 2.5 tarball but are only applicable for the head Sep 10 00:19:57 right? Sep 10 00:20:49 thats probably a typo, firmware-safe is what youre looking for. Sep 10 00:21:11 you can make firmware too Sep 10 00:21:49 ok, understood that; can I also build individual packages with make or is this strictly a bitbake thing Sep 10 00:22:22 No, the makefile is there to make the whole stuff. Sep 10 00:22:34 understood Sep 10 00:22:45 if you wish to make a individual package; you would do "source setup-env; bitbake package" Sep 10 00:22:58 but before that, you'd want to "make create-topdir" Sep 10 00:23:24 hm. don't recall having done that one Sep 10 00:24:12 you didnt. Sep 10 00:24:41 its a dependency of the "firmware" and "firmware-safe" targets; so it got run without you having to actually do it Sep 10 00:25:14 should you run it if for some reason you move your tree ? Sep 10 00:25:26 Yes, or just edit conf/topdir.conf Sep 10 00:25:42 I'm asking all these Q's so I can make a good page for this Sep 10 00:26:02 of course! Sep 10 00:26:05 what is the diff between firmware and firmware-safe Sep 10 00:27:20 -safe clobbers the environment. Sep 10 00:27:32 ie: it resets $HOME and $PATH. Sep 10 00:27:56 I dont remember the reasoning behind that. Sep 10 00:28:19 ok. clear Sep 10 00:29:10 another Q: I placed my tree a little bit clumsy, so while chatting I moved it; did a make create-topdir;redid a source setup-env; but make firmware doesn't do the job any more Sep 10 00:30:22 the rootfs log says: fakeroot: preload library not found, aborting. Sep 10 00:31:31 on first look the paths in the run script look ok Sep 10 00:32:29 thinking of it i might need to rebuild the cross compiler since some paths in it might now be wrong Sep 10 00:33:59 does conf/topdir.conf say the right thing? Sep 10 00:34:03 yes] Sep 10 00:34:31 you may need to blow away tmp/cache Sep 10 00:35:59 let me try that, hang on Sep 10 00:36:24 meanwhile, do you by any chance know what I need to do to access a USB cdrom drive on the slug? Sep 10 00:38:53 removing tmp/cache didn't work Sep 10 00:43:10 not sure. Sep 10 00:43:23 I think its all there though. cdrom module, iso9660 module, etc Sep 10 00:44:10 that's what I thought. I expected the drive to be at /dev/scd0 but I cannot mount it Sep 10 00:44:19 lemme check Sep 10 00:44:29 Oh, does that devicename exist? Sep 10 00:44:37 you may have to make the link yourself. Sep 10 00:45:14 with mknod Sep 10 00:46:00 i know makenod; devname exists. see this: Sep 10 00:46:01 root@NSLU2:/usr/home/slug# mount /dev/scd0 /mnt Sep 10 00:46:01 mount: /dev/scd0 is not a valid block device Sep 10 00:46:01 root@NSLU2:/usr/home/slug# ls -l /dev/scd0 Sep 10 00:46:01 brw-rw---- 1 root root 11, 0 Oct 3 2005 /dev/scd0 Sep 10 00:46:40 did dmesg tell you anything of use when you plugged the drive? Sep 10 00:46:41 the dev was there. Would major 11 be ok? Sep 10 00:47:06 wouldn't you need srmod and all the scsi-cd stuff too? Sep 10 00:47:15 good morning all Sep 10 00:47:23 hi koen Sep 10 00:47:26 srmod? Sep 10 00:47:50 dmesg added the following 10 lines (apologies for the flood) Sep 10 00:47:52 usb 1-2: new high speed USB device using ehci_hcd and address 24 Sep 10 00:47:53 scsi5 : SCSI emulation for USB Mass Storage devices Sep 10 00:47:53 usb-storage: device found at 24 Sep 10 00:47:53 usb-storage: waiting for device to settle before scanning Sep 10 00:47:53 Vendor: PHILIPS Model: JR4DVDRW Rev: 3.00 Sep 10 00:47:55 Type: CD-ROM ANSI SCSI revision: 00 Sep 10 00:47:57 usb-storage: device scan complete Sep 10 00:48:42 with regular scsi drives you need to have srmod (scsi removable devices) loaded Sep 10 00:48:57 and in /proc/bus/usb/devices it is added as: Sep 10 00:48:58 T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 24 Spd=480 MxCh= 0 Sep 10 00:48:58 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 Sep 10 00:48:58 P: Vendor=0471 ProdID=0816 Rev=11.06 Sep 10 00:48:58 S: Manufacturer=PHILIPS Sep 10 00:48:58 S: Product=Philips USB Storage Device Sep 10 00:49:00 S: SerialNumber=MD100349001408 Sep 10 00:49:02 C:* #Ifs= 1 Cfg#= 2 Atr=c0 MxPwr= 98mA Sep 10 00:49:04 I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage Sep 10 00:49:08 E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=125us Sep 10 00:49:10 E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms Sep 10 00:49:12 E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=32ms Sep 10 00:49:14 how can I check if srmod is loaded ? Sep 10 00:49:21 with lsmod Sep 10 00:49:54 of course! It is not loaded Sep 10 00:50:14 any idea where I can find it? Sep 10 00:52:39 dyoung, I made a symlink from tmp to its old place and now it works again Sep 10 00:52:54 I'm now trying to find out which subdir actually causes the problem Sep 10 00:53:22 (I know recreating the tree is probably faster, but I'd like to know why things fail) Sep 10 00:54:32 Hmm, I dont see srmod in the feed. but cdrom is there Sep 10 01:03:25 back in 15 mins or so Sep 10 01:31:48 dyoung, I've been playing a little bit more with the moved build tree Sep 10 01:32:17 if I keep a symlink to staging in the old tmp location all builds and I end up with a rootfs in the old tmp location as well Sep 10 01:34:46 decided to just start again Sep 10 01:38:56 gives me also a good way to playtest the buildingthetarball howto I am crafting ... Sep 10 02:23:34 just carved http://www.nslu2-linux.org/wiki/OpenSlug/BuildingTheTarball describing what I learned today Sep 10 02:23:47 please review/update/comment/whatever... Sep 10 02:25:27 hehe Sep 10 02:25:34 "may require an extended vacation" Sep 10 02:27:25 as compared to the "night out" mentioned for the cross-build somewhere else Sep 10 02:27:38 eFfeM: one thing to note for yourself and possibly the wiki, all sources used in the autobuilds are available at http://sources.nslu2-linux.org/sources . Sep 10 02:27:59 Its supposed to fallback to get stuff from there; but YMMV Sep 10 02:28:10 ok, didn't know that Sep 10 02:28:49 still need to add some more on tmp in the wiki, but I restarted the build and it is still running so it will take a few more hours until it is done Sep 10 02:29:17 http://sources.nslu2-linux.org/sources/ : directory listing not allowed Sep 10 02:29:31 Yeah, you need to know what you want before you ask. :-) Sep 10 02:30:04 Also, for adding new packages to OE, I'm pretty sure koen can point you to the OE howto for that. :-) Sep 10 02:30:58 koen, can you add a few lines for that? Sep 10 02:32:06 Dont bug koen for that... hes a core OE dev and has already written lots of documentation; i was thinking more he can point you in the right direction. ;-) Sep 10 02:32:45 because documentation is best written by someone that is doing something for the first time. Sep 10 02:33:33 ah ok, np, just thought that the edit would be a ref to another howto and in that case adding it is probably less work than explaining it to someone else Sep 10 02:34:05 I agree with your doc comment. Such a person does make less assumptions that the reader will already know something. Sep 10 02:34:26 Does require a knowledgeable reviewer to check for correctness though Sep 10 02:35:36 there is a bitbake manual; but honestly, the best is to look at other packages and mimic them. Sep 10 02:35:39 http://bitbake.berlios.de/manual/ Sep 10 02:36:22 updated the openslug homepage to refer to the BuildingTheTarball page and moved the ref to the MasterMakefile to make clearer that this is the 3rd option (using the HEAD version) and not for building the tarball Sep 10 02:36:39 will make a change for bitbake Sep 10 02:57:06 when I install something with ipkg it always wants to do a Configuring coreutls Sep 10 02:57:25 this one then tries to link using update-alternatives but some of the link commands fail Sep 10 02:57:41 how can I get rid of this, do I need to link manually> Sep 10 02:57:47 you can work around that with 'ipkg flag installed coreutils' Sep 10 02:57:53 e.g. what I get is Sep 10 02:57:54 update-alternatives: Error: not linking //usr/bin/du to du.coreutils since //usr/bin/du exists and is not a link Sep 10 02:58:22 ok, thanks. Can I force these links to be made? **** ENDING LOGGING AT Sat Sep 10 02:59:56 2005