Lunduke
News • Science & Tech
Make Computers Fun Again - Linux, UNIX, Alternative Operating Systems, Computer History, and Retro Computing. Also dad jokes.
Interested? Want to learn more about the community?
September 19, 2022

I got a mad idea, and I blame DOS week for. The background for this is special_snowflake, the FOSH computer I've been building/writing for the last 5 years. Without going into all the details (because then I'll be here for two days), its new CPU is registerless and directly reads and writes into main memory for all instructions. To make it performant, the "main memory" is 0.5-8 KiB is size and treats the actual RAM as expanded memory, copying bits of it in and out. Like a disk. Now, that leaves me with the question of organization of this expanded memory. I decided I won't go the normal route and I won't implement a virtual memory system. Which leaves me with the question of what to do.

And then it occured to me yesterday. What IF you treated your expanded memory as a literral disk and put FAT on it? To allocate memory, processes create a file of some size. Processes can pass memory objects to each other by passing filesystems paths around. All memory objects are dynamically sized. Some implementations of FAT (DR-DOS 6.0 and others) track user&group ID as well as access permissions for them. You could literally implement the well-understood-by-sysadmins Unix filesystem permissions model for all memory! Super important: a single categorization unites ALL of memory which means ALL of memory is always accounted for. Modern systems have all kinds of weird kinks. Inodes, sysfs, procfs, netlink, ioctl, device nodes, semaphores, muliple kinds of sockets, multiple namespaces for all those kinds of sockets, acl, quotas, memory maps, process trees, uids and guids, mounts, etc, etc... If you put all of those into a filesystem, you suddenly make them all observable and manipulable. Another benefit: it's now possible to dump the entire contents of memory to real disks and examine them or change them. Messing with system internals is now easier than ever! And the best part? Both the running memory and the disk image of it can be manipulated with normal filesystem tools!

This can be made to play real nice in a microkernel design with lots of system daemons offering services. I already checked the extensive Wikipedia article on FAT and I found that it practically nativelly supports being used for this purpose. You would need to repurpose some fields from what Microsoft uses them for, but this is a long and time-honoured tradition. The article (linked below) lists several mutually incompatible standards for various data structures that were all used in parallel by several operating systems from several vendors.

Besides breaking the Microsoft's non-standard on FAT, there are two other problems I can see. The first is that my CPU is big-endian and FAT is used on little-endian machines which means the multi-octet fields will be messed up. That can be lived with - this will only come into effect if somebody attempted to mount the memory image on a little-endian machine, but that can be fixed by the appropriate filesystem driver.

The much bigger problem - and the only serious problem I've so far seen - is that FAT keeps track of file contents in a singly linked list. That's.... inapropriate for quick access. :) Since the use of this scheme implies there is only one daemon which manages the memory filesystem for all other applications, and since this is the only place where file handles (or whatever) is handed out, this limitation can be worked around. The filesystem daemon could keep a special structure for all open files/assigned file handles which has a map to all clusters that are part of the file. So if you want to randomly access parts of a large file, the FS daemon doesn't have to read the entire FAT from the start, it can just read from its map. But the problem is that, since this is a memory management scheme, most files can be expected to be open. Which would mean most files would have an associated fast-access map. But then the question is why have the FAT, if most access is going through the map?

Another mitigation strategy is to take care to have the memory defragmented, and then try to assign memory in large contiguous blocks of clusters. That way, if the random access happens inside such a large block, working out the sector (=page) that is to be accessed should be straightforward. The access map cache from the previous paragraph then only needs to keep track of starts and lenghts of blocks. The scheme is simpler, requires less overhead, and should benefit from the last four decades (!) of improvements to FAT drivers and algorithms.

This manage-memory-as-a-filesystem idea can BTW also be implemented on normal registered CPUs, by having some pages (in the reserved section between the sector 0 and the first FAT table xD ) function as faux main memory for currently running processes and the rest used in the FAT.

Wikipedia page on FAT: https://en.wikipedia.org/wiki/Design_of_the_FAT_file_system

Interested? Want to learn more about the community?
What else you may like…
Videos
Podcasts
Posts
Articles
The Phrack, North Korea, & Proton Mail Story

A hacker for the 1980's zine, Phrack, gained access to a North Korean cyber espionage system... then got banned by Proton Mail. Yeah. It's crazy.

