9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Ezequiel Reyes" <ezequiel.reyes@newhotel.co.cu>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] accesing a local fossil
Date: Mon, 15 Aug 2005 10:05:33 -0700	[thread overview]
Message-ID: <003801c5a1bb$8de29440$e000a8c0@OBLIVIONDT> (raw)
In-Reply-To: <32d987d5050815093233b57d4e@mail.gmail.com>

----- Original Message -----
From: "Federico Benavento" <benavento@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Sent: Monday, August 15, 2005 9:32 AM
Subject: Re: [9fans] accesing a local fossil

>> had noticed it used a different rio version since it have smaller fonts
and
>> circular menus unlike the liveCD option which I think is older) just to
see
> circular menus?

well, that's what I would call them anyway. In the liveCD system, rio has
normal drop down rectangular menus, while using option 1 starts a rio whose
menus are like pie slice graphic charts with every menu option in a pie. I
think the reason behind it is ergonomics, since the mouse is in the center
of the circle and only a minor move in the right direction will hilight the
correct menu entry. I just recibed a mail telling me these are menus from
and old iso image, so I think what is happening is that the vesa enabled iso
image is old compared to the current standard iso since I am using the
former. Well, in tha case I can only hope vesa becomes part of the standard
iso soon :)

>> %fossil/fossil -f /dev/sdC0/fossil
>check where is your fossil partition
>% ls /dev/sd*/fossil

I did that, my installed fossil went to /dev/sdC0/fossil, I seem to remember
the installer tells it in an auxiliar console while performing install
operations. I even removed the CD just to be sure I could still browse sdC0
without it, besides, only 386 from the arch especific folders was there. In
my system, the CD showed in sdC1 and when I try to boot from hard drive the
message right before stopping tells sdC0 as well.

> open a new window
> % cat file
> edit whatevet you want, snarf the hole thing
> % cat > file
paste the buf and

Yes. I can do that, but I was just curious on why I could not start fossil
on /dev/sdC0/fossil using the liveCD demo but could start it and get the
need /srv/fossil using the install system. Any ideas? I am new to plan 9,
but for what I've read, all I needed was the command: fossil/fossil -f
/dev/sdC0. Is it a problem with the liveCD option or a bad procedure of
mine?



  reply	other threads:[~2005-08-15 17:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  9:16 [9fans] can acme clients (Wiki) access acme's clean/dirty status? Axel Belinfante
2005-08-15  9:34 ` Axel Belinfante
2005-08-15 14:37   ` [9fans] accesing a local fossil Ezequiel Reyes
2005-08-15 16:29     ` Federico Benavento
2005-08-15 16:32       ` Federico Benavento
2005-08-15 17:05         ` Ezequiel Reyes [this message]
2005-08-15 16:42     ` Christoph Lohmann
2005-08-15 19:09       ` Ezequiel Reyes
2005-08-15 19:20         ` Christoph Lohmann
2005-08-15 17:26     ` Steve Simon
2005-08-22 17:39       ` Ezequiel Reyes
2005-08-23  8:49         ` Robert Raschke
2005-08-23 16:48         ` Micah Stetson

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='003801c5a1bb$8de29440$e000a8c0@OBLIVIONDT' \
    --to=ezequiel.reyes@newhotel.co.cu \
    --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).