public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Crawford <flacycads@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: /dev/cdrom has gone!
Date: Mon, 5 Sep 2005 13:55:11 -0400	[thread overview]
Message-ID: <200509051355.11314.flacycads@cox.net> (raw)
In-Reply-To: <200509051551.34331.stevee@gorbag.com>

Page 5-6 of a long udev thread is good reading on recent udev problems.

Robert
http://forums.gentoo.org/viewtopic-t-355069-postdays-0-postorder-asc-start-100.html


On Monday 05 September 2005 10:51 am, Steve Evans wrote:
> On Monday 05 Sep 2005 15:31, Robert Crawford wrote:
> > I just had a similar problem after I updated udev (I think). I run ~x86
> > systems, always kept current, so I expect a few minor hiccups, even
> > though I'm extremely careful  with etc-update. There seems to be some
> > weird stuff going on with udev, at least on my system, but after a lot of
> > reading on the formum, and trying many things, I tried changing my fstab
> > line
> >
> > /dev/cdroms/cdrom0	/mnt/cdrom	iso9660		noauto,rw,user		0 0
> >
> > to this.
> >
> > /dev/hdc 	/mnt/cdrom	iso9660		noauto,rw,user		0 0
> >
> > I think some rule in the new udev changed, and it wasn't creating cdroms
> > and cdrom0 anymore- only /dev/hdc.
> >
> > I looked in /dev, and sure enough, the cdrom and cdrw links point to the
> > hdc block device.
> >
> > Anyway, whatever it was, changing the fstab line now lets me mount cdroms
> > normally, as before.
> >
> > Robert Crawford
>
> I assume that as you are running ~x86 you have upgraded to gentoo-sources
> version 2.6.13. In that version devfs has been removed (well the config
> option has gone, the code is still there). The /dev/cdroms/cdrom0 style of
> device file name is a part of devfs, so if with earlier kernels you still
> had devfs enabled in the kernel, despite running udev, then you would have
> gotten the /dev/cdroms/cdrom0 link.
>
> I am running x86 and running with udev but with devfs still in the kernel.
> Yesterday I disabled devfs on one of the machines so that I could see what
> would break in preparation for 2.6.13 moving to x86. I experienced exactly
> your problem of /dev/cdroms/cdrom0 disappearing. Fortunately the solution
> is simple, as you describe above.
>
> Steve
> --
> ____________________________________________________________________
> Steve Evans            E-mail: mailto:stevee@gorbag.com
>                        WEB:    http://www.gorbag.com
> Registered Linux user #217906: http://counter.li.org
> Public Encryption Key:         http://www.gorbag.com/public-key.html
> ____________________________________________________________________
-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2005-09-05 17:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-03 10:19 [gentoo-user] /dev/cdrom has gone! danielhf
2005-09-03 10:36 ` Holly Bostick
2005-09-03 12:08   ` danielhf
2005-09-03 12:07     ` [gentoo-user] " Sven Köhler
2005-09-03 12:07       ` Sven Köhler
2005-09-03 12:32       ` danielhf
2005-09-03 12:40         ` danielhf
2005-09-03 12:53           ` Alex Korshunov
2005-09-03 13:20             ` Matt Randolph
2005-09-03 13:31               ` danielhf
2005-09-04 13:39                 ` [gentoo-user] " Greg Yasko
2005-09-03 13:40               ` [gentoo-user] " John Jolet
2005-09-03 13:56                 ` danielhf
2005-09-03 13:28             ` danielhf
2005-09-03 14:53               ` Philip Webb
2005-09-03 17:45         ` Daniel Drake
2005-09-04  3:06           ` danielhf
2005-09-04  5:21           ` danielhf
2005-09-04 13:13             ` Sven Köhler
2005-09-03 18:35 ` Greg Yasko
2005-09-05 13:56   ` danielhf
2005-09-05 14:31     ` Robert Crawford
2005-09-05 14:51       ` Steve Evans
2005-09-05 17:17         ` Robert Crawford
2005-09-05 17:55         ` Robert Crawford [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=200509051355.11314.flacycads@cox.net \
    --to=flacycads@cox.net \
    --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