More from The Lunduke Journal:
https://lunduke.com/

00:10:52
Open Source Leftists Celebrate Murder of Charlie Kirk

Within moments of Charlie Kirk being shot, the Leftist Activists of Open Source & Big Tech were celebrating - including Tech Journalists, Linux developers, and employees of Red Hat.

More from The Lunduke Journal:
https://lunduke.com/

00:23:38
September 09, 2025
Is an "Amazon Worker Intifada" Forming?

"Palestinian resistance is forming at Amazon." Pro-Hamas Amazon employees tell executives "[we] outnumber you" and "we will force your hand". Thanks to an Amazon whistleblower for the details.

More from The Lunduke Journal:
https://lunduke.com/

00:09:40
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

Live Lunduke Journal show today at 1pm Eastern (5pm UTC, 10am Pacific).

Will be streaming on X, Locals, Rumble, & YouTube.

post photo preview

RIP Charlie Kirk :(

September 10, 2025

Lunduke is back with a live show tonight!

5:30pm Central (3:30pm Pacific, 10:30pm UTC)

Will be broadcasting on X, Rumble, Locals, & YouTube. Free for the nerds of the world to enjoy.

post photo preview
Keep The Lunduke Journal Free!

So far, in 2025, The Lunduke Journal has published 246 shows — being the only Tech News outlet covering the vast majority of those stories.

All without even the slightest influence from Big Tech. No sponsorships, no ad reads, not a penny taken from any company.

And every single story — every article, podcast, & video — is free to share far and wide.

In order for The Lunduke Journal to continue doing this unique work — to keep the lights on well into the future — we need your help.

If you haven’t yet become a subscriber to The Lunduke Journal, doing so today makes a big impact. Pick one of the options below. Big or small. Monthly, Yearly, or Lifetime subscriptions — or even simply one-time donations — all make a huge difference.

Support The Lunduke Journal

Monthly or Yearly Subscriptions:
Locals, Substack, X, YouTube, or Patreon

Lifetime Subscriptions:
Pay Once, For Life (Locals & Substack)

One-Time Donations:
Locals or Bitcoin

You Make The Lunduke Journal Possible

Seriously. This is all possible because of you.

We are able to make all of this free to share with the world because of you.

Might I make a suggestion?

The Lifetime Subscription (which counts towards both Substack and Locals) is a marvelous, one time, way to show support. And it comes with all of the perks (access to the Locals community as well as the official Lunduke Journal forum, & DRM-free eBooks).

You can snag a Lifetime Subscription via Locals, Substack, or with Bitcoin. Lots of options.

But, heck, any type of subscription (via any platform) is appreciated! Choose whichever works best for you!

Then be sure to go to Lunduke.com and choose the platforms which are the most convenient for you to use — The Lunduke Journal publishes all over!

And, once again, thank you for making The Lunduke Journal possible.

-Lunduke

Read full Article
September 08, 2025
post photo preview
Lunduke Journal hit 9 million views in August
And still not taking a single penny from Big Tech.

Thanks to all of you, August was a truly spectacular month for The Lunduke Journal.

After everything was tallied up — audio podcast downloads, video views, and article views — all of you viewed (or listened to) my work over 9 million times last month.

I’m not sure if that’s a record or not — I’ll need to go over some of the past stats to be sure — but it definitely makes me smile.

It means that the real Tech News — the stories that most Tech Journalists refuse to tell — is getting out there. In a big way. No matter how much Big Tech wants some of these stories to go away.

Stats for August

Here’s some Lunduke Journal stats (because stats are fun):

  • 238 shows, so far, in 2025 (Jan 1st → Sep 8th, nearly one show per day).

  • Over 9 million views (or listens) during the last month (August) alone.

  • 131,817 free subscribers (not including audio podcast feeds).

  • 4,488 new free subscribers on the primary platforms.

  • $0.00 (zero) taken from any corporation (no sponsorships, no ad campaigns… not a penny).

9 Million “views”. In one month. Hot diggity!

You better believe I’ll be keeping a close eye on the stats this month to see if we get close to 10 Million. Because 10 Million is a nice, big round number.

And big, round numbers are fun.

No Sales in September

One other thing I wanted to mention: I’m hoping to do away with sales and discounts on Lunduke Journal subscriptions. Which means no sales during this month (September).

My hope is that, with the rapidly growing size of The Lunduke Journal’s audience, enough new subscriptions and donations will continue to roll in to keep this publication afloat… without sales. Because, let’s be honest, sales are kind of annoying, right?

The Lunduke Journal is unique in taking zero money from any company (while giving away nearly everything for free). Most Tech News outlets struggle to keep the lights on even with running paid ads (and paid articles) nearly non-stop.

Being funded 100% by all of you is something no other Tech News outlet even attempts.

And if we can do that while making all articles & shows free for the world… without needing to run any sales or promotions? How amazing would that be? It would send a profound message.

With that in mind, if you appreciate The Lunduke Journal, consider grabbing a subscription. Big or small (and via any platform), every subscription and donation goes directly to making this work possible.

Once again, a huge thank you for every subscription and donation.

Truly, The Lunduke Journal would not be possible without all of you.

Now, if you’ll excuse me, I have another show to record… which is probably going to make another Tech company very grumpy.

I love my job.

-Lunduke

Read full Article
September 01, 2025
post photo preview
Fired Microsoft Employee Encouraged Corporate Sabotage
Leaked screenshots from a Microsoft whistleblower reveals efforts, by a "Worker Intifada" organizer, to disrupt Microsoft business and send spam propaganda email to thousands.

This last week, members of the Microsoft “Worker Intifada” claimed that some of their members were fired by Microsoft in an attempt to silence the speech of pro-Palestinian employees.

Thanks to an internal Microsoft whistleblower, we have gained additional insight into the real reasons at least one of the “Intifada” organizers was fired.

Including mass emailing thousands of Microsoft employees with anti-Microsoft messages, and building internal, corporate websites dedicated to disrupting company business. Over the course of months.

And, of course, we’ve got screenshots.

The Microsoft “Intifada”

The Microsoft’s “Worker Intifada” held a press conference, on August 28th, at the office of CAIR — a response to a Microsoft’s Media briefing held 2 days earlier.

The topic of both press events being the “Intifada” actions of the previous week — including vandalism, breaking and entering, and public demonstrations against Jewish people (with chants of “Go away, Jews!”).

A key topic being the firing of 4 Microsoft employees related to the “Intifada”.

One of those fired employees is Nisreen Jaradat, seen here speaking at the press conference at CAIR on August 28th:

 

Thanks to leaked Microsoft material, we can get a glimpse into the anti-Microsoft activity of Nisreen Jaradat… going back several months.

Anti-Microsoft Microsoft Employee

Nisreen created an internal website — on the Microsoft corporate Intranet — entitled “PledgeForPalestine”.

 

On that website, Nisreen encourages employees to take a pledge declaring that employees will “not support genocide”, specifically demanding that Microsoft no longer interact with Israel in any way.

It should be noted that, as of just a few days ago, this website was up within Microsoft.

Nisreen’s website also includes a list of ways where employees could sabotage internal corporate work.

 

Nisreen encouraged employees to:

  1. Refuse to work on support tickets that involve Israel (and sabotage any tickets worked on by others).

  2. Refuse to work with other employees on tasks which may involve Israel — or any Israeli Microsoft employees or customers.

In July, Nisreen sent internal Microsoft Teams messages to thousands of employees encouraging them to sign that anti-Israel and anti-Microsoft pledge.

 

But this wasn’t the first time Nisreen spammed Microsoft employees with pro-Palestinian propaganda.

Back in May of this year, Nisreen sent an email to over 8,000 Microsoft employees entitled “You can’t get rid of us.”

 

Within that email, she declared that her employers have “shown their true face, brutalizing, detaining, firing, pepper spraying, threatening and insulting workers and former workers protesting.”

Surprise, She Got Fired

Protesting your bosses and accusing them of “genocide” while encouraging thousands of other employees, in spam emails, to sabotage corporate work?

Now, think what you will about Microsoft… but I can’t imagine any company not firing someone who takes those actions internally.

In fact, I would suggest that it is wild that Microsoft put up with the actions of this “Intifada” organizer for so many months.


If you would like to be a Tech whistleblower — or would like to support the work of The Lunduke Journal — head to Lunduke.com. All of the information is there.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals