9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] ~Off Topic: disk layout
Date: Sun, 28 Jan 2007 19:02:16 +0100	[thread overview]
Message-ID: <82c890d00701281002q42980820i92d662df38388ef8@mail.gmail.com> (raw)

hello

it was usual in the unix time (that is, when there was no plan9) to
have those bloated disk layouts that lunix suggests? or just was
common to have a couple of disks instead of one?

i wonder where that came from. . .

thanks,

gabi



On 1/28/07, sqweek <sqweek@gmail.com> wrote:
> On 1/28/07, erik quanstrom <quanstro@coraid.com> wrote:
> >         if(test -f /dev/mousectl && ~ $mouseport ps2 ps2intellimouse 0 1 2 usb){
> >                 if(~ $mouseport usb)
> >                         usbstart
> >                 if not
> >                         aux/mouse $mouseport
>
>  Inspired by this code, I tried entering some gibberish at the
> mouseport prompt instead of just hitting enter, and suddenly the
> keyboard worked for the install.
>  So, two hours and one recovery from having my partition table crapped
> on (thank you testdisk) later, I have plan9 installed. Tomorrow I'll
> see if I can convince lilo to boot it and check out the usb stuff.
>
>  But OK, the partition thing deserves some attention. I'm actually
> somewhat impressed and somewhat horrified at the same time... Here was
> my setup prior to the plan9 install (9039 cylinders total):
> PRI1  0001-8633 Extended
> PRI2  8634-8756 Linux swap
> LOG5 0001-0032 Linux /boot
> LOG6 0033-2465 Linux /home
> LOG7 2466-4333 Linux /usr
> LOG8 4334-4956 Linux /var
> LOG9 4957-5081 Linux /
> LOG10 5082-5144 Linux /tmp
>
>  So I went to give plan9 about 5G of logical partition at 5145-5775
> (IIRC I entered p8 as the partition name in plan9's fdisk, which may
> have marked the start of my problems). This is what I ended up with:
> PRI1  0001-5144 Extended
> PRI2  5145-5775 Plan9
> PRI3  8634-8756 Linux swap
> LOG5 0001-0032 Linux /boot
> LOG6 0033-2465 Linux /home
>
>  And that's it, logical partitions 7-10 where nowhere to be found
> (linux wasn't to happy when it couldn't find its root device). So
> plan9 shoved the swap partition out of the way and made a new primary
> for itself (this is the impressive part). Fortunately, after restoring
> the missing partitions and booting back into linux it hasn't mounted
> /dev/sda2 as swap and pissed all over the plan9 install. I think that
> makes the score Linux: 1 Plan9: 0 sqweek: -1.
>
>  I'm not sure whether it's the partitioning step that did me in or the
> boot setup. Since I don't have windows and couldn't be assed looking
> for a floppy, I hit plan9 at that step, which may have been what
> motivated it to put itself on a primary partition.
>


             reply	other threads:[~2007-01-28 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-28 18:02 Gabriel Diaz [this message]
2007-01-28 18:17 ` sqweek
2007-01-28 18:54   ` Gabriel Diaz

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=82c890d00701281002q42980820i92d662df38388ef8@mail.gmail.com \
    --to=gabidiaz@gmail.com \
    --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).