Bcachefs Changes Rejected Reportedly Due To CoC, Kernel Future "Uncertain"
Collapse
X
-
Originally posted by TheMightyBuzzard View PostDid you learn nothing a couple weeks ago? It's not just the alt-right that hates you. Not by a long, long way.
I don't have to be part of your moronic system to recognize the brain rot you people display in this discussions.
A CoC gouverns how people interact in a project. People who can't take their ego back when interacting with others don't have a right to be heard. This is a software development projecf, not a public forum. Get some fucking perspective or fork off..Last edited by ZeroPointEnergy; 22 November 2024, 04:37 PM.
Comment
-
-
Originally posted by mdedetrich View PostStop spreading horseshit, I have broken EXT4 so many times with hard power shutdowns, I had to deal with 4 broken machines recently at work where the filesystem corrupted itself.
.
Originally posted by mdedetrich View Post...
With CoW you can provide mathematically correct atomic operations over multiple physical block devices because CoW is only way to provide these guarantees while having zero trust the underlying hardware is working correctly.
Your implication that COW is the only way a filesystem could provide such a guarantee is also false. A well-designed fully log-based filesystem could just as easily provide the same guarantee, for example. And I'm sure there are other approaches too.
Originally posted by mdedetrich View PostFirstly I don't believe you (I think you are spreading shit) and secondly even if its true ...
Originally posted by mdedetrich View Post... bcachefs is under active development with the experimental flag. That flag will only be removed once its proven that bcachefs can recover/heal from all situations which is currently being done ...
Originally posted by mdedetrich View Post... but whats undisputed is they[COW filesystems] are much safer than journalling filesystems.
Originally posted by mdedetrich View PostWho is doing this? Your sprouting FUD.
Originally posted by mdedetrich View PostAlso wrong ZFS can be configured to only provide a success callback on a filesystem operation if the data is flushed to disk in the same way that postgres will only report an operation as successful if the data is flushed.
Originally posted by mdedetrich View PostLike I am sorry to break it to you but its kind of obvious you don't know what you are talking about.
You're a bcachefs fan. It may be hard to tell from this conversation but I am too. But you need to be able to take a step back and look at things realistically. Bcachefs is not magic and not perfect. Nor is it the only possible way forward.Last edited by clipcarl; 22 November 2024, 05:11 PM.
Comment
-
-
Originally posted by logical View Post
Hate is definitely the key word here. It's amazing how so many relish, take pride in it, and boast about having it.
Comment
-
-
Originally posted by mdedetrich View PostThis is not what the issue is, obviously having backups is a good idea. What I am talking about is that if you have a ZFS partition on non ECC memory and someone reads from it and gets the data from memory, the chance of delivering bad data is significant enough to note. Usually people don't see these issues with non ECC memory because
1. Data that is read from the filesystem without filesystems (i.e. non ZFS) is often done with zero copying so it doesn't go via RAM (which is where ECC matters)
2. For the tasks where memory is used, it often sits in L2/L3 caches where moderm CPU's use error checking. For most tasks the memory gets cached into these caches due to how obscenely large they have gotten so you also don't have to deal with the problem
The thing is with a filesystem, the amount of data we are talking about is so huge that by definition its non cachable and due to how RAM physically works, physically pushing huge amounts of data into RAM and reading off it at very high rates (and especially at overclocked/higher memory settings) greatly increases the risk of delivering bad data.
Comment
-
-
Originally posted by ZeroPointEnergy View PostDo you project your political enemy on me that fits into your simpleton worldview molded by a byparty neo-liberal hypercapitalistic dystopia? Lol
I don't have to be part of your moronic system to recognize the brain rot you people display in this discussions.
A CoC gouverns how people interact in a project. People who can't take their ego back when interacting with others don't have a right to be heard. This is a software development projecf, not a public forum. Get some fucking perspective or fork off..
No, CoCs do nothing of the sort. That's simply the lie told to get it implemented. Then what it's really used for is drumming anyone you don't like out of the project while ignoring any amount of bad behavior of those who agree with you. Every. Single. Time.
I love people who jump into "Free as in speech" projects and immediately try to put their boots on the neck of speech. It's freaking hilarious, especially when they act like the morally superior ones. Tone troll to someone who doesn't know better, noob.
Comment
-
-
Originally posted by Panix View PostAgreed - so many ppl here supporting the CoC here is alarming. If KO is a jerk - it's their issue to deal with - publicly offering their dirty laundry is childish and demanding apologies and giving threats is juvenile and petty - they should just deal with it in-house. I think anyone including KO would eventually relent but they are being butt hurt about it so he is grumbling about the conflict - just settle it and move on - fix the damn code.
But you could also make the argument that the rules, implementation and enforcement of certain CoCs, such as in the case of the Linux kernel's CoC here, isn't as fair as it could be. If you did I wouldn't disagree with you.
But the issue here isn't whether Kent or anyone else agrees with the CoC rules, it's Kent's seeming inability to follow any except those he wants to.
To paraphrase someone wittier than I: We're trying to run a civilization here.
Comment
-
-
Originally posted by TheMightyBuzzard View PostI love people who jump into "Free as in speech" projects and immediately try to put their boots on the neck of speech. It's freaking hilarious, especially when they act like the morally superior ones. Tone troll to someone who doesn't know better, noob.
"Free as in speech" is the hardest community project of them all, without the will to co-operate it simply dies.
Comment
-
-
Originally posted by fotomar View Post
There is nothing wrong with hating the odious
Comment
-
-
Originally posted by logical View Post
So utterly self-assured in your hate are you? The classic justification of hate throughout history. How original. Remember that when the time comes that you're the object of a similar hate instead of the giver.
And you obviously didn’t look up the words you didn’t understand
Comment
-
Comment