From: "Rick A. Hohensee" <rickh@capaccess.org>
To: linux-assembly@vger.kernel.org, wli@holomorphy.com,
root@chaos.analogic.com, hpa@zytor.com, doug@osdl.org,
lwn@lwn.net, business@fsmlabs.com, esr@thyrsus.com,
maddog@li.org, linux-kernel@vger.kernel.org
Subject: Now that the 0 Penguin doesn't work for Microsoft
Date: Thu, 19 Jun 2003 03:44:45 -0400 [thread overview]
Message-ID: <fc.0010c7b20092aa700010c7b20092aa70.92aa79@capaccess.org> (raw)
Now that the 0 Penguin doesn't work for TransMicrosoft perhaps Linux can
develop a wholesome interest in end-users. cLIeNUX is still on my webpage,
and still on this box, all by itself, along with my Ha3sm-in-kernel and so
on. But I don't usually boot to that. Hmmm, my webpage is unreachable.
Speaking of this box, cLIeNUX 0...
:; cLIeNUX /dev/tty10 02:55:14 /
:;d -d */
Ha3sm/ configure/ enth04/ help/ owner/ suite/
boot/ dev/ floppy/ log/ source/ temp/
command/ device/ guest/ mount/ subroutine/
:; cLIeNUX /dev/tty10 02:55:20 /
:;
I wonder why Torvalds left. How long would it take one guy to port 1.2.13
to osimplay, anyway?
Rick Hohensee
Ha3sm Viralinux II asmacs shasm osimplay cLIeNUX kspamd pasties
PASSM syslib.a "man C" eforthl upForth Dotted Standard File Hierarchy
edcL BashcL etc. etc.
next reply other threads:[~2003-06-19 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 7:44 Rick A. Hohensee [this message]
2003-06-22 14:21 ` Now that the 0 Penguin doesn't work for Microsoft Pavel Machek
2003-06-22 15:45 ` Now that the 0 Penguin Rick A. Hohensee
2003-06-22 15:48 ` Jens Axboe
2003-06-22 16:11 ` Pavel Machek
2003-06-23 16:09 ` Gerhard Mack
2003-06-23 16:41 ` Alan Cox
2003-06-23 16:52 ` Eli Carter
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.0010c7b20092aa700010c7b20092aa70.92aa79@capaccess.org \
--to=rickh@capaccess.org \
--cc=business@fsmlabs.com \
--cc=doug@osdl.org \
--cc=esr@thyrsus.com \
--cc=hpa@zytor.com \
--cc=linux-assembly@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=maddog@li.org \
--cc=root@chaos.analogic.com \
--cc=wli@holomorphy.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.