techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.6K
active users

#loader

0 posts0 participants0 posts today
James_inthe_box<p>An unknown <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> <a href="https://infosec.exchange/tags/loader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loader</span></a>:</p><p><a href="https://app.any.run/tasks/17232420-9cc7-41f8-937f-16fd654312da" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">app.any.run/tasks/17232420-9cc</span><span class="invisible">7-41f8-937f-16fd654312da</span></a></p><p>c2/drop 185.249.198.213 is suspiciously clean... cc <span class="h-card" translate="no"><a href="https://infosec.exchange/@da_667" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>da_667</span></a></span></p>

The Expert Cartridge – Der Experte unter den Spezialisten

The Expert cartridge wurde 1986 von Trilogic auf den Markt gebracht und war eine sehr beliebte Erweiterung. Und der Fast Loader war eher zweitrangig… Ein interessantes Modul, das einen Nachbau lohnend machte.

#c64 #Cartridge #commodore #Commodore64 #diy #Expansion #Extension #Fast #Freezer #Loader #Port #ram #Replica #TriLogic

dirkwouters.de/the-expert-cart

Dirk Wouters · The Expert Cartridge - Der Experte unter den Spezialisten
More from Dirk Wouters
Replied in thread

@dvl @dch
Not 100% sure about loader.efi, but at least boot1.efi would be affected if any read-incompatible feature(s) is/are enabled and active even on data-only pools.
This is because, in boot1.efi, it sniffs the existence of /boot/loader.efi to determine whether the pool is bootable or not.
loader.efi should need to sniff at least pool name(s), whether it's bootable or not by somehow reading the pool(s).

If you're 100% sure there's not at all a plan to have bootable ZFS (means, use UFS for boot throughout the future), and once confirmed it works as wanted, using gptboot.efi would be the way to go.
It does not sniff ZFS pools (not linked against ZFS codes) and (in contrast with boot1.efi) not obsoleted.