9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roderick <hruodr@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port : complete system : kernel : freebsd || linux ?
Date: Tue,  2 Oct 2018 14:32:25 +0000	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.1810021428430.1260@fbsd.local> (raw)
In-Reply-To: <20181002113028.kucfal5ffcjjk7ky@v520.kathe.in>


I think it is uninteresting: one can always install plan9port in a
meager installation of openbsd, freebsd or linux.

More interesting is to have the original plan9 and perhaps a virtual
machine on it to run one of the above OS and their software.

Unfortunately I am having problems installing plan9. It seems to be
very selective on the hardware.

Rodrigo




On Tue, 2 Oct 2018, Mayuresh Kathe wrote:

> i had been trying to work with a collaborator to develop a complete,
> installable system for plan9port.
>
> while initially being quite gung-ho about linux, an accidental discovery
> and ensuing experiements show the freebsd environment to be a lot more
> performant and responsive, almost as much as netbsd for something like a
> plan9port system.
>
> wish to ask the community that if such a system were to be successfully
> developed and distributed with source and free of cost, would it be
> welcomed or most would not even bother to look at?
>
> also, if there's enough interest, would there be someone out here
> capable enough to support netbsd-amd64?
>
> thanks,
>
> ~mayuresh
>
>
>



  parent reply	other threads:[~2018-10-02 14:32 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 11:30 Mayuresh Kathe
2018-10-02 12:01 ` Lucio De Re
2018-10-02 12:11   ` Mayuresh Kathe
2018-10-02 12:43     ` Lucio De Re
2018-10-02 14:26       ` Mayuresh Kathe
2018-10-02 14:32 ` Roderick [this message]
2018-10-02 14:43   ` hiro
2018-10-02 14:40     ` Roderick
2018-10-02 16:35   ` Iruatã Souza
2018-10-02 14:41 ` Dave MacFarlane
2018-10-02 17:14   ` Ethan Gardener
2018-10-02 17:22   ` Bakul Shah
2018-10-02 17:26     ` Steve Simon
2018-10-02 18:10       ` hiro
2018-10-02 19:18         ` Kurt H Maier
2018-10-03 21:23 ` Aram Hăvărneanu
2018-10-04  3:44   ` Mayuresh Kathe
2018-10-04  8:01     ` Ethan Gardener
2018-10-05  1:44     ` Bakul Shah
2018-10-04  3:49 sl
2018-10-04  5:13 ` Mayuresh Kathe
2018-10-04  5:32   ` Iruatã Souza
2018-10-04  7:38 ` Aram Hăvărneanu
2018-10-04  7:50   ` Rui Carmo
2018-10-04  8:39     ` Ethan Gardener
2018-10-04  8:50     ` Kurt H Maier
2018-10-04 10:33       ` Rui Carmo
2018-10-04 16:31         ` Iruatã Souza
2018-10-04 17:00           ` hiro
2018-10-04 18:02             ` Steve Simon
2018-10-04 18:34               ` Aram Hăvărneanu
2018-10-04 19:21               ` Steven Stallion
2018-10-04 19:41                 ` Skip Tavakkolian
2018-10-04 20:20                   ` hiro
2018-10-04 20:57                     ` Steven Stallion
2018-10-04 20:36                   ` Alexander Keller
2018-10-04 21:00                     ` hiro
2018-10-04 20:55                 ` Aram Hăvărneanu
2018-10-04 17:42         ` Kurt H Maier
2018-10-04 21:56 sl

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=alpine.BSF.2.21.9999.1810021428430.1260@fbsd.local \
    --to=hruodr@gmail.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).