here you go;

qemu-img create -f qcow2 Unknown.qcow2 60G
qemu-system-x86_64 -m 3072 -cdrom Unknown.iso -boot d Unknown.qcow2 --enable-kvm
qemu-system-x86_64 --enable-kvm Unknown.qcow2 -cpu kvm64,+nx -m 4096 -device AC97

The below is for loading usbs in said vm:

qemu-system-x86_64 --enable-kvm Unknown.qcow2 -cpu kvm64,+nx -m 4096 -device AC97 -hdb /dev/sdb

@golinux I saw no mention of this on this forum, so I thought I knew something most people here didn't.

I am glad someone is developing an alternative for x86 including 64 bit at least anyhow. Maybe other architectures will follow once they get stable support for their devices.

I am of course talking of HyperbolaBSD. (when its stable!)

If it gets up to snuff the way it should, perhaps Devuan will have another interface of interest if this corporate nonsense starts overtaking linux to the level of no return.

I doubt the point of no return has happened yet though, as devuan still exists.

@GNUser That is fair,.  Btw, to be honest, the only init that is probably as light as sysvinit but still very featured like openrc is runit.

I still have to learn a bit more on how to use it though.

@delgado maybe blobs was the wrong word, what I should have said, is privacy invasive blobs.

Like anything that is a blob that has a network stack that can send stuff where you don't want it.

An example of this for many is, intel me enabled fully in most intel devices.

If you have such a situation, keep important files off of that!

That would be my reply.

@ralph.ronnquist fair point hmm....

Yeah, it must keep resetting... then.  I am doing something a bit out of the norm anyhow for here.

So I will leave it at that.

@golinux I now read what you said about stupidity being the driving force of humanity, but there is one other thing, egos/stubbornness  also plays a huge part too..

Probably a larger part actually.

In simple terms, I did this:

find . -type f -exec sed -i 's/old-word/new-word/g' {} \;

Then I did my command to check to see if it was fixed,

git rev-list --all | xargs git grep -F python2.7

I seem to have gotten mixed up and written wrong thing down... my bad.

In any case, that might help clear up the confusion.

Does the find command you gave me actually replace all mentions of the word python2.7 if I put it as first word with the second word in all source code?

Or am I really confused.

@golinux which is why I am replacing python2.7 with tauthon instead of python with tauthon

;P

Btw, I used this command after doing that:

git rev-list --all | xargs git grep -F python2.7

and it still shows python2.7 mentions... weird stuff.

Correcting what I said, I wrote down the wrong one.

@chris2be8

I got more ram and that fixed the problem thankfully.

@chris2be8 I decided anyhow that I might need more ram. So thats what I will do.

@chris2be8 do you think wayland would be affected by this then? Don't get me wrong, I hate wayland, but this is my gaming computer so ill put up with it if i have to.