From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 122 updates
Date: Thu, 02 Aug 2018 22:46:00 +0100 [thread overview]
Message-ID: <e0d228246b948816a74b017c151cbacb7b57c5cd.camel@ipfire.org> (raw)
In-Reply-To: <H000006e00429396.1533236266.mail.at4b.net@MHS>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Hello Fred,
yes, this might indeed be an issue.
The updater will catch that and not install the update if not enough
disk space is available on either / or /boot.
So you can try, but it might make sense to reinstall or if you are very
brave remove the old kernel and then install the update :)
-Michael
On Thu, 2018-08-02 at 14:57 -0400, Kienker, Fred wrote:
> FYI – some of the very old firewalls, installed long ago before there was an x86-64 version, have VERY small /boot partitions. This may pose issues updating to Core 122.
>
> This screen shot was taken from a very old IPFire system running the x586 version:
>
> [root(a)fw ~]# df -h
> Filesystem Size Used Avail Use% Mounted on
> devtmpfs 1001M 4.0K 1001M 1% /dev
> tmpfs 1006M 12K 1006M 1% /dev/shm
> tmpfs 1006M 264K 1006M 1% /run
> /dev/sda3 2.0G 1001M 840M 55% /
> /dev/sda1 24M 18M 4.4M 81% /boot
> /dev/sda4 71G 52G 16G 78% /var
> none 8.0M 12K 8.0M 1% /var/lock
> none 1006M 16K 1006M 1% /var/log/vnstat
> none 1006M 32M 975M 4% /var/log/rrd
>
> Note that the /boot partition is only 24M in total and has only 4.4M free.
>
> Michael’s posting on the website about maybe it is time for a “clean” reinstall is very much to the point. But this is very hard to do with these older systems. I’m not sure it is possible to install 122 then restore a backup from 120, but I may well be wrong.
> Best regards,
> Fred
>
next parent reply other threads:[~2018-08-02 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <H000006e00429396.1533236266.mail.at4b.net@MHS>
2018-08-02 21:46 ` Michael Tremer [this message]
[not found] <578BF898-3F94-4ED9-BD24-983245F07D5B@rymes.com>
2018-08-03 8:14 ` Michael Tremer
2018-08-03 17:17 ` Kienker, Fred
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0d228246b948816a74b017c151cbacb7b57c5cd.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox