From phil at pricom.com.au  Tue Mar 14 05:05:55 2017
From: phil at pricom.com.au (Philip Rhoades)
Date: Tue, 14 Mar 2017 16:05:55 +1100
Subject: [Aboriginal] Building a floppy rescue set like BG did?
Message-ID: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>

People,

As an exercise, I want to create a VM image (or at least backup of all 
the files with rsync) from a SCSI drive in an old Red Hat (NOT 
Enterprise) v5.2 Linux 486 machine (circa 1999 that does have rsync on 
it but it has protocol problems talking to my server).  The 486 has:

- an ISA Adaptec 1542 SCSI controller attached to a Seagate 2GB drive 
with 6 partitions

- an ISA ne2000 network card

- a 1.44MB FD

So, to be able to create the image of the 2GB SCSI drive that is in the 
486, I need to boot the 486 on one or more floppy disks and dd the 
/dev/sda drive over SSH to a file on my big Fedora 25 x86_64 
workstation.  I now have Basic Linux booting from floppies but it is 
still 2005 vintage and uses SSH1 and I haven't been able to get the old 
Ciphers, MACs and KexAlgorithms working with my Fedora 25 x86_64 server 
- so I still can't ssh or rsync to it from the 486.  BL does not have 
any rshd that rsync could use . . so I am thinking that AL should be 
more up to date but I will have to build my own system it seems.  I got 
BG's disks going:

   http://www.giannone.ch/rescue/current

but they didn't have support for the SCSI controller - I sent him a 
couple of emails (and even rang him from Australia!) about getting his 
custom build scripts of AL to modify . . but he didn't get back to me . 
.

Has anyone here already produced a floppy boot set?  I have just cloned 
the git repo and am building for the 486 but it would be nice if someone 
could make my learning curve less steep . .

Thanks!

Phil.
-- 
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  phil at pricom.com.au


From christopher.r.barry at gmail.com  Tue Mar 14 16:03:49 2017
From: christopher.r.barry at gmail.com (Christopher Barry)
Date: Tue, 14 Mar 2017 12:03:49 -0400
Subject: [Aboriginal] Building a floppy rescue set like BG did?
In-Reply-To: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>
References: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>
Message-ID: <20170314120349.4577e7be@monolith.infinux.org>

On Tue, 14 Mar 2017 16:05:55 +1100
Philip Rhoades <phil at pricom.com.au> wrote:

>People,
>
>As an exercise, I want to create a VM image (or at least backup of all 
>the files with rsync) from a SCSI drive in an old Red Hat (NOT 
>Enterprise) v5.2 Linux 486 machine (circa 1999 that does have rsync on 
>it but it has protocol problems talking to my server).  The 486 has:
>
>- an ISA Adaptec 1542 SCSI controller attached to a Seagate 2GB drive 
>with 6 partitions
>
>- an ISA ne2000 network card
>
>- a 1.44MB FD
>
>So, to be able to create the image of the 2GB SCSI drive that is in
>the 486, I need to boot the 486 on one or more floppy disks and dd the 
>/dev/sda drive over SSH to a file on my big Fedora 25 x86_64 
>workstation.  I now have Basic Linux booting from floppies but it is 
>still 2005 vintage and uses SSH1 and I haven't been able to get the
>old Ciphers, MACs and KexAlgorithms working with my Fedora 25 x86_64
>server 
>- so I still can't ssh or rsync to it from the 486.  BL does not have 
>any rshd that rsync could use . . so I am thinking that AL should be 
>more up to date but I will have to build my own system it seems.  I
>got BG's disks going:
>
>   http://www.giannone.ch/rescue/current
>
>but they didn't have support for the SCSI controller - I sent him a 
>couple of emails (and even rang him from Australia!) about getting his 
>custom build scripts of AL to modify . . but he didn't get back to
>me . .
>
>Has anyone here already produced a floppy boot set?  I have just
>cloned the git repo and am building for the 486 but it would be nice
>if someone could make my learning curve less steep . .
>
>Thanks!
>
>Phil.

Q: does the 486 boot at all on it's own? That's not clear to me from
this email. If it does boot, then I assume you are worried about open
files not transferring.

If it can boot on it's own, then I also assume you can see the disk and
and all the files and the network too.

If you have nc (netcat command) you can simply use dd over netcat to
backup the system. It's the simplest way to backup a disk image to
another host over the network.

