

Thanks for cross-posting and tagging me!
InfoSec Person | Alt-Account#2


Thanks for cross-posting and tagging me!
There’s a pretty cool video about it here:
https://www.theguardian.com/environment/2022/aug/04/magnificent-jellyfish-found-off-coast-of-papua-new-guinea-sparks-interest-among-researchers (YouTube link: https://www.youtube.com/watch?v=tpaGYqE7dPA)
AFAICT, it’s the second sighting of this jellyfish.
The original video (without edits) is on Facebook 🤮: https://www.facebook.com/watch/?v=253522076865770


Someone asked the same question on a cross-post: https://lemmy.world/comment/14943883
Tl;Dr is the recent rust drama.
More info: https://www.phoronix.com/news/Asahi-Linux-Lead-No-Upstream
I’m unsure whether your formatting messed up, but you shouldn’t have a space between the shebang (#!) and the interpreter path (/bin/bash). Also add a new line before your command:
#!/bin/bash
gnome-terminal -- sh -c gotop
I tried this on my system (with htop instead of gotop) and it worked.


Yep, a few forks were identified within a few hours. I think the maintainers had forks too.


Do you want to return to that account?
If not, Temp mail works fine.
Also, Bug me not has user-submitted usernames + passwords to services. This works nicely.
I’ve used Port87 in the past. The user who created it promoted the service on lemmy initially. It worked (I paid for a few months).
I suggest using two different spellings:
Mold is the fungus.
To mould is to shape.
Nvm I’m an idiot. Lol
That seems to be the consensus online. But thanks for that tidbit! It feels even more bizarre now knowing that.
I wonder why a handful of people think the way I presented in the post. Perhaps American/British influences in certain places? Reading books by british authors and books by american authors at the same time? Feels unlikely.


Insane. Just insane:
Ah if you messed it up, you can press “e” on the grub entry and edit the command line parameters to remove the thing that messes it up. Good luck with your fresh install [and use Debian this time… jk :)]
Make sure to update your grub after you do. I’ve messed that one up before lol 😅
Do you not need the nvidia-drm.modeset=1 in GRUB_CMDLINE_LINUX?
https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/#262-edit-etcdefaultgrub
Could you show us the kernel command line parameters (in /etc/default/grub)? Is the modeset along with other params enabled? I’m not a fedora user, so I may not be of too much help.
https://www.linuxjournal.com/article/10754
MINIX originally was developed in 1987 by Andrew S. Tanenbaum as a teaching tool for his textbook Operating Systems Design and Implementation. Today, it is a text-oriented operating system with a kernel of less than 6,000 lines of code. MINIX’s largest claim to fame is as an example of a microkernel, in which each device driver runs as an isolated user-mode process—a structure that not only increases security but also reliability, because it means a bug in a driver cannot bring down the entire system.
In its heyday during the early 1990s, MINIX was popular among hobbyists and developers because of its inexpensive proprietary license. However, by the time it was licensed under a BSD-style license in 2000, MINIX had been overshadowed by other free-licensed operating systems.
Today, MINIX is best known as a footnote in GNU/Linux history. It inspired Linus Torvalds to develop Linux, and some of his early work was written on MINIX. Probably too, Torvalds’ early decision to support the MINIX filesystem is responsible for the Linux kernel’s support of almost every filesystem imaginable.
Later, Torvalds and Tanenbaum had a frank e-mail debate about the relative merits of macrokernels (sic) and microkernels. This early history resurfaced in 2004 when Kenneth Brown of the Alexis de Tocqueville Institution prepared a book alleging that Torvalds borrowed code from MINIX—a charge that Tanenbaum, among others, so comprehensively debunked, and the book was never actually published (see Resources).
See also: https://en.wikipedia.org/wiki/Tanenbaum–Torvalds_debate
That’s crazy helpful - thanks!
Thanks for the question!
As long as caches have existed, very similar styles of side channels have been demonstrated since the late 90s. A lot of the terminology we use (flush+reload, flush+flush…) are attack techniques that have been already demonstrated on CPU caches, and these demonstrations are at least a decade old.
Flush+Reload: https://www.usenix.org/conference/usenixsecurity14/technical-sessions/presentation/yarom
Flush+Flush: https://gruss.cc/files/flushflush.pdf
Invalidate+Compare (GPU caches, 2024): https://www.usenix.org/conference/usenixsecurity24/presentation/zhang-zhenkai
My colleague, Hannes, found similar styles of attacks existed with the Linux DNS cache too: https://hannesweissteiner.com/pdfs/dmt.pdf (also published at NDSS 26!)
The one really big difference between the page-cache side channel and other side channels is the “monitor” primitive. There are methods that the OS provides which directly report the presence of a page in cache. These are syscalls like
mincore(mitigated in 2019),preadv2 + rwf_nowait(unmitigated), andcachestat(mitigated in 2025).With these syscalls, we don’t even have to rely on timing information (is page access fast -> cached; is it slow -> not cached). These syscalls really set the page-cache side channel apart because you can nondestructively figure out whether a page is in cache.
The page-cache side channel was first explored in 2019. It was explored on Linux but also on Windows by my advisor et al.: https://gruss.cc/files/pagecacheattacks.pdf
Hope this answers your question :D