<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.busybox">
    <title>gmane.linux.busybox</title>
    <link>http://blog.gmane.org/gmane.linux.busybox</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36256"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36253"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36251"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36247"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36243"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36242"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36223"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36221"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36220"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36217"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36213"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36209"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36201"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36199"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36185"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36173"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36172"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36167"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36163"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/36152"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36256">
    <title>bb 1.17 causing subsequent driver problems</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36256</link>
    <description>&lt;pre&gt;I've been using bb 1.16.2 to build a custom initramfs, which we use to
replace the stock initrd in Centos 5 (we do some special things we need
in the initramfs).  Now I need mkfs_ext2, so I grabbed the bb 1.17.2
that I use in another project.  But I'm getting some odd behavior.  The
initramfs loads fine and does all the stuff it's supposed to, after
which it does a switch_root (so the initramfs &amp;amp; bb are out of the
picture) and mounts the file systems from the local disk, runs the
Centos rc scripts, all which seems to go fine.  But with 1.17, when udev
is started by Centos's rc.sysinit, I get an error that "DM multipath
kernel driver not loaded", and then later a modprobe warning, "Could not
open 'kernel/net/netfilter/x_tables.ko': no such file or directory"
followed by another modprobe error, "FATAL: Error inserting ip_tables
(kernel/net/ipv4/netfilter.ko: no such file or directory", even though
both those files are on the disk.  And of course, iptables then won't
run.

Any ideas as to what changed between 1&lt;/pre&gt;</description>
    <dc:creator>Peter Scheie</dc:creator>
    <dc:date>2012-05-25T16:27:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36253">
    <title>Problems with --sort-section=alignment</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36253</link>
    <description>&lt;pre&gt;Busybox is linked with --sort-section=alignment, and this seems to be
causing an obscure bugs one of my users experienced building busybox
on ARM/musl target. I've filed a bug report with binutils, but I'm not
sure where the issue should be addressed. See here:

http://sourceware.org/bugzilla/show_bug.cgi?id=14156

Basically, --sort-section=alignment wants to reorder the .init
section, which is not possible. The problem does not show up on other
targets, but I can't see anything that inhibits reordering .init, so
it seems to be working only by chance...

Rich
&lt;/pre&gt;</description>
    <dc:creator>Rich Felker</dc:creator>
    <dc:date>2012-05-24T00:21:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36251">
    <title>swapon: implementing discard option.</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36251</link>
    <description>&lt;pre&gt;Hi,

This makes swapon to use discard option.
Enable support for discarding freed pages before they are reused.

Cheers,
Andy

---
 util-linux/Config.src  |    7 +++++++
 util-linux/swaponoff.c |   41 +++++++++++++++++++++++++++++++++--------
 2 files changed, 40 insertions(+), 8 deletions(-)

diff --git a/util-linux/Config.src b/util-linux/Config.src
index 57a52ce..84652eb 100644
--- a/util-linux/Config.src
+++ b/util-linux/Config.src
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -606,6 +606,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; config FEATURE_SWAPON_PRI
 help
   Enable support for setting swap device priority in swapon.

+config FEATURE_SWAPON_DISCARD
+bool "Support discard option -d"
+default y
+depends on SWAPONOFF
+help
+  Enable support for discarding freed pages before they are reused.
+
 config SWITCH_ROOT
 bool "switch_root"
 default y
diff --git a/util-linux/swaponoff.c b/util-linux/swaponoff.c
index 54867ec..d911b31 100644
--- a/util-linux/swaponoff.c
+++ b/util-linux/swaponoff.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -8,10 +8,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
  */

 //usage:#define swapon_trivial_usage
-//usage:       "[-a]&lt;/pre&gt;</description>
    <dc:creator>Andy Lee</dc:creator>
    <dc:date>2012-05-23T01:02:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36247">
    <title>[PATCH] unzip: ignore chmod errors</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36247</link>
    <description>&lt;pre&gt;This makes unzip to FAT filesystems not exit with error.

This similar to how the "normal" unzip works.
---
 archival/unzip.c       |    2 +-
 include/libbb.h        |    1 +
 libbb/make_directory.c |    7 ++++++-
 3 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/archival/unzip.c b/archival/unzip.c
index 3c76cda..c1b945a 100644
--- a/archival/unzip.c
+++ b/archival/unzip.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -596,7 +596,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int unzip_main(int argc, char **argv)
 printf("   creating: %s\n", dst_fn);
 }
 unzip_create_leading_dirs(dst_fn);
-if (bb_make_directory(dst_fn, dir_mode, 0)) {
+if (bb_make_directory(dst_fn, dir_mode, FILEUTILS_IGNORE_CHMOD_ERR)) {
 xfunc_die();
 }
 } else {
diff --git a/include/libbb.h b/include/libbb.h
index f12800f..5e5c8c7 100644
--- a/include/libbb.h
+++ b/include/libbb.h
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -333,6 +333,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; enum {/* DO NOT CHANGE THESE VALUES!  cp.c, mv.c, install.c depend on them. */
 FILEUTILS_PRESERVE_SECURITY_CONTEXT = 1 &amp;lt;&amp;lt; 9, /* -c */
 FILEUTILS_SET_SECURITY_CONTEXT &lt;/pre&gt;</description>
    <dc:creator>Natanael Copa</dc:creator>
    <dc:date>2012-05-22T14:56:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36243">
    <title>patches for building with Android NDK</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36243</link>
    <description>&lt;pre&gt;Dear Busybox developers,

Since Rob Walker's patch[1], building busybox with the Android NDK has 
really become dead simple; no special hacks or external libraries are 
needed anymore.

However, a large number of applets can currently not be built.

I started documenting why applets don't build, as well as collecting 
patches from different sources, that fix the issues:
https://github.com/tias/android-busybox-ndk
https://github.com/tias/android-busybox-ndk/tree/master/patches

I would love to see the ideas behind these patches integrated, so that a 
standard busybox build can be used in the many android open-source 
projects that depend on it (and currently use a statically built 
third-party blob).


However, I am unfamiliar with the coding practices of the busybox 
community, and many of these patches were written to fix the build and 
not necessarily to get merged upstream.
I consider my work in collecting these patches as just a first step.
Hence, I would like to solicit feedback on what can and can not &lt;/pre&gt;</description>
    <dc:creator>Tias</dc:creator>
    <dc:date>2012-05-21T22:03:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36242">
    <title>[PATCH] Allow XZ streaming format in tar.</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36242</link>
    <description>&lt;pre&gt;Here's a patch that will allow tar to uncompress XZ file formats when it 
can't properly detect XZ data formats when the input data comes from the 
standard input.  I have added the (-J) option to force tar to recognize 
XZ file format. Without this patch, it won't work with data streams.

Example: wget -O - http://192.168.0.1/1.xz | tar -xvJf -

diff -uNr busybox-original/archival/tar.c busybox/archival/tar.c
--- busybox-original/archival/tar.c     2012-05-21 00:19:38.876360998 -0500
+++ busybox/archival/tar.c      2012-05-21 00:05:08.299222265 -0500
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -693,6 +693,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
  //usage:       "-[" IF_FEATURE_TAR_CREATE("c") "xt"
  //usage:       IF_FEATURE_SEAMLESS_Z("Z")
  //usage:       IF_FEATURE_SEAMLESS_GZ("z")
+//usage:       IF_FEATURE_SEAMLESS_XZ("J")
  //usage:       IF_FEATURE_SEAMLESS_BZ2("j")
  //usage:       IF_FEATURE_SEAMLESS_LZMA("a")
  //usage:       IF_FEATURE_TAR_CREATE("h")
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -719,6 +720,9 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
  //usage:       IF_FEATURE_SEAMLESS_GZ(
  //usage:     "\n       z       (De)compress using gzip"
  &lt;/pre&gt;</description>
    <dc:creator>Boris Reisig</dc:creator>
    <dc:date>2012-05-21T19:24:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36223">
    <title>/sbin/reboot does SIGINT and not SIGTERM?</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36223</link>
    <description>&lt;pre&gt;I was trying to get rcK to run to shutdown gracefully and noticed that
the inittab should use SHUTDOWN for the action.  If I run /sbin/reboot
this causes a SIGINT, which doesn't cause the rcK to get run.  If I do
kill -15 1 then rcK gets run and I get a reboot.

Is this the intended action for /sbin/reboot or am I doing something
wrong here?  poweroff also doesn't do SIGTERM for init.

I'm using Busybox 1.19.4.  My relevant inittab lines are:

# Stuff to do for the 3-finger salute
::ctrlaltdel:/sbin/reboot

# Stuff to do before rebooting
::shutdown:/etc/init.d/rcK
::shutdown:/bin/umount -a -r
::shutdown:/sbin/swapoff -a

&lt;/pre&gt;</description>
    <dc:creator>Michael J. Hammel</dc:creator>
    <dc:date>2012-05-17T03:06:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36221">
    <title>[PATCH] ext4 detection in blkid applet</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36221</link>
    <description>&lt;pre&gt;Available here :

http://review.cyanogenmod.com/16046

--
Tanguy Pruvot                         email : tanguy.pruvot&amp;lt; at &amp;gt;gmail.com
&lt;/pre&gt;</description>
    <dc:creator>Tanguy Pruvot</dc:creator>
    <dc:date>2012-05-15T23:22:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36220">
    <title>[PATCH] Fix link time error for functions calling check_signature16()</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36220</link>
    <description>&lt;pre&gt;From: Anthony G. Basile &amp;lt;blueness&amp;lt; at &amp;gt;gentoo.org&amp;gt;

archival/libarchive/decompress_bunzip2.c, decompress_gunzip.c and
decompress_uncompress.c all make calls to check_signature16() which
is defined in open_transformer.c.  However, Kbuild.src does not
properly respect this dependency leading to a link time error.
This patch addresses this problem.

Signed-off-by: Anthony G. Basile &amp;lt;blueness&amp;lt; at &amp;gt;gentoo.org&amp;gt;
---
 archival/libarchive/Kbuild.src |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/archival/libarchive/Kbuild.src b/archival/libarchive/Kbuild.src
index e2134be..72dc733 100644
--- a/archival/libarchive/Kbuild.src
+++ b/archival/libarchive/Kbuild.src
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -39,17 +39,17 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; DPKG_FILES:= \
 INSERT
 
 lib-$(CONFIG_AR)                        += get_header_ar.o unpack_ar_archive.o
-lib-$(CONFIG_BUNZIP2)                   += decompress_bunzip2.o
+lib-$(CONFIG_BUNZIP2)                   += open_transformer.o decompress_bunzip2.o
 lib-$(CONFIG_UNLZMA)                    += decompress_unlzma.o
&lt;/pre&gt;</description>
    <dc:creator>Anthony G. Basile</dc:creator>
    <dc:date>2012-05-15T11:36:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36217">
    <title>mdev automount questions</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36217</link>
    <description>&lt;pre&gt;  This really should be a separate topic.  Sorry for derailing the wifi
question.

On Sun, May 13, 2012 at 12:16:37PM +0200, Laurent Bercot wrote


  A couple of options...

1) The comments in /lib/mdev/usbdisk_link say
# NOTE: since mdev -s only provide $MDEV, don't depend on any hotplug vars.
Can I use the lack of an ACTION var to assume that this call is from
"mdev -s" (i.e. bootup), whereas if ACTION is present, assume that it's
a hotplug
if [ "X${ACTION}" == "X" ]; then
   assume it's a hard drive coming up at boot time (mdev -s)
else
   it's from the command in /proc/sys/kernel/hotplug (userspace hotplug)
fi

2) Get info from /sys

