On Fri, Jul 16, 2010 at 10:47:28AM -0800, Greg Madden wrote:
> There is a 'udev' script in '/etc/init.d'. maybe doing a restart on it will
> do
> the trick.
'reload' would also do the trick there. And create less work for the
system. It only asks udevd to re-read the rules.
--
Tzafrir Cohen
udevadm trigger perhaps?
--
jvaart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktikp8y7wij4wkmddfgvl7wvm8t6zggsinolpx...@mail.gmail.com
On Friday 16 July 2010 08:15:23 H.S. wrote:
> On 10-07-16 11:48 AM, Eduardo M KALINOWSKI wrote:
> > On Sex, 16 Jul 2010, "H.S." wrote:
> >> given eth2 while I wanted eth0). After tweaking udev rules, can I have
> >> them reapplied, or the rules reread, without having to reboot? If yes,
> >> how? I
On 10-07-16 11:48 AM, Eduardo M KALINOWSKI wrote:
On Sex, 16 Jul 2010, "H.S." wrote:
given eth2 while I wanted eth0). After tweaking udev rules, can I have
them reapplied, or the rules reread, without having to reboot? If yes,
how? I have tried restarting udev and hal, but that didn't work out
f
On Sex, 16 Jul 2010, "H.S." wrote:
I just now had to change my
/etc/udev/rules.d/70-persistent-net.rules file so that a new network
card be give the same number (it was being given eth2 while I wanted
eth0). After tweaking udev rules, can I have them reapplied, or the
rules reread, without
5 matches
Mail list logo
