9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Digby Tarvin digbyt@acm.org
Subject: The future of Plan9?
Date: Fri,  2 May 1997 13:26:12 +0100	[thread overview]
Message-ID: <19970502122612.5kIhAdUciqbv1SVaH818PXaQ2n405J4_aMQiheVpbxs@z> (raw)

Steve's comments:
>
>> [Plan 9's] main failing,
>> in my opinion, is its inability to interact with other operating
>> systems conveniently.
>
>I don't think the other operating system is a problem, because
>most users aren't concerned with it. They just use it for kicking
>off their main applications. The interchange of data is the important
>thing.
>
I should have said that this was the biggest problem for me. I don't
know how others are using it. When I kick off my main applications,
I need to be able to interact with them. Having found hp(1), this is
now just a problem for graphical apps. And it is still a problem
accessing and running plan 9 apps from an external non-plan9 system.

>
>> At least the
>> wealth of quality free software available on the net makes developing
>> alternate operating systems less of a daunting task than it used to
>> be - only the core has to be build, and a quite usable suite of
>> applications can be readily ported by a user community.
>
>Huh? If I understand you, you're saying that one can bash out a
>new kernel, and then chuck all the standard freebie tools on top
>of it. Ok, so this is handy for researchers into OS development,
>but apart from that, what does it give you that you haven't
>already got? [Bzzzt! Warning: heading off-topic]
>
That is mostly what I had in mind. I used to tinker with
operating systems when I was at University, and the thing
that always seemed to be the obstacle to making a usable system
was the thought of having to write all the compilers, editors
and utilities from scratch. I had access to Unix sources, but nothing
that could be redistributed.  Now at least it is only a porting
effort. But it only gets you the level of funtionality of plan 9,
certainly not what you need to compete with M$ in commercial
applications :-/


Regards,
DigbyT
-- 
Digby R. S. Tarvin                                              digbyt@acm.org
http://www.users.dircon.co.uk/~cthulhu/




             reply	other threads:[~1997-05-02 12:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-02 12:26 Digby [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-05-08  4:39 Adam
1997-05-06  0:45 Eric
1997-05-05 14:02 Brandon
1997-05-04  9:04 Markus
1997-05-02 22:04 Bengt
1997-05-02  0:59 Digby
1997-05-01 19:14 Greg
1997-05-01 18:28 Eric
1997-05-01 16:04 Berry
1997-05-01 15:25 Tom
1997-05-01 12:46 bwong
1997-05-01  7:45 Steve_Kilbane
1997-05-01  3:54 Digby
1997-04-30 23:48 Scott
1997-04-30 21:11 rsc
1997-04-30 20:09 Lucio
1997-04-30 17:06 Digby
1997-04-30  7:38 Borja
1997-04-30  6:01 Brandon
1997-04-29 23:28 Alex
1997-04-29 23:06 Digby

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=19970502122612.5kIhAdUciqbv1SVaH818PXaQ2n405J4_aMQiheVpbxs@z \
    --to=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).