applet 'ls' - wrong sort by 'time' when using wildcards/globbing

2014-01-30 Thread Bastian Bittorf
unsure if this is normal, but today i stumbled over this:

root@box:~ ls -lt /dev/dsp*
crw-r--r--1 root root   14,   3 Jan 30 08:44 /dev/dsp
crw-r--r--1 root root   14,  19 Jan 30 08:44 /dev/dsp1

the exspected result was to get the 'newest' link on top.
normal sorting by time works:

root@box:~ ls -lt /var/log/
-rw-r--r--1 root root   134 Jan 30 08:45 ulogd.log
-rw-r--r--1 root root 0 Jan 30 08:04 lastlog
-rw-r--r--1 root root 0 Jan 30 08:04 wtmp

root@4900erHybrid-kueche:~ busybox --help | grep ^BusyBox
BusyBox v1.19.4 (2014-01-24 09:32:52 EST) multi-call binary.

bye, bastian
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox


Re: applet 'ls' - wrong sort by 'time' when using wildcards/globbing

2014-01-30 Thread Loïc Grenié
2014-01-30 Bastian Bittorf bitt...@bluebottle.com:
 unsure if this is normal, but today i stumbled over this:

 root@box:~ ls -lt /dev/dsp*
 crw-r--r--1 root root   14,   3 Jan 30 08:44 /dev/dsp
 crw-r--r--1 root root   14,  19 Jan 30 08:44 /dev/dsp1

 the exspected result was to get the 'newest' link on top.
 normal sorting by time works:

 I think you misread the time: date is Jan 30th for both, time is 8:44
  for both so there is no obvious order. What is before Jan is the minor
  number of the device.

Hope this helps,

 Loïc
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Re: applet 'ls' - wrong sort by 'time' when using wildcards/globbing

2014-01-30 Thread Bastian Bittorf
* Loïc Grenié loic.gre...@gmail.com [30.01.2014 11:05]:
  I think you misread the time: date is Jan 30th for both, time is 8:44

oops, sorry for the noise - you are right 8-) bye, bastian
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox


Re: [PATCH trivial] do not fail build if SIGPWR is not defined

2014-01-30 Thread Denys Vlasenko
Applied, thanks!

On Wed, Jan 29, 2014 at 9:40 AM, Michael Tokarev m...@tls.msk.ru wrote:
 Apparently, some *BSD variants (and maybe some other OSes) does not define
 SIGPWR signal.  So since commit 760fc6debcba8c, busybox fails to build on
 such platforms.  Fix this.

 Signed-off-By: Michael Tokarev m...@tls.msk.ru

 diff --git a/init/init.c b/init/init.c
 index d29328c..992a21e 100644
 --- a/init/init.c
 +++ b/init/init.c
 @@ -1135,7 +1137,9 @@ int init_main(int argc UNUSED_PARAM, char **argv)
 struct sigaction sa;

 bb_signals(0
 +#ifdef SIGPWR
 + (1  SIGPWR)  /* halt */
 +#endif
 + (1  SIGUSR1) /* halt */
 + (1  SIGTERM) /* reboot */
 + (1  SIGUSR2) /* poweroff */
 ___
 busybox mailing list
 busybox@busybox.net
 http://lists.busybox.net/mailman/listinfo/busybox
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox


[PATCH] Fix incorrect OS reporting in uname -o

2014-01-30 Thread Quinn Wood
On 2013-09-18 04:18, Laurent Bercot wrote:
   In 2000, I have built a server without GNU software just to contradict RMS,
 who was insisting that I should call my system GNU/Linux instead of Linux.
 Don't make me build a server without GNU *and* without Busybox just to
 contradict you. ;)

I'd be interested in hearing more about that process, possibly
somewhere less topical and gravediggy.
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox