| 1 |
Il 24/01/2013 21:45, Michael Orlitzky ha scritto: |
| 2 |
> On 01/24/13 15:39, Michael Orlitzky wrote: |
| 3 |
>> On 01/24/13 15:26, vivo75@×××××.com wrote: |
| 4 |
>>>> If you're going to upgrade both anyway, you should be upgrading the |
| 5 |
>>>> kernel first. That way if you lose power or the system crashes, the box |
| 6 |
>>>> can reboot. |
| 7 |
>>>> |
| 8 |
>>> which can be the exact opposite order if instead you have to _disable_ a |
| 9 |
>>> feature in the kernel which would make udev not bootable. |
| 10 |
>>> Don't remember exactly what, but it happened in the past when Greg was |
| 11 |
>>> still maintainer and an obsolete feature was making udev confused. |
| 12 |
>>> |
| 13 |
>> Suppose, you're on e.g. udev-1, and, |
| 14 |
>> |
| 15 |
>> * udev-2 requires CONFIG_FOO=n |
| 16 |
>> * udev-1 will not boot with CONFIG_FOO=y |
| 17 |
> Sorry, that should be an 'n' instead of a 'y'. I started out with 'y' |
| 18 |
> and tried to switch to 'n' to match your example. |
| 19 |
> |
| 20 |
> |
| 21 |
actually it wasn't an issue that could made a system un-bootable but was |
| 22 |
like this: |
| 23 |
|
| 24 |
* udev-129 could live with CONFIG_SYSFS_DEPRECATED=y |
| 25 |
* udev-130 require CONFIG_SYSFS_DEPRECATED not set |
| 26 |
|
| 27 |
The example was given just to underline the fact that a different emerge |
| 28 |
order may be required. |
| 29 |
|
| 30 |
cheers |
Archives