9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jacob Todd <jaketodd422@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Noob says Hi ..
Date: Thu, 13 Jan 2011 09:43:17 -0500	[thread overview]
Message-ID: <AANLkTi=aifHRs=jjmsq2LerTx6WrLqU0Z8Ho=Y=doFGA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101130719230.3710@fryrpg-zna>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

On Jan 13, 2011 9:32 AM, "Duke Normandin" <dukeofperl@ml1.net> wrote:
>
> Hello 9fans ...
>
> I'm _totally_ new to Plan9! Two days ago I had never heard of
> it. Yesterday I DLed the LiveCD - now I want to know more.
>
> The closest I've come to such an OS as Plan9, is the Native Oberon
> OS. I have a partition which I can overwrite. Does the LiveCD
> installation process allow me to abort the process if I see that
> things are not proceeding smoothly (like I need to gather some
> hardware info, etc)?
>
You can, just reboot with ^t rr. ;)

> Should I be installing Lucent's Plan9 or a more recent derivative, if
> any?
>
There's a iso by erik quanstrom called 9atom. It has some extra hardware
support. Just google 9atom

> Is there software available for this OS? Or do I have to write my own?
>
There's plenty of software. Most of it is in contrib.

> What is the primary development language for Plan9? C? What languages
> have been ported to Plan9?
Ansi c with some changes.

>
> Where are the best docs? TIA...
See /sys/doc and the wiki. Also, you may want to google 9.intro.pdf.

[-- Attachment #2: Type: text/html, Size: 1382 bytes --]

  parent reply	other threads:[~2011-01-13 14:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 14:30 Duke Normandin
2011-01-13 14:38 ` andrey mirtchovski
2011-01-13 15:15   ` Duke Normandin
2011-01-13 14:43 ` Jacob Todd [this message]
2011-01-13 15:10   ` Duke Normandin
2011-01-13 15:12     ` erik quanstrom
2011-01-13 15:33       ` Duke Normandin
2011-01-13 15:40         ` Gorka Guardiola
2011-01-13 15:44           ` erik quanstrom
2011-01-13 15:59             ` Duke Normandin
2011-01-13 15:42         ` Tassilo Philipp
2011-01-14  0:05         ` Federico G. Benavento
2011-01-14  0:31           ` Duke Normandin
2011-01-13 16:06 Duke Normandin
2011-01-13 16:51 ` Tassilo Philipp
2011-01-13 18:21   ` Duke Normandin
     [not found] ` <dcb4736d2e43c99bcf89af37a9d0addd-EhVcXl1ERwBcRx0AAAwEUR8fGQlVS19>
2011-01-13 16:56   ` erik quanstrom
2011-01-13 17:32     ` Skip Tavakkolian
2011-01-13 17:48       ` erik quanstrom
2011-01-13 18:20     ` Duke Normandin

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='AANLkTi=aifHRs=jjmsq2LerTx6WrLqU0Z8Ho=Y=doFGA@mail.gmail.com' \
    --to=jaketodd422@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).