#sarge — Public Fediverse posts

Heavy Metal Geomatrix with Billy

Welcome back, comic crusaders and digital daredevils! This week on Play Comics, we’re diving into the gloriously chaotic world of Heavy Metal: Geomatrix for the Sega Dreamcast—a game that asks, “What if Heavy Metal magazine became a button-mashing arena brawler with enough explosions to make Michael Bay jealous?” Released by Capcom in 2001 and featuring the wild art of Simon Bisley, this four-player deathmatch extravaganza throws you into a 23rd-century future where VR-addicted humanity battles it out in submerged cities, all while capturing the magazine’s signature blend of sci-fi, fantasy, and “did my mom just see that?” moments.

Joining us for this high-octane journey through neo-cyberspace mayhem is none other than our beloved returning guest Billy – yes, the same mysterious internet hermit who graced us with his presence during our previous mecha-focused episodes covering Gundam Battle Assault 2 and Gundam Wing: Endless Duel. Billy’s back to help us navigate the testosterone-fueled battlegrounds of teams like the 818 Stompers, 991 Elite, 707 Metal Heads, and 323 Agents, because apparently in the future, gang names are just random numbers followed by edgy nouns.

So grab your favorite energy drink, prepare your best robot voice impressions, and settle in for another episode where we discover if this Dreamcast gem was a faithful adaptation or just an excuse to watch scantily-clad warriors duke it out with bazookas and laser swords in the name of preserving humanity. With Billy’s expert commentary on all things giant robot-adjacent, this promises to be more entertaining than watching someone try to explain the plot of Heavy Metal magazine to their grandmother!

Learn such things as:

• Can nano-technology make terrible character names sound cooler?
• Is it possible to have too many weapons in one arena, or is that just quitter talk?
• How many metal bands does it take to make a video game soundtrack truly “heavy”?
• And so much more!

You can find Billy nowhere online because he’s a hermit who hides out in those secret places of the internet that only we know about.

If you want to be a guest on the show please check out the Be a A Guest on the Show page and let me know what you’re interested in.

If you want to help support the show check out the Play Comics Patreon page or head over to the Support page if you want to go another route. You can also check out the Play Comics Merch Store.

Play Comics is part of the Gonna Geek Network, which is a wonderful collection of geeky podcasts. Be sure to check out the other shows on Gonna Geek if you need more of a nerd fix.

You can find Play Comics @playcomics.bsky.social on Bluesky, @playcomicscast on Twitter and in the Play Comics Podcast Fan Group on Facebook.

A big thanks to the Kickstarter campaign for Starlite and The Last Comic Shop Podcast for the promos today.

Intro/Outro Music by Backing Track, who  couldn’t make a better soundtrack for this game. But he could come pretty close.

#BillyCommanderCast #Capcom #Di #Dreamcast #Duke #HeavyMetal #Hound #Kassey #Lance #Mayfly #Phantom #Sarge #Slash #Stab #Talbot #Zeus

@jerry 24/7 pkt cap can cut both ways but you need to know and have regular reports #ntop-ng #sarge #lightsquid

@adamw @mjgardner @Perl There's a solution to that, which is I believe somewhat acceptable albeit annoying, #Debian #sarge used to use it, around 2006ish? @Perl was only the language, and core-modules was core modules. But as someone who packages for #TinyCore, I can tell you what nonsense such concerns are, in TC, perl, the whole thing, is 30 MiB.

Maybe more uncompressed, I don't know, that's the install size of the binary. Full core modules.

@mjgardner language stability was and is an absolutely core language requirement for #inxi. Runs on #Perl 5.008 and 5.36. Validated for 7. I test on #Debian #Sarge #Etch and #Lenny. #slackware guys were testing on 9 if I remember right. I believe the set of languages able to meet these speed, complex data, and feature stability requirements numbers exactly 1. Target is 2005 Linux servers and anything newer. 2.4 kernel or newer. 2.6 better though. ARM MIPS RISC-V Android erc.

@mjgardner language stability was and is an absolutely core language requirement for #inxi. Runs on #Perl 5.008 and 5.36. Validated for 7. I test on #Debian #Sarge #Etch and #Lenny. #slackware guys were testing on 9 if I remember right. I believe the set of languages able to meet these speed, complex data, and feature stability requirements numbers exactly 1. Target is 2005 Linux servers and anything newer. 2.4 kernel or newer. 2.6 better though. ARM MIPS RISC-V Android erc.

@mjgardner language stability was and is an absolutely core language requirement for #inxi. Runs on #Perl 5.008 and 5.36. Validated for 7. I test on #Debian #Sarge #Etch and #Lenny. #slackware guys were testing on 9 if I remember right. I believe the set of languages able to meet these speed, complex data, and feature stability requirements numbers exactly 1. Target is 2005 Linux servers and anything newer. 2.4 kernel or newer. 2.6 better though. ARM MIPS RISC-V Android erc.

