Re: /var/lib/flatpak/repo/objects using up /var partition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2025-01-19 22.21, Mike Wright wrote:
On 1/19/25 11:00, Robin Laing wrote:

It needs to be planned for as many of us, me included, didn't have enough space if /var partition to account for this change.

I am now going to be rebuilding machines that have small /var partitions.  At least with flatpack, I can use applications that are not in any Fedora repository.

Many of the servers and services, ie dnf, apt, postgres, mysql, apache (httpd), knot (dns), among others (except bind9 which for historical purposes uses /etc), have been using /var since I can remember.  Adding flatpak to the mix makes sense.  Snaps are there now, too, but I seem to recall them originally hanging out at /snap, at least on Ubuntu.

I have separate partitions for /home and /var.  You could even go the LVM route which gives you the ability to grow the storage area relatively easily.  I've never lost anything doing it that way.

:m


I am not against flatpak or snap using /var. I agree with the standard and how it is implemented. All I meant to say is it is part of the future and what we did in the past needs to be updated to meet today's needs.

About to rebuild and give / and boot to a single small SSD.

Giving up on partitioning out /var. /home will be part of the same drive but each user will be on a different drive/partition and I have been doing that for a long time.

If I cannot get everything but home and swap on a single 260G drive, Linux has a problem.

Oh the days of a full graphical OS on a 40Gig drive.

I have lost data with LVM's and btrfs at different times in the past and have to regain my trust.

I do want to move to a COW FS in the future. I don't need to merge multiple devices. If it doesn't fit on one drive, then a new drive goes in. Old school here.

In some searches, I came across this that I find interesting with some recent discussions I have been involved in.

https://access.redhat.com/solutions/197643 (Updated August 6 2024 at 7:27 AM )

The Btrfs file system received numerous updates from the upstream in Red Hat Enterprise Linux versions 6.0 through 6.6 and 7.0 through 7.4. It will remain available in Red Hat Enterprise Linux versions 6 and 7, however there will be no further updates to this feature, and it has been fully removed in Red Hat Enterprise Linux 8.

This takes btrfs out of the running.


--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux