<?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/37778"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37775"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37774"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37765"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37757"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37754"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37753"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37720"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37718"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37716"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37714"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37705"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37704"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37700"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37692"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37688"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37687"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37684"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37683"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.busybox/37680"/>
      </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/37778">
    <title>UBI patches</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37778</link>
    <description>&lt;pre&gt;I haven't gotten any further feedback from any developers on my proposed 
UBI feature enhancement patches I resubmitted with Mike's requested 
changes a few weeks ago. If there's any developer who would like to 
commit them, that would be great. If there's any developer who would be 
willing to commit them with any other updates or changes, please let me 
know what you would like to see. Otherwise, I guess I will just keep 
them in my local fork and stop trying to contribute them upstream.

Thanks…
&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-06-19T18:47:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37775">
    <title>[PATCH] lsof: correct check for symbolic link</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37775</link>
    <description>&lt;pre&gt;# HG changeset patch
# User Thomas De Schampheleire &amp;lt;thomas.de_schampheleire&amp;lt; at &amp;gt;alcatel-lucent.com&amp;gt;
# Date 1371558718 -7200
# Node ID 38fb4edf4bb684a9a14ded6c15181e9d490d83ef
# Parent  77208178d3ef7ac035f10e5b6e0859be170ff788
lsof: correct check for symbolic link

Busybox lsof used the d_type field of a 'struct dirent' to verify whether the
entry is a symbolic link. This field, however, is not portable. On at least
one board [1] I have seen, that field is 0, and the check fails even though
the entry is a link.
This patch replaces the check on d_type with a call to lstat and a subsequent
check S_ISLNK. This should work in all cases, at the cost of the extra lstat
call.

[1] A MIPS-based board with glibc 2.9, Linux 2.6.32.27.

Signed-off-by: Thomas De Schampheleire &amp;lt;thomas.de.schampheleire&amp;lt; at &amp;gt;gmail.com&amp;gt;

---
 procps/lsof.c |  9 +++++++--
 1 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/procps/lsof.c b/procps/lsof.c
