You still need to file every year. An advisor at least here in Germany can do both countries, but you pay a premium for that.
You still need to file every year. An advisor at least here in Germany can do both countries, but you pay a premium for that.
Not a sysadmin, but a programmer. My work machines have been:
Probably going to keep using NixOS. This is a very cool OS.
Steely Dan. The worst part would be I won’t stop talking about the drum solo in Aja.
That thing which makes Meta and Apple so scared they do not release their new products in AI anymore in the EU to pressure us to loosen up the laws. That has already been costly to these companies.
That prevents Paypal from doing this change in the EU.
The law that has been awesome so far.
Yeah, the perks of the Android ecosystem. There’s also a version for Android TV such as NVIDIA Shield. Again just works and filters out ads and sponsor segments.
I’ve been using this one for years, which filters out ads and sponsor segments:
Only for Android though. If you use iOS, switch to Android and you’ll also get a really Firefox browser with ublock origin that blocks all the ads compared to that 30something% what every iOS browser does.
I run invidious at home on my proxmox server. The server is available everywhere with tailscale, so I can use it even when travelling. If Google ever blocks this, nobody at home can watch youtube anymore…
His job is to not get the maintainers to agree, but his job definitely is to bark a bit if somebody behaves like Ted.
It might even be Rust is not meant for Linux kernel and it will never happen. Or it happens in the driver layers, but stays out from the core. We do not know yet. The concern Ted is raising is definitely valid: if the C APIs change, people who work daily in the C code cannot spent cycles fixing the Rust APIs. These people have their day jobs which pays them to maintain these subsystems, and it is at least not yet clear will these employers fund rewriting anything in Rust. There are tens of filesystems in Linux, with lifetimes passing around that are not documented and might not work in Rust.
Note: I’m a Rust dev for the past 10 years, and I follow this discussion with high interest.
Yeah. Isn’t it funny that the most popular file system in the world has such a codebase, and it is not even well documented how it works!
I have my reasons to choose XFS or bcachefs with my machines.
Yes and no. Linus can yell to people and he does, he can force his say as he has been recently doing by expecting sched_ext to land in 6.12. BUT. Linux is a bazaar, it’s so big and there are so many different factions forcing them to do anything is going to take a long time. Lots of different teams are working on Linux, with their own priorities.
The borrow checker is exactly what the kernel needs.
Ted is the maintainer of ext4 and there are not many people in the world who understand this code.
For Rust to succeed, it has to get the subsystem maintainers to agree. It is going to be many years of petting very angry bobcats…
And that is not even the worst I’ve heard, makes you a bit numb if you follow LKML.
Me neither, but the risk is there and well documented.
The point was, ZFS is not great as your normal laptop/workstation filesystem. It kind of requires a certain setup, can be slow in certain kinds of workflows, expects disks of same size and is never available immediately for the latest kernel version. Nowadays you actually can add more disks to a pool, but for a very long time you needed to build a new one. Adding a larger disk to a pool will still not resize it, untill all the disks are replaced.
It shines with steady and stable raid arrays, which are designed to a certain size and never touched after they are built. I would never use it in my workstation, and this is the point where bcachefs gets interesting.
At the same time Windows is going down the drain, so if you compare removed to that it definitely has an edge. And that 8GB Air is not that expensive either… And fanboy can tell you it can swap to SSD so fast blah blah…
But if you have the knowledge to use Linux, there are less and less reasons to go even near removed computers…
But scrub is not fsck. It just goes through the checksums and corrects if needed. That’s why you need ECC ram so the checksums are always correct. If you get any other issues with the fs, like a power off when syncing a raidz2, there is a chance of an error that scrub cannot fix. Fsck does many other things to fix a filesystem…
So basically a typical zfs installation is with UPS, and I would avoid using it on my laptop just because it kind of needs ECC ram and you should always unmount it cleanly.
This is the spot where bcachefs comes into place. It will implement whatever we love about zfs, but also be kind of feasible for mobile devices. And its fsck is pretty good already, it even gets online checks in 6.11.
Don’t get me wrong, my NAS has and will have zfs because it just works and I don’t usually need to touch it. The NAS sits next to UPS…
It is one of the most addictive games I’ve played. The good thing is that it is cheap and doesn’t have any microtransactions. And a lot of fun.
It is only in TLS where you have to disable compression, not in HTTP.
https://security.stackexchange.com/questions/19911/crime-how-to-beat-the-beast-successor/19914#19914
Could you explain how a CRIME attack can be done to a disk?
Depends. For example in Finland the filing is done for you every year by the tax authorities and tax is deducted every month from your salary. Once a year you get either money back or need to pay more if your work situation changes during the year. You can also correct them by saying “hey I paid this bus card” etc. and get money back.
In Germany it works about the same, except they charge you quite a lot more every month. Here you do not have to file, but if you do you usually get a lot of money back. Filing is more complex than in Finland, so you might want to have a tax advisor to do it for you.