From: Joe Barr <warthawg@austin.rr.com>
To: "Rick A. Hohensee" <rickh@Capaccess.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PUPLinux 1.2.14 Umbilical Snip Version
Date: 01 Mar 2002 13:41:00 -0600 [thread overview]
Message-ID: <1015011660.1451.5.camel@localhost.localdomain> (raw)
In-Reply-To: <fc.0085841200327e340085841200327e34.327e56@Capaccess.org>
In-Reply-To: <fc.0085841200327e340085841200327e34.327e56@Capaccess.org>
[-- Attachment #1: Type: text/plain, Size: 3341 bytes --]
Rick,
PUPLinux sounds great!
Does it run on Red Hat?
See ya,
Joe Barr
On Fri, 2002-03-01 at 13:00, Rick A. Hohensee wrote:
> THIS DOES NOT EXIST. I AM NOT DOING THIS. THIS IS A SUGGESTION.
> THIS DOES NOT EXIST. I AM NOT DOING THIS. THIS IS A SUGGESTION.
> THIS DOES NOT EXIST. I AM NOT DOING THIS. THIS IS A SUGGESTION.
>
> I've done some of the harder parts, but I personally am not going to
> saddle them with a unixoid kernel at this point without severe
> provocation. YMMV.
>
> <spastic trombone/banjo/kazoo/forking-penguins fanfare>
>
>
>
> PUPLinux
>
> Personable UniProcessor Linux
>
> 1.2.14 umbilical snip version
>
> FEATURISMING...
>
> * based on Linux 1.2.13
> * ignores POSIX. Aims to further the unix tradition of innovation,
> in conjunction with innovations from Forth, Amiga, and
> <your name here>.
> * converted entirely to the osimplay meta-assembler
> o Therefor builds, if necessary, with nothing but a
> 32 bit post-Korn shell. No dd even. Includes one.
> o Is also therefor x86-only, and 386-max, at least at
> first, but not nearly to the extent that you think.
> * No SMP ever, guaranteed. Not one ASCII byte.
> * EOL = CR,LF
> * dyndufs, appropriate ls included, shows the du of a dir, not the
> less-than-useless 1970 legacy noise the
> innocent user sees now for a dir's "size"
> o block sizes from one byte to Sagans in powers of 2
> * Forth or similar in kernelspace (H3sm and/or Tiny OpenBoot)
> * hard realtime service on NMI
> * More stateful vt's; per-vt text modes, fonts, etc.
> * Dotted Standard File Hierarchy support, DSFH
> * No modules
> * probably no threads, but I'm not sure.
> * Plan-9-style CPU-based "includes" structure, to the extent
> that that pertains to a meta-assembler
> * (back-port?) full UTF-8 support
> * stdaux, FD 3, secondary input for all executables
> * latched (level-triggered) interrupts
> * Forth interpreter syscall(s) on INT 0x81
>
> "Doc, GUIs aren't putting Linux on the desktop."
> "Of course not. The GUI didn't put Windows on "the client". Try the above,
> and call me in the warm new glorious light of morning."
>
> Rick Hohensee
> parts of the above are in
> ftp://ftp.gwdg.de/pub/cLIeNUX
> ftp://ftp.gwdg.de/pub/cLIeNUX/interim read ./ABOUT
>
> My apologies to the perps if there's a real "PUPLinux" somewhere.
> You didn't know penguins had umbilical cords, did you? Ain't l-k grand?
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
#####################################################
| Joe Barr warthawg@austin.rr.com |
| 46DD E7E9 3F65 0ECB CF45 847A 01DF EB92 DDE9 15FE |
#####################################################
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-03-01 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 19:00 Rick A. Hohensee
2002-03-01 19:41 ` Joe Barr [this message]
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=1015011660.1451.5.camel@localhost.localdomain \
--to=warthawg@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rickh@Capaccess.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®