[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


Why does silverblue default to btrfs?
The whole point of btrfs is rollback snapshots and rolling back is built into the nature of silverblue with atomic updates.
So what's the point of btrfs in this case?
>>
No one cares about your GlowingOS.
>>
why does cutting edge distro do cutting edge thing by default. stop the press.
>>
>>108795864
CoW, compression and easy snapshots are nice vs ext4.
atomic os is more then just rollbacks.
>>
>>108795898
would there be a usecase where it would be beneficial to have both btrfs snapshots and an ostree image?
Would btrfs even be able to create snapshots when only /etc and /var are mutable?
>>
>>108795910
ostree doesn't protect your home subvolume user data from accidental deletion etc but you could setup snapper or similar to automatically manage snapshots.
>>
>>108795864
What? You basically explained the point of btrfs in that case.
>>
>>108795864
Take a look at opensuse microos if you want what you described.
>>
It actually makes sense in silverblue
Where it doesn't make sense is fedora where they haven't managed to enable sensible defaults, instead they just expect you to go through the whole process or manually do the fucking snapshots.
Someone decided to release a derivative distro called Ludora for that very reason, kinda stupid if you ask me, but I tried to enable btrfs bootable snapshots with working rollback and it was an absolute godawful fucking mess in Fedora 43. I managed to make it work but not without it being some hacky bullshit where snapper rollback didn't actually work and I had to use btrfs manager instead.
>>
>>108795864
just because btrfs is the default filesystem no special reason, you dont HAVE to use every single feature of the filesystem in a stock distro install.
you can probably set up a snapshot system for parts of your home folder if you want to have rollback capability for projects and such
>>
>>108798449
btrfs has prominent features most would benefit of when switching, but ext4 is still more reliable. If you're going to set it as default the least you could do is highlight those features that make it worth it over the previous choice.
>>
>>108798253
>Someone decided to release a derivative distro called Ludora for that very reason
damn i had no idea i set it up manually for periodic snapshots. it's the one thing i hate about fedora there's no reason why they should have no auto snapshots in the bootloader like cachy/suse

but also ... i feel like making a whole 'spin' to add this one feature is a bit much. people who know what this feature is probably distrohopped suse/cachy/arch at some point and can probably follow instructions to add it to fedora manually, i really dont like the idea of making spins with small changes from the very robust and long-running base distro unless there's an extremely good reason for it , im thinking in a year or two the dude making it will abandon the project and sometime later things will start breaking if you try to keep running it.

>>108798473
>but ext4 is still more reliable.
is it tho? its a couple of years older but ive honestly never had an issue with either system. fedora default configuration across all their spins/editions is fat32 /boot/efi ext4 /boot and btrfs root and its been this way ever since i remember so fedora kinda uses both by default.

i do think fedora non-atomic should integrate system snapshots (daily,on boot,before/after running dnf, integrated with grub) and both atomic and nonatomic versions should add /home snapshots as an option during install/onboarding
>>
>>108795864
It has bunch of other featurs like CoW, check-summing, compression etc.
>>
>>108795864
To snapshot the user volume for personal backups?
>>
>>108795864
btrfs can save space with deduplication and copying files between btrfs drives is pretty nice. RAID0 can protect against bit rot as well. btrfs feels kind of like a dead Facebook side project at this point tho.
>>
>>108800819
I meant RAID1
>>
Because it's currently the go-to Linux-native filesystem with CoW, dedup, volume management and so on. Distro features have nothing to do with it. You can use another filesystem if you have the need for it (most people do not).
>>
>>108795864
Companies chasing the immutabilty dragon are trying to solve for horizontal scaling of *deployment* of siloed, automated systems, not maintenance or human use. The usage of snapshotting filesystems is a way to extend it further in a very bastardized fashion for human users.

Let me elaborate: Immutable systems are retarded. The way immutability is achieved in silverblue, and even with nixos, is to be immutable/declarative at the software level - so whatever programs you have installed, their config etc. but for desktop users this is actually just pushing the problem elsewhere. Snapshotting filesystems are required to work around the fact that these immutable distros cannot solve the real issue, which is some data has to be mutable and it is that data that people both care most about, and causes the most downtime. This is true even if you start using distrobox etc to work around the mutability - those containers are themselves state, as are their manifests. Same with state kept inside flatpaks.
>>
>>108800924
For a concrete example of this: As a human user of a computer, what value do I get out of being able to roll-back /usr, /etc to a previous version, when I lose my work from /home, or my configs/state/cache etc. no longer work with the old versions? I have to rollback the FS for /home, at which point, I may as well do it for /usr/ and /etc as well. Even without any convergent system for my root FS this would just work.
The only benefit of convergent systems is for scaling deployment horizontally, users of count 1 get nothing out of it. You would be insane to not use a snapshotting FS with one though.
>>
nobody is gonna read your post, dumb effortposter
>>
The main reason Fedora goes with btrfs across all versions atomic or not is because it's a very flatpak friendly distro and btrfs lets you save a ton of space with them. Fedora even maintains its own flatpak repo but everyone just enables flathub anyways. Atomic relies of flatpak so it's obvious to stick with btrfs just like regular Fedora.
>>
Btrfs is the only Linux filesystem that doesn't completely suck ass. XFS is a close second.
>>
I remember some time ago there were benchmarking tests on file systems (maybe by proxmox?).
Anyway, one of the results showed how brfs makes more write operations by several factors on average than other file systems which would make it more detremental to ssds.
>>
File: fedora-kinoite-light.png (16 KB, 615x210)
16 KB PNG
>>108795864
I use EXT4 because I picked the LVM option.
>>
ext4 > xfs > organizing your data in a table carved in stone >>>> btrfs



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.