| 1 |
Am 19.05.2014 22:51, schrieb Dale: |
| 2 |
|
| 3 |
> I might add, I used dracut for a while. A while back when I went to |
| 4 |
> boot back up, shutdown because my power went out, the init thingy |
| 5 |
> failed. I had zero clue on how to fix it so I edited grub to ignore the |
| 6 |
> init part and booted up the old way. Once booted, I kicked out the init |
| 7 |
> thingy and haven't built one since. I posted this a good while back, |
| 8 |
> init thingy fails, it's gone. You are right, it is one more thing that |
| 9 |
> can go wrong. It certainly hasn't fixed anything yet but it sure did |
| 10 |
> break and keep me from booting with it. ;-) |
| 11 |
|
| 12 |
you english speaking guy call that YMMV ... right? |
| 13 |
|
| 14 |
;-) |
| 15 |
|
| 16 |
on the other hand this evening I was able to boot up a live cd on a |
| 17 |
brand new Fuji TX150, transfer some rootfs-backup to it and configure |
| 18 |
grub2/systemd/dracut/btrfs/kitchensink from the chroot so that grub2 and |
| 19 |
dracut booted up correctly on the first try. |
| 20 |
|
| 21 |
... yeah ... |
| 22 |
|
| 23 |
I am quite experienced already (I think so, sorry for sounding arrogant) |
| 24 |
but I am not used to getting it right on the first time (usually you |
| 25 |
forget some fs/module/uuid-detail ... and chroot a 2nd time). |
| 26 |
|
| 27 |
This might not have been dracut's own merit but it worked anyway. |
| 28 |
|
| 29 |
Stefan |
Archives