From: Rick Hohensee <humbubba@smarty.smart.net>
To: linux-kernel@vger.kernel.org
Subject: Re: __KERNEL__ removal
Date: Sat, 14 Jul 2001 19:10:30 -0400 (EDT) [thread overview]
Message-ID: <200107142310.TAA07985@smarty.smart.net> (raw)
>Jeff Garzik
>If there -must- be parts of the kernel that are visible to userspace,
>yes, we should separate them and make that separation obvious. I would
>not call our current setup obvious :)
There are. -must-. Plan 9 minimizes them. It ain't POSIX, I'm guessing,
never having seen a POSIX in real life myself. I do happen to have K&R2
right here though. Hmmm, unistd.h is not in the 89 spec. Well of course
not. It's not C. You need need need that (which is why I did libsys.a),
and I think Plan 9 has a thing that lays out calling conventions for
syscalls, and some other things about the local CPU. Actually, Plan 9 lays
out lots of CPUs, being heterogenously distributed. That's where I get
dizzy, and start to wax unix-traditional. With all my twisted antics, I've
never cross-compiled anything. You also need ioctls for userland probably,
which Plan 9 either doesn't have or they actually figured out how to hide
them.
There's also a level below unistd.h maybe. A libcpu or something. Dono.
Rick Hohensee
www.clienux.com
next reply other threads:[~2001-07-14 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 23:10 Rick Hohensee [this message]
2001-07-14 23:26 ` __KERNEL__ removal Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-07-14 17:33 (patch-2.4.6) Fix oops with Iomega Clik! (ide-floppy) Alan Cox
2001-07-14 17:38 ` Jeff Garzik
2001-07-14 18:04 ` __KERNEL__ removal Jonathan Lundell
2001-07-14 18:19 ` Jeff Garzik
2001-07-14 18:30 ` Mo McKinlay
2001-07-15 11:53 ` Kai Henningsen
2001-07-15 13:12 ` Chris Wedgwood
2001-07-15 14:21 ` Horst von Brand
2001-07-16 9:16 ` Chris Wedgwood
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=200107142310.TAA07985@smarty.smart.net \
--to=humbubba@smarty.smart.net \
--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