9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] success with 9vx from a terminal
Date: Tue, 11 Nov 2008 20:10:58 -0800	[thread overview]
Message-ID: <78C60DD0-DC53-41CE-AA5B-2332191A4E23@sun.com> (raw)
In-Reply-To: <293e3598f5d2998c03d90e1dae8428c7@quanstro.net>

On Nov 10, 2008, at 3:27 PM, erik quanstrom wrote:
>> At least in case of cpu(1) the magic is a bit perverse and quite
>> unlike the rest of the system. The way notes are managed make
>> a local end of a cpu(1) jump through considerable hoops in order
>> for the notes to be properly delivered. That was a sad discovery.
>>
>> Another discovery was that devcons.c could have made DEL work
>> but decided not to :-(
>
> talking about it is the easy part.  why don't you code something up?


Good question. I guess the easiest way to explain would be that
I am not actually using Plan9 for anything as a standalone system,
but rather as a source of inspiration (yeah, may be it is lame to say
something like that -- but here I'm saying it anyway). Everytime I
have to implement something for Solaris/Linux I usually take
a look (unless I remember) at how similar things were handled
by Plan9. Most of the things I've looked at are true gems in terms of
ideas and coding. Really, really elegant stuff.

A small number of things, however, make me go "Huh?". Which is,
usually, a sign of me not being smart enough to instantly recognize
the constraints these things are dealing with. But how am I to know
for certain that they are not the rarest case of an oversight?

One way would be, as you suggested, to start hacking things up
and coming up with better solution. I suspect that in 90% of the
cases I would end up fully appreciating why it was coded the
way it was. That would be the .u way ;-) Very rewarding, but also
quite time consuming.

Another way (which I try NOT to abuse) is to talk about it here.
In the hopes that even if I'm making a total fool out of myself there
will be somebody idle enough to quickly enlighten me.

Does that sound fair to you?

Thanks,
Roman.

P.S. I would love to have any project related to Plan9/Inferno proper
as my day job, but right now I'm reduced to UNIX and 9P
at best :-(



  reply	other threads:[~2008-11-12  4:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  8:35 Chris Brannon
2008-10-22 16:54 ` andrey mirtchovski
2008-10-22 17:56   ` andrey mirtchovski
2008-10-22 17:56   ` erik quanstrom
2008-10-22 18:52     ` andrey mirtchovski
2008-10-22 23:43   ` Roman V. Shaposhnik
2008-11-09 16:55     ` sqweek
2008-11-09 20:50       ` Charles Forsyth
2008-11-10 22:24       ` Roman V. Shaposhnik
2008-11-10 22:49         ` ron minnich
2008-11-10 22:50           ` Roman V. Shaposhnik
2008-11-10 23:14             ` ron minnich
2008-11-10 23:42             ` andrey mirtchovski
2008-11-11  0:42               ` Roman V. Shaposhnik
2008-11-11  1:04                 ` andrey mirtchovski
2008-11-11 16:47                   ` ron minnich
2008-11-10 23:27         ` erik quanstrom
2008-11-12  4:10           ` Roman Shaposhnik [this message]
2008-10-22  9:15 gdiaz
2008-10-22  9:18 ` Christian Kellermann
2008-10-22 11:42 erik quanstrom
2008-10-22 12:25 ` roger peppe
2008-10-22 14:22 ` john
2008-10-22 16:28   ` erik quanstrom
2008-10-22 16:35     ` Roman V. Shaposhnik
     [not found] <0bff7fbe9fa7f6b6305adedeba12e019@quanstro.net>
2008-10-22 12:01 ` Christian Kellermann

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=78C60DD0-DC53-41CE-AA5B-2332191A4E23@sun.com \
    --to=rvs@sun.com \
    --cc=9fans@9fans.net \
    /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).