| 1 |
On 31 October 2014 16:16:33 WET, Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
> On Friday 31 October 2014 15:09:26 J. Roeleveld wrote: |
| 3 |
> |
| 4 |
> > I've got a few systems where grub1 doesn't work. This is more likely |
| 5 |
> caused |
| 6 |
> > by some changes in used filesystems instead of any other cause. |
| 7 |
> > If I really wanted to, I might get it to work, but I don't see the |
| 8 |
> point in |
| 9 |
> > spending time on this. |
| 10 |
> > Grub starts the boot process and then, afaik, disappears. |
| 11 |
> > Which is sufficient for me. |
| 12 |
> |
| 13 |
> My grub-0.99 lets me choose from four kernels and two or three run |
| 14 |
> levels at |
| 15 |
> boot time, and grub-2 can't handle this yet, or it couldn't the last |
| 16 |
> time I |
| 17 |
> checked. I don't suggest that everyone has a similar need, but at |
| 18 |
> least in |
| 19 |
> some cases the old grub does still have a place. |
| 20 |
> |
| 21 |
> -- |
| 22 |
> Rgds |
| 23 |
> Peter |
| 24 |
|
| 25 |
Grub2 can do that in at least three different ways. You can write a complete manual configuration, just like with 0.9,you can put a manual custom configuration in /etc/grub.d or you can put a simple she'll script in that directory that creates menu entries with each set of options for each kernel in /boot. |
| 26 |
|
| 27 |
None of these options are any more complex than creating a grub 0 configuration by hand. |
| 28 |
-- |
| 29 |
Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
Archives