Yeah, and if you're going to use one vehicle for both, that makes sense. Personally I wouldn't use my personal vehicle for work like that, because if it gets wrecked somehow, my insurance won't cover it, and I'd be out of a car until I fight the company's insurance enough to get something out of them. But that might be a US thing.
Maybe, but the same "work pickups" you see everywhere also aren't towing anything.
But the Mercedes-Benz Sprinter Van has a towing capacity of 5000-7500 pounds, or 2.5-3.75 tons, depending on configuration. That's the same range as most medium pickups.
Pickup trucks are fine. It's the huge ones with giant cabs and useless beds that are just a fashion accessory.
"But muh work tools", yeah just get a sprinter van like normal people. You can fit more, and you can close and lock it so your shit doesn't get stolen out of the bed.
It's also not technology. It'd be nice if one of the "technology" communities actually focused on technology and scientific development, not business news or whatever Elon Musk is doing today.
That actually sounds pretty good to me. If the rear seats go down so I can put bigger stuff in the back, that's a huge advantage over the weird trunk angles you have to work with in a sedan. I don't need to tow anything, but a slightly higher ride is useful when I'm going out in the woods and need to clear rocks in the middle of the unmaintained road.
Does Ctrl+Alt+Backspace not kill X any more (assuming you're using X)?
Does Ctrl+Alt+Delete reboot the system from a graphical desktop? Or is that only from the virtual consoles?
I wonder if locking the session would have stopped it as well. I doubt the Alt+SysRq combos would have been useful since other random input was happening at the same time (unless the next keystroke happened to be an I, U, or B).
Partitioning doesn't affect backups. Any modern system supports both full images and file-level backups, so even if you take a whole disk image, you can just restore /home if that's what you want.
I would just use whatever filesystem is the default for your distro. For the root partition, usually that's ext4. That's a perfectly good default.
One internal study cited 13.5% of teen girls saying Instagram makes thoughts of suicide worse and 17% of teen girls saying it makes eating disorders worse.
Not always. I've seen Linux systems keep running, and open programs work, until they need something from disk, and then either they throw an error or crash.
Storage media doesn't make a difference here. You can partition a spinning drive, an SSD, NVRAM, phase change storage, hell even magnetic core if you have enough of it.
It also depends on how you did the partitioning. A full partitioning program like gparted will intelligently move and resize partitions. But even if you blindly rewrote a partition table, if you did something like take a 100gb partition, changed it to 50gb, and added a 50gb partition after it, as long as the filesystem has only used that first 50gb, nothing bad will happen. A partition table just says "partition starts here, ends here".
Just look at the output of fdisk:
Disk /dev/sda: 100 GiB, 107374182400 bytes, 209715200 sectors
Disk model: Virtual disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xaf179753
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 192944127 192942080 92G 83 Linux
/dev/sda2 192944128 209715199 16771072 8G 5 Extended
/dev/sda5 192946176 209715199 16769024 8G 82 Linux swap / Solaris
It can easily see you're in a VM. For example, the OVMF UEFI firmware is a dead giveaway. Nobody runs that on physical hardware.