Remember the old days before /dev was its own virtual filesystem?

Add clarinet reeds to that. That feeling of wood against teeth… great, now I’ll have shivers down my spine all day from thinking about it.

They’re pricy but not beyond the pale for an obscure theme and very overproduced components.

A lot of licensed board games are kinda shit but I’ll hold out a bit of hope.

Yeah that’s true of Google as well I believe. I think Archive is more careful, but I’m sure some books get damaged in the process there as well.

Digitized for private consumption.

Nobody cares when Google did this or when archive.org does this, because they’re sharing the results with the world. (Idiotic shortsighted lawsuits from the authors guild notwithstanding)

That sounds right.

I’m also mostly familiar with the business lines: Dell Latitude and slightly less with HP ProBook.

Given the context that we were talking about laptop chargers rather than generic power bricks, I think it’s fair to consider standard laptop power supplies. (HP has the same connectors even though their protocol is different, and I’m not familiar with other brands but I expect they are much the same).

Unfortunately, barrel plugs tell you zilch about the power supply they’re connected to. They’re a dumb connector with no data capability whatsoever, and I’ve seen the same size of plug on power supplies with output anywhere from 3V to 24V.

That’s definitely not true: Dell laptop chargers and desktop power supplies do communicate what wattage they are able to supply.

Are you saying his mother is stupid?

Also good luck with firmware updates, since most of them are extremely inconvenient to install with Linux, and also few vendors actually update their firmware any more than they need to.

Yup.

Although I’d expand texting to “messenger apps” specifically Signal for me.

Fuck SMS.

If it helps to explain it, Red Hat is owned by IBM.

As someone who uses Windows for work and Linux for pleasure: one of the cons of Linux is the lack of integrated ubiquitous file sharing via SMB and UNC paths. Being able to “cd \\server\c$” and expect that to work with 99% of programs made in the last two decades, is pretty great.

“Hardcode a few pre-selected paths and their credentials in /etc/fstab” just doesn’t cut it. Neither does autofs.

You could have done that, but here we are.

Print it out and scan it. Use a barcode reader. Use another mobile. Upload it to a barcode decoder website.

What exactly is “improper use”?

Odds are neither and it’s a “plausibly deniable” attack.

You know what would probably REALLY actually help?!

Requiring the phone companies to authenticate the incoming calls. They know perfectly well which numbers should be coming in from where.

Can it not?

It would be impossible to distinguish the malware from the apps intended function