1 |
Grant Edwards wrote: |
2 |
> On 2020-11-25, Neil Bothwick <neil@××××××××××.uk> wrote: |
3 |
>> On Wed, 25 Nov 2020 13:30:46 -0600, Dale wrote: |
4 |
>> |
5 |
>>>>> If I can get rid of the plain grub, that would free up some space. |
6 |
>>>>> The grub2 directory isn't as big but still wouldn't hurt. |
7 |
>>>> GRUB2 uses /boot/grub here, I suspect /boot/grub2 might be the surplus |
8 |
>>>> one, but check the timestamps. |
9 |
>>> Well, grub2 shows the latest change. Plain grub shows older changes. |
10 |
>>> Most things in plain grub shows a date of April 2019. Things in grub2 |
11 |
>>> are 2013 except for grub.cfg which shows June 2020. That is likely |
12 |
>>> about the time I rebuilt my last kernel, or somewhere close to that |
13 |
>>> anyway. Sort of confusing. |
14 |
>>> |
15 |
>>> Just wondering if leaving that alone may be best. ;-) |
16 |
>> Rename one of the directories and see if you can still boot :) |
17 |
> That may not be a valid test. If grub is using a blocklist to locate |
18 |
> secondary files, renaming the directory that contains those files |
19 |
> won't bother grub at all. Even rm'ing the files and directory might |
20 |
> not cause problems until the disk blocks of interest get reused by new |
21 |
> files. |
22 |
> |
23 |
> -- |
24 |
> Grant |
25 |
|
26 |
Great. I don't know if I can remove them and boot normal or not. :/ I |
27 |
guess I'll leave them for now. Maybe I can create a chroot and see what |
28 |
it looks like after I install grub2??? I got equery to list the files |
29 |
grub installs but it doesn't show anything being put in /boot. I |
30 |
wonder, if I remove all but grub.cfg, would installing it again, like |
31 |
after a kernel upgrade, would install what is needed again??? |
32 |
|
33 |
Dale |
34 |
|
35 |
:-) :-) |