On Wed, 2013-02-13 at 14:03 -0600, Bruce Dubbs wrote:
> Armin K. wrote:
> > On 02/13/2013 08:46 PM, Bruce Dubbs wrote:
> >> Armin K. wrote:
> >>> lfs net-rules are prefixed with 70 while systemd net rules are prefixed
> >>> with 80. systemd net rules are ran *after* lfs ones and they basicaly
> >>> overwrite them.
> >>
> >> But 80-net-name-slot.rules is skipped internally if NAME!="" and we set
> >> NAME in 70-persistent-net.rules. What am I missing?
> >>
> >> -- Bruce
> >
> > I'm not sure. It was just a guess.
> >
> > Matt, can you try renaming 70-persisten-net.rules or whatever they are
> > called to <something higher than 80>-persistent-net.rules and see if I
> > am right.
>
> 70-persisten-net.rules depends on all of the following:
>
> UBSYSTEM=="net",
> ACTION=="add",
> DRIVERS=="?*",
> ATTR{address}=="00:25:64:38:ec:dd",
> ATTR{dev_id}=="0x0",
> ATTR{type}=="1",
> KERNEL=="eth*"
>
> of course the address changes for your device. If any of these don't
> match, then the 80-net-name-slot.rules *will* run.
I think that's the problem. My host (Fedora 18) calls my eth0 device
p5p1. So, when I run ./init-net-rules.sh, none of the DEVICES strings
match, so it only picks up my wlan0 device and populates
70-persistent-net.rules with that. That leaves 80-net-name-slot.rules
to do its thing, and give me the rather unpleasant enp7s0 device name.
Now, once I'm booted into LFS, and run init-net-rules.sh again, my
70-persistent-net.rules is populated with both my Ethernet & Wlan cards,
but the Ethernet device is once again going to get a name of enp7s0. I
can only assume this is /lib/udev/write_net_rules (called toward the end
of init-net-rules.sh) doing this?
Cheers,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
