Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <mkp@mkp.net>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: Peter Mottram <peter@petescaff.com>,
	"parisc-linux@lists.parisc-linux.org"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] partitioned md to enable root on raid
Date: 22 Jan 2002 01:32:10 -0500	[thread overview]
Message-ID: <yq1665ukiad.fsf@jaguar.wave.mkp.net> (raw)
In-Reply-To: <20020122022033.C1685482A@dsl2.external.hp.com>

>>>>> "Grant" == Grant Grundler <grundler@dsl2.external.hp.com> writes:

>> Here's the next question - does palo understand how to boot from
>> LVM?

Grant> No. HPUX LVM is derived from the same original sources as
Grant> linux's LVM but is not compatible. 

Linux LVM is closely modeled after the HP/UX LVM from a sysadmin
perspective.  But there's no code sharing involved.

What I really said was that IBM wrote the original LVM and donated the
code to OSF.  HP then picked it up and ported it to HP/UX.  So AIX,
OSF/1 and HP/UX volume managers share a common ancestor.  These days
they have diverted greatly, though.


Grant> HP cannot release the disk layout since it's not HP's to give
Grant> away. MKP tried to reverse engineer it early in the port and
Grant> gave up after a while. 

I didn't spend a lot of time on it (a couple of hours of poking).  I
also tried getting specs for the LVM metadata out of HP with no avail.

A read-only implementation for palo should be fairly trivial to write
but hardly worth the effort.


I do agree with the concensus that MD partitioning is not worth it.

Mirror the palo partition as md0, swap as md1 and / as md2.  Or
whatever.  That's the way to do it.

As long as you don't need autodetection (and you don't since PDC/IODC
don't understand MD devices anyway), you'll be fine leaving the
palo partition type as F0.

-- 
Martin K. Petersen      Cereal Bowl Engineer, Linuxcare, Inc.
http://mkp.net/         SGI XFS, Linux/PA-RISC, GNOME

  parent reply	other threads:[~2002-01-22  6:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-20 13:10 [parisc-linux] Booting to ISL with Linux installed Björn Bylander
2002-01-20 13:48 ` [parisc-linux] partitioned md to enable root on raid Peter Mottram
2002-01-21 20:32   ` Grant Grundler
2002-01-21 23:13     ` Peter Mottram
2002-01-22  2:20       ` Grant Grundler
2002-01-22  2:33         ` Matthew Wilcox
2002-01-22  4:11           ` Grant Grundler
2002-01-22  4:08         ` Grant Grundler
2002-01-22  6:32         ` Martin K. Petersen [this message]
2002-01-20 16:16 ` [parisc-linux] Booting to ISL with Linux installed Christoph Plattner
2002-01-20 23:05   ` Björn Bylander
2002-01-21  3:02     ` Matt Taggart
2002-01-21  6:59       ` [parisc-linux] sti console (was: Booting to ISL with Linux installed) Kaj-Michael Lang
2002-01-21 17:34         ` Bdale Garbee
2002-01-21 21:40           ` Christoph Plattner
2002-01-21 21:26       ` [parisc-linux] Booting to ISL with Linux installed Christoph Plattner
2002-01-22  1:51         ` Grant Grundler

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=yq1665ukiad.fsf@jaguar.wave.mkp.net \
    --to=mkp@mkp.net \
    --cc=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=peter@petescaff.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