cat /sys/block/sda/removable
0

cat /sys/block/sdb/removable 
1

&lt;/pre&gt;</description>
    <dc:creator>Walter Dnes</dc:creator>
    <dc:date>2012-05-14T07:45:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36213">
    <title>MAC address deny in udhcpd</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36213</link>
    <description>&lt;pre&gt;In the example udhcpd.conf it shows how to declare a static IP address 
for a specific MAC address:

|   # Static leases map
   static_lease 00:60:08:11:CE:4E 192.168.0.54
|

You can also use a MAC address range by using the wildcard:

|   static_lease 00:21:5a:e7:xx:xx 10.10.1.254

But it doesn't seem possible to deny an IP address to a MAC address or range, which is possible in dhcpd.conf. I was thinking this could be done in the same way static leases are done:
||   static_lease 00:21:5a:e7:xx:xx 0.0.0.0|
Alternatively we could add a new command:
   deny|00:21:5a:e7:xx:xx|

What are your thoughts?

|Tom

|
&lt;/pre&gt;</description>
    <dc:creator>Tom Isaacson</dc:creator>
    <dc:date>2012-05-14T00:08:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36209">
    <title>Possible change to /etc/mdev.conf default?</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36209</link>
    <description>&lt;pre&gt;  I was spelunking through my /etc/mdev.conf, looking at the syntax,