start nc listening on port 9000 for connections in a shell on the f25
boxen first:

# nc -l -p 9000 | dd of=/somewhere/486-rh-backup.img
It will hang there waiting...
(-p may or may not be needed on your f25 box)

then on the 486, boot to single user mode with networking (if an
option), or telinit S to get into single mode and start networking if
needed.

From the 486 command line, dd off the entire disk (I assume it's called
sda here):

# dd if=/dev/sda | nc ip.of.fedora.box:9000


This sends data in the clear though, no encryption. Being in single user
mode, there will be very few if any important files open during the
transfer (e.g. some logfiles may be truncated), and you should be fine.

Here's the netcat source code if you need to build it on the 486.
ftp://ftp.debian.org/debian/pool/main/n/netcat/netcat_1.10.orig.tar.bz2

-- 
Regards,
Christopher


From phil at pricom.com.au  Tue Mar 14 23:11:41 2017
From: phil at pricom.com.au (Philip Rhoades)
Date: Wed, 15 Mar 2017 10:11:41 +1100
Subject: [Aboriginal] Building a floppy rescue set like BG did?
In-Reply-To: <20170314120349.4577e7be@monolith.infinux.org>
References: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>
	<20170314120349.4577e7be@monolith.infinux.org>
Message-ID: <7306b0a4c6d37a77f60c873895ca8f28@pricom.com.au>

Christopher,


On 2017-03-15 03:03, Christopher Barry wrote:
> On Tue, 14 Mar 2017 16:05:55 +1100
> Philip Rhoades <phil at pricom.com.au> wrote:
> 
>> People,
>> 
>> As an exercise, I want to create a VM image (or at least backup of all
>> the files with rsync) from a SCSI drive in an old Red Hat (NOT
>> Enterprise) v5.2 Linux 486 machine (circa 1999 that does have rsync on
>> it but it has protocol problems talking to my server).  The 486 has:
>> 
>> - an ISA Adaptec 1542 SCSI controller attached to a Seagate 2GB drive
>> with 6 partitions
>> 
>> - an ISA ne2000 network card
>> 
>> - a 1.44MB FD
>> 
>> So, to be able to create the image of the 2GB SCSI drive that is in
>> the 486, I need to boot the 486 on one or more floppy disks and dd the
>> /dev/sda drive over SSH to a file on my big Fedora 25 x86_64
>> workstation.  I now have Basic Linux booting from floppies but it is
>> still 2005 vintage and uses SSH1 and I haven't been able to get the
>> old Ciphers, MACs and KexAlgorithms working with my Fedora 25 x86_64
>> server
>> - so I still can't ssh or rsync to it from the 486.  BL does not have
>> any rshd that rsync could use . . so I am thinking that AL should be
>> more up to date but I will have to build my own system it seems.  I
>> got BG's disks going:
>> 
>>   http://www.giannone.ch/rescue/current
>> 
>> but they didn't have support for the SCSI controller - I sent him a
>> couple of emails (and even rang him from Australia!) about getting his
>> custom build scripts of AL to modify . . but he didn't get back to
>> me . .
>> 
>> Has anyone here already produced a floppy boot set?  I have just
>> cloned the git repo and am building for the 486 but it would be nice
>> if someone could make my learning curve less steep . .
>> 
>> Thanks!
>> 
>> Phil.
> 
> Q: does the 486 boot at all on it's own? That's not clear to me from
> this email. If it does boot, then I assume you are worried about open
> files not transferring.


Correct - RH5.2.


> If it can boot on it's own, then I also assume you can see the disk and
> and all the files and the network too.


Yes.


> If you have nc (netcat command) you can simply use dd over netcat to
> backup the system. It's the simplest way to backup a disk image to
> another host over the network.


Ah yes . .


> start nc listening on port 9000 for connections in a shell on the f25
> boxen first:
> 
> # nc -l -p 9000 | dd of=/somewhere/486-rh-backup.img
> It will hang there waiting...
> (-p may or may not be needed on your f25 box)
> 
> then on the 486, boot to single user mode with networking (if an
> option), or telinit S to get into single mode and start networking if
> needed.


Isn't that just Level 3?  Are you saying that after starting networking, 
the system is still in single-user mode?


