0
7
1henno1

@feddit.ch

1henno1 6 points 3 years ago

Sadly not as AFAIK you need to be connected to the same network as the device (at least on iOS)

path: 0 2432559 2433864 2434416, hotness: undefined, score: 6, children: 0
1henno1 5 points 3 years ago

Any chance it was „CYB3R HUNT“? I‘ve never played it but saw a post about it here a while ago…

path: 0 5495834, hotness: undefined, score: 5, children: 2
1henno1 3 points 3 years ago

Could it be the ::: spoiler (possible spoiler) Mauvoisin dam ::: ?

path: 0 803122, hotness: undefined, score: 3, children: 2
1henno1 2 points 3 years ago

Mine was a Raspberry Pi in the early 2010s - I‘d had relatively little experience with computers before and had no idea what a terminal was (or even Linux for that matter, tbh), so it took me a good couple of weeks to even figure out how to reach the desktop… Used Windows most of the time after that, but got back into Linux via Ubuntu a couple of years ago. I‘ve now switched to Fedora as my daily driver and wouldn‘t go back either :)

path: 0 1221652, hotness: undefined, score: 2, children: 0
1henno1 1 point 3 years ago

Nice! No worries, glad I could help :)

path: 0 5495834 5499213 5504699, hotness: undefined, score: 1, children: 0
1henno1 0 points 3 years ago

(Here‘s my adjusted version too in case that helps :)

path: 0 5278974 5279027, hotness: undefined, score: 0, children: 0
1henno1 -1 points 3 years ago

I had the same problem (running Fedora 38), and this post really helped me - it goes through the whole MOK generation/enrollment and then provides a script to automatically sign the modules. I had to make a couple of adjustments to make it work on my system and to automatically load the modules with modprobe , but now I just run /sbin/vboxconfig; /root/bin/sign-vbox-modules each time my kernel gets updated and can use VBox fine again.

path: 0 5278974, hotness: undefined, score: -1, children: 1

thanks for using Leebra!

go to feed...