Arguably, the homeowner may not want to give it up -- the debris is likely to be worth way more to a collector than the damage it caused, especially since there's video of the crash.

Of course, then the question of "who owns it?" comes up -- the ISS *clearly* discarded it, and by chance it ended up in the homeowner's possession.

Typically, meteorites belong to the land owner where they fall, and this isn't debris from a crash like we had with Columbia -- it's literally trash from space.

So, maybe the lawyers will be arguing about it for a while, or maybe the homeowner will just give it to NASA without any drama -- I know that the previous article says that NASA now has it, but that doesn't mean they get to keep it. Or maybe NASA will analyze it and then return it without any drama.

Either way, I imagine that the homeowner will file a claim with their own insurance, who will then file a claim with NASA or Japan (or both?) and if they recover the money, the homeowner will get their deductable back.

To answer some other parts of this that I forgot in my other comment, I've never used Devuan, but it's described as :

... so if you're looking to keep things simple, keeping systemd out sounds like a big step in that direction, so choosing Devuan over Debian should be a big step in that direction.

But if the system doesn't have systemd, how can it possibly "patch a version of libsystemd into sshd"? Is systemd in there after all somehow anyways?

If you want to compile OpenSSH from scratch who cares if a specific distribution gives you the option? You're just going to not install their package or rip it out, and install your own.

Compiling such things isn't hard -- it's typically some variation of "wget tarball, extract tarball, cd into directory created, ./configure ; make ; make test ; make install" though OpenSSH might need a bit more configuration tweaking than that to work with whatever you're trying to slap it into -- or that might work as-is.

It's fine that you want to do this with OpenSSH, but you're trying to close the barn door after the horses have escaped. Sure, the very latest xz got backdoored, and a given OpenSSH may use it even though it doesn't *need* to use it, and so on, but this is just the very tip of the iceberg. All eyes are on xz now, but what about the other hundred or so libraries your system may have? Running ldd on my /usr/sbin/sshd finds 28 libraries linked, and while some of these would not be there after a rebuild with all the options turned off, there would still be more than a few left -- better rebuild them net.

And OpenSSH isn't the only thing you've got to worry about.

Ultimately, as a practical matter, most people are going to have to trust somebody else to build their system for them -- one person can do it on their own (and there are distributions aimed at trying to help with the process at least somewhat), but it quickly turns into a huge job just building all your own things to your own specifications, and then you're personally on the hook for all updates. Only if it's a super paired-down system (maybe in a container?) does it become practical for most people to do this all themselves. And even then they're still trusting that the code they're running is secure -- and the xz issue make it clear how hard people can try to obfuscate their backdoors.

I understand that you are not one of these people, but there are *plenty* of people who like looking at these bumpy, lumpy men. Even the ones who aren't "pretty boys".

Ultimately, men aren't usually described as "beautiful" because the word is at least somewhat gendered and tied to feminine standards for beauty. But there are plenty of "gorgeous" guys out there too, even if the traditional standards for attractiveness/beauty are different for men and women.

Indeed.

And so this is definitely a *great* lead for the police to follow up on -- show up on the street and start looking around -- but it's nowhere near enough to pick a specific house and knock its door down, not by itself. And the police should absolutely already know this.

But here we are.

Google "won" (or dominated might be better?) the browser wars because they had the best browser. (Well, at least at first, and for a long time. It's not clear if this is still the case, however.)

As far as attitudes go, Google controls Android like Microsoft controls Windows, so ... does Android complain when you install Firefox?

Yeah, it doesn't seem to add up.

If they just lost instrumentation for a few seconds, the plane should have just kept flying as it did before, where the passengers probably wouldn't even notice.

If the lost instrumentation caused the autopilot to move some control surface to the max improperly for a few seconds, I'd expect the resulting movement to not be *that* violent -- these planes are not really nimble, though if it lasted more than a few seconds the accumulated tilt could certainly cause people to fall.

And if the autopilot or something else failed and caused the control surfaces to move unexpectedly -- again, I'd not expect that to be that violent, but given enough time people are going to fall (like if the plane is now banking at a 30 degree angle.)

Whatever happened, it sounds like it's a damn good thing it happened at altitude rather than at takeoff or landing

The space industry is filthy and needs to sort its act out.

There are only three other ways to get rid of something that is currently at the ISS: bring it back to Earth, send it into deep space or send it into the Sun.

All three of these would require considerable expenditures of fuel (with the corresponding pollution) and considerable cost -- and it already cost a *lot* to get that fuel up to the ISS (around $40,000 per pound) in the first place.

Bringing it back with a trip back down from the ISS would still require additional fuel, but a lot less additional fuel than the other two methods. But it comes with its own risks -- for example, the cargo could cause problems with the trip back, especially if it can't be properly secured, and once it's down it's just ... trash. Or something to be recycled, if you're luck.y

But just throwing it out the airlock? That's relatively cheap and easy.

People burn things like this on Earth all the time. It's not good, but it happens regularly. Letting it burn up in the atmosphere falling from orbit isn't going to be that different.

As long as we are at the mercy of the rocket equation -- and there is no end in sight -- it's going to make the most sense to keep doing this.

Apparently, a part of this case is that the two parties had regularly executed contracts between themselves that were signed in exactly the same way -- with an emoji.

So never mind what other people do -- *these two people* regularly did contracts like this.

Can you even copyright a concept?

I mean, this sounds more like they think they have a patent, but a patent needs to be filed and doesn't involve the DMCA at all.

And their lawyers must have told them this already, but they went ahead with it anyway?

Nintendo definitely has heard of it by now.

They just don't care.

Of course. For example, each filesystem root directory on my system has an inode of 2 on the ext4 filesystems, and 34 on the zfs mountpoints. (I thought it was 1, but maybe that's me thinking of something outside of Linux? For Linux, after looking it up, ext2/3/4 use inode 1 to store bad block data. Interesting.)

But if you combine "device" and "inode", that's always been a unique identifier for each file, at least on "traditional" filesystems, and a lot of utilities do rely on this.

For example, changing this would break utilities like "du" and "tar" in how they handle hard links.

I'm having a hard time thinking how this would be a problem for synthetic filesystem, however.

I haven't looked at btrfs much, but I'd expect it to behave like other filesystems in that regard. I can confirm that zfs does.

Ehh, maybe.

POTS lines go from 40v to 54v when on-hook, and 5v to 20v when off hook. 48v is nominal, but there's a lot of tolerance there too.

And when the phone is actually ringing they'll throw an A/C voltage in there up to 110 volts. That will definitely shock you.

I find it kind of hard to believe that a pharmacist would break the law on that, even a rural one -- I mean, the government will take their license over stuff like that with a quickness.

I am also in the USA and this process is a hassle.

Also, living in Austin, TX we're now entering Cedar fever season (it's really "juniper but I digress), and the amount of pseudoephedrine that they'll let you buy is insufficient for some who really suffer from this, and if one person is buying for a whole family it's pretty much impossible to get enough.

It's bad enough that some people have to plan months ahead -- they'll start "hoarding" (not that there's any shortage) pseudoephedrine months in advance so they have enough when cedar fever arrives.