[PATCH] losetup -f
This is a trivial patch to add a -f option to losetup. losetup -f shows the
first free loop device. After the patch executable size is not changed in
two of three arch that I've tested:
AMD64: unchanged
i386: unchanged
i386: +4060bytes (different version of gcc)
The code is incorrect if 1) there are less than 10 loop devices and 2) they
are all busy (but I don't know loop devices enough to correct...).
I use a custom version of ubuntu initrd using busybox 1.6.1 for nearly all
executables (resulting in a 700kb smaller initrd.gz). losetup -f is
used during
the boot, so that it'd be better if it got included in busybox.
Untested suggestion to shave a couple of bytes from losetup.c:
char dev[sizeof(LOOP_NAME0)] = LOOP_NAME0;
char c;
for (c = '0'; c = '9'; ++c) {
char *s;
dev[sizeof(LOOP_NAME0)-2] = c;
s = query_loop(dev);
can be modified into:
char dev[sizeof(LOOP_NAME0)] = LOOP_NAME0;
for (; dev[sizeof(dev)-2] = '9'; ++dev[sizeof(dev)-2]) {
char *s;
s = query_loop(dev);
(stylewise I prefer char dev[] = LOOP_NAME0; but I don't know whether
all compilers would accept it and produce correct code).
Cheers,
Loïc
diff -c -r busybox-1.6.1/include/usage.h busybox-1.6.1.loic/include/usage.h
*** busybox-1.6.1/include/usage.h Sat Jun 30 17:06:45 2007
--- busybox-1.6.1.loic/include/usage.h Thu Sep 20 22:41:43 2007
***
*** 1845,1863
-f Output data as the log grows
#define losetup_trivial_usage \
![-o OFFSET] [-d] LOOPDEVICE [FILE]]
#define losetup_full_usage \
(Dis)associate LOOPDEVICE with FILE, or display current associations \
\n\nOptions:\n \
-d Disassociate LOOPDEVICE\n \
! -o OFFSET Start OFFSET bytes into FILE
#define losetup_notes_usage \
No arguments will display all current associations.\n \
One argument (losetup /dev/loop1) will display the current association\n \
(if any), or disassociate it (with -d). The display shows the offset\n \
and filename of the file the loop device is currently bound to.\n\n \
Two arguments (losetup /dev/loop1 file.img) create a new association,\n \
!with an optional offset (-o 12345). Encryption is not yet supported.\n\n
#define ls_trivial_usage \
[-1Aa USE_FEATURE_LS_TIMESTAMPS(c) Cd \
--- 1845,1865
-f Output data as the log grows
#define losetup_trivial_usage \
!{[-o OFFSET] [-d] LOOPDEVICE [FILE] | -f }
#define losetup_full_usage \
(Dis)associate LOOPDEVICE with FILE, or display current associations \
\n\nOptions:\n \
-d Disassociate LOOPDEVICE\n \
! -o OFFSET Start OFFSET bytes into FILE\n \
! -f Show first free loop device
#define losetup_notes_usage \
No arguments will display all current associations.\n \
One argument (losetup /dev/loop1) will display the current association\n \
(if any), or disassociate it (with -d). The display shows the offset\n \
and filename of the file the loop device is currently bound to.\n\n \
Two arguments (losetup /dev/loop1 file.img) create a new association,\n \
!with an optional offset (-o 12345). Encryption is not yet supported.\n \
!losetup -f will show the first loop free loop device\n\n
#define ls_trivial_usage \
[-1Aa USE_FEATURE_LS_TIMESTAMPS(c) Cd \
diff -c -r busybox-1.6.1/util-linux/losetup.c busybox-1.6.1.loic/util-linux/losetup.c
*** busybox-1.6.1/util-linux/losetup.c Sat Jun 30 17:06:48 2007
--- busybox-1.6.1.loic/util-linux/losetup.c Thu Sep 20 22:43:22 2007
***
*** 18,28
char *opt_o;
unsigned long long offset = 0;
! opt = getopt32(argc, argv, do:, opt_o);
argc -= optind;
argv += optind;
! if (opt == 0x3) // -d + -o (illegal)
bb_show_usage();
if (opt == 0x1) { // -d
--- 18,28
char *opt_o;
unsigned long long offset = 0;
! opt = getopt32(argc, argv, do:f, opt_o);
argc -= optind;
argv += optind;
! if (opt == 0x3 || opt == 0x5 || opt == 0x6) // two options (illegal)
bb_show_usage();
if (opt == 0x1) { // -d
***
*** 37,43
if (opt == 0x2) // -o
offset = xatoull(opt_o);
! /* -o or no option */
if (argc == 2) {
if (set_loop(argv[0], argv[1], offset) 0)
--- 37,46
if (opt == 0x2) // -o
offset = xatoull(opt_o);
! if (opt == 0x4 argc) // -f does not take any argument
! bb_show_usage();
!
! /* -o, -f or no option */
if (argc == 2) {
if (set_loop(argv[0], argv[1], offset) 0)
***
*** 56,66
char *s;
dev[sizeof(LOOP_NAME0)-2] = c;
s = query_loop(dev);
! if (s) {
printf(%s: %s\n, dev, s);
if
JFFS2 rootfs can not boot on my TI DaVinci DVEVM board
Hi all: I am developping on TI DaVinci DVEVM board with Montavista Embeded 2.6.10 linux system. TI DaVinci has supplied a ramdisk filesystme which built by BUSYBOX1.0, I convert it to JFFS2 rootfs image and store to NOR flash, it can boot normally, but the reboot command can not execute successfully, so I want to build my own JFFS2 filesystem. I use busybox-1.5.1,built it as a static binary, and I got /bin,/sbin,/usr,linuxrc at install diretory, then copy /etc,/dev,/lib and other files to the install dir from ramdisk supplied by TI, and usr #mkfs.jffs2 -d install-dir -o rootfs.jffs2 -e 0x1, then store rootfs.jffs2 to mtdblock3 partition on my nor flash, then boot my system. got below errors: request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c I use ramdisk filesyetem supplied by TI as JFFS2 source rootfs, it can work normally, but if I copy the files built by maks install busybox1-5-1 to the ramdisk filesystem, it print the above errors and hang there. Any advice would be appreciatory, thanks! BESTREGARDS Steven _ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/ ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: Updated contact details
On Friday 21 September 2007 01:23, Glenn McGrath wrote: The attached patch updates by contact email address in AUTHORS and removes the email address from copyright statements. Applied. -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: Fwd: New applet: microcom
Hi Vladimir, Applet is in current svn now. Thanks! -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
find does not work correctly with whitespaces
hi all
i'm using BusyBox v1.1.0 (2007.09.08-10:26+) multi-call binary
the command find unfortunately seems to handle files with whitespaces
in the filename incorrectly as the following example shows:
onion ls -la
drwxrwxrwx2 root root 4096 Sep 21 15:39 .
drwxr-xr-x9 root root 4096 Sep 20 14:57 ..
-rwxrwxrwx1 lru users6148 Sep 21 15:22 .DS_Store
-rwxrwxrwx1 lru users 82 Sep 21 15:22 ._test.html
-rwxrwxrwx1 samo users 840050688 Jun 27 16:18 300 -
ForumMasti.com.avi
-rwxrwxrwx1 samo users 679016448 Mar 4 2007 Romance And
Cigarettes.avi
-rwxrwxrwx1 lru users 40874 Sep 21 15:22 httpd.conf
-rwxrwxrwx1 lru users 623 Sep 21 15:22 test.html
onion find . -exec touch '{}' \;
onion ls -la
-rw-r--r--1 root root0 Sep 21 15:40 -
drwxrwxrwx2 root root 4096 Sep 21 15:40 .
drwxr-xr-x9 root root 4096 Sep 20 14:57 ..
-rwxrwxrwx1 lru users6148 Sep 21 15:40 .DS_Store
-rwxrwxrwx1 lru users 82 Sep 21 15:40 ._test.html
-rw-r--r--1 root root0 Sep 21 15:40 300
-rwxrwxrwx1 samo users 840050688 Jun 27 16:18 300 -
ForumMasti.com.avi
-rw-r--r--1 root root0 Sep 21 15:40 And
-rw-r--r--1 root root0 Sep 21 15:40 Cigarettes.avi
-rw-r--r--1 root root0 Sep 21 15:40
ForumMasti.com.avi
-rw-r--r--1 root root0 Sep 21 15:40 Romance
-rwxrwxrwx1 samo users 679016448 Mar 4 2007 Romance And
Cigarettes.avi
-rwxrwxrwx1 lru users 40874 Sep 21 15:40 httpd.conf
-rwxrwxrwx1 lru users 623 Sep 21 15:40 test.html
as you see, there are new files created, instead of updating the
existing files with whitespaces in the filename ...
does anybody know a workaround to this problem or is this a bug?
thanks for any informations and best regards
lukas.
___
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
FATAL: kernel too old
Hello all, I got a problem while tryin' to install busybox on RHEL 3. I've been looking for a rpm to install this the easiest way, and it's seems it's finally not ... I've found three of em, which I tested, and sent me the same error message: - busybox-1.6.1-2.fc8.i386.rpm - busybox-1.2.0-4.i386.rpm - busybox-1.01-3.i386.rpm (The 0.60.5 version is workin', but I need the rpm applet, which is not implemented in this version ...) The message is: # busybox FATAL: kernel too old Segmentation fault I've also tried to compile the 1.7.1 version, but got an error with taskset miscutils/taskset.c: In function `taskset_main': miscutils/taskset.c:78: warning: passing arg 2 of `sched_getaffinity' makes pointer from integer without a cast miscutils/taskset.c:78: too many arguments to function `sched_getaffinity' miscutils/taskset.c:86: warning: passing arg 2 of `sched_setaffinity' makes pointer from integer without a cast miscutils/taskset.c:86: too many arguments to function `sched_setaffinity' make[1]: *** [miscutils/taskset.o] Error 1 make: *** [miscutils] Error 2 Anyone could help please ? Cedric * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Failed to compile busybox 1.7.1 with gcc 3.2.2
Hi, I am having a problem to compile busybox 1.7.1 with gcc 3.2.2. This is the error messages I got: -- libbb/time.c: In function `monotonic_us': libbb/time.c:20: `__NR_clock_gettime' undeclared (first use in this function) libbb/time.c:20: (Each undeclared identifier is reported only once libbb/time.c:20: for each function it appears in.) libbb/time.c: In function `monotonic_sec': libbb/time.c:27: `__NR_clock_gettime' undeclared (first use in this function) make[1]: *** [libbb/time.o] Error 1 make: *** [libbb] Error 2 -- Does anyone have similar problem ? Attached is the config file I used. 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 # # Automatically generated make config: don't edit # Busybox version: 1.7.1 # Fri Sep 21 22:19:00 2007 # CONFIG_HAVE_DOT_CONFIG=y # # Busybox Settings # # # General Configuration # # CONFIG_NITPICK is not set # CONFIG_DESKTOP is not set # CONFIG_FEATURE_BUFFERS_USE_MALLOC is not set # CONFIG_FEATURE_BUFFERS_GO_ON_STACK is not set # CONFIG_FEATURE_BUFFERS_GO_IN_BSS is not set CONFIG_SHOW_USAGE=y # CONFIG_FEATURE_VERBOSE_USAGE is not set # CONFIG_FEATURE_COMPRESS_USAGE is not set CONFIG_FEATURE_INSTALLER=y # CONFIG_LOCALE_SUPPORT is not set CONFIG_GETOPT_LONG=y # CONFIG_FEATURE_DEVPTS is not set # CONFIG_FEATURE_CLEAN_UP is not set # CONFIG_FEATURE_PIDFILE is not set CONFIG_FEATURE_SUID=y # CONFIG_FEATURE_SUID_CONFIG is not set # CONFIG_FEATURE_SUID_CONFIG_QUIET is not set # CONFIG_SELINUX is not set # CONFIG_FEATURE_PREFER_APPLETS is not set CONFIG_BUSYBOX_EXEC_PATH=/proc/self/exe CONFIG_FEATURE_SYSLOG=y CONFIG_FEATURE_HAVE_RPC=y # # Build Options # # CONFIG_STATIC is not set # CONFIG_BUILD_LIBBUSYBOX is not set # CONFIG_FEATURE_FULL_LIBBUSYBOX is not set # CONFIG_FEATURE_SHARED_BUSYBOX is not set # CONFIG_LFS is not set # CONFIG_BUILD_AT_ONCE is not set # # Debugging Options # # CONFIG_DEBUG is not set # CONFIG_WERROR is not set CONFIG_NO_DEBUG_LIB=y # CONFIG_DMALLOC is not set # CONFIG_EFENCE is not set CONFIG_INCLUDE_SUSv2=y # # Installation Options # # CONFIG_INSTALL_NO_USR is not set CONFIG_INSTALL_APPLET_SYMLINKS=y # CONFIG_INSTALL_APPLET_HARDLINKS is not set # CONFIG_INSTALL_APPLET_DONT is not set CONFIG_PREFIX=./_install # # Busybox Library Tuning # CONFIG_PASSWORD_MINLEN=6 CONFIG_MD5_SIZE_VS_SPEED=2 # CONFIG_FEATURE_FAST_TOP is not set # CONFIG_FEATURE_ETC_NETWORKS is not set # CONFIG_FEATURE_EDITING is not set CONFIG_FEATURE_EDITING_MAX_LEN= # CONFIG_FEATURE_EDITING_FANCY_KEYS is not set # CONFIG_FEATURE_EDITING_VI is not set CONFIG_FEATURE_EDITING_HISTORY= # CONFIG_FEATURE_EDITING_SAVEHISTORY is not set # CONFIG_FEATURE_TAB_COMPLETION is not set # CONFIG_FEATURE_USERNAME_COMPLETION is not set # CONFIG_FEATURE_EDITING_FANCY_PROMPT is not set CONFIG_MONOTONIC_SYSCALL=y CONFIG_IOCTL_HEX2STR_ERROR=y # # Applets # # # Archival Utilities # # CONFIG_AR is not set # CONFIG_FEATURE_AR_LONG_FILENAMES is not set # CONFIG_BUNZIP2 is not set # CONFIG_CPIO is not set # CONFIG_DPKG is not set # CONFIG_DPKG_DEB is not set # CONFIG_FEATURE_DPKG_DEB_EXTRACT_ONLY is not set CONFIG_GUNZIP=y CONFIG_FEATURE_GUNZIP_UNCOMPRESS=y CONFIG_GZIP=y # CONFIG_RPM2CPIO is not set # CONFIG_RPM is not set # CONFIG_FEATURE_RPM_BZ2 is not set CONFIG_TAR=y CONFIG_FEATURE_TAR_CREATE=y CONFIG_FEATURE_TAR_BZIP2=y # CONFIG_FEATURE_TAR_LZMA is not set # CONFIG_FEATURE_TAR_FROM is not set CONFIG_FEATURE_TAR_GZIP=y # CONFIG_FEATURE_TAR_COMPRESS is not set # CONFIG_FEATURE_TAR_OLDGNU_COMPATIBILITY is not set # CONFIG_FEATURE_TAR_OLDSUN_COMPATIBILITY is not set CONFIG_FEATURE_TAR_GNU_EXTENSIONS=y # CONFIG_FEATURE_TAR_LONG_OPTIONS is not set # CONFIG_UNCOMPRESS is not set # CONFIG_UNLZMA is not set # CONFIG_FEATURE_LZMA_FAST is not set # CONFIG_UNZIP is not set # # Common options for cpio and tar # # CONFIG_FEATURE_UNARCHIVE_TAPE is not set # CONFIG_FEATURE_DEB_TAR_GZ is not set # CONFIG_FEATURE_DEB_TAR_BZ2 is not set # CONFIG_FEATURE_DEB_TAR_LZMA is not set # # Coreutils # CONFIG_BASENAME=y # CONFIG_CAL is not set CONFIG_CAT=y # CONFIG_CATV is not set CONFIG_CHGRP=y CONFIG_CHMOD=y CONFIG_CHOWN=y CONFIG_CHROOT=y # CONFIG_CKSUM is not set # CONFIG_COMM is not set CONFIG_CP=y CONFIG_CUT=y CONFIG_DATE=y CONFIG_FEATURE_DATE_ISOFMT=y CONFIG_DD=y CONFIG_FEATURE_DD_SIGNAL_HANDLING=y # CONFIG_FEATURE_DD_IBS_OBS is not set CONFIG_DF=y CONFIG_DIRNAME=y CONFIG_DOS2UNIX=y CONFIG_UNIX2DOS=y CONFIG_DU=y CONFIG_FEATURE_DU_DEFAULT_BLOCKSIZE_1K=y CONFIG_ECHO=y CONFIG_FEATURE_FANCY_ECHO=y CONFIG_ENV=y # CONFIG_FEATURE_ENV_LONG_OPTIONS is not set # CONFIG_EXPAND is not set # CONFIG_FEATURE_EXPAND_LONG_OPTIONS is not set CONFIG_EXPR=y # CONFIG_EXPR_MATH_SUPPORT_64 is not set CONFIG_FALSE=y # CONFIG_FOLD is not set CONFIG_HEAD=y #
Re: svn commit: trunk/busybox: include util-linux
On Fri, Sep 21, 2007 at 06:43:29AM -0700, [EMAIL PROTECTED] wrote: Author: vda Date: 2007-09-21 06:43:28 -0700 (Fri, 21 Sep 2007) New Revision: 19927 Log: microcom: new applet by Vladimir Dronnikov [EMAIL PROTECTED] Modified: trunk/busybox/include/applets.h trunk/busybox/include/usage.h trunk/busybox/util-linux/Config.in trunk/busybox/util-linux/Kbuild vda. Fortunately you forgot to add the actual microcom.c Several grave issues with the submitted version: 1) no copyright nor a license! 2) it is not related to the util-linux package, thus should live somewhere else. I'd put it into network/, but miscutils would also be fine. 3) other cosmetic issues i raised in the corresponding thread. ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
RE: FATAL: kernel too old
Thanks for your help ; the menuconfig doesn't work for me, but I manually modified the .config file. I modified it to make a static build of busybox, and it's working fine now ... Sorry for the footer, I've no way to remove it, as it's generated automatically by the mail server ... Sorry for that. To Bernhard Fischer: thanks for your help, though you were a little bit ironic, and I think it's not the way people should answer here, as we do not have all the same knowledge ! In addition, there's a reason why I do not updgrade my OS : this server is running from hours know, and lots of people work on it, using plenty of applications ; and upgrading an OS is not a easy thing, neither a free thing ! That's all, Thx Ced -Message d'origine- De : Natanael Copa [mailto:[EMAIL PROTECTED] Envoyé : vendredi 21 septembre 2007 16:48 À : HAMMER Cédric Ext ROSI/DPS Cc : busybox@busybox.net Objet : Re: FATAL: kernel too old On Fri, 2007-09-21 at 14:47 +0200, HAMMER Cédric Ext ROSI/DPS wrote: Hello all, hi ... I've also tried to compile the 1.7.1 version, but got an error with taskset miscutils/taskset.c: In function `taskset_main': miscutils/taskset.c:78: warning: passing arg 2 of `sched_getaffinity' makes pointer from integer without a cast miscutils/taskset.c:78: too many arguments to function `sched_getaffinity' miscutils/taskset.c:86: warning: passing arg 2 of `sched_setaffinity' makes pointer from integer without a cast miscutils/taskset.c:86: too many arguments to function `sched_setaffinity' make[1]: *** [miscutils/taskset.o] Error 1 make: *** [miscutils] Error 2 Anyone could help please ? Disable taskset in your config. make menuconfig - Miscellaneous Utilities --- taskset This should be added to the FAQ Cedric * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. Ok, I'm informing you, I don't think i'm the inteded addressee of this message. Sorry for not cancelling immediatly. It's generelly a bad idea to send confidential messages to public mailing lists. (those footers are kind of worthless arent they?) -nc * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: FATAL: kernel too old
On Fri, 2007-09-21 at 14:47 +0200, HAMMER Cédric Ext ROSI/DPS wrote: Hello all, hi ... I've also tried to compile the 1.7.1 version, but got an error with taskset miscutils/taskset.c: In function `taskset_main': miscutils/taskset.c:78: warning: passing arg 2 of `sched_getaffinity' makes pointer from integer without a cast miscutils/taskset.c:78: too many arguments to function `sched_getaffinity' miscutils/taskset.c:86: warning: passing arg 2 of `sched_setaffinity' makes pointer from integer without a cast miscutils/taskset.c:86: too many arguments to function `sched_setaffinity' make[1]: *** [miscutils/taskset.o] Error 1 make: *** [miscutils] Error 2 Anyone could help please ? Disable taskset in your config. make menuconfig - Miscellaneous Utilities --- taskset This should be added to the FAQ Cedric * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. Ok, I'm informing you, I don't think i'm the inteded addressee of this message. Sorry for not cancelling immediatly. It's generelly a bad idea to send confidential messages to public mailing lists. (those footers are kind of worthless arent they?) -nc ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: FATAL: kernel too old
On Fri, Sep 21, 2007 at 04:57:05PM +0200, HAMMER Cédric Ext ROSI/DPS wrote: Thanks for your help ; the menuconfig doesn't work for me, but I manually modified the .config file. I modified it to make a static build of busybox, and it's working fine now ... Sorry for the footer, I've no way to remove it, as it's generated automatically by the mail server ... Sorry for that. To Bernhard Fischer: thanks for your help, though you were a little bit ironic, and I think it's not the way people should answer here, as we do not have all the same knowledge ! In addition, there's a reason why I do not updgrade my OS : this server is running from hours know, and lots of people work on it, using plenty of applications ; and upgrading an OS is not a easy thing, neither a free thing ! Sorry for having been ironic, but these issues come up regularly. Previous discussion of this topic can easily be obtained via google.com or your preferred search engine. ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: svn commit: trunk/busybox: include util-linux
On Friday 21 September 2007 15:53, Bernhard Fischer wrote: On Fri, Sep 21, 2007 at 06:43:29AM -0700, [EMAIL PROTECTED] wrote: Author: vda Date: 2007-09-21 06:43:28 -0700 (Fri, 21 Sep 2007) New Revision: 19927 Log: microcom: new applet by Vladimir Dronnikov [EMAIL PROTECTED] Modified: trunk/busybox/include/applets.h trunk/busybox/include/usage.h trunk/busybox/util-linux/Config.in trunk/busybox/util-linux/Kbuild vda. Fortunately you forgot to add the actual microcom.c Several grave issues with the submitted version: 1) no copyright nor a license! Vladimir, please send us a verbatim /* * Header comment block which describes your (c) and licencing terms */ 2) it is not related to the util-linux package, thus should live somewhere else. I'd put it into network/, but miscutils would also be fine. 3) other cosmetic issues i raised in the corresponding thread. I will move it to miscutils (in separate commit). Sorry. -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: Failed to compile busybox 1.7.1 with gcc 3.2.2
Denys Vlasenko wrote: On Friday 21 September 2007 15:28, Steven Shiau wrote: Hi, I am having a problem to compile busybox 1.7.1 with gcc 3.2.2. This is the error messages I got: -- libbb/time.c: In function `monotonic_us': libbb/time.c:20: `__NR_clock_gettime' undeclared (first use in this function) libbb/time.c:20: (Each undeclared identifier is reported only once libbb/time.c:20: for each function it appears in.) libbb/time.c: In function `monotonic_sec': libbb/time.c:27: `__NR_clock_gettime' undeclared (first use in this function) make[1]: *** [libbb/time.o] Error 1 make: *** [libbb] Error 2 -- Does anyone have similar problem ? Attached is the config file I used. Switch off CONFIG_MONOTONIC_SYSCALL -- vda Cool! It's working here. Thanks for your fast response. Steven -- 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
Re: r18727 broke fdisk
On Thu, Jul 12, 2007 at 02:04:38AM +0200, Denis Vlasenko wrote: On Sunday 08 July 2007 10:38, Bernhard Fischer wrote: vda, util-linux/fdisk.c: In function 'seek_sector': util-linux/fdisk.c:641: warning: implicit declaration of function 'lseek64' util-linux/fdisk.c:641: error: 'off64_t' undeclared (first use in this function) util-linux/fdisk.c:641: error: (Each undeclared identifier is reported only once util-linux/fdisk.c:641: error: for each function it appears in.) util-linux/fdisk.c:641: error: expected ')' before 'secno' make[2]: *** [util-linux/fdisk.o] Error 1 make[1]: *** [util-linux] Error 2 If LFS is off, then there really is no lseek64. Please revert. I tested both. On my glibc it works. I suppose it (maybe incorrectly) provides lseek64 even without #define _LARGEFILE64_SOURCE. Can you test whether fdisk.c compiles with LFS unset but with #define _LARGEFILE64_SOURCE added to the top of fdisk.c? No, this will never help. I do not have and do not want LFS. [EMAIL PROTECTED]:/tmp/busybox$ /scratch/obj.i686/buildroot_trunk/build_i386/staging_dir/usr/bin/i386-linux-uclibc-objdump -d /scratch/obj.i686/buildroot_trunk/project_build_i386/uclibc/root/lib/libc.so.0 | grep seek64 || echo none none [EMAIL PROTECTED]:/tmp/busybox$ I do have lseek, of course: [EMAIL PROTECTED]:/tmp/busybox$ /scratch/obj.i686/buildroot_trunk/build_i386/staging_dir/usr/bin/i386-linux-uclibc-objdump -d /scratch/obj.i686/buildroot_trunk/project_build_i386/uclibc/root/lib/libc.so.0 | grep lseek || echo none 8830: e8 df 08 00 00 call 9114 __libc_lseek 9114 __libc_lseek: 9119: e8 00 00 00 00 call 911e __libc_lseek+0xa 9141: 76 0c jbe914f __libc_lseek+0x3b 98b1: e8 5e f8 ff ff call 9114 __libc_lseek 98c7: e8 48 f8 ff ff call 9114 __libc_lseek 9907: e8 08 f8 ff ff call 9114 __libc_lseek b7d2: e8 3d d9 ff ff call 9114 __libc_lseek b99f: e8 70 d7 ff ff call 9114 __libc_lseek 15f87: e8 88 31 ff ff call 9114 __libc_lseek 160ad: e8 62 30 ff ff call 9114 __libc_lseek 160d3: e8 3c 30 ff ff call 9114 __libc_lseek 19126: e8 e9 ff fe ff call 9114 __libc_lseek This issue is still present on trunk, r19927 (and also in 1.7.1). ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: r18727 broke fdisk
On Friday 21 September 2007 17:37, Bernhard Fischer wrote:
If LFS is off, then there really is no lseek64. Please revert.
I tested both. On my glibc it works.
I suppose it (maybe incorrectly) provides lseek64 even without
#define _LARGEFILE64_SOURCE.
Can you test whether fdisk.c compiles with LFS unset but with
#define _LARGEFILE64_SOURCE
added to the top of fdisk.c?
No, this will never help. I do not have and do not want LFS.
Please test attached patch.
--
vda
diff -d -urpN busybox.5/util-linux/fdisk.c busybox.6/util-linux/fdisk.c
--- busybox.5/util-linux/fdisk.c 2007-09-06 20:06:16.0 +0100
+++ busybox.6/util-linux/fdisk.c 2007-09-21 18:01:57.0 +0100
@@ -638,8 +638,16 @@ static void
seek_sector(ullong secno)
{
secno *= sector_size;
+#if ENABLE_FDISK_SUPPORT_LARGE_DISKS
if (lseek64(fd, (off64_t)secno, SEEK_SET) == (off64_t) -1)
fdisk_fatal(unable_to_seek);
+#else
+ if (secno MAXINT(off_t)
+ || lseek(fd, (off_t)secno, SEEK_SET) == (off_t) -1
+ ) {
+ fdisk_fatal(unable_to_seek);
+ }
+#endif
}
#if ENABLE_FEATURE_FDISK_WRITABLE
___
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: JFFS2 rootfs can not boot on my TI DaVinci DVEVM board
On Friday 21 September 2007, yin yinhai wrote: request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c I use ramdisk filesyetem supplied by TI as JFFS2 source rootfs, it can work normally, but if I copy the files built by maks install busybox1-5-1 to the ramdisk filesystem, it print the above errors and hang there. not a busybox problem, please seek advice from the vendor providing support for your setup -mike signature.asc Description: This is a digitally signed message part. ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: FATAL: kernel too old
On Friday 21 September 2007, HAMMER Cédric Ext ROSI/DPS wrote: I got a problem while tryin' to install busybox on RHEL 3. I've been looking for a rpm to install this the easiest way, and it's seems it's finally not ... I've found three of em, which I tested, and sent me the same error message: - busybox-1.6.1-2.fc8.i386.rpm - busybox-1.2.0-4.i386.rpm - busybox-1.01-3.i386.rpm (The 0.60.5 version is workin', but I need the rpm applet, which is not implemented in this version ...) The message is: # busybox FATAL: kernel too old whoever built the .rpm did so requiring a kernel version newer than what you're running ... either upgrade your kernel or dont use prebuilt binaries -mike signature.asc Description: This is a digitally signed message part. ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Re: [PATCH] ash fancy prompt expansion
On Friday 21 September 2007 20:15, Natanael Copa wrote: Looks like it got worse, not better... I am attaching my .config too. How does it look with your config and without the patch? It works without the patch. -- vda ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
JFFS2 rootfs can not boot on my TI DaVinci DVEVM board
Hi all: I am developping on TI DaVinci DVEVM board with Montavista Embeded 2.6.10 linux system. TI DaVinci has supplied a ramdisk filesystme which built by BUSYBOX1.0, I convert it to JFFS2 rootfs image and store to NOR flash, it can boot normally, but the reboot command can not execute successfully, so I want to build my own JFFS2 filesystem. I use busybox-1.5.1,built it as a static binary, and I got /bin,/sbin,/usr,linuxrc at install diretory, then copy /etc,/dev, b and other files to the install dir from ramdisk supplied by TI, and usr #mkfs.jffs2 -d install-dir -o rootfs.jffs2 -e 0x1, then store rootfs.jffs2 to mtdblock3 partition on my nor flash, then boot my system. got below errors: request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c I use ramdisk filesyetem supplied by TI as JFFS2 source rootfs, it can work normally, but if I copy the files built by maks install busybox1-5-1 to the ramdisk filesystem, it print the above errors and hang there. Any advice would be appreciatory, thanks! BESTREGARDS Steven _ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
