On Wed, 18 Mar 1998, james hartley (sys admin) wrote:
> Vidiot wrote:
>
> >
> > I'm curious as to how you got in this state. I didn't know that fdisk
> > would let you put in bad numbers. Whenever I've used it, after doing
> > hda1 (using the above example), putting in the next partition woul
>Yes I would like that but unfortunatly the fdisk utility puts in the
>screwed up numbers that I listed in the last post automatically.
Interesting. I never really noticed before, since it has always worked.
Here is what my fdisks are for my three disks:
/dev/hda111 102
Vidiot wrote:
>
> I'm curious as to how you got in this state. I didn't know that fdisk
> would let you put in bad numbers. Whenever I've used it, after doing
> hda1 (using the above example), putting in the next partition would give
> you 1085 as the choice as to where to start the next parti
>HELLO: I am trying to load redhat 4.1 on a 4.3 gig drive. during the
>partitioning using fdisk I noticed that the begin start and end fields
>had overlapping in the begin field. specifically
>
>Device BootBegin Start End Blocks Id System
>/tmp/hda1 1 1 1084
HELLO: I am trying to load redhat 4.1 on a 4.3 gig drive. during the
partitioning using fdisk I noticed that the begin start and end fields
had overlapping in the begin field. specifically
Device Boot Begin Start End Blocks Id System
/tmp/hda1 1 1 1084512
