| 1 |
On 2020-11-25, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Wed, 25 Nov 2020 13:30:46 -0600, Dale wrote: |
| 3 |
> |
| 4 |
>> >> If I can get rid of the plain grub, that would free up some space. |
| 5 |
>> >> The grub2 directory isn't as big but still wouldn't hurt. |
| 6 |
>> > GRUB2 uses /boot/grub here, I suspect /boot/grub2 might be the surplus |
| 7 |
>> > one, but check the timestamps. |
| 8 |
>> |
| 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 |
> |
| 17 |
> Rename one of the directories and see if you can still boot :) |
| 18 |
|
| 19 |
That may not be a valid test. If grub is using a blocklist to locate |
| 20 |
secondary files, renaming the directory that contains those files |
| 21 |
won't bother grub at all. Even rm'ing the files and directory might |
| 22 |
not cause problems until the disk blocks of interest get reused by new |
| 23 |
files. |
| 24 |
|
| 25 |
-- |
| 26 |
Grant |
Archives