== Summary ==
Silverblue and Kinoite: For new clean automatic (guided)
installations, create a "var" subvolume to be mounted at /var.
== Owner ==
* Name: [[User:chrismurphy| Chris Murphy]]
* Email: bugzilla(a)colorremedies.com
== Detailed Description ==
Currently, Silverblue and Kinoite mimic other Fedora desktops. There
is a "root" subvolume mounted at `/` and a "home" subvolume mounted at
This proposal adds a "var" subvolume to be mounted at `/var`.
The "var" subvolume will be located at the top-level of the Btrfs file
system, along-side the "root" and "home" subvolumes. An entry in
`/etc/fstab` will mount it at `/var` during startup.
== Benefit to Fedora ==
Users who opt into Btrfs features like snapshots and rollbacks.
* By moving /var into its own subvolume, it will be excluded from
snapshots and rollbacks of the "root" subvolume, which contains `/etc`
* Users will find it straightforward to rollback "root" while not
rolling back "var": including logs, VMs, databases, flatpaks, etc.
* The ability to snapshot only "var" and use Btrfs send/receive to
replicate only "var" permits for an efficient way of backing up the
variable system data.
** A clean install can restore the "root", therefore it doesn't
strictly need to be backed up. Meanwhile "var" and "home" can be
restored using snapshot replication via send/receive.
== Scope ==
* Proposal owners:
** changes to lorax and anaconda as needed so that Silverblue and
Kinoite variants have their own installation kickstart, such that
automatic/guided installation automatically creates "var".
*** possible liability, determine whether the the addition of /var
mount point for Btrfs scheme results in /var mount point for other
schemes (and inhibit)
== Upgrade/compatibility impact ==
Change will not be applied to upgrades. But we can document steps to
apply the change to existing installations.
== How To Test ==
* Do a clean installation and check `df` and `/etc/fstab` for an
explicitly listed `/var` mount point.
== User Experience ==
* The change won't generally be noticeable to users
* Users will see an additional `/var` mount point in /etc/fstab, and `df`
* Some utilities, notably backup programs like borg backup, and rsync
with -x option, will treat Btrfs subvolumes as separate file systems
and may not descend (recursively) into them.
== Dependencies ==
* Anaconda/blivet, lorax, and possibly kickstarts
== Contingency Plan ==
* Contingency deadline: beta freeze
* Blocks release? No
== Documentation ==
No significant documentation is planned other than this change proposal.
== Release Notes ==
He / Him / His
Fedora Program Manager
My name is Dorinda and I am an Associate software Engineer at Red Hat,
I'm passionate about software development, contributing to the growth
of communities and I have
some experience contributing to FOSS projects.
I am interested in becoming a package maintainer.
I learnt how to create RPM packages and build with mock and copr,
My plan so far is to maintain gpuvis and gpu-trace packages(yet to submit).
I'm also open to maintaining some more in the future.
On Wed, 2022-01-19 at 00:26 +0000, bugzilla(a)redhat.com wrote:
> Fedora Admin user for bugzilla script actions <fedora-admin-xmlrpc(a)fedoraproject.org> changed:
> What |Removed |Added
> Assignee|pahan(a)hubbitus.info |extras-orphan@fedoraproject
> | |.org
> --- Comment #6 from Fedora Admin user for bugzilla script actions <
> fedora-admin-xmlrpc(a)fedoraproject.org> ---
> This package has changed maintainer in Fedora. Reassigning to the new
> maintainer of this component.
It seems remmina has been orphaned (see above). I already package remmina personally for RHEL and
would be happy to package and maintain it for fedora, EPEL etc.
I am already in the packagers group and would only need to be given access.
*** Playing the game for the games own sake. ***
I am working on getting the xtrkcad program into fedora. Using
I have gotten to the point of creating a bug (2040728) for a new package review.
I am not sure how the process works going forward. So far there has been no action on the bug to get it reviewed. Does it usually take a while to get the review started? Do I need to inform someone to get this going? I am just looking for information on how the process works and what I need to do.
I know fedora36 is coming up. It would be good to get it into that but if I have missed dates it can wait for f37. I am not sure what the final date was/is for new packages.