public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Andrew Clausen <clausen@conectiva.com.br>
Cc: linux-fsdevel@vger.kernel.org, bug-parted@gnu.org,
	linux-kernel@vger.kernel.org
Subject: Re: Partition IDs in the New World TM
Date: Mon, 22 Jan 2001 11:32:31 -0500	[thread overview]
Message-ID: <3A6C609F.F135DB0@didntduck.org> (raw)
In-Reply-To: <3A6C5D12.99704689@conectiva.com.br>

Andrew Clausen wrote:
> 
> Hi all,
> 
> We have roughly 10 different types of partition tables.  We hate
> them, but it looks like they won't be going away for a long time.
> 
> Partition IDs seem to create a lot of confusion.  For example,
> most people use 0x83 for both ext2 and reiserfs, on msdos
> partition tables.  People use "Apple_UNIX_SVR2" for ext2 on
> Mac, etc.
> 
> Linux doesn't really use partition IDs.  Well, not entirely
> true... it's used on Mac's as a heuristic, for finding swap
> devices, etc. - but I think this unnecessary.
> 
> LVM also uses it, but I also think it's unnecessary.
> 
> So, can anyone remember why we have partition IDs?  (as opposed
> to just probing for signatures on the fs)  If new partition table
> types come out (which is happening, believe it or not...), how
> should Linux/fdisk/parted handle IDs?  Should we have one Linux
> type, that we use for everything?  Should we have one type for each
> TYPE of data (file system, swap, logical volume physical device, etc.)?

For compatability with dual booting other operating systems.  Would you
want Windows walking over your ext2 filesystems?  Linux didn't invent
the partition table schemes, it just borrows from those that are most
common for a given architecture (ie. msdos on PC compatable systems,
etc.)

--

				Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-22 16:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22 16:17 Partition IDs in the New World TM Andrew Clausen
2001-01-22 16:32 ` Brian Gerst [this message]
2001-01-22 16:47   ` Andrew Clausen
2001-01-22 21:39     ` Russell King
2001-01-22 22:30       ` Andrew Clausen
2001-01-22 22:42         ` Russell King
2001-01-22 23:28           ` Andrew Clausen
2001-01-22 23:35         ` H. Peter Anvin
2001-01-23  4:47           ` Andreas Dilger
2001-01-23  6:23             ` H. Peter Anvin
2001-01-23 19:26             ` Matt D. Robinson
2001-01-24  8:18               ` Andreas Dilger
2001-01-22 22:16 ` Glenn McGrath
2001-01-22 23:35   ` Jason Venner
  -- strict thread matches above, loose matches on Subject: below --
2001-01-22 22:42 Andries.Brouwer
2001-01-22 17:35 ` Mark I Manning IV
2001-01-22 22:55 Andries.Brouwer
2001-01-23 15:46 Andries.Brouwer
     [not found] <OF03708398.46274A87-ON872569DD.005CA0DE@LocalDomain>
2001-01-23 17:08 ` Andrew Clausen
     [not found] <OF5F9BE7DB.C1ADFB0E-ON872569DD.006485CC@LocalDomain>
2001-01-23 18:35 ` Andrew Clausen
2001-01-23 22:01   ` Glenn McGrath
2001-01-24 13:40     ` Andrew Clausen
2001-01-24 10:28 Andries.Brouwer

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=3A6C609F.F135DB0@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=bug-parted@gnu.org \
    --cc=clausen@conectiva.com.br \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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