9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sl@9front.org
To: 9fans@9fans.net
Subject: Re: [9fans] There is no fork
Date: Wed, 14 Feb 2018 09:37:12 -0500	[thread overview]
Message-ID: <7D7DD795FCACD03C69AD16416271610F@5ess.inri.net> (raw)
In-Reply-To: D3CB83A6-32DB-4D5B-B358-BC6A098F85BD@gmail.com

On Feb 14, 2018, at 2:18 AM, Rui Carmo <rui.carmo@gmail.com> wrote:

> On 14 Feb 2018, at 00:31, sl@9front.org wrote:
> 
>> 1.) is the wrong approach.  Just build inside Plan 9.
> 
> You missed the rest of the thread.

I read the entire thread but I didn’t see this point specifically
addressed.  From the latest posts it is still unclear where you plan
to do the compiling.

Okay, so let’s stipulate compiling on Plan 9.  Unless I missed it, the
relationship between your automated tools on the Linux host and the
build on the Plan 9 guest (for example, how they will communicate)
hasn’t been mentioned at all.  That’s why I brought up the 9front fork
of drawterm as a possible facilitator.  It can handle 9front’s new
auth scheme and it can run individual commands.  Lacking something
like this, how else do you plan to control the build on Plan 9?

It also wasn’t clear to me that you’ve spent any significant time
actually using Plan 9.  It might even be a good idea to use the system
for a while, even without all the external automation, to figure out
if any of this is even worth your time.  A lot of people find they
don’t like Plan 9 once they get here.

Anyway, good luck with whatever your ultimate goal is.

sl



             reply	other threads:[~2018-02-14 14:37 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 14:37 sl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-14  0:31 sl
2018-02-14  7:18 ` Rui Carmo
2018-02-13 14:15 sl
2018-02-12 23:48 sl
2018-02-13  3:06 ` Lucio De Re
2018-02-13  9:31   ` Rui Carmo
2018-02-13 10:43     ` Lucio De Re
2018-02-13 11:05       ` hiro
2018-02-13 11:07         ` hiro
2018-02-13 11:13           ` hiro
2018-02-13 13:45           ` Lucio De Re
2018-02-13 14:35             ` hiro
2018-02-13 16:09               ` Lucio De Re
2018-02-13 15:10         ` Rui Carmo
2018-02-13 15:22           ` Lucio De Re
2018-02-13 16:25           ` Kurt H Maier
2018-02-13 17:01             ` Rui Carmo
2018-02-13 18:12               ` Kurt H Maier
2018-02-13 18:21                 ` Rui Carmo
2018-02-13 19:10                   ` Kurt H Maier
2018-02-13 23:37                     ` Rui Carmo
2018-02-14  9:09                       ` Steve Simon
2018-02-14 11:10                         ` Lucio De Re
2018-02-14 11:32                           ` hiro
2018-02-14 13:53                             ` Ethan Grammatikidis
2018-02-13 19:14                   ` hiro
2018-02-13 18:16           ` Steve Simon
2018-02-13 18:46             ` Bakul Shah
2018-02-10  2:48 Benjamin Huntsman
2018-02-10  4:24 ` Lucio De Re
2018-02-10 10:43   ` Ethan Grammatikidis
2018-02-10  4:43 ` Jens Staal
2018-02-10 10:46   ` hiro
2018-02-10 10:51     ` Ethan Grammatikidis
2018-02-10 11:59       ` hiro
2018-02-10 14:54         ` Ethan Grammatikidis
2018-02-10 12:03       ` as
2018-02-11 12:26 ` Giacomo Tesio
2018-02-11 13:48   ` Rui Carmo
2018-02-11 22:40   ` Lyndon Nerenberg
2018-02-11 23:48   ` Benjamin Huntsman
2018-02-12  0:20     ` Giacomo Tesio
2018-02-12  0:58       ` Benjamin Huntsman
2018-02-12  1:10       ` Ethan Grammatikidis
2018-02-12  8:33         ` Giacomo Tesio
2018-02-12 13:05           ` Ethan Grammatikidis
2018-02-12 13:39             ` Lucio De Re
2018-02-13 13:59               ` Ethan Grammatikidis
2018-02-12 15:21             ` Giacomo Tesio
2018-02-12 15:50               ` Chris McGee
2018-02-12 16:13               ` tlaronde
2018-02-12 18:51                 ` Steve Simon
2018-02-12 20:40                 ` Giacomo Tesio
2018-02-12 23:49                   ` Benjamin Huntsman
2018-02-14 13:17               ` Ethan Grammatikidis
2018-02-14 13:57     ` Erik Quanstrom

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=7D7DD795FCACD03C69AD16416271610F@5ess.inri.net \
    --to=sl@9front.org \
    --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).