1 |
On 19/08/13 22:20, Alecks Gates wrote: |
2 |
> On Mon, Aug 19, 2013 at 8:26 AM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
3 |
>> |
4 |
... |
5 |
> |
6 |
> Can someone please explain to me what's so hard and/or complicated |
7 |
> about making an initramfs? At this point in time it's extremely |
8 |
> simple for me, but I only manage relatively simple systems (although |
9 |
> I'd like that to change soon). All I do is add one extra line (for |
10 |
> example - "dracut -H --kver=3.11.0-rc6") to my kernel install |
11 |
> procedure. |
12 |
> |
13 |
> Granted, the only reason I have an initramfs is for the plymouth |
14 |
> splash screen (other systems aren't desktops) -- but from everything I |
15 |
> can see it's not too complicated otherwise. |
16 |
> |
17 |
|
18 |
Ive had one employment threatening episode when a redhat system using |
19 |
initramfs wouldnt boot (my fault in fact, I got out of sync with |
20 |
initramfs/kernel version on the install) and it was an important server. |
21 |
Since then I eliminated them and surprise never had a failure until |
22 |
recently when I started using genkernel. So now I have mostly systems |
23 |
using initramfs, 3 customised, one of which will no longer hibernate to |
24 |
disk and I am suspecting the initrd. |
25 |
|
26 |
Its fine when it all works, but the question in this case is how many |
27 |
times do I want to crash the system trying to fault-find it? Its not |
28 |
that it doesn't work, or that its generally reliable but that its an |
29 |
unwanted/unneeded extra point of failure built around an extra workload. |
30 |
Distros like Redhat have specialists that do that, we dont and we are |
31 |
NOT competing in Redhats market space so "why"? |
32 |
|
33 |
I actually think working towards a read-only /usr is a good idea and am |
34 |
ambivalent about it being in the root, its the baggage thats being |
35 |
worked in alongside this thats the problem for me. |
36 |
|
37 |
BillK |