when something occured to me looking at...

sr[0-9]*        root:cdrom 660 &amp;lt; at &amp;gt;ln -sf $MDEV cdrom

  What happens if you have multiple devices, e.g. "sr0" and "sr1"?  Does
the system get confused?  Would the following work better...

sr[0-9]*        root:cdrom 660 &amp;lt; at &amp;gt;ln -sf $MDEV cdrom%1

&lt;/pre&gt;</description>
    <dc:creator>Walter Dnes</dc:creator>
    <dc:date>2012-05-13T22:14:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36201">
    <title>Yank multiple character bug in VI</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36201</link>
    <description>&lt;pre&gt;When editing a file, typing #yl where # is &amp;gt; 1, only 1 byte is yanked.  Same
is true for #dl except that only 1 character is deleted.  Replacing "l" with
"h" works for yanking/deleting X amount of characters left of the cursor.

vim-tiny 2:7.3.429-2 in debian works as expected.

Tested with busybox v1.20.0 and
git with commit a5ee090e8651692545514a81a16c6cde3a2dc577 (Which was the
latest when I cloned today)

&lt;/pre&gt;</description>
    <dc:creator>Wakko Warner</dc:creator>
    <dc:date>2012-05-12T14:24:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36199">
    <title>mdev with USB wifi adapters</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36199</link>
    <description>&lt;pre&gt;I've googled on this but didn't find much, though there was a long
discussion in the BusyBox archives on the extension of mdev event
variables (and other things) that helped.

I'm looking at using mdev to recognize a USB wifi adapter at boot time.
I've finally figured out that a line like the following will at least
get my handler script called:

usb.* - - &amp;lt; at &amp;gt;/usr/bin/spew.sh

(spew.sh is just a script echoing the event variables passed to it)

Using a device such as "net.*" doesn't seem to work for USB connected
wifi adapters.  I believe using event variables should also work but the
output from spew.sh showed that none of them were getting set except
MDEV, SUBSYSTEM and PWD.  I couldn't find a regex for SUBSYTEM that
identified just the wifi adapter. 

I was thinking the best way to use this would be to have a handler
script that uses the MDEV variable to identify the USB bus and device or
major/minor numbers, then use those to find the vendor and product ID
and match those with a configuration file to deter&lt;/pre&gt;</description>
    <dc:creator>Michael J. Hammel</dc:creator>
    <dc:date>2012-05-11T20:02:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36185">
    <title>Massive eh_frame bloat in busybox (stripped)</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36185</link>
    <description>&lt;pre&gt;The busybox build system first builds busybox_unstripped with debug
