From: fire-eyes <sgtphou@fire-eyes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev issue? (No /dev/cdroms/XXX on two machines)
Date: Tue, 27 Sep 2005 14:03:19 -0400 [thread overview]
Message-ID: <43398967.5020103@fire-eyes.org> (raw)
In-Reply-To: <5bdc1c8b05092710444c4c57c9@mail.gmail.com>
Mark Knecht wrote:
> Hi,
> It seems that on two of my machines, after recent updates, I no
> longer have /dev/cdroms and therefore cannot mount CDs, etc. I can
> mount them by hand using the old style /dev/hda. The hardware works.
> It just seems that udev is now doing something different.
>
> Has anyone else seen this of late?
>
> I am set up as "auto" for the udev/devfs choice in /etc/conf.d/rc,
> as well as not using a tarball. udev is up and running:
>
> gigastudio ~ # ps aux | grep udev
> root 854 0.0 0.0 1468 484 ? S<s 10:30 0:00 udevd
> gigastudio ~ #
>
> gigastudio ~ # emerge -pv udev
>
> These are the packages that I would merge, in order:
>
> Calculating dependencies ...done!
> [ebuild U ] sys-fs/udev-068-r1 [068] (-selinux) -static 0 kB
>
> Total size of downloads: 0 kB
> gigastudio ~ #
>
> Any ideas why this might happen and where I'd look to solve the problem?
>
> All machines have been rebooted, etc.
>
> Thanks,
> Mark
>
I saw this too, with udev-070. I tried everything I could to rule out it
being udev, but I was unable to do so. I filed a bug, it would help if
you could provide your details there.
http://bugs.gentoo.org/show_bug.cgi?id=107142
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-27 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 17:44 [gentoo-user] udev issue? (No /dev/cdroms/XXX on two machines) Mark Knecht
2005-09-27 18:03 ` fire-eyes [this message]
2005-09-27 18:34 ` Mark Knecht
2005-09-27 19:10 ` fire-eyes
2005-09-28 18:09 ` Richard Fish
2005-09-28 18:52 ` Mark Knecht
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=43398967.5020103@fire-eyes.org \
--to=sgtphou@fire-eyes.org \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox