9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Google finally announces their lightweight OS
Date: Wed,  8 Jul 2009 22:04:30 +0200	[thread overview]
Message-ID: <5d375e920907081304y72741f00of20a7abf6d695d4b@mail.gmail.com> (raw)
In-Reply-To: <9ab217670907081256i55d08aa7v86d4eb7348a080f4@mail.gmail.com>

On Wed, Jul 8, 2009 at 9:56 PM, Devon H. O'Dell<devon.odell@gmail.com> wrote:
> 2009/7/8 Uriel <uriel99@gmail.com>:
>> On Wed, Jul 8, 2009 at 6:56 PM, Devon H. O'Dell<devon.odell@gmail.com> wrote:
>>> I don't think so. We already have IPv6 support and it's not that bad.
>>> Having more drivers and supported commodity architectures would be a
>>> good thing. I'd love to do this, but I don't think anybody's going to
>>> match my salary to port drivers, do ACPI, add amd64 support for
>>> workstations, etc.
>>
>> ACPI will never, ever, ever happen, so people better get over it (and
>> if anyone is naive enough to waste their time trying, it will end up
>> as a useless atrocious mess that wont boot even in a 100th of the
>> systems out there, much less suspend or do anything useful).
>
> ACPI support doesn't need to suspend or do thermal zones. It just
> needs to be able to read the ADT and get MP / interrupt routing table
> information. This is doable. Have you ever read any of the ACPI spec?
> I have.

The spec doesn't matter much, given that most BIOS out there totally ignore it.

>> As for amd64, it is already done, we are just not worthy to have access to it.
>
> Without this getting into a holy war, what Geoff told me was that the
> amd64 work was for headless CPU servers, which is only mildly useful
> to me anyway.

If it was released perhaps somebody would add the missing drivers, who knows...

As things stand, we will never know.

uriel



  reply	other threads:[~2009-07-08 20:04 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08  7:48 Aharon Robbins
2009-07-08  8:48 ` tlaronde
2009-07-08  9:02   ` Richard Miller
2009-07-08  9:23     ` tlaronde
2009-07-08  9:41       ` Richard Miller
2009-07-08 10:33         ` Uriel
2009-07-08 12:39         ` erik quanstrom
2009-07-08  9:28     ` Anselm R Garbe
2009-07-08 10:22     ` Uriel
2009-07-08 10:40       ` Richard Miller
2009-07-08 11:05         ` Uriel
2009-07-08 11:34           ` Anselm R Garbe
2009-07-08 12:07     ` erik quanstrom
2009-07-08 15:07     ` David Leimbach
2009-07-08 16:15     ` Balwinder S Dheeman
2009-07-08 16:27       ` erik quanstrom
2009-07-08 16:56         ` Devon H. O'Dell
2009-07-08 19:34           ` erik quanstrom
2009-07-08 19:41             ` Devon H. O'Dell
2009-07-08 19:47               ` erik quanstrom
2009-07-08 19:56               ` Uriel
2009-07-08 20:44                 ` Noah Evans
2009-07-08 21:14                 ` Dan Cross
2009-07-08 21:23                   ` Devon H. O'Dell
2009-07-08 19:50           ` Uriel
2009-07-08 19:56             ` Devon H. O'Dell
2009-07-08 20:04               ` Uriel [this message]
2009-07-08 20:10                 ` Devon H. O'Dell
2009-07-08 20:19                   ` ron minnich
2009-07-08 20:25                 ` Benjamin Huntsman
2009-07-08 20:30                   ` Devon H. O'Dell
2009-07-08 20:44                     ` Benjamin Huntsman
2009-07-08 20:32                 ` John Floren
2009-07-08 22:21                   ` Jason Catena
2009-07-08 22:41                     ` Venkatesh Srinivas
2009-07-09  4:10                     ` erik quanstrom
2009-07-09  5:43                       ` Jason Catena
2009-07-09 17:48                         ` Micah Stetson
2009-07-09 17:50                           ` Devon H. O'Dell
2009-07-09 17:50                           ` erik quanstrom
2009-07-09 19:47                           ` Jason Catena
2009-07-09 20:29                             ` tlaronde
2009-07-09 20:58                               ` Jason Catena
2009-07-09 21:34                               ` erik quanstrom
2009-07-09 21:44                                 ` Jack Johnson
2009-07-10  4:21                                   ` Bakul Shah
2009-07-09 21:59                                 ` Jason Catena
2009-07-09 22:18                                   ` erik quanstrom
2009-07-10  6:32                                     ` tlaronde
2009-07-09 12:45                       ` Eric Van Hensbergen
2009-07-09 15:24                       ` David Leimbach
2009-07-08 20:11             ` ron minnich
2009-07-08 20:43             ` Francisco J Ballesteros
2009-07-08 20:59               ` Devon H. O'Dell
2009-07-08 21:04                 ` Francisco J Ballesteros
2009-07-08 17:34         ` Dan Cross
2009-07-08 17:52           ` ron minnich
2009-07-08 19:30             ` erik quanstrom
2009-07-08 19:40               ` Devon H. O'Dell
2009-07-08 20:09               ` ron minnich
2009-07-08 16:12   ` Balwinder S Dheeman
2009-07-08  9:04 ` Charles Forsyth
2009-07-10  6:32 Akshat Kumar
2009-07-10 12:02 ` Anthony Sorace
2009-07-10 12:14   ` erik quanstrom
2009-07-10 12:52     ` Robert Raschke
2009-07-10 17:11       ` Ethan Grammatikidis
2009-07-10 19:54       ` Richard Miller
2009-07-10 19:14     ` Bakul Shah

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=5d375e920907081304y72741f00of20a7abf6d695d4b@mail.gmail.com \
    --to=uriel99@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).