| 1 |
On 22/08/2013 08:20, J. Roeleveld wrote: |
| 2 |
> On Wed, August 21, 2013 22:02, Neil Bothwick wrote: |
| 3 |
>> On Wed, 21 Aug 2013 11:50:57 -0400, Tanstaafl wrote: |
| 4 |
>> |
| 5 |
|
| 6 |
[snip] |
| 7 |
|
| 8 |
>> No one has demonstrated that it can. An initramfs isn't magic, it |
| 9 |
>> caries out a couple of trivial tasks before switching to the real root |
| 10 |
>> partition. |
| 11 |
> |
| 12 |
> The issue mentioned was an example. It was also: |
| 13 |
> 1) The only one I can remember from the last 4 or 5 years |
| 14 |
> 2) Easily avoided with a "rebuild initramfs" notice during upgrade |
| 15 |
|
| 16 |
Take out that word "Easily", it doesn't belong there. |
| 17 |
|
| 18 |
What is the trigger condition that causes the message to be emitted? |
| 19 |
|
| 20 |
Will it be in each ebuild whose files might end up in an intramfs? |
| 21 |
Expect much bitching and refusing from the devs who will have to |
| 22 |
maintain that, so not gonna fly. |
| 23 |
|
| 24 |
Will it be at the tail end of all emerge actions? Ain't gonna fly either |
| 25 |
as that is completely not a portage function. The PM installs and |
| 26 |
updates packages, it does not check what you then do with the results. |
| 27 |
And portage doesn't really know if you a) have an initramfs, b) where it |
| 28 |
is, c) what you want in it (as opposed to what you have in it) |
| 29 |
|
| 30 |
Will it be a reminder after installing kernel sources? Changed sources |
| 31 |
are not the cause of the isolated problems being mentioned here. Changed |
| 32 |
userland is. |
| 33 |
|
| 34 |
Face it. If you want to use an initramf, IT IS THE USERS JOB to keep it |
| 35 |
working as he wants it to work. It's a somewhat similar problem to out |
| 36 |
of tree modules and keeping them installed and in sync - portage makes |
| 37 |
zero effort to help with that one too.-- |
| 38 |
-- |
| 39 |
Alan McKinnon |
| 40 |
alan.mckinnon@×××××.com |
Archives