Giver of skulls
If you use the .local syntax, and the device name stays the same, I think the domain name based fingerprint should prevent the “do you trust this fingerprint” problem.
If you want to avoid the question all together, you could set up an SSH certificate authority (quick guide here, less dense guides are available on the internet). By signing the servers’ host keys, you can prevent the trust on first use prompt entirely, even for servers you may not have logged into before.
mDNS solves this. It may actually work out of the box. Try ssh’ing into your-device-name.local. If that fails, check your devices’ names and if they have Avahi/Bonjour/mDNS enabled.
Something like Tailscale will set up a VPN with hostnames and IP addresses for you (and you can host your own entry server if you don’t want to use the cloud stuff). That’ll work across networks. It’ll also add overhead and it’s probably overkill for your use case, though.
I take advantage of the free disk space savings and don’t worry about disk space much. I’ll clear out my download directory and maybe some caches when my disk usage grows beyond 80% (as reported in GUI tools). Running duperemove across my drive every now and then also tends to help a lot without deleting anything.
If I do run out of space, there are a few interactive terminal tools that’ll point out the biggest files so I can delete them and save some space in a pinch. I practice, I just don’t really think about it much.
df is the standard command line tool to see how much of your disk space is free.
The problems happen in GUI tools too. Most of the time, they work out in your favour (you think you only have 10GB left but you can put 15GB away) but after a lot of deletes you may “lose” some space until you do a rebalance even through you’d think looking at the stats that you have plenty of space.
Another issue is that file managers showing you a file’s size often don’t know about compression. You can store a large text file with standard compression on a disk and have it be reported as 100MB while it only takes up a megabyte of space. You can end up deleting a whole bunch of “hundred megabyte files” and save basically no disk space. Other file types, like images and video, often do represent the real size as they’re already compressed, making some 100MB files larger than others. If you don’t enable compression, you won’t have this problem, or course.
GUI tools also often don’t know about CoW. If you copy a file on BTRFS, the copy action should be instant and take up maybe a couple hundred bytes for the new metadata. To your file manager it looks like you have two 3GB movie files, but in practice they’re just names pointing to the same directory. You can get petabytes of used disk space this way by just making more and more copies, even though your actual disk space barely grows. This also means deleting files may not clear up as much disk space as you’d like.
Actually, I want to backup my system as I’m new to Linux, there is that I will break the system.
Then you will need to also include most if not all system packages. You can exclude your home folder if you want.
Note that there are big differences between how Timeshift works on btrfs or on anything else. BTRFS snapshots allow something called “copy on write”, basically allowing the system to make a “copy” of a file that references the same data as another, and from that moment only tracking changes. That way, you can instantly create snapshots of entire drives, and keep dozens of snapshots without risking running out of storage. I’ve got my system set up to make a snapshot every time software updates are installed and the biggest snapshot I’ve seen was about 45GB (it was a snapshot from before upgrading Ubuntu 22.04 to 24.04 and included a few virtual machine and ML models). My daily apt upgrades generate snapshots of about 100MB but I can still roll back the moment I need to. I can even select an older snapshot in my Grub boot menu in case my bootloader dies.
The rsync based approach used on ext4 and other filesystems isn’t that flexible. You’ll get snapshots, but each file needs to be processed individually. This means you need to make sure to close down programs before making snapshots or you’ll risk corruption. The disk space savings are also more limited; filesystems like ext4 will still have almost 0 overhead for files that haven’t been changed between two snapshots, but if you change a single bit in the middle of a 100MB file, chances are rsync will create a fresh copy (whereas btrfs would only store an extra extent, usually 4KB, which is the smallest unit the filesystem will let you control).
Restoring snapshots using rsync requires copying/linking files back, and can’t be done transparently. This means you can’t boot a previous version of the system like on btrfs, you’ll need to boot into recovery mode, restore the snapshot manually, and reboot.
I’m afraid about the compatibility of BTRFS ( not like system drive need any compatibility ). Does it have a good community support as ext4?
Support is mature enough that it’ll Just Work in most cases. With some edge cases, like disk usage statistics not being accurate, because tools don’t realise files can be partially deduplicated or compressed, let alone taking subvolume quotas into account. In most cases, the more fancy features you enable, the more older software will act a bit funny.
I believe Fedora has picked it as the default for a few years now. Haven’t checked, though.
?
Tools like df and other file system monitors only support very rudimentary disk usage statistics, even when certain ext4 features are involved. There are a bunch of methods in which btrfs can seem full, but still have plenty of space, or it can seem like there are gigabytes of space left but the volume is so unbalanced that that space isn’t actually usable. There are also about three types of data stores that can technically get full (though your rarely run into that). Usually, you can claim back a chunk of storage after a year or two by rebalancing and defragmenting the file system, especially if you use advanced features like snapshotting. I believe there are rolls to automatically run these operations as well.
These issues seem to come up. Most when you’ve nearly filled the FS to the brim. Keeping 10% free seems to prevent most of them from ever popping up.
There are a few other edge cases as well (like how you should disable compression on swap files and virtual machine images, and how you may want to disable copy on write and snapshots on them as well for performance reasons) but they’re more niche. There are a bunch of really cool features as well (like how you can send a snapshot over the network in the form of only the difference since the version before, making network disk backups tiny). You’re not that likely to run into any of them, but the project website has everything documented if you’re interested.
Doing it in a VM would be excellent! I recommend taking a look at a tool called “btrfs assistant” if it’s available for your distro, it’s a lot easier to navigate than the deep menu of command line flags.
You can convert a running ext4 system into BTRFS and even move back to ext4, but to optimise the file system there are quite a few tricks to run as well. They come down to “remove the ext4 metadata (can’t go back after that), defragment, balance, maybe defragment again” and there are tools out there that make this stuff doable though the GUI, but I wouldn’t necessarily recommend that approach I novices.
The cleanest switch would be to reinstall. Not just because of the steps above, but also to make sure the right subvolumes are set up with the right properties. This too can be done from a (mostly) running system, but it’s an absolute pain in the ass to have to do manually, especially if you’re not an expert in command line stuff.
ext4 works fine if you don’t want to deal with all of this, but you’ll have to keep an eye on things like backup sizes just a bit more often
If you can’t take advantage of Timeshift’s BTRFS support, you’ll probably need to keep an eye on disk space regardless.
All the .deb files are installed across system directories like /usr and /etc. If you only want backups of your files, just exclude everything outside /home and your data drive. This makes it more difficult to recover from a failed upgrade Windows System Restore style (as you exclude the system components from the backups) but hopefully you’ll never need that (or will be willing to reinstall and restore from backup when failure does happen). You may also want to exclude folders like $HOME/.cache and $HOME/.var if they’re present on your system. I think Chrome puts some of its cache in $HOME/.config as well, though I’d back up most .config folders myself.
If your storage is that limited and you’re already familiar with Timeshift, you may want to consider switching to BTRFS. It’s not very friendly when it’s almost full, but compression and deduplication can save a lot of disk space, especially with tools like Timeshift. Other filesystems also offer these features, but Timeshift doesn’t make use of anything but BTRFS as far as I know.
You can probably just swap the SSD if your dock uses a protocol that Windows’ bootloader can understand. Some USB 3.2/Thunderbolt docks just seem to work with Windows, albeit a bit slower because of hubs and such that aren’t always top quality.
Just try it. It either boots or it doesn’t. If it doesn’t, it’s probably a massive pain to get working in the dock (best of luck to you if you’ll still try).
You should also check for updates/update your new SSD’s firmware, probably under Windows. Not a lot of brands make Linux installers and the automatic tools that check compatibility generally aren’t part of the Linux firmware downloads.
Re: file transfer: make sure you have your Bitlocker recovery key, or disable encryption on the Windows partition so you can access it in Linux. Other than that, just copy over the files. Linux can read Windows’ file system just fine. If you load the right drivers, Windows can also read file systems like btrfs or ext4 just fine.
A lot of people are afraid of systemd expanding because systemd handles a lot of stuff, so distros are likely to support it rather than the mishmash of tools they personally prefer. It all started with the System-V/Upstart replacement and now very few distros have the patience to customise and roll out the 90s style service management anymore. Their preferences used to align with the mainstream, but no longer do these days, and that causes friction.
This process pushes people who prefer old tools to fringe distros, and newer software is less likely to work on their setups. They’re still free to use whatever system they like, of course, but the burden for developing and maintaining daemon management scripts is now on their fringe distro or themselves if their distro doesn’t have anything yet. I’d find that pretty annoying too, especially with how convoluted many older system management scripts are and how many moving parts are typically involved. Plus, some stuff like socket activation can’t even be done with some of the older init systems so people have to find alternatives.
I doubt anyone reeling against run0 was ever going to consider it anyway.
sudo had several severe security bugs caused by copying env variables so I’m not surprised run0 isn’t doing much of that. I’ve had to help a whole bunch of people fix the permissions/ownership on their Jo. E directory after running sudo so I can even see the point of jot copying $HOME by default.
I don’t think it’ll replace sudo necessarily, or doas would’ve done that already. It’s still useful as a shorthand for systemd-run and in some locked down system configurations I can see it being useful (i.e. when minimising the amount of SUID binaries). Maybe some elaborate enterprise setups will switch to it for security reasons, especially if they’re already leveraging PolKit heavily.
The nice thing is that it already runs Linux. The less nice thing is that it’s running some ancient Linux 2.6 kernel with Android on top of it.
It should be doable to install Linux in some form or another onto it, but it won’t be easy like installing Linux on a PC.
Corporate stuff is probably already running on unsupported and unpatched Linux distros if they still haven’t migrated to Python 3. I doubt the new version of Fedora removing the binaries will make much of a difference.
Then you should tell that to the several brands that leave their caps sticking forward partially no matter how much you bend them backwards. I don’t care, but there are plenty of brands with much shittier bottle designs than the ones that stay out of your face like they should be designed to.
I think what I saw was the full version of this segment: https://youtu.be/Z9PM14qKhe4 Although, I think it may have been about the 1.5L/2L bottle as well, and this video is about the dangerous bottles that remained after a bunch of them got off the market.
The shots in the video you linked seem rather fake (and kind of artsy, I love old Dutch television sometimes), the video I recall had bottles treated rather normally.
I think the people complaining about this stuff fall into several categories. One of them is depicted well by that GIF. A second group is just upset about environmental regulations existing. There’s probably a third group out there with some kind of hypersensitivity for things touching their face. And maybe a fourth group who hates it when things change even if there are good reasons for it (can relate, was diagnosed as autistic).
I feel bad for the people with hypersensitivities but the rest should just suck it up already. Maybe some bamboo or metal straws can help these folks get used to the new bottles? They’re available online for cheap.
There’s a good reason why many carbonated drinks stopped being sold in glass bottles. When you go over a certain volume, they become bombs. There are videos online or 2L soda bottles falling over and sending shards of glass flying everywhere. I’d rather not have that back.
Glass bottles are also great at starting fires when they’re left outside by trashy people. Looking at how often I still find plastic trash in the woods, I’m not sure if switching to glass would make that much of an improvement.
Plus, you’d still have the same problem with the bottle cap.
Unless you have some kind of knockoff SSD, that ūsung SSD looks like something is corrupted to me. usb 1-10 device descriptor read/64, error -71 might be unrelated.
This could be a problem with RAM defects or overclocking. If your computer is overclocked, try setting it to stock configuration. Also run a memtest to check if your RAM sticks aren’t going bad. I don’t know what might’ve changed between 6.8.9 and 6.8.10 to cause this, but it could just be a coincidence (i.e. the kernel defaulting to a different RAM page that suffers from corruption for whatever reason).
These messages are actually part of the systemd startup sequence, so the kernel has already loaded at this point. This means the problem may not be the kernel, but the initramfs installed/generated for your computer. You can try regenerating your initramfs on Fedora by running dracut --regenerate-all as root. Before you do that, you may also want to double check your /etc/fstab to make sure nothing accidentally added a swap device for some reason.
Restart your ssh server to be sure (probably sudo systemctl restart sshd). No need to reboot your server for this.
I don’t know how reliable this is, but I usually go into htop to check if stuff needs to be restarted. Processes in red have been replaced or removed since starting.
That said, regular server reboots are a good idea to make sure kernel patches are applied. Can’t go wrong with a reboot just in case.
Ah, in that case I would definitely recommend taking a look at Tailscale!