**** BEGIN LOGGING AT Sat Apr 23 23:59:57 2005 Apr 24 02:49:40 From the logs it's been very quiet in here the last couple of days. Apr 24 02:49:50 Anyone got any feedback on the 4.x README ? Apr 24 02:54:53 Tiersten: ping Apr 24 02:55:22 Tiersten: would you prefer that we make OE get the R25 to R29 patch from your site, or would you like us to copy it to nslu.sf.net? Apr 24 02:58:04 I inspected the readme Apr 24 02:59:03 but having sensed no feedback to my feedback, I did nothing. Apr 24 03:02:39 I donto think we want to base unslung on R29. Apr 24 03:03:12 the the USB disk hack really is a hack. Apr 24 03:03:20 for the Genesys chipset.. Apr 24 03:03:24 and no telnet. Apr 24 03:17:45 Speak of the devil.... Apr 24 03:33:34 dyoung-zzzz: did you give feedback but I didn't see it? Apr 24 03:33:50 and what USB disk hack (I haven't looked at the patch yet) Apr 24 03:36:05 So the fix for large transfer problems is simply to decrease the ixp queue dispatch timer rate? Apr 24 03:36:54 Basically its the Genesys patch, excpet it does it all the time and doesnt sense if the buffer change is required or not Apr 24 03:37:19 yeah, I saw that one, and we would just use our patch instead, right? Apr 24 03:37:24 and the ixp polling interval was changed.. Apr 24 03:37:39 to 2000 from 4000. Apr 24 03:37:49 I dont know exactly what all that affects Apr 24 03:38:04 wasn't it from 4000 to 2000 ? Apr 24 03:38:13 (i.e. less often) Apr 24 03:38:21 thats what I jusut said? Apr 24 03:38:33 oops, sorry. Apr 24 03:38:45 that's exactly what you wrote, but not what I read :-) Apr 24 03:38:51 heh Apr 24 03:38:51 heh Apr 24 03:39:22 IMHO, the code isnt changed enough in a positive way to want to use it as the unslung base. Apr 24 03:39:33 and theres no telnet. Apr 24 03:39:44 so that's the only part of that patch which could affect the stability of large transfers. Unless the change is in one of the linksys binaries. Apr 24 03:39:56 we can easily keep the telnet Apr 24 03:40:43 probably? Apr 24 03:41:04 I havnt used R29 yet; so i dunno if the large transfer is really fixed or not Apr 24 03:44:41 Hmm, still only 16 Unslung 4.x alpha testers. Apr 24 03:45:01 that's a bit disappointing. Apr 24 03:45:56 I was planning to flash that new alpha on the prodslug2 since its currently busted with the last 4.x alpha. Apr 24 03:46:05 maybe last last... Apr 24 03:46:27 but I havnt gotten to turning it on yet. Apr 24 03:46:54 so does that mean that 3.18 was good enough for the masses? Apr 24 03:47:15 Or have folks found another toy to play with? Apr 24 03:47:23 Well, I had to reimage my laptop (planned, not emergency, and no data loss) this weekend, so I'm taking the opportunity to update to the latest CoLinux which is 2.6-based. Apr 24 03:47:43 dyoung-zzzz: is the README up to scratch? Apr 24 03:47:45 rwhitby, I just installed that one. Apr 24 03:47:58 rwhitby, the README looks fine nto me. Apr 24 03:48:15 I want to put the changelog in NOTES into CHANGELOG though. Apr 24 03:48:43 so the only possibly outstanding thing is conversion and migration from 3.x conf partition to 4.x data partition. Apr 24 03:48:45 I gotta look at it again though since I dont trust my judgement from that day. Apr 24 03:49:15 yeah, we can separate out CHANGELOG. We need to update that too. And we need to flesh out the UnslungFeatures wiki page. Apr 24 03:49:19 For opt eh. Yeah; I was thinking about that earlier. Apr 24 03:50:06 Do we need a /sbin/slingover ? Apr 24 03:50:56 I dunno, is it that hard to mv /share/hdd/conf/opt /share/hdd/data ? Apr 24 03:51:11 slingover /share/hdd/conf /share/hdd/data .... run it after unsling, and it moves /opt and /usr/lib/ipkg and /unslung Apr 24 03:51:14 and fiddle the symlink9s) ? Apr 24 03:51:35 hmm. Apr 24 03:51:53 would also have to update /usr/bin/perl and /bin/bash, and any other special symlinks we put in the rootfs Apr 24 03:52:26 what does /usr/bin/perl link to now? Apr 24 03:52:37 I would think it would link to /opt/bin/perl ... Apr 24 03:52:48 (but i dont have a booted slug to check on) Apr 24 03:52:57 yep Apr 24 03:53:14 we put in that symlink when perl is installed Apr 24 03:53:21 Okay, so no problem right? Apr 24 03:53:28 as long as /opt points to the right place Apr 24 03:53:55 yeah, just have to remember to put the symlinks in, so that people don't need to reinstall the packages Apr 24 03:54:17 Ah, I get it; you mean as a upgrade issue. Apr 24 03:54:25 yeah Apr 24 03:54:39 that's what slingover would do Apr 24 03:55:56 Can we easily detect what packages with special links are already (allegedly) installed? Apr 24 03:56:13 and just run the postinst for those packages? Apr 24 03:57:15 as far as I know it's just /bin/bash and /usr/bin/perl, so we'd just check for the exe's under /opt and link it if they are there Apr 24 05:20:11 Drat. Apr 24 05:20:20 hnl->yow is really expensive in July. Apr 24 05:36:11 03rwhitby * 10unslung/Makefile: Fixed the name of phpmyadmin. Apr 24 05:41:18 Hi, I am new to nslu and would like to compile svn as it does not have apache support at the moment Apr 24 05:41:38 unslung or openslug? Apr 24 05:41:46 for the unslung Apr 24 05:42:01 the problem is that I never used crosstool or anything like that Apr 24 05:42:12 I installed debian sarge and crosstool today Apr 24 05:42:19 and everything is set up now Apr 24 05:42:28 the problem is I do not know how to proceed Apr 24 05:42:33 have you checked out the unslung cvs ? Apr 24 05:42:38 I downloaded the svn sources Apr 24 05:42:50 and know I would like to use the created crosstool compilers Apr 24 05:43:01 yes, I checked out unslung cvs Apr 24 05:43:08 why do I need that? Apr 24 05:43:15 and read the wiki page on how to add a package to Unslung ? Apr 24 05:43:19 yes Apr 24 05:43:31 and looked at template.mk ? Apr 24 05:43:36 no Apr 24 05:43:39 what is that? Apr 24 05:43:59 it is explained on the wiki page about how to add a package to Unslung - you said you read that? Apr 24 05:44:14 okay, I browsed it... Apr 24 05:44:25 I will look into that Apr 24 05:44:30 thanks for the hint! Apr 24 05:44:31 ok, ask again after you have read it twice :-) Apr 24 05:44:45 ok, thanks again! Apr 24 05:44:53 np Apr 24 05:45:47 when you're ready to submit it to the CVS repository, send me svn.mk file to the mailing list, with your sf.net id, and we will give you CVS write access so you can contribute the package. Apr 24 05:46:01 s/send me/send the/ Apr 24 05:52:07 ok, but I guess it is still a long way to go for me... Apr 24 05:52:59 you'll be surprised. some packages take all of five minutes once you have read template.mk Apr 24 05:53:46 jacques: heard anything about bkbits being down? Apr 24 05:54:06 wojtek : but some takes longer :( Apr 24 05:54:15 hehe Apr 24 05:54:37 as this will be my first time to compile packages at all I guess it will take some time Apr 24 05:54:58 jacques: : nm, looks like it's local to me :-) Apr 24 06:00:35 03rwhitby 07 * r1.3264 10openembedded/packages/meta/openslug-packages.bb: Apr 24 06:00:35 Merge bk://nslu2-linux@nslu2-linux.bkbits.net/openembedded Apr 24 06:00:35 into home.(none):/home/bitbake/openembedded Apr 24 06:00:41 03rwhitby 07 * r1.3225.1.1 10openembedded/packages/ (2 files in 2 dirs): Added bridge-utils and sysfsutils to OpenSlug. Added the NOTES file to the Unslung image. Apr 24 06:12:58 I am looking to run php with a web server, what's better apache or thttpd? Apr 24 06:13:38 I am using it to run a php front end for mpd Apr 24 06:14:19 will I see better preformance with thttpd? Apr 24 06:16:03 dunno. probably depends on whether you have long-lasting sessions, or lots of little requests. Apr 24 06:16:16 thttpd does everything in a single thread. Apr 24 06:18:29 everything in a single thread would mean the lots of little requests would be better for thttpd? Apr 24 06:20:36 depends if they are sequential (like following a trail of pages) or parallel (like lots of images on a page) Apr 24 06:21:28 can I have php installed for both webservers without any problems? Apr 24 06:23:16 should be able to, but that is very new, so there could be bugs. Apr 24 06:27:05 I will try it, the easiest thing is probably just empirically compare the two for preformance Apr 24 06:28:41 yep Apr 24 08:22:48 Hi again, I am having some problems with my svn build Apr 24 08:23:06 I am really new to building packages on Linux and nslu2 Apr 24 08:23:29 I have to change some configuration for the apr library Apr 24 08:23:44 every time I change something in a file named configure.in Apr 24 08:23:59 and do a make svn afterward my changes are undone Apr 24 08:24:11 so where do I have to do those changes to make them permantent? Apr 24 08:24:25 I guess this is common to all make builds...? Apr 24 08:24:58 sorry, apr=Apache portable runtime Apr 24 08:25:45 hi wojtek, we usually put the change in sources/package-name/configure.in.patch Apr 24 08:26:26 and relying on make unpack to expand a new tree, applying the patches cleanly Apr 24 08:27:02 ok, so the sources get unpacked and are overriding my changes Apr 24 08:27:06 is that right? Apr 24 08:27:16 yes Apr 24 08:27:33 can you give me a quick hint how to do a patch file? Apr 24 08:27:42 s/do/create/ Apr 24 08:28:30 just do "diff -u package-orig/filename package/filename > ../sources/package/configure.in.patch" Apr 24 08:28:50 assuming you save a tree as package-orig Apr 24 08:28:52 cool, I'll try thank, thank you VERY MUCH for your help! Apr 24 08:28:54 and you're at builds Apr 24 08:29:07 u r welcome Apr 24 08:29:54 oh, you do need to list configure.in.patch as a patch to apply in package.mk Apr 24 08:30:21 okay, let me try this Apr 24 08:34:18 eno-away: I see a SVN_PATCHES directive in my package.mk Apr 24 08:34:29 is this the place where I sould put my patch file name? Apr 24 08:34:43 does it have to be gzipped or anything like that? Apr 24 08:35:27 s/SVN_PATCHES/MYPACKAGE_PATCHES/ Apr 24 08:35:30 yes, that's the place, just plain text diff file Apr 24 08:35:50 can I leave the patch file in my destination build directory? Apr 24 08:35:56 wojtek: once you have created your patch, create a svn subdir under sources/ Apr 24 08:36:01 and put your patch in Apr 24 08:36:06 okay Apr 24 08:36:12 I'll do that Apr 24 08:36:18 thanks for the great support!!!!!!! Apr 24 08:36:30 It's my first time I do something like that Apr 24 08:36:43 and without your help it would take much more time, THANK YOU! Apr 24 08:36:45 make sure the "cat patch-file | patch -p1" the -p parameter needs to match Apr 24 08:36:55 if you look under sources/ dir, you'll notice there's almost a dir per package. each dir may contains patch for the appropriate package Apr 24 08:37:36 eno-away: "cat patch-file | patch -p1" - where do I have take care of that? Apr 24 08:38:02 man patch, you can find what the -p parameter does Apr 24 08:38:26 basically strips away the number of leading path component from the patch file Apr 24 08:38:40 the cat SVN_PATCHES should be located in you svn.mk Apr 24 08:39:52 if you make the patch under unslung/builds/, then it usually should be -p1 Apr 24 08:40:18 if you make the patch under unslung/builds/package/, then it usually should be -p0 Apr 24 08:40:37 I am confused... Apr 24 08:40:54 I copied that patch file to sources/svn Apr 24 08:41:07 this in the content of the file: Apr 24 08:41:19 only the first line plz Apr 24 08:41:41 1041c1041 Apr 24 08:41:58 hummm.. the second one then ;) Apr 24 08:42:10 < AC_FUNC_SETPGRP Apr 24 08:42:21 --- Apr 24 08:42:25 hmm, did you use diff -u or just diff? Apr 24 08:42:33 uahhhh.... Apr 24 08:42:36 okay Apr 24 08:42:38 well, this is not unidied. Make diff -uN Apr 24 08:42:59 s/unidied/unified Apr 24 08:44:48 what does unified mean in context of diff? Apr 24 08:45:03 now the patch file looks much different Apr 24 08:45:13 it says something like this: Apr 24 08:45:15 it gives you context of the diff Apr 24 08:45:32 unified == more human readable Apr 24 08:45:43 --- configure.in 2005-04-01 15:44:09.000000000000000... Apr 24 08:46:01 but on the second line my temporary configure.test is mentioned Apr 24 08:46:06 is that correct? Apr 24 08:46:22 good Apr 24 08:46:33 you should applied (that's what I do), like eno told you : diff -uN svn-orig/configure svn-patched/configure Apr 24 08:46:55 where svn-orig is the original source of svn and svn-patched is where you make your change Apr 24 08:47:15 okay, I'll do this in the builds directory... Apr 24 08:47:44 sorry - I feel like a real stupid beginner - but I am... Apr 24 08:47:46 do this is a temp directory as it's only needed for creating your pacth file Apr 24 08:47:47 if you do that, you will see the first two lines in your patch file change Apr 24 08:48:02 Like I'm still... Apr 24 08:50:03 the more you learn, the more to learn Apr 24 08:50:14 hehe Apr 24 08:50:24 but it's fun Apr 24 08:52:01 that's right Apr 24 08:52:04 now i did that Apr 24 08:52:17 my patchfile still contains the patch to the tmp dir on the second line Apr 24 08:52:39 do I have to do this "cat" magic mentioned earlies now? Apr 24 08:53:46 sorry: it contains the path to the temp dir Apr 24 08:53:48 the "cat patch-files | patch -p1" line should be already in the unpack section of your .mk file Apr 24 08:54:33 the key here is that the number of leading path components should match the -p parameter of patch Apr 24 08:55:16 I'll post you the second line Apr 24 08:55:23 if you did the patch from the builds/ directory, and the cat line has -p1, usu. you're okay Apr 24 08:55:51 the first two lines please Apr 24 08:56:08 --- configure.in 2005-04-01...... Apr 24 08:56:29 +++ /tmp/svn-patched-apr/configure.in 2005-04-24...... Apr 24 08:56:56 the file is in my sources/svn/ directory now Apr 24 08:56:57 that might have problem when applying patch Apr 24 08:57:10 so what can I do about that? Apr 24 08:57:46 looking from the patch program's POV, the number of leading path components of the first two lines should match Apr 24 08:58:23 okay, I see that Apr 24 08:58:31 but how do I achieve this? Apr 24 08:59:15 either save svn/ tree as svn-orig/, or save configure.in as configure.in-orig, redo the diff from builds/ dir Apr 24 09:00:54 sorry, but now I have no idea about what to do next Apr 24 09:01:13 I created that patch being in my builds/svn/apr directory Apr 24 09:01:17 is that wrong? Apr 24 09:01:54 where is the configure.in originally? Apr 24 09:02:10 in the builds/svn/apr Apr 24 09:02:27 (after issuing a make svn) Apr 24 09:03:57 so its in the apr directory of the original src distribution of subversion Apr 24 09:04:10 ok, "cd builds/svn/apr; cp configure.in configure.in.orig; editor configure.in; cd ../..; diff -u svn/apr/configure.in.orig svn/apr/configure.in > ../sources/svn/apr-configure.in.patch" Apr 24 09:07:16 okay Apr 24 09:07:18 did that Apr 24 09:07:25 now the first lines say this Apr 24 09:07:35 --- svn/apr/configure.in.orig 2005.... Apr 24 09:07:47 +++ svn/apr/configure.in 2005...... Apr 24 09:08:08 great, that should work ok Apr 24 09:08:15 is this correct? I am wondering because the .orig file won't be in the original distribution Apr 24 09:08:21 when someone else installs it Apr 24 09:09:02 did you save the pristine configure.in somewhere? Apr 24 09:09:18 use it in the place of configure.in.orig Apr 24 09:11:47 so I have to edit the first line of the patchfile and change configure.in.orig to configure.in? Apr 24 09:11:54 is that what you are saying? Apr 24 09:13:24 not quite. So we need the configure.in that comes with original svn tar ball, we also need your patched configure.in Apr 24 09:13:39 let's say we call the first one configure.in.orig Apr 24 09:13:51 let's call your changed one configure.in.patched Apr 24 09:14:08 okay Apr 24 09:14:19 the patch should contain "diff -u configure.in.orig configure.in.patched" Apr 24 09:15:55 okay, so it was wrong to use the copied configure.in.orig file? Apr 24 09:15:55 the second issue is to match the number of leading path components in the patch file with the -p parameter of the patch command Apr 24 09:16:29 sorry, my bad in assuming your svn tree is original Apr 24 09:16:50 okay, I'll restart this again Apr 24 09:17:03 in your case, we should not cp configure.in Apr 24 09:17:04 I'll create a new builds/svn directory first Apr 24 09:17:17 ...but copy the whole tree to temp? Apr 24 09:17:30 and then diff? Apr 24 09:17:54 it's easier if you copy unpatched builds/svn to builds/svn-orig Apr 24 09:18:38 okay, just a second... Apr 24 09:20:30 ok, I did this, now I have a svn and svn-orig dir in builds Apr 24 09:20:44 I will edit the configure.in now in the svn dir Apr 24 09:21:07 i just looked at svn.mk, and it uses patch -p2 Apr 24 09:21:40 okay, so do I have to adjust something? Apr 24 09:21:40 and zcat Apr 24 09:21:59 I am not using the provided patches Apr 24 09:22:01 to match that, do your diff from unslung/ Apr 24 09:22:18 as I am trying to create a new svn package Apr 24 09:23:07 do you use make/svn.mk from CVS? or did you create your own from make/template.mk? Apr 24 09:23:48 I use the one from cvs but commented out the SVN_PATCHES section Apr 24 09:24:15 I am now in the unsling dir and will create the patch Apr 24 09:25:30 ok, you can replace the SVN_PATCHES with your patch, you also need to change the zcat ... | patch line, to match your .patch file Apr 24 09:26:32 something like "SVN_PATCHES=$(SVN_SOURCE_DIR)/configure.in.patch" Apr 24 09:26:58 I created the diff patch Apr 24 09:27:05 the first two lines again: Apr 24 09:27:30 builds/svn-orig/apr/configure.in 2005[...] Apr 24 09:27:51 +++ builds/svn/apr/configure.in 2005[...] Apr 24 09:27:55 is this correct? Apr 24 09:28:04 and around line 84 of svn.mk, change it to "cat $(SVN_PATCHES) | patch -d $(BUILD_DIR)/$(SVN_DIR) -p2" Apr 24 09:28:15 looks correct Apr 24 09:28:37 ...still wondering about the mentioned "svn-orig" directory Apr 24 09:28:44 ...hope it will be okay Apr 24 09:29:17 when you do make, do one step at a time Apr 24 09:29:44 to start clean, do "make svn-dirclean" Apr 24 09:29:57 to retrieve tarball, do "make svn-source" Apr 24 09:30:18 to unpack, apply patches and configure, do "make svn-unpack" Apr 24 09:39:36 great Apr 24 09:39:40 it works now Apr 24 09:39:45 cool Apr 24 09:40:16 so the directory entries in my patch file (like "svn-orig") won't interfere when someone else will use the package? Apr 24 09:41:12 a/b/c/configure.in only the number of "/" and the final configure.in matter Apr 24 09:41:40 okay, now I got it Apr 24 09:41:45 thanks for your help Apr 24 09:41:57 you tell patch command what current directory to use, and how many leading '/' to strip Apr 24 09:42:35 my package does not compile thought... but this is another problem ;-) Apr 24 09:43:39 r u working on mod_dav_svn? Apr 24 09:43:55 yes, how do you know? Apr 24 09:44:11 http://ibot.rikers.org/%23nslu2-linux/20050423.html.gz the IRC log Apr 24 09:44:50 hehe Apr 24 09:45:22 good luck and be sure to contribute back when you get it working Apr 24 09:45:35 I would like to get it running, so I contacted the original maintainer Apr 24 09:45:45 and hope that he can help me a bit Apr 24 09:46:14 he created the package for 1.1.1 and I would like to see 1.1.4 running Apr 24 09:46:19 which is the current versio Apr 24 09:46:43 n. and of course mod_dav_svn... :) Apr 24 09:46:51 i c Apr 24 09:47:37 i don't see anybody listed as svn maintainer Apr 24 09:48:18 i take it back, it's in sources/svn/control Apr 24 09:48:57 do you think it would be easier to compile directly on the nslu2? Apr 24 09:49:17 no, the slug is pretty slow Apr 24 09:49:56 resolving configuration issue to make it cross compile is worthwhile Apr 24 09:50:10 i see that Apr 24 09:51:01 especially svn is listed as cross packages already Apr 24 09:51:22 okay, I'll do the best I can Apr 24 09:51:55 so maybe take a look at the existing sources/svn/svn.patch.gz would help Apr 24 09:52:07 yes, I am now reading it Apr 24 09:52:12 and trying to understand Apr 24 09:52:23 it's quite a big patch... Apr 24 09:57:08 yeah, it can probably win the award of biggest patch of the year Apr 24 09:57:59 I will create patch files for each file edited Apr 24 09:58:10 isn't this a better approach Apr 24 09:58:11 ? Apr 24 09:59:44 i would think so too, and i dislike gz patch Apr 24 10:08:29 another patch related question Apr 24 10:08:39 does the date on the two first lines matter? Apr 24 19:47:01 hello? Apr 24 22:58:30 03bzhou * 10unslung/Makefile: libesmtp & esmtp (cross packages) ready for testing Apr 24 23:04:31 03bzhou * 10unslung/make/getmail.mk: added getmail (A fetchmail replacement with qmail-like Maildir and external MDA delivery in Python) **** ENDING LOGGING AT Sun Apr 24 23:59:56 2005