linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heinz J. Mauelshagen <Heinz.Mauelshagen@t-online.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] fdisk and the LVM partition.
Date: Fri, 19 Jan 2001 11:52:01 +0000	[thread overview]
Message-ID: <20010119115201.B11381@srv.sistina.com> (raw)
In-Reply-To: <200101190934.JAA05616@lindbergh.avbrief.com>; from tmdg@avbrief.com on Fri, Jan 19, 2001 at 09:34:18AM +0000

I registered 0x8E a long time ago.
Obviously nobody (including me ;-) took care of extending fdisk.
Could you go for it, please?

On Fri, Jan 19, 2001 at 09:34:18AM +0000, Tom Dawes-Gamble wrote:
> Hi,
> 
> 	Is anyone actively pursuing getting the LVM partition ID
> "Registered"?
> 
> 	  I got a little tee-d off with the LVM partition showing 
> 'Unknown' so I fixed my fdisk with this patch to i386_sys_types.c
> 
> *** i386_sys_types.c    Fri Jan 19 09:30:07 2001
> --- i386_sys_types.c.new        Fri Jan 19 09:29:52 2001
> ***************
> *** 58,63 ****
> --- 58,64 ----
>         {0x85, N_("Linux extended")},
>         {0x86, N_("NTFS volume set")},
>         {0x87, N_("NTFS volume set")},
> +       {0x8e, N_("LVM Physical volume")}, /* LVM http://www.sistina.com/lvm/ */
>         {0x93, N_("Amoeba")},
>         {0x94, N_("Amoeba BBT")},       /* (bad block table) */
>         {0xa0, N_("IBM Thinkpad hibernation")},     
> 
> 
> 
> 	So now my fdisk knows about LVM partitions.
> 
> 	While checking that fdisk still worked correctly I was reminded
> the we used to use Partition type 'fe' but I guess that got stolen by LANstep. 
> 
> 	I changed the type of my 'fe' to '8e' and rebooted no problems.
> Though I guess I can't go back to my old and I mean "really" old kernel.  :-)
> 
> 	
> Regards,
> Tom.
> 
> -- 
> char  *r,*e,*w="%.9s%.7s%.7s\n";extern int printf(const char*,...);int main(){
> int l=*w,a,b,th=*(w-~(l/=l))-*(w+l);b=*w+~th--;a=b-th;//Aviation Briefing Ltd.
> r=e="  DISPLAY'tmdg@avbr';,,;'ief.com'*>"+b;l+=~b,th-=printf(w,e-a,th+e,r);
> r=e="  DISPLAY'http://www.avbrief.com/' *>"-~b,exit(~l-printf(w,e+~a,th+e,r));}
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-01-19 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19  9:34 [linux-lvm] fdisk and the LVM partition Tom Dawes-Gamble
2001-01-19 11:52 ` Heinz J. Mauelshagen [this message]
2001-01-19 12:12   ` Patrick Boutilier
2001-01-24  1:13   ` Brett G. Person
2001-01-24  7:13 ` Benoit SERRA

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=20010119115201.B11381@srv.sistina.com \
    --to=heinz.mauelshagen@t-online.de \
    --cc=linux-lvm@sistina.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;
as well as URLs for NNTP newsgroup(s).