From: Vester Thacker <vester.thacker@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] browse /sys/src
Date: Wed, 26 Jan 2005 18:01:06 +0900 [thread overview]
Message-ID: <32a656c2050126010130a014a4@mail.gmail.com> (raw)
In-Reply-To: <d7b3771331fde107bfd315e256b31d71@granite.cias.osakafu-u.ac.jp>
On Wed, 26 Jan 2005 15:44:37 +0900, Kenji Okamoto
<okamoto@granite.cias.osakafu-u.ac.jp> wrote:
> I should be more full to explain my thoughts on this issue.
>
> 1) Do we need to expertize Plan 9 distribution more?
>
> No, these decade history of Plan 9 revealed we don't.
> Plan 9 is for someone who really want it.
We can agree to disagree, but I say 'Yes' to the question. There are
areas where Plan 9 needs to be improved to stay current. I believe it
is important to change with the times. For example, more and more
machines today are sold without a floppy drive. This makes it
difficult to pass parameters, as with an edited plan9.ini on a boot
floppy, if you're doing a CD only install. Of course, Plan 9 can still
be installed but at a greater cost in time and effort. Why not revise
a method/tool if it is possible? Having an installation that also
serves as an aptitude test is a dumb idea. "A program should do one
thing well", I forgot who said that originally.
> 2) sources is not enough for dowloading things for us?
>
> I don't think so.
> It seems not so large amount of downloders of Plan 9.☺
Viewing sources via http and seeing changes over time is helpful to
some people. Granted, not everyone is a programmer. But if a few
programmers find it useful, then I say why not give them an easy to
view resource.
On another note, I wonder how often Plan 9 sources will appear when
doing a Google search for a C reserve word. ;-)
> 3) Do we need another host to prepare when the sources will appear?
>
> Maybe. if so, Yamanashi-san がんばれ!
It never hurts to be prepared. If Lucent was ever to give up Plan 9
and request the Plan 9 community to move the source tree out of the
Labs, then Plan 9 would have a happy home in Japan. Of course, only if
it meets the approval of the Plan 9 community. ;-)
> 4) Other downlod site may make the difficulty more?
>
> Yes, now it's not so easy to maintain the consistency between
> source trees.
There is only one true source tree, the one at Lucent, everything else
is a mirror image. Consistency is an issue, but a manageable one.
-vester
next prev parent reply other threads:[~2005-01-26 9:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 5:44 YAMANASHI Takeshi
2005-01-26 5:48 ` Kenji Okamoto
2005-01-26 5:54 ` Kenji Okamoto
2005-01-26 6:11 ` andrey mirtchovski
2005-01-26 6:24 ` Kenji Okamoto
2005-01-26 6:44 ` Kenji Okamoto
2005-01-26 6:53 ` andrey mirtchovski
2005-01-26 7:01 ` Kenji Okamoto
2005-01-26 9:01 ` Vester Thacker [this message]
2005-01-27 1:51 ` Kenji Okamoto
2005-01-26 8:49 ` Skip Tavakkolian
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 5:03 YAMANASHI Takeshi
2005-01-26 5:07 ` Kenji Okamoto
2005-01-26 5:09 ` Kenji Okamoto
2005-01-26 4:09 YAMANASHI Takeshi
2005-01-26 2:57 YAMANASHI Takeshi
2005-01-26 3:03 ` andrey mirtchovski
2005-01-26 3:30 ` Kenji Okamoto
2005-01-26 3:38 ` Devon H. O'Dell
2005-01-26 3:51 ` Kenji Okamoto
2005-01-26 2:09 YAMANASHI Takeshi
2005-01-26 2:00 YAMANASHI Takeshi
2005-01-26 2:27 ` Kenji Okamoto
2005-01-26 2:31 ` Michael H. Collins
2005-01-26 2:45 ` boyd, rounin
2005-01-26 3:50 ` Russ Cox
2005-01-26 4:28 ` Kenji Okamoto
2005-01-26 4:39 ` Kenji Okamoto
2005-01-26 8:49 ` Skip Tavakkolian
2005-01-26 10:00 ` Matthias Teege
2005-01-26 9:55 ` Fco. J. Ballesteros
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=32a656c2050126010130a014a4@mail.gmail.com \
--to=vester.thacker@gmail.com \
--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).