You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But /sysroot/tmp is different: /tmp → /sysroot/tmp
Then when I look at the x86_64 fedora silverblue directory layout, I see other directories not /var, are they all the immutable directories without state? Why was /var/home/ setup as different directory from /var/?
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 476.9G 0 disk
├─sda1 8:1 0 600M 0 part /boot/efi
├─sda2 8:2 0 1G 0 part /boot
└─sda3 8:3 0 475.4G 0 part /var/home
/var
/sysroot/ostree/deploy/fedora/var
/usr
/etc
/
/sysroot
What were the specific commands used to create this btrfs layout of volume and subvolumes for the silverblue installer?
The text was updated successfully, but these errors were encountered:
The layout is made at install time in Anaconda, not sure where exactly.
travier
changed the title
[master] Doc issue in file modules/ROOT/pages/technical-information.adoc please clarify the silverblue btrfs layout and their role
technical-information: Clarify the btrfs layout and their role
Mar 8, 2024
Ok so I understand /var holds the state for silverblue and is symlinked by:
But /sysroot/tmp is different:
/tmp → /sysroot/tmp
Then when I look at the x86_64 fedora silverblue directory layout, I see other directories not /var, are they all the immutable directories without state? Why was /var/home/ setup as different directory from /var/?
What were the specific commands used to create this btrfs layout of volume and subvolumes for the silverblue installer?
The text was updated successfully, but these errors were encountered: