From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: udev, was: Re: File system erase the softsynth device
Date: Tue, 24 Oct 2006 09:53:47 -0700 [thread overview]
Message-ID: <20061024165347.GA7463@localhost.localdomain> (raw)
In-Reply-To: <20061024134507.GA5143@lnx3.holmesgrown.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I personally don't like it. When I decided to try it one time, most of
my hardware was non-functional after boot, until I loaded the modules
by hand, upon which the hardware was functional, and /dev was
populated. Since I prefer to have functioning hardware after boot,
without loading modules for everything by hand, rather then having a
customized /dev directory, I went back to using hotplug under debian
testing, currently running linux 2.6.18, and have been happily doing
so ever since. I must admit however, that when I tried it, I didn't
have the time to read up on it, and was expecting udev to work out of
the box, just as hotplug has for me. That's just my opinion, based on
my quick and undetailed experience, so take it for what it's worth.
Greg
On Tue, Oct 24, 2006 at 06:45:07AM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> This might be a dumb off-topic question but what can you tell me about
> udev? I've heard of it but haven't done anything with it around here.
> When upgrading to Slackware 11.0, they included some notes about major
> changes with upgrading it. I see on one of my boxes that udev as a
> package is installed but the startup script is not marked for execution;
> so it must be installed but nopt running rightnow. Is it a good thing
> to use? I'm currently on kernel 2.6.16.12 but plan to move up to 2.6.18
> when I get around to it:).
>
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFPkUb7s9z/XlyUyARAgpFAKDCuKNI7YB7npXGsXbPepkiPusK8gCgmC5f
w1SyURlXQ9OBxtfZlTBGRR0=
=QbXX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Jan Buchal
` Chris Norman
` Jan Buchal
` Kenny Hitt
` Steve Holmes
` Igor Gueths
` Gregory Nowak [this message]
` udev, was: " Chuck Hallenbeck
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=20061024165347.GA7463@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).