False options
Hello, List! Just tried to run # mv foo ---bar and it failed saying unrecognized option ---bar. Wonder, is this the correct behavior or a buglet in getopt32()? -- Vladimir ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
new modprobe
Hi, I have been playing around with Timo's modutils. It solves some issues i have with the alias handling. It works just great. the patch is more or less a rewrite of current utils so its understandable its not replacing current until the 2.4 support is there and working 100%. But what do you think about adding Timo's modprobe in a new directory called module-init-tools. It means we can have both in there and when the 2.4 support is done, the modutils dir can be removed. That way the new code can get more eraly testing while those who prefers the old, stable can still use it. thanks! -nc ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: False options
On Wednesday 03 September 2008 10:03:46 Vladimir Dronnikov wrote: Hello, List! Just tried to run # mv foo ---bar and it failed saying unrecognized option ---bar. Wonder, is this the correct behavior or a buglet in getopt32()? -- Vladimir Hi, it is the same with mv (GNU coreutils) 6.10 mv foo ---bar mv: unrecognized option `---bar' Try `mv --help' for more information. Ciao, Tito ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: False options
On Wednesday 03 September 2008 10:03, Vladimir Dronnikov wrote: Hello, List! Just tried to run # mv foo ---bar and it failed saying unrecognized option ---bar. Wonder, is this the correct behavior or a buglet in getopt32()? # /usr/bin/mv --version mv (GNU coreutils) 6.9 Copyright (C) 2007 Free Software Foundation, Inc. This is free software. You may redistribute copies of it under the terms of the GNU General Public License http://www.gnu.org/licenses/gpl.html. There is NO WARRANTY, to the extent permitted by law. Written by Mike Parker, David MacKenzie, and Jim Meyering. # /usr/bin/mv abc ---xyz /usr/bin/mv: unrecognized option `---xyz' Try `/usr/bin/mv --help' for more information. Use --: # /usr/bin/mv -- abc ---xyz /usr/bin/mv: cannot stat `abc': No such file or directory -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: False options
On Wed, 3 Sep 2008, Denys Vlasenko wrote: On Wednesday 03 September 2008 10:03, Vladimir Dronnikov wrote: Hello, List! Just tried to run # mv foo ---bar and it failed saying unrecognized option ---bar. [skip] Use --: # /usr/bin/mv -- abc ---xyz /usr/bin/mv: cannot stat `abc': No such file or directory # mv foo ./---bar works for me. Cheers, -- Cristian ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: compile 1.10.4 using buildroot
On Tuesday 02 September 2008 04:21, Steven Woody wrote: I got the following error: util-linux/mount.c:520:2: error: #error You need to build uClibc with UCLIBC_HAS_RPC for NFS support. But I think the uClibc has already turned the flag. Comes from here: /* This is just a warning of a common mistake. Possibly this should be a * uclibc faq entry rather than in busybox... */ #if defined(__UCLIBC__) ! defined(__UCLIBC_HAS_RPC__) #error You need to build uClibc with UCLIBC_HAS_RPC for NFS support. #endif below is from uClibc-0.9.29.config: # # Networking Support # UCLIBC_HAS_IPV6=y UCLIBC_HAS_RPC=y UCLIBC_HAS_FULL_RPC=y UCLIBC_HAS_REENTRANT_RPC=y # UCLIBC_USE_NETLINK is not set # UCLIBC_HAS_BSD_RES_CLOSE is not set any clue? Thanks. Something broke, probably in uclibc. Do you see __UCLIBC_HAS_RPC__ #defined in include/bits/uClibc_config.h ? -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: Login exited
On Tuesday 02 September 2008 02:47, Steven Woody wrote: The buildroot I am using is the 080831 snapshot, the busybox is 1.11.2. Now I see the boot prompt finally! But I can't login: --- Welcome to uClibc uClibc login: root Dec 31 17:01:05 nlmt auth.info login[195]: root login on 'ttyS0' Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart. Dec 31 17:0 Welcome to uClibc uClibc login: default Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart. Dec 31 17:0 --- And, I got see a suspicious messages just after the kernel booted: --- VFS: Mounted root (cramfs filesystem) readonly. Freeing init memory: 84K Error -3 while decompressing! c0925384(-7384812)-c3e38000(4096) Coming from kernel's fs/cramfs/uncompress.c: err: printk(Error %d while decompressing!\n, err); printk(%p(%d)-%p(%d)\n, src, srclen, dst, dstlen); return 0; I think I am so near to success, please help me! Thanks. Your filesystem image seems to be damaged. -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: False options
Well, I see it is not BB specific. Thanks! -- Vladimir ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: some patches
On Monday 01 September 2008 10:59, Vladimir Dronnikov wrote: I see. But who (which process) calls finalization? Calls what? I didn't understand you. Well. I use initramfs. Bootloader loads kernel, initramfs and finally executes /sbin/init. In my case init is BB (locally patched) runit which then sits and calls stages. A-ha. Stage 1 runit runs /etc/runit/1 and waits for it to terminate. The system’s one time tasks are done here. /etc/runit/1 has full control of /dev/console to be able to start an emergency shell if the one time initialization tasks fail. If /etc/runit/1 crashes, or exits 100, runit will skip stage 2 and enter stage 3. Stage 2 runit runs /etc/runit/2, which should not return until system shutdown; if it crashes, or exits 111, it will be restarted. Normally /etc/runit/2 starts runsvdir(8). runit is able to handle the ctrl-alt-del keyboard request in stage 2, see below. Stage 3 If runit is told to shutdown the system, or stage 2 returns, it terminates stage 2 if it is running, and runs /etc/runit/3. The systems tasks to shutdown and possibly halt or reboot the system are done here. If stage 3 returns, runit checks if the file /etc/runit/reboot exists and has the execute by owner permission set. If so, the system is rebooted, it’s halted otherwise. So finalization is called by that runit process. But how do you perform startup? Your /sbin/init is what? The mentioned shell script? Or you use /linuxrc? Yes. Look again at the above. Why there is stage 1 at all? Why not #!/bin/sh /a/path/to/stage1_script.sh /a/path/to/stage2_script.sh or even roll them up into one script (or split into more scripts, whatever). and stage 3 is not needed at all - killall5 -TERM etc still works, no need to talk to init. I could reuse existing halt/reboot/poweroff in halt.c but it is made specially for init.c and sends different signals to pid 1, depending on the name of called applet. And runsvdir exits cleanly only if gets TERM signal. Exactly. Good programs _have_ to_ exit on TERM, why can't we use that? I don't understand you again. You can reuse halt/reboot/poweroff for what? I wanna have halt/reboot/poweroff utilities to operate my box. With BB runit (if we apply the patch) they can be bundled in runit.c. But I see that these applets already exist in init/halt.c BB source file. I can reuse them to operate on runit-less stage 2 (bare runsvdir run from shell script, as you suggested) but they (applets) need to be patched so they should send TERM signal to pid #1, not USR1, USR2. I personally will continue to use script as init + killall5 for shutdown. http://busybox.net/~vda/init_vs_runsv.html explains my position. Of course you don't have to do the same. It only means that if you want runit in busybox, you need to write up a mini-doc why is it useful + how to use it (targeted for those who only ever used sysV init). -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: insmod broken in 1.12.0
On Monday 01 September 2008 09:42, Tobias Poschwatta wrote: On Sun, Aug 31, 2008 at 11:58:41PM +0200, Denys Vlasenko wrote: Looks like standard insmod works the same? # /app/module-init-tools-0.9.15-pre2/sbin/insmod camellia insmod: can't read 'camellia': No such file or directory When was 0.9.15-pre2 released? I have module-init-tools-3.4 and insmod works as expected, even after moving /lib/modules/`uname -r` out of the way, copying the module file to e.g. /tmp, and renaming it to xxx.ko. Still can't reproduce. # /usr/app/module-init-tools-3.4/sbin/insmod --version module-init-tools version 3.4 # /usr/app/module-init-tools-3.4/sbin/insmod camellia insmod: can't read 'camellia': No such file or directory strace -o log /usr/app/module-init-tools-3.4/sbin/insmod camellia log: ... open(camellia, O_RDONLY) = -1 ENOENT (No such file or directory) write(2, insmod: can\'t read \'camellia\': N..., 57) = 57 exit_group(1) = ? It does not seem to search any paths. insmod in busybox up to 1.11.2 works as expected. 1.12.0 is the first version that doesn't. Please provide a full command line and strace log of both with the following strace parameters: strace -o log -tt -s 99 /path/to/busybox/insmod ... -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: Login exited
On Thu, Sep 4, 2008 at 1:50 AM, Denys Vlasenko [EMAIL PROTECTED] wrote: On Tuesday 02 September 2008 02:47, Steven Woody wrote: The buildroot I am using is the 080831 snapshot, the busybox is 1.11.2. Now I see the boot prompt finally! But I can't login: --- Welcome to uClibc uClibc login: root Dec 31 17:01:05 nlmt auth.info login[195]: root login on 'ttyS0' Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart. Dec 31 17:0 Welcome to uClibc uClibc login: default Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart. Dec 31 17:0 --- And, I got see a suspicious messages just after the kernel booted: --- VFS: Mounted root (cramfs filesystem) readonly. Freeing init memory: 84K Error -3 while decompressing! c0925384(-7384812)-c3e38000(4096) Coming from kernel's fs/cramfs/uncompress.c: err: printk(Error %d while decompressing!\n, err); printk(%p(%d)-%p(%d)\n, src, srclen, dst, dstlen); return 0; I think I am so near to success, please help me! Thanks. Your filesystem image seems to be damaged. Okay, we leave this 'decompressing' error for a moment. I rebuilt (mostly using default options from buildroot) a very small rootfs image, 780k cramfs. This time, it boots without the 'decompressing' error message, I still can not login in. It's same: whatever user name I inputed, the getty restarted and I get nothing but another prompt. If you experts can not guess what's is going on here, I hope you can tell me how to debug this kind of problem. Tks. -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: [Buildroot] Login exited
On Thu, Sep 04, 2008 at 09:50:01AM +0800, Steven Woody wrote: Okay, we leave this 'decompressing' error for a moment. I rebuilt Actually on second reading I think that is a result of trying to mount configfs on /config, and nothing to do with the root filesystem itself. (mostly using default options from buildroot) a very small rootfs image, 780k cramfs. This time, it boots without the 'decompressing' error message, I still can not login in. It's same: whatever user name I inputed, the getty restarted and I get nothing but another prompt. If you experts can not guess what's is going on here, I hope you can tell me how to debug this kind of problem. Tks. Did you try booting with init=/bin/sh as I suggested two days ago? Or modify your inittab to present you with a shell without needing to login? This will help to break down the problem dramatically. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: [Buildroot] Login exited
On Thu, Sep 4, 2008 at 10:00 AM, Hamish Moffatt [EMAIL PROTECTED] wrote: On Thu, Sep 04, 2008 at 09:50:01AM +0800, Steven Woody wrote: Okay, we leave this 'decompressing' error for a moment. I rebuilt Actually on second reading I think that is a result of trying to mount configfs on /config, and nothing to do with the root filesystem itself. (mostly using default options from buildroot) a very small rootfs image, 780k cramfs. This time, it boots without the 'decompressing' error message, I still can not login in. It's same: whatever user name I inputed, the getty restarted and I get nothing but another prompt. If you experts can not guess what's is going on here, I hope you can tell me how to debug this kind of problem. Tks. Did you try booting with init=/bin/sh as I suggested two days ago? Or modify your inittab to present you with a shell without needing to login? This will help to break down the problem dramatically. I did init=/bin/sh as you suggested and reported the result to the list. Again, the result is: there is nothing I can do after rootfs was loaded by kernel. I can type in characters can see the echo of what I typed on the screen, but no any other outputs. Does this has something to do with my read-only file system type (cramfs)? Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Add ethtool to Busybox ?
Hi, Ethtool (http://sourceforge.net/projects/gkernel) is an useful tool. I found in 2006 there was a try to include that: http://bugs.busybox.net/view.php?id=789 Is that possible to include that in the future release of busybox ? Thanks in advance. -- Steven Shiau steven _at_ nchc org tw steven _at_ stevenshiau org National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
