Yes, back in the early 00s. We toyed with making a net-bootable image with it for our computer labs, but it was really not practical. It definitely taught me a ton about systems, though.
Yes, back in the early 00s. We toyed with making a net-bootable image with it for our computer labs, but it was really not practical. It definitely taught me a ton about systems, though.
I admit, I’m not a big fan of putting more functionality into systemd (or just of systemd in general), but that is a well-reasoned argument for having sudo live in the init system.
“No lawful way…”
I just finished saving backups of the games I bought using my (hackable) Switch, and I’m planning on setting it up w/ Yuzu on my Steam Deck.
And no one’s going to stop me from fairly using my stuff.
I read the man page, but I didn’t see the answer to your question in there.
I am assuming that it would only dump the root filesystem in your example. Other mounted filesystems like /home or /media, if they’re separate filesystems, probably aren’t included. You’d have to run a separate dump for each one.
Best option to find out is to try it and see what happens. No better way to learn than by doing.
No official, public explanation. We know why…
Well, I’m in the midwest US, so winter can be a bit harsh for walking or biking (though not this year thus far). Most of the time I drive, I’m dragging kids somewhere. It’s inconvenient to walk with them.
I have been walking and or biking when it’s just me, and I don’t need to haul much. I’ve lost a lot of weight recently, so I can actually bike to work in the summer and not be a sweaty mess when I arrive, so that’s a nice change.
We are taking about moving outside the city to have more space, which means not driving will become less possible for almost everything. Today I have groceries, dentist, and doctor within half a mile, and I’ve walked or biked to those places many times.
Bottom line, most of the time I’m either dragging kids around or I’m in a rush. Driving is very convenient, and is hard to change.
I’ve very seriously considered that. Right now, we could probably go down to one car without issue. We have two reasons why I’d like to maintain a second, though. We have young kids, and we are already starting to run them around to different places at the same time. We’re looking to move soon, and the idea is to move outside of town where we have more room. That would make basically every drive longer, which would increase the likelihood of needing a second vehicle.
Either way, an EV should be fine. Depending on cost, I might stick with a small, used ICE this time, because I don’t need much. But I’m not at that point quite yet, so maybe things will change by the time I’m ready.
I was among those worrying about range until I spent 5 minutes thinking about what I actually do on a daily/weekly/monthly basis.
We’d still have my wife’s ICE van, we both work from home, and 99% of the time my work-related travel is local (within 5 miles). My wife’s van can pull the camper for our camping trips, or for our longer drives.
I have no good reason not to get an EV for my next car.
Read the error again. It’s journalctl.
I’ve had 5 shots of Moderna now, most recently last week. The first one made me feel miserable for a day. I was having chills, and my entire body was sore. I took several naps that day. The others made me sore and a little tired for a day.
All told, not the worst side effects, but certainly more than a sore arm. And still entirely worth the mild inconvenience.
I would call my first reaction nearly “unplayable.” I was having issues working (remotely even, a desk job), and I just wanted to sleep most of the day. But people react differently. Sounds like you had no issues, so good for you.
PowerShell makes that a lot better these days. It’s still not perfect, but a lot better.
It’s not that it’s deleted automatically. If you define deleting as “not being referenced by the file system,” then it’s deleted as soon as it’s unlinked.
Fun story - create a big file, and hold it open in an application. Unlink the file. Then compare the output of du and df for the mount point the file was on. It will differ until the app closes and the inode of the file is finally freed.
I hear your annoyance, and I get it, because the “real” question is “How do I stop this from ever happening again on Windows?”
But the bottom line is, no matter what workaround or registry fix is found, nothing stops MS from making changes and popping this crap up yet again in some other obnoxious and shitty way.
If you run Windows, you have to accept some level of this bullshittery.
Cursory Google searches will give you driver downloads. Dell/HP can give you a pre-bundled package of drivers.
Unless you’ve got some very unique hardware (or very old), it just isn’t that difficult to figure out.
I’m all for using Linux, and I’m considering moving my desktop over from Win 10, but I’ve never had any issues with the install of Windows. If it’s any level of modern hardware, it should mostly work out of the box.
These kinds of rants really trip my BS detector, because it’s just not that complicated. If you can handle Linux but can’t manage to even install Windows, I have a lot of questions.
Interesting. Looks like perhaps your boot loader isn’t properly pointing at your root partition.
I’m assuming you’ve just done the install and never successfully booted, yes? In that case, you can try to re-run the installer, or try rescue mode and try repairing the bootloader.
Are you doing dual-booting, or is this system dedicated to Linux?