1 |
Alan McKinnon wrote: |
2 |
> I see that as a liability not a feature. Our routers have very clear |
3 |
> naming conventions for interfaces and they are exactly how Cisco |
4 |
> enumerates them and no other way. It's a firing offense to dick with |
5 |
> them and dream up useless "descriptive names". Mind you, these for the |
6 |
> most part are big iron with several 1000 interfaces each and 100+ |
7 |
> support personnel working on them. But even the on-site routers and |
8 |
> firewalls at customer premises have the same rule. I assume we are |
9 |
> talking about kit that routes properly (whether a Unix or something |
10 |
> else is not relevant) and not some joke system. As for NICs that do |
11 |
> not come up at boot time in a consistent order, if any piece of |
12 |
> hardware in our DC did that it would be sent right back to the vendor |
13 |
> labeled as a piece of shit with a demand for a refund. FFS, if my boss |
14 |
> shells out 3 months wages for some iron and it can't even get |
15 |
> something that basic correct, I start to wonder what else might be |
16 |
> dodgy. There is ZERO excuse for a system that cannot deterministically |
17 |
> enumerate it's fixed devices at boot time. |
18 |
|
19 |
I have a couple desktop rigs. I had a card that would sometimes not do |
20 |
right and change the order of my cards numbering. Since it was earlier |
21 |
than the card that hooked to my modem, it would mess up my connection to |
22 |
the internet. The card was eth0 and I had internet coming through on |
23 |
eth2. That rig now has two nics. The defective nic was removed. It |
24 |
has a new address called /dev/dump. |
25 |
|
26 |
It may be a desktop rig but I like them being recognized the same each |
27 |
time I reboot. Although, I forgot about being able to give them names. |
28 |
< scratches chin > Nah, I'll leave well enough alone. It's working and |
29 |
we don't mess with what is working, except for Fedora devs. lol |
30 |
|
31 |
Dale |
32 |
|
33 |
:-) :-) |
34 |
|
35 |
-- |
36 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
37 |
|
38 |
Miss the compile output? Hint: |
39 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |