On 08/26/2014 09:02 AM, Robert Moskowitz wrote:
It appears to be
udevadm
Which is so complex. According to the man page 'command
--reload-rules' does NOT change any device that has existing rules. So
by that, if you change a rule, tough luck. It is SUPPOSE to be
automatic.
I have tried
On 08/26/2014 09:20 AM, fedora wrote:
On 2014-08-26 15:02, Robert Moskowitz wrote:
It appears to be
udevadm
Which is so complex. According to the man page 'command --reload-rules'
does NOT change any device that has existing rules. So by that, if you
change a rule, tough luck. It is SUPPO
On 2014-08-26 15:02, Robert Moskowitz wrote:
It appears to be
udevadm
Which is so complex. According to the man page 'command --reload-rules'
does NOT change any device that has existing rules. So by that, if you
change a rule, tough luck. It is SUPPOSE to be automatic.
I have tried export
It appears to be
udevadm
Which is so complex. According to the man page 'command --reload-rules'
does NOT change any device that has existing rules. So by that, if you
change a rule, tough luck. It is SUPPOSE to be automatic.
I have tried exporting the dev-db and looking for the mac info.
All the instructions I have found for 70-persistent-net.rules call for
running:
start_udev
But it is not on ANY of my f20 systems, arm or intel. Something
changed. Most likely related to systemd stuff.
So any pointers would be appreciated, as I still don't have this working.
On 08/25/201
