On Tue, 30 Nov 2004, Greywolf wrote:

>[Thus spake der Mouse ("dM: ") 6:19am...]
>
>dM: - The partitioning tool seems semi-broken, in that it refuses to allow
>dM:   partitions to overlap (except for overlap with c).  I had a disk
>dM:   pre-partitioned roughly thus:
>dM:
>dM:     aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa     dddddddddddbbbbbbbbbb
>dM:                                   eeeeeeeeeeeeeeee
>dM:
>dM:   and perhaps I just told it the wrong thing, but it whined about d and
>dM:   e overlapping - I knew they overlapped and I wanted it that way.  I'm
>dM:   quite sure I set both d and e to no-mount.
>
>Yes, please don't try to be smart about this.
>
>I have frequently had need for overlapping partitions so that, depending
>upon the project at hand, I could slice 'n' dice as needed.
>
>[Maybe I really AM a dinosaur for remembering
>
>	aaabbbbbbggggggggggggggggggghhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
>	   dddddeeeeeeeeffffffffffff
> :-)
>]


How can this possibly be useful?


>
>
>I also find it rather obnoxious that fdisk partitions cannot overlap.
>While "user fiendly", I also find it "knowledgeable-user hostile".
>Do we not at least have a force flag that will let me tell fdisk that
>"Yes, I really do want to 'hose' my disk."?


I find it rather obnoxious that I can't hose kernel memory, but it is
"user friendly" in that the OS's job is to manage my machine in a way that
is secure and reliable.


>dM: - When doing unmounted-FS installation, the installer prompts for a
>dM:   base directory and a path.  It would help if it gave some indication
>dM:   what it means by these; I couldn't figure out what the base directory
>dM:   was supposed to be until I saw the pathnames it was trying to use, in
>dM:   error messages.


Ah yes, it is not exactly clear whether the directory is relative to the
mount point, if I remember correctly.


Christian

-- 
    /"\
    \ /    ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
     X                           - AGAINST MS ATTACHMENTS
    / \