From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] using usb
Date: Thu, 1 Apr 2010 09:19:13 -0400 [thread overview]
Message-ID: <c6cdf531826b5dfdc9f87e7f4b39430b@ladd.quanstro.net> (raw)
In-Reply-To: <8620f5b87bbbfc30468f7e134aa1acc0@hera.eonet.ne.jp>
> Up-to-now, I only aplied /sys/src/boot/pc drivers, and found strange
> behaviour of that, say missing 'other' partition in a SATA HDD(only this partition).
> It has many partiotions, such as 9fat, fossil, arenas0, isect0~3, swap, cache, nvram and other).
> Then, I used /disk/prep, which reported right partioning, and write it
> to the disk. Then, I can use other file system.
> However, when I rebooted the system, then, 'other' partition disappears
> again.
>
> Do you have some idea what's going on here.
i hope i have understood correctly that you applied
the partitions which were originally missing with
disk/prep -p and rebooted and the partitions didn't
reappear. in that case, ...
disk/prep -p doesn't write anything to the disk. it just
prints a list of partions and ranges, one per line. if
you inform sd about partions with
disk/prep -p /dev/sdXX/data>/dev/sdXX/ctl
again, nothing is written to disk but sd creates the
partitions it was told about in memory. and a
file with the name of each partition appears.
each time the machine is booted, prep must be run.
if necessary, diskparts(8) serves this purpose.
on the other hand, if 9load provides the kernel with
a conf variable sdXXpart, sd with partition sdXX on
boot. 9load only automaticly provides this variable if it
booted a kernel from sdXX. i have set the variable
sda0part for a machine using sas disks because i never
bothered porting the driver to 9load but needed a
place for nvram.
- erik
next prev parent reply other threads:[~2010-04-01 13:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 5:24 ruel hernandez
2010-03-31 7:53 ` Sergey Zhilkin
2010-03-31 7:56 ` Sergey Zhilkin
2010-03-31 8:10 ` Francisco J Ballesteros
2010-03-31 11:49 ` EBo
2010-03-31 12:17 ` Francisco J Ballesteros
2010-03-31 14:41 ` EBo
2010-03-31 12:42 ` kokamoto
2010-03-31 12:43 ` kokamoto
2010-03-31 12:56 ` erik quanstrom
2010-03-31 14:30 ` Francisco J Ballesteros
2010-03-31 22:12 ` kokamoto
2010-03-31 22:28 ` erik quanstrom
2010-04-01 11:11 ` kokamoto
2010-04-01 13:19 ` erik quanstrom [this message]
2010-04-02 10:49 ` kokamoto
2010-04-02 10:56 ` erik quanstrom
2010-04-01 10:13 ` antonio.fin
2010-04-01 10:24 ` Francisco J Ballesteros
2010-04-01 12:37 ` EBo
2010-04-12 9:30 ` antonio.fin
2010-04-12 9:58 ` Francisco J Ballesteros
2010-04-04 4:41 ruel hernandez
2010-04-05 4:50 ruel hernandez
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=c6cdf531826b5dfdc9f87e7f4b39430b@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).