9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Getting started in Plan9 - help
Date: Mon, 21 Jan 2002 17:15:15 -0500	[thread overview]
Message-ID: <20020121221520.88DFF199E3@mail.cse.psu.edu> (raw)

// ...i cant seem to be able to change it...

in my experience (always?), aux/vga is unable to change the
resolution of a display once it's first been brought up. to get
your display to boot in a different resolution, change the
definition of vgasize in plan9.ini (which generally lives in a
FAT partition or on a floppy; more on that in a minute).

Acessibility:

Plan 9 does not include a web browser or other html
interpreter; look to Vita Nuova's freely-available Inferno
distribution, which includes Charon.

man dossrv(4) for a description of the a:, c:, and 9fat:
scripts which will facilitate, respectivly, access to a floppy
drive, your primary FAT partition, and your plan9 FAT
partition, where configuration information like plan9.ini
is commonly stored.

for example, to edit my plan9.ini, i do this:
	9fat:
	acme -c1 /n/9fat/plan9.ini
	unmount /n/9fat

Shell:

to find a file named "myfile" in /usr/anothy, i do:
	`{du -a /usr/anothy | awk '{print $2}'} | grep myfile
this sort of construction works well for all manner of
tools (although i have on occasion missed find's easy
methods of finding files based on greater/less-than
comparisons). also try
	grep some_string `{du -a /usr/anothy | awk '{print $2}'}
for finding "some_string" in a set of files.

rc has no command completion or history. the design
rational is essentially that this functionality properly
belongs in the windowing system, not the shell, so that
the solution becomes general: it can be applied to every
program that looks for input. while not having history
(and to a lesser extent command completion) took me a
bit of getting used to comming from unix, i do not miss
it, and now strongly prefer the Plan 9 way of giving me
such things.

Keys:

plan 9 terminals are much more mouse-driven than
unix terminals. the current UI basically mandates that
you become comfortable using the mouse alot. the end
result is a much more efficient system - the mouse is
much better at many tasks than moving things around
with a keyboard, even when it doesn't feel like it (there
was a good report on this linked here earlier, but i failed
to make a note of it; anyone?). this is not always true
(folks with various disabilities or motor imparment
being the primary counter-example), but is true the
overwhelming majority of the time, and the system is
designed with that in mind.

the interupt functionality could be moved off del, and
onto something else, like the pause/break key. but
keyboards vary widely, and a replacement would have
to be well-chosen. on most smaller keyboards (like on
laptops), del is a key, while pause/break is often a
pseudo-key.

also, as noted earlier, it's not at all clear what the
"conventional" functionality of del is. on most of my
Unix systems, it produces ^? - far less useful than the
interupt function.

General:

i'm not sure what you're asking WRT plan9 default
boot being "safe" for other OSes. the bootloader plan
9 will install is not a multi-booter - it only finds the
first partition marked "active" (or can there only ever
be one?) and runs that. it will not, however, touch
any data living on other partitions.

there has been wide speculation on why Plan 9 has
not gained greater support than it has. ideas on
this topic vary widely. my own theory is something
along the lines of plan 9 is just too much: it requires
people to understand (or be willing to learn) many
new concepts all at once to really "get it". others
believe it has something to do with licensing terms,
or the attitude of people on 9fans and comp.os.plan9.
there's also the old chicken-and-egg problem: users
aren't interested because of the comparitave lack of
apps, and app developers arn't interested because of
the lack of users. but that's all just speculation.
ア



             reply	other threads:[~2002-01-21 22:15 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 22:15 anothy [this message]
2002-01-22  9:53 ` Douglas A. Gwyn
  -- strict thread matches above, loose matches on Subject: below --
2002-01-24 16:30 Russ Cox
2002-01-24 17:34 ` Thomas Bushnell, BSG
2002-01-23 18:24 Russ Cox
2002-01-24  9:38 ` Thomas Bushnell, BSG
2002-01-22 18:28 David Gordon Hogan
2002-01-23 10:04 ` Douglas A. Gwyn
2002-01-23 18:01   ` Thomas Bushnell, BSG
2002-01-23 18:19     ` Ronald G Minnich
2002-01-23 18:21       ` Scott Schwartz
2002-01-24  9:38       ` Thomas Bushnell, BSG
2002-01-23 18:46     ` Boyd Roberts
2002-01-24  9:38       ` Thomas Bushnell, BSG
2002-01-24 13:01         ` David Arnold
2002-01-24 17:35           ` Thomas Bushnell, BSG
2002-01-24 21:40             ` Dan Cross
2002-01-25 10:00               ` Thomas Bushnell, BSG
2002-01-25 22:56                 ` Dan Cross
2002-01-28 18:26                   ` Boyd Roberts
2002-01-29  9:31                     ` Douglas A. Gwyn
2002-01-24 16:05         ` Boyd Roberts
2002-01-24 17:34           ` Thomas Bushnell, BSG
2002-01-25 10:00     ` Douglas A. Gwyn
2002-01-23 10:48 ` Boyd Roberts
2002-01-23 18:01 ` Thomas Bushnell, BSG
2002-01-22  6:44 okamoto
2002-01-22  2:54 dmr
2002-01-22 11:13 ` Boyd Roberts
2002-01-22 17:39   ` Douglas A. Gwyn
     [not found] <20020121170104.2FABD19A05@mail.cse.psu.edu>
2002-01-21 23:30 ` Andrew Simmons
2002-01-21 22:34 erik quanstrom
2002-01-21 20:39 Russ Cox
2002-01-21 21:16 ` Matt H
2002-01-21 23:39 ` Quinn Dunkan
2002-01-22 15:36 ` cej
2002-01-22 15:42   ` Matt H
2002-01-22 23:02 ` skipt
2002-01-23 10:05   ` Douglas A. Gwyn
2002-01-23 22:28     ` Lyndon Nerenberg
2002-01-21 20:34 presotto
2002-01-21 20:21 Russ Cox
2002-01-21 20:44 ` Mike Haertel
2002-01-21 19:42 David Gordon Hogan
2002-01-21 20:28 ` Matt H
2002-01-25 10:30   ` Ralph Corderoy
2002-01-21 18:48 Russ Cox
2002-01-21 19:58 ` Mike Haertel
2002-01-21 20:05   ` James A. Robinson
2002-01-21 10:01 Re[2]: " steve.simon
2002-01-21 10:28 ` Boyd Roberts
2002-01-20 21:15 rob pike
2002-01-20 20:02 Roshan James
2002-01-20 21:01 ` Matt H
2002-01-20 22:02   ` Scott Schwartz
2002-01-22  9:54     ` ozan s yigit
2002-01-23 10:05       ` Bakul Shah
2002-01-21 10:22   ` Boyd Roberts
2002-01-21 10:40     ` John Murdie
2002-01-20 21:03 ` William S.
2002-01-20 21:34 ` William Josephson
2002-01-21  6:53 ` cej

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=20020121221520.88DFF199E3@mail.cse.psu.edu \
    --to=anothy@cosym.net \
    --cc=9fans@cse.psu.edu \
    /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).