info, then uses the strip utility to obtain a non-debug busybox binary
that's not so bloated. However, ever since GCC switched to using
DWARF2 for debugging data, it puts a .eh_frame section in the output
binary which is NOT stripped by the strip command. See:

$ size -A busybox
section       size        addr
.init           11   134512788
.text       533493   134512800
.fini            6   135046293
.rodata     146886   135046304
.eh_frame    72232   135193192
...

It's possible that strip -R .eh_frame could be used to remove this
bloat, but see my bug report here:

http://sourceware.org/bugzilla/show_bug.cgi?id=14037

I'm fairly confident this bug in strip can't break static binaries,
but I'm unsure if it's safe for dynamic-linked ones. Some checking
should definitely be done if it's going to be added to busybox's strip
command...

Rich
&lt;/pre&gt;</description>
    <dc:creator>Rich Felker</dc:creator>
    <dc:date>2012-05-10T02:44:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36173">
    <title>[PATCH] syslogd should use _PATH_LOG when available</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36173</link>
    <description>&lt;pre&gt;---
 sysklogd/syslogd.c |   11 +++++++----
 1 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/sysklogd/syslogd.c b/sysklogd/syslogd.c
index fc380d9..f7fbc16 100644
--- a/sysklogd/syslogd.c
+++ b/sysklogd/syslogd.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -55,6 +55,9 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 #define SYSLOG_NAMES_CONST
 #include &amp;lt;syslog.h&amp;gt;
 */
+#ifndef _PATH_LOG
+#define _PATH_LOG"/dev/log"
+#endif
 
 #include &amp;lt;sys/un.h&amp;gt;
 #include &amp;lt;sys/uio.h&amp;gt;
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -768,8 +771,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static NOINLINE int create_socket(void)
 
 /* Unlink old /dev/log or object it points to. */
 /* (if it exists, bind will fail) */
-strcpy(sunx.sun_path, "/dev/log");
-dev_log_name = xmalloc_follow_symlinks("/dev/log");
+strcpy(sunx.sun_path, _PATH_LOG);
+dev_log_name = xmalloc_follow_symlinks(_PATH_LOG);
 if (dev_log_name) {
 safe_strncpy(sunx.sun_path, dev_log_name, sizeof(sunx.sun_path));
 free(dev_log_name);
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -778,7 +781,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static NOINLINE int create_socket(void)
 
 sock_fd = xsocket(AF_UNIX, SOCK_DGRAM, 0);
 xbind(sock_fd, (struct sockaddr *) &amp;amp;sunx, sizeof(sunx));
-chmod("/&lt;/pre&gt;</description>
    <dc:creator>Cédric Cabessa</dc:creator>
    <dc:date>2012-05-08T14:51:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36172">
    <title>[PATCH] Only write leasefile if anything changed</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36172</link>
    <description>&lt;pre&gt;Also, move the check for changed leases to before the select(), so
changes will occur immediately instead only after select() returns the
next time.

Signed-off-by: Phil Sutter &amp;lt;phil.sutter&amp;lt; at &amp;gt;viprinet.com&amp;gt;
Signed-off-by: Nico Erfurth &amp;lt;nico.erfurth&amp;lt; at &amp;gt;viprinet.com&amp;gt;
---
 networking/udhcp/dhcpd.c |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/networking/udhcp/dhcpd.c b/networking/udhcp/dhcpd.c
index dd55e70..356c81f 100644
--- a/networking/udhcp/dhcpd.c
+++ b/networking/udhcp/dhcpd.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -298,6 +298,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int udhcpd_main(int argc UNUSED_PARAM, char **argv)
 {
 int server_socket = -1, retval, max_sock;
 uint8_t *state;
+uint8_t leases_changed = 0;
 unsigned timeout_end;
 unsigned num_ips;
 unsigned opt;
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -389,6 +390,11 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int udhcpd_main(int argc UNUSED_PARAM, char **argv)
 uint32_t static_lease_nip;
 struct dyn_lease *lease, fake_lease;
 
+if (leases_changed) {
+write_leases();
+leases_changed = 0;
+}
+
 if (server_socket &amp;lt; 0) {
 server_socket = udhcp_liste&lt;/pre&gt;</description>
    <dc:creator>Phil Sutter</dc:creator>
    <dc:date>2012-05-08T14:09:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36167">
    <title>(unknown)</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36167</link>
    <description>&lt;pre&gt;Hi,


Some thoughts on the defaults:

1) OTP should not be enabled by default in bb. It should require an
active config, like CONFIG_FEATURE_LOGIN_OTP. (I guess all agree on
this one)

2) Even when compiled with OTP I think it should be easy to disable
OTP for some users. Some examples:

    # cat /etc/otp
    $UID1:$SHAREDSECRET:$DELIVERY
    $UID2:$SHAREDSECRET:

   a) $UID1 will get the PIN delivered by the configured $DELIVERY.
   b) $UID2 will get the PIN within login (the default).
   c) $UID3 will not benefit from OTP at all (not present in /etc/otp).

