9front - general discussion about 9front
 help / color / mirror / Atom feed
From: tony@instaview.com
To: 9front@9front.org
Subject: Re: [9front] Debian port of Plan 9
Date: Mon, 1 Dec 2014 17:24:51 -0500	[thread overview]
Message-ID: <b7dff157b9c6497d1a9e1cef8fe5f50f.squirrel@box718.bluehost.com> (raw)
In-Reply-To: <547BCB9A.8090301@ix.netcom.com>

Ack... No.

> Hi list,
>
> I'm still new to Plan 9. My current desktop is Debian, so I am looking
> for way to combine both interests.
>
> How feasible would it be to do a Debian port of Plan 9, like the Debian
> GNU/Hurd experimental port, and how suitable would 9front be as a
> starting point?
>
> If this happens, I see 9front as an upstream source for Debian, not a
> competing project. I'm looking at 9front because it looks like the most
> active Plan 9 project at the moment.
>
> A Debian port would entail:
>
>   - multiple architecture support
>   - porting the packaging system (dpkg/apt)
>   - porting all the apps
>   - adding the missing drivers
>   - following Debian policy and release schedule
>   - finding Debian developers who will sponsor and sustain the port
>
> I don't know anything about getting approval for such a project, but
> if it happens I think there will be a lot of interest. Debian seems like
> a natural fit because it is the only distro (that I know of) that
> supports alternate OSs and kernels, and Plan 9 would be the first to
> do both. The port could also be done unofficially, but it would have
> less visibility and support.
>
> There are many porting issues. A large number of Debian apps use dbus,
> so that might be a biggest obstacle to porting (this is a general
> problem in Debian ports). Could 9p be used instead as a dbus
> replacement? I don't know much about either protocol, but 9p seems like
> a more professionally engineered solution.
>
> Unix APIs, POSIX and FHS are also porting issues to contend with, but I
> am hoping the Plan 9 for User Space will alleviate some of those. For
> graphics apps, could ports be done from one of the frame buffer
> ports, like the Debian ARM port? I have more questions, but I'll stop
> there. Thanks,
>
> Marty
>




  parent reply	other threads:[~2014-12-01 22:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  1:59 Marty
2014-12-01  2:00 ` [9front] " Jacob Todd
2014-12-01  2:11 ` Daniel Camolês
2014-12-01  2:34 ` Kurt H Maier
2014-12-01  2:46 ` Justin Ennen
2014-12-01 22:24 ` tony [this message]
2014-12-01  4:09 sl
2014-12-02  7:33 ` Marty
2014-12-02 20:24   ` David L. Craig
2014-12-02 20:33 sl
2014-12-02 20:40 ` David L. Craig

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=b7dff157b9c6497d1a9e1cef8fe5f50f.squirrel@box718.bluehost.com \
    --to=tony@instaview.com \
    --cc=9front@9front.org \
    /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).