mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anthony DiSante <theant@nodivisions.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Has anyone dumped udev for devfs?
Date: Fri, 04 Feb 2005 00:54:14 -0500	[thread overview]
Message-ID: <42030E06.8080900@nodivisions.com> (raw)
In-Reply-To: <20050204050822.GT2493@waste.org>

Kevin Fries wrote:
 > Any ETA on when udev is going to be ready for prime time?  And, any
 > clue why Fedora insists on relying on a program that does not f*(&%ing
 > work!!!!
 >
 > I am trying to get a Microtek X12 USL scanner attached, and udev fails
 > to mount it, every time.  Has anyone tried uninstalling udev and
 > reinstalling devfs to stop all these damn usb failures?
 >
 > If so, any hints on how not to make your system unstable?
 >
 > TIA
 > Kevin Fries

I haven't gone back to devfs, but I feel your pain.  udev+hal worked fine 
for a couple months, until hald started intermittently locking up.  Now I 
can't go 2 days without a reboot, because hald so often goes into 
"uninterruptible sleep" and is totally unkillable.  I've upgraded udev, hal, 
and my kernel a bunch of times, but nothing has fixed this.  And it's not a 
single piece of hardware; sometimes it's USB, sometimes Firewire, sometimes 
a CDROM, that causes hald to take a nap, permanently.

-Anthony DiSante
http://nodivisions.com/

  reply	other threads:[~2005-02-04  5:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  3:44 e1000, sshd, and the infamous "Corrupted MAC on input" Ethan Weinstein
2005-02-03  7:04 ` Matt Mackall
2005-02-04  4:16   ` Ethan Weinstein
2005-02-04  5:08     ` Matt Mackall
2005-02-04  5:54       ` Anthony DiSante [this message]
2005-02-05  4:53       ` Ethan Weinstein
2005-02-04  6:03     ` Willy Tarreau

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=42030E06.8080900@nodivisions.com \
    --to=theant@nodivisions.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®