From: "Jim Bodkikns (Dakotacom)" <JimBodkins@yahoo.com>
To: linux-hotplug@vger.kernel.org
Subject: udev issues
Date: Mon, 23 Jan 2006 15:48:51 +0000 [thread overview]
Message-ID: <000901c62034$83ee5260$6401a8c0@HomePC> (raw)
This is mainly a (pointless) comment.
I frankly dont give a damn what dev system is used. But frankly, the
isssues that are caused and not dealt with with the introduction of udev are
entirely unacceptable. They are, to me, symptomatic of a half baked idea.
What is the raw half? Implementation. I am currently running Debian (Sarge)
2.4.x and cant upgrade to 2.6 because of your 'mess' of a 'solution'. Dont
blame debian.
Do you understand that this makes the core linux effort appear entirely
amateurish? I should ask ... is it entirely amateurish? Can you do better?
Have you done your best? This falls very short IMO - even IF it is a better
device filesystem.
Jim
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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
next reply other threads:[~2006-01-23 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 15:48 Jim Bodkikns (Dakotacom) [this message]
2006-01-23 16:15 ` udev issues Andrey Borzenkov
2006-01-23 16:28 ` Dmitry Torokhov
2006-01-23 17:10 ` Robert Kennedy
2006-01-23 17:22 ` Brian Sammon
2006-01-23 18:00 ` Andrey Borzenkov
2006-01-23 18:08 ` Marco d'Itri
2006-01-23 18:36 ` Olivier Blin
2006-01-23 18:38 ` Marco d'Itri
2006-01-23 19:39 ` Patrick Mulder
2006-01-23 19:51 ` Andrey Borzenkov
2006-01-23 20:27 ` Greg KH
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='000901c62034$83ee5260$6401a8c0@HomePC' \
--to=jimbodkins@yahoo.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 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 NNTP newsgroup(s).