you mentioned it twice so I fear the worst, please tell me you didn’t remove 14000 lines manually using a text editor.
you mentioned it twice so I fear the worst, please tell me you didn’t remove 14000 lines manually using a text editor.
well you can put your “not in my computer” opinion in your ass. widespread benchmarks by established gaming journalists show good computers struggling.
you don’t have to know the internals of the engine. you just need some basic deduction powers.
does it look it look good compared to other AAA games? no
does it run fast? no
ergo. the engine is crap.
the same thing happened to cd projekt red but they ditched their engine after the cyberpunk fiasco. they will just pay epic
“we have worked a lot on PC performance. wanted to reach performance parity with consoles for release on similar hardware and we achieved that, However, our teams will continue working on improvements and integrating technologies like fsr and dlss in the future. “
dd is good if the destination disk is equal or bigger, unless you are brave enough to shrink the source partition.
if you are moving to a smaller disk for whatever reason (hdd to sdd) then you need to fallback to a different method, which takes us back to cp/rsync.
why not? sudo cp -ax
foots the bill.
I assume people prefer rsync because you may need to run it twice, but unless you tick all the boxes rsync won’t copy capabilities (see getcap /usr/bin/rsh
)
sudo cp -ax is short and sweet and does everything right.
it’s not the recommended way but it’s how I’ve been doing.
you format the new drives and just cp -a -x from the running os to the destination, update the destination fstab, then treat the new drives as an os with a broken boot and continue from there.
Well of course you can do it quickly with vim. Regardless, my suspicion is that OP deleted the lines manually, hence the need to mention it a couple of times. Otherwise, why would they even mention something you can do with grep in a literal second.