This is a big nothingburger because it doesn’t have a cute name, a marketing campaign, or a silly logo. /s
Living 20 minutes into the future. Eccentric weirdo. Virtual Adept. Time traveler. Thelemite. Technomage. Hacker on main. APT 3319. Not human. 30% software and implants. H+ - 0.4 on the Berram-7 scale. Furry adjacent. Pan/poly. Burnout.
I try to post as sincerely as possible.
This is a big nothingburger because it doesn’t have a cute name, a marketing campaign, or a silly logo. /s
Yinz shut your boxen down?
I’m not seeing a problem here.
It’s not that. It’s not getting complacent by eliding the semantics of what you’re doing. It’s being consciously aware that you’re doing something that could possibly fuck stuff up.
I don’t, because stuff like that is a little too touchy to wrap in a cute shell alias. If I’m going to update a box, I’m going to update a box. If I’m going to reboot a machine, I want to be reminded that I’m going to reboot a machine (which in turn is a reminder that there are other people using stuff there and not to fuck their days up without at least a little warning).
Are they going to unfuck the layer management UI?
They remember what happened when they migrated Hotmail to Microsoft Exchange.
That’s pretty well answered here: http://vger.kernel.org/lkml/#s15-3
Ew.
Huge pain in the ass to set up, but from the user’s end of things it was pretty easy to do.
Some years ago, I had a client with a really fucked up set of requirements:
This was during the days when booting into a LUKS encrypted Gentoo install involved copy-and-pasting a shell script out of the Gentoo wiki and adding it to the initrd. I want to say late 2006 or early 2007.
I remember creating a /boot partition, a tiny little LUKS partition (512 megs, at most) after it, and the rest of the drive was the LUKS encrypted root partition. The encrypted root partition had a randomly generated keyfile as its unlocker; it was symmetrically encrypted using gnupg and a passphrase before being stored in the tiny partition. The tiny partition had a passphrase to unlock it. gnupg was in the initrd. I think the workflow went something like this:
I don’t miss those days.
Syncthing could do it.
It would probably be more reliable to partition and format the new drive manually and use rsync
to copy everything over. Updating /etc/fstab with the new UUIDs isn’t a big deal (though you can also manually specify the partition UUIDs at time of format - mkfs.btrfs --uuid ...
) (you didn’t say what file system your /boot partition was using, so I don’t want to guess).
No, that makes perfect sense. Thank you for explaining.
I like hearing about other people’s environments, because it gives perspective.
I was starting college (comp.sci, natch) and a hard req for the program was “Your own personal computer, with an Ethernet card and an OS that had a TCP/IP stack for remotely accessing classwork.” I didn’t have a great deal of money (most of it was tied up in tuition and housing) and ethernet cards were expensive (I think I paid $140us for it at the time). I couldn’t afford Windows and didn’t have a warez hookup for '95. A BBS I used to call had Slackware disk images for download.
The rest, as they say, is history.
Just out of curiosity, how often do you have to run pip install
?
Now if they could just help defuckulate the Pypi search problem.
It’s written in Rust.
All jokes about the Rust Evangelism Strike Force aside, various parts of the industry are finally starting to think that “If it’s written in Rust, we have less to worry about with respect to that thing, so we won’t torture the devs and force them to sneak it in the side door anyway.”
It’s a thing that I’ve been seeing at work for the last few years.
Chromebooks? Built like tanks?
Maybe if you folded origami tanks and spritzed them with water. They’re cheap, they’re cheaply made, and they’re made to be e-waste.
“Gentlebeings?”