My parents treated my device access something they had to keep a keen eye on. They were good at manually making sure I wasn’t sitting around having my brain rot, but their spying on what I was doing into my teens left me with some trust issues.
They briefly tried to use technological solutions to control my access and monitor me, but all that served was to make me very good at circumventing them. Outsourcing parenting to a computer program doesn’t work, and kids notice when you try.
They’re not trivializing, just noting that the different things you need to discuss for kernel development compared with other work. It is very different in a lot of ways, and does shape your perspective. I also find it interesting.
For the same reason spoken languages often have semantic structures that make a literal translation often cumbersome and incorrect, translating nontrivial code from one language into another without being a near expert in both langauges, as well as being an expert in the project in question, can lead to differences in behaviour varying from “it crashes and takes down the OS with it”, to “it performs worse”.
A rather overly simplistic view of filesystem design.
More complex data structures are harder to optimise for pretty much all operations, but I’d suggest the overwhelmingly most important metric for performance is development time.
Yes, but note that neither the Linux foundation nor OpenZFS are going to put themselves in legal risk on the word of a stack exchange comment, no matter who it’s from. Even if their legal teams all have no issue, Oracle has a reputation for being litigious and the fact that they haven’t resolved the issue once and for all despite the fact they could suggest they’re keeping the possibility of litigation in their back pocket (regardless of if such a case would have merit).
Canonical has said they don’t think there is an issue and put their money where their mouth was, but they are one of very few to do so.
Opengear in Brisbane; development teams often use Linux.
Brand new anything will not show up with amazing performance, because the primary focus is correctness and features secondary.
Premature optimisation could kill a project’s maintainability; wait a few years. Even then, despite Ken’s optimism I’m not certain we’ll see performance beating a good non-cow filesystem; XFS and EXT4 have been eeking out performance for many years.
License incompatibility is one big reason OpenZFS is not in-tree for Linux, there is plenty of public discussion about this online.
I’ll also tac on that when you use cloud storage, what do you think your stuff is stored on at the end of the day? Sure as shit not Bcachefs yet, but it’s more likely than not on some netapp appliance for the same features that Bcachefs is developing.
In addition to the comment on the mentioned better hardware flexibility, I’ve seen really interesting features like defining compression & deduplication in a granular way, even to the point of having a compression algo when you first write data, and then a different more expensive one when your computer is idle.
This is actually a feature that enterprise SAN solutions have had for a while, being able choose your level of redundancy & performance at a file level is extremely useful for minimising downtime and not replicating ephemeral data.
Most filesystem features are not for the average user who has their data replicated in a cloud service; they’re for businesses where this flexibility saves a lot of money.
Depends on the failure mode; If your USB4 cable has enough noise (due to poor cabling, damage, or interference), it may negotiate down to 40Gbps (or even 20Gbps) instead of 80Gbps instead of outright failure, but it might also intermittently crap out if it negotiates a certain speed and then get moved.
If your device requires a speed that can’t be reached, yeah it’ll pretty much always fail on a bad cable.
Regarding 1: if you open up dmesg after it happens and you see an error regarding “No edid read”, your GPU is having a hard time automatically getting the monitor’s edid over display port. My 7800xt has this issue.
If your monitor setup doesn’t change much, you can manually set the edid on a per output basis. Here is a good guide.
Also, regarding 3: you may need to set your amdgpu feature mask in your kernel parameters.
A bunch of tech companies do a lot of their work within Israel; a comprehensive secondary boycott would rule out a lot of technology companies.
Not saying it’s not a worthy effort, just that I doubt arm are worried about themselves specifically.
While I do agree these people exist, most people are some mixture of benefiting from, and being harmed by the status quo. To erode support for a mode of production takes both fighting those who are directly against your class interests, and convincing the majority of people that their class interests align with your actions. Often those who feel the most precarity under the current system are it’s most ardent defenders, simply because their afraid of loosing what little status they have eked out for themselves.
Corbyn was sabotaged both by people who rightly saw him as a threat, and by those who didn’t see the benefit he could bring them.
A mixed system which starts with changing the most socially egregious examples is probably the only politically viable transition; lots of people fear disruption, and it takes time and proving to them that the changes are beneficial.
I’d suggest beginning with something like Corbyn’s Labor had proposed; if a capitalist business is sold or fails, the workers are given first right of refusal and a govt loan is given for them to purchase as a worker cooperative.
If it’s a G502/702, they’ve got a very fucky scroll wheel & middle click; it’s actually a lemon, but since nothing else works with the wireless pads they’re the only options.
Care to elaborate?
deleted by creator
Moving some packages (especially libraries) onto an unstable branch while keeping others back on a stable one. It probably won’t fuck you immediately, but when it does it’ll be a bastard to diagnose because you will have forgotten what you did.