9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Problem caused by recent change to diskparts
Date: Tue, 17 Jun 2008 20:59:07 +0200	[thread overview]
Message-ID: <ba0d3bc70806171159h32e6997dvd0d9fc4a2dcca0a8@mail.gmail.com> (raw)

Hi,

Between 11 and 12 June, there has been a change to /rc/bin/diskparts
to detect plan9 partitions on disks without a mbr. This change seems
to cause a problem with disks that do not have a plan9 partition at
all though: after running diskparts, one of my harddisks (the one
without a plan9 partition), shows only the files 'ctl', 'raw' and
'data'.  I would expect my 'linux' and 'linux1' to be there as well.
When I run 'disk/fdisk -p $disk/data > $disk/ctl' on it by hand, the
files 'linux' and 'linux1' do show up. Here is the code that sets up
the partitions:

for(disk in /dev/sd[0-9A-Zabd-z]*) {
	if(test -f $disk/data && test -f $disk/ctl)
		disk/fdisk -p $disk/data >$disk/ctl >[2]/dev/null
	if(test -f $disk/plan9)
		parts=($disk/plan9*)
	if not
		parts=($disk/data)
	for(part in $parts)
		if(test -f $part)
			disk/prep -p $part >$disk/ctl >[2]/dev/null
}

The 'disk/fdisk' line sets the partitions up correctly, but then after
that, the 'disk/prep' line seems to erase them again. I guess the
output of the 'disk/fdisk' and 'disk/prep' lines should be accumulated
and written to the $disk/ctl file all at once?

Greetings, Sander.



             reply	other threads:[~2008-06-17 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17 18:59 Sander van Dijk [this message]
2008-06-17 19:19 ` erik quanstrom

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=ba0d3bc70806171159h32e6997dvd0d9fc4a2dcca0a8@mail.gmail.com \
    --to=a.h.vandijk@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).