| 1 |
On Thu, 22 Aug 2013 07:26:38 +0200, J. Roeleveld wrote: |
| 2 |
|
| 3 |
> > So the only "out of sync" scenario that should matter is with the |
| 4 |
> > kernel or kernel modules. Even if it were out of sync with your |
| 5 |
> > current toolset it should still be able |
| 6 |
> > to perform the pivot. Shouldn't any "userland stuff" that |
| 7 |
> > breaks initramfs BE in initramfs? |
| 8 |
> |
| 9 |
> Incorrect, there are userland tools, like LVM and MDADM (layout 1.2 does |
| 10 |
> NOT support auto-assembly by kernel), that are needed to access of the |
| 11 |
> filesystems. |
| 12 |
> |
| 13 |
> It is possible that an older version of one of these tools, after an |
| 14 |
> update, can no longer access the disks succesfully. When portage updates |
| 15 |
> this package, the initramfs is not automatically updated with the new |
| 16 |
> version. |
| 17 |
|
| 18 |
The userland tools either work or they don't. Nothing stops working as |
| 19 |
soon as an update becomes available. The versions of the tools in the |
| 20 |
root filesystem don't matter at this point, because the root filesystem |
| 21 |
is not mounted. The initramfs is a standalone environment that doesn't |
| 22 |
stop working just because someone changed a file on an unmounted |
| 23 |
filesystem. |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Neil Bothwick |
| 28 |
|
| 29 |
No, you *can't* call 999 now. I'm downloading my mail. |
Archives