> From the 486 command line, dd off the entire disk (I assume it's called
> sda here):
> 
> # dd if=/dev/sda | nc ip.of.fedora.box:9000
> 
> 
> This sends data in the clear though, no encryption.


Yep, no worries - it is just over the LAN.


> Being in single user
> mode, there will be very few if any important files open during the
> transfer (e.g. some logfiles may be truncated), and you should be fine.


Oh, OK - I will give it a shot!  Thanks!


> Here's the netcat source code if you need to build it on the 486.
> ftp://ftp.debian.org/debian/pool/main/n/netcat/netcat_1.10.orig.tar.bz2


I can't remember if it has netcat on there - I will have a look.  I 
think the SCSI drive is on the way out though - but I did manage to 
compile rsh - but that still didn't work for some reason . .

Even if netcat works - I am still interested in building a floppy-booted 
AL system!

Regards,

Phil.
-- 
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  phil at pricom.com.au


From rob at landley.net  Thu Mar 23 19:56:29 2017
From: rob at landley.net (Rob Landley)
Date: Thu, 23 Mar 2017 14:56:29 -0500
Subject: [Aboriginal] Building a floppy rescue set like BG did?
In-Reply-To: <7306b0a4c6d37a77f60c873895ca8f28@pricom.com.au>
References: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>
	<20170314120349.4577e7be@monolith.infinux.org>
	<7306b0a4c6d37a77f60c873895ca8f28@pricom.com.au>
Message-ID: <8d1392c0-0554-7db5-a4ca-3fe50e434d4c@landley.net>

On 03/14/2017 06:11 PM, Philip Rhoades wrote:
> Even if netcat works - I am still interested in building a floppy-booted
> AL system!

You're not fitting the native toolchain on a floppy (the /usr/include
headers alone _compress_ to multiple megabytes), and if you skip the
native toolchain you might as well use the much simpler
https://github.com/landley/mkroot build.

I need to finish implementing the various targets' kernel builds, do a
proper release of that, write up better documentation for it (probably a
big README since github displays that), and get the control images to
run under it.

I also need to update the aboriginal linux website to say that the
project's concluded and mkroot is the successor. I keep starting a
writeup and it goes off into long explanations of the history and what I
was trying to accomplish and so on... I should just finish
http://landley.net/aboriginal/history.html

Rob


From phil at pricom.com.au  Fri Mar 24 14:36:53 2017
From: phil at pricom.com.au (Philip Rhoades)
Date: Sat, 25 Mar 2017 01:36:53 +1100
Subject: [Aboriginal] Building a floppy rescue set like BG did? +
 "Android self-hosting" idea
In-Reply-To: <8d1392c0-0554-7db5-a4ca-3fe50e434d4c@landley.net>
References: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>
	<20170314120349.4577e7be@monolith.infinux.org>
	<7306b0a4c6d37a77f60c873895ca8f28@pricom.com.au>
	<8d1392c0-0554-7db5-a4ca-3fe50e434d4c@landley.net>
Message-ID: <983bfd081c5978e7942581289361c03e@pricom.com.au>

Rob,


On 2017-03-24 06:56, Rob Landley wrote:
> On 03/14/2017 06:11 PM, Philip Rhoades wrote:
>> Even if netcat works - I am still interested in building a 
>> floppy-booted
>> AL system!
> 
> You're not fitting the native toolchain on a floppy (the /usr/include
> headers alone _compress_ to multiple megabytes), and if you skip the
> native toolchain you might as well use the much simpler
> https://github.com/landley/mkroot build.


Thanks for that but see output below - although running make in the 
./build/toybox-0.7.3 dir worked OK . .


> I need to finish implementing the various targets' kernel builds, do a
> proper release of that, write up better documentation for it (probably 
> a
> big README since github displays that), and get the control images to
> run under it.


Right.


> I also need to update the aboriginal linux website to say that the
> project's concluded and mkroot is the successor. I keep starting a
> writeup and it goes off into long explanations of the history and what 
> I
> was trying to accomplish and so on... I should just finish
> http://landley.net/aboriginal/history.html


I think I have read that before but I will have another look to see if 
there is an updated version.

Also, have you thought about updating your comments in a blog or 
something re Android from the "Embedded Linux Conference 2013"?  I find 
your "Android self-hosting" argument very compelling and interesting and 
wonder how you feel about the situation now after a few years have 
passed since you made that talk.