@mjgardner language stability was and is an absolutely core language requirement for #inxi. Runs on #Perl 5.008 and 5.36. Validated for 7. I test on #Debian #Sarge #Etch and #Lenny. #slackware guys were testing on 9 if I remember right. I believe the set of languages able to meet these speed, complex data, and feature stability requirements numbers exactly 1. Target is 2005 Linux servers and anything newer. 2.4 kernel or newer. 2.6 better though. ARM MIPS RISC-V Android erc.

@mjgardner language stability was and is an absolutely core language requirement for #inxi. Runs on #Perl 5.008 and 5.36. Validated for 7. I test on #Debian #Sarge #Etch and #Lenny. #slackware guys were testing on 9 if I remember right. I believe the set of languages able to meet these speed, complex data, and feature stability requirements numbers exactly 1. Target is 2005 Linux servers and anything newer. 2.4 kernel or newer. 2.6 better though. ARM MIPS RISC-V Android erc.

#TodayILearned that the voice actor of #DaddyPig, #RichardRidings, also provides the voice of Sarge in #Quake III Arena, as well as the voice of the Mentor, i.e. the narrator, of #DungeonKeeper.
That just tickles my funny bone. 😂

#TIL #QuakeIIIArena #Sarge #voiceActing #voiceActors #TodayILearnt

Finding even more in #pinxi / #inxi working in old distros in vm, #Debian #sarge, failed to handle x log file name XFree86.0.log, no idea how that escaped me, and also modules were _drv.o, not .so, back then with 2.4 kernel, so those tests failed too. Have versions for the sound servers that support version, so the list of fixes / enhancements shaping up nicely for the completed version, 3.3.27, did 26 as a quick out the door get bugs fixed release, but 27 will be the final one for this series.

Filling in the the #inxi / #pinxi sound server/api stuff. Added #aRts, #Esound/#Enlightenment Sound Daemon/esd, filled out #NAS (Network Audio System), added active/inactive detection for #ALSA.

I wanted to get the initial fixes for the standard current sound servers out as bug fixes, which was 3.3.26, and then I figured I'd fill in the rest.

Testing on old #Debian vms, #etch, #sarge, #lenny, all working fine as of today. Sarge shipped with aRts installed, with OSS+2.4 kernel, good test case..

@ChristosArgyrop @mjgardner I have vms of #Debian #Sarge and #Etch, and run #Lenny on an old system, which helps me catch little oversights that slip in now and then. Some other people who test, #mrmazda in particular, runs a lot of old systems, so he catches stuff sometimes too. And I run current Debian testing so I'm also current on reasonable new #perl as well.

....
As a reminder, again, the only true dependency #inxi has is #Perl 5.008 or newer, and a few Perl core modules. This is to capture mainly very old #redhat servers, but also old #Debian servers, #Sarge, #Etch. While not a real dependency, kernel 2.6 introduced a lot more data over 2.4, so systems running 2.4 kernels tend to not show as much information.

#acxi is designed for Perl 5.010 or newer. As I learned once when getting an urgent issue due to bug on 5.010, this matters to acxi users!

....
As a reminder, again, the only true dependency #inxi has is #Perl 5.008 or newer, and a few Perl core modules. This is to capture mainly very old #redhat servers, but also old #Debian servers, #Sarge, #Etch. While not a real dependency, kernel 2.6 introduced a lot more data over 2.4, so systems running 2.4 kernels tend to not show as much information.

#acxi is designed for Perl 5.010 or newer. As I learned once when getting an urgent issue due to bug on 5.010, this matters to acxi users!

....
As a reminder, again, the only true dependency #inxi has is #Perl 5.008 or newer, and a few Perl core modules. This is to capture mainly very old #redhat servers, but also old #Debian servers, #Sarge, #Etch. While not a real dependency, kernel 2.6 introduced a lot more data over 2.4, so systems running 2.4 kernels tend to not show as much information.

#acxi is designed for Perl 5.010 or newer. As I learned once when getting an urgent issue due to bug on 5.010, this matters to acxi users!

....
As a reminder, again, the only true dependency #inxi has is #Perl 5.008 or newer, and a few Perl core modules. This is to capture mainly very old #redhat servers, but also old #Debian servers, #Sarge, #Etch. While not a real dependency, kernel 2.6 introduced a lot more data over 2.4, so systems running 2.4 kernels tend to not show as much information.

#acxi is designed for Perl 5.010 or newer. As I learned once when getting an urgent issue due to bug on 5.010, this matters to acxi users!

....
As a reminder, again, the only true dependency #inxi has is #Perl 5.008 or newer, and a few Perl core modules. This is to capture mainly very old #redhat servers, but also old #Debian servers, #Sarge, #Etch. While not a real dependency, kernel 2.6 introduced a lot more data over 2.4, so systems running 2.4 kernels tend to not show as much information.

#acxi is designed for Perl 5.010 or newer. As I learned once when getting an urgent issue due to bug on 5.010, this matters to acxi users!