Blog

I originally registered SecureLang.com but missed a renewal while I was getting thrown out of my rental in Narooma, now they want $850+ to get it back but I think I have other ideas.

The American internet doesn’t really work for businesses in rural Australia because it barely allows us to run our own servers here, they just sell us consumer connections so we can buy from American sites but just getting an IP address can be a pain in the arse. The artificial housing scarcity here (which is just drugfucked landlords controlling the law and being dicks to everybody) makes it hard to get any stable internet connection at all.

So I think I’m gonna keep working on network technologies and come up with a local alternative, hopefully as compatible as possible but making it easier to run sites locally (my current site is hosted in USA). That will probably piss some people off though, as there has been a lot of pushback against developing technologies locally, especially from people embedded in this government who serve foreign nations.

Many people both foreign and Aboriginal are kept hostage by this government against our will. They refuse to acknowledge their fuckups or deport me to Egypt.

I am not an Australian, I am foreign to those people, they didn’t want me in their schools and their army treats me as an enemy race, they told me they would never hire me. I need to be returned to an African nation where I am allowed to join the army, and this land needs to be returned to Aboriginals for their own nations.

The “whites” here are mostly backwards Jews who hate technology and despise children, I don’t know how to coexist with that race of people as they don’t have any intentions of coexisting with anyone else. Their laws are idiotic and they need to deport me, they can’t spend their whole lives trying to keep me out of industry it’s sorta pathetic.

Networking Finished

After success porting the protocol stack itself I’ve ported the driver and ifconfig program from the xv6-riscv-net demo of microps to my new kernel and it looks like it all works.

This makes the network system basically complete, although a few patches will be needed to enable real workloads as only basic versions of the networking system calls are implemented for now (e.g. the kqueue system hasn’t been linked to the new socket code yet).

Nano-X Port In Progress

The build of Nano-X to go with the system now includes a few changes leaning towards getting it to build & run in unusual circumstances.

Aside from the new simplified build system, this involves changes to the server initialisation code to make it easier to configure it to use AF_INET sockets instead of local domain sockets (normally this is platform-dependent instead of being a separate option).

Source code for these/other changes to Nano-X will be included when it is included in a release.

Convenient Date For A Filesystem Epoch

The filesystem code was mostly written a year or so ago but I didn’t add support for “real time” clock (date & time support) until right at the end of the year, so maybe the midnight just passed will be a good epoch point when adding this support to the filesystem.

This idea is mostly just cosmetic engineering but could help distinguish the operating system as something focused on new developments.

Some system calls have now been integrated with the network stack, and the system appears to initialise correctly (but without drivers).

This means the port of microps network protocol stack is almost complete, aside from finishing some more system calls and writing or porting some drivers.

Simple Networking Soon

This networking implementation is mainly aimed at being simple, rather than importing a larger “full” network stack. So hopefully this network stack will continue to be easy to work with as I look at bringing up more drivers & legacy software, but it won’t fully replace the features of Linux or BSD network stacks.

Fast Networking Later

Improvements such as optimisations, extended protocol support or added security checks can be added to this codebase later, or could be implemented as alternative network implementations.

https://www.tomshardware.com/tech-industry/semiconductors/china-tells-chipmakers-to-use-homegrown-chipmaking-tools-for-50-percent-of-new-capacity-decree-designed-to-squeeze-foreign-suppliers-out-of-supply-chain

Hopefully the rest of the world can learn from China and start supporting our own people for once.

Some initial announcements for 1.1.x updates have already been posted, this post will go over their technical implementation and current integration status.

Kernel Inet

The network stack will be minimal but should work particularly well for testing simple drivers.

This is based on https://github.com/pandax381/microps which conveniently already has a RISC-V demo on xv6 (which I used as a reference for the new kernel). This code is MIT licensed and is an optional module in kernel builds.

DistNX

Modern graphics stacks can be a nightmare compared to what is actually needed to run many business apps & classic games.

Porting old or new desktop systems mostly used on Linux to a new platform would be a time consuming task, whereas writing a whole new system from scratch would be a waste as the old graphics systems worked fine for most apps.

So the compromise, for now at least, will be to use a fork of Nano-X (a GUI system designed for embedded devices) but ideally scaled up a little for easy distribution as a non-bloated but general-purpose window system server.

The fork currently is almost unmodified sources from Nano-X but with a simpler build system aimed at easy/reproducible server builds, and this will stay open source or mostly so in compliance with the original license.

These are just being delayed while (the rest of) the OS is pushed into a usable state, but the payoff will be worth it as this will all still feed back into compiler testing!

The windowing system is now partly-integrated, but it won’t run until there is more OS support (sockets, drivers).

As for networking functions there have been some improvements to projects I’ve been watching in that field, so I’m gonna go right ahead and integrate a basic TCP/IP stack into the kernel at the same time I start implementing local sockets. This will probably take a little while to get right.

So it’s likely that the 1.1 release will include both these major components (GUI & networking) but in an unusable form (i.e. they will just report missing drivers for now), and a 1.2 release will follow once they become somewhat usable. This way 1.2 will be like a preview of a full “version 2” product with most auxiliary features working in some basic form, and 1.1.x will just be the initial versions of those 1.2 changes.

Both of these components were developed by third-party developers, so at least the GUI will remain mostly open source, and the networking subsystem will also be made optional if possible.

SecureLang™ REFDOS will continue to be a command-driven operating system focused on filesystem tools and other core OS features, it is designed to run on devices without graphics.

The GUI will be something like a classic desktop that can run on top of the operating system, when drivers permit! It will probably be more useful on Linux/Mac/Windows in the short term.

I can probably start posting political shit with my software now. I don’t have to care, I’ve almost made it.

Next OS release will probably ship with a windowing system but it won’t work yet. Some teasers:

• It’s not Wayland
• It’s not X11
• It’s not something new
• It may end up as a full fork with new features

There’s still a lot of work I’ve got to do to get it working, and I don’t know how long that’ll take maybe that’ll be a forever thing, but a major port is in progress! I’m looking at the code right now… The refactoring has begun, better announcements will be made when it uhhh works (or at least when it compiles for the system).

Implications For Networking

Porting a GUI rather than implementing my own means that I’ll need to use the network functions (which means I’ll need to implement my own network functions).

So this happens to be convenient for testing the network functions, and implies that local implementations of those functions will be the first step towards bringing up proper networking.

Implications For My Business

This move is part of a shift away from developer tools, towards protocols & standards relevant to consumers. But the initial graphical versions will still be developer-centric.