--- a/procps/lsof.c
+++ b/procps/lsof.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -61,8 +61,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int lsof_main(int argc UNUSE&lt;/pre&gt;</description>
    <dc:creator>Thomas De Schampheleire</dc:creator>
    <dc:date>2013-06-19T16:52:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37774">
    <title>status of FTP get/put using ipv6?</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37774</link>
    <description>&lt;pre&gt;Hi all:

I'm new to the busybox world, and am using it on an Android device for
FTP get/put testing.  I noticed there is a patch by Kev Kitchens that
will support "EPSV" mode needed for IPv6 FTP transfers. 

[PATCH] networking/ftpgetput.c: Make ftp client code RFC compliant for IPv4 and IPv6

Will this patch be going into an official distribution soon?  I'm hoping to avoid 
compiling a custom version using the patch, as I have no experience in that area, but 
I'll make plans to do so if IPv6 FTP will not be "officially" supported anytime soon.

thanks for the advice,

Mike Harrison
&lt;/pre&gt;</description>
    <dc:creator>Harrison, Michael J (Mike</dc:creator>
    <dc:date>2013-06-19T15:43:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37765">
    <title>Has anybody seen Denys in the past 3 weeks?</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37765</link>
    <description>&lt;pre&gt;Wondering. I don't have contact info for him other than email, and he  
vanished somewhat abruptly from the list. No git checkins since then  
either. Never responded to my ping about a #busybox channel on freenode  
(not that he ever did irc before)...

Vacation, do you think?

Rob
&lt;/pre&gt;</description>
    <dc:creator>Rob Landley</dc:creator>
    <dc:date>2013-06-15T06:04:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37757">
    <title>Issue with tar (Busybox 1.20.2): unknown file type</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37757</link>
    <description>&lt;pre&gt;Hi,

I'm building several different busybox 1.20.2 binaries with various applets, to be run onto a tiny MIPS embedded system.
(I'm cross compiling with aboriginal system images and assorted cross tools).
Busybox utils I build are setup from makeallnoconfig and then adding applets I want: they are therefore dynamically linked.
Applets I built so far are things like gzip, wget, find, cat, echo, du, ...
They all work as expected on my target.

I decided to do tar applet, with all its options.

It compiles, and work on my aboriginal system image, but fails on target with message "unknown file type".
I tried with tar options off: same issue.


I tried same config but static build: it works!
However I find the error message strange would my target really miss a library...
How to find which eventual one?
Would adding another magic applet/option solve the issue?


Any hint, suggestion to fix this, or alternative?
As my embedded system is really constrained in storage, I'd rather use dynamically linked version obviou&lt;/pre&gt;</description>
    <dc:creator>piquemal michel</dc:creator>
    <dc:date>2013-06-11T20:45:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37754">
    <title>NFS mount not backgrounding if host/network unreachable</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37754</link>
    <description>&lt;pre&gt;Hello!

I found that mount will not go to the background and retry mounting
if mounting a NFS share with the "bg" options set fails with an error 
other than ECONNREFUSED.

Why does BB mount only go to the background in that case?
Is there a specific reason for that?

My problem is, that my machines try to mount a NFS share when they're 
booting up.
If the remote host or the network is unreachable during that time,
mount will fail (which is why I use the bg option) and never retry (bad).

I found this in BusyBox 1.14.4 but it's still present in the current 
snapshot.
The problematic code is at (snapshot) util-linux/mount.c:1580.

Out of my naivety: Shouldn't mount retry in case of *any* error?


Regards,

Andreas
&lt;/pre&gt;</description>
    <dc:creator>Andreas Wehrmann</dc:creator>
    <dc:date>2013-06-10T13:46:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37753">
    <title>taskset fails on big endian system (mips)</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37753</link>
    <description>&lt;pre&gt;In busybox/miscutils/taskset.c the function from_cpuset has following
logic for big endian systems:

---
#if BB_BIG_ENDIAN
    /* For big endian, it means LAST bits */
    if (CPU_SETSIZE &amp;lt; sizeof(long))
        p += CPU_SETSIZE - sizeof(int);
    else if (CPU_SETSIZE &amp;lt; sizeof(long long))
        p += CPU_SETSIZE - sizeof(long);
    else
        p += CPU_SETSIZE - sizeof(long long);
#endif
---

First issue is that CPU_SETSIZE is in bits, while this calculation
uses it as bytes, so we overwrite part of the stack from the calling
function.

Another issue on the platform I'm running it on, is that CPU_SETSIZE
is 1024 bits (128 bytes). This logic here takes the last "long long"
out of the structure, but the result is actually stored in the first
few bytes of the structure. I'm not sure if all big endian systems
follow this logic?!

The "fancy feature" implementation on the other hand, works fine.
&lt;/pre&gt;</description>
    <dc:creator>Karl Vogel</dc:creator>
    <dc:date>2013-06-10T07:21:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37720">
    <title>[PATCH] ubi_tools: enhance -s option to allow size multiplier to match mtd-utils</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37720</link>
    <description>&lt;pre&gt;Signed-off-by: Paul B. Henson &amp;lt;henson&amp;lt; at &amp;gt;acm.org&amp;gt;
---
 miscutils/ubi_tools.c |   33 ++++++++++++++++++++++++---------
 1 files changed, 24 insertions(+), 9 deletions(-)

diff --git a/miscutils/ubi_tools.c b/miscutils/ubi_tools.c
index f09be8c..6b5d384 100644
--- a/miscutils/ubi_tools.c
+++ b/miscutils/ubi_tools.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -103,7 +103,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 //usage:     "\n-n VOLIDVolume ID, if not specified, it"
 //usage:     "\nwill be assigned automatically"
 //usage:     "\n-N NAMEVolume name"
-//usage:     "\n-s SIZESize in bytes"
+//usage:     "\n-s SIZESize in bytes, kilobytes (KiB),"
+//usage:     "\nmegabytes (MiB), or gigabytes (GiB)"
 //usage:     "\n-t TYPEVolume type (static|dynamic)"
 //usage:
 //usage:#define ubirmvol_trivial_usage
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -117,15 +118,23 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 //usage:#define ubirsvol_full_usage "\n\n"
 //usage:       "Resize UBI volume\n"
 //usage:     "\n-n VOLIDVolume ID to resize"
-//usage:     "\n-s SIZESize in bytes"
+//usage:     "\n-s SIZESize in bytes, kilobytes (KiB),"
+//usage:     "\n&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-06-03T01:11:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37718">
    <title>[PATCH] ubimkvol: add -m option to create volume of maximum size</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37718</link>
    <description>&lt;pre&gt;Signed-off-by: Paul B. Henson &amp;lt;henson&amp;lt; at &amp;gt;acm.org&amp;gt;
---
 miscutils/ubi_tools.c |   51 +++++++++++++++++++++++++++++++++++++++++++-----
 1 files changed, 45 insertions(+), 6 deletions(-)

diff --git a/miscutils/ubi_tools.c b/miscutils/ubi_tools.c
index f6dfcae..f09be8c 100644
--- a/miscutils/ubi_tools.c
+++ b/miscutils/ubi_tools.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -95,10 +95,11 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 //usage:     "\n-d UBI_NUMUBI device number"
 //usage:
 //usage:#define ubimkvol_trivial_usage
-//usage:       "UBI_DEVICE -N NAME -s SIZE"
+//usage:       "UBI_DEVICE -N NAME [-s SIZE | -m]"
 //usage:#define ubimkvol_full_usage "\n\n"
 //usage:       "Create UBI volume\n"
 //usage:     "\n-a ALIGNMENTVolume alignment (default 1)"
+//usage:     "\n-mSet volume size to maximum available"
 //usage:     "\n-n VOLIDVolume ID, if not specified, it"
 //usage:     "\nwill be assigned automatically"
 //usage:     "\n-N NAMEVolume name"
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -141,11 +142,19 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int ubi_tools_main(int argc UNUSED_PARAM, char **argv)
 int alignment = 1;
 char *type = NULL;
 
-opt&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-06-03T00:48:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37716">
    <title>[PATCH] Convert sscanf to preferred xstrtou conversion.</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37716</link>
    <description>&lt;pre&gt;Signed-off-by: Paul B. Henson &amp;lt;henson&amp;lt; at &amp;gt;acm.org&amp;gt;
---
 miscutils/ubi_tools.c |   20 ++++++++++++++------
 1 files changed, 14 insertions(+), 6 deletions(-)

diff --git a/miscutils/ubi_tools.c b/miscutils/ubi_tools.c
index dd99a44..f6dfcae 100644
--- a/miscutils/ubi_tools.c
+++ b/miscutils/ubi_tools.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -234,16 +234,24 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int ubi_tools_main(int argc UNUSED_PARAM, char **argv)
 ssize_t len;
 char *input_data;
 
-// Make assumption that device not is in normal format.
-// Removes need for scanning sysfs tree as full libubi does
-if (sscanf(ubi_ctrl, "/dev/ubi%u_%u", &amp;amp;ubinum, &amp;amp;volnum) != 2)
+// Make assumption that device node is in normal format
+// (/dev/ubi%d_%d), removes need for scanning sysfs
+// tree as full libubi does
+if (strncmp(ubi_ctrl, "/dev/ubi", 8) != 0 ||
+    (input_data = strchr(ubi_ctrl+8, '_')) == NULL)
 bb_error_msg_and_die("%s volume node not in correct format", "UBI");
+// temporarily tokenize for parsing
+*input_data = '\0';
+ubinum = xstrtou(ubi_&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-06-02T19:49:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37714">
    <title>[PATCH] Convert sscanf to preferred xstrtou conversion.</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37714</link>
    <description>&lt;pre&gt;Signed-off-by: Paul B. Henson &amp;lt;henson&amp;lt; at &amp;gt;acm.org&amp;gt;
---
 miscutils/ubi_tools.c |   17 ++++++++++++-----
 1 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/miscutils/ubi_tools.c b/miscutils/ubi_tools.c
index dd99a44..9e3db1e 100644
--- a/miscutils/ubi_tools.c
+++ b/miscutils/ubi_tools.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -234,16 +234,23 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int ubi_tools_main(int argc UNUSED_PARAM, char **argv)
 ssize_t len;
 char *input_data;
 
-// Make assumption that device not is in normal format.
-// Removes need for scanning sysfs tree as full libubi does
-if (sscanf(ubi_ctrl, "/dev/ubi%u_%u", &amp;amp;ubinum, &amp;amp;volnum) != 2)
+// Make assumption that device node is in normal format
+// (/dev/ubi%d_%d), removes need for scanning sysfs
+// tree as full libubi does
+if (strncmp(ubi_ctrl, "/dev/ubi", 8) != 0 ||
+    (input_data = strchr(ubi_ctrl+8, '_')) == NULL)
 bb_error_msg_and_die("%s volume node not in correct format", "UBI");
+// temporarily tokenize for parsing
+*input_data = '\0';
+ubinum = xstrtou(ubi_ctr&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-06-02T19:49:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37705">
    <title>[PATCH] man: use less as default pager and parse DEFINE lines defining pager</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37705</link>
    <description>&lt;pre&gt;man.config can define lines such as
DEFINE         pager   less -s

this patch parses them, additionally it always sets pager to less 
instead of more.

Signed-off-by: John Spencer &amp;lt;maillist-busybox&amp;lt; at &amp;gt;barfooze.de&amp;gt;

_______________________________________________
busybox mailing list
busybox&amp;lt; at &amp;gt;busybox.net
http://lists.busybox.net/mailman/listinfo/busybox&lt;/pre&gt;</description>
    <dc:creator>John Spencer</dc:creator>
    <dc:date>2013-06-02T10:51:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37704">
    <title>[PATCH] man: find posix man pages</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37704</link>
    <description>&lt;pre&gt;the posix manpages ( 
http://www.kernel.org/pub/linux/docs/man-pages/man-pages-posix/man-pages-posix-2003-a.tar.xz 
) are placed in man0p man1p and man3p.

Signed-off-by: John Spencer &amp;lt;maillist-busybox&amp;lt; at &amp;gt;barfooze.de&amp;gt;

_______________________________________________
busybox mailing list
busybox&amp;lt; at &amp;gt;busybox.net
http://lists.busybox.net/mailman/listinfo/busybox&lt;/pre&gt;</description>
    <dc:creator>John Spencer</dc:creator>
    <dc:date>2013-06-02T11:10:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37700">
    <title>less with disabled options show help for them</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37700</link>
    <description>&lt;pre&gt;Hi!

I use busybox 1.19.4 on OpenWRT 12.09 and noticed that search and the
-M options do not work.

I guess they have been not compiled in, to save space.

Can anyone confirm, that in such case the help text (less -h) still
shows those options (-M and -I) ?

If so, please consider removing them together with the actual function
when configured so.

Regards,
David
&lt;/pre&gt;</description>
    <dc:creator>David Balažic</dc:creator>
    <dc:date>2013-06-01T13:08:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37692">
    <title>Truncated thread names in pstree</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37692</link>
    <description>&lt;pre&gt;Hi,

I noticed that thread names are truncated by one character (to 14 
characters instead of 15), the below patch fixes the issue. (The 
attached patch has proper whitespaces !)

--- busybox-1.21.0/procps/pstree.c.orig 2013-06-01 02:27:14.008530872 +0200
+++ busybox-1.21.0/procps/pstree.c      2013-06-01 02:31:36.483537110 +0200
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -342,7 +342,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
  static void handle_thread(const char *comm, pid_t pid, pid_t ppid, uid_t uid)
  {
         char threadname[COMM_LEN + 2];
-       sprintf(threadname, "{%.*s}", COMM_LEN - 2, comm);
+       sprintf(threadname, "{%.*s}", COMM_LEN - 1, comm);
         add_proc(threadname, pid, ppid, uid/*, 1*/);
  }
  #endif

&lt;/pre&gt;</description>
    <dc:creator>Dag Wieers</dc:creator>
    <dc:date>2013-06-01T00:34:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37688">
    <title>[PATCH] ubi_tools: enhance -s option to allow size multiplier to match mtd-utils</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37688</link>
    <description>&lt;pre&gt;Signed-off-by: Paul B. Henson &amp;lt;henson&amp;lt; at &amp;gt;acm.org&amp;gt;
---
 miscutils/ubi_tools.c |   57 +++++++++++++++++++++++++++++++++++++++++-------
 1 files changed, 48 insertions(+), 9 deletions(-)

diff --git a/miscutils/ubi_tools.c b/miscutils/ubi_tools.c
index 6cb7cd5..87dfab0 100644
--- a/miscutils/ubi_tools.c
+++ b/miscutils/ubi_tools.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -103,7 +103,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 //usage:     "\n-n VOLIDVolume ID, if not specified, it"
 //usage:     "\nwill be assigned automatically"
 //usage:     "\n-N NAMEVolume name"
-//usage:     "\n-s SIZESize in bytes"
+//usage:     "\n-s SIZESize in bytes, kilobytes (KiB),"
+//usage:     "\nmegabytes (MiB), or gigabytes (GiB)"
 //usage:     "\n-t TYPEVolume type (static|dynamic)"
 //usage:
 //usage:#define ubirmvol_trivial_usage
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -117,15 +118,45 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 //usage:#define ubirsvol_full_usage "\n\n"
 //usage:       "Resize UBI volume\n"
 //usage:     "\n-n VOLIDVolume ID to resize"
-//usage:     "\n-s SIZESize in bytes"
+//usage:     "\n-s SIZESize in bytes, kilobytes (KiB),"
+//u&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-05-29T01:17:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37687">
    <title>[PATCH] ubimkvol: add -m option to create volume of maximum size</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37687</link>
    <description>&lt;pre&gt;Signed-off-by: Paul B. Henson &amp;lt;henson&amp;lt; at &amp;gt;acm.org&amp;gt;
---
 miscutils/ubi_tools.c |   45 +++++++++++++++++++++++++++++++++++++++------
 1 files changed, 39 insertions(+), 6 deletions(-)

diff --git a/miscutils/ubi_tools.c b/miscutils/ubi_tools.c
index dd99a44..6cb7cd5 100644
--- a/miscutils/ubi_tools.c
+++ b/miscutils/ubi_tools.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -95,10 +95,11 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 //usage:     "\n-d UBI_NUMUBI device number"
 //usage:
 //usage:#define ubimkvol_trivial_usage
-//usage:       "UBI_DEVICE -N NAME -s SIZE"
+//usage:       "UBI_DEVICE -N NAME [-s SIZE | -m]"
 //usage:#define ubimkvol_full_usage "\n\n"
 //usage:       "Create UBI volume\n"
 //usage:     "\n-a ALIGNMENTVolume alignment (default 1)"
+//usage:     "\n-mSet volume size to maximum available"
 //usage:     "\n-n VOLIDVolume ID, if not specified, it"
 //usage:     "\nwill be assigned automatically"
 //usage:     "\n-N NAMEVolume name"
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -141,11 +142,19 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int ubi_tools_main(int argc UNUSED_PARAM, char **argv)
 int alignment = 1;
 char *type = NULL;
 
-opt_co&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-05-28T21:35:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37684">
    <title>#busybox channel on freenode.</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37684</link>
    <description>&lt;pre&gt;People have been gradually wandering from #uclibc to #busybox on  
freenode (due ot the incessant git-commit spam from the bot on uclibc  
about buildroot commits and such, which made everybody stop checking  
the tab).

I finally got around to registering the channel. Denys: glad to op your  
freenode handle if you'll tell me what it is. Up to you if you want to  
mention #busybox on irc.freenode.net on the web page...

Anyway, thing.

(Back to banging on toybox...)

Rob
&lt;/pre&gt;</description>
    <dc:creator>Rob Landley</dc:creator>
    <dc:date>2013-05-31T17:21:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37683">
    <title>contributing patches?</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37683</link>
    <description>&lt;pre&gt;I haven't seen any feedback on the potential ubi feature additions I 
sent to the list last weekend, is there any other policy/procedure I 
should follow for submitting them for consideration other than just 
posting them to the list?

Thanks much…
&lt;/pre&gt;</description>
    <dc:creator>Paul B. Henson</dc:creator>
    <dc:date>2013-05-31T19:54:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37680">
    <title>Thank you for not using autoconf</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37680</link>
    <description>&lt;pre&gt;I've just had a really pleasant experience cross compiling busybox for our
embedded PowerPC platform. It reminded me how you can point C compilers at
C source and get the right output. It even seemed to do something sensible
about libm (temporarily being) missing.

Thank you for making this work and please don't let anyone tell you to
start using GNU autoconf and friends. They're absolute crap for most
packages when cross building.

Jon
&lt;/pre&gt;</description>
    <dc:creator>Jon Schneider</dc:creator>
    <dc:date>2013-05-31T14:43:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.busybox/37679">
    <title>recursive_action (and thus find) slow due to [l]stat()</title>
    <link>http://comments.gmane.org/gmane.linux.busybox/37679</link>
    <description>&lt;pre&gt;Conceptually, the find utility need not perform lstat on each filename
unless it's needed for matching criteria. However, find is implemented
based on libbb's recursive_action, which always performs stat or
lstat. This makes busybox's find excruciatingly slow compared to GNU
find.

I think the easiest way to fix this is to add an extra argument to
recursive_action so that the dirent d_type field can be passed, with
fallback code to call [l]stat when d_type is blank or the flags are
such that d_type is insufficient to determine the preferred action
(i.e. when the type is a symlink and symlinks are to be followed).

There may also be solutions that involve just trying an operation
(e.g. opendir), but I don't think these approaches handle the full
range of flags supported by recursive_action.

Comments? Anyone interested in looking into this?

Rich
&lt;/pre&gt;</description>
    <dc:creator>Rich Felker</dc:creator>
    <dc:date>2013-05-29T04:12:40</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>
