Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael Marxmeier <mike@msede.com>
To: hppa-linux@puffingroup.com
Cc: jason@gatekeeper.equator.com
Subject: Re: [hppa-linux] Booting issues.
Date: Tue, 16 Feb 99 19:47:03 MEZ	[thread overview]
Message-ID: <199902161847.TAA01112@e35.msede.com> (raw)
In-Reply-To: <199902161812.KAA22762@hairball.cup.hp.com>; from "Richard "J." Rauenzahn" at Feb 16, 99 10:12 am

> Software convention.  Pre 10.x, people used whole disks, after 10.x we
> have Logical Volume Manager which lets you put a set of disks into a
> Volume Group and create Logical Volumes using the space within that
> Volume Group.  You then newfs the Logical Volumes..
> 
> /dev/vg01/lvol1
> /dev/vg01/rlvol1

For older systems (read pre-LVM) fixed partitions (calls "sections")
were used which were defined in /etc/disktab and hard-coded
in the driver. With the LVM this has changed.

AFAIR only a small boot area (/stand) or for other configurations
the root file system is required to be in hfs format and must be
contiguous. There should be a pointer towards it somewhere in the
LVM data structures. All other file systems can be VxFS.

> A logical volume might span one disk, or multiple disks, or stripe
> across all the disks..  and you can extend the filesystems later, and
> they don't have to be contiguous.  Pretty handy -- I've wished Linux had
> it as I hate PC partition schemes that aren't resizable..

It has. http://linux.msede.com/lvm (alpha code)

> I'm not sure how the root directory logical volume is handled -- I
> believe it has to be the first volume on the root volume group, and has
> to be contiguous.

Yes.


Michael

--
Michael Marxmeier           Marxmeier Software GmbH
E-Mail: mike@msede.com      Besenbruckstrasse 9
Voice : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/

----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.

  reply	other threads:[~1999-02-16 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-16 16:32 [hppa-linux] Booting issues Jason Eckhardt
1999-02-16 18:01 ` Alex deVries
1999-02-16 19:01   ` Bill Katz
1999-02-16 18:12 ` Richard J. Rauenzahn
1999-02-16 18:47   ` Michael Marxmeier [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-02-16  1:48 Alex deVries
1999-02-16  6:06 ` Bill Katz
1999-02-16 17:18   ` Alex deVries
1999-02-16 18:23     ` Bill Katz
1999-02-16 18:35     ` Richard J. Rauenzahn

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=199902161847.TAA01112@e35.msede.com \
    --to=mike@msede.com \
    --cc=hppa-linux@puffingroup.com \
    --cc=jason@gatekeeper.equator.com \
    /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