9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Uriel <uriel@berlinblue.org>
To: 9front@googlegroups.com
Subject: Re: alternative compilers
Date: Tue, 21 Jun 2011 16:16:49 +0200	[thread overview]
Message-ID: <BANLkTikU0HFvmBxnJ32-WN4HROJOADj9nw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimdhX+43RQQv__ph9RTEj0eYgHwTg@mail.gmail.com>

On Tue, Jun 21, 2011 at 6:08 AM, Jens Staal <staal1978@gmail.com> wrote:
> (A cool thing I was thinking aobut for PCC on plan9 was actually to
> bring up an alternative *BSD kernel (FreeBSD kernel can apparently be
> compiled with PCC) with glendix-type patches natively on Plan9. This
> "glendie" could thus be an alternative kernel for extended hardware
> support)

If we wanted LSD we would be in Berkeley already.

If you want lunix, get a real lunix.

uriel

P.S.: OpenBSD is actually nice and useful, but makes much more sense
to port the Plan 9 compilers to obsd than the other way around.

  parent reply	other threads:[~2011-06-21 14:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 21:39 ron minnich
2011-06-20 21:49 ` Julius Schmidt
2011-06-20 21:49   ` ron minnich
2011-06-20 21:52     ` Julius Schmidt
2011-06-21 10:01   ` suharik
2011-06-21 10:31     ` Noah Evans
2011-06-21 11:13       ` Uriel
2011-06-21 11:16         ` Noah Evans
2011-06-21 11:23           ` suharik
2011-06-21 13:56           ` Julius Schmidt
2011-06-21 14:36             ` Noah Evans
2011-06-21 14:47               ` Julius Schmidt
2011-06-21 14:50                 ` Noah Evans
2011-06-21 22:21                   ` Iruatã Souza
2011-06-22  8:50                     ` Noah Evans
2011-06-22 10:04                       ` Julius Schmidt
2011-06-22 10:49                         ` Noah Evans
2011-06-22 11:06                           ` Julius Schmidt
2011-06-22 11:10                             ` Uriel
2011-06-22 11:19                               ` Julius Schmidt
2011-06-22 11:15                             ` Noah Evans
2011-06-22 11:29                               ` Uriel
2011-06-22 11:06                           ` Uriel
2011-06-22 12:10                           ` Iruatã Souza
2011-06-22 12:24                             ` Uriel
2011-06-22 12:41                               ` Julius Schmidt
2011-06-22 12:52                                 ` Uriel
2011-06-22 14:54                                   ` Stanley Lieber
2011-06-22 14:56                                     ` John Floren
2011-06-22 14:57                                       ` Stanley Lieber
2011-06-22 15:24                           ` Kurt H Maier
2011-06-22 16:47                             ` Stanley Lieber
2011-06-27  0:34                             ` cinap_lenrek
2011-06-27  0:42                               ` Kurt H Maier
2011-06-22 11:01                         ` Uriel
2011-06-21 14:53                 ` Uriel
2011-06-21 11:12     ` Uriel
2011-06-21 14:05     ` Jacob Todd
2011-06-21  4:08 ` Jens Staal
2011-06-21 13:48   ` Iruatã Souza
2011-06-21 13:58     ` Jens Staal
2011-06-21 14:16   ` Uriel [this message]
2011-06-21 11:14 ` Uriel

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=BANLkTikU0HFvmBxnJ32-WN4HROJOADj9nw@mail.gmail.com \
    --to=uriel@berlinblue.org \
    --cc=9front@googlegroups.com \
    /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).