From: Andries Brouwer <aeb@veritas.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.0-test9 Root no longer permitted to format floppies?
Date: Thu, 7 Dec 2000 20:28:09 +0100 [thread overview]
Message-ID: <20001207202809.A24021@veritas.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1001207114503.171A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1001207114503.171A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Thu, Dec 07, 2000 at 11:54:38AM -0500
On Thu, Dec 07, 2000 at 11:54:38AM -0500, Richard B. Johnson wrote:
> # fdformat /dev/fd0h1440
> Double-sided, 80 tracks, 18 sec/track. Total capacity 1440 kB.
> Formatting ...
> ioctl(FDFMTBEG): Operation not permitted
Probably an old fdformat?
Try a recent util-linux.
[I forgot the details - people will correct me -
Old situation: a special kludge in floppy.c allows ioctls,
including formatting, on a fd opened without read or write
permission. And the old fdformat did just that.
Some cleanup removed the kludge, and fdformat had to open
the fd for writing. So the util-linux fdformat was updated.
Later Alain Knaff said that the old kludge remained necessary,
because one might wish to use ioctl's on write protected floppies.
Maybe the change was partially reverted, I have not checked.]
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-07 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 16:54 2.4.0-test9 Root no longer permitted to format floppies? Richard B. Johnson
2000-12-07 18:05 ` Tigran Aivazian
2000-12-07 18:38 ` Richard B. Johnson
2000-12-07 19:28 ` Andries Brouwer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001207202809.A24021@veritas.com \
--to=aeb@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox