| Age | Commit message (Collapse) | Author |
|---|
|
with odd or broken networking setups
|
|
|
|
|
|
|
|
I wrote:
>>I think, fdisk have special ext2lseek special for:
>>disk can have size > 4Gb, but all any partitions have < 4Gb and lseek64
>>not require.
>>May be best create new configure option for set DOLFS for fdisk applet
>>if global DOLFS unset?
>
Erik Andersen wrote:
>Agreed. Using an extra configure option when ! DOLFS
>would be a good idea.
Ok. Patch attached.
|
|
actually compile)
|
|
When using "losetup" the device is always setup as Read-Only.
(I have only tested with the -o flag, but looking at the code the
problem seems general)
The problem is the "opt" variable in "losetup.c" that is reused in
the "set_loop()" call. Clear it before the call and everything is OK;
opt = 0; /* <-------- added line */
if (delete)
return del_loop (argv[optind]) ? EXIT_SUCCESS : EXIT_FAILURE;
else
return set_loop (argv[optind], argv[optind + 1], offset, &opt)
? EXIT_FAILURE : EXIT_SUCCESS;
}
Best Regards,
Lars Ekman
|
|
|
|
If BusyBox was compiled with -DCONFIG_FEATURE_CLEAN_UP dmesg command
segfaults if invoked with the "-n" option. (Due to a free() of an
uninitialized pointer).
|
|
|
|
since fdisk will work just fine on smaller disks w/o it.
|
|
|
|
|
|
using uClibc, but have not enabled UCLIBC_HAS_RPC...
-Erik
|
|
|
|
|
|
|
|
enabled, regular lseek is transparently promoted to lseek64 anyways, rendering
the llseek stuff pointless.
-Erik
|
|
but I then completely reworked the fdformat utility to comply
with the current busybox way of doing things.
|
|
|
|
|
|
"rootfs" entry as well as the traditional "/dev/root" entry. This caused
applets such as mount and df to display two root filesystem entries....
This teaches the relevant utilities to ignore the "rootfs" entry.
-Erik
|
|
|
|
|
|
|
|
-Erik
|
|
|
|
-Erik
|
|
during 'mount -a'. If the user wants to do that, hey, its their
lifs. If the nfs server is down and they don't want to wait for
nfs to time out, that is their problem.
-Erik
|
|
people to locate the mtab file somewhere other that /etc to
accomodate read only root filesystems.
-Erik
|
|
N. Oleynik
|
|
only read partition table, by Vladimir N. Oleynik
|
|
> Using linux kernel headers is a Bad Thing(tm) and should be
> punished.
> -Erik
Doing this wrong should be punished even harder :)
- Robert
|
|
Using linux kernel headers is a Bad Thing(tm) and should be
punished.
-Erik
|
|
Using linux kernel headers is a Bad Thing(tm) and should be
punished.
|
|
Using linux kernel headers is a Bad Thing(tm) and should be
punished.
-Erik
|
|
|
|
modified Kbuild system I put into uClibc. With this, there should be no more
need to modify Rules.mak since I've moved all the interesting options into the
config system. I think I've got everything updated, but you never know, I may
have made some mistakes, so watch closely.
-Erik
|
|
maintaining it anymore, and it is now terribly out of date.
-Erik
|
|
|
|
|
|
|
|
-Erik
|
|
The following usage from original user:
$ ./busybox swapon -a
Have typo problem:
swapon: swapon: Operation not permitted
But regular version:
swapon: /dev/hda5: Operation not permitted
Patch attached, reduced 9 bytes and advanced
exit code also.
|
|
|
|
-Erik
|
|
|
|
|
|
why these efforts aren't making the binary smaller.
|
|
<mjn3> printf("\tgeometry %u %u %u %u %u\n", v->xres, v->yres,
<mjn3> v->xres_virtual, v->yres_virtual, v->bits_per_pixel);
<mjn3> printf("\ttimings %u %u %u %u %u %u %u\n", v->pixclock, v->left_margin,
<mjn3> v->right_margin, v->upper_margin, v->lower_margin, v->hsync_l
<mjn3> en,
<mjn3> v->vsync_len);
<mjn3> printf("\taccel %s\n", (v->accel_flags > 0 ? "true" : "false"));
<mjn3> printf("\trgba %u/%u,%u/%u,%u/%u,%u/%u\n", v->red.length,
<mjn3> v->red.offset, v->green.length, v->green.offset, v->blue.leng
<mjn3> th,
<mjn3> v->blue.offset, v->transp.length, v->transp.offset);
<mjn3> printf("endmode\n\n");
<mjn3> whay have multiple printf calls when one would do?
<mjn3> and this:
<mjn3> static struct cmdoptions_t {
<mjn3> char *name;
<mjn3> unsigned char param_count;
<mjn3> unsigned char code;
<mjn3> } g_cmdoptions[] = {
<mjn3> {
<mjn3> "-fb", 1, CMD_FB}, {
<mjn3> (repeated entries)
<mjn3> why isn't this constant? what about struct packing?
inline the helper functions that are only referenced once.
|
