From: Eric Bambach <eric@cisu.net>
To: linux-hotplug@vger.kernel.org
Subject: [BUG]? Udev, USB Disks and /dev special files
Date: Thu, 15 Jul 2004 19:59:12 +0000 [thread overview]
Message-ID: <200407151459.12915.eric@cisu.net> (raw)
Hello,
First, please pardon me if this is a known problem,fixed or I am posting to
the wrong list. Second please CC me as im not subscribed.
I have an interesting situation. It seems /dev entries,specifically special
devices are not interpreted by the kernel across UDEV mounted devices. My
hardware. One IDE to USB 2.0 enclosure with an 80GB HD with kernel
2.6.7-gentoo-r8 . I have configured udev to name my device /dev/usbcage and
its partitions /dev/usbcage1...etc.
I am installing gentoo on this disk and was having trouble because /dev/null
was neither readable nor writeable, same for other special files, random,
zero, etc. Even a chmod 777 would not fix the problem. Turns out that if I
unmount /dev/usbcage and mount it as its proper name /dev/sde1 then this
problem disappers. Same permission, even scaled back to 666. Is this an issue
with the kernel, Udev, or both? Can't the kernel interpret /dev entries
across symlinks? Should I submit this as a bug to LKML?
Let me know if anyone would like more info.
--
-EB
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click
_______________________________________________
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:[~2004-07-15 19:59 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=200407151459.12915.eric@cisu.net \
--to=eric@cisu.net \
--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.