Regards,

Phil.

Error output:

scripts/make.sh
Generate headers from toys/*/*.c...
Make generated/config.h from .config.
generated/flags.h Compile 
toybox......................................................................................................................................................../home/floppy_booted/toybox/airlock/ld: 
cannot find -lselinux
/home/floppy_booted/toybox/airlock/ld: cannot find -lcrypto
generated/obj/id.o: In function `do_id':
id.c:(.text.do_id+0x1a3): warning: Using 'getgrouplist' in statically 
linked applications requires at runtime the shared libraries from the 
glibc version used for linking
generated/obj/lib_xwrap.o: In function `xsetuser':
xwrap.c:(.text.xsetuser+0xb): warning: Using 'initgroups' in statically 
linked applications requires at runtime the shared libraries from the 
glibc version used for linking
generated/obj/lib_xwrap.o: In function `xgetgrgid':
xwrap.c:(.text.xgetgrgid+0x4): warning: Using 'getgrgid' in statically 
linked applications requires at runtime the shared libraries from the 
glibc version used for linking
generated/obj/lib_xwrap.o: In function `xgetgid':
xwrap.c:(.text.xgetgid+0xa): warning: Using 'getgrnam' in statically 
linked applications requires at runtime the shared libraries from the 
glibc version used for linking
generated/obj/lib_lib.o: In function `bufgetgrgid':
lib.c:(.text.bufgetgrgid+0x60): warning: Using 'getgrgid_r' in 
statically linked applications requires at runtime the shared libraries 
from the glibc version used for linking
generated/obj/lib_xwrap.o: In function `xgetuid':
xwrap.c:(.text.xgetuid+0xa): warning: Using 'getpwnam' in statically 
linked applications requires at runtime the shared libraries from the 
glibc version used for linking
generated/obj/lib_xwrap.o: In function `xgetpwuid':
xwrap.c:(.text.xgetpwuid+0x4): warning: Using 'getpwuid' in statically 
linked applications requires at runtime the shared libraries from the 
glibc version used for linking
generated/obj/lib_lib.o: In function `bufgetpwuid':
lib.c:(.text.bufgetpwuid+0x60): warning: Using 'getpwuid_r' in 
statically linked applications requires at runtime the shared libraries 
from the glibc version used for linking
generated/obj/lib_net.o: In function `xconnect':
net.c:(.text.xconnect+0x46): warning: Using 'getaddrinfo' in statically 
linked applications requires at runtime the shared libraries from the 
glibc version used for linking
generated/obj/passwd.o: In function `passwd_main':
passwd.c:(.text.passwd_main+0x71): warning: Using 'getspnam' in 
statically linked applications requires at runtime the shared libraries 
from the glibc version used for linking
generated/obj/netcat.o: In function `lookup_name.constprop.1':
netcat.c:(.text.lookup_name.constprop.1+0x5): warning: Using 
'gethostbyname' in statically linked applications requires at runtime 
the shared libraries from the glibc version used for linking
generated/obj/netstat.o: In function `addr2str':
netstat.c:(.text.addr2str+0x15a): warning: Using 'getservbyport' in 
statically linked applications requires at runtime the shared libraries 
from the glibc version used for linking
collect2: error: ld returned 1 exit status
Makefile:19: recipe for target 'toybox' failed
make: *** [toybox] Error 1


-- 
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  phil at pricom.com.au


From rob at landley.net  Fri Mar 24 16:54:00 2017
From: rob at landley.net (Rob Landley)
Date: Fri, 24 Mar 2017 11:54:00 -0500
Subject: [Aboriginal] Building a floppy rescue set like BG did? +
 "Android self-hosting" idea
In-Reply-To: <983bfd081c5978e7942581289361c03e@pricom.com.au>
References: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>
	<20170314120349.4577e7be@monolith.infinux.org>
	<7306b0a4c6d37a77f60c873895ca8f28@pricom.com.au>
	<8d1392c0-0554-7db5-a4ca-3fe50e434d4c@landley.net>
	<983bfd081c5978e7942581289361c03e@pricom.com.au>
Message-ID: <3d0dad55-d768-9c9e-7f66-39131e456bcc@landley.net>

On 03/24/2017 09:36 AM, Philip Rhoades wrote:
> Rob,
> On 2017-03-24 06:56, Rob Landley wrote:
>> On 03/14/2017 06:11 PM, Philip Rhoades wrote:
>>> Even if netcat works - I am still interested in building a floppy-booted
>>> AL system!
>>
>> You're not fitting the native toolchain on a floppy (the /usr/include
>> headers alone _compress_ to multiple megabytes), and if you skip the
>> native toolchain you might as well use the much simpler
>> https://github.com/landley/mkroot build.
> 
> 
> Thanks for that but see output below - although running make in the
> ./build/toybox-0.7.3 dir worked OK . .

Let's see, that would be...

> Error output:
>
> scripts/make.sh
> Generate headers from toys/*/*.c...
> Make generated/config.h from .config.
> generated/flags.h Compile
>
toybox......................................................................................................................................................../home/floppy_booted/toybox/airlock/ld:
> cannot find -lselinux
> /home/floppy_booted/toybox/airlock/ld: cannot find -lcrypto

