On Tue, 13 Apr 2010 22:01:24 +0200, you wrote:
I started the port about three years ago, on 1.6.1.
I try to use this, but:
e:\vm\1busybox.exe
BusyBox v1.19.1_18_0-306-geb28f73.git (2011-01-16 17:56:02 ICT)
cat q.sh
ls -al RCDx86_11_02.iso
tail -c16384 RCDx86_11_02.iso | head -c 333 www
tail
Does only head have this problem ?
What libc do you use ?
re,
wh
Am 24.07.2011 14:27, schrieb Arkadiusz Patyk:
On Tue, 13 Apr 2010 22:01:24 +0200, you wrote:
I started the port about three years ago, on 1.6.1.
I try to use this, but:
e:\vm\1busybox.exe
BusyBox
Am 24.07.2011 18:40, schrieb Nguyen Thai Ngoc Duy:
On Sun, Jul 24, 2011 at 11:20 PM, Arkadiusz Patyk a...@areq.eu.org wrote:
On Sun, 24 Jul 2011 17:59:57 +0200, you wrote:
Does only head have this problem ?
What libc do you use ?
I used binary from:
On Tuesday 13 April 2010 15:01:24 Nguyen Thai Ngoc Duy wrote:
Hi,
I started the port about three years ago, on 1.6.1. Currently I'm
rebasing my work on master, but it will take some time before I could
submit anything. The old version based on 1.6.1 is on
On Wednesday 14 April 2010 11:37:45 Cathey, Jim wrote:
I would _really_ hate
to see them all crapped up with half-implemented junk that let
them build anyway, but didn't even try to let them run correctly.
That's like painting over rot.
+1
Making busybox work under mingw or on
On Wednesday 14 April 2010 15:42:41 Denys Vlasenko wrote:
On Tue, Apr 13, 2010 at 10:33 PM, Nguyen Thai Ngoc Duy
pclo...@gmail.com wrote:
On Wed, Apr 14, 2010 at 4:34 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
4. ash
~1000 lines, half of them to work around fork(). Not
On Sat, Apr 17, 2010 at 8:40 AM, Rob Landley r...@landley.net wrote:
On Tuesday 13 April 2010 15:01:24 Nguyen Thai Ngoc Duy wrote:
Hi,
I started the port about three years ago, on 1.6.1. Currently I'm
rebasing my work on master, but it will take some time before I could
submit anything. The
On Sat, Apr 17, 2010 at 8:52 AM, Rob Landley r...@landley.net wrote:
On Wednesday 14 April 2010 11:37:45 Cathey, Jim wrote:
I would _really_ hate
to see them all crapped up with half-implemented junk that let
them build anyway, but didn't even try to let them run correctly.
That's like
On Sat, Apr 17, 2010 at 8:40 AM, Rob Landley r...@landley.net wrote:
On Tuesday 13 April 2010 15:01:24 Nguyen Thai Ngoc Duy wrote:
Hi,
I started the port about three years ago, on 1.6.1. Currently I'm
rebasing my work on master, but it will take some time before I could
submit anything. The
Nguyen Thai Ngoc Duy schrieb:
On Sat, Apr 17, 2010 at 8:40 AM, Rob Landley r...@landley.net wrote:
On Tuesday 13 April 2010 15:01:24 Nguyen Thai Ngoc Duy wrote:
Hi,
I started the port about three years ago, on 1.6.1. Currently I'm
rebasing my work on master, but it will take some time
On Sat, Apr 17, 2010 at 12:58 PM, walter harms wha...@bfs.de wrote:
I admire your effort to make busybox run on Win but i wonder why there
seems no compartibility lib for porting UNIX programs to Win. Surely this is
not the first time it is done.
Sure I'm not the first one doing this. Cygwin
On Wed, Apr 14, 2010 at 3:02 AM, Doug Clapp doug.cl...@triad.rr.com wrote:
A couple of suggestions for Unix/Linux shell users stuck in a Windows
environment:
Try delorie software (www.delorie.com) for djgpp and associated tools. A bit
dated now, but may help. Gives you a build environment for
On Tue, Apr 13, 2010 at 10:01 PM, Nguyen Thai Ngoc Duy
pclo...@gmail.com wrote:
Hi,
(...)
Except network and tty-related commands, others (sort of) work. wget
and vi work, although limited. Linux-specific commands won't work,
obviously.
Hi, I intend to port BusyBox to GNU Hurd, so I'm in a
2010/4/14 Jérémie Koenig j...@jk.fr.eu.org:
On Tue, Apr 13, 2010 at 10:01 PM, Nguyen Thai Ngoc Duy
pclo...@gmail.com wrote:
Hi,
(...)
Except network and tty-related commands, others (sort of) work. wget
and vi work, although limited. Linux-specific commands won't work,
obviously.
Hi, I
One question I have been asking to myself is whether and how the
applets irrelevant to a target system should be dealt with:
* disabled at the configuration stage using KConfig dependencies;
* allowed to fail to build if the user chooses them;
* allowed to build successfully with stub
On Wed, Apr 14, 2010 at 6:04 PM, Cathey, Jim jcat...@ciena.com wrote:
One question I have been asking to myself is whether and how the
applets irrelevant to a target system should be dealt with:
* disabled at the configuration stage using KConfig dependencies;
* allowed to fail to build if
On Tue, Apr 13, 2010 at 10:33 PM, Nguyen Thai Ngoc Duy
pclo...@gmail.com wrote:
On Wed, Apr 14, 2010 at 4:34 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
4. ash
~1000 lines, half of them to work around fork(). Not everything works,
and not really stable. I'm thinking about a
On Wed, Apr 14, 2010 at 10:42 PM, Denys Vlasenko
vda.li...@googlemail.com wrote:
On Tue, Apr 13, 2010 at 10:33 PM, Nguyen Thai Ngoc Duy
pclo...@gmail.com wrote:
On Wed, Apr 14, 2010 at 4:34 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
4. ash
~1000 lines, half of them to work around
Nguyen Thai Ngoc Duy wrote:
Hi,
I started the port about three years ago, on 1.6.1. Currently I'm
rebasing my work on master, but it will take some time before I could
submit anything. The old version based on 1.6.1 is on
http://github.com/pclouds/busybox-w32. Anyway I would like to discuss
On Tue, Apr 13, 2010 at 1:01 PM, Nguyen Thai Ngoc Duy pclo...@gmail.com wrote:
Hi,
I started the port about three years ago, on 1.6.1. Currently I'm
rebasing my work on master, but it will take some time before I could
submit anything. The old version based on 1.6.1 is on
20 matches
Mail list logo
