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.
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.
Read the error again. It’s journalctl.
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.
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?