Huh. What distro are you building this on? I'd like to try to reproduce
it here. In scripts/make.sh toybox does test builds to see which
libraries are there, and only adds the ones it can find to the link.
This implies that it's seeing different libraries at probe time than it
is at build time.

When I build here, I get:

scripts/make.sh
Generate headers from toys/*/*.c...
generated/newtoys.h Library probe.........
Make generated/config.h from .config.
generated/flags.h generated/globals.h generated/tags.h generated/help.h

Which is 3 more headers being generated at the end than yours showed.
This implies that something did a build in build/toybox-0.7.3 (filling
it with temporary files) and _then_ ran mkroot.sh?

Also, you deleted context: is this the airlock build or is it the target
build you're seeing this one? (It says "airlock" before the airlock
build.) Did you speciry a cross compiler? (Guessing no since the page of
"glibc doesn't support static linking!" warnings shouldn't happen with
basically any cross compiler, since none of them use glibc.)

(The airlock step is basically a smaller host-tools from aboriginal, I
merged it into toybox as "make install_airlock".)

>> I need to finish implementing the various targets' kernel builds, do a
>> proper release of that, write up better documentation for it (probably a
>> big README since github displays that), and get the control images to
>> run under it.
> 
> Right.

That's basically my todo list before I have big announcements, I've just
been distracted by a half-dozen other things. (Bug reports from toybox
in android, j-core.org stuff, so far this year I've had to fly to
portland, tasmania, tokyo, and san francisco. Add december and I was in
minneapolis and san diego.)

>> I also need to update the aboriginal linux website to say that the
>> project's concluded and mkroot is the successor. I keep starting a
>> writeup and it goes off into long explanations of the history and what I
>> was trying to accomplish and so on... I should just finish
>> http://landley.net/aboriginal/history.html
> 
> I think I have read that before but I will have another look to see if
> there is an updated version.

There is but it's not uploaded yet since it _also_ trails off
midsentence. :)

> Also, have you thought about updating your comments in a blog or
> something re Android from the "Embedded Linux Conference 2013"?  I find
> your "Android self-hosting" argument very compelling and interesting and
> wonder how you feel about the situation now after a few years have
> passed since you made that talk.

Android merged toybox at the start of 2015, it first shipped in Marshmallow:

  https://lwn.net/Articles/629362/

The #2 contributor to toybox is Elliott Hughes, Android's toolbox and
bionic maintainer, who has committed to replacing toolbox entirely with
toybox:

http://lists.landley.net/pipermail/toybox-landley.net/2016-June/008484.html

He updates the toybox roadmap more often than I do:

  https://github.com/landley/toybox/commits/master/www/roadmap.html

Alas, I'm the bottleneck on finishing off toolbox, $DAYJOB and life have
been hugely distracting for the past ~8 months. (Trying to dig out of
that, but I need to be in San Diego again a week from monday...)

Still, let's try to track down the failure you're seeing with mkroot. I
want that to work for everybody. I haven't moved over the environment
variable whitelisting yet, although it's basically something like:

  [ ! -z "$TERM" ] && exec env -i "PATH=$PATH" "$0"

(Modulo "$TERM" being reliably set in the host environment and NOT set
by magic /etc/profile stuff that runs even for shell scripts. I dunno,
maybe $USER would be better? Tested to work with my bash on ubuntu !=
and this won't screw up on some obscure distro like RHELL 9...)

> Regards,
>
> Phil.

Rob

P.S. I'm not sure if I should get mkroot a new list, or move this one
over to a new name. At the moment there's not enough to see to take
action on either way. Working on it, but juggling 9 other things at the
same time...


From phil at pricom.com.au  Fri Mar 24 17:56:43 2017
From: phil at pricom.com.au (Philip Rhoades)
Date: Sat, 25 Mar 2017 04:56:43 +1100
Subject: [Aboriginal] Building a floppy rescue set like BG did? +
 "Android self-hosting" idea
In-Reply-To: <3d0dad55-d768-9c9e-7f66-39131e456bcc@landley.net>
References: <cac837ca5fcbe0b6c1a400d0bc7480d8@pricom.com.au>
	<20170314120349.4577e7be@monolith.infinux.org>
	<7306b0a4c6d37a77f60c873895ca8f28@pricom.com.au>
	<8d1392c0-0554-7db5-a4ca-3fe50e434d4c@landley.net>
	<983bfd081c5978e7942581289361c03e@pricom.com.au>
	<3d0dad55-d768-9c9e-7f66-39131e456bcc@landley.net>
Message-ID: <096155cda8bf79de3d226697b4e35904@pricom.com.au>

Rob,


On 2017-03-25 03:54, Rob Landley wrote:
> On 03/24/2017 09:36 AM, Philip Rhoades wrote:
>> Rob,
>> On 2017-03-24 06:56, Rob Landley wrote:
>>> On 03/14/2017 06:11 PM, Philip Rhoades wrote:
>>>> Even if netcat works - I am still interested in building a 
>>>> floppy-booted
>>>> AL system!
>>> 
>>> You're not fitting the native toolchain on a floppy (the /usr/include
>>> headers alone _compress_ to multiple megabytes), and if you skip the
>>> native toolchain you might as well use the much simpler
>>> https://github.com/landley/mkroot build.
>> 
>> 
>> Thanks for that but see output below - although running make in the
>> ./build/toybox-0.7.3 dir worked OK . .
> 
> Let's see, that would be...
> 
>> Error output:
>> 
>> scripts/make.sh
>> Generate headers from toys/*/*.c...
>> Make generated/config.h from .config.
>> generated/flags.h Compile
>> 
> toybox......................................................................................................................................................../home/floppy_booted/toybox/airlock/ld:
>> cannot find -lselinux
>> /home/floppy_booted/toybox/airlock/ld: cannot find -lcrypto
> 
> Huh. What distro are you building this on?


