On Wed, Apr 20, 2016 at 03:31:12PM +0200, Linus Walleij wrote:
> On Tue, Apr 19, 2016 at 5:52 AM, Isaac Dunham wrote:
> > On Mon, Apr 18, 2016 at 11:31:27AM +0200, Linus Walleij wrote:
> >> On Wed, Apr 13, 2016 at 2:37 PM, Linus Walleij
> >> wrote:
> >>
> - Yes?
> - No?
> - Linus is an idiot?
FWIW, I'm for it, though I'd like to hear if anyone is using new busybox
with 'vendor'/'BSP' kernels that are old enough for this to be problematic,
yet new enough to need mdev (ie, fro
STEM.
In /sys/dev/char, there's no way to get subsystem from the directory,
so you would need to set it in fileAction; I'm not sure what file is
guaranteed to be readable if present and contains the subsystem off
the top of my head. (You would want to use openat() rather than accepting
a
HCP client or running the manual config.
'wpa-roam' will run wpa_supplicant, listen until wpa_supplicant reports a
connection, and then apply the appropriate configuration for the network.
As a result, wpa-conf has a tendency to cause hangs in the boot process,
while wpa-roam yields faster starts and works better with switching
networks.
(In some cases, buggy out-of-tree drivers can panic the kernel with
wpa-conf; several years ago I noticed that madwifi liked to panic if the
dhcp client started before the connection was complete.)
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
terfaces file
> > and was curious what declarations are available to busybox. So far
> > I'm interested in using the following:
> >
> > address 192.168.0.10
> > netmask 255.255.255.0
> > gateway 192.168.0.1
&
p plugin (IF_WPA_CONF).
These 'plugins' I refer to are scripts in
/etc/network/if-{,pre-,post-}{up,down}.d/
Depending on the directory, they will be executed before or after
interfaces go up or down.
> A list of available, working declarations would be greatly appreciated!
HTH
;t know what those settings are and you can't find them, you'd
be most likely to find out if you ask something like this on XDA:
Where would I find the .config for busybox 1.24.1 (Stericson)?
Once you get that file, look for a line that contains
FEATURE_FTP_AUTHENTICATION
If it says something like "# FEATURE_FTP_AUTHENTICATION is not set",
then it's anonymous.
If it says "FEATURE_FTP_AUTHENTICATION=y", then it's not anonymous.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
e 'config file is '.
If you're very lucky, your busybox version contains an applet named
'bbconfig', which will output the text of the configuration file.
Once you find that config file, grep for FEATURE_FTP_AUTHENTICATION.
> From: Isaac Dunham
> Sent: Wednesda
On Tue, Mar 15, 2016 at 10:46:16AM +0100, Davide Urbani wrote:
> Hi I have a problem with the ftpd command busybox. When I create the socket
> from ftpd server (tcpsvd -vE 0.0.0.0 21 ftpd / files / to / serve) the server
> is running. But when I connect with a client I am always required me a
>
On Tue, Mar 08, 2016 at 01:52:13PM -0300, Marco Viggiano wrote:
>
> On 8 March 2016 at 13:32, Isaac Dunham wrote:
> > On Tue, Mar 08, 2016 at 07:56:09AM +0100, Tito wrote:
> >>
> >>
> >> On 03/08/2016 07:27 AM, Marco Viggiano wrote:
> >> >Hi
ows you to mount a mountpoint so that it's visible across
mount namespaces.
'private' (the default, except with systemd + util-linux) mounts it so
it's visible only in the current namespace.
HTH,
Isaac Dunham
If you add the prefix 'r',
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
it 3163821967821518cfa4c4315f775ec5301bb023
Author: Erik Andersen
Date: Sat Jan 15 22:28:50 2000 +
Sync up busybox with the latest and greatest. This is not stuff for
the Embedix release.
-Erik
Nothing indicates what the reason was. Looking
On Fri, Jan 29, 2016 at 06:10:10PM +0100, Didier Kryn wrote:
> Le 29/01/2016 17:32, Isaac Dunham a écrit :
> >for opt in $#; do
> > case "$opt" in
> > (*=*) eval "$opt"
> > ;;
> > esac
> >done
> >
> >exec busybo
wever, I seem to recall that commonly, options like 'foo=bar' get into
the environment.
This would be doable by means of a script that execs busybox init,
something like this (untested, doesn't handle -...):
for opt in $#; do
case "$opt&qu
it's certainly ugly.)
If you reset the clock time, crond should pick up the new time, sleep
a while if it went backwards, and continue.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
t; Any help would greatly be appreciated!
When testing these, do you restart *crond* so that the timezone applies?
Do you use /etc/localtime for setting the system timezone?
To check the environment of crond, you can do (as root):
# tr '\0' '\n' < /proc/`pidof crond`/environ
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
y minute if it exists
- cron.update is created by 'crontab', and is a simple list of users
whose cron jobs need to be updated.
In your example, .cron.d would need to have this line at the end:
echo 'root' >> /var/spool/cron/crontabs/cron.update
If that's not the pro
MIN $H $DOM $MON $DOW $EXEC" >> /var/spool/cron/crontabs/"$U"
done
}
Bear in mind that this script is a one-shot conversion tool; you would need
to remove duplicates manually if you ran it automatically, and there's
no rovision for removing cron jobs.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
ng the lock.
If you want to run it to lock a critical section of a script, use
exec FD>> FILE
flock FD
...
flock -u FD
(I'm not sure offhand whether you need spaces between FD and the
redirection; < > >> <> are all possible redirectors, meaning open
RO/WO/APPEND/RW.)
HTH
ss = pw_encrypt(pass, salt, 0);
> >> }
> Hi,
> maybe we could change crypt_make_salt to accept lowercase and uppercase algo
> arguments to keep compatibility with both ways
It looks to me like pw_encrypt(pass, str_tolower(salt), 0); would be
simpler and perhaps smaller.
Alternately, you could call that in crypt_make_salt() if you want to
make it consistent.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
ther one is fairly small and can be added without recompiling busybox.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
t that means in practical terms:
I suspect you need a different toolchain, such as a chroot with an older
environment.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
it will *not* be possible to use Busybox ntpd, OpenNTPD, or ntpclient.
NTPsec (gitlab.com/NTPsec/ntpsec), a fork of NTP with a lot of code
cleanup already done, provides ntpq.
(The code cleanup involves a significant reduction in LOCs.)
chrony (chrony.tuxfamily.org), an independent implementati
s not support any runtime configuration; ntpq corresponds
to unimplemented functionality.
ntpdate is not provided, but equivalent behavior can be obtained with
ntpd -q -p PEER [-p PEER2 ...]
OpenNTPD, from which Busybox ntpd came, provides an "ntpctl" comma
this:
DISKPATH=$(readlink -f /sys/class/block/)
USBPATH=${DISKSPOT#*/usb}
USBPORT=$(echo $USBPATH | cut -d/ -f2)
But I'm not sure about all that; it's my best guess of what's going on.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
bly also include
- kernel version
- wpa_supplicant version
- nl80211/wireless related portions of your dmesg (this may be something to
wait on, if it's large.)
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
etlink listener that
writes events to stdout. This work has bitrotted over the last 6 months,
though I could probably get it updated without *too* much work.
There are existing non-Busybox netlink listeners that can work with
the proposed design.)
-
ries so it doesn't matter whether we
> follow symlinks
>
> Granted, the oldest kernel version I tested on at the time was 2.6.37
> (also tested with 3.3 and 3.14). Things may have been different
> before that.
Mdev supports kernels that a
do we do in the DHCP client?
(this is the only one that's been 'solved'.)
My question was whether generalizing the 'sanitize hostname' code made
sense. Seeing that bug, I suspect that's a better function to use for
at least everything but the the DHCP server and dumpleases.
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Mon, Oct 19, 2015 at 10:52:27AM +0200, walter harms wrote:
>
>
> Am 18.10.2015 23:26, schrieb Isaac Dunham:
> > On Sun, Oct 18, 2015 at 07:55:38PM +0200, walter harms wrote:
> >>
> >>
> >> Am 18.10.2015 07:54, schrieb Isaac Dunham:
> >>> R
On Mon, Oct 19, 2015 at 05:41:16PM -0400, Rich Felker wrote:
> On Mon, Oct 19, 2015 at 10:52:27AM +0200, walter harms wrote:
> >
> >
> > Am 18.10.2015 23:26, schrieb Isaac Dunham:
> > > On Sun, Oct 18, 2015 at 07:55:38PM +0200, walter harms wrote:
> >
On Sun, Oct 18, 2015 at 07:55:38PM +0200, walter harms wrote:
>
>
> Am 18.10.2015 07:54, schrieb Isaac Dunham:
> > RFC952/RFC1123 limit the characters in a hostname for a node to
> > [-a-zA-Z0-9], with '-' being legal only in the middle; we were
> > acceptin
From: Isaac Dunham
Subject: [PATCH 0/2] networking/udhcp: conform to RFCs, print numeric age of
leases
In-Reply-To:
Hello,
I'd like to use dumpleases for generating DNS configuration, so that if a
new client joins a udhcpd-based server, it can automatically get a name
assigned.
Part of
RFC952/RFC1123 limit the characters in a hostname for a node to
[-a-zA-Z0-9], with '-' being legal only in the middle; we were
accepting everything from ' ' to '~'.
(As a byproduct of this, the hostname in dumpleases can now be safely
used from scripts without sanitization.)
function
Get lease expiration time in seconds, for tools that care.
This is meant to feed into a script to generate TinyDNS configuration,
where a host can have a 'timestamp' that marks its expiration.
function old new delta
dumpleases_main
On Sat, Oct 10, 2015 at 05:41:44PM +0530, purushi1 . wrote:
> Hi,
>
> Thanks for the response.
> I have attached the modified "whitelist.busybox-small" configuration file .
(which is the .config you use for building Busybox, I presume).
> It throws me the following error:
>
> =
On Wed, Aug 26, 2015 at 07:49:36PM +0200, Tito wrote:
>
>
> On 08/26/2015 07:18 PM, Isaac Dunham wrote:
> >By my test (Debian Jessie, GCC 4.9.2, glibc shared build), the results are:
> >function old new delt
On Wed, Aug 26, 2015 at 10:18:33AM -0700, Isaac Dunham wrote:
> By my test (Debian Jessie, GCC 4.9.2, glibc shared build), the results are:
> function old new delta
> is_suffixed_with 61 4
By my test (Debian Jessie, GCC 4.9.2, glibc shared build), the results are:
function old new delta
is_suffixed_with 61 45 -16
-
he modules load in a predictable
order while removing some duplicates, so that interfaces and devices will
be named consistently.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
ode configurable/default 'n' instead.
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
formation on the
> console through any source. Tracing or logging will be disabled for
> security reasons to make it difficult for hacking.
I hope you realize that CONFIG_FEATURE_SYSLOG does not affect the kernel,
but only Busybox?
Does that affect anything?
Th
stall the
symlinks yourself, but the installer might work.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
nistrable
unless you recover via init=/bin/sh, chroot, or such?
Or is blanking the root password completely wrong?
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Thu, May 07, 2015 at 05:42:40PM +0100, linuxcbon linuxcbon wrote:
> On Thu, May 7, 2015 at 1:28 AM, Isaac Dunham wrote:
> > and your kernel must be set to use mdev as the hotplug helper,
> > via writing to /proc/sys/kernel/hotplug, or using an equivalent
> > sysctl invoca
td
http://git.alpinelinux.org/cgit/aports/tree/main/busybox-initscripts
helpers are the scripts named *dev and *_links
> (Sorry for those questions, I never used mdev before...)
Read docs/mdev.txt!
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Wed, Apr 15, 2015 at 06:46:08PM +0200, Denys Vlasenko wrote:
> On Mon, Apr 13, 2015 at 7:15 PM, Isaac Dunham wrote:
> > Here's a patch series to add mdev -i and make mdev -s a little more
> > featureful, so rules like this one:
> > $MODALIAS=.*root:root 660 @mod
ditional CFLAGS
This is obvious, and as discoverable as you can get.
BTW: -Og is a pretty recent addition to GCC, so there will be toolchains
where that's inappropriate. I think it was implemented after Squeeze was
released...
Thanks,
Isaac Dunham
___
k on mdev -i, including a config option to disable it.
Patch 4 is FEATURE_MDEV_NEWSCAN.
Comments welcome.
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
This can save a bit of space (~100 bytes) when MDEV_PIPE is selected,
since it uses some of the same code.
If MDEV_PIPE is not selected, it costs ~26 bytes.
The main point is to allow executing $VAR rules from mdev -s, so that
manually running modprobe is not needed.
---
util-linux/mdev.c | 48 ++
* strcmp() logic was inverted.
* Keep a default path.
We don't use a dynamically allocated buffer since clearenv() *could*
free that.
* Avoid a slow leak in the reader, whereby we copy strings, add them to
the environment, clear the environment, and forget it.
* micro-optimizations:
- char
From: Natanael Copa
This is to prepare for reading events from a stream. No changes in
logic.
Signed-off-by: Natanael Copa
---
util-linux/mdev.c | 121 --
1 file changed, 63 insertions(+), 58 deletions(-)
diff --git a/util-linux/mdev.c b/uti
From: Natanael Copa
Signed-off-by: Natanael Copa
---
util-linux/mdev.c | 51 +--
1 file changed, 45 insertions(+), 6 deletions(-)
diff --git a/util-linux/mdev.c b/util-linux/mdev.c
index 34d32e5..689fe3a 100644
--- a/util-linux/mdev.c
+++ b/util-
On Sat, Mar 21, 2015 at 03:49:13PM +, Isaac Dunham wrote:
> >
> > >Well, I've poked at this a little this evening.
> > >
> > >See
> > >https://github.com/idunham/busybox
> > >(in branch mdev) if you're curious about details.
>
o read a uevent file, replace
\n with \0, and call handle_event().
> - Why do you need to memset practically the whole buffer every
> poll() iteration ?
This has been fixed with the getenv -> getkey switch.
Thanks for your comments, Laurent!
Thank you,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Fri, Mar 20, 2015 at 10:09:59PM +0100, Laurent Bercot wrote:
> On 20/03/2015 17:47, Isaac Dunham wrote:
> >I'm not sure I follow you on the malloc/free/realloc bit:
> >-according to the manpage, putenv() does not copy the string, but
> >modifies environ by inserti
On Fri, Mar 20, 2015 at 10:04:19AM +0100, Laurent Bercot wrote:
>
> >Well, I've poked at this a little this evening.
> >
> >See
> >https://github.com/idunham/busybox
> >(in branch mdev) if you're curious about details.
>
> Hi Isaac,
> Nice job!
Thanks.
> A few comments:
>
> - Original mdev
ated
VAR=VALUE pairs, followed by a NUL byte).
I've not tested it yet and it's getting latish here, so there are
almost certainly bugs.
I have not yet made this optional; it should be possible to disable
mdev -i completely before it gets merged.
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Thu, Mar 19, 2015 at 06:02:33PM -0600, James Bowlin wrote:
> On Wed, Mar 18, 2015 at 02:48 AM, Isaac Dunham said:
> > Is this manifested as "the root device never shows up"?
>
> Yes, although we call it the boot device.
>
> > As the one who probably
has been solved
though).
The workaround I used was to redirect stdin to read from the file:
- gzip -dc FILE
+ gzip -dc < FILE
3) While I don't remember what it is, I know that fglrx has an option
that will create archives raher than installing the driver.
This may be your best bet.
>
loading modules since in every case I've been able to
> investigate, an alias for the missing module(s) is in the output
> of the find command I gave above. I haven't yet done exhaustive
> testing but every test with repeated coldplugging has worked even
> on the system where the hotplugging is flaky (and which is now
> out of my reach).
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Mon, Mar 16, 2015 at 10:08:37PM +0100, Natanael Copa wrote:
> On Sun, 15 Mar 2015 01:07:02 +
> Isaac Dunham wrote:
>
> > Also, I'm thinking about adding "mount -m"; this is an extension over
> > util-linux mount, which would create the mountpoint if it
an array of strings in the memory you
read to, then blank environ[0], then overwrite the memory where
everything was stored.
You may want to save $PATH if you do this, though I don't know if the
kernel-provided default is functionally different from the shell
default.
> + }
> + handle_event(temp, 0);
> + if (fds.revents & POLLHUP)
> + break;
> + }
> + if (r == -1)
> + return EXIT_FAILURE;
> } else {
> - handle_event(temp);
> + handle_event(temp, 1);
> }
>
> if (ENABLE_FEATURE_CLEAN_UP)
> --
> 2.3.2
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
ything
be the *source* for mdev.conf, your fstab, and so on?
> >Also, I really am interested in what this looks like/lets you do
> >(in the sense of wanting to start experimenting some more.)
>
> My usual steps of development are: Planning, hacking, testing on my
> machines,
On Sun, Mar 15, 2015 at 09:08:19PM +0100, Harald Becker wrote:
> On 15.03.2015 06:01, Isaac Dunham wrote:
> >>the fstab approach has one big cave-eat, which got me awy from that idea: he
> >>format of fstab does not allow to specify the owner, group and permissions
>
th a service file
or adding "mkdir /dev/mqueue && mount -t mqueue /dev/mqueue" to a
script.
> ... beside that i think it's always a good idea to have the possibility to
> overwrite the name of the default table (e.g. when your root file system
> including etc is read
ons similar to die(), edie()
> and dbg() that don't use stdio, and call _exit() instead of exit().
> If you manage to scrap stdio, you gain 2 pages of text (with the
> musl implementation).
For what it's worth, atexit() requires using exit() instead of _exit().
But that doesn't a
On Wed, Mar 11, 2015 at 08:07:02PM +0100, Denys Vlasenko wrote:
> On Wed, Mar 11, 2015 at 7:14 PM, Isaac Dunham wrote:
> > On Wed, Mar 11, 2015 at 04:11:27PM +0100, Denys Vlasenko wrote:
> >> Applied, thanks!
> >
> > Ok, I have two questions (one about the chan
ce mdev, or that a long-running
fifo supervisor is a *good* solution for hotplug, it would certainly be
possible to do what Harald proposes - likely in 200-300 LOC.
Thanks,
Isaac Dunham
/* shp - stupid hotplugger
*
* This is a "hotplugger" that (a) opens a fifo,
* spawns a helper, and du
nction/tool that parses the
output of ldd to figure out what to copy.
> Thanks again, your pointers are moving me down the line. Unfortunately, I
> got preempted for other work at the moment.
> Thanks!
> Regards,
> Stephen Beckwith
Glad to be of help.
Thanks,
Isaac Dunham
On Thu, Mar 12, 2015 at 04:04:41PM +0100, Harald Becker wrote:
> Hi Isaac !
>
> On 12.03.2015 02:05, Isaac Dunham wrote:
> >>>I just don't think you're quite thinking through exactly what this means.
> >>In which sense? Let me know, what I got wrong.
fo or (as daemon) read from the fifo, spawn
> >mdev -p, and write to a pipe.
> >I'd assume it needs a *simple* config file, which could be just a line
> >or two:
> >/sbin/mdev -p
> >timeout
>
> ??? :(
The first line specifies the hotplu
On Wed, Mar 11, 2015 at 04:15:21PM -0400, Stephen Beckwith wrote:
> Greetings,
>Please forgive the long-winded e-mail, but as a fellow developer, the
> more you know, the easier/quicker you can reach some sort of conclusion
> with my problem here.
> This kernel seems to boot OK, to the point o
On Wed, Mar 11, 2015 at 04:11:27PM +0100, Denys Vlasenko wrote:
> On Wed, Mar 11, 2015 at 3:47 PM, Isaac Dunham wrote:
> > On Wed, Mar 11, 2015 at 10:21:26AM +0100, walter harms wrote:
> >>
> >>
> >> Am 11.03.2015 06:35, schrieb Isaac Dunham:
> >> >
mmonly
used to find help.
A line in the help text mentioning
echo /sbin/mdev >/proc/sys/kernel/hotplug
would be at least as helpful.
Besides, I think that Denys has a good point about the Unix way.
> The following questions to this topic:
>
> - are MODALIAS requests send to
On Wed, Mar 11, 2015 at 10:21:26AM +0100, walter harms wrote:
>
>
> Am 11.03.2015 06:35, schrieb Isaac Dunham:
> > +0 bytes disabled, +56 enabled when DESKTOP is enabled (glibc/i386):
> > function old ne
+0 bytes disabled, +56 enabled when DESKTOP is enabled (glibc/i386):
function old new delta
.rodata 144949 144971 +22
packed_usage 30236 30256 +20
mount_main
---
I wanted to add a feature to mount, and this made that a little nicer,
since everything is in one place.
util-linux/Config.src | 88 ---
util-linux/mount.c| 88 +++
2 files changed, 88 inserti
the environment,
checked for a match, run if need be, then unset and freed.
mdev -p
- same functionality, but another name would be *much* better.
I suggested mdev -i for this, and would prefer that on the grounds
that only programmers care about the fact that it's pre-parsing
the config file; as a *user*, I'd find
"-iread events from stdin"
to be much more obvious.
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
n it finishes
Everything but the timeout has to be done anyhow in both mdev and the
netlink daemon.
In (a), the timeout could be set on the mdev commandline, or in mdev.conf;
if it is set on the mdev commandline, *that* needs to be specified on
the netlink daemon's c
gotten Samba working, though I briefly attempted it years
ago.
I wouldn't be able to help with part 1 either without knowing kernel
version and how /dev is managed.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Wed, Mar 04, 2015 at 10:05:06PM +, Laszlo Papp wrote:
> Better, thanks, but the documentation would still not mention the case of
> abort.
>
> On Tuesday, March 3, 2015, Isaac Dunham wrote:
> > How is this patch for clarifying the documentation?
> > //usage:
uot; suffix for decimal is not in coreutils manpage, looks like it's
> deprecated */
> + /* coreutils also understands TPEZY suffixes for tera- and so on, with
> B suffix for decimal */
> + { "", 0 }
> +};
Was this copy-pasted from coreutils/dd.c?
The bloat
On Tue, Mar 03, 2015 at 03:58:12PM +, Laszlo Papp wrote:
> On Tue, Mar 3, 2015 at 3:54 PM, Denys Vlasenko
> wrote:
> > On Tue, Mar 3, 2015 at 2:56 PM, Laszlo Papp wrote:
> >> On Mon, Mar 2, 2015 at 5:07 PM, Denys Vlasenko
> >> wrote:
> >>> On Mon, Mar 2, 2015 at 10:39 AM, Laszlo Papp wrot
ngs is a mistake?
+ || (detected_fstype != NULL && detected_fstype != mp->mnt_type))
- guess_fstype, fstype, blkid commands:
guess_fstype is the name that Puppy Linux has used for a command that
outputs filesystem type without label/uuid.
fstype is the name that it goes by in Toybox, which is now in Android.
However, upstream Android turns it off and just uses blkid.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
e same
prototype as glibc; apparently Solaris uses the first alternate prototype;
and the last mentioned seems to be a reference to Tru64, which
uses pw_fp to keep track of its position instead of an iterator.
OpenBSD and MirBSD do not implement getpwent_r, as far as I can tell.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
ns had only long options.
>
> > In addition, the long option is not the problem. The problem is that
> > the functionality is switched off by switching the long option off,
> > rather than the actual functionality.
>
> It's about 6.5 kb
do not use nonstandard extensions...
>
> Ok, let me restate the question.
> On which version(s) of FreeBSD do you see lack of mempcpy?
I see no indication that mempcpy has ever been available on FreeBSD;
the man page says only "This function is a GNU extension." under
CONFORMING TO.
gnulib documentation indicates that it is essentially glibc only.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
o `basename $MODPATH .ko`)
By definition, a module name (type 3) cannot contain '/'.
However, the check for '/' checked the command line, which can be an alias.
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On Wed, Jan 14, 2015 at 06:58:09PM +0100, Denys Vlasenko wrote:
> On Sun, Jan 11, 2015 at 10:02 PM, Isaac Dunham wrote:
> > On Sun, Jan 11, 2015 at 05:39:19PM +0100, Denys Vlasenko wrote:
> >> On Sun, Jan 11, 2015 at 7:23 AM, Isaac Dunham wrote:
> >> > filename2mod
On Sun, Jan 11, 2015 at 05:39:19PM +0100, Denys Vlasenko wrote:
> On Sun, Jan 11, 2015 at 7:23 AM, Isaac Dunham wrote:
> > filename2modname needs to do dir-stripping,
>
> Well, it was doing that.
>
> Which lead to "modprobe dir/dir/dir/file"
> work as if it wa
that filename2modname() is
functionally equivalent to part of the code in pathname_matches_modname(),
so I made the latter call the former and saved 119 bytes
(gcc 4.9, musl/x86).
Could you test and see if my patch fixes your problem?
(Note: apparently the "full" modutils does
filename2modname needs to do dir-stripping, or I get:
modprobe: remove 'kernel/drivers/usb/class/usblp': No such file or directory
While we're here, replace the guts with functionally equivalent code
from pathname_matches_modname(), and make that call filename2modname().
Unbreaks modprobe-small f
lot.
> You and me, as authors, still can re-license all our changes.
> --
> vda
I prefer seeing the original license preserved in general, but if you
take that course, I'd assume you will need to contact at least the
first three of the other Busybox contributors who modified ntpd:
Miroslav Lichvar
Jean-Christophe Dubois
Paul Marks
Anthony G. Basile
Cristian Ionescu-Idbohrn
Mike Frysinger
Pere Orga
Leonid Lisovskiy
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
;if ... else' statement.
This is the wrong way, IMHO.
It means that you *cannot* compile busybox with i2ctools that work on
pre-2.6.14(?) kernels, unless you build it using 2.6.14 or older headers;
and in that case, you must recompile busybox if you upgrade the kernel.
It would be tolerable if it
On Fri, Oct 10, 2014 at 11:24:15PM -0700, Isaac Dunham wrote:
> On several occasions I've wished for a tool that can show battery charge,
> whether the power supply is working, and similar things.
> Some time back I wrote the original version of this for toybox;
> I just por
the documentation for your emulator to
see if the emulator allows configuring the MAC address.
HTH,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
oo", optionally having the "--frobnicate"
option):
/* CONFIG_FOO usage: does foo to input
* -b do bar
* -o FILE write to FILE
*/
/* CONFIG_FOO_FROBNICATE usage:
* -f,--frobnicate frobnicate the output
*/
But I'm not quite sure how to handle wanting a su
change that behaviour.
Is there a reason that this sort of command line wouldn't work:
zcip -f -r $RANGE 2>&1 |logger -t zcip
?
>
> Best regards,
>
> Michel Stam
> Embedded System Engineer
Thanks,
Isaac Dunham
___
busyb
-h instead. And it works.
But ls -d should not follow symlinks.)
Thanks,
Isaac Dunham
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
1 - 100 of 141 matches
Mail list logo
