| 1 |
"Walter Dnes" <waltdnes@××××××××.org> writes: |
| 2 |
|
| 3 |
> Similarly, the vast majority of home users have a machine with one |
| 4 |
> ethernet port, and in the past it's always been eth0. |
| 5 |
|
| 6 |
Since 10 years or so, the default is two ports. |
| 7 |
|
| 8 |
> Now the name varies in each machine depending on the motherboard |
| 9 |
> layout; oogabooga11? foobar42? It may be static, but you don't know |
| 10 |
> what it'll be, without first booting the machine. In a truly |
| 11 |
> Orwellian twist, this "feature" is referred to as "Predictable" |
| 12 |
> Network Interface Names. It only makes things easier for corporate |
| 13 |
> machines acting as gateways/routers, with multiple ports. Again, the |
| 14 |
> average home user is being jerked around for a corporate agenda. |
| 15 |
|
| 16 |
Perhaps the hidden agenda was to make the names indistinguishable and |
| 17 |
unrecognisable, forcing everyone to use copy and paste --- after at |
| 18 |
least double-checking which port is which --- to eliminate human and |
| 19 |
typing errors in order to get more predictable results. |
| 20 |
|
| 21 |
Otherwise, how would using unrecognisable names for network ports make |
| 22 |
anything easier for corporate machines? |
Archives