[Swlug] Boot directory

[Marcus Davage]

Good spot, Sam. Yes, I do reboot a kernel upgrade before I autoremove.

Marcus

On Fri, 20 Sep 2019, 11:15 Sam Braithwaite via Swlug, <
swlug at mailman.lug.org.uk> wrote:

> Hi Bill & Marcus. I also run apt-get autoremove after a kernel upgrade,
> although I think if you want to be completely safe you should try
> rebooting into the new kernel first, as after you've run autoremove, I
> don't think you'll have the option to boot into your old kernel again,
> so if you had problems with the new kernel you'd be stuck. (I think this
> is in reality quite rare, but I seem to remember I have had problems
> with this in the past relating to proprietary graphics drivers - anyone
> else know any more about this?)
>
> Sam
>
>
> On 20/09/2019 10:20, Marcus Davage via Swlug wrote:
> > Hi Bill. I've been a happy user of Linux Mint for years and years, on
> > all my home equipment. I just have a mental note to run autoremove each
> > time I'm prompted to upgrade the kernel.
> >
> > Side note: had an IFA around the other night, who was running Linux Mint
> > on his laptop. He emailed me a password encrypted zip file, which
> > Archive Manager wouldn't extract. I ended up having to install another
> > zip manager and use that. (After unzipping it on my OnePlus phone first!)
> >
> > Marcus
> >
> > On Wed, 18 Sep 2019, 12:26 Bill Thomson via Swlug,
> > <swlug at mailman.lug.org.uk <mailto:swlug at mailman.lug.org.uk>> wrote:
> >
> >     Thanks Mark, that's useful to know 🙂 I guess I'll just run
> >     autoremove every so often to keep the /boot partition reasonably
> clean.
> >
> >     Many thanks,
> >
> >     Bill
> >
> >     On 18 Sep 2019 12:12, Mark Einon via Swlug <swlug at mailman.lug.org.uk
> >     <mailto:swlug at mailman.lug.org.uk>> wrote:
> >
> >         Be careful doing this!
> >
> >         Not all systems/distros can read all filesystem types prior to
> >         initrd
> >         booting (as this is done by the bootloader).
> >
> >         One of the compelling reasons for having a separate /boot is
> >         that it's
> >         formatted in a known supported FS, whilst you can have any Linux-
> >         supporting FS for your main partiton.
> >
> >         Mark
> >
> >         On Wed, 2019-09-18 at 10:10 +0100, Colin Law via Swlug wrote:
> >          > On Wed, 18 Sep 2019 at 10:04, Bill Thomson via Swlug
> >          > <swlug at mailman.lug.org.uk <mailto:swlug at mailman.lug.org.uk>>
> >         wrote:
> >          > > Hi Colin, that seems to have done the trick! I've freed up
> >         in excess
> >          > > of 2Gb in the boot directory - thank you!
> >          > >
> >          >
> >          > For future reference I believe it is generally considered
> >         better not
> >          > to have a separate partition for /boot as it can give rise to
> >         this
> >          > problem.  Just put /boot in the main root (/) partition so
> >         that it
> >          > will not fill up.  If it /boot actually fills up completely
> >         it can be
> >          > a big pain to recover as you can't then run autoremove, you
> >         have to
> >          > manually remove the old kernels.
> >          >
> >          > Colin
> >          >
>
> ___________________________________________
> This email has been scanned by iomartcloud.
> http://www.iomartcloud.com/
>
>
> --
> Swlug mailing list
> Swlug at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/swlug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/swlug/attachments/20190922/c0ebab14/attachment.html>