| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"There seems to be a slight problem with the "mod_strcmp" function in
modprobe.c, it scans for the first occurence of the module name in the
"mod_path" variable and expects it to be the last path element. ie
/lib/modules/2.4.22-debug/kernel/fs/vfat in my example. The comparison
will always fail if mod_path contains another substring matching the
module name."
Robert McQueen wrote
"Although William Barsse's patch fixed mod_strcmp for 2.4 kernels, there
was a remaining problem which prevented it from working for me. I've
just tracked it down - when you enable kernel 2.6 module support it
hard-wired the extension to .ko instead of checking at runtime like the
other places where 2.4 differs from 2.6. The attached patch fixes this
for me."
git-svn-id: svn://busybox.net/trunk/busybox@9082 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9064 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9063 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A question was posted a month ago by Mark Alamo to see if others had
problems with sourcing subscripts within msh. We asked his firm to fix the
msh.c bug he described because we didn't have enough time to do it
ourselves.
When msh.c is executing a compound statement and there is a . command to
source another script file, msh.c will not execute the subscript until it's
completed executing the rest of the compound statement.
His example was this:
Echo "Start" ; . ./subA; echo "mid" ; . ./subB ; echo "end"
subA and subB execute AFTER end is printed in reverse order. The same is
true if the sourced files are inside an if else fi, case esac, or any
compound statement.
Attached is a patch to msh.c. It fixes the problem. Cd to the root of your
busybox tree and execute "patch -p1 < msh.c.patch"
Unfortunately, I won't have more time to work on this so I hope that there
aren't any problems!
Michael Leibow
Senior Software Engineer
Belkin Corporation
git-svn-id: svn://busybox.net/trunk/busybox@9062 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9061 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fixes two other issues (plus the previous as well) with a 2.4 kernel :
- should be able to modprobe an already loaded module and get 0 return
code :
# modprobe <something> && modprobe <something> && echo "ok" || echo "failed"
....
failed
Well, hope this helps and that I didn't screw up again,
- William
git-svn-id: svn://busybox.net/trunk/busybox@9057 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hi to all,
This patch is useful for:
1) remove an unused var from extern char *find_real_root_device_name(const char* name)
changing it to extern char *find_real_root_device_name(void).
2) fixes include/libbb.h, coreutils/df.c, util-linux/mount.c and util-linux/umount.c accordingly.
3) fixes a bug, really a false positive, in find_real_root_device_name() that happens if
in the /dev directory exists a link named root (/dev/root) that should be skipped but
is not. This affects applets like df that display wrong results
git-svn-id: svn://busybox.net/trunk/busybox@9056 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9055 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with no value exist, i.e.
$ export BOB=''
% ./busybox awk
Segmentation fault
This patch teaches awk to not blow chunks on empty env variables.
-Erik
git-svn-id: svn://busybox.net/trunk/busybox@9054 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9049 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
-Erik
git-svn-id: svn://busybox.net/trunk/busybox@9048 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
| |
the 'who' and 'last' applets among other things to work as expected.
-Erik
git-svn-id: svn://busybox.net/trunk/busybox@9047 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9046 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
create a dev_t
git-svn-id: svn://busybox.net/trunk/busybox@9045 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
| |
bootp_down() seems redundant, esp since bootp_down was a subset
of static_down, so just use that...
git-svn-id: svn://busybox.net/trunk/busybox@9044 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9038 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9036 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9030 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9029 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9026 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9025 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9024 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9023 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9022 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9021 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hi,
With the following /etc/fstab (any two or more lines of nfs), mount -a
-t nfs causes a segmentation faults.
server:/exports/aaa /mnt/aaa nfs defaults 0 0
server:/exprots/bbb /mnt/bbb nfs defaults 0 0
In util-linux/nfsmount.c, it overwrites malloc'ed pointer *mount_opts
with a static pointer. With this patch it does proper memory realloc
and data copy instead.
git-svn-id: svn://busybox.net/trunk/busybox@9020 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9019 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9018 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9017 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9016 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
| |
dev_t. This is especially important now that the user space concept of a dev_t
and the kernel concept of a dev_t are divergant. The only bit of user space
allowed to know the number of major and minor bits is include/sys/sysmacros.h
(i.e. part of libc). When used with a current C library and a 2.6.x kernel,
this fix should allow BusyBox to support wide device major/minor numbers.
-Erik
git-svn-id: svn://busybox.net/trunk/busybox@9015 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With job control enabled, ash fails to tcsetpgrp back to initialpgrp
upon exit. exitshell() should call setjobctl(0) to do this.
Context: I am using a lightweight menu system (replimenu[.sf.net]) on my
console, which invokes "/bin/sh -i -c /bin/login", where /bin/sh and
/bin/login are busybox applets. /bin/sh is ash, with
CONFIG_ASH_JOB_CONTROL=y as the sole suboption. The shell of the user
concerned (nobody) is also /bin/sh (ash). When the user /bin/sh exits
(and thereby login and its parent sh), replimenu receives EIO when it
tries to read from the terminal.
git-svn-id: svn://busybox.net/trunk/busybox@9013 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
the following example was broken, echo "1 1 +" | dc
git-svn-id: svn://busybox.net/trunk/busybox@9012 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9011 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
increment > 0.
git-svn-id: svn://busybox.net/trunk/busybox@9010 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
some trailing '\n'
git-svn-id: svn://busybox.net/trunk/busybox@9009 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9008 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9007 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
script.
git-svn-id: svn://busybox.net/trunk/busybox@9006 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
in this case) the order was incorrect and there were duplicate entries.
git-svn-id: svn://busybox.net/trunk/busybox@9005 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
| |
"As noticed today by Steven Scholz, the od's `-v' was broken.
I've fixed that and now both the flags `-v' and `-a' are OK"
Fixes a segfault in
echo "uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu\02bar\4"| ./busybox od -av
git-svn-id: svn://busybox.net/trunk/busybox@9004 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
referencing a string and using a single char, when *p <= 0x1f."
git-svn-id: svn://busybox.net/trunk/busybox@9003 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9002 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9001 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@9000 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
| |
an optional argument.
Looks like a glibc bug to me
git-svn-id: svn://busybox.net/trunk/busybox@8997 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
| |
Support for /etc/modprobe.conf (for 2.6 kernels) should likely be added
to bb's modprobe, see attached patch.
modprobe.conf is just a (even simpler) variant of modules.conf
git-svn-id: svn://busybox.net/trunk/busybox@8996 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"I have a need to _really_ know if the interface was properly configured
via ifup so I made busybox's ifupdown pass the return codes through rather
than dropping them on the floor."
"All the functions in ifupdown.c return 1 on success and 0 on failure
(which happens to the opposite of standard practices but whatever).
So it is important for all these functions to not blindly return 1."
"The problem with blindly returning ret, even if it is != 1, is the
callers expect a 0 or 1 and accumulate the return codes. So a function that
makes 3 calls to execute will have a value of 3 accumulated. That value
of 1 (success) was almost always returned even if 1 of the commands in the
command sequence failed. The attached patch fixes the lack of checking
to verify thar result == expected_reult."
git-svn-id: svn://busybox.net/trunk/busybox@8995 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@8994 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@8993 69ca8d6d-28ef-0310-b511-8ec308f3f277
|