1 |
> On Jul 16, 2015, at 3:46 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> |
3 |
> On 16/07/2015 21:34, James wrote: |
4 |
>> Hello:: |
5 |
>> |
6 |
>> Background:: |
7 |
>> I have had many challenges with grub 2, in the past (as have many). |
8 |
>> |
9 |
>> Current:: |
10 |
>> Grub-2.02_beta2-r3 wants to upgrade to |
11 |
>> grub-2.02_beta2-r7 It appears to be marked stable..... |
12 |
>> |
13 |
>> |
14 |
> |
15 |
> The don't use it, grub:0 still works just fine :-) |
16 |
> |
17 |
|
18 |
It looks like he’s going from grub-2.02 to grub-2.02. I don’t think any action is necessary. |
19 |
|
20 |
> I gave grub-2 a try earlier this week and once again couldn;t figure out |
21 |
> how to install that mini-OS that bootstraps a boot loader which |
22 |
> bootstraps a boot loader which loads code that loads a kernel. So back |
23 |
> to grub:0 for me |
24 |
> |
25 |
> |
26 |
> -- |
27 |
> Alan McKinnon |
28 |
> alan.mckinnon@×××××.com <mailto:alan.mckinnon@×××××.com> |
29 |
How complicated is your partitioning? I have always used a single partition for all of my personal machines, and it’s always been a simple process. |
30 |
|
31 |
grub-install --recheck /dev/sda |
32 |
grub-mkconfig -o /boot/grub/grub.cfg |
33 |
|
34 |
I know that for servers it’s common to have a bunch of partitions to prevent a rogue process from filling up the entire disk and tanking the entire system, but I can’t imagine it’s that much more complex. |
35 |
|
36 |
Alec |