1 |
On Fri, Jan 18, 2013 at 10:07:42AM -0500, Ian Stakenvicius wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA256 |
4 |
> |
5 |
> On 18/01/13 09:54 AM, William Hubbs wrote: |
6 |
> > On Fri, Jan 18, 2013 at 08:33:13AM -0500, Ian Stakenvicius wrote: |
7 |
> >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 |
8 |
> >> |
9 |
> >> On 18/01/13 07:24 AM, vivo75@×××××.com wrote: |
10 |
> >>> Since for servers predictable names are useful and for desktop |
11 |
> >>> (which usually have only one ethernet that never change) Is it |
12 |
> >>> possible to set desktop profiles to still use ethX, and base |
13 |
> >>> profile to use new naming scheme? |
14 |
> >>> |
15 |
> >>> For wireless situation may be different, many of them are |
16 |
> >>> external, could wireless be managed differently? |
17 |
> >>> |
18 |
> >> |
19 |
> >> In short, no. At least, not unless the functionality that is |
20 |
> >> currently a configure-time thing is changed into a |
21 |
> >> build-time/install-time thing controlled via a use flag. |
22 |
> > |
23 |
> > Actually,this is how I set you up by dropping the file in |
24 |
> > /etc/udev/rules.d/80-net-name-slot.rules. |
25 |
> > |
26 |
> > Nothing changes on your system unless you remove this file and do |
27 |
> > not have 70-persistent-net.rules. |
28 |
> > |
29 |
> > William |
30 |
> > |
31 |
> |
32 |
> ..right, but default behaviour can't be changed automatically |
33 |
> depending on what profile you're on, as vivo requested, since profiles |
34 |
> don't control configuration (just use flags) |
35 |
|
36 |
Right, and we have a policy against using use flags to control the |
37 |
installation of configuration files. |
38 |
|
39 |
vivo, what is your concern here exactly? |
40 |
|
41 |
William |