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, 22 Aug 2005 10:39:21 -0700 [thread overview]
Message-ID: <005e01c5a740$6ee1e250$e000a8c0@OBLIVIONDT> (raw)
In-Reply-To: <666de0517e982a8cdbb3f45e0c278b16@quintile.net>
----- Original Message -----
From: "Steve Simon" <steve@quintile.net>
To: <9fans@cse.psu.edu>
Sent: Monday, August 15, 2005 10:26 AM
Subject: Re: [9fans] accesing a local fossil
> This happens because the fossil config file burnt onto the start of the
fossil
> partition does not contain a srv command, it is passed on the command line
when fossil
> is envoked.
>
> /sys/src/9/boot/local.c:256
> run("/boot/fossil", "-f", partition, "-c", "srv -A fboot", "-c", "srv -p
fscons", 0);
>
> You could start the bootable CDROM and then type:
>
> % fossil/fossil -f /dev/sdC0/fossil -c 'srv -APW open' -c 'srv -p fscons'
> % mount /srv/open /n/open
>
> Your fossil filesystem should now appear in /n/open/active/ and all
permission
> checking will be turned off so you can fix anything you like.
>
I did just that, I first listed to find all fossils:
ls /dev/sd*/foosil
which gave me /dev/sdC0 twise
Then:
% fossil/fossil -f /dev/sdC0/fossil -c 'srv -APW open' -c 'srv -p fscons'
% mount /srv/open /n/open
But there was no /n/open/active. In /n/open there was I filesystem very
similar to the one on the CD but with some files missing and different date
signatures.
When I tried to cp some file there:
can't create "/n/open/PLAN9.INI" : mounted directory forbids creation
I had installed plan 9 using the option 1 of the CD and the 9pccd.gz in it
to run the instalation system. I am sure it installed, there were no errors
during the process and the progress bar took some time. When I boot I get
these 3 final lines:
using sdC0!9fat!plan9.ini
Boot devices: fd0 ether0 sdC0!9fat
boot from:
Then I tried sdC0!9fat!9pcdisk.gz but: error walking to 9pcdisk.gz
So, there is a plan 9 system installed, but I can not access it because the
plan9.ini is not well configured or does not mention the proper kernel file.
I can not depend on the floppy because it does not have vesa driver on it so
rio won't start. That's why I am trying to create or modify a plan9.ini file
on the instalation using the cd demo system.
Is it at all possible to do this? I mean, accesing the just installed system
using the CD demo and modifying or copying the plan9.ini file?
In case it is, why can't I write on the mounted fossil?
where should I put (or look for in order to modify) the plan9.ini on the
disk?
The booting system finds it on sdC0!9fat!plan9.ini
But I can't find it on the mounted fossil.
next prev parent reply other threads:[~2005-08-22 17:39 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
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 [this message]
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='005e01c5a740$6ee1e250$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).