I wrote:
+screenuserinput
+cat gt; /etc/udev/rules.d/26-network.rules lt;lt; EOF
+ACTION==add, SUBSYSTEM==net, SYSFS{address}==52:54:00:12:34:56,
NAME=realtek
+ACTION==add, SUBSYSTEM==net, SYSFS{address}==00:a0:c9:78:9a:bc,
NAME=intel
+EOF/userinput/screen
+paraThis rule will always
I wrote:
+sect3
+ titleUdev creates a device incorrectly, or makes a wrong
symlink/title
+
+ paraThis usually happens if an incorrect rule unexpectedly matches
+ the device, or some rule unexpectedly matches the wrong device. E.g.,
+ a poorly-writen rule can match by
On Fri, Feb 24, 2006 at 05:29:07PM +0500, Alexander E. Patrakov wrote:
As written, this is incorrect. Increasing the logging verbosity achieves
nothing, because udev runs before syslogd. Proposed solution:
1) Implement some restart target in the udev initscript that kills old
udevd, starts
William Harrington wrote:
Howdy folks,
Well the dreaded day has arrived and I shall be deployed overseas. I
will be active
march 2nd and should last around 416 days. Maybe who knows...
Good luck. We'll see you when you get back.
-- Bruce
--
Bryan Kadzban wrote:
It should be easy enough to have only start and restart targets, and
have the restart target do a killall udevd (or whatever), then
simply run $0 start (perhaps after waiting for a second).
No, that won't work. We want to mount tmpfs on /dev for start, but not
for
