9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] alright, this should be interesting
Date: Tue, 19 Oct 2004 18:01:30 -1000	[thread overview]
Message-ID: <Pine.BSI.4.58.0410191746410.12265@malasada.lava.net> (raw)
In-Reply-To: <FE3466B8-2224-11D9-9370-000D9336F3FE@anvil.com>

> Tim,
> You are missing the point of what I said:

I must be, because I still dont agree with your point.

> In other words, if you have a crufty kernel, you'll have a smelly
> compiler,
> and vice-versa.

Why?  You could build a fresh smelling compiler like 8c/8a/8l.

> >> kencc wouldn't have happened on linux, for example.
>
> i.e. if you have just implemented the 15th optional parameter to
> the
> asynciowithorwithoutsignalandoptionalscattergatherfromthe19thaddresszone
> () system call,

You don't need to change any of the system calls to build an emulation
layer.

> which supplies a bitmask of signal numbers and the days of the week on
> which to send them in the event of there being a 'c' in the month name,
> then adding the
> __asm____stuff___3_registers_and_a_status_mask_up_your_nose() inline to
> gcc to make it run 10 times faster
> seems like a ReallyGoodIdea(tm).

You dont have to play with gcc/gas cruft either.

> > The "personality" can be completely isolated from the kernel.
>
> Yes, but you've still gotta struggle through six piles of elephant
> excrement to get there,
> by which time your brain is soup, and you're muttering about how to
> implement a 15th way to map
> all the odd-numbered framebuffers into someone else's address space.

Now, I'm not saying that working through six piles of elephant
excrement is easy, but some of us do this for work on a daily basis.
So yah, the person who wrote the emulation layer would have to
get their feet wet, but the users of an emulation layer hardly
need to worry about such things.

> Well, we're talking oranges and (Posix-compliant) apples, so it's hard
> to agree:
> you're talking about implementations, I'm talking about philosophical
> approaches to problem solving.

Perhaps this is why I don't see your point...

but.. if you were to go in to work one day and found that some
linux (*bsd, slolaris, win32, etc..) box that you used on a daily
basis was running a plan9 emulation layer that was running rio,
acme, 9p and the whole shebang, how would it matter to you what
was under the covers?

> 	DaveL.

Tim N.


  reply	other threads:[~2004-10-20  4:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 17:36 andrey mirtchovski
2004-10-06  1:07 ` Kenji Okamoto
2004-10-06  1:25   ` andrey mirtchovski
2004-10-06  5:25     ` geoff
2004-10-06  7:52   ` C H Forsyth
2004-10-18 16:05     ` Leo Caves
2004-10-19  2:50       ` Kenji Okamoto
2004-10-19 15:44         ` Ronald G. Minnich
2004-10-19 15:57           ` Dave Lukes
2004-10-19 19:45             ` Tim Newsham
2004-10-19 21:22               ` Ronald G. Minnich
2004-10-19 22:47                 ` Charles Forsyth
2004-10-19 23:39                   ` Dave Lukes
2004-10-20  3:25                 ` Tim Newsham
2004-10-20  9:46                   ` Steve Simon
2004-10-20 14:20                     ` Russ Cox
2004-10-20 19:47                   ` Ronald G. Minnich
2004-10-20 20:29                     ` Ronald G. Minnich
2004-10-20 20:41                     ` boyd, rounin
2004-10-21  1:31                     ` Tim Newsham
2004-10-21 16:19                       ` Ronald G. Minnich
2004-10-19 23:17               ` Dave Lukes
2004-10-20  4:01                 ` Tim Newsham [this message]
2004-10-20  4:19                   ` Russ Cox
2004-10-20  4:27                     ` Kenji Okamoto
2004-10-20  6:23                     ` Skip Tavakkolian
2004-10-20  7:36                       ` Nigel Roles
2004-10-20 11:20                         ` Dave Lukes
2004-10-20 12:36                           ` Nigel Roles
2004-10-20 13:45                             ` Brantley Coile
2004-10-24  5:33                               ` Dan Cross
2004-10-24 11:53                                 ` Tiit Lankots
2004-10-24 13:44                                   ` Brantley Coile
2004-10-25 11:23                                     ` Dave Lukes
2004-10-20 17:06                         ` Skip Tavakkolian
2004-10-22  7:12                           ` Dave Lukes
2004-10-22 19:02                             ` Jason Gurtz
2004-10-23  1:27                               ` Dave Lukes
2004-10-20 18:40                         ` boyd, rounin
2004-10-20 20:16                           ` Nigel Roles
2004-10-20 20:46                             ` boyd, rounin
2004-10-20 19:59                       ` Ronald G. Minnich
2004-10-20 20:02                         ` Russ Cox
2004-10-20 20:05                           ` Eric Van Hensbergen
2004-10-20 20:25                           ` Charles Forsyth
2004-10-20 20:48                             ` boyd, rounin
2004-10-21 18:36                             ` Dave Lukes
2004-10-21  4:47                           ` William Josephson
2004-10-20 20:44                         ` boyd, rounin
2004-10-23 18:54                           ` Dan Cross
2004-10-20 11:13                     ` Dave Lukes
2004-10-20 11:09                   ` Dave Lukes

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=Pine.BSI.4.58.0410191746410.12265@malasada.lava.net \
    --to=newsham@lava.net \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).