From: Felix Miata <mrmazda@earthlink.net>
To: util-linux@vger.kernel.org
Subject: Re: fdisk -l hits floppy drive
Date: Tue, 17 Feb 2015 03:32:31 -0500 [thread overview]
Message-ID: <54E2FC9F.9060607@earthlink.net> (raw)
In-Reply-To: <87r3tpqngz.fsf@hobgoblin.ariadne.com>
worley@alum.mit.edu (Dale R. Worley) composed on 2015-02-16 21:30 (UTC-0500):
> Felix Miata wrote:
>> Dale R. Worley composed on 2015-02-07 21:37 (UTC-0500):
>>> Felix Miata wrote:
>>>> fdisk -l is causing the floppy drive to get hit, which reflects the 4 kernel
>>>> messages onto the tty running fdisk. Is this expected or intended?
>>> I see in the manual page:
>>> -l List the partition tables for the specified devices and then
>>> exit. If no devices are given, those mentioned in /proc/parti-
>>> tions (if that exists) are used.
>>> Is the floppy listed in /proc/partitions?
>> Yes, as is the OM drive:
>>...
>> 2 0 4 fd0
>>...
> Then the answer to your question is, "Yes, it is expected and intended."
Why?
> Are you saying that you find this undesirable?
Based on my understanding of the meaning of partition, yes. From the man page:
fdisk is a dialog-driven program for creation and manipulation of
partition tables.
sr0 and fd0 don't have partition tables. Are sr0 and fd0 not always invalid
targets for fdisk? If yes, what reason is there for /proc/partitions to
contain them?
> If so, do you have a
> proposal for how "fdisk -l" should determine the list of devices that it
> should list?
AFAICT, it should list all items in /proc/partitions, which should contain
only devices that are partitionable. Including /dev/md* in /proc/partitions
also seems wrong.
How fdisk does what it does doesn't really matter to me. What matters is not
hearing unexpected attempts to access an old floppy drive that I expect to
work when I need it instead of being worn out by unwanted and useless access
attempts; and not seeing floppy access failure messages appear in the middle
of other activity.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
next prev parent reply other threads:[~2015-02-17 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 19:13 fdisk -l hits floppy drive Felix Miata
2015-02-08 2:37 ` Dale R. Worley
2015-02-08 7:52 ` Felix Miata
2015-02-09 10:36 ` Karel Zak
2015-02-17 2:30 ` Dale R. Worley
2015-02-17 8:32 ` Felix Miata [this message]
2015-02-18 3:29 ` Dale R. Worley
2015-02-09 14:45 ` Phillip Susi
2015-02-10 14:59 ` Felix Miata
2015-04-07 1:03 ` Phillip Susi
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=54E2FC9F.9060607@earthlink.net \
--to=mrmazda@earthlink.net \
--cc=util-linux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.