Posts by Bronek Kozicki 2863 publicly visible posts • joined 6 Sep 2007
"none of them are on Linux"
Not a Tim Cook fan, but there is MacOS and it can be made into a pretty solid office work environment. With `brew.sh` it does most of the things you can do on Linux. For my own home machines I do use Linux, and I do dislike swapping to different keybindings when I switch to the work-supplied Mac, but at least it's not Windows ! I can do most things that I need on it, and it is not actively trying to hack my files - that counts for something.
.... and for a good reason. Linux has a much smaller, and better designed, system API that it needs to support indefinitely. On the other hand, the necessity to drag Windows API *and* native (kernel) API to every new release is a severe drag on Windows development speed.
Yes exactly - original data is stored fine. It is only the tiny window while it is still being written (to memory, not to disk - it is not IO bound) when, if read, it will appear there are all zeroes. IF there is anyone reading the data at this *very* specific moment. And that's a big IF, which is why this bug actually was in ZFS for a very long time. Some started looking back at Solaris at this point - it might have been "forever", or as long as ZFS supported hole reporting.
non-standard screws; replacing battery requires actual total disassembly (as opposed "you need to remove some difficult parts first") or battery is on strong glue; replacing ports is near impossible.
Microsoft Surface Duo got a score of 2, Motorola razr 2020 got 1 ; these things are near impossible to disassemble. Have a look at https://www.ifixit.com/smartphone-repairability :)
Actually it's a good practice to have a non-root user in the wheel (i.e. sudoers) group, to fall back to when some outage prevents connections to kerberos domain etc. Alternatively you could use root of course, but logging as root is not best practice because the potential for fatal mistake is too big.
... what will that bomber do when a bunch of critical processes get evicted due to too much disk space taken up by logs. And the logs immediately deleted, as the pods are being destroyed. Don't get me wrong, Kubernetes is very useful for lots of different cases, but critical software that can result in people dying when gone wrong is probably not one of them.
It probably already is.
Not yet. I quite like 20.04 server edition, but right after installation I run a small script which starts like so:
apt-get purge -y fwupd packagekit dconf-service dconf-gsettings-backend bolt unattended-upgrades open-iscsi multipath-tools sg3-utils tpm-udev glib-networking glib-networking-common glib-networking-services snapd landscape-common
apt-get install -y zsh bc kpartx zip unzip wget curl tmux htop vim
apt-get autoremove --purge -y
The machines work just fine without snapd. It's a good luck that I have no desire to use LXD because then I would have to install it with snap.
C++ has threads since version C++11 . Rather than create threads ad-hoc, the more efficient way is to manage a thread pool, fixed to the number of available cores. The problem with efficiency remains because of synchronization overhead, see also Amdahl's law (not to mention whole new category of bugs). Although of course there are better alternatives to explicit synchronization, e.g. message passing (for C++ example see seastar library - it looks ugly, but is also very efficient). Message passing is one of the reasons to try Go because channels are quite a good abstraction.
The smart thing would be for UK to "support" this. When US corporations (esp. Silicon Valley) wake up to the fact that everyone is considering their tech a liability rather than asset, lure them to this side of the pond with more liberal regulation, and let US slide to Amish level of tech.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
