Wonderful ;(
There's nothing in any of the installation documentation that I can
remember that warns me about any of this. I suppose this could be
considered a documentation bug?
As mentioned in my response to Kay Sievers, so far as I know this system
had never had any other operating system than Linux installed. It's a
Dell server originally purchased with Red Hat 7.0 or 7.1 installed at
the factory. This could of course be part of the problem, in that the
tools used by that OS are relatively old. It's not something I'd
considered, prior to hearing from Kay.
The "tool I used to create the filesystem" is whatever it is that's in
the basic Debian etch net install. I have no idea what tool is actually
run, in this case. Can you provide a pointer or two, as to who I should
contact or what package is involved?
Thank you.
Marco d'Itri wrote:
On May 11, Kay Sievers <[EMAIL PROTECTED]> wrote:
Never use any of the all broken mkfs* tools without writing zeros to the
start and the end of the partition before applying a different format.
Overwrite at least 64kb. (Sane formatting applications like everything that
is libparted based don't need this.)
The upstream maintainer is right, this cannot really be fixed in udev
because a filesystem may contain ambiguous metadata.
I am closing the bug, I suggest you further discuss this with the
maintainer of the tool you used to create the file system.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
