All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problems
Date: Mon, 18 Apr 2005 20:49:33 +0000	[thread overview]
Message-ID: <20050418204933.GA19415@kroah.com> (raw)
In-Reply-To: <200403071315.02925.michal@cihar.com>

On Mon, Apr 18, 2005 at 12:13:38PM -0600, clemens@dwf.com wrote:
> is.
> 
> If it is legal, then I have a complaint...
> 
> This has happened to me twice now (three times if you count the twice
> yesterday while I was trying to dig my way out).
> 
> It would seem, that on a reboot (on the way down, on the way up, Im not
> sure) that udev proceeds to remove all files that were active at the
> time the system went down.  I will assume that it created all of these
> files, so it thinks that it can remove them.

No, odds are /dev is mounted on a ram or tmpfs filesystem, which means
the whole thing was thrown away when the machine was rebooted.  udev did
not remove anything on it's own.

> Hey what ever happened to the MKNOD (?) script that used to be in
> UNIX systems?  I dont see it in Fedora2.  That would have helped in
> the repair.

Try asking the Fedora people, that's up to them, and how they package
udev.

> I had this same problem a couple of months ago, and just gave up
> and reinstalled the OS.  I hate to do that as it may only take 30-45m
> to do the reinstall, but it takes another week to get everything
> configured back the way it was...

Sounds like you need to learn about backing stuff up :)

> Needless to say, Im not going to use
> 
>         udev_root="/dev/"
>         udev_db="/dev/.udev.tdb
> 
> again, anthough it sure makes life a lot simpler.
> 
> And, Im going to have to go and remove it from some machines at the
> lab, before disaster strikes there too.

Might I suggest a newer distro than Fedora2?  Like one that actually
implementes udev properly?

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
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

  parent reply	other threads:[~2005-04-18 20:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 12:15 udev problems Michal Čihař
2004-03-07 12:29 ` Kay Sievers
2004-03-07 12:47 ` Michal Čihař
2004-03-07 13:10 ` Michal Čihař
2004-03-07 13:44 ` Kay Sievers
2004-03-07 13:49 ` Michal Čihař
2004-03-07 14:05 ` Kay Sievers
2004-03-07 14:16 ` Kay Sievers
2004-03-07 14:20 ` Michal Čihař
2004-03-07 14:28 ` Kay Sievers
2004-03-07 14:30 ` Michal Čihař
2004-03-07 14:41 ` Kay Sievers
2004-03-07 14:43 ` Michal Čihař
2004-03-07 15:11 ` Michal Čihař
2004-03-07 15:28 ` Michal Čihař
2004-03-07 15:46 ` Michal Čihař
2005-04-18 18:13 ` clemens
2005-04-18 20:49 ` Greg KH [this message]
2005-04-18 21:02 ` David Zeuthen
2005-04-18 21:12 ` Greg KH
2005-04-18 21:27 ` clemens
2005-04-18 21:36 ` Kay Sievers
2005-04-19  7:36 ` clemens

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=20050418204933.GA19415@kroah.com \
    --to=greg@kroah.com \
    --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.