Fedora 25 x86_64


> I'd like to try to reproduce
> it here. In scripts/make.sh toybox does test builds to see which
> libraries are there, and only adds the ones it can find to the link.
> This implies that it's seeing different libraries at probe time than it
> is at build time.


Right.


> When I build here, I get:
> 
> scripts/make.sh
> Generate headers from toys/*/*.c...
> generated/newtoys.h Library probe.........
> Make generated/config.h from .config.
> generated/flags.h generated/globals.h generated/tags.h generated/help.h
> 
> Which is 3 more headers being generated at the end than yours showed.
> This implies that something did a build in build/toybox-0.7.3 (filling
> it with temporary files) and _then_ ran mkroot.sh?


I just deleted the created dirs and ran the script again to be sure that 
it wasn't a different result from manually running the make in between 
running the script twice but I got the same problem . . so I am 
definitely just running "mkroot.sh" in an otherwise empty directory.


> Also, you deleted context: is this the airlock build or is it the 
> target
> build you're seeing this one? (It says "airlock" before the airlock
> build.) Did you speciry a cross compiler? (Guessing no since the page 
> of
> "glibc doesn't support static linking!" warnings shouldn't happen with
> basically any cross compiler, since none of them use glibc.)


Attached is the full output - does that help?


> (The airlock step is basically a smaller host-tools from aboriginal, I
> merged it into toybox as "make install_airlock".)


Right.


>>> I need to finish implementing the various targets' kernel builds, do 
>>> a
>>> proper release of that, write up better documentation for it 
>>> (probably a
>>> big README since github displays that), and get the control images to
>>> run under it.
>> 
>> Right.
> 
> That's basically my todo list before I have big announcements, I've 
> just
> been distracted by a half-dozen other things. (Bug reports from toybox
> in android, j-core.org stuff, so far this year I've had to fly to
> portland, tasmania, tokyo, and san francisco. Add december and I was in
> minneapolis and san diego.)


Tasmania!  If I had known you were in Oz it would have been good to 
catch up . .


>>> I also need to update the aboriginal linux website to say that the
>>> project's concluded and mkroot is the successor. I keep starting a
>>> writeup and it goes off into long explanations of the history and 
>>> what I
>>> was trying to accomplish and so on... I should just finish
>>> http://landley.net/aboriginal/history.html
>> 
>> I think I have read that before but I will have another look to see if
>> there is an updated version.
> 
> There is but it's not uploaded yet since it _also_ trails off
> midsentence. :)


No worries . .


>> Also, have you thought about updating your comments in a blog or
>> something re Android from the "Embedded Linux Conference 2013"?  I 
>> find
>> your "Android self-hosting" argument very compelling and interesting 
>> and
>> wonder how you feel about the situation now after a few years have
>> passed since you made that talk.
> 
> Android merged toybox at the start of 2015, it first shipped in 
> Marshmallow:
> 
>   https://lwn.net/Articles/629362/


Will check it out.


> The #2 contributor to toybox is Elliott Hughes, Android's toolbox and
> bionic maintainer, who has committed to replacing toolbox entirely with
> toybox:
> 
> http://lists.landley.net/pipermail/toybox-landley.net/2016-June/008484.html


Ditto.


> He updates the toybox roadmap more often than I do:
> 
>   https://github.com/landley/toybox/commits/master/www/roadmap.html


Ditto again . .


> Alas, I'm the bottleneck on finishing off toolbox, $DAYJOB and life 
> have
> been hugely distracting for the past ~8 months. (Trying to dig out of
> that, but I need to be in San Diego again a week from monday...)


No worries . .


> Still, let's try to track down the failure you're seeing with mkroot. I
> want that to work for everybody. I haven't moved over the environment
> variable whitelisting yet, although it's basically something like:
> 
>   [ ! -z "$TERM" ] && exec env -i "PATH=$PATH" "$0"


Aha!  Before I was running the script in a tmux tab and getting the 
results that I have attached.  I just tried running the line above in 
the tmux tab and the tab disappeared! - so I tried opening a new xterm 
with no tmux and running the script from there and got a different 
result:

toybox-0.7.3/www/
toybox-0.7.3/www/about.html
toybox-0.7.3/www/cleanup.html
toybox-0.7.3/www/code.html
toybox-0.7.3/www/design.html
toybox-0.7.3/www/ext2.html
toybox-0.7.3/www/faq.html
toybox-0.7.3/www/footer.html
toybox-0.7.3/www/header.html
toybox-0.7.3/www/index.html
toybox-0.7.3/www/license.html
toybox-0.7.3/www/news.html
toybox-0.7.3/www/oldnews.html
toybox-0.7.3/www/roadmap.html
toybox-0.7.3/www/status.html
toybox-0.7.3/www/toycans.png
cc -o kconfig/conf kconfig/conf.c kconfig/zconf.tab.c -DKBUILD_NO_NLS=1 
\
	-DPROJECT_NAME=\"ToyBox\"
ccache: error: Could not find compiler "cc" in PATH
kconfig/Makefile:65: recipe for target 'kconfig/conf' failed
make: *** [kconfig/conf] Error 1


> (Modulo "$TERM" being reliably set in the host environment and NOT set
> by magic /etc/profile stuff that runs even for shell scripts. I dunno,
> maybe $USER would be better? Tested to work with my bash on ubuntu !=
> and this won't screw up on some obscure distro like RHELL 9...)


Well not exactly RHELL 9 but still Fedora 25 . . I think the last RH I 
used was 5.2 (ie a still "free" version before RHE).


> P.S. I'm not sure if I should get mkroot a new list, or move this one
> over to a new name. At the moment there's not enough to see to take
> action on either way. Working on it, but juggling 9 other things at the
> same time...


I am in a similar position but I am interested in making more progress 
with this stuff whenever I can so I will just try things whenever you 
have time to look at it and can suggest something.

Regards,

Phil.
-- 
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  phil at pricom.com.au
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mkroot.out
URL: <http://lists.landley.net/pipermail/aboriginal/attachments/20170325/87594186/attachment.ksh>