9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Partitioning the disk
Date: Thu, 10 Apr 2014 16:53:00 -0400	[thread overview]
Message-ID: <11ab5f66f83c6d62dd6f5bb6932e16d2@ladd.quanstro.net> (raw)
In-Reply-To: <20140410202343.GA1684@thunderclap>

> 1. After mounting usb disk with addloop, there is no file /dev/sdU1.0/plan9. How
> can I create plan9 partion table?
>
> 2. What does diskparts(8), actually do? Does it create partitons on phisical disk?

diskparts reads existing paritition information from the disk, it does not write anything.

amd it's just a short rc(1) script, that typically runs "disk/fdisk -p data>ctl",
 and "disk/prep -p plan9>ctl".  with this setup prep is subpartitioning the
plan 9 partition.

it's worth a read.

> 3. Is the inst/textonly avalible in 9atom or is it obsolete?

textonly is not available in the 9atom usb install, but that doesn't mean it's
obsolete.

> 4. This whole partiton process seems very strange to me. How can I determine partiton
> sizes during partinoning? Which files go where(as I can see there are at least two partition
> types: fossil and 9fat)?

both prep and fdisk take the "p" command which will print the current partition info.
prep(8) is a good reference.  btw, "fossil" and "9fat" are not partition types.  prep doesn't
use that concept.  they are partition names, and by convention they have the obvious use.

> 5. Thank you very much erik for your help but could you give me a little descripton on what
> does the commands you've provided me supose to do?
>
> Sorry, if this questions are to obvious to you but as a newbie I don't understand plan9
> fully. I can already feel its power but I'm sitll not able to use it.

i lost the context here, sorry.

- erik



      reply	other threads:[~2014-04-10 20:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 21:54 Szymon Olewniczak
2014-04-02 14:28 ` erik quanstrom
2014-04-02 21:48   ` Szymon Olewniczak
2014-04-02 22:02     ` erik quanstrom
2014-04-03 18:08       ` Szymon Olewniczak
2014-04-03 18:13         ` erik quanstrom
2014-04-03 18:25           ` Szymon Olewniczak
2014-04-03 18:30             ` erik quanstrom
2014-04-06 19:21               ` Szymon Olewniczak
2014-04-03 18:22         ` Alexander Kapshuk
2014-04-03 18:24           ` erik quanstrom
2014-04-07 18:18             ` Szymon Olewniczak
2014-04-07 20:05               ` erik quanstrom
2014-04-10 20:23                 ` Szymon Olewniczak
2014-04-10 20:53                   ` erik quanstrom [this message]

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=11ab5f66f83c6d62dd6f5bb6932e16d2@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).