From: Mikael Pettersson <mikpe@it.uu.se>
To: "Andries E. Brouwer" <Andries.Brouwer@cwi.nl>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: completely hide parts of the partition table from Windows?
Date: Wed, 19 Aug 2009 01:56:18 +0200 [thread overview]
Message-ID: <19083.16290.445891.283072@pilspetsen.it.uu.se> (raw)
In-Reply-To: <20090818223522.GA5872@ub>
Andries E. Brouwer writes:
> On Tue, Aug 18, 2009 at 11:22:30PM +0200, Mikael Pettersson wrote:
>
> > So what I'm looking for is some sub-partition table format with the
> > following two properties:
> > 1. resides in an msdos partition entry of a type that Windows does
> > not inspect (for whatever extended partitions or Apple/BSD/Sun
> > stuff that Windows may have been taught to recognize)
> > 2. the locations and sizes of the sub-partitions are NOT limited by
> > the parent msdos partition entry
>
> The reason I added type 85 = LINUX_EXTENDED_PARTITION
> was precisely your concern: it should be something
> that DOS/Windows doesnt know about.
>
> > I've looked at the code in fs/partitions/msdos.c, and it seems that
> > most of the extended/BSD/Sun formats don't give me property #2 above.
>
> The standard description of extended partitions says that the size field
> of the parent extended partition descriptor is irrelevant, only the
> starting sector matters.
>
> If you look at the parse_extended() code in msdos.c you'll see
> that it does not use its parameter first_size.
> (Except in a certain case that you will not be in.)
Right. I misread the "process the data partitions" part to imply
that the limits were enforced for all four entries, not just the
last two usually-junk entries. Thanks for clarifiying that.
> Make a table that has a Linux extended partition (type 85)
> that is short enough not to cause Windows to worry. Have logical
> partitions inside of any size and location you desire.
I have created extended partitions with non-default type
(though not 85). I'll see if I can convince fdisk or parted to
create one with entries exceeding the parent's limits.
Thanks,
/Mikael
next prev parent reply other threads:[~2009-08-18 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 21:22 Mikael Pettersson
2009-08-18 22:32 ` Alan Cox
2009-08-18 23:49 ` Mikael Pettersson
2009-08-22 22:54 ` Mikael Pettersson
2009-08-18 22:35 ` Andries E. Brouwer
2009-08-18 23:56 ` Mikael Pettersson [this message]
2009-08-22 22:59 ` Mikael Pettersson
2009-08-23 7:36 ` Andries E. Brouwer
2009-08-23 15:19 ` Mikael Pettersson
2009-08-18 22:39 ` Matthias Schniedermeyer
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=19083.16290.445891.283072@pilspetsen.it.uu.se \
--to=mikpe@it.uu.se \
--cc=Andries.Brouwer@cwi.nl \
--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
all inboxes | Powered by JetHome®