Re: Empty partition nodes not created (was device node issues with recent mm's and udev)

[Bodo Eggert <7eggert@gmx.de>]

On Tue, 3 May 2005, Joe wrote:

> On 5/3/05, Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
> <7eggert@gmx.de> wrote:
> > Joe <joecool1029@gmail.com> wrote:
> > 
> > > Here is the partition table from fdisk, fdisk does run fine.. its just
> > > the fact this node is not created that threw me off before.
> > >
> > >    Device Boot      Start         End      Blocks   Id  System
> > > /dev/sdb1   *           1           2       16033+   0  Empty
> > > /dev/sdb2   *           6        2431    19486845    b  W95 FAT32
> > > /dev/sdb3               3           5       24097+  83  Linux
> > >
> > > Notice, /dev/sdb1 is a Empty partition... in /dev I only have sdb,
> > > sdb2, and sdb3.  No sdb1.  Any help would be appreciated.
> > 
> > Some vendors depend on empty partitions not showing up. That's why this
> > patch was introduced.
> 
> It would be interesting to see just how important it is to hide this. 

The size and position values were quite random, and the useless extra
partition caused some problems.

> > BTW: Is there a special reason you why choose "empty"?
> > Is this partition showing up in other systems at all?
> 
> Actually, yes there is.. its a firmware partition that would normally
> not be mounted, but in order to dd new firmware versions to it, I
> depended on the node... which has ceased to exist.

So it isn't empty.-) I asume it will be in a custom system, so you can
hijack the compaq partition type (which was used for a similar purpose).

BTW: If you can do that, you should move the partition to the end of the
disk into the slower area of he disk.

-- 
"Bravery is being the only one who knows you're afraid."
-David Hackworth
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/