From: andrey mirtchovski <mirtchovski@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 07:38:24 -0700 [thread overview]
Message-ID: <AANLkTikBrr9bVk7w5S5EhQOCddk5h8qF8ohZh+bLRV1p@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101130719230.3710@fryrpg-zna>
When you boot the live cd you'll have a pretty good idea whether your
system is supported -- if things are OK you'll get to a gui with
installation information. You'll be able to figure out whether you
want to try it or not even before you get to the hard drive
partitioning :)
There's no 'other plan9', WYSIWYG. There's another installation cd
with slightly more supported hardware called '9atom'. You can try that
if the current one doesn't work.
Failing the CD path, you can download 9vx and try the full Plan 9
environment hosted on your normal OS.
cheers
On Thu, Jan 13, 2011 at 7:30 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)?
>
> Should I be installing Lucent's Plan9 or a more recent derivative, if
> any?
>
> Is there software available for this OS? Or do I have to write my own?
>
> What is the primary development language for Plan9? C? What languages
> have been ported to Plan9?
>
> Where are the best docs? TIA...
>
> --
> Duke Normandin
> Turner Valley, Alberta, Canada
>
>
next prev parent reply other threads:[~2011-01-13 14:38 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 [this message]
2011-01-13 15:15 ` Duke Normandin
2011-01-13 14:43 ` Jacob Todd
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=AANLkTikBrr9bVk7w5S5EhQOCddk5h8qF8ohZh+bLRV1p@mail.gmail.com \
--to=mirtchovski@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).