| 1 |
On Tue, 18 Dec 2012 22:05:21 -0500 |
| 2 |
Michael Mol <mikemol@×××××.com> wrote: |
| 3 |
|
| 4 |
> > I don't use separate initr* files, the initramfs is built into the |
| 5 |
> > kernel, using the latest versions of the tools installed at the |
| 6 |
> > time the kernel was compiled. That gives a single bootable file |
| 7 |
> > that, if it works now, should always work. Most changes to the |
| 8 |
> > component packages do not affect the simple job they have to do to |
| 9 |
> > get a system ready to run init. |
| 10 |
> |
| 11 |
> Just because it runs, doesn't mean it "works." For example, let's say |
| 12 |
> your network now requires an additional protocol for the host to |
| 13 |
> operate properly. Or let's say there's a security vulnerability in |
| 14 |
> some network-aware component in your initramfs. Or that some piece of |
| 15 |
> automounter code is vulnerable to corrupted filesystems on flash |
| 16 |
> drives. |
| 17 |
|
| 18 |
To borrow your own term, all that falls fair and square under the |
| 19 |
heading of "unforeseen operational requirements demanded it" |
| 20 |
|
| 21 |
Things change, packagers and sysadmins must react. |
| 22 |
|
| 23 |
-- |
| 24 |
Alan McKinnon |
| 25 |
alan.mckinnon@×××××.com |
Archives