Unfortunately, your existing /home and the ntfs partitions you could remove are in completely non-contiguous regions, so you cannot easily just combine the space. If I were you, I would switch to LVM piece-meal. Ideally, you’d have some other medium were you can temporarily store the current contents of /home while your repartition the drive. Then combine sda2 and sda7 into a volume group and pull just one logical volume out of it for the new /home.

Otherwise, create a new volume group with only sda2 in it (just overwrite the existing ntfs filesystem) using vgcreate, create a logical on top of that using lvcreate, make a filesystem in that using mkfs.ext4, I would add the -m 0 parameter for a non-root filesystem, mount that somewhere under /mnt/, move or copy over all the contents from /home to that mountpoint, taking care to replicate file owners and permissions (I would just use cp -a), then once this is done (and you’ve double-checked that it is because at the next step you can lose data if you’re not careful), umount /home, extend the volume group to include sda7 using vgextend, enlarge the logical volume for the new /home to the maximum using lvresize, enlarge the ext4 filesystem in there to the maximum possible using resize2fs, finally editing /etx/fstab to use that new logical volume as /home and remounting /home.

The nerd inside me automatically wants to correct that to

$ > grass

That avoids starting up one addidtional process.

(Unless the file already exists, and you just want to update its mtime, of course.)

I wouldn’t want to put the air intakes of my Thinkpad directly on the grass like that. It’s bound to suck in dirt.

Years ago, we used to use Etherpad for that. Don’t know if that’s still a thing.

Any further “helpful” information in that error message would be a security issue.

Literacy rates in medieval times were not what they are today, but they’re still routinely underestimated. Most places, including peasant villages, would have had some people around who could read.

Then again, it also depends heavily in what part of the middle ages you are talking about. Early, high and late middle ages were almost different worlds in many regards.

It’s even worse: It answers the questions correctly enough that most people cannot tell the difference – but still not reliably correctly. Meaning you get answer that sound very convincing, but could easily still be dead wrong.

It’s hard to believe how insanely long it took, and still is taking to get a production-ready, solid ntfs driver in linux.

I’m in this picture and I don’t like it.

Cockroaches kill each other and eat each other…

Well, in PHP you cannot #define new words from some new language to mean basic language keywords.

Error correction and compression are usually at odds.

Not really. If your data compresses well, you can compress it by easily 60, 70%, then add Reed-Solomon forward error correction blocks at like 20% redundancy, and you’d still be up overall.

If any person actually typed that they aren’t sane at all.

That doesn’t actually rule out anything.

Except it’s also an important tool to ensure continued employment, and so people have taken to turning the public part of it into an unorganized sycophancy contest.

Probably because a lot of the “people” in the larger networks are literally not “real”. Many of them are secretly bots, and a lot of the rest are either sock puppets or meat puppets

“They’re a private company” (with a state-sponsored monopoly on an essential good).

I don’t know how anybody is surprised by this. Who do you think would buy a privatized municipal water supplier, other than people trying to squeeze as much money as possible from a population with no recourse and no say in the matter?

There is no wise way to use that information.

But the foolish ones could be entertaining.

Saying RAM can help because you can reencode the video to h.264 or h.265 to make use of hardware decoding is more than a bit of a stretch. You can just reencode it to the normal disk instead. Unless it’s the speed of the local block device that’s the bottleneck here (and there’s no indication that it is, and it would be extremely unlikely), using a ramdisk/tmpfs for any part of that is just pointless.

Modern CPUs (from like the last 20 years) will throttle down a lot before they actually shut down. Unless your cooling is completely inadequate or somehow broken, shutdowns because of high load just dont happen. I suspect there is something fundamentally wrong with your hardware.

A problem with cooling could also go some way to explaining your performance problems – but it could also just be that your system just doesn’t have the computing power to do what you want it to. The computing demands from video decoding go up dramatically when you go beyond 1080p. If I recall correctly, the Intel Core CPUs with the “U” at the end were the low-energy models (for longer battery life); of course that comes with compromises on the performance side.

The CPU model suggests that this is a laptop, and a fairly old one at that. I would look for things like blocked air ducts or broken fans if I were you. It’s also possible that the thermal compound between your CPU and the CPU cooler has dried out and needs replacing (although laptops of that power class should be using thermal contact solutions that do not dry out), or that contact has lessened for other reasons. Again, if your computer seriously powers down because of load, it’s borderline broken and in need of maintenance.

As for your other question, no RAM cannot help with that. It can hurt if you have too little of it, but once you have enough, the best it can do is not be a bottleneck.

* Edit: Also, make sure you are not setting down the laptop on anything soft, like a blanket, when using it. It will sink in and have its air intakes blocked if you do that.

You just gave me flashbacks to that abomination of a programming language they call sqf.