From roy at marples.name Fri Feb 1 03:46:11 2008 From: roy at marples.name (Roy Marples) Date: Fri, 01 Feb 2008 11:46:11 +0000 Subject: [PATCH] fsck -A goes into infinite loop and kills all processes In-Reply-To: <1201811567.3887.1.camel@uberlaptop.marples.name> References: <25800.1201801922@brightstareng.com> <1201803456.4267.1.camel@uberlaptop.marples.name> <1201811567.3887.1.camel@uberlaptop.marples.name> Message-ID: <1201866371.5420.3.camel@uberlaptop.marples.name> On Thu, 2008-01-31 at 20:32 +0000, Roy Marples wrote: > On Thu, 2008-01-31 at 18:17 +0000, Roy Marples wrote: > > Ah yes, it's because there is no helper installed for ext4dev. Ensuring > > that all helpers exist fixes the error. So it's not handling exec errors > > correctly. I'll see if I can fix fsck now. > > The execute function does not return when pid is <1, so it stores -1 as > a pid to kill, which kills quite a bit really :) Attached is a new patch that free's any malloced memory correctly. BTW, this behaviour should match upstream as if the don't find a helper then they free the instance and return even if noexecute is set. As the spawn function does that as well, we just need to check if pid is less than 1. Thanks Roy -------------- next part -------------- A non-text attachment was scrubbed... Name: busybox-fsck.patch Type: text/x-patch Size: 469 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080201/463d921e/attachment.bin From rep.dot.nop at gmail.com Fri Feb 1 05:08:31 2008 From: rep.dot.nop at gmail.com (Bernhard Fischer) Date: Fri, 1 Feb 2008 14:08:31 +0100 Subject: [PATCH] fsck -A goes into infinite loop and kills all processes In-Reply-To: <1201866371.5420.3.camel@uberlaptop.marples.name> References: <25800.1201801922@brightstareng.com> <1201803456.4267.1.camel@uberlaptop.marples.name> <1201811567.3887.1.camel@uberlaptop.marples.name> <1201866371.5420.3.camel@uberlaptop.marples.name> Message-ID: <20080201130831.GA2127@aon.at> On Fri, Feb 01, 2008 at 11:46:11AM +0000, Roy Marples wrote: > >On Thu, 2008-01-31 at 20:32 +0000, Roy Marples wrote: >> On Thu, 2008-01-31 at 18:17 +0000, Roy Marples wrote: >> > Ah yes, it's because there is no helper installed for ext4dev. Ensuring >> > that all helpers exist fixes the error. So it's not handling exec errors >> > correctly. I'll see if I can fix fsck now. >> >> The execute function does not return when pid is <1, so it stores -1 as >> a pid to kill, which kills quite a bit really :) > >Attached is a new patch that free's any malloced memory correctly. BTW, Yes, but this should be dependant on whether ENABLE_FEATURE_CLEAN_UP is requested. >this behaviour should match upstream as if the don't find a helper then >they free the instance and return even if noexecute is set. As the spawn >function does that as well, we just need to check if pid is less than 1. From dronnikov at gmail.com Fri Feb 1 05:30:08 2008 From: dronnikov at gmail.com (Vladimir Dronnikov) Date: Fri, 1 Feb 2008 16:30:08 +0300 Subject: Microcom updated Message-ID: <6784529b0802010530j57992b9fu1195742bebd0650f@mail.gmail.com> Hello! I' ve prepared new version of microcom applet. It now should correctly handle slow devices when used non-interactively. Also added -X option which turns off special processing of Ctrl-X -- immediately quit microcom and Ctrl+@ -- send break sequence to device Denys, please consider applying. -- Vladimir -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20080201/42ccf094/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: microcom.c Type: text/x-csrc Size: 4694 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080201/42ccf094/attachment.c From obelix0 at yahoo.fr Fri Feb 1 06:06:48 2008 From: obelix0 at yahoo.fr (Obelix) Date: Fri, 1 Feb 2008 06:06:48 -0800 (PST) Subject: sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD Message-ID: <949405.37450.qm@web53102.mail.re2.yahoo.com> Hi, I'm a newbie with bb and I would like to compil a bb :D I have a complete bubybox project that some ohters compile, so it's works. Now I would like to compile on my own PC and I have this error when I do a "make" I found in the FAQ that there is a problem with the version of sed and I'm using sed 4.1.2 on a sarge (debian 3.0) My questions are : - my problem came from the version of sed ? - which version of sed I need ? - I need to be root to do a make / make menuconfig ? Many thanks for your help Obelix ------------------------------------------------------------------------------------------------------------------------------------ ~/bb/make sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD sysdeps/linux/Config.in:106: invalid menu option sysdeps/linux/Config.in:107: syntax error, unexpected T_WORD sysdeps/linux/Config.in:120: invalid menu option sysdeps/linux/Config.in:120: syntax error, unexpected T_BOOLEAN sysdeps/linux/Config.in:121: invalid menu option sysdeps/linux/Config.in:121: syntax error, unexpected T_DEFAULT sysdeps/linux/Config.in:122: invalid menu option sysdeps/linux/Config.in:122: syntax error, unexpected T_DEPENDS sysdeps/linux/Config.in:123: invalid menu option sysdeps/linux/Config.in:123: syntax error, unexpected T_HELP sysdeps/linux/Config.in:124: invalid menu option sysdeps/linux/Config.in:124: syntax error, unexpected T_WORD sysdeps/linux/Config.in:128: invalid menu option sysdeps/linux/Config.in:128: syntax error, unexpected T_BOOLEAN sysdeps/linux/Config.in:129: invalid menu option sysdeps/linux/Config.in:129: syntax error, unexpected T_DEFAULT sysdeps/linux/Config.in:130: invalid menu option sysdeps/linux/Config.in:130: syntax error, unexpected T_HELP sysdeps/linux/Config.in:131: invalid menu option sysdeps/linux/Config.in:131: syntax error, unexpected T_WORD sysdeps/linux/Config.in:143: invalid menu option sysdeps/linux/Config.in:158: syntax error, unexpected T_WORD sysdeps/linux/Config.in:161: invalid menu option sysdeps/linux/Config.in:161: syntax error, unexpected T_BOOLEAN sysdeps/linux/Config.in:162: invalid menu option sysdeps/linux/Config.in:162: syntax error, unexpected T_DEFAULT sysdeps/linux/Config.in:163: invalid menu option sysdeps/linux/Config.in:163: syntax error, unexpected T_SELECT sysdeps/linux/Config.in:164: invalid menu option sysdeps/linux/Config.in:164: syntax error, unexpected T_HELP sysdeps/linux/Config.in:165: invalid menu option sysdeps/linux/Config.in:165: syntax error, unexpected T_WORD sysdeps/linux/Config.in:166: invalid menu option sysdeps/linux/Config.in:166: syntax error, unexpected T_WORD sysdeps/linux/Config.in:167: invalid menu option sysdeps/linux/Config.in:167: syntax error, unexpected T_WORD sysdeps/linux/Config.in:171: invalid menu option ------------------------------------------------------------------------------------------------------------------------------------ ____________________________________________________________________________________________ Yahoo! Mail innove : interface hyper pratique, messenger int?gr?, couleurs - http://mail.yahoo.fr From vapier at gentoo.org Fri Feb 1 06:29:12 2008 From: vapier at gentoo.org (Mike Frysinger) Date: Fri, 1 Feb 2008 09:29:12 -0500 Subject: sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD In-Reply-To: <949405.37450.qm@web53102.mail.re2.yahoo.com> References: <949405.37450.qm@web53102.mail.re2.yahoo.com> Message-ID: <200802010929.12782.vapier@gentoo.org> On Friday 01 February 2008, Obelix wrote: > sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD this file isnt part of busybox, so i dont know what you're actually using -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: This is a digitally signed message part. Url : http://busybox.net/lists/busybox/attachments/20080201/c5047111/attachment-0001.pgp From obelix0 at yahoo.fr Fri Feb 1 07:46:38 2008 From: obelix0 at yahoo.fr (Obelix) Date: Fri, 1 Feb 2008 07:46:38 -0800 (PST) Subject: sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD Message-ID: <282426.93979.qm@web53105.mail.re2.yahoo.com> Thanks for your help I found the line in the bb makefile who have a problem : ./scripts/config/conf -o sysdeps/linux/Config.in but I don't know why :( ------------------------------ On Friday 01 February 2008, Obelix wrote: > sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD this file isnt part of busybox, so i dont know what you're actually using -mike _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr From vapier at gentoo.org Fri Feb 1 07:59:56 2008 From: vapier at gentoo.org (Mike Frysinger) Date: Fri, 1 Feb 2008 10:59:56 -0500 Subject: sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD In-Reply-To: <282426.93979.qm@web53105.mail.re2.yahoo.com> References: <282426.93979.qm@web53105.mail.re2.yahoo.com> Message-ID: <200802011059.57326.vapier@gentoo.org> On Friday 01 February 2008, Obelix wrote: > Thanks for your help please fix your e-mail client quoting. it's broken. > I found the line in the bb makefile who have a problem : > ./scripts/config/conf -o sysdeps/linux/Config.in > > but I don't know why :( you're using a very old busybox. please test with the latest release. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: This is a digitally signed message part. Url : http://busybox.net/lists/busybox/attachments/20080201/60eb1596/attachment.pgp From obelix0 at yahoo.fr Fri Feb 1 08:07:47 2008 From: obelix0 at yahoo.fr (Obelix) Date: Fri, 1 Feb 2008 08:07:47 -0800 (PST) Subject: sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD Message-ID: <169796.90319.qm@web53112.mail.re2.yahoo.com> > please fix your e-mail client quoting. it's broken. sorry but I'm not on my PC :( > you're using a very old busybox. please test with the latest release. yes, I'm using busybox-1.00-rc3 but I haven't got the choice : I must rebuild this one ! I did a make -n to find the good line wha have a problem. The full log is : [~/busybox-1.00-rc3]./scripts/config/conf -o sysdeps/linux/Config.in sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD sysdeps/linux/Config.in:106: invalid menu option sysdeps/linux/Config.in:107: syntax error, unexpected T_WORD sysdeps/linux/Config.in:120: invalid menu option sysdeps/linux/Config.in:120: syntax error, unexpected T_BOOLEAN sysdeps/linux/Config.in:121: invalid menu option sysdeps/linux/Config.in:121: syntax error, unexpected T_DEFAULT sysdeps/linux/Config.in:122: invalid menu option sysdeps/linux/Config.in:122: syntax error, unexpected T_DEPENDS sysdeps/linux/Config.in:123: invalid menu option sysdeps/linux/Config.in:123: syntax error, unexpected T_HELP sysdeps/linux/Config.in:124: invalid menu option sysdeps/linux/Config.in:124: syntax error, unexpected T_WORD sysdeps/linux/Config.in:128: invalid menu option sysdeps/linux/Config.in:128: syntax error, unexpected T_BOOLEAN sysdeps/linux/Config.in:129: invalid menu option sysdeps/linux/Config.in:129: syntax error, unexpected T_DEFAULT sysdeps/linux/Config.in:130: invalid menu option sysdeps/linux/Config.in:130: syntax error, unexpected T_HELP sysdeps/linux/Config.in:131: invalid menu option sysdeps/linux/Config.in:131: syntax error, unexpected T_WORD sysdeps/linux/Config.in:143: invalid menu option sysdeps/linux/Config.in:158: syntax error, unexpected T_WORD sysdeps/linux/Config.in:161: invalid menu option sysdeps/linux/Config.in:161: syntax error, unexpected T_BOOLEAN sysdeps/linux/Config.in:162: invalid menu option sysdeps/linux/Config.in:162: syntax error, unexpected T_DEFAULT sysdeps/linux/Config.in:163: invalid menu option sysdeps/linux/Config.in:163: syntax error, unexpected T_SELECT sysdeps/linux/Config.in:164: invalid menu option sysdeps/linux/Config.in:164: syntax error, unexpected T_HELP sysdeps/linux/Config.in:165: invalid menu option sysdeps/linux/Config.in:165: syntax error, unexpected T_WORD sysdeps/linux/Config.in:166: invalid menu option sysdeps/linux/Config.in:166: syntax error, unexpected T_WORD sysdeps/linux/Config.in:167: invalid menu option sysdeps/linux/Config.in:167: syntax error, unexpected T_WORD sysdeps/linux/Config.in:171: invalid menu option archival/Config.in:20: syntax error, unexpected T_WORD archival/Config.in:29: invalid menu option archival/Config.in:29: syntax error, unexpected T_WORD archival/Config.in:32: invalid menu option archival/Config.in:32: syntax error, unexpected T_BOOLEAN archival/Config.in:33: invalid menu option archival/Config.in:33: syntax error, unexpected T_DEFAULT archival/Config.in:34: invalid menu option archival/Config.in:34: syntax error, unexpected T_DEPENDS archival/Config.in:35: invalid menu option archival/Config.in:35: syntax error, unexpected T_HELP archival/Config.in:36: invalid menu option archival/Config.in:36: syntax error, unexpected T_WORD archival/Config.in:37: invalid menu option archival/Config.in:37: syntax error, unexpected T_WORD archival/Config.in:42: invalid menu option archival/Config.in:42: syntax error, unexpected T_BOOLEAN archival/Config.in:43: invalid menu option archival/Config.in:43: syntax error, unexpected T_DEFAULT archival/Config.in:44: invalid menu option archival/Config.in:44: syntax error, unexpected T_HELP archival/Config.in:45: invalid menu option archival/Config.in:45: syntax error, unexpected T_WORD archival/Config.in:55: invalid menu option archival/Config.in:55: syntax error, unexpected T_WORD archival/Config.in:58: invalid menu option archival/Config.in:58: syntax error, unexpected T_BOOLEAN archival/Config.in:59: invalid menu option archival/Config.in:59: syntax error, unexpected T_DEFAULT archival/Config.in:60: invalid menu option archival/Config.in:60: syntax error, unexpected T_HELP archival/Config.in:61: invalid menu option archival/Config.in:61: syntax error, unexpected T_WORD archival/Config.in:69: invalid menu option archival/Config.in:69: syntax error, unexpected T_WORD archival/Config.in:72: invalid menu option archival/Config.in:72: syntax error, unexpected T_BOOLEAN archival/Config.in:73: invalid menu option archival/Config.in:73: syntax error, unexpected T_DEFAULT archival/Config.in:74: invalid menu option archival/Config.in:74: syntax error, unexpected T_HELP archival/Config.in:75: invalid menu option archival/Config.in:75: syntax error, unexpected T_WORD archival/Config.in:79: invalid menu option archival/Config.in:86: syntax error, unexpected T_WORD archival/Config.in:89: invalid menu option archival/Config.in:89: syntax error, unexpected T_WORD archival/Config.in:92: invalid menu option archival/Config.in:92: syntax error, unexpected T_BOOLEAN archival/Config.in:93: invalid menu option archival/Config.in:93: syntax error, unexpected T_DEFAULT archival/Config.in:94: invalid menu option archival/Config.in:94: syntax error, unexpected T_DEPENDS archival/Config.in:95: invalid menu option archival/Config.in:95: syntax error, unexpected T_HELP archival/Config.in:96: invalid menu option archival/Config.in:96: syntax error, unexpected T_WORD archival/Config.in:101: invalid menu option archival/Config.in:101: syntax error, unexpected T_BOOLEAN archival/Config.in:102: invalid menu option archival/Config.in:102: syntax error, unexpected T_DEFAULT archival/Config.in:103: invalid menu option archival/Config.in:103: syntax error, unexpected T_HELP archival/Config.in:104: invalid menu option archival/Config.in:104: syntax error, unexpected T_WORD archival/Config.in:109: invalid menu option archival/Config.in:109: syntax error, unexpected T_BOOLEAN archival/Config.in:110: invalid menu option archival/Config.in:110: syntax error, unexpected T_DEFAULT archival/Config.in:111: invalid menu option archival/Config.in:111: syntax error, unexpected T_DEPENDS archival/Config.in:112: invalid menu option archival/Config.in:112: syntax error, unexpected T_HELP archival/Config.in:113: invalid menu option archival/Config.in:113: syntax error, unexpected T_WORD archival/Config.in:114: invalid menu option archival/Config.in:114: syntax error, unexpected T_WORD archival/Config.in:118: invalid menu option archival/Config.in:118: syntax error, unexpected T_BOOLEAN archival/Config.in:119: invalid menu option archival/Config.in:119: syntax error, unexpected T_DEFAULT archival/Config.in:120: invalid menu option archival/Config.in:120: syntax error, unexpected T_HELP archival/Config.in:121: invalid menu option archival/Config.in:121: syntax error, unexpected T_WORD archival/Config.in:125: invalid menu option archival/Config.in:125: syntax error, unexpected T_BOOLEAN archival/Config.in:126: invalid menu option archival/Config.in:126: syntax error, unexpected T_DEFAULT archival/Config.in:127: invalid menu option archival/Config.in:127: syntax error, unexpected T_HELP archival/Config.in:128: invalid menu option archival/Config.in:128: syntax error, unexpected T_WORD archival/Config.in:131: invalid menu option archival/Config.in:131: syntax error, unexpected T_BOOLEAN archival/Config.in:132: invalid menu option archival/Config.in:132: syntax error, unexpected T_DEFAULT archival/Config.in:133: invalid menu option archival/Config.in:133: syntax error, unexpected T_HELP archival/Config.in:134: invalid menu option archival/Config.in:134: syntax error, unexpected T_WORD archival/Config.in:137: invalid menu option archival/Config.in:137: syntax error, unexpected T_BOOLEAN archival/Config.in:138: invalid menu option archival/Config.in:138: syntax error, unexpected T_DEFAULT archival/Config.in:139: invalid menu option archival/Config.in:139: syntax error, unexpected T_HELP archival/Config.in:140: invalid menu option archival/Config.in:140: syntax error, unexpected T_WORD archival/Config.in:145: invalid menu option archival/Config.in:145: syntax error, unexpected T_BOOLEAN archival/Config.in:146: invalid menu option archival/Config.in:146: syntax error, unexpected T_DEFAULT archival/Config.in:147: invalid menu option archival/Config.in:147: syntax error, unexpected T_DEPENDS archival/Config.in:148: invalid menu option archival/Config.in:148: syntax error, unexpected T_HELP archival/Config.in:149: invalid menu option archival/Config.in:149: syntax error, unexpected T_WORD archival/Config.in:148:warning: multi-line strings not supported archival/Config.in:150: invalid menu option archival/Config.in:150: syntax error, unexpected T_WORD archival/Config.in:153: invalid menu option archival/Config.in:153: syntax error, unexpected T_BOOLEAN archival/Config.in:154: invalid menu option archival/Config.in:154: syntax error, unexpected T_DEFAULT archival/Config.in:155: invalid menu option archival/Config.in:155: syntax error, unexpected T_DEPENDS archival/Config.in:156: invalid menu option archival/Config.in:156: syntax error, unexpected T_HELP archival/Config.in:157: invalid menu option archival/Config.in:157: syntax error, unexpected T_WORD archival/Config.in:156:warning: multi-line strings not supported archival/Config.in:158: invalid menu option archival/Config.in:158: syntax error, unexpected T_WORD archival/Config.in:161: invalid menu option archival/Config.in:161: syntax error, unexpected T_BOOLEAN archival/Config.in:162: invalid menu option archival/Config.in:162: syntax error, unexpected T_DEFAULT archival/Config.in:163: invalid menu option archival/Config.in:163: syntax error, unexpected T_DEPENDS archival/Config.in:164: invalid menu option archival/Config.in:164: syntax error, unexpected T_HELP archival/Config.in:165: invalid menu option archival/Config.in:165: syntax error, unexpected T_WORD archival/Config.in:164:warning: multi-line strings not supported archival/Config.in:166: invalid menu option archival/Config.in:166: syntax error, unexpected T_WORD archival/Config.in:169: invalid menu option archival/Config.in:169: syntax error, unexpected T_BOOLEAN archival/Config.in:170: invalid menu option archival/Config.in:170: syntax error, unexpected T_DEFAULT archival/Config.in:171: invalid menu option archival/Config.in:171: syntax error, unexpected T_DEPENDS archival/Config.in:172: invalid menu option archival/Config.in:172: syntax error, unexpected T_HELP archival/Config.in:173: invalid menu option archival/Config.in:173: syntax error, unexpected T_WORD archival/Config.in:174: invalid menu option archival/Config.in:174: syntax error, unexpected T_WORD archival/Config.in:177: invalid menu option archival/Config.in:177: syntax error, unexpected T_BOOLEAN archival/Config.in:178: invalid menu option archival/Config.in:178: syntax error, unexpected T_DEFAULT archival/Config.in:179: invalid menu option archival/Config.in:179: syntax error, unexpected T_DEPENDS archival/Config.in:180: invalid menu option archival/Config.in:180: syntax error, unexpected T_HELP archival/Config.in:181: invalid menu option archival/Config.in:181: syntax error, unexpected T_WORD archival/Config.in:182: invalid menu option archival/Config.in:182: syntax error, unexpected T_WORD archival/Config.in:185: invalid menu option archival/Config.in:185: syntax error, unexpected T_BOOLEAN archival/Config.in:186: invalid menu option archival/Config.in:186: syntax error, unexpected T_DEFAULT archival/Config.in:187: invalid menu option archival/Config.in:187: syntax error, unexpected T_DEPENDS archival/Config.in:188: invalid menu option archival/Config.in:188: syntax error, unexpected T_HELP archival/Config.in:189: invalid menu option archival/Config.in:189: syntax error, unexpected T_WORD archival/Config.in:191: invalid menu option archival/Config.in:191: syntax error, unexpected T_WORD archival/Config.in:194: invalid menu option archival/Config.in:194: syntax error, unexpected T_BOOLEAN archival/Config.in:195: invalid menu option archival/Config.in:195: syntax error, unexpected T_DEFAULT archival/Config.in:196: invalid menu option archival/Config.in:196: syntax error, unexpected T_DEPENDS archival/Config.in:197: invalid menu option archival/Config.in:197: syntax error, unexpected T_HELP archival/Config.in:198: invalid menu option archival/Config.in:198: syntax error, unexpected T_WORD archival/Config.in:202: invalid menu option archival/Config.in:202: syntax error, unexpected T_BOOLEAN archival/Config.in:203: invalid menu option archival/Config.in:203: syntax error, unexpected T_DEFAULT archival/Config.in:204: invalid menu option archival/Config.in:204: syntax error, unexpected T_DEPENDS archival/Config.in:205: invalid menu option archival/Config.in:205: syntax error, unexpected T_HELP archival/Config.in:206: invalid menu option archival/Config.in:206: syntax error, unexpected T_WORD archival/Config.in:209: invalid menu option archival/Config.in:209: syntax error, unexpected T_BOOLEAN archival/Config.in:210: invalid menu option archival/Config.in:210: syntax error, unexpected T_DEFAULT archival/Config.in:211: invalid menu option archival/Config.in:211: syntax error, unexpected T_HELP archival/Config.in:212: invalid menu option archival/Config.in:212: syntax error, unexpected T_WORD archival/Config.in:216: invalid menu option archival/Config.in:216: syntax error, unexpected T_BOOLEAN archival/Config.in:217: invalid menu option archival/Config.in:217: syntax error, unexpected T_DEFAULT archival/Config.in:218: invalid menu option archival/Config.in:218: syntax error, unexpected T_HELP archival/Config.in:219: invalid menu option archival/Config.in:219: syntax error, unexpected T_WORD archival/Config.in:221: invalid menu option archival/Config.in:221: syntax error, unexpected T_WORD archival/Config.in:224: invalid menu option archival/Config.in:245: syntax error, unexpected T_WORD archival/Config.in:248: invalid menu option archival/Config.in:248: syntax error, unexpected T_BOOLEAN archival/Config.in:249: invalid menu option archival/Config.in:249: syntax error, unexpected T_DEFAULT archival/Config.in:250: invalid menu option archival/Config.in:250: syntax error, unexpected T_DEPENDS archival/Config.in:251: invalid menu option archival/Config.in:251: syntax error, unexpected T_HELP archival/Config.in:252: invalid menu option archival/Config.in:252: syntax error, unexpected T_WORD archival/Config.in:256: invalid menu option archival/Config.in:256: syntax error, unexpected T_WORD archival/Config.in:259: invalid menu option coreutils/Config.in:611: syntax error, unexpected T_WORD coreutils/Config.in:614: invalid menu option debianutils/Config.in:33: syntax error, unexpected T_WORD debianutils/Config.in:43: invalid menu option debianutils/Config.in:43: syntax error, unexpected T_BOOLEAN debianutils/Config.in:44: invalid menu option debianutils/Config.in:44: syntax error, unexpected T_DEFAULT debianutils/Config.in:45: invalid menu option debianutils/Config.in:45: syntax error, unexpected T_HELP debianutils/Config.in:46: invalid menu option debianutils/Config.in:46: syntax error, unexpected T_WORD debianutils/Config.in:51: invalid menu option debianutils/Config.in:51: syntax error, unexpected T_BOOLEAN debianutils/Config.in:52: invalid menu option debianutils/Config.in:52: syntax error, unexpected T_DEFAULT debianutils/Config.in:53: invalid menu option debianutils/Config.in:53: syntax error, unexpected T_HELP debianutils/Config.in:54: invalid menu option debianutils/Config.in:54: syntax error, unexpected T_WORD debianutils/Config.in:58: invalid menu option loginutils/Config.in:19: syntax error, unexpected T_WORD loginutils/Config.in:24: invalid menu option loginutils/Config.in:24: syntax error, unexpected T_WORD loginutils/Config.in:28: invalid menu option loginutils/Config.in:137: syntax error, unexpected T_WORD loginutils/Config.in:145: invalid menu option miscutils/Config.in:59: syntax error, unexpected T_WORD miscutils/Config.in:60: invalid menu option networking/Config.in:206: syntax error, unexpected T_WORD networking/Config.in:210: invalid menu option networking/Config.in:210: syntax error, unexpected T_BOOLEAN networking/Config.in:211: invalid menu option networking/Config.in:211: syntax error, unexpected T_DEFAULT networking/Config.in:212: invalid menu option networking/Config.in:212: syntax error, unexpected T_DEPENDS networking/Config.in:213: invalid menu option networking/Config.in:213: syntax error, unexpected T_SELECT networking/Config.in:214: invalid menu option networking/Config.in:214: syntax error, unexpected T_SELECT networking/Config.in:215: invalid menu option networking/Config.in:215: syntax error, unexpected T_HELP networking/Config.in:216: invalid menu option networking/Config.in:216: syntax error, unexpected T_WORD networking/Config.in:224: invalid menu option networking/Config.in:224: syntax error, unexpected T_BOOLEAN networking/Config.in:225: invalid menu option networking/Config.in:225: syntax error, unexpected T_DEFAULT networking/Config.in:226: invalid menu option networking/Config.in:226: syntax error, unexpected T_DEPENDS networking/Config.in:227: invalid menu option networking/Config.in:227: syntax error, unexpected T_HELP networking/Config.in:228: invalid menu option networking/Config.in:228: syntax error, unexpected T_WORD networking/Config.in:231: invalid menu option networking/Config.in:231: syntax error, unexpected T_BOOLEAN networking/Config.in:232: invalid menu option networking/Config.in:232: syntax error, unexpected T_DEFAULT networking/Config.in:233: invalid menu option networking/Config.in:233: syntax error, unexpected T_DEPENDS networking/Config.in:234: invalid menu option networking/Config.in:234: syntax error, unexpected T_HELP networking/Config.in:235: invalid menu option networking/Config.in:235: syntax error, unexpected T_WORD networking/Config.in:238: invalid menu option networking/Config.in:238: syntax error, unexpected T_BOOLEAN networking/Config.in:239: invalid menu option networking/Config.in:239: syntax error, unexpected T_DEFAULT networking/Config.in:240: invalid menu option networking/Config.in:240: syntax error, unexpected T_DEPENDS networking/Config.in:241: invalid menu option networking/Config.in:241: syntax error, unexpected T_HELP networking/Config.in:242: invalid menu option networking/Config.in:242: syntax error, unexpected T_WORD networking/Config.in:246: invalid menu option networking/Config.in:246: syntax error, unexpected T_BOOLEAN networking/Config.in:247: invalid menu option networking/Config.in:247: syntax error, unexpected T_DEFAULT networking/Config.in:248: invalid menu option networking/Config.in:248: syntax error, unexpected T_DEPENDS networking/Config.in:249: invalid menu option networking/Config.in:249: syntax error, unexpected T_HELP networking/Config.in:250: invalid menu option networking/Config.in:250: syntax error, unexpected T_WORD networking/Config.in:254: invalid menu option networking/Config.in:254: syntax error, unexpected T_BOOLEAN networking/Config.in:255: invalid menu option networking/Config.in:255: syntax error, unexpected T_DEFAULT networking/Config.in:256: invalid menu option networking/Config.in:256: syntax error, unexpected T_HELP networking/Config.in:257: invalid menu option networking/Config.in:257: syntax error, unexpected T_WORD networking/Config.in:260: invalid menu option networking/Config.in:260: syntax error, unexpected T_BOOLEAN networking/Config.in:261: invalid menu option networking/Config.in:261: syntax error, unexpected T_DEFAULT networking/Config.in:262: invalid menu option networking/Config.in:262: syntax error, unexpected T_DEPENDS networking/Config.in:263: invalid menu option networking/Config.in:263: syntax error, unexpected T_HELP networking/Config.in:264: invalid menu option networking/Config.in:264: syntax error, unexpected T_WORD networking/Config.in:267: invalid menu option networking/Config.in:267: syntax error, unexpected T_BOOLEAN networking/Config.in:268: invalid menu option networking/Config.in:268: syntax error, unexpected T_DEFAULT networking/Config.in:269: invalid menu option networking/Config.in:269: syntax error, unexpected T_DEPENDS networking/Config.in:270: invalid menu option networking/Config.in:270: syntax error, unexpected T_HELP networking/Config.in:271: invalid menu option networking/Config.in:271: syntax error, unexpected T_WORD networking/Config.in:274: invalid menu option networking/Config.in:274: syntax error, unexpected T_BOOLEAN networking/Config.in:275: invalid menu option networking/Config.in:275: syntax error, unexpected T_DEFAULT networking/Config.in:276: invalid menu option networking/Config.in:276: syntax error, unexpected T_DEPENDS networking/Config.in:277: invalid menu option networking/Config.in:277: syntax error, unexpected T_HELP networking/Config.in:278: invalid menu option networking/Config.in:278: syntax error, unexpected T_WORD networking/Config.in:281: invalid menu option networking/Config.in:281: syntax error, unexpected T_BOOLEAN networking/Config.in:282: invalid menu option networking/Config.in:282: syntax error, unexpected T_DEFAULT networking/Config.in:283: invalid menu option networking/Config.in:283: syntax error, unexpected T_DEPENDS networking/Config.in:284: invalid menu option networking/Config.in:284: syntax error, unexpected T_HELP networking/Config.in:285: invalid menu option networking/Config.in:285: syntax error, unexpected T_WORD networking/Config.in:288: invalid menu option networking/Config.in:288: syntax error, unexpected T_BOOLEAN networking/Config.in:289: invalid menu option networking/Config.in:289: syntax error, unexpected T_DEFAULT networking/Config.in:290: invalid menu option networking/Config.in:290: syntax error, unexpected T_DEPENDS networking/Config.in:291: invalid menu option networking/Config.in:291: syntax error, unexpected T_HELP networking/Config.in:292: invalid menu option networking/Config.in:292: syntax error, unexpected T_WORD networking/Config.in:296: invalid menu option networking/Config.in:296: syntax error, unexpected T_BOOLEAN networking/Config.in:297: invalid menu option networking/Config.in:297: syntax error, unexpected T_DEFAULT networking/Config.in:298: invalid menu option networking/Config.in:298: syntax error, unexpected T_HELP networking/Config.in:299: invalid menu option networking/Config.in:299: syntax error, unexpected T_WORD networking/Config.in:304: invalid menu option networking/Config.in:308: unexpected 'endif' within menu block networking/udhcp/Config.in:15: syntax error, unexpected T_WORD networking/udhcp/Config.in:18: invalid menu option networking/udhcp/Config.in:18: syntax error, unexpected T_BOOLEAN networking/udhcp/Config.in:19: invalid menu option networking/udhcp/Config.in:19: syntax error, unexpected T_DEFAULT networking/udhcp/Config.in:20: invalid menu option networking/udhcp/Config.in:20: syntax error, unexpected T_HELP networking/udhcp/Config.in:21: invalid menu option networking/udhcp/Config.in:21: syntax error, unexpected T_WORD networking/udhcp/Config.in:30: invalid menu option networking/udhcp/Config.in:30: syntax error, unexpected T_BOOLEAN networking/udhcp/Config.in:31: invalid menu option networking/udhcp/Config.in:31: syntax error, unexpected T_DEFAULT networking/udhcp/Config.in:32: invalid menu option networking/udhcp/Config.in:32: syntax error, unexpected T_DEPENDS networking/udhcp/Config.in:33: invalid menu option networking/udhcp/Config.in:33: syntax error, unexpected T_HELP networking/udhcp/Config.in:34: invalid menu option networking/udhcp/Config.in:34: syntax error, unexpected T_WORD networking/udhcp/Config.in:41: invalid menu option networking/udhcp/Config.in:41: syntax error, unexpected T_BOOLEAN networking/udhcp/Config.in:42: invalid menu option networking/udhcp/Config.in:42: syntax error, unexpected T_DEFAULT networking/udhcp/Config.in:43: invalid menu option networking/udhcp/Config.in:43: syntax error, unexpected T_DEPENDS networking/udhcp/Config.in:44: invalid menu option networking/udhcp/Config.in:44: syntax error, unexpected T_HELP networking/udhcp/Config.in:45: invalid menu option networking/udhcp/Config.in:45: syntax error, unexpected T_WORD networking/udhcp/Config.in:51: invalid menu option networking/udhcp/Config.in:51: syntax error, unexpected T_BOOLEAN networking/udhcp/Config.in:52: invalid menu option networking/udhcp/Config.in:52: syntax error, unexpected T_DEFAULT networking/udhcp/Config.in:53: invalid menu option networking/udhcp/Config.in:53: syntax error, unexpected T_DEPENDS networking/udhcp/Config.in:54: invalid menu option networking/udhcp/Config.in:54: syntax error, unexpected T_HELP networking/udhcp/Config.in:55: invalid menu option networking/udhcp/Config.in:55: syntax error, unexpected T_WORD networking/udhcp/Config.in:62: invalid menu option networking/Config.in:600: 'endmenu' in different file than 'menu' networking/Config.in:600: location of the 'menu' shell/Config.in:129: syntax error, unexpected T_WORD shell/Config.in:130: invalid menu option shell/Config.in:130: syntax error, unexpected T_WORD shell/Config.in:135: invalid menu option shell/Config.in:135: syntax error, unexpected T_BOOLEAN shell/Config.in:136: invalid menu option shell/Config.in:136: syntax error, unexpected T_DEFAULT shell/Config.in:137: invalid menu option shell/Config.in:137: syntax error, unexpected T_HELP shell/Config.in:138: invalid menu option shell/Config.in:138: syntax error, unexpected T_WORD shell/Config.in:140: invalid menu option shell/Config.in:140: syntax error, unexpected T_WORD shell/Config.in:144: invalid menu option sysdeps/linux/Config.in:248: syntax error, unexpected T_WORD sysdeps/linux/Config.in:251: invalid menu option sysdeps/linux/Config.in:251: syntax error, unexpected T_PROMPT sysdeps/linux/Config.in:252: invalid menu option sysdeps/linux/Config.in:252: syntax error, unexpected T_DEFAULT sysdeps/linux/Config.in:253: invalid menu option sysdeps/linux/Config.in:253: syntax error, unexpected T_DEPENDS sysdeps/linux/Config.in:254: invalid menu option sysdeps/linux/Config.in:254: syntax error, unexpected T_HELP sysdeps/linux/Config.in:255: invalid menu option sysdeps/linux/Config.in:255: syntax error, unexpected T_WORD sysdeps/linux/Config.in:264: invalid menu option sysdeps/linux/Config.in:264: syntax error, unexpected T_WORD sysdeps/linux/Config.in:282: invalid menu option sysdeps/linux/Config.in:282: syntax error, unexpected T_BOOLEAN sysdeps/linux/Config.in:283: invalid menu option sysdeps/linux/Config.in:291: unexpected 'endchoice' within menu block networking/udhcp/Config.in:6: missing 'endmenu' for this 'menu' statement networking/udhcp/Config.in:6: missing 'endmenu' for this 'menu' statement networking/udhcp/Config.in:6: missing 'endmenu' for this 'menu' statement networking/udhcp/Config.in:6: missing 'endmenu' for this 'menu' statement _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr From vapier at gentoo.org Fri Feb 1 08:47:06 2008 From: vapier at gentoo.org (Mike Frysinger) Date: Fri, 1 Feb 2008 11:47:06 -0500 Subject: sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD In-Reply-To: <169796.90319.qm@web53112.mail.re2.yahoo.com> References: <169796.90319.qm@web53112.mail.re2.yahoo.com> Message-ID: <200802011147.07330.vapier@gentoo.org> On Friday 01 February 2008, Obelix wrote: > sorry but I'm not on my PC :( then get an e-mail provider who doesnt have a broken web interface > yes, I'm using busybox-1.00-rc3 but I haven't got the choice yes you do > I must rebuild this one ! then you'll have to debug it. i imagine it's been fixed since. but we wont know unless you try. the version you're playing with is terribly outdated. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: This is a digitally signed message part. Url : http://busybox.net/lists/busybox/attachments/20080201/2efb8fc6/attachment.pgp From jsujjavanich at syntech-fuelmaster.com Fri Feb 1 14:15:54 2008 From: jsujjavanich at syntech-fuelmaster.com (Jate Sujjavanich) Date: Fri, 1 Feb 2008 17:15:54 -0500 Subject: msh and signals lost due to blocking In-Reply-To: Message-ID: Removing the SIGINT -> SIG_IGN on msh.c:2799 leads apparently prevents the SIGINT failure. Could the system calls be happening out of order? I haven't been able to get strace working yet. - Jate S. -----Original Message----- From: busybox-bounces at busybox.net [mailto:busybox-bounces at busybox.net] On Behalf Of Jate Sujjavanich Sent: Tuesday, January 29, 2008 5:51 PM To: Denis Vlasenko; busybox at busybox.net Subject: RE: msh and signals lost due to blocking I compiled busybox for x86, and the bug does not appear to manifest itself. I've been reproducing it by running a ping and hitting ctrl-C from the shell prompt. After about four successes, the signal block occurs. With version 1.7.2 on x86, I can do this at will. I fired up the kernel debugger. I ran ping and terminated it with a ctrl-C. It looks like there's an explicit system call which turns on the signal blocking. I haven't yet been able to determine if busybox msh is the culprit. The odd thing is that I added debug statements to call out sigprocmask calls in busybox, and that allowed me to ctrl-c many times. That is troubling. I am fairly certain that this was not a problem with the last version (whatever's in uClinux-dist) of busybox that I used. That version was incompatible with the new toolchain/uClibc I got from codesourcery (4.2-8). That led me to busybox 1.7.2 (where I am today). I haven't been able to try any other versions yet. - Jate S. -----Original Message----- From: Denis Vlasenko [mailto:vda.linux at googlemail.com] Sent: Tuesday, January 29, 2008 4:08 AM To: busybox at busybox.net Cc: Jate Sujjavanich Subject: Re: msh and signals lost due to blocking On Thursday 24 January 2008 22:54, Jate Sujjavanich wrote: > I am using msh from busybox 1.7.2 and kernel 2.4.31-uc0 on m68knommu. > The shell handles SIGINT properly one to four times. After these > successes, the process group has signals blocked, and it the processes > never dequeue SIGINT. Restarting the shell resets the blocks. The > cycle repeats. > > Does anyone familiar with msh know whether it activates signal blocking? Does it happen on desktop (x86 machine)? Can you post the .config? Can you describe how to reproduce it? msh seems to be relatively untouched for many versions, but it still worth checking. Can you try older busybox versions, built with same .config? > I am also not sure whether the something in the library does this. Not likely. Most probably it's msh bug. -- vda ************************************************************************ ************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************ ************ ************************************************************************ ************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************ ************ From vapier at gentoo.org Fri Feb 1 14:19:53 2008 From: vapier at gentoo.org (Mike Frysinger) Date: Fri, 1 Feb 2008 17:19:53 -0500 Subject: msh + cmdline editing is broken Message-ID: <200802011719.54233.vapier@gentoo.org> this was working in busybox-1.4.1, but broke between that and busybox-1.9.0 ... the quick test is to do `make allnoconfig` and then turn on just msh and command line editing. then when you run msh, do: $ ls $ ls lsls: command not found (so you type "ls", hit CTRL+C, then type "ls" again followed by return) also, if you send just EOF to kill the shell (ctrl+d), you get a new prompt instead of exiting ... perhaps someone more familiar with the new common command line editing can track down the issue quickly ... otherwise i'll be banging on it next week -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: This is a digitally signed message part. Url : http://busybox.net/lists/busybox/attachments/20080201/d30cabb5/attachment.pgp From cristian.ionescu-idbohrn at axis.com Fri Feb 1 15:05:03 2008 From: cristian.ionescu-idbohrn at axis.com (Cristian Ionescu-Idbohrn) Date: Sat, 2 Feb 2008 00:05:03 +0100 (CET) Subject: [patch] networking/ping.c In-Reply-To: <0801301451300.19715@somehost> References: <0801301451300.19715@somehost> Message-ID: <0802012353550.29870@somehost> On Wed, 30 Jan 2008, Cristian Ionescu-Idbohrn wrote: > Looks like last checkin with this comment: > > ,---- > | r20923 | aldot | 2008-01-29 11:33:34 +0100 (Tue, 29 Jan 2008) | 4 lines > | - be C99 friendly. Anonymous unions are a GNU extension. This change is > | size-neutral WRT -std=gnu99 and fixes several compilation errors for > | strict C99 mode. > `---- > > missed a couple of spots. Compilation error: Ok. No reaction, yet. Let me try again. If I disable FEATURE_FANCY_PING (which is enabled by default) and then try to build, I get this thrown at me: ,---- | networking/ping.c: In function 'ping4': | networking/ping.c:97: error: 'len_and_sockaddr' has no member named 'sin' | networking/ping.c: In function 'ping6': | networking/ping.c:141: error: 'len_and_sockaddr' has no member named 'sin6' | make[1]: *** [networking/ping.o] Error 1 `---- The attached patch corrects that. It also reorders networking/Config.in moving FEATURE_FANCY_PING next to PING6. Cheers, -- Cristian -------------- next part -------------- A non-text attachment was scrubbed... Name: ping-and-Config.patch Type: text/x-diff Size: 1361 bytes Desc: Url : http://busybox.net/lists/busybox/attachments/20080202/4a8bb466/attachment.bin From pgf at brightstareng.com Fri Feb 1 15:25:54 2008 From: pgf at brightstareng.com (Paul Fox) Date: Fri, 01 Feb 2008 18:25:54 -0500 Subject: [patch] networking/ping.c In-Reply-To: cristian.ionescu-idbohrn's message of Sat, 02 Feb 2008 00:05:03 +0100. <0802012353550.29870@somehost> Message-ID: <15879.1201908354@brightstareng.com> > > Ok. No reaction, yet. Let me try again. > > If I disable FEATURE_FANCY_PING (which is enabled by default) and then try > to build, I get this thrown at me: thanks --- applied. paul =--------------------- paul fox, pgf at brightstareng.com From obelix0 at yahoo.fr Fri Feb 1 13:01:17 2008 From: obelix0 at yahoo.fr (obelix0) Date: Fri, 01 Feb 2008 22:01:17 +0100 Subject: sysdeps/linux/Config.in:103: syntax error, unexpected T_WORD In-Reply-To: <200802011147.07330.vapier@gentoo.org> References: <169796.90319.qm@web53112.mail.re2.yahoo.com> <200802011147.07330.vapier@gentoo.org> Message-ID: <47A3889D.1010808@yahoo.fr> thanks again for your help ! > then you'll have to debug it. i imagine it's been fixed since. but we wont > know unless you try. the version you're playing with is terribly outdated. > yes I know that I'm using a old version but an other team rebuild this version the last month so I know that is possible and I'm thinking that is possible ! I will search my problem... From max8y at yahoo.com Fri Feb 1 20:29:28 2008 From: max8y at yahoo.com (max y) Date: Fri, 1 Feb 2008 20:29:28 -0800 (PST) Subject: init scripts Message-ID: <452983.97972.qm@web56006.mail.re3.yahoo.com> I have this observation on the linux box, with busybox 1.01. I have this script in my rc.d/rc?.d/S10script with these two lines: mydaemon & myapp & mydaemon is a daemon program, myapp is not a daemon program buy a script periodically running in back ground. I notice this when S10script finishes, mydaemon stays, myapp always receives a EXIT signal, I guess init kills it. My question, is it the expected behavior. Is this behavior changeable by configuration? Thanks, Max --------------------------------- Never miss a thing. Make Yahoo your homepage. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20080201/d12ccb53/attachment.htm From rep.dot.nop at gmail.com Sat Feb 2 04:31:21 2008 From: rep.dot.nop at gmail.com (Bernhard Fischer) Date: Sat, 2 Feb 2008 13:31:21 +0100 Subject: [patch] networking/ping.c In-Reply-To: <15879.1201908354@brightstareng.com> References: <0802012353550.29870@somehost> <15879.1201908354@brightstareng.com> Message-ID: <20080202123121.GB26554@aon.at> On Fri, Feb 01, 2008 at 06:25:54PM -0500, Paul Fox wrote: > > > > Ok. No reaction, yet. Let me try again. > > > > If I disable FEATURE_FANCY_PING (which is enabled by default) and then try > > to build, I get this thrown at me: > >thanks --- applied. Sounds like it was me who broke this in my be-C99-compatible patch :( Sorry for the breakage and thanks for fixing it so fast, pgf! cheers, From rep.dot.nop at gmail.com Sat Feb 2 04:33:56 2008 From: rep.dot.nop at gmail.com (Bernhard Fischer) Date: Sat, 2 Feb 2008 13:33:56 +0100 Subject: [patch] networking/ping.c In-Reply-To: <0801301451300.19715@somehost> References: <0801301451300.19715@somehost> Message-ID: <20080202123356.GC26554@aon.at> On Wed, Jan 30, 2008 at 02:59:32PM +0100, Cristian Ionescu-Idbohrn wrote: >Looks like last checkin with this comment: > >,---- >| r20923 | aldot | 2008-01-29 11:33:34 +0100 (Tue, 29 Jan 2008) | 4 lines >| - be C99 friendly. Anonymous unions are a GNU extension. This change is >| size-neutral WRT -std=gnu99 and fixes several compilation errors for >| strict C99 mode. >`---- > >missed a couple of spots. Compilation error: Please CC me so i have a chance to see them in a vaguely timely manner. TIA, From WHarms at bfs.de Sat Feb 2 07:21:52 2008 From: WHarms at bfs.de (walter harms) Date: Sat, 02 Feb 2008 16:21:52 +0100 Subject: init scripts In-Reply-To: <452983.97972.qm@web56006.mail.re3.yahoo.com> References: <452983.97972.qm@web56006.mail.re3.yahoo.com> Message-ID: <47A48A90.5000202@bfs.de> hi max, i am sorry you have that problem, you are using a very ancient BusyBox Version. There is a good change that things have changed to the better since the last releases. please try a newer release so we can be sure that the problem is not already fixed. re, wh max y wrote: > I have this observation on the linux box, with busybox 1.01. > > I have this script in my rc.d/rc?.d/S10script with these two lines: > mydaemon & > myapp & > > mydaemon is a daemon program, myapp is not a daemon program buy a script periodically running in back ground. > > I notice this when S10script finishes, mydaemon stays, myapp always receives a EXIT signal, I guess init kills it. > > My question, is it the expected behavior. Is this behavior changeable by configuration? > > Thanks, > > Max > > > --------------------------------- > Never miss a thing. Make Yahoo your homepage. > > > ------------------------------------------------------------------------ > > _______________________________________________ > busybox mailing list > busybox at busybox.net > http://busybox.net/cgi-bin/mailman/listinfo/busybox From vda.linux at googlemail.com Sat Feb 2 08:19:04 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 16:19:04 +0000 Subject: ps and username size In-Reply-To: <200801102307.25184.farmatito@tiscali.it> References: <0801052121440.17543@somehost> <0801102228320.8551@somehost> <200801102307.25184.farmatito@tiscali.it> Message-ID: <200802021619.04686.vda.linux@googlemail.com> On Thursday 10 January 2008 22:07, Tito wrote: > On Thursday 10 January 2008 22:40:26 Cristian Ionescu-Idbohrn wrote: > > On Thu, 10 Jan 2008, Tito wrote: > > > > > Isn't there a maximum lenght for usernames on unix/linux? > > > Would it make sense to set the width of this field to that value? > > > > Doing so seems like the clever thing to do, though you'd run into a > > columnisation problem and loose compatibility to full version of the app. > > > > > I ask this because on my system (Ubuntu 7.10 - more or less) > > > adduser fails with usernames longer than 32 chars. > > > > > > Adding user `qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq' ... > > > Adding new group `qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq' (1006) ... > > > groupadd: qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq is not a valid group name > > > adduser: `/usr/sbin/groupadd -g 1006 qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq' returned error code 3. Exiting. > > > > 32 chars seems reasonable, but display real estate seems to be a problem. > > I believe truncated usernames vs. option to display user ids only seems to > > be an acceptable compromise. What do you think? > > > > > > Cheers, > > > > Hi, > of course it is acceptable. > > OTOH it doesn't solve the problem of a possible ambiguity > between username and uid as names composed only of digits > are legal. I think we can right-justify IDs: static void func_user(char *buf, int size, const procps_status_t *ps) { /* procps 2.18 shows numeric UID if name overflows the field */ /* TODO: get_cached_username() returns numeric string if * user has no passwd record, we will display it * left-justified here; too long usernames are shown * as _right-justified_ IDs. Is it worth fixing? */ const char *user = get_cached_username(ps->uid); if (strlen(user) <= size) safe_strncpy(buf, get_cached_username(ps->uid), size+1); else sprintf(buf, "%*u", size, (unsigned)ps->uid); } Output: # ./busybox ps PID USER TIME COMMAND 1 root 0:00 /bin/sh /init 2 root 0:00 [kthreadd] 3 root 0:00 [migration/0] ... 542 root 0:00 [kjournald] 560 root 0:01 udevd 570 root 0:00 [reiserfs/0] 577 1 0:00 rpc.portmap <================ UID with no matching passwd record 630 root 0:00 runsvdir -P /var/service 632 root 0:00 runsv fw 634 root 0:00 runsv gpm 635 root 0:00 gpm -D -2 -m /dev/psaux -t ps2 636 root 0:00 runsv ntp 637 65 0:00 svlogd -tt /var/log/service/ntp <========= Username is too long 638 root 0:00 runsv top 639 user0 0:07 top 640 root 0:00 runsv klog 641 65 0:00 svlogd -tt /var/log/service/klog 642 root 0:00 socklog ucspi But wouldn't it go against bbox's size saving goal to have this feature? Is it really necessary? -- vda From WHarms at bfs.de Sat Feb 2 08:57:59 2008 From: WHarms at bfs.de (walter harms) Date: Sat, 02 Feb 2008 17:57:59 +0100 Subject: ps and username size In-Reply-To: <200802021619.04686.vda.linux@googlemail.com> References: <0801052121440.17543@somehost> <0801102228320.8551@somehost> <200801102307.25184.farmatito@tiscali.it> <200802021619.04686.vda.linux@googlemail.com> Message-ID: <47A4A117.7000105@bfs.de> Denis Vlasenko wrote: > On Thursday 10 January 2008 22:07, Tito wrote: >> On Thursday 10 January 2008 22:40:26 Cristian Ionescu-Idbohrn wrote: >>> On Thu, 10 Jan 2008, Tito wrote: >>> >>>> Isn't there a maximum lenght for usernames on unix/linux? >>>> Would it make sense to set the width of this field to that value? >>> Doing so seems like the clever thing to do, though you'd run into a >>> columnisation problem and loose compatibility to full version of the app. >>> >>>> I ask this because on my system (Ubuntu 7.10 - more or less) >>>> adduser fails with usernames longer than 32 chars. >>>> >>>> Adding user `qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq' ... >>>> Adding new group `qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq' (1006) ... >>>> groupadd: qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq is not a valid group name >>>> adduser: `/usr/sbin/groupadd -g 1006 qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq' returned error code 3. Exiting. >>> 32 chars seems reasonable, but display real estate seems to be a problem. >>> I believe truncated usernames vs. option to display user ids only seems to >>> be an acceptable compromise. What do you think? >>> >>> >>> Cheers, >>> >> Hi, >> of course it is acceptable. >> >> OTOH it doesn't solve the problem of a possible ambiguity >> between username and uid as names composed only of digits >> are legal. > > I think we can right-justify IDs: > > static void func_user(char *buf, int size, const procps_status_t *ps) > { > /* procps 2.18 shows numeric UID if name overflows the field */ > /* TODO: get_cached_username() returns numeric string if > * user has no passwd record, we will display it > * left-justified here; too long usernames are shown > * as _right-justified_ IDs. Is it worth fixing? */ > const char *user = get_cached_username(ps->uid); > if (strlen(user) <= size) > safe_strncpy(buf, get_cached_username(ps->uid), size+1); > else > sprintf(buf, "%*u", size, (unsigned)ps->uid); > } > > Output: > > # ./busybox ps > PID USER TIME COMMAND > 1 root 0:00 /bin/sh /init > 2 root 0:00 [kthreadd] > 3 root 0:00 [migration/0] > ... > 542 root 0:00 [kjournald] > 560 root 0:01 udevd > 570 root 0:00 [reiserfs/0] > 577 1 0:00 rpc.portmap <================ UID with no matching passwd record > 630 root 0:00 runsvdir -P /var/service > 632 root 0:00 runsv fw > 634 root 0:00 runsv gpm > 635 root 0:00 gpm -D -2 -m /dev/psaux -t ps2 > 636 root 0:00 runsv ntp > 637 65 0:00 svlogd -tt /var/log/service/ntp <========= Username is too long > 638 root 0:00 runsv top > 639 user0 0:07 top > 640 root 0:00 runsv klog > 641 65 0:00 svlogd -tt /var/log/service/klog > 642 root 0:00 socklog ucspi > > But wouldn't it go against bbox's size saving goal > to have this feature? Is it really necessary? > -- The real question is: is it useful ? it make automatic parsing hard without need. please add @ before UID (no one should have a @ in its name). re, wh From vda.linux at googlemail.com Sat Feb 2 08:55:05 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 16:55:05 +0000 Subject: Again, german umlauts in ash command line prompt In-Reply-To: <47872281.9090100@lkh-vil.or.at> References: <30057.1199976450@brightstareng.com> <47872281.9090100@lkh-vil.or.at> Message-ID: <200802021655.05970.vda.linux@googlemail.com> On Friday 11 January 2008 08:02, Alexander Griesser wrote: > Paul Fox wrote: > > > Hi! > > > > > > I'm still stuggling with getting the german umlauts (=E4,=F6,=FC, a.s.o) > > > working on my thinclient installation. > > > The really strange thing is, that it doesn't seem to be a keyboard > > > layout problem at all. > > > > if you build busybox without command-line editing enabled, does > > the problem go away? > > Yes, it does. > > > if editing is enabled, i assume you're in emacs (default) mode, > > and not vi editing mode, correct? > > That doesn't matter. I tried with emacs and vi editing mode and the > problem stays the same. > > After having a look at lineedit.c, I found the following code: > > if (!Isprint(c)) /* Skip non-printable characters */ > break; > > That's bad. > isprint() does _NOT_ work correctly, as I already mentioned in my mail > with the subject "Strange problems with FEATURE_VI_8BIT". This code is disabled (ENABLE_FEATURE_NONPRINTABLE_INVERSE_PUT==0), so it cannot be a problem here: #if ENABLE_FEATURE_NONPRINTABLE_INVERSE_PUT /* Display non-printable characters in reverse */ if (!Isprint(c)) { if (c >= 128) c -= 128; if (c < ' ') c += '@'; if (c == 127) c = '?'; printf("\033[7m%c\033[0m", c); } else #endif -- vda From vda.linux at googlemail.com Sat Feb 2 09:02:37 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 17:02:37 +0000 Subject: Again, german umlauts in ash command line prompt In-Reply-To: <4785F513.3040006@lkh-vil.or.at> References: <4785F513.3040006@lkh-vil.or.at> Message-ID: <200802021702.37371.vda.linux@googlemail.com> On Thursday 10 January 2008 10:36, Alexander Griesser wrote: > Hi! > > I'm still stuggling with getting the german umlauts (?,?,?, a.s.o) > working on my thinclient installation. > The really strange thing is, that it doesn't seem to be a keyboard > layout problem at all. > > When I'm at the ash command prompt, I can _NOT_ type ?, ?, ? and what > is really strange, I cannot type the ? character. > > In the following output I tried to enter these characters in the first > line (you can't see them, because they didn't get accepted). > In the second line, I used the `read` builtin to fill a variable with > input and that worked perfectly. > > I can reproduce this every time and on all my systems (even with a > freshly compiled busybox on my desktop system), so I'm sure it has > nothing todo with keyboard layout settings, language settings, etc. > > ~/busybox/busybox-1.9.0 $ ll"!$"$"$ > ~/busybox/busybox-1.9.0 $ read TEST > ???"!?$ > ~/busybox/busybox-1.9.0 $ > > Can anyone reproduce this too? Works for me. Please post your .config Assuming that you are using line editing, this is the plase where "ordinary" chars are inserted into line buffer. Can you add bb_error_msg(...) as indicated by '+'? Does it trigger for umlauts? libbb/lineedit.c ================ default: /* If it's regular input, do the normal thing */ /* Control-V -- force insert of next char */ if (c == CTRL('V')) { if (safe_read(STDIN_FILENO, &c, 1) < 1) goto prepare_to_die; if (c == 0) { beep(); break; } } #if ENABLE_FEATURE_EDITING_VI if (vi_cmdmode) /* Don't self-insert */ break; #endif if (command_len >= (maxsize - 2)) /* Need to leave space for enter */ break; +bb_error_msg("Adding char with code %d", c); command_len++; if (cursor == (command_len - 1)) { /* Append if at the end of the line */ command[cursor] = c; command[cursor+1] = '\0'; cmdedit_set_out_char(' '); } else { /* Insert otherwise */ -- vda From vda.linux at googlemail.com Sat Feb 2 09:05:36 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 17:05:36 +0000 Subject: Again, german umlauts in ash command line prompt In-Reply-To: <3043.1200321031@brightstareng.com> References: <3043.1200321031@brightstareng.com> Message-ID: <200802021705.36792.vda.linux@googlemail.com> On Monday 14 January 2008 14:30, Paul Fox wrote: > alexander wrote: > > > > Thanks. Could you please also have a look at vi.c? It has the same > > problem. I already opened up a topic on this but got no reply so far... > > sure. give me a day or two. This is not a simple problem. The short-term fix is to allow all chars with codes >= 32. However, in UTF-8 non-ASCII chars (German umlauts etc) are actually multi-byte sequences, and they cannot be checked for validity by looking at single character's code. for now, ENABLE_FEATURE_VI_8BIT in vi allows any chars with codes >= 32 (except for 0x9b which is a control char for VT-100 terminals (STUPID!!!)). Umlauts should work in vi, if they are single chars, not UTF-8 sequences. -- vda From vda.linux at googlemail.com Sat Feb 2 09:11:36 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 17:11:36 +0000 Subject: -sh: can't access tty; job control turned off - busybox v1.6.0 In-Reply-To: <8B3BF7A02B910640AB146A919AB36594053B2B28@exsvl03.hq.netapp.com> References: <8B3BF7A02B910640AB146A919AB36594051849B7@exsvl03.hq.netapp.com> <200801272353.58163.vda.linux@googlemail.com> <8B3BF7A02B910640AB146A919AB36594053B2B28@exsvl03.hq.netapp.com> Message-ID: <200802021711.36433.vda.linux@googlemail.com> On Tuesday 29 January 2008 21:49, Tallam, Sreenivas wrote: > Hi vda, > > Thanks for the reply. > But unfortunately that does not work for me. > > Since my /bin dir does not have setsid or cttyhack utilities in it. > > # cd /bin > # ls > addgroup deluser ln ping sync > adduser df login ping6 tar > ash dmesg ls ps tempfile > busybox dnsdomainname mkdir pwd touch > cat echo mknod readlink true > chgrp false mktemp rm umount > chmod grep more rmdir uname > chown gunzip mount run-parts usleep > chroot gzip mt sed vi > cp hostname mv sh watch > date ip netstat sleep zcat > dd ipcalc nice stty > delgroup kill pidof su > > Any other clues? If you build busybox yourself, just enable them in .config -- vda From vda.linux at googlemail.com Sat Feb 2 09:22:04 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 17:22:04 +0000 Subject: Strange problems with FEATURE_VI_8BIT In-Reply-To: <31866.1200329833@brightstareng.com> References: <31866.1200329833@brightstareng.com> Message-ID: <200802021722.04869.vda.linux@googlemail.com> On Monday 14 January 2008 16:57, Paul Fox wrote: > i'm just re-reading this message, which i didn't pay attention to before. > > > I tried to use FEATURE_VI_8BIT in busybox 1.9.0 bus was unsuccessful so > > far. Even though this feature is enabled in my configuration, I can't > > enter german umlauts into vi. > > ... > > int main(int argc, char **argv) > > { > > unsigned int x; > > while(1) { > > x = getc(stdin); > > if(isprint(x)) > > { > > printf("%c is printable\n", x); > > } else { > > printf("%c is not printable\n", x); > > } > > } > > return 0; > > } > > - ----------------------------- 8< ------------------------ > > > > Needless to say, it always prints out the "is not printable" text > > for all umlauts I enter. > > > > Am I doing something wrong or is this a bug? > > is your locale set correctly? if busybox is built to honor your > locale, then i'm surprised that the umlaut isn't "printable". > > (in fact, this makes me wonder if my fix to lineedit.c was correct.) Alexander, with ENABLE_LOCALE_SUPPORT off and ENABLE_FEATURE_VI_8BIT on, vi shall accept everything above 31 which is not x7f and not 0x9b: #if ENABLE_LOCALE_SUPPORT #if ENABLE_FEATURE_VI_8BIT #define Isprint(c) isprint(c) #else #define Isprint(c) (isprint(c) && (unsigned char)(c) < 0x7f) #endif #else /* 0x9b is Meta-ESC */ #if ENABLE_FEATURE_VI_8BIT #define Isprint(c) ((unsigned char)(c) >= ' ' && (c) != 0x7f && (unsigned char)(c) != 0x9b) #else #define Isprint(c) ((unsigned char)(c) >= ' ' && (unsigned char)(c) < 0x7f) #endif #endif Can you test that this combination works? If yes, then it seems in your locale setup isprint() thinks that umlauts are not printable chars. P.S. Wonders of vi.c... what is this "if (1 <= (unsigned char)c || ...)" check for? "If char is Ctrl-A or NUL" - ?? static void do_cmd(char c) { ... if (cmd_mode == 2) { ... if (*dot == '\n') {... } else { if (1 <= (unsigned char)c || Isprint(c)) { if (c != 27) dot = yank_delete(dot, dot, 0, YANKDEL); // delete char dot = char_insert(dot, c); // insert new char } goto dc1; } } if (cmd_mode == 1) { // hitting "Insert" twice means "R" replace mode if (c == VI_K_INSERT) goto dc5; // insert the char c at "dot" if (1 <= (unsigned char)c || Isprint(c)) { dot = char_insert(dot, c); } goto dc1; } ... -- vda From vda.linux at googlemail.com Sat Feb 2 09:53:50 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 17:53:50 +0000 Subject: New applet: sendmail In-Reply-To: <6784529b0801290139w7f38719eob98e222019b45b62@mail.gmail.com> References: <6784529b0801080449u5d51dd83y5176df1ff0302ed0@mail.gmail.com> <20080129091017.GA23918@aon.at> <6784529b0801290139w7f38719eob98e222019b45b62@mail.gmail.com> Message-ID: <200802021753.50885.vda.linux@googlemail.com> On Tuesday 29 January 2008 09:39, Vladimir Dronnikov wrote: > Attached is the patch against current svn. > > It now sanitizes possible malicious user input. > And works with Lotus Notes which requires \r\n EOLs. - if (pipes[i] > STDOUT_FILENO) + if (pipes[i] > STDERR_FILENO) // let us not touch stderr Why? if pipes[i] == 2 (stderr), then stderr fd was closed when sendmail was started. Weird, but possible. And then pipe() used fd 2 for one of pipe ends (ther is no other way it could end up equal to 2). Why you don't want to close it? + const char *charset = NULL; + const char *opt_user = NULL; + const char *opt_pass = NULL; None of these NULLs seem to be needed. static char *sane(const char *str) If you are going to modify *str, don't declare it as const. Applied with modifications. Thanks. vda From vda.linux at googlemail.com Sat Feb 2 10:04:06 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 18:04:06 +0000 Subject: dhcp options 121,63 In-Reply-To: <200801291643.48466.nmav@gennetsa.com> References: <200801291643.48466.nmav@gennetsa.com> Message-ID: <200802021804.06046.vda.linux@googlemail.com> On Tuesday 29 January 2008 14:43, Nikos Mavrogiannopoulos wrote: > I've submitted a patch in http://bugs.busybox.net/view.php?id=1999 to support > the DHCP options 121, 63. The static routes option exports a variable > $sroutes that contains NETWORK1 NETMASK1 GATEWAY1 NETWORK2 NETMASK2 GATEWAY2 > etc. The vendorinfo option is quite intrusive and allows to export vendorinfo > suboptions via the dhcp_sub_options structure. Needs to be rediffed against 1.9.0. There were many changes in DHCP applets in 1.9.0. Also: +static uint8_t* mask_to_ip(uint8_t * ip, uint8_t mask) +{ +int i; +uint32_t ret = 0; Broken indentation. +inline +static void extract_route_octets( uint8_t *ret_ip, uint8_t* p, int mask, int *adv) +{ +*adv = 0; It's too big for inline. + case OPTION_STATIC_ROUTES: { + /* we return the static routes in a string containing a list + * of NETWORK1 NETMASK1 GATEWAY1 NETWORK2 NETMASK2 GATEWAY2 ... */ + int left = len; + int mask; + int adv; + uint8_t *p = option; + uint8_t ip[4]; + + *dest = 0; + + do { + mask = *p; Please indent with tabs, not spaces. -- vda From dronnikov at gmail.com Sat Feb 2 10:48:33 2008 From: dronnikov at gmail.com (Vladimir Dronnikov) Date: Sat, 2 Feb 2008 18:48:33 +0000 Subject: New applet: sendmail In-Reply-To: <200802021753.50885.vda.linux@googlemail.com> References: <6784529b0801080449u5d51dd83y5176df1ff0302ed0@mail.gmail.com> <20080129091017.GA23918@aon.at> <6784529b0801290139w7f38719eob98e222019b45b62@mail.gmail.com> <200802021753.50885.vda.linux@googlemail.com> Message-ID: <6784529b0802021048j292fc913labc58122e30bcfd1@mail.gmail.com> Hello! I'm now developing in parallel to sendmail a simple fetchmail (or, better to say, getmail) applet. It's aimed to just dump the content of remote mailbox to local Maildir. Since it shares much code with sendmail (signal handling, openssl helper IPC, and so on) I would like to ask the list some questions. Will it be relevant to busybox? If so, should I just combine both applets as, e.g., swaponoff in one file or just make shared code non-static? If let them be combined, what is the best way to process options which are common for both applets (username, password, server, port, ...)? Is there a way to use getopt32 twice: one time for common options and second time for particular applet? Plz, do answer. -- Vladimir From vda.linux at googlemail.com Sat Feb 2 10:49:36 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 18:49:36 +0000 Subject: msh + cmdline editing is broken In-Reply-To: <200802011719.54233.vapier@gentoo.org> References: <200802011719.54233.vapier@gentoo.org> Message-ID: <200802021849.36142.vda.linux@googlemail.com> On Friday 01 February 2008 22:19, Mike Frysinger wrote: > this was working in busybox-1.4.1, but broke between that and > busybox-1.9.0 ... the quick test is to do `make allnoconfig` and then turn on > just msh and command line editing. then when you run msh, do: > $ ls > $ ls > lsls: command not found > (so you type "ls", hit CTRL+C, then type "ls" again followed by return) > > also, if you send just EOF to kill the shell (ctrl+d), you get a new prompt > instead of exiting ... > > perhaps someone more familiar with the new common command line editing can > track down the issue quickly ... otherwise i'll be banging on it next week > -mike Fixed in svn, will be in 1.9.1 too. -- vda From vda.linux at googlemail.com Sat Feb 2 10:58:36 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 18:58:36 +0000 Subject: [PATCH] fsck -A goes into infinite loop and kills all processes In-Reply-To: <1201866371.5420.3.camel@uberlaptop.marples.name> References: <25800.1201801922@brightstareng.com> <1201811567.3887.1.camel@uberlaptop.marples.name> <1201866371.5420.3.camel@uberlaptop.marples.name> Message-ID: <200802021858.36301.vda.linux@googlemail.com> On Friday 01 February 2008 11:46, Roy Marples wrote: > > On Thu, 2008-01-31 at 20:32 +0000, Roy Marples wrote: > > On Thu, 2008-01-31 at 18:17 +0000, Roy Marples wrote: > > > Ah yes, it's because there is no helper installed for ext4dev. Ensuring > > > that all helpers exist fixes the error. So it's not handling exec errors > > > correctly. I'll see if I can fix fsck now. > > > > The execute function does not return when pid is <1, so it stores -1 as > > a pid to kill, which kills quite a bit really :) > > Attached is a new patch that free's any malloced memory correctly. BTW, > this behaviour should match upstream as if the don't find a helper then > they free the instance and return even if noexecute is set. As the spawn > function does that as well, we just need to check if pid is less than 1. Applied, thanks. -- vda From vda.linux at googlemail.com Sat Feb 2 11:03:01 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sat, 2 Feb 2008 19:03:01 +0000 Subject: [PATCH] Getty: Don't do auto parity in local mode(-L). In-Reply-To: <1201775638-22055-1-git-send-email-Joakim.Tjernlund@transmode.se> References: <1201775638-22055-1-git-send-email-Joakim.Tjernlund@transmode.se> Message-ID: <200802021903.01965.vda.linux@googlemail.com> On Thursday 31 January 2008 10:33, Joakim Tjernlund wrote: > 8 bit chars trigges the auto parity function which > makes the serial port unreadable. > --- > See http://busybox.net/lists/busybox/2008-January/029855.html > for some more info. > > loginutils/getty.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/loginutils/getty.c b/loginutils/getty.c > index 31230c9..9c1a336 100644 > --- a/loginutils/getty.c > +++ b/loginutils/getty.c > @@ -435,7 +435,7 @@ static char *get_logname(char *logname, unsigned size_logname, > > /* Do parity bit handling. */ > ascval = c & 0177; > - if (c != ascval) { /* "parity" bit on ? */ > + if (!(op->flags & F_LOCAL) && (c != ascval)) { /* "parity" bit on ? */ > bits = 1; > mask = 1; > while (mask & 0177) { Applied, thanks. -- vda From farmatito at tiscali.it Sat Feb 2 11:40:52 2008 From: farmatito at tiscali.it (Tito) Date: Sat, 2 Feb 2008 20:40:52 +0100 Subject: New applet: sendmail In-Reply-To: <6784529b0802021048j292fc913labc58122e30bcfd1@mail.gmail.com> References: <6784529b0801080449u5d51dd83y5176df1ff0302ed0@mail.gmail.com> <200802021753.50885.vda.linux@googlemail.com> <6784529b0802021048j292fc913labc58122e30bcfd1@mail.gmail.com> Message-ID: <200802022040.53271.farmatito@tiscali.it> On Saturday 02 February 2008 19:48:33 you wrote: > Hello! > > I'm now developing in parallel to sendmail a simple fetchmail (or, > better to say, getmail) applet. It's aimed to just dump the content of > remote mailbox to local Maildir. > Since it shares much code with sendmail (signal handling, openssl > helper IPC, and so on) I would like to ask the list some questions. > > Will it be relevant to busybox? > > If so, should I just combine both applets as, e.g., swaponoff in one > file or just make shared code non-static? > > If let them be combined, what is the best way to process options which > are common for both applets (username, password, server, port, ...)? > Is there a way to use getopt32 twice: one time for common options and > second time for particular applet? Hi, maybe check the applet_name at startup and then if (applet_name[0] == 'f') getopt32(.............................); else getopt32(.............................); Ciao, Tito > Plz, do answer. > > -- > Vladimir > _______________________________________________ > busybox mailing list > busybox at busybox.net > http://busybox.net/cgi-bin/mailman/listinfo/busybox > From farmatito at tiscali.it Sat Feb 2 12:37:48 2008 From: farmatito at tiscali.it (Tito) Date: Sat, 2 Feb 2008 21:37:48 +0100 Subject: New applet: sendmail In-Reply-To: <6784529b0802021206o549ebf7ev2d1fb36d9bd78022@mail.gmail.com> References: <6784529b0801080449u5d51dd83y5176df1ff0302ed0@mail.gmail.com> <200802022040.53271.farmatito@tiscali.it> <6784529b0802021206o549ebf7ev2d1fb36d9bd78022@mail.gmail.com> Message-ID: <200802022137.48310.farmatito@tiscali.it> On Saturday 02 February 2008 21:06:52 Vladimir Dronnikov wrote: > > > > Hi, > > maybe check the applet_name at startup and then > > > > if (applet_name[0] == 'f') > > getopt32(.............................); > > else > > getopt32(.............................); > > > __________________ > Sure! But I meant the following: > unsigned opts = getopt32(argv, common_options); > ... > if ( ) opts = getopt32(argv, sendmail_specific_options); > else opts = getopt32(argv, fetchmail_specific_options); I suspect this will cause evil results, i think it is better to isolate the option parsing between fetchmail and sendmail. Maybe it is possible to use a single getopt32 call tough.... char *opt_string; if (sendmail) { opt_complementary = "f:t::b::a::"; opt_string = "f:t:n::s:b:a:c:" USE_FEATURE_SENDMAIL_NETWORK("dw:h:p:U:P:"); } else { opt_complementary = "whatever"; opt_string = "aqwerty"; } opts = getopt32(argv, opt_string, &from, &recipients, ¬ify, &subject, &bodies, &attachments, &charset USE_FEATURE_SENDMAIL_NETWORK(, &wsecs, &server, &port, &opt_user, &opt_pass) ); but only if there are similar options that take arguments. IMHO the best solution is to use two independent getopt32 calls. Ciao, Tito > You see, if we launch, say, sendmail then the first call to getopt32 > would fail [showing bb_usage()] on any fetchmail_specific_options and > even on sendmail_specific_options, since it is not aware of these > specific options! > > So is there a way to tell getopt32 to not fail on unknown options? > > Thank you for reply > > -- > Vladimir > From farmatito at tiscali.it Sat Feb 2 13:01:43 2008 From: farmatito at tiscali.it (Tito) Date: Sat, 2 Feb 2008 22:01:43 +0100 Subject: New applet: sendmail In-Reply-To: <6784529b0802021253w6f4dde2ep481027c579479fde@mail.gmail.com> References: <6784529b0801080449u5d51dd83y5176df1ff0302ed0@mail.gmail.com> <200802022137.48310.farmatito@tiscali.it> <6784529b0802021253w6f4dde2ep481027c579479fde@mail.gmail.com> Message-ID: <200802022201.43635.farmatito@tiscali.it> On Saturday 02 February 2008 21:53:12 Vladimir Dronnikov wrote: > I see. In fact all the options which depend on *_NETWORK are shared... In this case maybe it is possible to use one call if you invert the order of options if (sendmail) { opt_complementary = "f:t::b::a::"; opt_string = USE_FEATURE_SENDMAIL_NETWORK("dw:h:p:U:P:")"f:t:n::s:b:a:c:"; } else { opt_complementary = ""; opt_string = USE_FEATURE_SENDMAIL_NETWORK("dw:h:p:U:P:")"xyz"; } opts = getopt32(argv, opt_string, USE_FEATURE_SENDMAIL_NETWORK(, &wsecs, &server, &port, &opt_user, &opt_pass) &from, &recipients, ¬ify, &subject, &bodies, &attachments, &charset); I presume it will not be a problem if there are more &xxx args than "xyz" options as they will be unused. Can't say if it is worth the effort tough. :-) Ciao, Tito > So let it be 2 calls. > > Thanx for discussion. > > -- > Vladimir > > 2008/2/2, Tito : > > On Saturday 02 February 2008 21:06:52 Vladimir Dronnikov wrote: > > > > > > > > Hi, > > > > maybe check the applet_name at startup and then > > > > > > > > if (applet_name[0] == 'f') > > > > getopt32(.............................); > > > > else > > > > getopt32(.............................); > > > > > > > __________________ > > > Sure! But I meant the following: > > > unsigned opts = getopt32(argv, common_options); > > > ... > > > if ( ) opts = getopt32(argv, sendmail_specific_options); > > > else opts = getopt32(argv, fetchmail_specific_options); > > > > I suspect this will cause evil results, i think it is better to isolate > > the option parsing between fetchmail and sendmail. > > Maybe it is possible to use a single getopt32 call tough.... > > char *opt_string; > > > > if (sendmail) { > > opt_complementary = "f:t::b::a::"; > > opt_string = "f:t:n::s:b:a:c:" > > USE_FEATURE_SENDMAIL_NETWORK("dw:h:p:U:P:"); > > } else { > > opt_complementary = "whatever"; > > opt_string = "aqwerty"; > > } > > > > opts = getopt32(argv, > > opt_string, > > &from, &recipients, ¬ify, &subject, &bodies, &attachments, &charset > > USE_FEATURE_SENDMAIL_NETWORK(, &wsecs, &server, &port, &opt_user, > > &opt_pass) > > ); > > > > but only if there are similar options that take arguments. > > IMHO the best solution is to use two independent getopt32 calls. > > > > Ciao, > > Tito > > > > > You see, if we launch, say, sendmail then the first call to getopt32 > > > would fail [showing bb_usage()] on any fetchmail_specific_options and > > > even on sendmail_specific_options, since it is not aware of these > > > specific options! > > > > > > So is there a way to tell getopt32 to not fail on unknown options? > > > > > > Thank you for reply > > > > > > -- > > > Vladimir > > > > > > > > > > From rep.dot.nop at gmail.com Sat Feb 2 16:40:24 2008 From: rep.dot.nop at gmail.com (Bernhard Fischer) Date: Sun, 3 Feb 2008 01:40:24 +0100 Subject: svn commit: trunk/busybox/e2fsprogs In-Reply-To: <20080202185458.05FFA120157@busybox.net> References: <20080202185458.05FFA120157@busybox.net> Message-ID: <20080203004023.GD26554@aon.at> On Sat, Feb 02, 2008 at 10:54:58AM -0800, vda at busybox.net wrote: >Author: vda >Date: 2008-02-02 10:54:58 -0800 (Sat, 02 Feb 2008) >New Revision: 20934 > >Log: >fsck: don't kill pid -1! (Roy Marples ) > > > >Modified: > trunk/busybox/e2fsprogs/fsck.c > > >Changeset: >Modified: trunk/busybox/e2fsprogs/fsck.c >=================================================================== >--- trunk/busybox/e2fsprogs/fsck.c 2008-02-02 18:50:50 UTC (rev 20933) >+++ trunk/busybox/e2fsprogs/fsck.c 2008-02-02 18:54:58 UTC (rev 20934) >@@ -663,6 +663,12 @@ > for (i = num_args+1; i < argc; i++) > free(argv[i]); > >+ /* No pid, so don't record an instance */ >+ if (pid < 0) { >+ free(inst); I didn't look at the context, but can it be if (ENABLE_FEATURE_CLEAN_UP) free() ? From max8y at yahoo.com Sat Feb 2 17:52:41 2008 From: max8y at yahoo.com (max y) Date: Sat, 2 Feb 2008 17:52:41 -0800 (PST) Subject: init scripts In-Reply-To: <47A48A90.5000202@bfs.de> Message-ID: <711278.94056.qm@web56013.mail.re3.yahoo.com> Hi Walter, Thanks for the reply. Are you saying that it's a known problem in version 1.01? As my bussbox comes with Monta Vista Linux, I am not sure if it's a modified version. Max walter harms wrote: hi max, i am sorry you have that problem, you are using a very ancient BusyBox Version. There is a good change that things have changed to the better since the last releases. please try a newer release so we can be sure that the problem is not already fixed. re, wh max y wrote: > I have this observation on the linux box, with busybox 1.01. > > I have this script in my rc.d/rc?.d/S10script with these two lines: > mydaemon & > myapp & > > mydaemon is a daemon program, myapp is not a daemon program buy a script periodically running in back ground. > > I notice this when S10script finishes, mydaemon stays, myapp always receives a EXIT signal, I guess init kills it. > > My question, is it the expected behavior. Is this behavior changeable by configuration? > > Thanks, > > Max > > > --------------------------------- > Never miss a thing. Make Yahoo your homepage. > > > ------------------------------------------------------------------------ > > _______________________________________________ > busybox mailing list > busybox at busybox.net > http://busybox.net/cgi-bin/mailman/listinfo/busybox --------------------------------- Looking for last minute shopping deals? Find them fast with Yahoo! Search. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20080202/3149f307/attachment.htm From cristian.ionescu-idbohrn at axis.com Sun Feb 3 03:36:29 2008 From: cristian.ionescu-idbohrn at axis.com (Cristian Ionescu-Idbohrn) Date: Sun, 3 Feb 2008 12:36:29 +0100 (CET) Subject: procps/ps.c, svn r20930 Message-ID: <0802031223360.29870@somehost> Would this adjustment be appropriate? No point in calling get_cached_username twice? Index: procps/ps.c =================================================================== --- procps/ps.c (revision 20936) +++ procps/ps.c (working copy) @@ -4,7 +4,7 @@ * * Copyright (C) 1999-2004 by Erik Andersen * Fix for SELinux Support:(c)2007 Hiroshi Shinji - (c)2007 Yuichi Nakamura + * (c)2007 Yuichi Nakamura * * Licensed under the GPL version 2, see the file LICENSE in this tarball. */ @@ -168,7 +168,7 @@ * as _right-justified_ IDs. Is it worth fixing? */ const char *user = get_cached_username(ps->uid); if (strlen(user) <= size) - safe_strncpy(buf, get_cached_username(ps->uid), size+1); + safe_strncpy(buf, user, size+1); else sprintf(buf, "%*u", size, (unsigned)ps->uid); #endif I do understand this is work in progress, but currently, even if this new code in function func_user were enabled, it doesn't look like it would produce the aimed results, as the ps-lines are still produced somewhere around line 555. Cheers, -- Cristian From kalyanatejaswi at yahoo.co.in Sun Feb 3 05:17:08 2008 From: kalyanatejaswi at yahoo.co.in (kalyan) Date: Sun, 3 Feb 2008 13:17:08 +0000 (GMT) Subject: %builtin + PATH Message-ID: <357698.67013.qm@web8601.mail.in.yahoo.com> Hi list, How do I make busybox shell to search for builtin commands after some point in my PATH by specifying %builtin? I am using BB-1.2.1 and "ash" shell. As an example, i have tried the builtin "kill" command to override normal "kill" command and didnt succeed. I have attached the log. Thanks in advance for your pointers. Regards Kalyan Forgot the famous last words? Access your message archive online at http://in.messenger.yahoo.com/webmessengerpromo.php -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: kill.txt Url: http://busybox.net/lists/busybox/attachments/20080203/9ec8c053/attachment.txt From WHarms at bfs.de Sun Feb 3 05:23:13 2008 From: WHarms at bfs.de (walter harms) Date: Sun, 03 Feb 2008 14:23:13 +0100 Subject: init scripts In-Reply-To: <711278.94056.qm@web56013.mail.re3.yahoo.com> References: <711278.94056.qm@web56013.mail.re3.yahoo.com> Message-ID: <47A5C041.3060308@bfs.de> hi max, you misunderstood me. I said, please try a newer release *most likely* the problems are fixed already *IF* its a busybox problem. re, wh max y wrote: > Hi Walter, > > Thanks for the reply. > > Are you saying that it's a known problem in version 1.01? As my bussbox comes with Monta Vista Linux, I am not sure if it's a modified version. > > Max > > walter harms wrote: > hi max, > i am sorry you have that problem, you are using a very ancient BusyBox Version. There is a good change that > things have changed to the better since the last releases. please try a newer release > so we can be sure that the problem is not already fixed. > > re, > wh > > > max y wrote: >> I have this observation on the linux box, with busybox 1.01. >> >> I have this script in my rc.d/rc?.d/S10script with these two lines: >> mydaemon & >> myapp & >> >> mydaemon is a daemon program, myapp is not a daemon program buy a script periodically running in back ground. >> >> I notice this when S10script finishes, mydaemon stays, myapp always receives a EXIT signal, I guess init kills it. >> >> My question, is it the expected behavior. Is this behavior changeable by configuration? >> >> Thanks, >> >> Max >> >> >> --------------------------------- >> Never miss a thing. Make Yahoo your homepage. >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> busybox mailing list >> busybox at busybox.net >> http://busybox.net/cgi-bin/mailman/listinfo/busybox > > > > --------------------------------- > Looking for last minute shopping deals? Find them fast with Yahoo! Search. From lists at zelow.no Sun Feb 3 07:37:10 2008 From: lists at zelow.no (Thomas Lundquist) Date: Sun, 3 Feb 2008 16:37:10 +0100 Subject: od -t Message-ID: <20080203153710.GA24672@zelow.no> Hi. I'm trying to build busybox within buildroot and then busybox provides od but applets/usage_compressed uses od -t which busybox does not have. Turning off CONFIG_FEATURE_COMPRESS_USAGE does not help either. Anyone with plan? I guess we should/could either try to add -t or fix the applets/usage_compressed or applets/usage to not use it. I'd be happy if it was possible to compress since it shuld save some space. Thomas. From Alexander at Kriegisch.name Sun Feb 3 09:19:03 2008 From: Alexander at Kriegisch.name (Alexander Kriegisch) Date: Sun, 03 Feb 2008 18:19:03 +0100 Subject: Tool to URL-encode text data Message-ID: <47A5F787.6000005@Kriegisch.name> We all know that httpd can URL-decode strings, but there is no counterpart to do the opposite, i.e. URL-encode strings, in BusyBox. Do you think it would be useful to have such a little tool, maybe even as an optional (non-standard) httpd feature? I know that URL encoding can be done via sed, e.g. like so (taken from the tool "Callmonitor" by Andreas B?hmann): urlencode() { _urlencode '%\1' "$@" } _urlencode() { local replacement=$1; shift local txt=$* case $txt in *[!0-9A-Z_a-z!*.-]*) ;; *) echo -n "$txt"; return ;; esac echo -e $(echo -n "$txt" | hexdump -v -e '/1 "!%02x"' | sed ' s/!\(2[1ade]\|3[0-9]\|4[1-9a-f]\|5[0-9af]\|6[1-9a-f]\|7[0-9a]\)/\\x\1/g s/!\([[:xdigit:]]\{2\}\)/'"$replacement"'/g ') } Denis, what do you think? Is there any chance of getting a C-coded little binary doing URL-encoding? BB's wget does not do it either, unfortunately. -- Alexander Kriegisch From WHarms at bfs.de Sun Feb 3 10:04:10 2008 From: WHarms at bfs.de (walter harms) Date: Sun, 03 Feb 2008 19:04:10 +0100 Subject: od -t In-Reply-To: <20080203153710.GA24672@zelow.no> References: <20080203153710.GA24672@zelow.no> Message-ID: <47A6021A.5070206@bfs.de> please try ENABLE_DESKTOP od.c says: #if ENABLE_DESKTOP /* This one provides -t (busybox's own build script needs it) */ please report results, i guess this should be added to the documentations. re, wh Thomas Lundquist wrote: > Hi. > > I'm trying to build busybox within buildroot and then busybox provides > od but applets/usage_compressed uses od -t which busybox does not have. > > Turning off CONFIG_FEATURE_COMPRESS_USAGE does not help either. > > Anyone with plan? I guess we should/could either try to add -t or fix > the applets/usage_compressed or applets/usage to not use it. > > I'd be happy if it was possible to compress since it shuld save some > space. > > > Thomas. > _______________________________________________ > busybox mailing list > busybox at busybox.net > http://busybox.net/cgi-bin/mailman/listinfo/busybox > > > From rep.dot.nop at gmail.com Sun Feb 3 10:26:28 2008 From: rep.dot.nop at gmail.com (Bernhard Fischer) Date: Sun, 3 Feb 2008 19:26:28 +0100 Subject: od -t In-Reply-To: <20080203153710.GA24672@zelow.no> References: <20080203153710.GA24672@zelow.no> Message-ID: <20080203182628.GE26554@aon.at> On Sun, Feb 03, 2008 at 04:37:10PM +0100, Thomas Lundquist wrote: >Hi. > >I'm trying to build busybox within buildroot and then busybox provides >od but applets/usage_compressed uses od -t which busybox does not have. > >Turning off CONFIG_FEATURE_COMPRESS_USAGE does not help either. > >Anyone with plan? I guess we should/could either try to add -t or fix We should fix the usage_compressed scripts, yes. Perhaps you want to experiment with just using "-x", something like echo 'static const char packed_usage[] ALIGN1 = ' | bzip2 -1 \ | ./busybox od -v -x \ | sed -e 's/^[^ ]*//' \ -e 's/ *\(..\)\(..\)/\\x\2\\x\1/g' \ -e 's/\\x[ ][ ]*\\x[ ]*$//' \ -e 's/^\(.*\)$/"\1"/' where the brackets contain a space and ^vi (i.e. a tab). Perhaps the above even works, i admit that i didn't try it out. From dronnikov at gmail.com Sun Feb 3 02:10:39 2008 From: dronnikov at gmail.com (Vladimir Dronnikov) Date: Sun, 3 Feb 2008 13:10:39 +0300 Subject: Some patches Message-ID: <6784529b0802030210mfbb3231w74585f6e461bfe9e@mail.gmail.com> Hello! I've prepared a set of patches. 1. mkswap: remove unnecessary rewind when getting length of swap device 2. mount: support mount helpers. E.g. mount -t ntfs-3g /dev/hda1 /mnt would first try to exec ntfs-3g binary and if it fails then try to issue mount(2). 3. new xmklock(char *lock_file_name) function. It dies if lock_file_name file already exists. Otherwise it creates that file and securely deletes it on exit. This function is then used by 2 BB applets: microcom and [send|fetch]mail. 4. microcom: now it properly works on piped stdin. Denys, please consider applying 5. sendmail: converted to sendmail+fetchmail. The latter simply pulls remote mailbox content into local Maildir. Fetchmail is being actively developed so any comments are welcome! Plz, take a look and make some feedback -- Vladimir -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20080203/0f100b15/attachment-0001.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: mkswap.patch Type: application/octet-stream Size: 507 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080203/0f100b15/attachment-0005.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: mount.patch Type: application/octet-stream Size: 870 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080203/0f100b15/attachment-0006.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: mklock.patch Type: application/octet-stream Size: 1150 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080203/0f100b15/attachment-0007.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: microcom.patch Type: application/octet-stream Size: 6679 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080203/0f100b15/attachment-0008.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: sendmail.patch Type: application/octet-stream Size: 22186 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080203/0f100b15/attachment-0009.obj From vda.linux at googlemail.com Sun Feb 3 13:54:15 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sun, 3 Feb 2008 21:54:15 +0000 Subject: %builtin + PATH In-Reply-To: <357698.67013.qm@web8601.mail.in.yahoo.com> References: <357698.67013.qm@web8601.mail.in.yahoo.com> Message-ID: <200802032154.15512.vda.linux@googlemail.com> On Sunday 03 February 2008 13:17, kalyan wrote: > Hi list, > How do I make busybox shell to search for builtin > commands after some point in my PATH by specifying > %builtin? I am using BB-1.2.1 and "ash" shell. > > As an example, i have tried the builtin "kill" command > to override normal "kill" command and didnt succeed. I > have attached the log. kill is a "regular" builtin and those always take precedence over commands. Exampe of "non-regular" builtin (NB: ash is instrumented to give debug printouts): # ./busybox ash /.1/usr/srcdevel/bbox/fix/busybox.t8 # let <======== builtin ash: builtin found ash: builtinloc <= 0 ash: let: expression expected /.1/usr/srcdevel/bbox/fix/busybox.t8 # PATH=/bin:%builtin /.1/usr/srcdevel/bbox/fix/busybox.t8 # let <========= /bin/let I am /bin/let /.1/usr/srcdevel/bbox/fix/busybox.t8 # I don't know why ash has this distinction. -- vda From vda.linux at googlemail.com Sun Feb 3 14:02:31 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sun, 3 Feb 2008 22:02:31 +0000 Subject: procps/ps.c, svn r20930 In-Reply-To: <0802031223360.29870@somehost> References: <0802031223360.29870@somehost> Message-ID: <200802032202.31961.vda.linux@googlemail.com> On Sunday 03 February 2008 11:36, Cristian Ionescu-Idbohrn wrote: > Would this adjustment be appropriate? > No point in calling get_cached_username twice? Yes. Fixed. Thanks. > I do understand this is work in progress, but currently, even if this new > code in function func_user were enabled, it doesn't look like it would > produce the aimed results, as the ps-lines are still produced somewhere > around line 555. thats "#else /* !ENABLE_DESKTOP */" part, which needs not be so compatible with "standard" ps. -- vda From vda.linux at googlemail.com Sun Feb 3 14:34:26 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sun, 3 Feb 2008 22:34:26 +0000 Subject: getting ash to read /etc/profile In-Reply-To: <4dc28b160801311054me1e61cfs5be93ccc00efcd17@mail.gmail.com> References: <4dc28b160801311054me1e61cfs5be93ccc00efcd17@mail.gmail.com> Message-ID: <200802032234.26118.vda.linux@googlemail.com> On Thursday 31 January 2008 18:54, Joe Halpin wrote: > I'm trying to get ash to read /etc/profile by setting PROFILE to 1 in > ash.c. When I do this I get compile errors about monitor() not being > declared, and indeed I can't find it in the distro. How do I fix this? PROFILE seems to be profiling code, has nothing to do with /etc/profile. Working method: # ./busybox ash --login <*> Executing /etc/profile from 'ash'. Command line: '' ... -- vda From vda.linux at googlemail.com Sun Feb 3 15:30:01 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sun, 3 Feb 2008 23:30:01 +0000 Subject: Tool to URL-encode text data In-Reply-To: <47A5F787.6000005@Kriegisch.name> References: <47A5F787.6000005@Kriegisch.name> Message-ID: <200802032330.01369.vda.linux@googlemail.com> On Sunday 03 February 2008 17:19, Alexander Kriegisch wrote: > We all know that httpd can URL-decode strings, but there is no > counterpart to do the opposite, i.e. URL-encode strings, in BusyBox. Do > you think it would be useful to have such a little tool, maybe even as > an optional (non-standard) httpd feature? > > I know that URL encoding can be done via sed, e.g. like so (taken from > the tool "Callmonitor" by Andreas B?hmann): > > urlencode() { > _urlencode '%\1' "$@" > } > > _urlencode() { > local replacement=$1; shift > local txt=$* > case $txt in > *[!0-9A-Z_a-z!*.-]*) ;; > *) echo -n "$txt"; return ;; > esac > echo -e $(echo -n "$txt" | > hexdump -v -e '/1 "!%02x"' | > sed ' > s/!\(2[1ade]\|3[0-9]\|4[1-9a-f]\|5[0-9af]\|6[1-9a-f]\|7[0-9a]\)/\\x\1/g > s/!\([[:xdigit:]]\{2\}\)/'"$replacement"'/g > ') > } > > Denis, what do you think? Is there any chance of getting a C-coded > little binary doing URL-encoding? BB's wget does not do it either, > unfortunately. why not? We can call them urlencode, urldecode, htmlencode, htmldecode etc... -- vda From vda.linux at googlemail.com Sun Feb 3 15:51:32 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Sun, 3 Feb 2008 23:51:32 +0000 Subject: Some patches In-Reply-To: <6784529b0802030210mfbb3231w74585f6e461bfe9e@mail.gmail.com> References: <6784529b0802030210mfbb3231w74585f6e461bfe9e@mail.gmail.com> Message-ID: <200802032351.32344.vda.linux@googlemail.com> On Sunday 03 February 2008 10:10, Vladimir Dronnikov wrote: > Hello! > > I've prepared a set of patches. Great. But please send them one per email. > 1. mkswap: remove unnecessary rewind when getting length of swap device ok, applied. > 2. mount: support mount helpers. E.g. mount -t ntfs-3g /dev/hda1 /mnt would > first try to exec ntfs-3g binary and if it fails then try to issue mount(2). char *args[4] should be char *args[6]. Otherwise ok, applied. > 3. new xmklock(char *lock_file_name) function. It dies if lock_file_name > file already exists. Otherwise it creates that file and securely deletes it > on exit. > This function is then used by 2 BB applets: microcom and [send|fetch]mail. atexit is evil (*big* problems with NOFORK etc). Please avoid. > 4. microcom: now it properly works on piped stdin. Denys, please consider > applying Depends on xmklock... > 5. sendmail: converted to sendmail+fetchmail. The latter simply pulls remote > mailbox content into local Maildir. > Fetchmail is being actively developed so any comments are welcome! Depends on xmklock... -- vda From cristian.ionescu-idbohrn at axis.com Sun Feb 3 16:06:36 2008 From: cristian.ionescu-idbohrn at axis.com (Cristian Ionescu-Idbohrn) Date: Mon, 4 Feb 2008 01:06:36 +0100 (CET) Subject: shell/ash.c; small adjustments Message-ID: <0802040057060.12633@somehost> I'm trying to figure out how to build ash with the DEBUG macro set to 1 or 2. I get linking errors: shell/lib.a(ash.o): In function `main': ash.c:(.text+0x11623): multiple definition of `main' libbb/lib.a(appletlib.o):appletlib.c:(.text+0x30d): first defined here collect2: ld returned 1 exit status Didn't dig. What's the magic Denis? Index: shell/ash.c =================================================================== --- shell/ash.c (revision 20939) +++ shell/ash.c (working copy) @@ -51,8 +51,10 @@ #endif #if DEBUG +#ifndef _GNU_SOURCE #define _GNU_SOURCE #endif +#endif #include "busybox.h" /* for applet_names */ #include #include @@ -6500,7 +6502,7 @@ /* unsigned flags; */ }; #define IS_BUILTIN_SPECIAL(b) ((b)->name[0] & 1) -/* "regular" bltins always take precedence over commands, +/* "regular" builtins always take precedence over commands, * regardless of PATH=....%builtin... position */ #define IS_BUILTIN_REGULAR(b) ((b)->name[0] & 2) #define IS_BUILTIN_ASSIGN(b) ((b)->name[0] & 4) Cheers, -- Cristian From vda.linux at googlemail.com Sun Feb 3 16:30:26 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Mon, 4 Feb 2008 00:30:26 +0000 Subject: [PATCH] nohup behaviour differs slightly from coreutils nohup In-Reply-To: <8fb844ee0801311039t669ddc92udebc1533bb5d312f@mail.gmail.com> References: <8fb844ee0801311039t669ddc92udebc1533bb5d312f@mail.gmail.com> Message-ID: <200802040030.26837.vda.linux@googlemail.com> On Thursday 31 January 2008 18:39, Christoph Gysin wrote: > Hi list > > I found a minor bug in busybox-1.9.0. The nohup module doesn't behave like nohup > from coreutils when it comes to output redirection. > > To test all possible cases I used the following little script: > > $ cat stdout-stderr > #!/bin/bash > echo stdout > echo stderr 1>&2 > > With this, I compared the behaviour of nohup and busybox's nohup module with > different output redirections: > > $ nohup ./stdout-stderr > $ busybox nohup ./stdout-stderr > $ nohup ./stdout-stderr 1>stdout.log > $ busybox nohup ./stdout-stderr 1>stdout.log > $ nohup ./stdout-stderr 2>stderr.log > $ busybox nohup ./stdout-stderr 2>stderr.log > $ nohup ./stdout-stderr 1>stdout.log 2>stderr.log > $ busybox nohup ./stdout-stderr 1>stdout.log 2>stderr.log > > After each command I checked the contents of nohup.out, stdout.log and > stderr.log. "file" stands for the output file nohup.out, "errmsg" stands for > the message nohup prints ("redirecting output to nohup.out"). These are > the results: > > +-----------------++--------------------------+--------------------------+ > | filedescriptors || nohup | busybox | > +--------+--------++--------+--------+--------+--------+--------+--------+ > | stdout | stderr || stdout | stderr | errmsg | stdout | stderr | errmsg | > +--------+--------++--------+--------+--------+--------+--------+--------+ > | tty | tty || file | file | stderr | file | file | stderr | > | tty | - || file | stderr | stderr | file | - | - | > | - | tty || stdout | stdout | stderr | - | - | stderr | > | - | - || stdout | stderr | stderr | - | - | - | > +--------+--------++--------+--------+--------+--------+--------+--------+ > > Please include my patch if you find it useful Applied, thanks! [I also tried to create testsuite for this, but it proved highly non-trivial :(. ] Please test whether current svn works better. -- vda From vda.linux at googlemail.com Sun Feb 3 16:34:50 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Mon, 4 Feb 2008 00:34:50 +0000 Subject: shell/ash.c; small adjustments In-Reply-To: <0802040057060.12633@somehost> References: <0802040057060.12633@somehost> Message-ID: <200802040034.50830.vda.linux@googlemail.com> On Monday 04 February 2008 00:06, Cristian Ionescu-Idbohrn wrote: > I'm trying to figure out how to build ash with the DEBUG macro set to 1 or > 2. I get linking errors: > > shell/lib.a(ash.o): In function `main': > ash.c:(.text+0x11623): multiple definition of `main' > libbb/lib.a(appletlib.o):appletlib.c:(.text+0x30d): first defined here > collect2: ld returned 1 exit status > > Didn't dig. What's the magic Denis? Have no idea, this DEBUG macro is not mine. -- vda From dronnikov at gmail.com Sun Feb 3 22:45:53 2008 From: dronnikov at gmail.com (Vladimir Dronnikov) Date: Mon, 4 Feb 2008 06:45:53 +0000 Subject: =?KOI8-R?Q?=EF=D4=D7=C5=D4:_Some_patches?= In-Reply-To: <200802032351.32344.vda.linux@googlemail.com> References: <6784529b0802030210mfbb3231w74585f6e461bfe9e@mail.gmail.com> <200802032351.32344.vda.linux@googlemail.com> Message-ID: <6784529b0802032245r5164f984l342f0f0dc94aa420@mail.gmail.com> > atexit() is evil. Is there another BB approved way to work with lock files cleanly? To set handlers for all signals to prevent program occasional termination? Isn't it too bloaty? Especially when used in multiple applets. List! Let us invent a library function to deal with lock files. -- Vladimir 2008/2/3, Denis Vlasenko : > On Sunday 03 February 2008 10:10, Vladimir Dronnikov wrote: > > Hello! > > > > I've prepared a set of patches. > > Great. But please send them one per email. > > > 1. mkswap: remove unnecessary rewind when getting length of swap device > > ok, applied. > > > 2. mount: support mount helpers. E.g. mount -t ntfs-3g /dev/hda1 /mnt > would > > first try to exec ntfs-3g binary and if it fails then try to issue > mount(2). > > char *args[4] should be char *args[6]. Otherwise ok, applied. > > > 3. new xmklock(char *lock_file_name) function. It dies if lock_file_name > > file already exists. Otherwise it creates that file and securely deletes > it > > on exit. > > This function is then used by 2 BB applets: microcom and [send|fetch]mail. > > atexit is evil (*big* problems with NOFORK etc). Please avoid. > > > 4. microcom: now it properly works on piped stdin. Denys, please consider > > applying > > Depends on xmklock... > > > 5. sendmail: converted to sendmail+fetchmail. The latter simply pulls > remote > > mailbox content into local Maildir. > > Fetchmail is being actively developed so any comments are welcome! > > Depends on xmklock... > -- > vda > From Alexander at Kriegisch.name Mon Feb 4 00:06:07 2008 From: Alexander at Kriegisch.name (Alexander Kriegisch) Date: Mon, 04 Feb 2008 09:06:07 +0100 Subject: Tool to URL-encode text data In-Reply-To: <200802032330.01369.vda.linux@googlemail.com> References: <47A5F787.6000005@Kriegisch.name> <200802032330.01369.vda.linux@googlemail.com> Message-ID: <47A6C76F.5020703@Kriegisch.name> >> Denis, what do you think? Is there any chance of getting a C-coded >> little binary doing URL-encoding? BB's wget does not do it either, >> unfortunately. > > why not? We can call them urlencode, urldecode, htmlencode, htmldecode > etc... Great. As you might have suspected, I hope you can provide those applets. My C is probably not very much better than your German. ;-) -- Alexander Kriegisch From robinsonnie.busybox at gmail.com Mon Feb 4 02:02:21 2008 From: robinsonnie.busybox at gmail.com (Robinson Nie) Date: Mon, 4 Feb 2008 18:02:21 +0800 Subject: test mail. to ignore it please. Message-ID: test mail to busybox at busybox.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20080204/d5480578/attachment.htm From mailinglist.cache at gmail.com Mon Feb 4 03:13:37 2008 From: mailinglist.cache at gmail.com (Christoph Gysin) Date: Mon, 4 Feb 2008 12:13:37 +0100 Subject: [PATCH] nohup behaviour differs slightly from coreutils nohup In-Reply-To: <200802040030.26837.vda.linux@googlemail.com> References: <8fb844ee0801311039t669ddc92udebc1533bb5d312f@mail.gmail.com> <200802040030.26837.vda.linux@googlemail.com> Message-ID: <8fb844ee0802040313w2afd4a78ka450436079b993ec@mail.gmail.com> On Feb 4, 2008 1:30 AM, Denis Vlasenko wrote: > > Applied, thanks! [I also tried to create testsuite for this, but it proved > highly non-trivial :(. ] > > Please test whether current svn works better. Current svn works as expected. Thanks! Christoph From a.gatt at btinternet.com Mon Feb 4 03:10:19 2008 From: a.gatt at btinternet.com (Andrew Gatt) Date: Mon, 04 Feb 2008 11:10:19 +0000 Subject: HTTPD CGI Message-ID: <47A6F29B.3090500@btinternet.com> Hi, I recently updated my busybox from 1.4.1 to 1.8.2, and now i'm having troubles executing any cgi scripts in httpd. It just returns 404 Not Found on any request. I start httpd with: httpd -f and my cgi scripts are in /cgi-bin/ . Are there any new run time options i need to set? It is serving straight html files fine. Only other idea is that i don't have a config file, but i didn't think you had to have one. Thanks Andrew From vda.linux at googlemail.com Mon Feb 4 04:12:14 2008 From: vda.linux at googlemail.com (Denis Vlasenko) Date: Mon, 4 Feb 2008 12:12:14 +0000 Subject: Patch: Short read problem in unzip and gunzip In-Reply-To: <242876bc0801272017s61e80a8fx1229498a4d343964@mail.gmail.com> References: <242876bc0801172003s756d8193mb4ff0a3cfe47519a@mail.gmail.com> <200801272312.29056.vda.linux@googlemail.com> <242876bc0801272017s61e80a8fx1229498a4d343964@mail.gmail.com> Message-ID: <200802041212.15044.vda.linux@googlemail.com> On Monday 28 January 2008 04:17, JoSH Lehan wrote: > Thanks for responding. > > > Failing that, at least give a reproducible testcase - > > how do you force short reads? > > (no promices that I can work on it soon, though... sorry). > > To give unzip a short read, have it decompress data that comes in > through a pipe. > > cat myfile.zip | unzip - > > This should quickly reproduce the problem. As a worst case scenario, > let unzip only have one byte at a time. > > cat myfile.zip | dd bs=1 | unzip - > > The zipfile you're decompressing should have multiple files in it. > Only the first file will work. The remaining files should fail with > an error. Please test attached fix. -- vda -------------- next part -------------- A non-text attachment was scrubbed... Name: 1.patch Type: text/x-diff Size: 3685 bytes Desc: not available Url : http://busybox.net/lists/busybox/attachments/20080204/9e11587d/attachment.bin From michele.sanges at otomelara.it Mon Feb 4 02:58:35 2008 From: michele.sanges at otomelara.it (Michele Sanges) Date: Mon, 04 Feb 2008 11:58:35 +0100 Subject: splash image during boot - new applet? Message-ID: <1202122715.8632.12.camel@pigreco> Hi all, I'm writing an application in order to show a splash image and a progress bar during the boot phase of my embedded device. This application is based on framebuffer device and is in user space so, unlike 'bootsplash', don't require any kernel patch (similar to 'splashy', but not use the directFB library). Someone think that this application could be useful if added to busybox as applet? Thanks. Michele Sanges From roberto.foglietta at gmail.com Mon Feb 4 04:48:31 2008 From: roberto.foglietta at gmail.com (Roberto A. Foglietta) Date: Mon, 4 Feb 2008 13:48:31 +0100 Subject: splash image during boot - new applet? In-Reply-To: <1202122715.8632.12.camel@pigreco> References: <1202122715.8632.12.camel@pigreco> Message-ID: 2008/2/4, Michele Sanges : > Hi all, > > I'm writing an application in order to show a splash image and a > progress bar during the boot phase of my embedded device. > This application is based on framebuffer device and is in user space so, > unlike 'bootsplash', don't require any kernel patch (similar to > 'splashy', but not use the directFB library). > > Someone think that this application could be useful if added to busybox > as applet? > Considering the growing number of embedded devices based on linux embedded and busybox it seems to me a good idea. Please take a look to asus_osd (from Eee PC source repository) which use X11 but it could be generalized to use FB in userspace. It uses queue in order to communicate the show... so the progress in boot process too. ftp://dlsvr02.asus.com/pub/ASUS/EeePC/701/ASUS_ACPI_071126.rar In that .rar ther are asus_osd.tar.gz containing the sources Ciao, -- /roberto From florian at brandner.net Mon Feb 4 05:05:37 2008 From: florian at brandner.net (Florian Brandner) Date: Mon, 04 Feb 2008 14:05:37 +0100 Subject: HTTPD CGI In-Reply-To: <47A6F29B.3090500@btinternet.com> References: <47A6F29B.3090500@btinternet.com> Message-ID: <20080204140537.k0ijd6h28k0gwo80@intranet.brandner.net> Hi! > I start httpd with: > httpd -f > and my cgi scripts are in /cgi-bin/ . The webroot is specified with -h. -f is for not running as a daemon. Try httpd -f -h My scripts are in /cgi-bin/. Most of them shell scripts generating plain HTML. I simply set them +x for everyone. Works perfectly for me on version 1.9.0. -- Mit freundlichen Gruessen, email:florian at brandner.net Florian Brandner http://www.brandner.net From a.gatt at btinternet.com Mon Feb 4 05:10:29 2008 From: a.gatt at btinternet.com (Andrew Gatt) Date: Mon, 04 Feb 2008 13:10:29 +0000 Subject: HTTPD CGI In-Reply-To: <20080204140537.k0ijd6h28k0gwo80@intranet.brandner.net> References: <47A6F29B.3090500@btinternet.com> <20080204140537.k0ijd6h28k0gwo80@intranet.brandner.net> Message-ID: <47A70EC5.5050802@btinternet.com> Florian Brandner wrote: > Hi! > > >> I start httpd with: >> httpd -f >> and my cgi scripts are in /cgi-bin/ . >> > > The webroot is specified with -h. -f is for not running as a daemon. > Try httpd -f -h > > Sorry, typo i meant -h > My scripts are in /cgi-bin/. Most of them shell scripts > generating plain HTML. I simply set them +x for everyone. Works > perfectly for me on version 1.9.0. > > All my scripts are executable for everyone. If i drop in the busybox 1.4.1 executable it works fine, if i change it for the 1.8.2, i get the 404 messages. I've checked and CGI is enabled in the make file. From florian at brandner.net Mon Feb 4 05:31:40 2008 From: florian at brandner.net (Florian Brandner) Date: Mon, 04 Feb 2008 14:31:40 +0100 Subject: HTTPD CGI In-Reply-To: <47A70EC5.5050802@btinternet.com> References: <47A6F29B.3090500@btinternet.com> <20080204140537.k0ijd6h28k0gwo80@intranet.brandner.net> <47A70EC5.5050802@btinternet.com> Message-ID: <20080204143140.4rm5hjmhc8gw0ww4@intranet.brandner.net> Zitat von Andrew Gatt : > All my scripts are executable for everyone. If i drop in the busybox > 1.4.1 executable it works fine, if i change it for the 1.8.2, i get the > 404 messages. I've checked and CGI is enabled in the make file. How do you start the httpd? From inetd? Then you need the -i option. Can you start it from a console? Make sure to stop any running httpd as well as inetd. Just to make sure that no other httpd is running. Then try "httpd -vv -f -h " to see httpds output. Maybe its printing something useful... Are static pages in loaded correctly? Is maybe the directory cgi-bin not set to executable (744 or something)? -- Mit freundlichen Gruessen, email:florian at brandner.net Florian Brandner http://www.brandner.net From a.gatt at btinternet.com Mon Feb 4 05:52:05 2008 From: a.gatt at btinternet.com (Andrew Gatt) Date: Mon, 04 Feb 2008 13:52:05 +0000 Subject: HTTPD CGI In-Reply-To: <20080204143140.4rm5hjmhc8gw0ww4@intranet.brandner.net> References: <47A6F29B.3090500@btinternet.com> <20080204140537.k0ijd6h28k0gwo80@intranet.brandner.net> <47A70EC5.5050802@btinternet.com> <20080204143140.4rm5hjmhc8gw0ww4@intranet.brandner.net> Message-ID: <47A71885.80007@btinternet.com> Florian Brandner wrote: > Zitat von Andrew Gatt : > >> All my scripts are executable for everyone. If i drop in the busybox >> 1.4.1 executable it works fine, if i change it for the 1.8.2, i get the >> 404 messages. I've checked and CGI is enabled in the make file. > > How do you start the httpd? From inetd? Then you need the -i option. > Can you start it from a console? Make sure to stop any running httpd > as well as inetd. Just to make sure that no other httpd is running. > Then try "httpd -vv -f -h " to see httpds output. Maybe its > printing something useful... > Are static pages in loaded correctly? Is maybe the directory > cgi-bin not set to executable (744 or something)? > I tried the verbose output but it just gave me this. # sbin/httpd -vv -f -h / 192.168.1.78:59031: url:/cgi-bin/control.cgi 192.168.1.78:59031: response:404 However, while checking the cgi-bin flags i realised i was pointing to the through a symlink. Something that seems to work fine in 1.4.1, but will only display static files with 1.8.2. I should have done that test before. I'm not sure either way what the "correct" behaviour should be, only that its different between the two versions. I would actually like to use symlinks, but is this deemed incorrect? From michele.sanges at otomelara.it Mon Feb 4 07:43:30 2008 From: michele.sanges at otomelara.it (Michele Sanges) Date: Mon, 04 Feb 2008 16:43:30 +0100 Subject: splash image during boot - new applet? In-Reply-To: References: <1202122715.8632.12.camel@pigreco> Message-ID: <1202139810.10865.22.camel@pigreco> Roberto, the application is almost completed. It's a program that starts a daemon and then exits; the daemon reads a configuration file for setting: - the splash image (in .ppm format) - position, dimension and RGB colour of the progress bar. and shows them. It is possible to communicate with the daemon by means a fifo; the possible commands are: - the percentage of the boot process - the 'exit' command in order to kill the daemon at the end of boot process. Best regards. Michele Il giorno lun, 04/02/2008 alle 13.48 +0100, Roberto A. Foglietta ha scritto: > 2008/2/4, Michele Sanges : > > Hi all, > > > > I'm writing an application in order to show a splash image and a > > progress bar during the boot phase of my embedded device. > > This application is based on framebuffer device and is in user space so, > > unlike 'bootsplash', don't require any kernel patch (similar to > > 'splashy', but not use the directFB library). > > > > Someone think that this application could be useful if added to busybox > > as applet? > > > > Considering the growing number of embedded devices based on linux > embedded and busybox it seems to me a good idea. Please take a look > to asus_osd (from Eee PC source repository) which use X11 but it could > be generalized to use FB in userspace. It uses queue in order to > communicate the show... so the progress in boot process too. > > ftp://dlsvr02.asus.com/pub/ASUS/EeePC/701/ASUS_ACPI_071126.rar > > In that .rar ther are asus_osd.tar.gz containing the sources > > Ciao, From pgf at brightstareng.com Mon Feb 4 08:39:58 2008 From: pgf at brightstareng.com (Paul Fox) Date: Mon, 04 Feb 2008 11:39:58 -0500 Subject: splash image during boot - new applet? In-Reply-To: michele.sanges's message of Mon, 04 Feb 2008 16:43:30 +0100. <1202139810.10865.22.camel@pigreco> Message-ID: <10476.1202143198@brightstareng.com> > Roberto, > > the application is almost completed. > It's a program that starts a daemon and then exits; the daemon reads a > configuration file for setting: > - the splash image (in .ppm format) > - position, dimension and RGB colour of the progress bar. > and shows them. how does a user-level daemon provide a nice "user experience"? don't you still need kernel splash support in order to fill the screen until you get past init? paul =--------------------- paul fox, pgf at brightstareng.com From WHarms at bfs.de Mon Feb 4 08:50:44 2008 From: WHarms at bfs.de (walter harms) Date: Mon, 04 Feb 2008 17:50:44 +0100 Subject: splash image during boot - new applet? In-Reply-To: <1202139810.10865.22.camel@pigreco> References: <1202122715.8632.12.camel@pigreco> <1202139810.10865.22.camel@pigreco> Message-ID: <47A74264.1060508@bfs.de> aehm there is one thing that troubles me, nothing against eyecandy ... but the whole point of bb is putting as much in so few (C-)byts as possible. but maybe its ok if we open a section with eyecandy (i am voting for fortune to include !) re, wh Michele Sanges wrote: > Roberto, > > the application is almost completed. > It's a program that starts a daemon and then exits; the daemon reads a > configuration file for setting: > - the splash image (in .ppm format) > - position, dimension and RGB colour of the progress bar. > and shows them. > > It is possible to communicate with the daemon by means a fifo; the > possible commands are: > - the percentage of the boot process > - the 'exit' command in order to kill the daemon at the end of boot > process. > > Best regards. > Michele > > Il giorno lun, 04/02/2008 alle 13.48 +0100, Roberto A. Foglietta ha > scritto: >> 2008/2/4, Michele Sanges : >>> Hi all, >>> >>> I'm writing an application in order to show a splash image and a >>> progress bar during the boot phase of my embedded device. >>> This application is based on framebuffer device and is in user space so, >>> unlike 'bootsplash', don't require any kernel patch (similar to >>> 'splashy', but not use the directFB library). >>> >>> Someone think that this application could be useful if added to busybox >>> as applet? >>> >> Considering the growing number of embedded devices based on linux >> embedded and busybox it seems to me a good idea. Please take a look >> to asus_osd (from Eee PC source repository) which use X11 but it could >> be generalized to use FB in userspace. It uses queue in order to >> communicate the show... so the progress in boot process too. >> >> ftp://dlsvr02.asus.com/pub/ASUS/EeePC/701/ASUS_ACPI_071126.rar >> >> In that .rar ther are asus_osd.tar.gz containing the sources >> >> Ciao, > _______________________________________________ > busybox mailing list > busybox at busybox.net > http://busybox.net/cgi-bin/mailman/listinfo/busybox > > > From pgf at brightstareng.com Mon Feb 4 09:23:49 2008 From: pgf at brightstareng.com (Paul Fox) Date: Mon, 04 Feb 2008 12:23:49 -0500 Subject: splash image during boot - new applet? In-Reply-To: yann.morin.1998's message of Mon, 04 Feb 2008 18:08:55 +0100. <200802041808.55157.yann.morin.1998@anciens.enib.fr> Message-ID: <11445.1202145829@brightstareng.com> > Hello all! > > On Monday 04 February 2008 17:39:58 Paul Fox wrote: > > how does a user-level daemon provide a nice "user experience"? don't > > you still need kernel splash support in order to fill the screen > > until you get past init? > > Assuming that getting up to init is fast enough (less than a few seconds), > then you could redirect kernel console to oblivion, and the only provide > user-space boot progress. i guess in our experience, it really looks a lot better if the screen shows something Right Away. we've even gone so far as to make the shutdown splash the same as the startup splash, with some tricks to delay re-init of the framebuffer. this makes reboots look fairly seamless. but i agree that a blank screen during kernel start is a fine thing in most cases. > I would just add a note. Displaying an image as background is nice; having > a progress bar is nice. But I would suggest the possibility to add a > text field (empty by default?) which would be used to display boot process. > Usage would be such as: > > echo "42 Don't Panic!" >/tmp/splash.fifo > > would set progress to 42 percent, and display the message "Don't Panic!" > in the text area. This would make a perfect splash applet! it would also be useful to be able to replace the splash image during boot -- this can help with the font problem, since the ppm image can contain the pre-formatted text in whatever font you want, for those where the FB font isn't appropriate. paul =--------------------- paul fox, pgf at brightstareng.com From brian at brianv.net Mon Feb 4 08:27:22 2008 From: brian at brianv.net (Brian Verenkoff) Date: Mon, 04 Feb 2008 10:27:22 -0600 Subject: Acceptable Characters for Passwords Message-ID: <000f01c8674a$d286a760$3801010a@brianvlt> Is there a resource that lists all the acceptable characters allowed for a Busybox password. I know there's a limitation of 8 characters, but I'm trying to define a password requirement for a test team and want to know what non-alphanumeric characters are or aren't supported. I've searched via google but have not located such a resource. Your help is greatly appreciated. Thanks, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/busybox/attachments/20080204/84593fb0/attachment.htm From gary4gar at gmail.com Mon Feb 4 09:35:19 2008 From: gary4gar at gmail.com (Gaurish Sharma) Date: Mon, 4 Feb 2008 23:05:19 +0530 Subject: Busybox is my Router Message-ID: <5bdba1f60802040935m6968b5c3j4b16b31da42a63ec@mail.gmail.com> Hi list, My router D-link GLB 502T runs on BusyBox v0.61.pre (2006.06.30-13:40+0000). I wanted to know is there any way by which i could disconnect & connect the router from internet via telnet, as this would enable me to use a script & automate the task of downloading Reason my ISP requires me to disconnect & then reconnect so that i can download among FREE time in which my downloads are not charged. I tried rebooting the router but it is not realible as sometimes the ADSL or LAN light does not come up when i start the reboot router, so i thought if there is any way by which i could just end connection without restarting the router. output of ifconfig ---------------------------------------------------------------------------------------- # ifconfig br0 Link encap:Ethernet HWaddr 00:17:7C:04:55:A6 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500 RX packets:3472 errors:0 dropped:0 overruns:0 frame:0 TX packets:2939 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:667880 (652.2 kb) TX bytes:1646841 (1.5 Mb) br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth0 Link encap:Ethernet HWaddr 00:17:7C:04:55:A6 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500 RX packets:3482 errors:0 dropped:0 overruns:0 frame:0 TX packets:2919 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:668686 (653.0 kb) TX bytes:1644947 (1.5 Mb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 ASYMMTU:0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) nas0 Link encap:Ethernet HWaddr 00:17:7C:04:7C:B6 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500 RX packets:3026 errors:0 dropped:0 overruns:0 frame:0 TX packets:2672 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1619634 (1.5 Mb) TX bytes:453679 (443.0 kb) ppp0 Link encap:Point-Point Protocol inet addr:59.95.165.216 P-t-P:59.95.160.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 ASYMMTU:1500