i think it’s also incorrect: the basic premise of arch is minimally configured, do whatever you like… no installer is going to allow a user to do everything they want, so that’s kinda not “the arch way”… it’s not some gatekeeping BS, it’s just not what arch is about, and that’s fine… that’s why there are spinoff distros that disagree and make their own - this is FOSS after all
it’s absolutely not his. he is a major and important contributor and person in the community, but linux belongs to humanity and to the community that has now written far more of linux than linus has
right! okay, i believe that’s theoretically possible, but the tools don’t exist - which is the constant problem with btrfs
… and i could be completely wrong too - this is getting to the limits of my knowledge
this is absolutely the issue… the specific thing he did is irrelevant: you play by the rules, or you gtfo… it doesn’t matter how valuable your contributions are, if you can’t treat people with respect that leads to a toxic culture that eats at the project from the inside
linus was renowned for his insults… he realised (or was told; doesn’t matter at this point) that that behaviour was inappropriate, and his behaviour is now more tempered because it’s important to be able to ensure everyone feels like their work is valued and they’re not just shoveling shit for someone else
and i say this all as someone who is absolutely ecstatic about the prospect of bcachefs and think that his code is among the most important being contributed in the past years and for the next few years: WE NEED A NEW STABLE FILESYSTEM more than almost anything… but if you allow bad behaviour, it erodes the collaborative culture and you just can not allow that in the largest collaborative software project humanity has ever created
I don’t know enough about btrfs to know whether this is feasible but perhaps it could be made a bit more log-structured such that old data is overwritten first which would allow you to simply roll back the filesystem state to a wide range of previous generations, of which some are hopefully not corrupted. You’d then discard the newer generations which would allow you to keep using the filesystem.
i’m not sure i understand quite what you’re suggesting, but BTRFD is a copy on write filesystem
so when you write a block, you’re not writing over the old data: you’re writing to empty space, and then BTRFS is marking the old space as unused - or in the case of snapshots, marking it to be kept as old data
this is literally the exact kind of thing that chatgpt hallucinates. it’s not only not trustworthy, i’d bet on it being wrong
this is actually the way it works in australia: downloading content is not illegal; sharing content is illegal
thus as a consumer, usenet is fine
obligatory ianal