From: "Rick A. Hohensee" <rickh@Capaccess.org>
To: linux-kernel@vger.kernel.org
Subject: Re: PUPLinux 1.2.14 Umbilical
Date: Sat, 02 Mar 2002 11:19:08 -0500 [thread overview]
Message-ID: <fc.008584120032a87d008584120032a87d.32a898@Capaccess.org> (raw)
> Rick,
>
> PUPLinux sounds great!
>
> Does it run on Red Hat?
>
Ha. Ha ha. (Actually that IS damn funny. Nice one. Made my day.)
> See ya,
> Joe Barr
>
Hmmm, not finding any "Joe Barr" in the last few weeks of l-k. Let's
see about google. From Joe Barr's annual Linux predictions on
linuxworld....
About the author
[39]Joe Barr is a freelance journalist covering Linux, open source,
and network security. His 'Open Source' column has been a regular
feature of LinuxWorld.com since its inception. As far as we know, he
is the only living journalist whose works have appeared both in
phrack, the legendary underground zine, and IBM Personal Systems
Magazine.
Resources
Oh. Hi.
Sorry I didn't recognize you. I spend more time trying to write the future
than reading about it. Or rather, I tend to read about the future in old
sourcecode. Like this bizarre thing dmr just sent me; ed.bun, which
appears to be a Plan 9 "bundle" of 3 V5 UNIX assembly source files for ed.
Plan 9 "bundle" appears to be a sed script. ed, bundled by the streamable
version of ed. Of course, for all I know Plan 9 sed is really streamable
sam. It's surely UTF-8. Welcome to the future.
Relax. I don't see my stuff screwing up any of your predictions any time
soon. However, if you want to see my most futuristic flakey untenable
stuff, sticking my own 3-stack Forth in the Linux kernel is nothing. Have
a look at
URL: ftp://linux01.gwdg.de/pub/cLIeNUX/descriptive/membership
and the other oddities in that directory. They are my non-technical side,
to the extent that I have such a thing.
So, on the "one bad joke deserves another" tack you established via email,
it's your turn.
Rick Hohensee
reply other threads:[~2002-03-02 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc.008584120032a87d008584120032a87d.32a898@Capaccess.org \
--to=rickh@capaccess.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®