| 1 |
Philip Webb wrote: |
| 2 |
> 120421 Dale wrote: |
| 3 |
>> Philip Webb wrote: |
| 4 |
>>> You actually have to remove the offensive file |
| 5 |
>>> from the dir, not simply rename it to 'xx70xx...' ! |
| 6 |
>> That's the same way files in /etc/portage/ works too. |
| 7 |
>> I do wish we could put a # on the front to make it ignore files. |
| 8 |
>> We can dream I guess. |
| 9 |
> |
| 10 |
> Yes & why did it start doing this only with the new mobo |
| 11 |
> -- was it provoked by seeing an unknown driver ? |
| 12 |
> And whyever did it want to rename the device to 'eth1' ?? |
| 13 |
> |
| 14 |
|
| 15 |
|
| 16 |
I would imagine udev saw something different and renamed it. It's not |
| 17 |
the first time something like this has happened. I doubt it will be the |
| 18 |
last either. Udev is hard to predict for sure. |
| 19 |
|
| 20 |
Dale |
| 21 |
|
| 22 |
:-) :-) |
| 23 |
|
| 24 |
-- |
| 25 |
I am only responsible for what I said ... Not for what you understood or |
| 26 |
how you interpreted my words! |
| 27 |
|
| 28 |
Miss the compile output? Hint: |
| 29 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives