1 |
On Tue, Aug 26, 2014 at 8:43 AM, Grant <emailgrant@×××××.com> wrote: |
2 |
>>>>> |
3 |
>>>>> SUBSYSTEM=="net", KERNEL=="enp3s0u1", NAME="net0" |
4 |
>>>> |
5 |
>>>> "enp3s0u1" isn't a kernel name; it's an "ID_NET_NAME_PATH" attribute. |
6 |
>>> |
7 |
>>> That's what came to my mind too, that's why I instructed him away from it. |
8 |
>> |
9 |
>> Yeah, I saw your email after I sent mine. |
10 |
>> |
11 |
>> I now have to figure out why you're recommending a 80< prefix when I |
12 |
>> thought that a >80 prefix is necessary in order AFAIK to override |
13 |
>> "/lib/udev/rules.d/80-net-setup-link.rules". |
14 |
>> |
15 |
>> I tried 75- instead of 85- this morning before leaving for work and |
16 |
>> the interfaces were renamed properly so I'm clearly wrong... |
17 |
> |
18 |
> I'm not totally sure that this answers your question, but: |
19 |
> |
20 |
> "Because the rules are triggered before the default one (rules are |
21 |
> triggered in alphanumerical order, so 70 comes before 80) the names |
22 |
> provided in the rule file will be used instead of the default ones. |
23 |
> The number granted to the file should be between 76 and 79 (the |
24 |
> environment variables are defined by a rule start starts with 75 and |
25 |
> the fallback naming is done in a rule numbered 80)." |
26 |
> |
27 |
> https://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=4&chap=2#doc_chap4 |
28 |
|
29 |
Thanks, it does. "fallback naming" explains it because I thought that |
30 |
80- provided override naming. But I'd still like to know more |
31 |
precisely. |
32 |
|
33 |
I looked at 75-net-description.rules and 80-net-setup-link.rules last |
34 |
night and decided to look up the source of "net_id", "path_id", |
35 |
"net_setup_link" this weekend because I was too tired... |
36 |
|
37 |
Thanks again. |