Here’s a post explaining how dual booting works.

When you turn on your computer, the bios or bios equavalent goes down its list of devices to try and boot from. It might have usb or cd first and ssd next, so if you put a cd or usb it’ll boot that automatically.

Devices that can be booted have special instructions in the first part of their storage that can be used to operate the hardware.

When the bios finds a device that can be booted it hands the hardware off to that device and breathes a sigh of relief, most of its work is over. That devices work is just beginning though.

If it finds a windows disk, that disks bootloader will load a minimal set of hardware drivers necessary to load the rest of windows and it builds itself up towards having a functional running windows operating system and presents a login screen to the user.

If it finds a Linux disk, the disks bootloader will do the same thing but instead of loading a set of drivers, kernel and configuration that let it start a windows system it will build towards having a running Linux system. Duh.

When you dual boot, the device the bios finds to boot from doesn’t do either of those things, it runs a bootloader that presents you the user with a choice between the two, then hands the task off to one or the other based on your choice.

Setting up dual booting means clearing off space and shrinking the windows partition so you can have a Linux partition, installing Linux to it and then installing a bootloader that gives you the option to use either os.

It’s the same thing.

Email even has its own version of federation and de federation in dkim.

The only difference is that you’re oftentimes not given access to an email address from your internet provider by default anymore so you’re not automatically joined into the system.

People balking at choosing a server are not showing you a bad user experience, they’re showing that they don’t really want to be part of a reddit alternative.

And the broader lemmy/activitypub/whatever needs to figure out if it wants to be like beehaw and hexbear and abandon the shape of reddit or if it wants to duplicate it and try to compete with reddit.

There’s a lot of arguments for one solution or the other based on security or privacy, but let me present a different scenario:

Imagine you’re in a natural disaster. Your home based self hosted server is down because of a general rolling network outage or just irrecoverably destroyed. Your offsite on the other side of the county is in a similar state. Can your cloud hosted backup be accessed at generic, public computer in a shelter or public building?

Bitwarden can. It has specific instructions for doing so as safely as possible.

Again, so much of the discussion around kernel mailing list exchanges excludes the context that what hellwig is talking about is not rust in the kernel at all or even r4l but a split code base.

I dealt with a c/c++ codebase once and it was beyond my meager abilities to handle both those ostensibly similar languages at the same time and I had people who were very knowledgeable in c involved with the project.

So when someone says “I think a split codebase is cancer to the Linux kernel” or “I will oppose this (split codebase) with all my energy” I’m like “yeah, that makes sense.”

I also need to clarify that I don’t think anyone is sabotaging anyone else and my intent in bringing up the simple field sabotage manual was to point out that the behaviors don’t necessarily indicate sabotage but fall into a broad category of behavior that isn’t gonna solve problems or get anywhere which is why it’s included in the manual.

I wasn’t aware it was circulating in social media recently and about fifteen years ago when I got exposed to it the main lessons to draw were not that people doing those things were active saboteurs but that those behaviors can lead to waste of energy and resources and they’re the first thing to avoid interacting with.

My exposure to and understanding of the manual was “here are some things to avoid in your own life” not “here’s how to throw a wrench into their plans!”

It’s surprising to see that statement get brought up in the news considering it’s immediately followed by a parenthetical specifically enumerating a multi language code base as the subject not rust specifically.

Iirc it’s even preceded by something to the effect of “I like rust, it’s good and there’s nothing wrong with projects that use it”.

The news coverage of kernel mailing list stuff is always so needlessly breathless.

The system works

Earthsea is what you want.

If it’s an asus ee, the vents are all on the sides. With a couple of shims underneath it would fit in a bookshelf with a bunch of other books.

As far as uses… nat hole punching for an overlay network is one way I’ve used these devices before.

Debian, lxqt and x11.

If you can get an ssd in there then there’s some zram or something or other that can make it even better.

It’s 孟子 for anyone wondering

Some food for thought:

Absence of information is its own sort of information. You may find it worthwhile in your search for an acceptable compromise to place some kind of value on “looking normal”.

Someone already linked to journalctl, but if you just quickly want to look, the command journalctl and the flag —since will get you going.

Journalctls output can be piped, so if you know what you’re looking for you can grep it easily.