On 12/20/2011 8:56 PM, Anders Johansson wrote:
On Wednesday 21 December 2011 02:06:21 Joachim Schrod wrote:
From current experience of my staff: that is not sufficient. If we want boot-problem-resolving tools to be available, we have to put them in initrd. That's the only way to be sure they will be available if GRUB/lilo succeeds booting.
Which tools do you mean? Given that /bin and /sbin will be unavailable only when the root partition fails to mount, what tools do you put into the initrd to resolve that? Aside from fsck perhaps, but that is already in there
ANders
Tons of things, but put it this way, the current initrd is not enough, but the net install iso initrd, after it has downloaded and unpacked it's other images, is good enough, but even there it's largely because it includes enough connectivity tools to let you get things from elsewhere that weren't included already when you discover you need them. Almost any time there is a problem booting and I'm dropped to the initrd emergency shell, Unless it's a plain case of needing to manually run mdadm because for whatever reason it failed to run automatically, I have to boot an install image and use it as the emergency repair platform. dd, parted, mkfs for all fs's, fsck for all fs's, vi, proprietary raid card utils, it hasn't happened lately and I'm too busy pretending not to panic at the time to take notes so I could later answer this question. The answer is "all manner of things". -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org