3) When compiled with OTP, default for the special case with no
/etc/otp could be argued, but here are my 2 cents:
   a) No /etc/opt =&amp;gt; enable the default for all users (PIN in login)
   b) Empty /etc/otp =&amp;gt; OTP disabled for all users (consistent with 2)

/Sven
&lt;/pre&gt;</description>
    <dc:creator>Sven-Göran Bergh</dc:creator>
    <dc:date>2012-05-08T06:59:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36163">
    <title>Bug in busybox sed - this one is real</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36163</link>
    <description>&lt;pre&gt;$ echo hello | busybox sed 's/l*/&amp;lt; at &amp;gt;/g'
&amp;lt; at &amp;gt;he&amp;lt; at &amp;gt;o
$ echo hello | sed 's/l*/&amp;lt; at &amp;gt;/g'
&amp;lt; at &amp;gt;h&amp;lt; at &amp;gt;e&amp;lt; at &amp;gt;o&amp;lt; at &amp;gt;

The latter is of course correct. My naive diagnosis is that Busybox
sed's 'g' option has an off-by-one error in its next-match search,
i.e. advanced by one character too many before searching for the next
match.

Rich
&lt;/pre&gt;</description>
    <dc:creator>Rich Felker</dc:creator>
    <dc:date>2012-05-08T03:12:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36152">
    <title>[BUG?] busybox sed fails to process ncurses scripts</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36152</link>
    <description>&lt;pre&gt;when compiling ncurses 5.9 with busybox sed,
it'll produce invalid C files

../ncurses/lib_gen.c:27:3: error: expected identifier or '(' before 'int'

the file contains:
/* DO NOT EDIT THIS FILE BY HAND!
* It is generated by ./base/MKlib_gen.sh generated. */

the line that errs is
* int waddch(stdscr,const chtype z) { ... }

which clearly is invalid C

it is generated by ncurses-5.9/ncurses/./base/MKlib_gen.sh which does a 
lot of sed...

since i'm not very familiar with sed, it would be nice if someone could 
look at the issue.

using gnu sed instead fixes the build.

--JS
&lt;/pre&gt;</description>
    <dc:creator>John Spencer</dc:creator>
    <dc:date>2012-05-07T04:16:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/36136">
    <title>OTP feature for /bin/login</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/36136</link>
    <description>&lt;pre&gt;Hello

I have prepared a OTP implementation for /bin/login, where a password
can optionally be replaced by an MOTP (md5 of epoch+pin+shared secret)
if ENABLE_FEATURE_LOGINOTP is defined.

This could be useful for example when using telnetd. The code can
easily be tweaked to support other things besides MOTP.

Shall I just post the code on the list? (it's a full replacement of
correct_password.c, GPLv2)

Guylhem
&lt;/pre&gt;</description>
    <dc:creator>Guylhem</dc:creator>
    <dc:date>2012-05-04T22:37:28</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.busybox">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.busybox</link>
  </textinput>
</rdf:RDF>

