From: John DeDourek <dedourek@unb.ca>
To: linux-hotplug@vger.kernel.org
Subject: Internal ZIP drive and udev device nodes
Date: Thu, 23 Feb 2006 00:49:07 +0000 [thread overview]
Message-ID: <43FD0683.7050604@unb.ca> (raw)
I am running Fedora Core 4,
kernel-2.6.15-1.1831_FC4
udev-071-0.FC4.2
hal-0.5.2-2.fc4.1
on an IBM ThinkCentre 8143-4JU
Pentium 4 550 with HT 3400MHz
Intel 915G chipset
Iomega ZIP 100 ATAPI drive
(as slave on second chain; master on that chain is
a DVD-ROM/CD-RW)
On a boot, /dev/hdd is created, but the required /dev/hdd4 is not.
On insertion of media, /dev/hdd4 is not created.
On attempted mount of /dev/hdd with media in drive
(mount -t vfat /dev/hdd /media/zip)
mount fails (as expected, "wrong fstype ...", because media
has a partition table) but /dev/hdd4 is created
Subsequently, mount -t vfat /dev/hdd4 /media/zip works correctly
An entry
/dev/hdd4 /media/zip auto pamconsole,exec,noauto,managed 0 0
exists in /etc/fstab.
However, neither
mount /media/zip
nor
mount /dev/hdd4
work, either before or after the /dev/hdd4 device node is created.
Looking for pointers to documentation that describes how removable
media with partition tables are supposed to work and/or advice
on correcting this problem.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2006-02-23 0:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43FD0683.7050604@unb.ca \
--to=dedourek@unb.ca \
--cc=linux-hotplug@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.