On 06/12/2020 09:42 pm, Martin Gregorie wrote:
> On Sun, 06 Dec 2020 21:00:33 +0000, Chris Elvidge wrote:
>
>> But it doesn't do any good, either.
>>
> This idea originally came from you!

I'm confused. I was talking about the .cache directory.
What's the rest of this about?
What has the boot partition have to do with .cache?

>
> In fact, it seems that the boot partition is mounted on /boot as part of
> the boot process, so on thinking about it, the only effect of it having
> content *should* be that the files in it occupy space in the filesystem
> partition but are inacessable while Raspbian is running. Consequently
> they would be better removed so that other, more useful files can occupy
> that space.
>
> Note that, if the entire filesystem is backed up using tar, rsync or zip
> pointed at '/' while Raspbian is running from that SD card, then the
> backed up archive *will* correctly show that /boot contains the entire
> content of the boot partition. IOW, cleaning out /boot after restoring an
> offline SD card from the archive will at worst do no harm and at best
> will release some tens of MB of filespace.
>
> I've always assumed that is why you said that /boot should be emptied
> when moving the two partitions to a bigger card. Doing so makes sense, is
> fast and easy to do, so why not do it?
>
>

I use rsync -ax which doesn't copy any files not IN the / partition.

--
Chris Elvidge
England

--- SoupGate-Win32 v1.05