▲ 48 ▼ Linux 7.3 Released With Faster I/O Performance, AMD Zen 6 Preparations & More (www.phoronix.com) submitted 3 weeks ago by cm0002@infosec.pub to c/linux@programming.dev 8 comments fedilink hide all child comments
[+] FiniteBanjo@feddit.online -9 points 3 weeks ago (7 children) We need to fork the kernel to purge the sloppers from the project. permalink fedilink source hideshow 7 child comments replies: [–] Ptsf@lemmy.world 18 points 3 weeks ago (2 children) permalink fedilink source parent hideshow 2 child comments replies: [+] FiniteBanjo@feddit.online -10 points 3 weeks ago (1 child) Yeah but I'm going to keep saying it until somebody actually does it, that way somebody has the opportunity to fill me in on the development. permalink fedilink source parent hideshow 1 child comment replies: [–] Epp@lemmus.org -2 points 3 weeks ago I'm still waiting on the fork where they don't use electricity, because anything made with electricity is slop. permalink fedilink source parent [–] The_Decryptor@aussie.zone 5 points 3 weeks ago (3 children) Unfortunately, at this point it's effectively impossible to fork the kernel, there's enough churn that any fork will very quickly go out of sync, and also the sheer amount of commercial backing Linux has won't move over to a community oriented fork. Any actual successful fork you'd see, is e.g. Google forking Android off entirely and stop contributing back upstream. permalink fedilink source parent hideshow 3 child comments replies: [–] FiniteBanjo@feddit.online 4 points 3 weeks ago (2 children) There are a lot of Kernel Forks, and some Linux have instructions on installing them such as CachyOS. What we're missing is an Anti-AI Kernal, afaik. permalink fedilink source parent hideshow 2 child comments replies: [–] The_Decryptor@aussie.zone 2 points 3 weeks ago (1 child) I dont know if I'd call them forks, they're more like unmerged branches. Like the bulds with different schedulers, the only thing different about them is they include an extra module that's not included by upstream, everything else is a 1:1 match for upstream, and follows closely. I'd personally say the real-time kernel would come close to it, but even that was still roughly tracking upstream, and was merged in the end. permalink fedilink source parent hideshow 1 child comment replies: [–] FiniteBanjo@feddit.online 0 points 3 weeks ago* I think the point is that they have different maintainers. Of course removing and preventing slop code and unattributed code is essential as well, but that's secondary. permalink fedilink source parent
[–] Ptsf@lemmy.world 18 points 3 weeks ago (2 children) permalink fedilink source parent hideshow 2 child comments replies: [+] FiniteBanjo@feddit.online -10 points 3 weeks ago (1 child) Yeah but I'm going to keep saying it until somebody actually does it, that way somebody has the opportunity to fill me in on the development. permalink fedilink source parent hideshow 1 child comment replies: [–] Epp@lemmus.org -2 points 3 weeks ago I'm still waiting on the fork where they don't use electricity, because anything made with electricity is slop. permalink fedilink source parent
[+] FiniteBanjo@feddit.online -10 points 3 weeks ago (1 child) Yeah but I'm going to keep saying it until somebody actually does it, that way somebody has the opportunity to fill me in on the development. permalink fedilink source parent hideshow 1 child comment replies: [–] Epp@lemmus.org -2 points 3 weeks ago I'm still waiting on the fork where they don't use electricity, because anything made with electricity is slop. permalink fedilink source parent
[–] Epp@lemmus.org -2 points 3 weeks ago I'm still waiting on the fork where they don't use electricity, because anything made with electricity is slop. permalink fedilink source parent
[–] The_Decryptor@aussie.zone 5 points 3 weeks ago (3 children) Unfortunately, at this point it's effectively impossible to fork the kernel, there's enough churn that any fork will very quickly go out of sync, and also the sheer amount of commercial backing Linux has won't move over to a community oriented fork. Any actual successful fork you'd see, is e.g. Google forking Android off entirely and stop contributing back upstream. permalink fedilink source parent hideshow 3 child comments replies: [–] FiniteBanjo@feddit.online 4 points 3 weeks ago (2 children) There are a lot of Kernel Forks, and some Linux have instructions on installing them such as CachyOS. What we're missing is an Anti-AI Kernal, afaik. permalink fedilink source parent hideshow 2 child comments replies: [–] The_Decryptor@aussie.zone 2 points 3 weeks ago (1 child) I dont know if I'd call them forks, they're more like unmerged branches. Like the bulds with different schedulers, the only thing different about them is they include an extra module that's not included by upstream, everything else is a 1:1 match for upstream, and follows closely. I'd personally say the real-time kernel would come close to it, but even that was still roughly tracking upstream, and was merged in the end. permalink fedilink source parent hideshow 1 child comment replies: [–] FiniteBanjo@feddit.online 0 points 3 weeks ago* I think the point is that they have different maintainers. Of course removing and preventing slop code and unattributed code is essential as well, but that's secondary. permalink fedilink source parent
[–] FiniteBanjo@feddit.online 4 points 3 weeks ago (2 children) There are a lot of Kernel Forks, and some Linux have instructions on installing them such as CachyOS. What we're missing is an Anti-AI Kernal, afaik. permalink fedilink source parent hideshow 2 child comments replies: [–] The_Decryptor@aussie.zone 2 points 3 weeks ago (1 child) I dont know if I'd call them forks, they're more like unmerged branches. Like the bulds with different schedulers, the only thing different about them is they include an extra module that's not included by upstream, everything else is a 1:1 match for upstream, and follows closely. I'd personally say the real-time kernel would come close to it, but even that was still roughly tracking upstream, and was merged in the end. permalink fedilink source parent hideshow 1 child comment replies: [–] FiniteBanjo@feddit.online 0 points 3 weeks ago* I think the point is that they have different maintainers. Of course removing and preventing slop code and unattributed code is essential as well, but that's secondary. permalink fedilink source parent
[–] The_Decryptor@aussie.zone 2 points 3 weeks ago (1 child) I dont know if I'd call them forks, they're more like unmerged branches. Like the bulds with different schedulers, the only thing different about them is they include an extra module that's not included by upstream, everything else is a 1:1 match for upstream, and follows closely. I'd personally say the real-time kernel would come close to it, but even that was still roughly tracking upstream, and was merged in the end. permalink fedilink source parent hideshow 1 child comment replies: [–] FiniteBanjo@feddit.online 0 points 3 weeks ago* I think the point is that they have different maintainers. Of course removing and preventing slop code and unattributed code is essential as well, but that's secondary. permalink fedilink source parent
[–] FiniteBanjo@feddit.online 0 points 3 weeks ago* I think the point is that they have different maintainers. Of course removing and preventing slop code and unattributed code is essential as well, but that's secondary. permalink fedilink source parent
all 8 comments