From vapier at gentoo.org Mon Jan 1 01:28:07 2007 From: vapier at gentoo.org (Mike Frysinger) Date: Mon, 1 Jan 2007 04:28:07 -0500 Subject: stty has warnings -> build failure Message-ID: <200701010428.08618.vapier@gentoo.org> the stty mode_info struct uses a short for the mask ... on my ppc32 system though, some of the masks actually overflow this value and i get warnings in particular, the VTDLY stuff expands as: VT1 00200000 and that number won't fit in a short on a 32bit machine -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20070101/bf3ea8dd/attachment.pgp From vda.linux at googlemail.com Mon Jan 1 07:20:34 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Mon, 1 Jan 2007 16:20:34 +0100 Subject: stty has warnings -> build failure In-Reply-To: <200701010428.08618.vapier@gentoo.org> References: <200701010428.08618.vapier@gentoo.org> Message-ID: <200701011620.34417.vda.linux@googlemail.com> On Monday 01 January 2007 10:28, Mike Frysinger wrote: > the stty mode_info struct uses a short for the mask ... on my ppc32 system > though, some of the masks actually overflow this value and i get warnings > > in particular, the VTDLY stuff expands as: > VT1 00200000 > > and that number won't fit in a short on a 32bit machine > -mike Fair enough. I think I will change it like this: struct mode_info { const char *name; /* Name given on command line */ char type; /* Which structure element to change */ char flags; /* Setting and display options */ tcflag_t mask; /* Other bits to turn off for this mode */ tcflag_t bits; /* Bits to set for this mode */ }; (i.e. last two fields are changed to tcflag_t). Does it work for you? -- vda From vda.linux at googlemail.com Mon Jan 1 07:24:42 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Mon, 1 Jan 2007 16:24:42 +0100 Subject: trying to build dash: awk and sort bugs uncovered Message-ID: <200701011624.43014.vda.linux@googlemail.com> In case some awk guru is around: I tried to build dash (Debian ash) and found the following. (The same text is also attached to prevent tab mangling: testcases have tabs in a few places)! awk: trouble with positional variables? echo -n "\ 3 ALIAS ALIASCMD 4 BG BGCMD " | awk '{ printf "#define %s (builtincmd + %d)\n", $3, $1}' -bbox +coreutils: -#define ALIASCMD3 (builtincmd + 0) -#define BGCMD4 (builtincmd + 0) +#define ALIASCMD (builtincmd + 3) +#define BGCMD (builtincmd + 4) awk: "awk: cmd. line:4: Too few arguments for builtin" awk '{ opt = "" if (NF > 2) { opt = substr($2, 2) $2 = $3 } printf "\t{ \"%s\", %s, %d },\n", $1, $2, (opt ~ /s/) + (opt ~ /[su]/) * 2 + (opt ~ /a/) * 4 }' input is: : -s truecmd . -s dotcmd [ testcmd alias -au aliascmd bg -u bgcmd break -s breakcmd ... chokes on "a a a", works on "a a" but output is not correct: -bbox +coreutils: - { "aa", , 0 }, + { "a", a, 0 }, sort -u -k 3.3: incorrect workings of -u[nigue] option: -bbox +coreutils: 3 alias aliascmd 4 bg bgcmd 5 break breakcmd - 9 continue breakcmd 6 cd cdcmd - 7 chdir cdcmd 8 command commandcmd 1 . dotcmd 10 echo echocmd sort -k 1,1: doesn't seem to be important: -bbox +coreutils: -. -s dotcmd : -s truecmd +. -s dotcmd [ testcmd alias -au aliascmd bg -u bgcmd -- vda -------------- next part -------------- awk: trouble with positional variables? echo -n "\ 3 ALIAS ALIASCMD 4 BG BGCMD " | awk '{ printf "#define %s (builtincmd + %d)\n", $3, $1}' -bbox +coreutils: -#define ALIASCMD3 (builtincmd + 0) -#define BGCMD4 (builtincmd + 0) +#define ALIASCMD (builtincmd + 3) +#define BGCMD (builtincmd + 4) awk: "awk: cmd. line:4: Too few arguments for builtin" awk '{ opt = "" if (NF > 2) { opt = substr($2, 2) $2 = $3 } printf "\t{ \"%s\", %s, %d },\n", $1, $2, (opt ~ /s/) + (opt ~ /[su]/) * 2 + (opt ~ /a/) * 4 }' input is: : -s truecmd . -s dotcmd [ testcmd alias -au aliascmd bg -u bgcmd break -s breakcmd ... chokes on "a a a", works on "a a" but output is not correct: -bbox +coreutils: - { "aa", , 0 }, + { "a", a, 0 }, sort -u -k 3.3: incorrect workings of -u[nigue] option: -bbox +coreutils: 3 alias aliascmd 4 bg bgcmd 5 break breakcmd - 9 continue breakcmd 6 cd cdcmd - 7 chdir cdcmd 8 command commandcmd 1 . dotcmd 10 echo echocmd sort -k 1,1: doesn't seem to be important: -bbox +coreutils: -. -s dotcmd : -s truecmd +. -s dotcmd [ testcmd alias -au aliascmd bg -u bgcmd From vda.linux at googlemail.com Mon Jan 1 16:01:15 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 01:01:15 +0100 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701011624.43014.vda.linux@googlemail.com> References: <200701011624.43014.vda.linux@googlemail.com> Message-ID: <200701020101.15822.vda.linux@googlemail.com> On Monday 01 January 2007 16:24, Denis Vlasenko wrote: > In case some awk guru is around: > > I tried to build dash (Debian ash) and found the following. > (The same text is also attached to prevent tab mangling: > testcases have tabs in a few places)! sort -u fixed, awk parsing in non-C locales fixed. Changes are committed to svn. -- vda From vapier at gentoo.org Mon Jan 1 18:54:37 2007 From: vapier at gentoo.org (Mike Frysinger) Date: Mon, 1 Jan 2007 21:54:37 -0500 Subject: stty has warnings -> build failure In-Reply-To: <200701011620.34417.vda.linux@googlemail.com> References: <200701010428.08618.vapier@gentoo.org> <200701011620.34417.vda.linux@googlemail.com> Message-ID: <200701012154.38644.vapier@gentoo.org> On Monday 01 January 2007 10:20, Denis Vlasenko wrote: > On Monday 01 January 2007 10:28, Mike Frysinger wrote: > > the stty mode_info struct uses a short for the mask ... on my ppc32 > > system though, some of the masks actually overflow this value and i get > > warnings > > > > in particular, the VTDLY stuff expands as: > > VT1 00200000 > > > > and that number won't fit in a short on a 32bit machine > > Fair enough. I think I will change it like this: > > struct mode_info { > const char *name; /* Name given on command line */ > char type; /* Which structure element to change */ > char flags; /* Setting and display options */ > tcflag_t mask; /* Other bits to turn off for this mode */ > tcflag_t bits; /* Bits to set for this mode */ > }; > > (i.e. last two fields are changed to tcflag_t). > > Does it work for you? a quick test shows that this OK for me ... thanks ! -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20070101/23eae321/attachment.pgp From rob at landley.net Mon Jan 1 20:03:13 2007 From: rob at landley.net (Rob Landley) Date: Mon, 1 Jan 2007 23:03:13 -0500 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701011624.43014.vda.linux@googlemail.com> References: <200701011624.43014.vda.linux@googlemail.com> Message-ID: <200701012303.16977.rob@landley.net> On Monday 01 January 2007 10:24 am, Denis Vlasenko wrote: > In case some awk guru is around: His email is at the top of awk.c. > I tried to build dash (Debian ash) and found the following. While trying to build what actual packages? (What actually _broke_?) > sort -u -k 3.3: incorrect workings of -u[nigue] option: 3,3 is a standard, 3.3 is a gnu extension. That said I'm under the vague impression I implemented it at some point. However, what you gave isn't a test I can reproduce. > sort -k 1,1: doesn't seem to be important: > -bbox +coreutils: > -. -s dotcmd > : -s truecmd > +. -s dotcmd Look at sort.tests and give me something I can reproduce, please? Rob -- "Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery From rep.nop at aon.at Tue Jan 2 01:07:18 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Tue, 2 Jan 2007 10:07:18 +0100 Subject: svn commit: trunk/busybox: coreutils include modutils networking ne etc... In-Reply-To: <20061231185739.45EFA485A9@busybox.net> References: <20061231185739.45EFA485A9@busybox.net> Message-ID: <20070102090718.GA4615@aon.at> On Sun, Dec 31, 2006 at 10:57:39AM -0800, vda at busybox.net wrote: >Author: vda >Date: 2006-12-31 10:57:37 -0800 (Sun, 31 Dec 2006) >New Revision: 17117 > >Log: >stop using __u32 etc. uint32_t is there for a reason >Modified: trunk/busybox/include/platform.h >=================================================================== >--- trunk/busybox/include/platform.h 2006-12-31 12:14:16 UTC (rev 17116) >+++ trunk/busybox/include/platform.h 2006-12-31 18:57:37 UTC (rev 17117) >@@ -133,12 +133,12 @@ > #endif > > /* ---- Compiler dependent settings ------------------------- */ >-#ifndef __GNUC__ >-#if defined __INTEL_COMPILER >-__extension__ typedef __signed__ long long __s64; >-__extension__ typedef unsigned long long __u64; >-#endif /* __INTEL_COMPILER */ >-#endif /* ifndef __GNUC__ */ >+//#ifndef __GNUC__ >+//#if defined __INTEL_COMPILER >+//__extension__ typedef __signed__ long long __s64; >+//__extension__ typedef unsigned long long __u64; >+//#endif /* __INTEL_COMPILER */ >+//#endif /* ifndef __GNUC__ */ You can ditch these if there are no occurances of __{s,u}64 in the tree anymore. I may look into making it compile (again, as it worked before the move to Kbuild) with non-gcc sometime later this year, fwiw. >Modified: trunk/busybox/networking/libiproute/linux/pkt_sched.h That one is just a fallback copy and IIRC isn't really used, right? Should perhaps be rm'ed.. >=================================================================== >--- trunk/busybox/networking/libiproute/linux/pkt_sched.h 2006-12-31 12:14:16 UTC (rev 17116) >+++ trunk/busybox/networking/libiproute/linux/pkt_sched.h 2006-12-31 18:57:37 UTC (rev 17117) From rep.nop at aon.at Tue Jan 2 02:49:14 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Tue, 2 Jan 2007 11:49:14 +0100 Subject: svn commit: trunk/busybox: archival coreutils miscutils modutils ne etc... In-Reply-To: <200612302331.17248.vda.linux@googlemail.com> References: <20061230175704.E11864858C@busybox.net> <200612302326.59993.yann.morin.1998@anciens.enib.fr> <200612302331.17248.vda.linux@googlemail.com> Message-ID: <20070102104914.GA6466@aon.at> On Sat, Dec 30, 2006 at 11:31:17PM +0100, Denis Vlasenko wrote: >On Saturday 30 December 2006 23:26, Yann E. MORIN wrote: >> On Saturday 30 December 2006 185, vda at busybox.net wrote: >> > done a dozen of randconfig test. guess what? ALL failed... May i point you at http://busybox.net/~aldot/bb/mk.busybox.sh I just updated it to version 0.5d Usage: $ mkdir -p /tmp/scratch $ cd /tmp/scratch $ ./mk.busybox.sh 2>&1 >&1 foo.log & even make clean allnoconfig ; make is b0rked, btw ;) From vda.linux at googlemail.com Tue Jan 2 08:03:04 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 17:03:04 +0100 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701012303.16977.rob@landley.net> References: <200701011624.43014.vda.linux@googlemail.com> <200701012303.16977.rob@landley.net> Message-ID: <200701021703.04389.vda.linux@googlemail.com> On Tuesday 02 January 2007 05:03, Rob Landley wrote: > > I tried to build dash (Debian ash) and found the following. > > While trying to build what actual packages? (What actually _broke_?) dash is an ash ported to Debian. I tried to compile it on a system where /bin/sort and /bin/awk are symlinks to busybox. > > sort -u -k 3.3: incorrect workings of -u[nigue] option: > > 3,3 is a standard, 3.3 is a gnu extension. That said I'm under the vague > impression I implemented it at some point. IIRC manpage says -k N[.Nflags][,N[.Nflags]] and bbox indeed supports almost all of this. > However, what you gave isn't a > test I can reproduce. Sorry. See attached test script. For it was showing the following: --- 1 Tue Jan 2 16:54:50 2007 +++ 2 Tue Jan 2 16:54:50 2007 @@ -1,7 +1,9 @@ 10 echo echocmd 6 cd cdcmd + 7 chdir cdcmd 4 bg bgcmd 3 alias aliascmd 8 command commandcmd 1 . dotcmd 5 break breakcmd + 9 continue breakcmd In other words, our sort -u did not discard lines if _key_ (not entire line) is the same, while coreutils did. I will describe awk bug if you really want to know. Or else yust look at current awk.c - it has a comment on that in awk_main(). I already fixed sort -u and awk bugs. You won't see awk bug anyway because you are most probably in POSIX locale. -- vda -------------- next part -------------- A non-text attachment was scrubbed... Name: sort_u_bug Type: application/x-shellscript Size: 402 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20070102/d8492662/attachment.bin From vda.linux at googlemail.com Tue Jan 2 08:15:57 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 17:15:57 +0100 Subject: svn commit: trunk/busybox: coreutils include modutils networking ne etc... In-Reply-To: <20070102090718.GA4615@aon.at> References: <20061231185739.45EFA485A9@busybox.net> <20070102090718.GA4615@aon.at> Message-ID: <200701021715.57470.vda.linux@googlemail.com> On Tuesday 02 January 2007 10:07, Bernhard Fischer wrote: > On Sun, Dec 31, 2006 at 10:57:39AM -0800, vda at busybox.net wrote: > >Author: vda > >Date: 2006-12-31 10:57:37 -0800 (Sun, 31 Dec 2006) > >New Revision: 17117 > > > >Log: > >stop using __u32 etc. uint32_t is there for a reason > > >Modified: trunk/busybox/include/platform.h > >=================================================================== > >--- trunk/busybox/include/platform.h 2006-12-31 12:14:16 UTC (rev 17116) > >+++ trunk/busybox/include/platform.h 2006-12-31 18:57:37 UTC (rev 17117) > >@@ -133,12 +133,12 @@ > > #endif > > > > /* ---- Compiler dependent settings ------------------------- */ > >-#ifndef __GNUC__ > >-#if defined __INTEL_COMPILER > >-__extension__ typedef __signed__ long long __s64; > >-__extension__ typedef unsigned long long __u64; > >-#endif /* __INTEL_COMPILER */ > >-#endif /* ifndef __GNUC__ */ > >+//#ifndef __GNUC__ > >+//#if defined __INTEL_COMPILER > >+//__extension__ typedef __signed__ long long __s64; > >+//__extension__ typedef unsigned long long __u64; > >+//#endif /* __INTEL_COMPILER */ > >+//#endif /* ifndef __GNUC__ */ > > You can ditch these if there are no occurances of __{s,u}64 in the tree > anymore. Done. It remains only in (non-compilable) e2fsprogs/old_e2fsprogs/* > I may look into making it compile (again, as it worked before the move > to Kbuild) with non-gcc sometime later this year, fwiw. > > >Modified: trunk/busybox/networking/libiproute/linux/pkt_sched.h > > That one is just a fallback copy and IIRC isn't really used, right? > Should perhaps be rm'ed.. Yes, indeed. rm'ing... -- vda From iggarpe at terra.es Tue Jan 2 08:27:02 2007 From: iggarpe at terra.es (=?ISO-8859-1?Q?Ignacio_Garc=EDa_P=E9rez?=) Date: Tue, 02 Jan 2007 17:27:02 +0100 Subject: Error compiling 1.3.1 In-Reply-To: <200701021703.04389.vda.linux@googlemail.com> References: <200701011624.43014.vda.linux@googlemail.com> <200701012303.16977.rob@landley.net> <200701021703.04389.vda.linux@googlemail.com> Message-ID: <459A87D6.90209@terra.es> Hi, Busybox fails to compile with the attached .config configuration. The issue seems to be having disabled shadow passwords. When it is disabled, "shadow_.h" is *not included*, and cimpilation of libpwdgrp/pwd_grp.c requires the structure spwd which is defined in that include file. Nacho. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: .config Url: http://busybox.net/lists/busybox/attachments/20070102/d2db8b0a/attachment-0001.pot From vda.linux at googlemail.com Tue Jan 2 08:57:58 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 17:57:58 +0100 Subject: RFC: size-saving boolean type for busybox Message-ID: <200701021757.58697.vda.linux@googlemail.com> Hi people, I am thinking about introducing a boolean type for busybox. In C people usually use int, but it takes 4 bytes of data or bss when you have global flag variable. C99 has _Bool and on i386 it really takes 1 byte, at least with gcc 4.1.1 -Os, but I am hot sure about other versions and especially other arches. OTOH, there are CPUs which _really_ have hard time dealing with 1-byte integers (generated code is much bigger), so using uint8_t as "standard" type for a flag variable isn't ok. How about this? #if defined(i386) /* || defined(...) as needed */ typedef unsigned char bbool; #else typedef unsigned bbool; #endif -- vda From psmith at netezza.com Tue Jan 2 09:01:04 2007 From: psmith at netezza.com (Paul Smith) Date: Tue, 2 Jan 2007 12:01:04 -0500 Subject: cmdedit fix In-Reply-To: <20061223055742.GC3434@brightrain.aerifal.cx> References: <458A3A23.000001.07769@mfront8.yandex.ru> <200612230221.21764.vda.linux@googlemail.com> <20061223055742.GC3434@brightrain.aerifal.cx> Message-ID: <1167757264.29946.5.camel@psmithub> On Sat, 2006-12-23 at 00:57 -0500, Rich Felker wrote: > On Sat, Dec 23, 2006 at 02:21:21AM +0100, Denis Vlasenko wrote: > > On Thursday 21 December 2006 08:39, ybrnj80 wrote: > > > Hi, Denis! > > > > > > BB fails to compile cmdedit.c if certain features is not enebled > > > Patch attached > > > > Thanks, applied. > > I'm hoping we can replace cmdedit.c soon. I'm working on a tiny line > editing module with nearly as much functionality as readline (and more > in some respects) which should be similar size to BB cmdedit (at least > once I add #ifdefs to turn off some of the improved features). Have you thought about using Tecla? http://www.astro.caltech.edu/~mcs/tecla/index.html I've used it for a few projects in the past and found it very, very good. Not sure if it will meet your size requirements (I don't think it was originally created with that as a design goal. -- ----------------------------------------------------------------------------- Paul D. Smith http://netezza.com "Please remain calm--I may be mad, but I am a professional."--Mad Scientist ----------------------------------------------------------------------------- These are my opinions--Netezza takes no responsibility for them. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20070102/c10f7a9e/attachment.html From albrecht at rdi1.com Tue Jan 2 07:15:55 2007 From: albrecht at rdi1.com (Paul Albrecht) Date: Tue, 02 Jan 2007 10:15:55 -0500 Subject: possible httpd applet bug? Message-ID: <1167750955.13878.23.camel@albrecht.rdi1.com> I have a question about the way the busybox httpd applet reads cgi program output: Why is safe_read used rather than full_read? The problem with safe_read is you're not guaranteed the entire first line of cgi output on the first read so the applet doesn't handle the status line or content-type header correctly. Seems like if you don't want to read all the cgi output at once, then you should buffer the first line, but I don't think it makes much of a difference for busybox httpd. Paul Albrecht From ddaney at avtrex.com Tue Jan 2 09:40:24 2007 From: ddaney at avtrex.com (David Daney) Date: Tue, 02 Jan 2007 09:40:24 -0800 Subject: RFC: size-saving boolean type for busybox In-Reply-To: <200701021757.58697.vda.linux@googlemail.com> References: <200701021757.58697.vda.linux@googlemail.com> Message-ID: <459A9908.2080006@avtrex.com> Denis Vlasenko wrote: > Hi people, > > I am thinking about introducing a boolean type for busybox. > In C people usually use int, but it takes 4 bytes of data > or bss when you have global flag variable. > > C99 has _Bool and on i386 it really takes 1 byte, > at least with gcc 4.1.1 -Os, but I am hot sure about > other versions and especially other arches. > > OTOH, there are CPUs which _really_ have hard time > dealing with 1-byte integers (generated code is much bigger), > so using uint8_t as "standard" type for a flag variable isn't ok. > > How about this? > > #if defined(i386) /* || defined(...) as needed */ > typedef unsigned char bbool; > #else > typedef unsigned bbool; > #endif > Did you do a size comparison? How about adding a check for C99 and if true, just use _Bool? Also MIPS can efficiently access bytes, so you could add mips to the test. Thanks, David Daney From strange at nsk.no-ip.org Tue Jan 2 11:06:24 2007 From: strange at nsk.no-ip.org (Luciano Miguel Ferreira Rocha) Date: Tue, 2 Jan 2007 19:06:24 +0000 Subject: RFC: size-saving boolean type for busybox In-Reply-To: <200701021757.58697.vda.linux@googlemail.com> References: <200701021757.58697.vda.linux@googlemail.com> Message-ID: <20070102190624.GA21618@nsk.no-ip.org> On Tue, Jan 02, 2007 at 05:57:58PM +0100, Denis Vlasenko wrote: > Hi people, > > I am thinking about introducing a boolean type for busybox. > In C people usually use int, but it takes 4 bytes of data > or bss when you have global flag variable. > > C99 has _Bool and on i386 it really takes 1 byte, > at least with gcc 4.1.1 -Os, but I am hot sure about > other versions and especially other arches. What about subsequent declarations? Do they immediatly follow the byte? If not, then there's really no space saved. > OTOH, there are CPUs which _really_ have hard time > dealing with 1-byte integers (generated code is much bigger), > so using uint8_t as "standard" type for a flag variable isn't ok. And access is more costly, too. And if the data does get packed, then access to the following variables will be costly too, until the moment other bools realign them at 4 bytes. However, I'm not against defining and using a bool type. Then these things can be tested. -- lfr 0/0 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20070102/b399edb9/attachment.pgp From rep.nop at aon.at Tue Jan 2 11:26:55 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Tue, 2 Jan 2007 20:26:55 +0100 Subject: svn commit: trunk/busybox/util-linux In-Reply-To: <20070102164506.BD57C485D8@busybox.net> References: <20070102164506.BD57C485D8@busybox.net> Message-ID: <20070102192654.GB24482@aon.at> On Tue, Jan 02, 2007 at 08:45:06AM -0800, vda at busybox.net wrote: >Author: vda >Date: 2007-01-02 08:45:05 -0800 (Tue, 02 Jan 2007) >New Revision: 17132 > >Log: >silly style fixes > > >Modified: > trunk/busybox/util-linux/fdisk_osf.c > > >Changeset: >Modified: trunk/busybox/util-linux/fdisk_osf.c >=================================================================== >--- trunk/busybox/util-linux/fdisk_osf.c 2007-01-02 16:32:16 UTC (rev 17131) >+++ trunk/busybox/util-linux/fdisk_osf.c 2007-01-02 16:45:05 UTC (rev 17132) >+ puts(_("Command action")); Some misguided folk apparently removed the /* NLS crap. Wipe me! */ #define _(a) (a) from platform.h and put those silly defines back into individual .c files. Let's do away with these superfluous _("hohoho") stuff when you touch them, please.. >+ puts(_("\td\tdelete a BSD partition")); >+ puts(_("\te\tedit drive data")); >+ puts(_("\ti\tinstall bootstrap")); >+ puts(_("\tl\tlist known filesystem types")); >+ puts(_("\tm\tprint this menu")); >+ puts(_("\tn\tadd a new BSD partition")); >+ puts(_("\tp\tprint BSD partition table")); >+ puts(_("\tq\tquit without saving changes")); >+ puts(_("\tr\treturn to main menu")); >+ puts(_("\ts\tshow complete disklabel")); >+ puts(_("\tt\tchange a partition's filesystem id")); >+ puts(_("\tu\tchange units (cylinders/sectors)")); >+ puts(_("\tw\twrite disklabel to disk")); >+#if !defined(__alpha__) >+ puts(_("\tx\tlink BSD partition to non-BSD partition")); > #endif > } >@@ -475,8 +478,8 @@ > > snprintf(mesg, sizeof(mesg), _("Last %s or +size or +sizeM or +sizeK"), > str_units(SINGULAR)); From rob at landley.net Tue Jan 2 12:06:41 2007 From: rob at landley.net (Rob Landley) Date: Tue, 2 Jan 2007 15:06:41 -0500 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701021703.04389.vda.linux@googlemail.com> References: <200701011624.43014.vda.linux@googlemail.com> <200701012303.16977.rob@landley.net> <200701021703.04389.vda.linux@googlemail.com> Message-ID: <200701021506.41760.rob@landley.net> On Tuesday 02 January 2007 11:03 am, Denis Vlasenko wrote: > On Tuesday 02 January 2007 05:03, Rob Landley wrote: > > > I tried to build dash (Debian ash) and found the following. > > > > While trying to build what actual packages? (What actually _broke_?) > > dash is an ash ported to Debian. I tried to compile it > on a system where /bin/sort and /bin/awk are symlinks > to busybox. Haven't tried that one. > In other words, our sort -u did not discard lines if _key_ > (not entire line) is the same, while coreutils did. Huh. Which one is the correct behavior? (Rummage for susve spec...) -u Unique: suppress all but one in each set of lines having equal keys. If used with the -c option, check that there are no lines with duplicate keys, in addition to checking that the input file is sorted. So yeah, it's unique keys. My bad. :) > I will describe awk bug if you really want to know. Dmitry Zakharov does an excellent job maintaining awk for busybox, and his email's at the top of editors/awk.c. > Or else yust look at current awk.c - it has a comment on that > in awk_main(). > > I already fixed sort -u and awk bugs. *shrug* Life is good. > You won't see awk bug anyway because you are most probably > in POSIX locale. Yes. Since when does busybox support locales? Rob -- "Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery From vda.linux at googlemail.com Tue Jan 2 14:11:32 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 23:11:32 +0100 Subject: RFC: size-saving boolean type for busybox In-Reply-To: <459A9908.2080006@avtrex.com> References: <200701021757.58697.vda.linux@googlemail.com> <459A9908.2080006@avtrex.com> Message-ID: <200701022311.32763.vda.linux@googlemail.com> On Tuesday 02 January 2007 18:40, David Daney wrote: > Denis Vlasenko wrote: > > Hi people, > > > > I am thinking about introducing a boolean type for busybox. > > In C people usually use int, but it takes 4 bytes of data > > or bss when you have global flag variable. > > > > C99 has _Bool and on i386 it really takes 1 byte, > > at least with gcc 4.1.1 -Os, but I am hot sure about > > other versions and especially other arches. > > > > OTOH, there are CPUs which _really_ have hard time > > dealing with 1-byte integers (generated code is much bigger), > > so using uint8_t as "standard" type for a flag variable isn't ok. > > > > How about this? > > > > #if defined(i386) /* || defined(...) as needed */ > > typedef unsigned char bbool; > > #else > > typedef unsigned bbool; > > #endif > > Did you do a size comparison? Not yet. > How about adding a check for C99 and if true, just use _Bool? I do not trust that gcc's _Bool is 1 byte on all arches where it makes sense. I want busybox's headers to be in control whether bbool is a char or an int, not gcc's developer. Why gcc should not be trusted (yet): unsigned f(unsigned v) { return v/10; } gcc 4.1.1 -O2: movl $-858993459, %eax mull 4(%esp) shrl $3, %edx movl %edx, %eax ret gcc 4.1.1 -Os: movl 4(%esp), %eax movl $10, %edx movl %edx, %ecx xorl %edx, %edx divl %ecx ret gcc -O2 is not just faster - it's SMALLER too. !?? > Also MIPS can efficiently access bytes, so you could add mips to the test. Will do. -- vda From vda.linux at googlemail.com Tue Jan 2 14:13:12 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 23:13:12 +0100 Subject: Error compiling 1.3.1 In-Reply-To: <459A87D6.90209@terra.es> References: <200701011624.43014.vda.linux@googlemail.com> <200701021703.04389.vda.linux@googlemail.com> <459A87D6.90209@terra.es> Message-ID: <200701022313.12405.vda.linux@googlemail.com> On Tuesday 02 January 2007 17:27, Ignacio Garc?a P?rez wrote: > Hi, > > Busybox fails to compile with the attached .config configuration. > > The issue seems to be having disabled shadow passwords. When it is > disabled, "shadow_.h" is *not included*, and cimpilation of > libpwdgrp/pwd_grp.c requires the structure spwd which is defined in that > include file. busybox.net page has link to post-1.3.1 patches: 27 December, 2006 -- BusyBox 1.3.1 (stable) BusyBox 1.3.1. (patches) ^^^^^^^here Currently, there is exactly one patch - for this shadow.h problem. Does it help? -- vda From vda.linux at googlemail.com Tue Jan 2 14:18:03 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 23:18:03 +0100 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701021506.41760.rob@landley.net> References: <200701011624.43014.vda.linux@googlemail.com> <200701021703.04389.vda.linux@googlemail.com> <200701021506.41760.rob@landley.net> Message-ID: <200701022318.03140.vda.linux@googlemail.com> On Tuesday 02 January 2007 21:06, Rob Landley wrote: > > You won't see awk bug anyway because you are most probably > > in POSIX locale. > > Yes. Since when does busybox support locales? No sir, I didn't commit that sin! ;) It was done by someone else: busybox.c /* Set locale for everybody except 'init' */ if (ENABLE_LOCALE_SUPPORT && getpid() != 1) setlocale(LC_ALL, ""); This is practically all. It doesn't take much space. Now we need to disable it back in a few places (date, httpd, awk) for specific LC_xxx. -- vda From vda.linux at googlemail.com Tue Jan 2 14:27:12 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 23:27:12 +0100 Subject: RFC: size-saving boolean type for busybox In-Reply-To: <20070102190624.GA21618@nsk.no-ip.org> References: <200701021757.58697.vda.linux@googlemail.com> <20070102190624.GA21618@nsk.no-ip.org> Message-ID: <200701022327.12839.vda.linux@googlemail.com> On Tuesday 02 January 2007 20:06, Luciano Miguel Ferreira Rocha wrote: > On Tue, Jan 02, 2007 at 05:57:58PM +0100, Denis Vlasenko wrote: > > Hi people, > > > > I am thinking about introducing a boolean type for busybox. > > In C people usually use int, but it takes 4 bytes of data > > or bss when you have global flag variable. > > > > C99 has _Bool and on i386 it really takes 1 byte, > > at least with gcc 4.1.1 -Os, but I am hot sure about > > other versions and especially other arches. > > What about subsequent declarations? Do they immediatly follow the byte? > If not, then there's really no space saved. > > > OTOH, there are CPUs which _really_ have hard time > > dealing with 1-byte integers (generated code is much bigger), > > so using uint8_t as "standard" type for a flag variable isn't ok. > > And access is more costly, too. And if the data does get packed, then > access to the following variables will be costly too, until the moment > other bools realign them at 4 bytes. I mostly think about places like this one: ./util-linux/fsck_minix.c:static int repair, automatic, verbose, list, show, warn_mode, force; ./util-linux/fsck_minix.c:static int directory, regular, blockdev, chardev, links, symlinks, total; ./util-linux/fsck_minix.c:static int changed; /* flags if the filesystem has been changed */ ./util-linux/fsck_minix.c:static int errors_uncorrected; /* flag if some error was not corrected */ ./util-linux/fsck_minix.c:static int dirsize = 16; ./util-linux/fsck_minix.c:static int namelen = 14; ./util-linux/fsck_minix.c:static int termios_set; ./util-linux/fsck_minix.c:static int version2; ./util-linux/fsck_minix.c:static int name_depth; -- vda From rob at landley.net Tue Jan 2 14:30:51 2007 From: rob at landley.net (Rob Landley) Date: Tue, 2 Jan 2007 17:30:51 -0500 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701022318.03140.vda.linux@googlemail.com> References: <200701011624.43014.vda.linux@googlemail.com> <200701021506.41760.rob@landley.net> <200701022318.03140.vda.linux@googlemail.com> Message-ID: <200701021730.52156.rob@landley.net> On Tuesday 02 January 2007 5:18 pm, Denis Vlasenko wrote: > On Tuesday 02 January 2007 21:06, Rob Landley wrote: > > > You won't see awk bug anyway because you are most probably > > > in POSIX locale. > > > > Yes. Since when does busybox support locales? > > No sir, I didn't commit that sin! ;) It was done by someone else: > > busybox.c > /* Set locale for everybody except 'init' */ > if (ENABLE_LOCALE_SUPPORT && getpid() != 1) > setlocale(LC_ALL, ""); > > This is practically all. It doesn't take much space. > > Now we need to disable it back in a few places (date, httpd, awk) > for specific LC_xxx. What does this actually affect? (I'm curious. If we can foist locale support off on the C library with one or two lines, it's not necessarily bad to have it as a config option. But what does it do, swap out strcmp() with a different implementation?) Rob -- "Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery From vda.linux at googlemail.com Tue Jan 2 14:52:09 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Tue, 2 Jan 2007 23:52:09 +0100 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701021730.52156.rob@landley.net> References: <200701011624.43014.vda.linux@googlemail.com> <200701022318.03140.vda.linux@googlemail.com> <200701021730.52156.rob@landley.net> Message-ID: <200701022352.09766.vda.linux@googlemail.com> On Tuesday 02 January 2007 23:30, Rob Landley wrote: > On Tuesday 02 January 2007 5:18 pm, Denis Vlasenko wrote: > > On Tuesday 02 January 2007 21:06, Rob Landley wrote: > > > > You won't see awk bug anyway because you are most probably > > > > in POSIX locale. > > > > > > Yes. Since when does busybox support locales? > > > > No sir, I didn't commit that sin! ;) It was done by someone else: > > > > busybox.c > > /* Set locale for everybody except 'init' */ > > if (ENABLE_LOCALE_SUPPORT && getpid() != 1) > > setlocale(LC_ALL, ""); > > > > This is practically all. It doesn't take much space. > > > > Now we need to disable it back in a few places (date, httpd, awk) > > for specific LC_xxx. > > What does this actually affect? (I'm curious. If we can foist locale support > off on the C library with one or two lines, it's not necessarily bad to have > it as a config option. But what does it do, swap out strcmp() with a > different implementation?) doubles start printing comma (123,456), month names and perror messages are in selected language, date style also changes. Etc... -- vda From rob at landley.net Tue Jan 2 15:32:40 2007 From: rob at landley.net (Rob Landley) Date: Tue, 2 Jan 2007 18:32:40 -0500 Subject: trying to build dash: awk and sort bugs uncovered In-Reply-To: <200701022352.09766.vda.linux@googlemail.com> References: <200701011624.43014.vda.linux@googlemail.com> <200701021730.52156.rob@landley.net> <200701022352.09766.vda.linux@googlemail.com> Message-ID: <200701021832.40954.rob@landley.net> On Tuesday 02 January 2007 5:52 pm, Denis Vlasenko wrote: > > What does this actually affect? (I'm curious. If we can foist locale support > > off on the C library with one or two lines, it's not necessarily bad to have > > it as a config option. But what does it do, swap out strcmp() with a > > different implementation?) > > doubles start printing comma (123,456), month names and perror messages > are in selected language, date style also changes. Etc... Translation: this is foisted off entirely upon the C library and we don't personally have to care? I'm all for it... Rob -- "Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery From vda.linux at googlemail.com Tue Jan 2 15:38:01 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Wed, 3 Jan 2007 00:38:01 +0100 Subject: RFC: size-saving boolean type for busybox In-Reply-To: <459A9908.2080006@avtrex.com> References: <200701021757.58697.vda.linux@googlemail.com> <459A9908.2080006@avtrex.com> Message-ID: <200701030038.01695.vda.linux@googlemail.com> On Tuesday 02 January 2007 18:40, David Daney wrote: > > #if defined(i386) /* || defined(...) as needed */ > > typedef unsigned char bbool; > > #else > > typedef unsigned bbool; > > #endif > > Did you do a size comparison? After some thought I decided to call it "small[u]int" and converted fsck_minix. Result: check_zones2 230 231 +1 check_zones 213 214 +1 add_zone_ind2 80 81 +1 add_zone_ind 80 81 +1 add_zone_dind2 80 81 +1 version2 8 5 -3 verbose 24 21 -3 termios_set 4 1 -3 show 4 1 -3 repair 4 1 -3 read_block 232 229 -3 list 393 390 -3 force 4 1 -3 errors_uncorrected 4 1 -3 check_zone_nr2 122 119 -3 changed 4 1 -3 automatic 4 1 -3 write_block 600 594 -6 ask 184 178 -6 add_zone2 225 216 -9 add_zone 224 215 -9 fsck_minix_main 4120 4096 -24 recursive_check 1206 1179 -27 recursive_check2 1397 1361 -36 ------------------------------------------------------------------------------ (add/remove: 0/0 grow/shrink: 9/24 up/down: 37/-177) Total: -140 bytes From vda.linux at googlemail.com Tue Jan 2 17:31:15 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Wed, 3 Jan 2007 02:31:15 +0100 Subject: Does it make sense to reduce bss? Message-ID: <200701030231.15388.vda.linux@googlemail.com> Hi, Current svn with all options on has ~85k in bss. It is not a problem for MMU systems but NOMMU, I suppose, would benefit from smaller bss. I was removing largish bss users and mostly fixed big ones, but should I go after not-so-big ones too? For example: Attached patch moves 8k of fsck_minix's buffers from bss to xzalloc'ed space, but it costs ~150 bytes of code: function old new delta recursive_check2 1382 1451 +69 recursive_check 1169 1207 +38 check_zones 214 240 +26 check_zones2 231 253 +22 add_zone_ind2 81 102 +21 add_zone_ind 81 102 +21 add_zone_dind2 81 102 +21 add_zone2 216 223 +7 add_zone 215 222 +7 blockbuf - 4 +4 write_block 594 592 -2 check_zone_nr2 119 117 -2 die 46 40 -6 write_super_block 117 106 -11 fsck_minix_main 4035 3990 -45 super_block_buffer 2048 1024 -1024 static.blk 7168 - -7168 ------------------------------------------------------------------------------ (add/remove: 1/1 grow/shrink: 11/6 up/down: 251/-8258) Total: -8022 bytes Opinions? -- vda -------------- next part -------------- A non-text attachment was scrubbed... Name: d.patch Type: text/x-diff Size: 5352 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20070103/3945bdcc/attachment-0001.bin From vda.linux at googlemail.com Tue Jan 2 19:30:12 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Wed, 3 Jan 2007 04:30:12 +0100 Subject: possible httpd applet bug? In-Reply-To: <1167750955.13878.23.camel@albrecht.rdi1.com> References: <1167750955.13878.23.camel@albrecht.rdi1.com> Message-ID: <200701030430.12228.vda.linux@googlemail.com> On Tuesday 02 January 2007 16:15, Paul Albrecht wrote: > > I have a question about the way the busybox httpd applet reads cgi > program output: Why is safe_read used rather than full_read? > > The problem with safe_read is you're not guaranteed the entire first > line of cgi output on the first read so the applet doesn't handle the > status line or content-type header correctly. > > Seems like if you don't want to read all the cgi output at once, then > you should buffer the first line, but I don't think it makes much of a > difference for busybox httpd. This code? if (FD_ISSET(inFd, &readSet)) { int s = config->accepted_socket; char *rbuf = config->buf; #ifndef PIPE_BUF # define PIPESIZE 4096 /* amount of buffering in a pipe */ #else # define PIPESIZE PIPE_BUF #endif #if PIPESIZE >= MAX_MEMORY_BUFF # error "PIPESIZE >= MAX_MEMORY_BUFF" #endif /* There is something to read */ count = safe_read(inFd, rbuf, PIPESIZE); What will happen if there is less than PIPESIZE bytes? Hmm... if child has died, we will get short read anyway; if it has paused, we will block on this read... is it bad? why? (btw, I read around that place. What kind of English is this variable name - post_readed_xxx? I think it's vodz contribution...) Need to think about it a bit more. Suggestions in the form of patches are always welcome. ;) -- vda From iggarpe at terra.es Wed Jan 3 02:17:15 2007 From: iggarpe at terra.es (=?ISO-8859-1?Q?Ignacio_Garc=EDa_P=E9rez?=) Date: Wed, 03 Jan 2007 11:17:15 +0100 Subject: ifup broken in 1.3.1 In-Reply-To: <200701030231.15388.vda.linux@googlemail.com> References: <200701030231.15388.vda.linux@googlemail.com> Message-ID: <459B82AB.90100@terra.es> Hi, "ifup eth0" segfaults on the following very simple /etc/network/interfaces: iface eth0 inet static address 10.0.0.1 netmask 255.0.0.0 Regards. Nacho. From marc.leeman at gmail.com Wed Jan 3 03:02:38 2007 From: marc.leeman at gmail.com (Marc Leeman) Date: Wed, 3 Jan 2007 12:02:38 +0100 Subject: [gmail] Re: SHADOW problem and patches In-Reply-To: <200612302250.25518.vda.linux@googlemail.com> References: <20061228091954.GP5750@scorpius.homelinux.org> <200612282357.17669.vda.linux@googlemail.com> <20061229093603.GS5750@scorpius.homelinux.org> <200612302250.25518.vda.linux@googlemail.com> Message-ID: <20070103110238.GL18182@scorpius.homelinux.org> > I am interested in being capable to at least compile bbox for some > non-386 and non-32-bit arches. > > This powerpc-linux-uclibc toolchain - is it 64-bit? No, it's intended for a 32-bit processors (82xx/83xx Freescale series). > Can you give me versions and configure params you gave to gcc > and binutils in order to produce powerpc-linux-uclibc toolchain? > (I think I'll try to compile it against glibc as a first step). I'll send you the config of buildroot. > Do you have environment (qemu-runnable image or something like that) > where I can test resulting binaries on amd64 hardware? No, but I really should test that with qemu :-/ I can send you the squashfs image from the firmware, as far as I understood from a collegue, it should work pretty much out of the box with qemu. -- Marc Leeman R&D Firmware Engineer Barco Security and Monitoring Division Noordlaan 5, Industriezone, B-8520 Kuurne (BE) Tel. +32 56 368 428 http://www.barco.com/controlrooms/ mailto:marc.leeman at barco.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://busybox.net/lists/busybox/attachments/20070103/b85c1d93/attachment.pgp From albrecht at rdi1.com Wed Jan 3 06:45:32 2007 From: albrecht at rdi1.com (Paul Albrecht) Date: Wed, 03 Jan 2007 09:45:32 -0500 Subject: possible httpd applet bug? In-Reply-To: <200701030430.12228.vda.linux@googlemail.com> References: <1167750955.13878.23.camel@albrecht.rdi1.com> <200701030430.12228.vda.linux@googlemail.com> Message-ID: <1167835532.2469.75.camel@albrecht.rdi1.com> On Wed, 2007-01-03 at 04:30 +0100, Denis Vlasenko wrote: > On Tuesday 02 January 2007 16:15, Paul Albrecht wrote: > > > > I have a question about the way the busybox httpd applet reads cgi > > program output: Why is safe_read used rather than full_read? > > > > The problem with safe_read is you're not guaranteed the entire first > > line of cgi output on the first read so the applet doesn't handle the > > status line or content-type header correctly. > > > > Seems like if you don't want to read all the cgi output at once, then > > you should buffer the first line, but I don't think it makes much of a > > difference for busybox httpd. > > This code? > > if (FD_ISSET(inFd, &readSet)) { > int s = config->accepted_socket; > char *rbuf = config->buf; > > #ifndef PIPE_BUF > # define PIPESIZE 4096 /* amount of buffering in a pipe */ > #else > # define PIPESIZE PIPE_BUF > #endif > #if PIPESIZE >= MAX_MEMORY_BUFF > # error "PIPESIZE >= MAX_MEMORY_BUFF" > #endif > > /* There is something to read */ > count = safe_read(inFd, rbuf, PIPESIZE); > Yes, this is a problem because safe_read is unbuffered so you can't assume you have the first line of output after the initial read, but here's what the server does next: if (count == 0) break; /* closed */ if (count > 0) { if (firstLine) { rbuf[count] = 0; /* check to see if the user script added headers */ if (strncmp(rbuf, "HTTP/1.0 200 OK\r\n", 4) != 0) { full_write(s, "HTTP/1.0 200 OK\r\n", 17); } /* Sometimes CGI is writing to pipe in small chunks * and we don't see Content-type (because the read * is too short) and we emit bogus "text/plain"! * Is it a bug or CGI *has to* write it in one piece? */ if (strstr(rbuf, "ontent-") == 0) { full_write(s, "Content-type: text/plain\r\n\r\n", 28); } firstLine = 0; } if (full_write(s, rbuf, count) != count) break; if (DEBUG) fprintf(stderr, "cgi read %d bytes: '%.*s'\n", count, count, rbuf); } The problem with the preceding code is it assumes the initial safe_read has read at least four bytes and that's not guaranteed because safe_read is unbuffered. I have worked around the problem by changing the safe_read to full_read so I get all the cgi output on the first read. If you change the safe_read to a full_read then I don't think you need to write the content-type header, but I haven't tested that yet. > What will happen if there is less than PIPESIZE bytes? Hmm... > if child has died, we will get short read anyway; > if it has paused, we will block on this read... is it bad? why? > > (btw, I read around that place. What kind of English is this > variable name - post_readed_xxx? I think it's vodz contribution...) > > Need to think about it a bit more. > > Suggestions in the form of patches are always welcome. ;) > -- > > vda From giuseppe at telvia.it Wed Jan 3 10:13:57 2007 From: giuseppe at telvia.it (Giuseppe Ciotta) Date: Wed, 03 Jan 2007 19:13:57 +0100 Subject: possible httpd applet bug? In-Reply-To: <1167750955.13878.23.camel@albrecht.rdi1.com> References: <1167750955.13878.23.camel@albrecht.rdi1.com> Message-ID: <459BF265.3030706@telvia.it> Paul Albrecht wrote: > I have a question about the way the busybox httpd applet reads cgi > program output: Why is safe_read used rather than full_read? > > The problem with safe_read is you're not guaranteed the entire first > line of cgi output on the first read so the applet doesn't handle the > status line or content-type header correctly. > > Seems like if you don't want to read all the cgi output at once, then > you should buffer the first line, but I don't think it makes much of a > difference for busybox httpd. > > Paul Albrecht > _______________________________________________ > busybox mailing list > busybox at busybox.net > http://busybox.net/cgi-bin/mailman/listinfo/busybox > I've noticed the same problem some time ago... see http://www.busybox.net/lists/busybox/2006-May/021421.html From somlo at cmu.edu Wed Jan 3 11:03:44 2007 From: somlo at cmu.edu (Gabriel L. Somlo) Date: Wed, 3 Jan 2007 14:03:44 -0500 Subject: udhcpc sample script Message-ID: <20070103190344.GC30822@hedwig.net.cmu.edu> Denis & All, I was messing around with udhcpc, and noticed the sample script included in examples/udhcp/ will re-run ifconfig, delete all default routers and re-add them, every time there's a dhcp renew request, and even when none of the parameters given to us by the dhcp server change. So, attached is my new udhcpc.script, which 1. uses 'ip' instead of 'ifconfig' and 'route' 2. only makes changes when the info received from the dhcp server changes 3. avoids making any unnecessary changes (i.e. rewriting resolv.conf with the same info just because the default gateway is different :) ) Please add it to examples/udhcpc if you think anyone else might find it useful... Thanks, Gabriel -------------- next part -------------- #!/bin/busybox sh # udhcp sample script by Gabriel Somlo (somlo at cmu edu) # - uses 'ip' instead of 'ifconfig' and 'route' # - make minimal changes, and only if required by changing dhcp options [ -z "$1" ] && echo 'Error: should be called from udhcpc' && exit 1 # where to save config information for $interface: CFG="/var/run/udhcpc.${interface}.cfg" # names of files we might need to touch: RESOLV_CONF='/etc/resolv.conf' NTP_CONF='/etc/ntp.conf' # which interface configures DNS and NTP ? Comment out if none: #PEERDNS_IF=eth0 #PEERNTP_IF=eth0 case "$1" in deconfig) # bring interface up, but with no IP configured: ip addr flush dev $interface ip link set $interface up # remove any stored config info for this $interface: rm -f $CFG # restore any pre-dhcp config files: if [ "$interface" == "$PEERDNS_IF" ] ; then [ -f ${RESOLV_CONF}.dhcsave ] && mv -f ${RESOLV_CONF}.dhcsave $RESOLV_CONF fi if [ "$interface" == "$PEERNTP_IF" ] ; then [ -f ${NTP_CONF}.dhcsave ] && mv -f ${NTP_CONF}.dhcsave $NTP_CONF fi ;; bound) # save config info for $interface: set > $CFG # configure interface and routes: ip addr flush dev $interface ip addr add ${ip}/${mask} dev $interface [ -n "$router" ] && ip route add default via ${router%% *} dev $interface # save pre-dhcp config files and generate new ones: if [ "$interface" == "$PEERDNS_IF" ] ; then [ -f $RESOLV_CONF ] && mv -f $RESOLV_CONF ${RESOLV_CONF}.dhcsave [ -n "$domain" ] && echo search $domain > $RESOLV_CONF for i in $dns ; do echo nameserver $i >> $RESOLV_CONF done fi if [ "$interface" == "$PEERNTP_IF" ] ; then [ -f $NTP_CONF ] && mv -f $NTP_CONF ${NTP_CONF}.dhcsave > $NTP_CONF for i in $ntpsrv ; do echo server $i >> $NTP_CONF done fi ;; renew) # compare new vs. previous config info: set > ${CFG}.new for i in $(diff -U1 $CFG ${CFG}.new | grep -E ^[+-] \ | tail +3 \ | awk -F[+-=] '{print $2}') ; do case "$i" in ip|mask|router) REDO_NET='yes' ;; domain|dns) REDO_DNS='yes' ;; ntpsrv) REDO_NTP='yes' ;; esac done # save new config info: mv -f ${CFG}.new $CFG # make only necessary changes, as per config comparison: if [ -n "$REDO_NET" ] ; then ip addr flush dev $interface ip addr add ${ip}/${mask} dev $interface [ -n "$router" ] && ip route add default via ${router%% *} dev $interface fi if [ -n "$REDO_DNS" -a "$interface" == "$PEERDNS_IF" ] ; then [ -n "$domain" ] && echo search $domain > $RESOLV_CONF for i in $dns ; do echo nameserver $i >> $RESOLV_CONF done fi if [ -n "$REDO_NTP" -a "$interface" == "$PEERNTP_IF" ] ; then > $NTP_CONF for i in $ntpsrv ; do echo server $i >> $NTP_CONF done # FIXME: RELOAD NTP DAEMON HERE fi ;; esac exit 0 From albrecht at rdi1.com Wed Jan 3 10:37:20 2007 From: albrecht at rdi1.com (Paul Albrecht) Date: Wed, 03 Jan 2007 13:37:20 -0500 Subject: possible httpd applet bug? In-Reply-To: <1167848161.3919.0.camel@albrecht.rdi1.com> References: <1167750955.13878.23.camel@albrecht.rdi1.com> <1167848161.3919.0.camel@albrecht.rdi1.com> Message-ID: <1167849440.3919.16.camel@albrecht.rdi1.com> On Wed, 2007-01-03 at 19:13 +0100, Giuseppe Ciotta wrote: > Paul Albrecht wrote: > > I have a question about the way the busybox httpd applet reads cgi > > program output: Why is safe_read used rather than full_read? > > > > The problem with safe_read is you're not guaranteed the entire first > > line of cgi output on the first read so the applet doesn't handle the > > status line or content-type header correctly. > > > > Seems like if you don't want to read all the cgi output at once, then > > you should buffer the first line, but I don't think it makes much of a > > difference for busybox httpd. > > > > Paul Albrecht > > _______________________________________________ > > busybox mailing list > > busybox at busybox.net > > http://busybox.net/cgi-bin/mailman/listinfo/busybox > > > I've noticed the same problem some time ago... see > http://www.busybox.net/lists/busybox/2006-May/021421.html Thanks for the pointer to your previous message. This is exactly the same problem. I don't think the busybox httpd server ever needs to return the content-type header. It seems like it's just a kludge around the bug handling the http status line. I think the fix is change the safe_read to a full_read so the status line is handled correctly. There's no need for the busybox httpd server to return the content-type header so that code should be deleted. From rep.nop at aon.at Wed Jan 3 14:13:42 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Wed, 3 Jan 2007 23:13:42 +0100 Subject: svn commit: trunk/busybox/networking In-Reply-To: <20070103220928.5643F48627@busybox.net> References: <20070103220928.5643F48627@busybox.net> Message-ID: <20070103221342.GA28746@aon.at> On Wed, Jan 03, 2007 at 02:09:28PM -0800, vda at busybox.net wrote: >Author: vda >Date: 2007-01-03 14:09:26 -0800 (Wed, 03 Jan 2007) >New Revision: 17147 > >Log: >wget: print port# in 'Host' header, if different from 80 Why can't we simply print the port regardless of it being 80 or not? From rob at landley.net Wed Jan 3 14:27:31 2007 From: rob at landley.net (Rob Landley) Date: Wed, 3 Jan 2007 17:27:31 -0500 Subject: Does it make sense to reduce bss? In-Reply-To: <200701030231.15388.vda.linux@googlemail.com> References: <200701030231.15388.vda.linux@googlemail.com> Message-ID: <200701031727.32218.rob@landley.net> On Tuesday 02 January 2007 8:31 pm, Denis Vlasenko wrote: > Hi, > > Current svn with all options on has ~85k in bss. It is not a problem > for MMU systems but NOMMU, I suppose, would benefit from smaller bss. > > I was removing largish bss users and mostly fixed big ones, > but should I go after not-so-big ones too? > > For example: > > Attached patch moves 8k of fsck_minix's buffers from bss to xzalloc'ed > space, but it costs ~150 bytes of code: This is why busybox historically had the allocation macros to put stuff on the stack or malloc it. We didn't use them much, and it turns out putting stuff on the _stack_ generally is not an improvement for nommu guys, and tends to make things bigger on register starved architectures like x86. For toybox I've done the "union of global structs" thing I talked about last year here, keeping bss use down from day 1, and I'm no longer paying all that much attention to how busybox does it. Sorry. Rob -- "Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery From vda.linux at googlemail.com Wed Jan 3 14:30:35 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Wed, 3 Jan 2007 23:30:35 +0100 Subject: svn commit: trunk/busybox/networking In-Reply-To: <20070103221342.GA28746@aon.at> References: <20070103220928.5643F48627@busybox.net> <20070103221342.GA28746@aon.at> Message-ID: <200701032330.35531.vda.linux@googlemail.com> On Wednesday 03 January 2007 23:13, Bernhard Fischer wrote: > On Wed, Jan 03, 2007 at 02:09:28PM -0800, vda at busybox.net wrote: > >Author: vda > >Date: 2007-01-03 14:09:26 -0800 (Wed, 03 Jan 2007) > >New Revision: 17147 > > > >Log: > >wget: print port# in 'Host' header, if different from 80 > > Why can't we simply print the port regardless of it being 80 or not? Indeed, we can. If somebody placed their Apache behind port-remapping firewall, the fact that their server will get requests with 'Host' header's port number != actual port number -- it's their problem, I think. Implemented in svn, thanks! -- vda From vda.linux at googlemail.com Wed Jan 3 14:43:07 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Wed, 3 Jan 2007 23:43:07 +0100 Subject: ifup broken in 1.3.1 In-Reply-To: <459B82AB.90100@terra.es> References: <200701030231.15388.vda.linux@googlemail.com> <459B82AB.90100@terra.es> Message-ID: <200701032343.07727.vda.linux@googlemail.com> On Wednesday 03 January 2007 11:17, Ignacio Garc?a P?rez wrote: > iface eth0 inet static > ? ? address 10.0.0.1 > ? ? netmask 255.0.0.0 Yes, it is, but current svn is fixed. With current svn: bash-3.2# cat /etc/network/interfaces iface if inet static address 10.0.0.1 netmask 255.0.0.0 My network is already up: bash-3.2# ip a 1: lo: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: if: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:16:17:6d:77:db brd ff:ff:ff:ff:ff:ff inet 192.168.1.111/24 brd 192.168.1.255 scope global if bash-3.2# ip r 192.168.1.0/24 dev if proto kernel scope link src 192.168.1.111 default via 192.168.1.10 dev if I reconfigure it: bash-3.2# ./busybox ifup if Doesn't segfault. bash-3.2# ip a 1: lo: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: if: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:16:17:6d:77:db brd ff:ff:ff:ff:ff:ff inet 192.168.1.111/24 brd 192.168.1.255 scope global if inet 10.0.0.1/8 scope global if bash-3.2# ip r 192.168.1.0/24 dev if proto kernel scope link src 192.168.1.111 10.0.0.0/8 dev if proto kernel scope link src 10.0.0.1 default via 192.168.1.10 dev if -- vda From vda.linux at googlemail.com Wed Jan 3 14:44:51 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Wed, 3 Jan 2007 23:44:51 +0100 Subject: possible httpd applet bug? In-Reply-To: <1167835532.2469.75.camel@albrecht.rdi1.com> References: <1167750955.13878.23.camel@albrecht.rdi1.com> <200701030430.12228.vda.linux@googlemail.com> <1167835532.2469.75.camel@albrecht.rdi1.com> Message-ID: <200701032344.51509.vda.linux@googlemail.com> On Wednesday 03 January 2007 15:45, Paul Albrecht wrote: > On Wed, 2007-01-03 at 04:30 +0100, Denis Vlasenko wrote: > > On Tuesday 02 January 2007 16:15, Paul Albrecht wrote: > > > > > > I have a question about the way the busybox httpd applet reads cgi > > > program output: Why is safe_read used rather than full_read? > > > > > > The problem with safe_read is you're not guaranteed the entire first > > > line of cgi output on the first read so the applet doesn't handle the > > > status line or content-type header correctly. > > > > > > Seems like if you don't want to read all the cgi output at once, then > > > you should buffer the first line, but I don't think it makes much of a > > > difference for busybox httpd. > > > > This code? > > > > if (FD_ISSET(inFd, &readSet)) { > > int s = config->accepted_socket; > > char *rbuf = config->buf; > > > > #ifndef PIPE_BUF > > # define PIPESIZE 4096 /* amount of buffering in a pipe */ > > #else > > # define PIPESIZE PIPE_BUF > > #endif > > #if PIPESIZE >= MAX_MEMORY_BUFF > > # error "PIPESIZE >= MAX_MEMORY_BUFF" > > #endif > > > > /* There is something to read */ > > count = safe_read(inFd, rbuf, PIPESIZE); > > > > Yes, this is a problem because safe_read is unbuffered so you can't > assume you have the first line of output after the initial read, but > here's what the server does next: > > if (count == 0) > break; /* closed */ > if (count > 0) { > if (firstLine) { > rbuf[count] = 0; > /* check to see if the user script added headers */ > if (strncmp(rbuf, "HTTP/1.0 200 OK\r\n", 4) != 0) { > full_write(s, "HTTP/1.0 200 OK\r\n", 17); > } > /* Sometimes CGI is writing to pipe in small chunks > * and we don't see Content-type (because the read > * is too short) and we emit bogus "text/plain"! > * Is it a bug or CGI *has to* write it in one piece? */ > if (strstr(rbuf, "ontent-") == 0) { > full_write(s, "Content-type: text/plain\r\n\r\n", 28); > } > firstLine = 0; > } > if (full_write(s, rbuf, count) != count) > break; > > if (DEBUG) > fprintf(stderr, "cgi read %d bytes: '%.*s'\n", count, count, rbuf); > } > > The problem with the preceding code is it assumes the initial safe_read has read at > least four bytes and that's not guaranteed because safe_read is unbuffered. Where it assumes that? > > I have worked around the problem by changing the safe_read to full_read so I get all > the cgi output on the first read. > > If you change the safe_read to a full_read then I don't think you need to write the > content-type header, but I haven't tested that yet. Why I don't have to do it? -- vda From vda.linux at googlemail.com Wed Jan 3 14:48:27 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Wed, 3 Jan 2007 23:48:27 +0100 Subject: possible httpd applet bug? In-Reply-To: <1167849440.3919.16.camel@albrecht.rdi1.com> References: <1167750955.13878.23.camel@albrecht.rdi1.com> <1167848161.3919.0.camel@albrecht.rdi1.com> <1167849440.3919.16.camel@albrecht.rdi1.com> Message-ID: <200701032348.27318.vda.linux@googlemail.com> On Wednesday 03 January 2007 19:37, Paul Albrecht wrote: > I think the fix is change the safe_read to a full_read so the status > line is handled correctly. There's no need for the busybox httpd server > to return the content-type header so that code should be deleted. If you have an URL or something which explains that GCIs _must_ produce Content-Type header, I can put URL into the comment and delete the code. Meanwhile I am going to replace safe_read by full_read. Thanks for the bug report! -- vda From vda.linux at googlemail.com Wed Jan 3 15:12:21 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Thu, 4 Jan 2007 00:12:21 +0100 Subject: cmdedit fix In-Reply-To: <1167757264.29946.5.camel@psmithub> References: <458A3A23.000001.07769@mfront8.yandex.ru> <20061223055742.GC3434@brightrain.aerifal.cx> <1167757264.29946.5.camel@psmithub> Message-ID: <200701040012.21757.vda.linux@googlemail.com> On Tuesday 02 January 2007 18:01, Paul Smith wrote: > On Sat, 2006-12-23 at 00:57 -0500, Rich Felker wrote: > > On Sat, Dec 23, 2006 at 02:21:21AM +0100, Denis Vlasenko wrote: > > > On Thursday 21 December 2006 08:39, ybrnj80 wrote: > > > > Hi, Denis! > > > > > > > > BB fails to compile cmdedit.c if certain features is not enebled > > > > Patch attached > > > > > > Thanks, applied. > > > > I'm hoping we can replace cmdedit.c soon. I'm working on a tiny line > > editing module with nearly as much functionality as readline (and more > > in some respects) which should be similar size to BB cmdedit (at least > > once I add #ifdefs to turn off some of the improved features). > > Have you thought about using Tecla? > > http://www.astro.caltech.edu/~mcs/tecla/index.html > > I've used it for a few projects in the past and found it very, very > good. Not sure if it will meet your size requirements (I don't think it > was originally created with that as a design goal. 1016106 bytes in 39 files (only *.[ch] files counted)? getline.c of 400310 bytes? No, I think this is a bit too much for line editing. -- vda From vda.linux at googlemail.com Wed Jan 3 15:23:39 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Thu, 4 Jan 2007 00:23:39 +0100 Subject: svn commit: trunk/busybox: archival coreutils miscutils modutils ne etc... In-Reply-To: <20070102104914.GA6466@aon.at> References: <20061230175704.E11864858C@busybox.net> <200612302331.17248.vda.linux@googlemail.com> <20070102104914.GA6466@aon.at> Message-ID: <200701040023.39073.vda.linux@googlemail.com> On Tuesday 02 January 2007 11:49, Bernhard Fischer wrote: > On Sat, Dec 30, 2006 at 11:31:17PM +0100, Denis Vlasenko wrote: > >On Saturday 30 December 2006 23:26, Yann E. MORIN wrote: > >> On Saturday 30 December 2006 185, vda at busybox.net wrote: > >> > done a dozen of randconfig test. guess what? ALL failed... > > May i point you at http://busybox.net/~aldot/bb/mk.busybox.sh > I just updated it to version 0.5d > > Usage: > $ mkdir -p /tmp/scratch > $ cd /tmp/scratch > $ ./mk.busybox.sh 2>&1 >&1 foo.log & > > even make clean allnoconfig ; make > is b0rked, btw ;) You are evil. :) Fixed in svn. # size busybox text data bss dec hex filename 2591 308 24 2923 b6b busybox What? We have nonzero data on NULL config? I'm curious where... ah, mostly gcc & glibc stuff: $ nm busybox_unstripped-NULL | grep -i ' [bd] ' 08049c74 B applet_name 08049c70 b applet_using 08049c6c b completed.5126 08049b34 d __CTOR_END__ 08049b30 d __CTOR_LIST__ 08049c78 B die_sleep 08049c50 D __dso_handle 08049b3c d __DTOR_END__ 08049b38 d __DTOR_LIST__ 08049b44 d _DYNAMIC 08049c10 d _GLOBAL_OFFSET_TABLE_ 08049b40 d __JCR_END__ 08049b40 d __JCR_LIST__ 08049c5c D logmode 08049c60 D msg_eol 08049c54 d p.5124 08049c68 B stderr@@GLIBC_2.0 08049c64 B stdout@@GLIBC_2.0 08049c58 D xfunc_error_retval -- vda From albrecht at rdi1.com Thu Jan 4 06:28:16 2007 From: albrecht at rdi1.com (Paul Albrecht) Date: Thu, 04 Jan 2007 09:28:16 -0500 Subject: possible httpd applet bug? In-Reply-To: <200701032348.27318.vda.linux@googlemail.com> References: <1167750955.13878.23.camel@albrecht.rdi1.com> <1167848161.3919.0.camel@albrecht.rdi1.com> <1167849440.3919.16.camel@albrecht.rdi1.com> <200701032348.27318.vda.linux@googlemail.com> Message-ID: <1167920896.2660.3.camel@albrecht.rdi1.com> On Wed, 2007-01-03 at 23:48 +0100, Denis Vlasenko wrote: > On Wednesday 03 January 2007 19:37, Paul Albrecht wrote: > > I think the fix is change the safe_read to a full_read so the status > > line is handled correctly. There's no need for the busybox httpd server > > to return the content-type header so that code should be deleted. > > If you have an URL or something which explains that GCIs _must_ > produce Content-Type header, I can put URL into the comment > and delete the code. > The cgi program generates the http response not the busybox http server so it should be obvious that it must return a content-type header if one is required. What the busybox http server actually does now is checks the output for something that kinda sorta looks like a content-type header and if it doesn't find one it inserts a content-type header of text/plain which doesn't make sense for some cgi programs. Here's an example of a cgi program without a entity body: echo -e "HTTP/1.0 302 Found\r\nLocation: http://www.busybox.net\r\n\r\n" If you for some reason feel obligated to insert a content-type of text/plain if a cgi program doesn't return a response header that kinda sorta looks like a content-type header, then you should verify the http response includes a entity body before you return a content-type header. :) > Meanwhile I am going to replace safe_read by full_read. > Thanks for the bug report! > -- > > vda From rep.nop at aon.at Thu Jan 4 10:15:51 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Thu, 4 Jan 2007 19:15:51 +0100 Subject: svn commit: trunk/busybox: coreutils include libbb sysklogd In-Reply-To: <20070104180000.0CD914865A@busybox.net> References: <20070104180000.0CD914865A@busybox.net> Message-ID: <20070104181551.GI28746@aon.at> On Thu, Jan 04, 2007 at 10:00:00AM -0800, vda at busybox.net wrote: >Author: vda >Date: 2007-01-04 09:59:59 -0800 (Thu, 04 Jan 2007) >New Revision: 17156 > >Log: >new libbb func: xmalloc_realpath (+ use it where makes sense) >syslogd, logread: add debugging code (disabled) >syslogs: drastically smaller bss; fix "-C n" behaviour Just curious as to the stats for this change? >--- trunk/busybox/include/usage.h 2007-01-04 17:57:54 UTC (rev 17155) >+++ trunk/busybox/include/usage.h 2007-01-04 17:59:59 UTC (rev 17156) >@@ -3021,7 +3021,8 @@ > "\n -R HOST[:PORT] Log to IP or hostname on PORT (default PORT=514/UDP)" \ > "\n -L Log locally and via network logging (default is network only)") \ > USE_FEATURE_IPC_SYSLOG( \ >- "\n -C [size(KiB)] Log to a circular buffer (read the buffer using logread)") ->+ "\n -C[size(KiB)] Log to a circular buffer (read the buffer using logread)") +>+ "\n -C[size(KiB)] Log to a circular buffer (read via logread)") is smaller and should be sufficiently clear. >+char *xmalloc_realpath(const char *path) >+{ Didn't try, but would using attribute_malloc (that we had in platform.h but someone apparently removed it since it wasn't used yet..) be benefical? >+static void error_exit(const char *str) ATTRIBUTE_NORETURN; >+static void error_exit(const char *str) >+{ >+ //release all acquired resources >+ if (log_shmid != -1) >+ shmdt(buf); >+ bb_perror_msg_and_die(str); >+} Identical to ipcsyslog_cleanup(), no? [snip] From MatthewLCreech at eaton.com Thu Jan 4 12:07:41 2007 From: MatthewLCreech at eaton.com (MatthewLCreech at eaton.com) Date: Thu, 4 Jan 2007 15:07:41 -0500 Subject: "Build at once" broken Message-ID: I'm not sure if this is known and was accidentally left in the config, or if nobody has noticed yet, but the "build all sources at once" option is currently broken. I noticed when updating from 1.2.2.1 to 1.3.1, as I enabled CONFIG_BUILD_AT_ONCE in the config, but BusyBox was still built in pieces. The offending change seems to be 16307, which removes pertinent code from the top-level Makefile. Just FYI -- Matthew L. Creech From rep.nop at aon.at Thu Jan 4 12:14:40 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Thu, 4 Jan 2007 21:14:40 +0100 Subject: "Build at once" broken In-Reply-To: References: Message-ID: <20070104201440.GL28746@aon.at> On Thu, Jan 04, 2007 at 03:07:41PM -0500, MatthewLCreech at eaton.com wrote: >I'm not sure if this is known and was accidentally left in the config, >or if nobody has noticed yet, but the "build all sources at once" option >is currently broken. I noticed when updating from 1.2.2.1 to 1.3.1, as >I enabled CONFIG_BUILD_AT_ONCE in the config, but BusyBox was still >built in pieces. > >The offending change seems to be 16307, which removes pertinent code >from the top-level Makefile. Just FYI That's a known missing feature due to the transition to the kbuild infrastructure. It shouldn't be too hard to reinstate it. I've heared that the kernel can at least build every builtin.o in IMA mode (which is suboptimal for busybox), but didn't try this myself. Patches welcome.. From vda.linux at googlemail.com Thu Jan 4 13:52:49 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Thu, 4 Jan 2007 22:52:49 +0100 Subject: svn commit: trunk/busybox: coreutils include libbb sysklogd In-Reply-To: <20070104181551.GI28746@aon.at> References: <20070104180000.0CD914865A@busybox.net> <20070104181551.GI28746@aon.at> Message-ID: <200701042252.49576.vda.linux@googlemail.com> On Thursday 04 January 2007 19:15, Bernhard Fischer wrote: > On Thu, Jan 04, 2007 at 10:00:00AM -0800, vda at busybox.net wrote: > >Author: vda > >Date: 2007-01-04 09:59:59 -0800 (Thu, 04 Jan 2007) > >New Revision: 17156 > > > >Log: > >new libbb func: xmalloc_realpath (+ use it where makes sense) > >syslogd, logread: add debugging code (disabled) > >syslogs: drastically smaller bss; fix "-C n" behaviour > > Just curious as to the stats for this change? dev_log_name was taking disproportionate chunk of bss (compared to its modest goal of holding a filename): function old new delta syslogd_main 1145 1169 +24 xmalloc_realpath - 14 +14 packed_usage 21908 21918 +10 interrupted 21 27 +6 xstrtoull_range_sfx 304 309 +5 expand 2404 2406 +2 quit_signal 115 116 +1 gunzip_main 743 744 +1 telnet_main 1561 1557 -4 error_exit 35 30 -5 popstring 138 132 -6 input_tab 2945 2937 -8 .rodata 157384 157352 -32 logread_main 556 494 -62 jmp_env 156 - -156 dev_log_name 4096 4 -4092 ------------------------------------------------------------------------------ (add/remove: 1/1 grow/shrink: 7/7 up/down: 63/-4365) Total: -4302 bytes As usual gcc 4.1.1 has some pretty bizarre jitter whenever you touch *.h files... (gunzip_main +1 etc) # size busybox_old busybox_unstripped text data bss dec hex filename 741183 5240 79464 825887 c9a1f busybox_old 741119 5240 75208 821567 c893f busybox_unstripped > >--- trunk/busybox/include/usage.h 2007-01-04 17:57:54 UTC (rev 17155) > >+++ trunk/busybox/include/usage.h 2007-01-04 17:59:59 UTC (rev 17156) > >@@ -3021,7 +3021,8 @@ > > "\n -R HOST[:PORT] Log to IP or hostname on PORT (default PORT=514/UDP)" \ > > "\n -L Log locally and via network logging (default is network only)") \ > > USE_FEATURE_IPC_SYSLOG( \ > >- "\n -C [size(KiB)] Log to a circular buffer (read the buffer using logread)") > ->+ "\n -C[size(KiB)] Log to a circular buffer (read the buffer using logread)") > +>+ "\n -C[size(KiB)] Log to a circular buffer (read via logread)") > > is smaller and should be sufficiently clear. Yes. Usage text in general will benefit from a few people making janitorial passes. I did a few. > >+char *xmalloc_realpath(const char *path) > >+{ > > Didn't try, but would using attribute_malloc (that we had in platform.h > but someone apparently removed it since it wasn't used yet..) be > benefical? How does it help? Helps gcc optimizer to have better alias info? -- vda From he-guo at mediaring.com Thu Jan 4 22:15:54 2007 From: he-guo at mediaring.com (he-guo at mediaring.com) Date: Fri, 5 Jan 2007 14:15:54 +0800 Subject: steps to create user account howto Message-ID: <01fe01c73090$f5c65c30$8119fea9@corp.mediaring.com> Hi everyone, I have tested busybox 1.3.1 version. I can NOT figure out how to adduser. I tried adduser without success. Does anyone know the steps to create account especially for root user ? appreciate any help. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20070105/1075d48c/attachment.htm From farmatito at tiscali.it Thu Jan 4 23:38:42 2007 From: farmatito at tiscali.it (Tito) Date: Fri, 5 Jan 2007 08:38:42 +0100 Subject: steps to create user account howto In-Reply-To: <01fe01c73090$f5c65c30$8119fea9@corp.mediaring.com> References: <01fe01c73090$f5c65c30$8119fea9@corp.mediaring.com> Message-ID: <200701050838.42585.farmatito@tiscali.it> On Friday 05 January 2007 07:15, he-guo at mediaring.com wrote: > Hi everyone, > > I have tested busybox 1.3.1 version. > I can NOT figure out how to adduser. > I tried adduser without success. > > Does anyone know the steps to create account especially for root user ? It is not possible to create a root account with adduser. The uid of the created accounts is in the range const int min = 500; const int max = 65000; You need to create your root account manually or with a script at boot time. Ciao, Tito > appreciate any help. > > Thanks > From ross.cameron at linuxpro.co.za Fri Jan 5 07:09:45 2007 From: ross.cameron at linuxpro.co.za (Ross Cameron) Date: Fri, 5 Jan 2007 17:09:45 +0200 Subject: Building a pkgsrc port of busybox Message-ID: <35f70db10701050709p7cec3a31o3dfcfec85b43b69e@mail.gmail.com> Hi there list,... Happy New Years! I work for a company that produces embedded systems and we're moving out package management system to NetBSD's pkgsrc system. I'm having a few issues and I was wondering if anyone knows how to proceed further than I've gotten at the moment. Host operating system is roughly a standard Slackware 11.0 for i386 system. Below is the output of my bmake (BSD make) command,... before anyone asks my Makefile overrides bmake and calls gmake (GNU make). root at seyos-devel:/usr/pkgsrc/sysutils/busybox# bmake => Required installed package digest> 010302: digest-20060826 found ==> Skipping vulnerability checks. WARNING: No /usr/pkgsrc/distfiles/pkg-vulnerabilities file found. WARNING: To fix, install the pkgsrc/security/audit-packages WARNING: package and run: ``/usr/pkg/sbin/download-vulnerability-list''. => Checksum SHA1 OK for busybox-1.3.1.tar.bz2 => Checksum RMD160 OK for busybox-1.3.1.tar.bz2 ==> Installing dependencies for busybox-1.3.1 ==> Overriding tools for busybox-1.3.1 ==> Extracting for busybox-1.3.1 ==> Patching for busybox-1.3.1 ==> Creating toolchain wrappers for busybox-1.3.1 ==> Configuring for busybox-1.3.1 ==> Building for busybox-1.3.1 HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/split-include HOSTCC scripts/basic/docproc HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o HOSTCC scripts/kconfig/mconf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf -s Config.in *** *** You have not yet configured your kernel! *** *** Please run some configurator (e.g. "make oldconfig" or *** "make menuconfig" or "make xconfig"). *** make[2]: *** [silentoldconfig] Error 1 make[1]: *** [silentoldconfig] Error 2 make: *** [include/autoconf.h] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/sysutils/busybox *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/sysutils/busybox -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20070105/9f444b01/attachment.htm From ross.cameron at linuxpro.co.za Fri Jan 5 08:23:24 2007 From: ross.cameron at linuxpro.co.za (Ross Cameron) Date: Fri, 5 Jan 2007 18:23:24 +0200 Subject: Building a pkgsrc port of busybox In-Reply-To: <35f70db10701050709p7cec3a31o3dfcfec85b43b69e@mail.gmail.com> References: <35f70db10701050709p7cec3a31o3dfcfec85b43b69e@mail.gmail.com> Message-ID: <35f70db10701050823q2a506bd5rc6a179b1f85dbf49@mail.gmail.com> A bit more info on this one,.... At the bottom of this email I've attached my previous busybox build script that works 100%,... how would I get the same functionality in pkgsrc? On 05/01/07, Ross Cameron wrote: > > Hi there list,... Happy New Years! > > I work for a company that produces embedded systems and we're moving out > package management system to NetBSD's pkgsrc system. > I'm having a few issues and I was wondering if anyone knows how to proceed > further than I've gotten at the moment. > > Host operating system is roughly a standard Slackware 11.0 for i386 > system. > > Below is the output of my bmake (BSD make) command,... before anyone asks > my Makefile overrides bmake and calls gmake (GNU make). > > root at seyos-devel:/usr/pkgsrc/sysutils/busybox# bmake > => Required installed package digest> 010302: digest-20060826 found > ==> Skipping vulnerability checks. > WARNING: No /usr/pkgsrc/distfiles/pkg-vulnerabilities file found. > WARNING: To fix, install the pkgsrc/security/audit-packages > WARNING: package and run: ``/usr/pkg/sbin/download-vulnerability-list''. > => Checksum SHA1 OK for busybox-1.3.1.tar.bz2 > => Checksum RMD160 OK for busybox-1.3.1.tar.bz2 > ==> Installing dependencies for busybox-1.3.1 > ==> Overriding tools for busybox-1.3.1 > ==> Extracting for busybox-1.3.1 > ==> Patching for busybox-1.3.1 > ==> Creating toolchain wrappers for busybox-1.3.1 > ==> Configuring for busybox-1.3.1 > ==> Building for busybox-1.3.1 > HOSTCC scripts/basic/fixdep > HOSTCC scripts/basic/split-include > HOSTCC scripts/basic/docproc > HOSTCC scripts/kconfig/conf.o > HOSTCC scripts/kconfig/kxgettext.o > HOSTCC scripts/kconfig/mconf.o > SHIPPED scripts/kconfig/zconf.tab.c > SHIPPED scripts/kconfig/lex.zconf.c > SHIPPED scripts/kconfig/zconf.hash.c > HOSTCC scripts/kconfig/zconf.tab.o > HOSTLD scripts/kconfig/conf > scripts/kconfig/conf -s Config.in > *** > *** You have not yet configured your kernel! > *** > *** Please run some configurator (e.g. "make oldconfig" or > *** "make menuconfig" or "make xconfig"). > *** > make[2]: *** [silentoldconfig] Error 1 > make[1]: *** [silentoldconfig] Error 2 > make: *** [include/autoconf.h] Error 2 > *** Error code 2 > > Stop. > bmake: stopped in /usr/pkgsrc/sysutils/busybox > *** Error code 1 > > Stop. > bmake: stopped in /usr/pkgsrc/sysutils/busybox > > Previous working script: # # Package: busybox # Summary: minimalistic set of command line tools # name() { echo "busybox-1.2.1-1" } build() { cd "busybox-1.2.1" cp "../control/busybox-config" .config make oldconfig make mkdir -p "$DISTDIR/bin" mkdir -p "$DISTDIR/sbin" mkdir -p "$DISTDIR/usr/bin" mkdir -p "$DISTDIR/usr/sbin" make PREFIX="$DISTDIR" install mv "$DISTDIR/usr/bin/cut" "$DISTDIR/bin/cut" make distclean cp "../control/busybox-suid-config" .config make oldconfig make $INSTALL -m 4711 busybox "$DISTDIR/bin/mount" ln "$DISTDIR/bin/mount" "$DISTDIR/bin/ping" ln "$DISTDIR/bin/mount" "$DISTDIR/bin/su" ln "$DISTDIR/bin/mount" "$DISTDIR/bin/umount" ln "$DISTDIR/bin/mount" "$DISTDIR/usr/bin/passwd" ln "$DISTDIR/bin/mount" "$DISTDIR/usr/bin/traceroute" } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20070105/d29ceb33/attachment-0001.html From jnewell at wgate.com Fri Jan 5 08:56:52 2007 From: jnewell at wgate.com (James Newell) Date: Fri, 05 Jan 2007 11:56:52 -0500 Subject: busybox 1.3.1 issue Message-ID: <1168016212.31665.3.camel@ndragon.eng.wgate.com> Where is the mail list archive found? I get unusual warnings with the new busybox 1.3.1 and I didn't get with the busybox 1.2.2.1 when I do a make menuconfig. I posted the warnings at the end of the email. Also, I do not see the build with a cross compiler option anymore? Has this been removed or replaced with a different mechanism? I apologize if any of this has already been asked or mentioned. Once, I figure out where the archives are I will visit those first next time. Regards, Jim ########################################################################## /boot/config-2.6.18-1.2257.fc5smp:2007:warning: trying to assign nonexistent symbol 60XX_WDT /boot/config-2.6.18-1.2257.fc5smp:2008:warning: trying to assign nonexistent symbol SBC8360_WDT /boot/config-2.6.18-1.2257.fc5smp:2009:warning: trying to assign nonexistent symbol CPU5_WDT /boot/config-2.6.18-1.2257.fc5smp:2010:warning: trying to assign nonexistent symbol W83627HF_WDT /boot/config-2.6.18-1.2257.fc5smp:2011:warning: trying to assign nonexistent symbol W83877F_WDT /boot/config-2.6.18-1.2257.fc5smp:2012:warning: trying to assign nonexistent symbol W83977F_WDT /boot/config-2.6.18-1.2257.fc5smp:2013:warning: trying to assign nonexistent symbol MACHZ_WDT /boot/config-2.6.18-1.2257.fc5smp:2014:warning: trying to assign nonexistent symbol SBC_EPX_C3_WATCHDOG /boot/config-2.6.18-1.2257.fc5smp:2019:warning: trying to assign nonexistent symbol PCWATCHDOG /boot/config-2.6.18-1.2257.fc5smp:2020:warning: trying to assign nonexistent symbol MIXCOMWD /boot/config-2.6.18-1.2257.fc5smp:2021:warning: trying to assign nonexistent symbol WDT /boot/config-2.6.18-1.2257.fc5smp:2026:warning: trying to assign nonexistent symbol PCIPCWATCHDOG /boot/config-2.6.18-1.2257.fc5smp:2027:warning: trying to assign nonexistent symbol WDTPCI /boot/config-2.6.18-1.2257.fc5smp:2028:warning: trying to assign nonexistent symbol WDT_501_PCI /boot/config-2.6.18-1.2257.fc5smp:2033:warning: trying to assign nonexistent symbol USBPCWATCHDOG /boot/config-2.6.18-1.2257.fc5smp:2034:warning: trying to assign nonexistent symbol HW_RANDOM /boot/config-2.6.18-1.2257.fc5smp:2035:warning: trying to assign nonexistent symbol HW_RANDOM_INTEL /boot/config-2.6.18-1.2257.fc5smp:2036:warning: trying to assign nonexistent symbol HW_RANDOM_AMD /boot/config-2.6.18-1.2257.fc5smp:2037:warning: trying to assign nonexistent symbol HW_RANDOM_GEODE /boot/config-2.6.18-1.2257.fc5smp:2038:warning: trying to assign nonexistent symbol HW_RANDOM_VIA /boot/config-2.6.18-1.2257.fc5smp:2039:warning: trying to assign nonexistent symbol NVRAM /boot/config-2.6.18-1.2257.fc5smp:2040:warning: trying to assign nonexistent symbol RTC /boot/config-2.6.18-1.2257.fc5smp:2041:warning: trying to assign nonexistent symbol DTLK /boot/config-2.6.18-1.2257.fc5smp:2042:warning: trying to assign nonexistent symbol R3964 /boot/config-2.6.18-1.2257.fc5smp:2043:warning: trying to assign nonexistent symbol APPLICOM /boot/config-2.6.18-1.2257.fc5smp:2044:warning: trying to assign nonexistent symbol SONYPI /boot/config-2.6.18-1.2257.fc5smp:2049:warning: trying to assign nonexistent symbol AGP /boot/config-2.6.18-1.2257.fc5smp:2050:warning: trying to assign nonexistent symbol AGP_ALI /boot/config-2.6.18-1.2257.fc5smp:2051:warning: trying to assign nonexistent symbol AGP_ATI /boot/config-2.6.18-1.2257.fc5smp:2052:warning: trying to assign nonexistent symbol AGP_AMD /boot/config-2.6.18-1.2257.fc5smp:2053:warning: trying to assign nonexistent symbol AGP_AMD64 /boot/config-2.6.18-1.2257.fc5smp:2054:warning: trying to assign nonexistent symbol AGP_INTEL /boot/config-2.6.18-1.2257.fc5smp:2055:warning: trying to assign nonexistent symbol AGP_NVIDIA /boot/config-2.6.18-1.2257.fc5smp:2056:warning: trying to assign nonexistent symbol AGP_SIS /boot/config-2.6.18-1.2257.fc5smp:2057:warning: trying to assign nonexistent symbol AGP_SWORKS /boot/config-2.6.18-1.2257.fc5smp:2058:warning: trying to assign nonexistent symbol AGP_VIA /boot/config-2.6.18-1.2257.fc5smp:2059:warning: trying to assign nonexistent symbol AGP_EFFICEON /boot/config-2.6.18-1.2257.fc5smp:2060:warning: trying to assign nonexistent symbol DRM /boot/config-2.6.18-1.2257.fc5smp:2061:warning: trying to assign nonexistent symbol DRM_TDFX /boot/config-2.6.18-1.2257.fc5smp:2062:warning: trying to assign nonexistent symbol DRM_R128 /boot/config-2.6.18-1.2257.fc5smp:2063:warning: trying to assign nonexistent symbol DRM_RADEON /boot/config-2.6.18-1.2257.fc5smp:2064:warning: trying to assign nonexistent symbol DRM_I810 /boot/config-2.6.18-1.2257.fc5smp:2065:warning: trying to assign nonexistent symbol DRM_I830 /boot/config-2.6.18-1.2257.fc5smp:2066:warning: trying to assign nonexistent symbol DRM_I915 /boot/config-2.6.18-1.2257.fc5smp:2067:warning: trying to assign nonexistent symbol DRM_MGA /boot/config-2.6.18-1.2257.fc5smp:2068:warning: trying to assign nonexistent symbol DRM_SIS /boot/config-2.6.18-1.2257.fc5smp:2069:warning: trying to assign nonexistent symbol DRM_VIA /boot/config-2.6.18-1.2257.fc5smp:2070:warning: trying to assign nonexistent symbol DRM_SAVAGE /boot/config-2.6.18-1.2257.fc5smp:2075:warning: trying to assign nonexistent symbol SYNCLINK_CS /boot/config-2.6.18-1.2257.fc5smp:2076:warning: trying to assign nonexistent symbol CARDMAN_4000 /boot/config-2.6.18-1.2257.fc5smp:2077:warning: trying to assign nonexistent symbol CARDMAN_4040 /boot/config-2.6.18-1.2257.fc5smp:2078:warning: trying to assign nonexistent symbol MWAVE /boot/config-2.6.18-1.2257.fc5smp:2079:warning: trying to assign nonexistent symbol PC8736x_GPIO /boot/config-2.6.18-1.2257.fc5smp:2080:warning: trying to assign nonexistent symbol NSC_GPIO /boot/config-2.6.18-1.2257.fc5smp:2081:warning: trying to assign nonexistent symbol CS5535_GPIO /boot/config-2.6.18-1.2257.fc5smp:2082:warning: trying to assign nonexistent symbol RAW_DRIVER /boot/config-2.6.18-1.2257.fc5smp:2083:warning: trying to assign nonexistent symbol HPET /boot/config-2.6.18-1.2257.fc5smp:2084:warning: trying to assign nonexistent symbol HPET_RTC_IRQ /boot/config-2.6.18-1.2257.fc5smp:2085:warning: trying to assign nonexistent symbol HPET_MMAP /boot/config-2.6.18-1.2257.fc5smp:2086:warning: trying to assign nonexistent symbol HANGCHECK_TIMER /boot/config-2.6.18-1.2257.fc5smp:2091:warning: trying to assign nonexistent symbol TCG_TPM /boot/config-2.6.18-1.2257.fc5smp:2092:warning: trying to assign nonexistent symbol TCG_TIS /boot/config-2.6.18-1.2257.fc5smp:2093:warning: trying to assign nonexistent symbol TCG_NSC /boot/config-2.6.18-1.2257.fc5smp:2094:warning: trying to assign nonexistent symbol TCG_ATMEL /boot/config-2.6.18-1.2257.fc5smp:2095:warning: trying to assign nonexistent symbol TCG_INFINEON /boot/config-2.6.18-1.2257.fc5smp:2096:warning: trying to assign nonexistent symbol TELCLOCK /boot/config-2.6.18-1.2257.fc5smp:2101:warning: trying to assign nonexistent symbol I2C /boot/config-2.6.18-1.2257.fc5smp:2102:warning: trying to assign nonexistent symbol I2C_CHARDEV /boot/config-2.6.18-1.2257.fc5smp:2107:warning: trying to assign nonexistent symbol I2C_ALGOBIT /boot/config-2.6.18-1.2257.fc5smp:2108:warning: trying to assign nonexistent symbol I2C_ALGOPCF /boot/config-2.6.18-1.2257.fc5smp:2109:warning: trying to assign nonexistent symbol I2C_ALGOPCA /boot/config-2.6.18-1.2257.fc5smp:2114:warning: trying to assign nonexistent symbol I2C_ALI1535 /boot/config-2.6.18-1.2257.fc5smp:2115:warning: trying to assign nonexistent symbol I2C_ALI1563 /boot/config-2.6.18-1.2257.fc5smp:2116:warning: trying to assign nonexistent symbol I2C_ALI15X3 /boot/config-2.6.18-1.2257.fc5smp:2117:warning: trying to assign nonexistent symbol I2C_AMD756 /boot/config-2.6.18-1.2257.fc5smp:2118:warning: trying to assign nonexistent symbol I2C_AMD756_S4882 /boot/config-2.6.18-1.2257.fc5smp:2119:warning: trying to assign nonexistent symbol I2C_AMD8111 /boot/config-2.6.18-1.2257.fc5smp:2120:warning: trying to assign nonexistent symbol I2C_I801 /boot/config-2.6.18-1.2257.fc5smp:2121:warning: trying to assign nonexistent symbol I2C_I810 /boot/config-2.6.18-1.2257.fc5smp:2122:warning: trying to assign nonexistent symbol I2C_PIIX4 /boot/config-2.6.18-1.2257.fc5smp:2123:warning: trying to assign nonexistent symbol I2C_ISA /boot/config-2.6.18-1.2257.fc5smp:2124:warning: trying to assign nonexistent symbol I2C_NFORCE2 /boot/config-2.6.18-1.2257.fc5smp:2125:warning: trying to assign nonexistent symbol I2C_OCORES /boot/config-2.6.18-1.2257.fc5smp:2126:warning: trying to assign nonexistent symbol I2C_PARPORT /boot/config-2.6.18-1.2257.fc5smp:2127:warning: trying to assign nonexistent symbol I2C_PARPORT_LIGHT /boot/config-2.6.18-1.2257.fc5smp:2128:warning: trying to assign nonexistent symbol I2C_PROSAVAGE /boot/config-2.6.18-1.2257.fc5smp:2129:warning: trying to assign nonexistent symbol I2C_SAVAGE4 /boot/config-2.6.18-1.2257.fc5smp:2130:warning: trying to assign nonexistent symbol SCx200_ACB /boot/config-2.6.18-1.2257.fc5smp:2131:warning: trying to assign nonexistent symbol I2C_SIS5595 /boot/config-2.6.18-1.2257.fc5smp:2132:warning: trying to assign nonexistent symbol I2C_SIS630 /boot/config-2.6.18-1.2257.fc5smp:2133:warning: trying to assign nonexistent symbol I2C_SIS96X /boot/config-2.6.18-1.2257.fc5smp:2134:warning: trying to assign nonexistent symbol I2C_STUB /boot/config-2.6.18-1.2257.fc5smp:2135:warning: trying to assign nonexistent symbol I2C_VIA /boot/config-2.6.18-1.2257.fc5smp:2136:warning: trying to assign nonexistent symbol I2C_VIAPRO /boot/config-2.6.18-1.2257.fc5smp:2137:warning: trying to assign nonexistent symbol I2C_VOODOO3 /boot/config-2.6.18-1.2257.fc5smp:2138:warning: trying to assign nonexistent symbol I2C_PCA_ISA /boot/config-2.6.18-1.2257.fc5smp:2143:warning: trying to assign nonexistent symbol SENSORS_DS1337 /boot/config-2.6.18-1.2257.fc5smp:2144:warning: trying to assign nonexistent symbol SENSORS_DS1374 /boot/config-2.6.18-1.2257.fc5smp:2145:warning: trying to assign nonexistent symbol SENSORS_EEPROM /boot/config-2.6.18-1.2257.fc5smp:2146:warning: trying to assign nonexistent symbol SENSORS_PCF8574 /boot/config-2.6.18-1.2257.fc5smp:2147:warning: trying to assign nonexistent symbol SENSORS_PCA9539 /boot/config-2.6.18-1.2257.fc5smp:2148:warning: trying to assign nonexistent symbol SENSORS_PCF8591 /boot/config-2.6.18-1.2257.fc5smp:2149:warning: trying to assign nonexistent symbol SENSORS_MAX6875 /boot/config-2.6.18-1.2257.fc5smp:2150:warning: trying to assign nonexistent symbol I2C_DEBUG_CORE /boot/config-2.6.18-1.2257.fc5smp:2151:warning: trying to assign nonexistent symbol I2C_DEBUG_ALGO /boot/config-2.6.18-1.2257.fc5smp:2152:warning: trying to assign nonexistent symbol I2C_DEBUG_BUS /boot/config-2.6.18-1.2257.fc5smp:2153:warning: trying to assign nonexistent symbol I2C_DEBUG_CHIP /boot/config-2.6.18-1.2257.fc5smp:2158:warning: trying to assign nonexistent symbol SPI /boot/config-2.6.18-1.2257.fc5smp:2159:warning: trying to assign nonexistent symbol SPI_MASTER /boot/config-2.6.18-1.2257.fc5smp:2164:warning: trying to assign nonexistent symbol W1 /boot/config-2.6.18-1.2257.fc5smp:2169:warning: trying to assign nonexistent symbol HWMON /boot/config-2.6.18-1.2257.fc5smp:2170:warning: trying to assign nonexistent symbol HWMON_VID /boot/config-2.6.18-1.2257.fc5smp:2171:warning: trying to assign nonexistent symbol SENSORS_ABITUGURU /boot/config-2.6.18-1.2257.fc5smp:2172:warning: trying to assign nonexistent symbol SENSORS_ADM1021 /boot/config-2.6.18-1.2257.fc5smp:2173:warning: trying to assign nonexistent symbol SENSORS_ADM1025 /boot/config-2.6.18-1.2257.fc5smp:2174:warning: trying to assign nonexistent symbol SENSORS_ADM1026 /boot/config-2.6.18-1.2257.fc5smp:2175:warning: trying to assign nonexistent symbol SENSORS_ADM1031 /boot/config-2.6.18-1.2257.fc5smp:2176:warning: trying to assign nonexistent symbol SENSORS_ADM9240 /boot/config-2.6.18-1.2257.fc5smp:2177:warning: trying to assign nonexistent symbol SENSORS_ASB100 /boot/config-2.6.18-1.2257.fc5smp:2178:warning: trying to assign nonexistent symbol SENSORS_ATXP1 /boot/config-2.6.18-1.2257.fc5smp:2179:warning: trying to assign nonexistent symbol SENSORS_DS1621 /boot/config-2.6.18-1.2257.fc5smp:2180:warning: trying to assign nonexistent symbol SENSORS_F71805F /boot/config-2.6.18-1.2257.fc5smp:2181:warning: trying to assign nonexistent symbol SENSORS_FSCHER /boot/config-2.6.18-1.2257.fc5smp:2182:warning: trying to assign nonexistent symbol SENSORS_FSCPOS /boot/config-2.6.18-1.2257.fc5smp:2183:warning: trying to assign nonexistent symbol SENSORS_GL518SM /boot/config-2.6.18-1.2257.fc5smp:2184:warning: trying to assign nonexistent symbol SENSORS_GL520SM /boot/config-2.6.18-1.2257.fc5smp:2185:warning: trying to assign nonexistent symbol SENSORS_IT87 /boot/config-2.6.18-1.2257.fc5smp:2186:warning: trying to assign nonexistent symbol SENSORS_LM63 /boot/config-2.6.18-1.2257.fc5smp:2187:warning: trying to assign nonexistent symbol SENSORS_LM75 /boot/config-2.6.18-1.2257.fc5smp:2188:warning: trying to assign nonexistent symbol SENSORS_LM77 /boot/config-2.6.18-1.2257.fc5smp:2189:warning: trying to assign nonexistent symbol SENSORS_LM78 /boot/config-2.6.18-1.2257.fc5smp:2190:warning: trying to assign nonexistent symbol SENSORS_LM80 /boot/config-2.6.18-1.2257.fc5smp:2191:warning: trying to assign nonexistent symbol SENSORS_LM83 /boot/config-2.6.18-1.2257.fc5smp:2192:warning: trying to assign nonexistent symbol SENSORS_LM85 /boot/config-2.6.18-1.2257.fc5smp:2193:warning: trying to assign nonexistent symbol SENSORS_LM87 /boot/config-2.6.18-1.2257.fc5smp:2194:warning: trying to assign nonexistent symbol SENSORS_LM90 /boot/config-2.6.18-1.2257.fc5smp:2195:warning: trying to assign nonexistent symbol SENSORS_LM92 /boot/config-2.6.18-1.2257.fc5smp:2196:warning: trying to assign nonexistent symbol SENSORS_MAX1619 /boot/config-2.6.18-1.2257.fc5smp:2197:warning: trying to assign nonexistent symbol SENSORS_PC87360 /boot/config-2.6.18-1.2257.fc5smp:2198:warning: trying to assign nonexistent symbol SENSORS_SIS5595 /boot/config-2.6.18-1.2257.fc5smp:2199:warning: trying to assign nonexistent symbol SENSORS_SMSC47M1 /boot/config-2.6.18-1.2257.fc5smp:2200:warning: trying to assign nonexistent symbol SENSORS_SMSC47M192 /boot/config-2.6.18-1.2257.fc5smp:2201:warning: trying to assign nonexistent symbol SENSORS_SMSC47B397 /boot/config-2.6.18-1.2257.fc5smp:2202:warning: trying to assign nonexistent symbol SENSORS_VIA686A /boot/config-2.6.18-1.2257.fc5smp:2203:warning: trying to assign nonexistent symbol SENSORS_VT8231 /boot/config-2.6.18-1.2257.fc5smp:2204:warning: trying to assign nonexistent symbol SENSORS_W83781D /boot/config-2.6.18-1.2257.fc5smp:2205:warning: trying to assign nonexistent symbol SENSORS_W83791D /boot/config-2.6.18-1.2257.fc5smp:2206:warning: trying to assign nonexistent symbol SENSORS_W83792D /boot/config-2.6.18-1.2257.fc5smp:2207:warning: trying to assign nonexistent symbol SENSORS_W83L785TS /boot/config-2.6.18-1.2257.fc5smp:2208:warning: trying to assign nonexistent symbol SENSORS_W83627HF /boot/config-2.6.18-1.2257.fc5smp:2209:warning: trying to assign nonexistent symbol SENSORS_W83627EHF /boot/config-2.6.18-1.2257.fc5smp:2210:warning: trying to assign nonexistent symbol SENSORS_HDAPS /boot/config-2.6.18-1.2257.fc5smp:2211:warning: trying to assign nonexistent symbol HWMON_DEBUG_CHIP /boot/config-2.6.18-1.2257.fc5smp:2216:warning: trying to assign nonexistent symbol IBM_ASM /boot/config-2.6.18-1.2257.fc5smp:2221:warning: trying to assign nonexistent symbol VIDEO_DEV /boot/config-2.6.18-1.2257.fc5smp:2222:warning: trying to assign nonexistent symbol VIDEO_V4L1 /boot/config-2.6.18-1.2257.fc5smp:2223:warning: trying to assign nonexistent symbol VIDEO_V4L1_COMPAT /boot/config-2.6.18-1.2257.fc5smp:2224:warning: trying to assign nonexistent symbol VIDEO_V4L2 /boot/config-2.6.18-1.2257.fc5smp:2233:warning: trying to assign nonexistent symbol VIDEO_ADV_DEBUG /boot/config-2.6.18-1.2257.fc5smp:2234:warning: trying to assign nonexistent symbol VIDEO_VIVI /boot/config-2.6.18-1.2257.fc5smp:2235:warning: trying to assign nonexistent symbol VIDEO_BT848 /boot/config-2.6.18-1.2257.fc5smp:2236:warning: trying to assign nonexistent symbol VIDEO_BT848_DVB /boot/config-2.6.18-1.2257.fc5smp:2237:warning: trying to assign nonexistent symbol VIDEO_SAA6588 /boot/config-2.6.18-1.2257.fc5smp:2238:warning: trying to assign nonexistent symbol VIDEO_PMS /boot/config-2.6.18-1.2257.fc5smp:2239:warning: trying to assign nonexistent symbol VIDEO_BWQCAM /boot/config-2.6.18-1.2257.fc5smp:2240:warning: trying to assign nonexistent symbol VIDEO_CQCAM /boot/config-2.6.18-1.2257.fc5smp:2241:warning: trying to assign nonexistent symbol VIDEO_W9966 /boot/config-2.6.18-1.2257.fc5smp:2242:warning: trying to assign nonexistent symbol VIDEO_CPIA /boot/config-2.6.18-1.2257.fc5smp:2243:warning: trying to assign nonexistent symbol VIDEO_CPIA_PP /boot/config-2.6.18-1.2257.fc5smp:2244:warning: trying to assign nonexistent symbol VIDEO_CPIA_USB /boot/config-2.6.18-1.2257.fc5smp:2245:warning: trying to assign nonexistent symbol VIDEO_CPIA2 /boot/config-2.6.18-1.2257.fc5smp:2246:warning: trying to assign nonexistent symbol VIDEO_SAA5246A /boot/config-2.6.18-1.2257.fc5smp:2247:warning: trying to assign nonexistent symbol VIDEO_SAA5249 /boot/config-2.6.18-1.2257.fc5smp:2248:warning: trying to assign nonexistent symbol TUNER_3036 /boot/config-2.6.18-1.2257.fc5smp:2249:warning: trying to assign nonexistent symbol VIDEO_STRADIS /boot/config-2.6.18-1.2257.fc5smp:2250:warning: trying to assign nonexistent symbol VIDEO_ZORAN /boot/config-2.6.18-1.2257.fc5smp:2251:warning: trying to assign nonexistent symbol VIDEO_ZORAN_BUZ /boot/config-2.6.18-1.2257.fc5smp:2252:warning: trying to assign nonexistent symbol VIDEO_ZORAN_DC10 /boot/config-2.6.18-1.2257.fc5smp:2253:warning: trying to assign nonexistent symbol VIDEO_ZORAN_DC30 /boot/config-2.6.18-1.2257.fc5smp:2254:warning: trying to assign nonexistent symbol VIDEO_ZORAN_LML33 /boot/config-2.6.18-1.2257.fc5smp:2255:warning: trying to assign nonexistent symbol VIDEO_ZORAN_LML33R10 /boot/config-2.6.18-1.2257.fc5smp:2256:warning: trying to assign nonexistent symbol VIDEO_ZORAN_AVS6EYES /boot/config-2.6.18-1.2257.fc5smp:2257:warning: trying to assign nonexistent symbol VIDEO_MEYE /boot/config-2.6.18-1.2257.fc5smp:2258:warning: trying to assign nonexistent symbol VIDEO_SAA7134 /boot/config-2.6.18-1.2257.fc5smp:2259:warning: trying to assign nonexistent symbol VIDEO_SAA7134_ALSA /boot/config-2.6.18-1.2257.fc5smp:2260:warning: trying to assign nonexistent symbol VIDEO_SAA7134_DVB /boot/config-2.6.18-1.2257.fc5smp:2261:warning: trying to assign nonexistent symbol VIDEO_SAA7134_DVB_ALL_FRONTENDS /boot/config-2.6.18-1.2257.fc5smp:2262:warning: trying to assign nonexistent symbol VIDEO_MXB /boot/config-2.6.18-1.2257.fc5smp:2263:warning: trying to assign nonexistent symbol VIDEO_DPC /boot/config-2.6.18-1.2257.fc5smp:2264:warning: trying to assign nonexistent symbol VIDEO_HEXIUM_ORION /boot/config-2.6.18-1.2257.fc5smp:2265:warning: trying to assign nonexistent symbol VIDEO_HEXIUM_GEMINI /boot/config-2.6.18-1.2257.fc5smp:2266:warning: trying to assign nonexistent symbol VIDEO_CX88_VP3054 /boot/config-2.6.18-1.2257.fc5smp:2267:warning: trying to assign nonexistent symbol VIDEO_CX88 /boot/config-2.6.18-1.2257.fc5smp:2268:warning: trying to assign nonexistent symbol VIDEO_CX88_ALSA /boot/config-2.6.18-1.2257.fc5smp:2269:warning: trying to assign nonexistent symbol VIDEO_CX88_BLACKBIRD /boot/config-2.6.18-1.2257.fc5smp:2270:warning: trying to assign nonexistent symbol VIDEO_CX88_DVB /boot/config-2.6.18-1.2257.fc5smp:2271:warning: trying to assign nonexistent symbol VIDEO_CX88_DVB_ALL_FRONTENDS /boot/config-2.6.18-1.2257.fc5smp:2276:warning: trying to assign nonexistent symbol VIDEO_MSP3400 /boot/config-2.6.18-1.2257.fc5smp:2277:warning: trying to assign nonexistent symbol VIDEO_CS53L32A /boot/config-2.6.18-1.2257.fc5smp:2278:warning: trying to assign nonexistent symbol VIDEO_TLV320AIC23B /boot/config-2.6.18-1.2257.fc5smp:2279:warning: trying to assign nonexistent symbol VIDEO_WM8775 /boot/config-2.6.18-1.2257.fc5smp:2280:warning: trying to assign nonexistent symbol VIDEO_WM8739 /boot/config-2.6.18-1.2257.fc5smp:2281:warning: trying to assign nonexistent symbol VIDEO_CX2341X /boot/config-2.6.18-1.2257.fc5smp:2282:warning: trying to assign nonexistent symbol VIDEO_CX25840 /boot/config-2.6.18-1.2257.fc5smp:2283:warning: trying to assign nonexistent symbol VIDEO_SAA711X /boot/config-2.6.18-1.2257.fc5smp:2284:warning: trying to assign nonexistent symbol VIDEO_SAA7127 /boot/config-2.6.18-1.2257.fc5smp:2285:warning: trying to assign nonexistent symbol VIDEO_UPD64031A /boot/config-2.6.18-1.2257.fc5smp:2286:warning: trying to assign nonexistent symbol VIDEO_UPD64083 /boot/config-2.6.18-1.2257.fc5smp:2291:warning: trying to assign nonexistent symbol VIDEO_PVRUSB2 /boot/config-2.6.18-1.2257.fc5smp:2292:warning: trying to assign nonexistent symbol VIDEO_PVRUSB2_24XXX /boot/config-2.6.18-1.2257.fc5smp:2293:warning: trying to assign nonexistent symbol VIDEO_PVRUSB2_SYSFS /boot/config-2.6.18-1.2257.fc5smp:2294:warning: trying to assign nonexistent symbol VIDEO_PVRUSB2_DEBUGIFC /boot/config-2.6.18-1.2257.fc5smp:2295:warning: trying to assign nonexistent symbol VIDEO_EM28XX /boot/config-2.6.18-1.2257.fc5smp:2296:warning: trying to assign nonexistent symbol VIDEO_USBVIDEO /boot/config-2.6.18-1.2257.fc5smp:2297:warning: trying to assign nonexistent symbol USB_VICAM /boot/config-2.6.18-1.2257.fc5smp:2298:warning: trying to assign nonexistent symbol USB_IBMCAM /boot/config-2.6.18-1.2257.fc5smp:2299:warning: trying to assign nonexistent symbol USB_KONICAWC /boot/config-2.6.18-1.2257.fc5smp:2300:warning: trying to assign nonexistent symbol USB_QUICKCAM_MESSENGER /boot/config-2.6.18-1.2257.fc5smp:2301:warning: trying to assign nonexistent symbol USB_ET61X251 /boot/config-2.6.18-1.2257.fc5smp:2302:warning: trying to assign nonexistent symbol VIDEO_OVCAMCHIP /boot/config-2.6.18-1.2257.fc5smp:2303:warning: trying to assign nonexistent symbol USB_W9968CF /boot/config-2.6.18-1.2257.fc5smp:2304:warning: trying to assign nonexistent symbol USB_OV511 /boot/config-2.6.18-1.2257.fc5smp:2305:warning: trying to assign nonexistent symbol USB_SE401 /boot/config-2.6.18-1.2257.fc5smp:2306:warning: trying to assign nonexistent symbol USB_SN9C102 /boot/config-2.6.18-1.2257.fc5smp:2307:warning: trying to assign nonexistent symbol USB_STV680 /boot/config-2.6.18-1.2257.fc5smp:2308:warning: trying to assign nonexistent symbol USB_ZC0301 /boot/config-2.6.18-1.2257.fc5smp:2309:warning: trying to assign nonexistent symbol USB_PWC /boot/config-2.6.18-1.2257.fc5smp:2310:warning: trying to assign nonexistent symbol USB_PWC_DEBUG /boot/config-2.6.18-1.2257.fc5smp:2315:warning: trying to assign nonexistent symbol RADIO_CADET /boot/config-2.6.18-1.2257.fc5smp:2316:warning: trying to assign nonexistent symbol RADIO_RTRACK /boot/config-2.6.18-1.2257.fc5smp:2317:warning: trying to assign nonexistent symbol RADIO_RTRACK2 /boot/config-2.6.18-1.2257.fc5smp:2318:warning: trying to assign nonexistent symbol RADIO_AZTECH /boot/config-2.6.18-1.2257.fc5smp:2319:warning: trying to assign nonexistent symbol RADIO_GEMTEK /boot/config-2.6.18-1.2257.fc5smp:2320:warning: trying to assign nonexistent symbol RADIO_GEMTEK_PCI /boot/config-2.6.18-1.2257.fc5smp:2321:warning: trying to assign nonexistent symbol RADIO_MAXIRADIO /boot/config-2.6.18-1.2257.fc5smp:2322:warning: trying to assign nonexistent symbol RADIO_MAESTRO /boot/config-2.6.18-1.2257.fc5smp:2323:warning: trying to assign nonexistent symbol RADIO_SF16FMI /boot/config-2.6.18-1.2257.fc5smp:2324:warning: trying to assign nonexistent symbol RADIO_SF16FMR2 /boot/config-2.6.18-1.2257.fc5smp:2325:warning: trying to assign nonexistent symbol RADIO_TERRATEC /boot/config-2.6.18-1.2257.fc5smp:2326:warning: trying to assign nonexistent symbol RADIO_TRUST /boot/config-2.6.18-1.2257.fc5smp:2327:warning: trying to assign nonexistent symbol RADIO_TYPHOON /boot/config-2.6.18-1.2257.fc5smp:2328:warning: trying to assign nonexistent symbol RADIO_ZOLTRIX /boot/config-2.6.18-1.2257.fc5smp:2329:warning: trying to assign nonexistent symbol USB_DSBR /boot/config-2.6.18-1.2257.fc5smp:2334:warning: trying to assign nonexistent symbol DVB /boot/config-2.6.18-1.2257.fc5smp:2335:warning: trying to assign nonexistent symbol DVB_CORE /boot/config-2.6.18-1.2257.fc5smp:2340:warning: trying to assign nonexistent symbol DVB_AV7110 /boot/config-2.6.18-1.2257.fc5smp:2341:warning: trying to assign nonexistent symbol DVB_AV7110_OSD /boot/config-2.6.18-1.2257.fc5smp:2342:warning: trying to assign nonexistent symbol DVB_BUDGET /boot/config-2.6.18-1.2257.fc5smp:2343:warning: trying to assign nonexistent symbol DVB_BUDGET_CI /boot/config-2.6.18-1.2257.fc5smp:2344:warning: trying to assign nonexistent symbol DVB_BUDGET_AV /boot/config-2.6.18-1.2257.fc5smp:2345:warning: trying to assign nonexistent symbol DVB_BUDGET_PATCH /boot/config-2.6.18-1.2257.fc5smp:2350:warning: trying to assign nonexistent symbol DVB_USB /boot/config-2.6.18-1.2257.fc5smp:2351:warning: trying to assign nonexistent symbol DVB_USB_DEBUG /boot/config-2.6.18-1.2257.fc5smp:2352:warning: trying to assign nonexistent symbol DVB_USB_A800 /boot/config-2.6.18-1.2257.fc5smp:2353:warning: trying to assign nonexistent symbol DVB_USB_DIBUSB_MB /boot/config-2.6.18-1.2257.fc5smp:2354:warning: trying to assign nonexistent symbol DVB_USB_DIBUSB_MB_FAULTY /boot/config-2.6.18-1.2257.fc5smp:2355:warning: trying to assign nonexistent symbol DVB_USB_DIBUSB_MC /boot/config-2.6.18-1.2257.fc5smp:2356:warning: trying to assign nonexistent symbol DVB_USB_UMT_010 /boot/config-2.6.18-1.2257.fc5smp:2357:warning: trying to assign nonexistent symbol DVB_USB_CXUSB /boot/config-2.6.18-1.2257.fc5smp:2358:warning: trying to assign nonexistent symbol DVB_USB_DIGITV /boot/config-2.6.18-1.2257.fc5smp:2359:warning: trying to assign nonexistent symbol DVB_USB_VP7045 /boot/config-2.6.18-1.2257.fc5smp:2360:warning: trying to assign nonexistent symbol DVB_USB_VP702X /boot/config-2.6.18-1.2257.fc5smp:2361:warning: trying to assign nonexistent symbol DVB_USB_GP8PSK /boot/config-2.6.18-1.2257.fc5smp:2362:warning: trying to assign nonexistent symbol DVB_USB_NOVA_T_USB2 /boot/config-2.6.18-1.2257.fc5smp:2363:warning: trying to assign nonexistent symbol DVB_USB_DTT200U /boot/config-2.6.18-1.2257.fc5smp:2364:warning: trying to assign nonexistent symbol DVB_TTUSB_BUDGET /boot/config-2.6.18-1.2257.fc5smp:2365:warning: trying to assign nonexistent symbol DVB_TTUSB_DEC /boot/config-2.6.18-1.2257.fc5smp:2366:warning: trying to assign nonexistent symbol DVB_CINERGYT2 /boot/config-2.6.18-1.2257.fc5smp:2367:warning: trying to assign nonexistent symbol DVB_CINERGYT2_TUNING /boot/config-2.6.18-1.2257.fc5smp:2368:warning: trying to assign nonexistent symbol DVB_CINERGYT2_STREAM_URB_COUNT /boot/config-2.6.18-1.2257.fc5smp:2369:warning: trying to assign nonexistent symbol DVB_CINERGYT2_STREAM_BUF_SIZE /boot/config-2.6.18-1.2257.fc5smp:2370:warning: trying to assign nonexistent symbol DVB_CINERGYT2_QUERY_INTERVAL /boot/config-2.6.18-1.2257.fc5smp:2371:warning: trying to assign nonexistent symbol DVB_CINERGYT2_ENABLE_RC_INPUT_DEVICE /boot/config-2.6.18-1.2257.fc5smp:2372:warning: trying to assign nonexistent symbol DVB_CINERGYT2_RC_QUERY_INTERVAL /boot/config-2.6.18-1.2257.fc5smp:2377:warning: trying to assign nonexistent symbol DVB_B2C2_FLEXCOP /boot/config-2.6.18-1.2257.fc5smp:2378:warning: trying to assign nonexistent symbol DVB_B2C2_FLEXCOP_PCI /boot/config-2.6.18-1.2257.fc5smp:2379:warning: trying to assign nonexistent symbol DVB_B2C2_FLEXCOP_USB /boot/config-2.6.18-1.2257.fc5smp:2380:warning: trying to assign nonexistent symbol DVB_B2C2_FLEXCOP_DEBUG /boot/config-2.6.18-1.2257.fc5smp:2385:warning: trying to assign nonexistent symbol DVB_BT8XX /boot/config-2.6.18-1.2257.fc5smp:2390:warning: trying to assign nonexistent symbol DVB_PLUTO2 /boot/config-2.6.18-1.2257.fc5smp:2403:warning: trying to assign nonexistent symbol DVB_STV0299 /boot/config-2.6.18-1.2257.fc5smp:2404:warning: trying to assign nonexistent symbol DVB_CX24110 /boot/config-2.6.18-1.2257.fc5smp:2405:warning: trying to assign nonexistent symbol DVB_CX24123 /boot/config-2.6.18-1.2257.fc5smp:2406:warning: trying to assign nonexistent symbol DVB_TDA8083 /boot/config-2.6.18-1.2257.fc5smp:2407:warning: trying to assign nonexistent symbol DVB_MT312 /boot/config-2.6.18-1.2257.fc5smp:2408:warning: trying to assign nonexistent symbol DVB_VES1X93 /boot/config-2.6.18-1.2257.fc5smp:2409:warning: trying to assign nonexistent symbol DVB_S5H1420 /boot/config-2.6.18-1.2257.fc5smp:2414:warning: trying to assign nonexistent symbol DVB_SP8870 /boot/config-2.6.18-1.2257.fc5smp:2415:warning: trying to assign nonexistent symbol DVB_SP887X /boot/config-2.6.18-1.2257.fc5smp:2416:warning: trying to assign nonexistent symbol DVB_CX22700 /boot/config-2.6.18-1.2257.fc5smp:2417:warning: trying to assign nonexistent symbol DVB_CX22702 /boot/config-2.6.18-1.2257.fc5smp:2418:warning: trying to assign nonexistent symbol DVB_L64781 /boot/config-2.6.18-1.2257.fc5smp:2419:warning: trying to assign nonexistent symbol DVB_TDA1004X /boot/config-2.6.18-1.2257.fc5smp:2420:warning: trying to assign nonexistent symbol DVB_NXT6000 /boot/config-2.6.18-1.2257.fc5smp:2421:warning: trying to assign nonexistent symbol DVB_MT352 /boot/config-2.6.18-1.2257.fc5smp:2422:warning: trying to assign nonexistent symbol DVB_ZL10353 /boot/config-2.6.18-1.2257.fc5smp:2423:warning: trying to assign nonexistent symbol DVB_DIB3000MB /boot/config-2.6.18-1.2257.fc5smp:2424:warning: trying to assign nonexistent symbol DVB_DIB3000MC /boot/config-2.6.18-1.2257.fc5smp:2429:warning: trying to assign nonexistent symbol DVB_VES1820 /boot/config-2.6.18-1.2257.fc5smp:2430:warning: trying to assign nonexistent symbol DVB_TDA10021 /boot/config-2.6.18-1.2257.fc5smp:2431:warning: trying to assign nonexistent symbol DVB_STV0297 /boot/config-2.6.18-1.2257.fc5smp:2436:warning: trying to assign nonexistent symbol DVB_NXT200X /boot/config-2.6.18-1.2257.fc5smp:2437:warning: trying to assign nonexistent symbol DVB_OR51211 /boot/config-2.6.18-1.2257.fc5smp:2438:warning: trying to assign nonexistent symbol DVB_OR51132 /boot/config-2.6.18-1.2257.fc5smp:2439:warning: trying to assign nonexistent symbol DVB_BCM3510 /boot/config-2.6.18-1.2257.fc5smp:2440:warning: trying to assign nonexistent symbol DVB_LGDT330X /boot/config-2.6.18-1.2257.fc5smp:2445:warning: trying to assign nonexistent symbol DVB_PLL /boot/config-2.6.18-1.2257.fc5smp:2446:warning: trying to assign nonexistent symbol DVB_LNBP21 /boot/config-2.6.18-1.2257.fc5smp:2447:warning: trying to assign nonexistent symbol DVB_ISL6421 /boot/config-2.6.18-1.2257.fc5smp:2448:warning: trying to assign nonexistent symbol VIDEO_SAA7146 /boot/config-2.6.18-1.2257.fc5smp:2449:warning: trying to assign nonexistent symbol VIDEO_SAA7146_VV /boot/config-2.6.18-1.2257.fc5smp:2450:warning: trying to assign nonexistent symbol VIDEO_VIDEOBUF /boot/config-2.6.18-1.2257.fc5smp:2451:warning: trying to assign nonexistent symbol VIDEO_TUNER /boot/config-2.6.18-1.2257.fc5smp:2452:warning: trying to assign nonexistent symbol VIDEO_BUF /boot/config-2.6.18-1.2257.fc5smp:2453:warning: trying to assign nonexistent symbol VIDEO_BUF_DVB /boot/config-2.6.18-1.2257.fc5smp:2454:warning: trying to assign nonexistent symbol VIDEO_BTCX /boot/config-2.6.18-1.2257.fc5smp:2455:warning: trying to assign nonexistent symbol VIDEO_IR /boot/config-2.6.18-1.2257.fc5smp:2456:warning: trying to assign nonexistent symbol VIDEO_TVEEPROM /boot/config-2.6.18-1.2257.fc5smp:2457:warning: trying to assign nonexistent symbol USB_DABUSB /boot/config-2.6.18-1.2257.fc5smp:2462:warning: trying to assign nonexistent symbol FIRMWARE_EDID /boot/config-2.6.18-1.2257.fc5smp:2463:warning: trying to assign nonexistent symbol FB /boot/config-2.6.18-1.2257.fc5smp:2464:warning: trying to assign nonexistent symbol FB_CFB_FILLRECT /boot/config-2.6.18-1.2257.fc5smp:2465:warning: trying to assign nonexistent symbol FB_CFB_COPYAREA /boot/config-2.6.18-1.2257.fc5smp:2466:warning: trying to assign nonexistent symbol FB_CFB_IMAGEBLIT /boot/config-2.6.18-1.2257.fc5smp:2467:warning: trying to assign nonexistent symbol FB_MACMODES /boot/config-2.6.18-1.2257.fc5smp:2468:warning: trying to assign nonexistent symbol FB_BACKLIGHT /boot/config-2.6.18-1.2257.fc5smp:2469:warning: trying to assign nonexistent symbol FB_MODE_HELPERS /boot/config-2.6.18-1.2257.fc5smp:2470:warning: trying to assign nonexistent symbol FB_TILEBLITTING /boot/config-2.6.18-1.2257.fc5smp:2471:warning: trying to assign nonexistent symbol FB_CIRRUS /boot/config-2.6.18-1.2257.fc5smp:2472:warning: trying to assign nonexistent symbol FB_PM2 /boot/config-2.6.18-1.2257.fc5smp:2473:warning: trying to assign nonexistent symbol FB_CYBER2000 /boot/config-2.6.18-1.2257.fc5smp:2474:warning: trying to assign nonexistent symbol FB_ARC /boot/config-2.6.18-1.2257.fc5smp:2475:warning: trying to assign nonexistent symbol FB_ASILIANT /boot/config-2.6.18-1.2257.fc5smp:2476:warning: trying to assign nonexistent symbol FB_IMSTT /boot/config-2.6.18-1.2257.fc5smp:2477:warning: trying to assign nonexistent symbol FB_VGA16 /boot/config-2.6.18-1.2257.fc5smp:2478:warning: trying to assign nonexistent symbol FB_VESA /boot/config-2.6.18-1.2257.fc5smp:2479:warning: trying to assign nonexistent symbol FB_IMAC /boot/config-2.6.18-1.2257.fc5smp:2480:warning: trying to assign nonexistent symbol FB_HGA /boot/config-2.6.18-1.2257.fc5smp:2481:warning: trying to assign nonexistent symbol FB_S1D13XXX /boot/config-2.6.18-1.2257.fc5smp:2482:warning: trying to assign nonexistent symbol FB_NVIDIA /boot/config-2.6.18-1.2257.fc5smp:2483:warning: trying to assign nonexistent symbol FB_NVIDIA_I2C /boot/config-2.6.18-1.2257.fc5smp:2484:warning: trying to assign nonexistent symbol FB_RIVA /boot/config-2.6.18-1.2257.fc5smp:2485:warning: trying to assign nonexistent symbol FB_RIVA_I2C /boot/config-2.6.18-1.2257.fc5smp:2486:warning: trying to assign nonexistent symbol FB_RIVA_DEBUG /boot/config-2.6.18-1.2257.fc5smp:2487:warning: trying to assign nonexistent symbol FB_I810 /boot/config-2.6.18-1.2257.fc5smp:2488:warning: trying to assign nonexistent symbol FB_I810_GTF /boot/config-2.6.18-1.2257.fc5smp:2489:warning: trying to assign nonexistent symbol FB_I810_I2C /boot/config-2.6.18-1.2257.fc5smp:2490:warning: trying to assign nonexistent symbol FB_INTEL /boot/config-2.6.18-1.2257.fc5smp:2491:warning: trying to assign nonexistent symbol FB_INTEL_DEBUG /boot/config-2.6.18-1.2257.fc5smp:2492:warning: trying to assign nonexistent symbol FB_MATROX /boot/config-2.6.18-1.2257.fc5smp:2493:warning: trying to assign nonexistent symbol FB_MATROX_MILLENIUM /boot/config-2.6.18-1.2257.fc5smp:2494:warning: trying to assign nonexistent symbol FB_MATROX_MYSTIQUE /boot/config-2.6.18-1.2257.fc5smp:2495:warning: trying to assign nonexistent symbol FB_MATROX_G /boot/config-2.6.18-1.2257.fc5smp:2496:warning: trying to assign nonexistent symbol FB_MATROX_I2C /boot/config-2.6.18-1.2257.fc5smp:2497:warning: trying to assign nonexistent symbol FB_MATROX_MAVEN /boot/config-2.6.18-1.2257.fc5smp:2498:warning: trying to assign nonexistent symbol FB_MATROX_MULTIHEAD /boot/config-2.6.18-1.2257.fc5smp:2499:warning: trying to assign nonexistent symbol FB_RADEON /boot/config-2.6.18-1.2257.fc5smp:2500:warning: trying to assign nonexistent symbol FB_RADEON_I2C /boot/config-2.6.18-1.2257.fc5smp:2501:warning: trying to assign nonexistent symbol FB_RADEON_DEBUG /boot/config-2.6.18-1.2257.fc5smp:2502:warning: trying to assign nonexistent symbol FB_ATY128 /boot/config-2.6.18-1.2257.fc5smp:2503:warning: trying to assign nonexistent symbol FB_ATY /boot/config-2.6.18-1.2257.fc5smp:2504:warning: trying to assign nonexistent symbol FB_ATY_CT /boot/config-2.6.18-1.2257.fc5smp:2505:warning: trying to assign nonexistent symbol FB_ATY_GENERIC_LCD /boot/config-2.6.18-1.2257.fc5smp:2506:warning: trying to assign nonexistent symbol FB_ATY_GX /boot/config-2.6.18-1.2257.fc5smp:2507:warning: trying to assign nonexistent symbol FB_SAVAGE /boot/config-2.6.18-1.2257.fc5smp:2508:warning: trying to assign nonexistent symbol FB_SAVAGE_I2C /boot/config-2.6.18-1.2257.fc5smp:2509:warning: trying to assign nonexistent symbol FB_SAVAGE_ACCEL /boot/config-2.6.18-1.2257.fc5smp:2510:warning: trying to assign nonexistent symbol FB_SIS /boot/config-2.6.18-1.2257.fc5smp:2511:warning: trying to assign nonexistent symbol FB_NEOMAGIC /boot/config-2.6.18-1.2257.fc5smp:2512:warning: trying to assign nonexistent symbol FB_KYRO /boot/config-2.6.18-1.2257.fc5smp:2513:warning: trying to assign nonexistent symbol FB_3DFX /boot/config-2.6.18-1.2257.fc5smp:2514:warning: trying to assign nonexistent symbol FB_3DFX_ACCEL /boot/config-2.6.18-1.2257.fc5smp:2515:warning: trying to assign nonexistent symbol FB_VOODOO1 /boot/config-2.6.18-1.2257.fc5smp:2516:warning: trying to assign nonexistent symbol FB_CYBLA /boot/config-2.6.18-1.2257.fc5smp:2517:warning: trying to assign nonexistent symbol FB_TRIDENT /boot/config-2.6.18-1.2257.fc5smp:2518:warning: trying to assign nonexistent symbol FB_TRIDENT_ACCEL /boot/config-2.6.18-1.2257.fc5smp:2519:warning: trying to assign nonexistent symbol FB_GEODE /boot/config-2.6.18-1.2257.fc5smp:2520:warning: trying to assign nonexistent symbol FB_VIRTUAL /boot/config-2.6.18-1.2257.fc5smp:2525:warning: trying to assign nonexistent symbol VGA_CONSOLE /boot/config-2.6.18-1.2257.fc5smp:2526:warning: trying to assign nonexistent symbol VGACON_SOFT_SCROLLBACK /boot/config-2.6.18-1.2257.fc5smp:2527:warning: trying to assign nonexistent symbol VGACON_SOFT_SCROLLBACK_SIZE /boot/config-2.6.18-1.2257.fc5smp:2528:warning: trying to assign nonexistent symbol VIDEO_SELECT /boot/config-2.6.18-1.2257.fc5smp:2529:warning: trying to assign nonexistent symbol MDA_CONSOLE /boot/config-2.6.18-1.2257.fc5smp:2530:warning: trying to assign nonexistent symbol DUMMY_CONSOLE /boot/config-2.6.18-1.2257.fc5smp:2531:warning: trying to assign nonexistent symbol FRAMEBUFFER_CONSOLE /boot/config-2.6.18-1.2257.fc5smp:2532:warning: trying to assign nonexistent symbol FRAMEBUFFER_CONSOLE_ROTATION /boot/config-2.6.18-1.2257.fc5smp:2533:warning: trying to assign nonexistent symbol FONTS /boot/config-2.6.18-1.2257.fc5smp:2534:warning: trying to assign nonexistent symbol FONT_8x8 /boot/config-2.6.18-1.2257.fc5smp:2535:warning: trying to assign nonexistent symbol FONT_8x16 /boot/config-2.6.18-1.2257.fc5smp:2540:warning: trying to assign nonexistent symbol LOGO /boot/config-2.6.18-1.2257.fc5smp:2541:warning: trying to assign nonexistent symbol LOGO_LINUX_MONO /boot/config-2.6.18-1.2257.fc5smp:2542:warning: trying to assign nonexistent symbol LOGO_LINUX_VGA16 /boot/config-2.6.18-1.2257.fc5smp:2543:warning: trying to assign nonexistent symbol LOGO_LINUX_CLUT224 /boot/config-2.6.18-1.2257.fc5smp:2544:warning: trying to assign nonexistent symbol BACKLIGHT_LCD_SUPPORT /boot/config-2.6.18-1.2257.fc5smp:2545:warning: trying to assign nonexistent symbol BACKLIGHT_CLASS_DEVICE /boot/config-2.6.18-1.2257.fc5smp:2546:warning: trying to assign nonexistent symbol BACKLIGHT_DEVICE /boot/config-2.6.18-1.2257.fc5smp:2547:warning: trying to assign nonexistent symbol LCD_CLASS_DEVICE /boot/config-2.6.18-1.2257.fc5smp:2548:warning: trying to assign nonexistent symbol LCD_DEVICE /boot/config-2.6.18-1.2257.fc5smp:2553:warning: trying to assign nonexistent symbol SOUND /boot/config-2.6.18-1.2257.fc5smp:2558:warning: trying to assign nonexistent symbol SND /boot/config-2.6.18-1.2257.fc5smp:2559:warning: trying to assign nonexistent symbol SND_TIMER /boot/config-2.6.18-1.2257.fc5smp:2560:warning: trying to assign nonexistent symbol SND_PCM /boot/config-2.6.18-1.2257.fc5smp:2561:warning: trying to assign nonexistent symbol SND_HWDEP /boot/config-2.6.18-1.2257.fc5smp:2562:warning: trying to assign nonexistent symbol SND_RAWMIDI /boot/config-2.6.18-1.2257.fc5smp:2563:warning: trying to assign nonexistent symbol SND_SEQUENCER /boot/config-2.6.18-1.2257.fc5smp:2564:warning: trying to assign nonexistent symbol SND_SEQ_DUMMY From natanael.copa at gmail.com Fri Jan 5 14:10:34 2007 From: natanael.copa at gmail.com (Natanael Copa) Date: Fri, 05 Jan 2007 23:10:34 +0100 Subject: Building a pkgsrc port of busybox In-Reply-To: <35f70db10701050823q2a506bd5rc6a179b1f85dbf49@mail.gmail.com> References: <35f70db10701050709p7cec3a31o3dfcfec85b43b69e@mail.gmail.com> <35f70db10701050823q2a506bd5rc6a179b1f85dbf49@mail.gmail.com> Message-ID: <1168035034.22628.139.camel@studio> On Fri, 2007-01-05 at 18:23 +0200, Ross Cameron wrote: > A bit more info on this one,.... > > At the bottom of this email I've attached my previous busybox build > script that works 100%,... how would I get the same functionality in > pkgsrc? > > cp "../control/busybox-suid-config" .config ^^^^^^^^^^^^^ I believe you have to re-create this file From develop at cle-mens.de Sat Jan 6 06:19:50 2007 From: develop at cle-mens.de (Dirk Clemens) Date: Sat, 06 Jan 2007 15:19:50 +0100 Subject: busybox 1.2.1 diff is buggy Message-ID: <459FB006.3060909@cle-mens.de> Hi I use busybox 1.2.1 with current patches on a Siemens Gigaset M740AV (dvb-t setopbox, mips) I have found the following diff error: $ echo abc >foo $ echo abc | diff - foo --- - Sat Jan 6 15:12:21 2007 +++ foo Sat Jan 6 15:12:12 2007 @@ -0,0 +1 @@ +abc $ echo $? 1 $echo xyz | diff - foo --- - Sat Jan 6 15:12:35 2007 +++ foo Sat Jan 6 15:12:12 2007 @@ -0,0 +1 @@ +abc $ echo $? 1 and my last test ... $ diff - foo reads from stdin And that means: diff is reading from stdin, but thinking, that stdin is empty. Dirk From rep.nop at aon.at Sat Jan 6 07:44:08 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Sat, 6 Jan 2007 16:44:08 +0100 Subject: busybox 1.2.1 diff is buggy In-Reply-To: <459FB006.3060909@cle-mens.de> References: <459FB006.3060909@cle-mens.de> Message-ID: <20070106154408.GA17577@aon.at> On Sat, Jan 06, 2007 at 03:19:50PM +0100, Dirk Clemens wrote: >Hi > >I use busybox 1.2.1 with current patches on >a Siemens Gigaset M740AV (dvb-t setopbox, mips) You don't link statically against glibc, do you? See busybox.net/ note for 1.2.2.1 From develop at cle-mens.de Sat Jan 6 08:35:49 2007 From: develop at cle-mens.de (Dirk Clemens) Date: Sat, 06 Jan 2007 17:35:49 +0100 Subject: busybox 1.2.1 diff is buggy In-Reply-To: <20070106154408.GA17577@aon.at> References: <459FB006.3060909@cle-mens.de> <20070106154408.GA17577@aon.at> Message-ID: <459FCFE5.6090107@cle-mens.de> Bernhard Fischer wrote: > On Sat, Jan 06, 2007 at 03:19:50PM +0100, Dirk Clemens wrote: >> Hi >> >> I use busybox 1.2.1 with current patches on >> a Siemens Gigaset M740AV (dvb-t setopbox, mips) > > You don't link statically against glibc, do you? > See busybox.net/ note for 1.2.2.1 > no, it's shared linked against uClibc-0.9.29.so Dirk From vda.linux at googlemail.com Sat Jan 6 15:03:31 2007 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sun, 7 Jan 2007 00:03:31 +0100 Subject: busybox 1.2.1 diff is buggy In-Reply-To: <459FB006.3060909@cle-mens.de> References: <459FB006.3060909@cle-mens.de> Message-ID: <200701070003.31166.vda.linux@googlemail.com> On Saturday 06 January 2007 15:19, Dirk Clemens wrote: > Hi > > I use busybox 1.2.1 with current patches on > a Siemens Gigaset M740AV (dvb-t setopbox, mips) > > I have found the following diff error: > > $ echo abc >foo > $ echo abc | diff - foo > --- - Sat Jan 6 15:12:21 2007 > +++ foo Sat Jan 6 15:12:12 2007 > @@ -0,0 +1 @@ > +abc > > $ echo $? > 1 diff doesn't support diffing non-seekable streams currently. Code uses fseek() and rewind(). I will make diff complain and exit instead of producing bad diff. Can't say when proper fix will be done. -- vda From rep.nop at aon.at Sun Jan 7 04:20:50 2007 From: rep.nop at aon.at (Bernhard Fischer) Date: Sun, 7 Jan 2007 13:20:50 +0100 Subject: svn commit: trunk/busybox: include networking In-Reply-To: <20070107012412.D3CCB485E7@busybox.net> References: <20070107012412.D3CCB485E7@busybox.net> Message-ID: <20070107122050.GC17577@aon.at> On Sat, Jan 06, 2007 at 05:24:12PM -0800, vda at busybox.net wrote: >Author: vda >Date: 2007-01-06 17:24:12 -0800 (Sat, 06 Jan 2007) >New Revision: 17177 > >Log: >add arp applet - thanks to >"Eric Spakman" > > >Modified: > trunk/busybox/include/applets.h > trunk/busybox/include/libbb.h > trunk/busybox/include/u