[Toybox] [PATCH] sh: pass "\" to the later app

[David Seikel]

On 2023-07-05 02:29:39, Rob Landley wrote:
> >> still matching the behavior in my devuan install. (Still devuan bronchitis,
> >> haven't updated to devuan cholera yet. Um, the web page says devuan B matches
> >> debian "buster" and devuan C matches "bullseye", if that helps.)
> > 
> > Not at all. But charming version names.
> 
> Devuan is "debian without systemd" so 99% just a wrapper around the existing
> debian repositories intercepting the small number of packages that need to be
> diddled, and once they decided they were stable they started doing alphabetical
> release names like xubuntu did, and I never remember what the names are but
> remember the letters. (The debian ones I look up because they don't have letters.)

I'm what we call "the package mirror herder" for Devuan, top level admin
contact for the package mirrors that do that "serve Devuan stuff or
redirect to Debian" thing.  Though some of them are running a Debian
mirror as well, so skip the redirect step.

> I'm still using the B (ahem, "Beowulf") release. The C ("Chimaera") release came
> out October 2021 but I haven't upgraded yet because B (from June 2020) is still
> supported.

I keep complaining that we need to pick names that are easier to spell,
they keep picking the hard names.  I mentioned in IRC that I now have
decided that being hard to spell is a feature, so I spell them wrong
deliberately.  Though now I'm thinking just using the first letter is a
better option.  Thanks for that idea.

Now that the latest Debian has been released, Daedalus is next up for
Devuan, it's close, and quite stable.  Just gotta sort out some things
with the web site and installer.

A ("ASCII") got archived earlier this year, B is still supported until
after the next major Debian release.

> Back when I did busybox, I was replacing the Linux From Scratch packages with
> busybox, and I eventually got a system built from just 7 packages (linux,
> busybox, uclibc, gcc, binutils, make, bash) to rebuild itself under itself from
> source code, and build Linux From Scratch and chunks of Beyond Linux From
> Scratch under the result. (And it cross compiled for a dozen architectures and
> ran the build under QEMU, and could call out to the cross compiler running on
> the host via distcc through the emulated network to move the heavy lifting of
> copilation outside of the emulator to speed things up...)
> 
> https://landley.net/aboriginal/about.html#design
> 
> That worked, meaning I know what success _used_ to look like. Pity it's a moving
> target...

I contributed the x486 support to Aboriginal Linux, my client was using
that at the time for his device.  We managed to get it approved by the
government auditors back then.  Now he's talking about updating it to
some Pi type thing.  Easiest thing for me to do I suspect is to stick
with the version of Aboriginal Linux we used back then, but I'm open to
being persuaded otherwise.  On the other hand, the less changes the
better for the auditors. "Same code you looked at last time, we just
added some more buttons and changed the graphics."

I even put together a Debian based build environment for the auditors, so
they could rebuild it and check if it was reproducible.

-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.