From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: development@lists.ipfire.org
Subject: Overfull Filesystems how to solve?
Date: Sat, 18 Jan 2020 10:57:08 +0100 [thread overview]
Message-ID: <70bd4343d85cf136b677fc6d23370316a071e22d.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Hi,
Daniel encountered the problem that his root partition was written full
because of the qemu addon being too big (200 MB). See bug #12268 for
details.
So he suggested moving the path /usr/share/qemu to /var. I do not
really like this solution as there are standards how the filesystem
hierarchy works under Linux.
Furthermore, as the systems become bigger (eg. moving python3 to the
core) this problem will become more relevant to us. So I would like to
start a discussion on how to solve this. Moving things to /var can only
be a temporary solution. Should we force a reinstallation, which solves
the root of the problem?
Jonatan
next reply other threads:[~2020-01-18 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 9:57 Jonatan Schlag [this message]
2020-01-18 10:30 ` Tapani Tarvainen
2020-01-19 18:16 ` Michael Tremer
2020-01-20 4:17 ` Tapani Tarvainen
2020-01-20 10:38 ` Michael Tremer
2020-01-20 11:39 ` Tapani Tarvainen
2020-01-20 11:49 ` Michael Tremer
2020-01-19 18:14 ` Michael Tremer
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=70bd4343d85cf136b677fc6d23370316a071e22d.camel@ipfire.org \
--to=jonatan.schlag@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