On 5/3/05, Bodo Eggert <[email protected]>
<[email protected]> wrote:
> Joe <[email protected]> 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.
> 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.
I would like to see an easier workaround then just ignoring it like
that, but if its really needed....
Anyways, thanks everyone for the info, its much appreciated.
Joe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
