I can use Fish’s history to jog my brain on actions I don’t quite remember. Remembering a sequence of screen menus to click thru is often much more tedious & error-prone. And when you have a commonly repeated process, it’s trivial to script because shell scripts are, well, scripts for that terminal shell.
Also the terminals applications are hella portable. I can use ssh/mosh over the network & have a similar or exact environment as my main PC on a remote box. vi was always a good enough editor.
I think you can already do this in one shortcuts, not sure of any standalone program that does, if definably accidentally bond like Ctrl+d, Ctrl+s to screenshot before
It was already split by a fit Latvian girl of a Yarr-harr, fiddle-dee-dee persuasion, if you catch my drift. I really am afraid of fucking something up, so I’ll try other methods before splitting it further.
Theyd need a ntfs driver to do anything. If you try to do what you are suggesting without one, bad things happen. Unless that part of the partition isn’t ntfs formatted.
Why do you think anyone bothered to write a ntfs driver if you could read and write to ntfs without it? Why do you think windows cant read ext4? What do you think file systems are?
The best way to be happy is to be kind. Seriously, just try it and come to your own conclusion. It works way better than trying to extract satisfaction from life, which actually just creates more dissatisfaction.
Sorry if it’s a noob question, but isn’t a live session something you do with a USB stick without installing? The file is currently on the Mint install I used to torrent it, along with my other daily-driver things.
Seems like your USB drive is formatted with a filesystem that doesn’t support large files like FAT32, if you are able to, try formatting into exFAT in Linux with:
Alright, I’ve used your code, sudo mkfs.exfat -n LABEL /dev/sdb1
but the console returns this
<span style="color:#323232;">exfatprogs version : 1.1.3
</span><span style="color:#323232;">open failed : /dev/sdb1, Device or resource busy
</span><span style="color:#323232;">
</span><span style="color:#323232;">exFAT format fail!
</span>
what’s the problem here? I’ve cleared out all storage on the drive, and made sure that it isn’t opened in the file explorer, and it shouldn’t be reading/writing anything because it’s empty.
You must unmount the drive before formatting. And also know that formatting wipes the drive, so if there is anything on there you want to keep, back it up beforehand
And triple check the device path, you don’t want to unceremoniously unmount and obliterate one of your non-system drives (shouldn’t be able to unmount your system drive)
This may or may not be advice from learned experience
It not only has to be not 'open' in the explorer, but properly unmounted. Tools like mkfs dont do that for you, its just not their job. (and might be unwanted or stop your from making mistakes like accidentally overwriting the wrong drive)
try umount /dev/USBDRIVE
If that still complaints about Device or ressource busy, then something is still using it.
Either try to close things that might be the culprit, reboot and try again or, if installed and you are compfortable, you can check which processes using lsof -D <path where drive is mounted to> (you can get that location using mount | grep <path to usb drive>)
I’ve messed with a decent amount, listed in my post. Most distros weren’t customized the way that I wanted them to be or I didn’t like the looks so I prefer Debian and Arch for simplicity’s sake depending on the use case and going from there.
Manjaro. I had previously already used Antergos and Ubuntu, but after Antergos stopped I needed something like it. So I installed Manjaro in my secondary PC (with old components). I constantly got into trouble with the manual kernel version selection thingy. I was used to kernel updates being part of the normal update process, and suddenly I had to manually pick the new one. I constantly ran into incompatibility issues with older or newer kernels, vague update deadlocks where I couldn’t update things because they depended in each other, and I absolutely hated having to use a separate program for updating the kernel. Now the PC runs Fedora and I’m liking that a lot more so far…
Manjaro ships with a LTS kernel, which is marked “recommended” in the kernel selection tool. By default you don’t have to do anything, don’t ever need to use the kernel selection, and you won’t experience any problems, it works like any other distro.
The issues you described are caused by selecting one of the non-recommended kernel versions. It’s assumed you know what you’re doing if you do that.
Exactly I really don’t get the argument there. Manjaro’s handling of kernel selection is brilliant. Multiple LTS kernels, a recommended one, bleeding hedge and experimental ones. There’s something for everyone and it’s super easy to use.
It’s not so much an argument, it’s my personal experience. My experience was just not great. Maybe I did something wrong, but I’ve had a way better experience with Antergos, Arch, Fedora, and Ubuntu.
Idk what was wrong then, but I constantly had issues with packages being out of date due to the kernel and not wanting to update. Dependencies were constantly a mess. I’d rather just have normal Arch or Antergos/Endeavor
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.