Iran is not an enemy of the common person and probably had no involvement in recent attacks on Australia.
Iran’s government have gone out of their way previously to alert Australian authorities of the risk from the Lindt cafe gunman and were ignored in that instance, I would say probably by ASIO and their foreign controllers.
ASIO being run by a foreigner and his foreign mates is the real security risk here, I can’t trust this “Australian” government and anyone who does is an idiot.
What the fuck are you losers doing hiding behind a broke as fuck “intelligence” agency that can’t even afford to pay staff competitive rates? Crawling up Israel’s arse looking for shekels?
I might as well run my own intelligence agency if any underqualified broke foreigner can do it.
I offered to help with these kinds of negotiations for the Australian Army when I was young and fit but the obese fuckers who were in charge of DFRC treated me as an enemy race, deeming me permanently unfit for service the moment they found out I’m an Arab.
Oh well, now I am enjoying watching your soldiers and their allies get cooked by Iran. And yes I’m pretty sure there were some Australians in those buildings.
PS: Australian soldiers are too fat to run and they suck at IQ tests. Their army seems to have intentionally hired idiots over capable people.
Aside from developing a whole new GUI there were a few options, it looks like the port of nano-X will be the first working GUI on the new kernel once I sort out some compatibility & system call issues (see dump of serial console above, the system currently lacks support for named sockets).
The Australian government overall do not have title over Aboriginal land. Their army are fat and cowardly, their police do nothing but protect criminals, they destroy local industries and they would be useless against an organised opponent.
I’ve reported in public before that there seems to be suspicious drone activity at night and nobody here cares 🤷, some possible targets or origins of foreign drone activity are just North of here especially around Jervis Bay. The people here seem to have little interest in defending a government who are dickheads to everybody.
The people who run the Australian government will just give any contract to their friends.
https://www.canberratimes.com.au/story/9178631/defence-awards-palantir-76m-defence-contract/
But that’s okay, I can play dirty too – I don’t have to give the Australian government access to my infrastructure.
This post is just a recap of the system’s main features and current progress.
Scheduler, memory management, program loading and system calls are all working well for now but will need some improvements over time.
Some advanced features like multithreading, priorities and CPU affinity have been implemented but not yet thoroughly pressure tested.
The kernel & tools are highly specialised for RISC-V platforms, this importantly means that not a lot of “bloat” is needed to support legacy architectures.
Testing has mostly been done on the latest Chinese hardware designs, especially SpacemiT chips.
The filesystem received a lot of work early on and the current codebase supports three filesystem versions:
The system does not have any support for reading or writing Linux/Mac/Windows disks at this stage and this probably won’t be a high priority compared to improving the native filesystem.
A freshly rewritten mkfs program is included so systems can be easily built based on this code.
The filesystem layout supports additional metadata but this hasn’t been exposed in APIs yet.
The networking support is relatively new and still needs some work.
The network stack is based on microps (not based on an in-house design and not based on LWIP like many other small operating systems). I’m really happy with this codebase but my port isn’t the fastest (drivers are a bit laggy) and it will need some extensions or a replacement over time (e.g. only supports legacy protocols, no IPv6).
Performance improvements are underway including a kqueue implementation suitable for server programs (as well as driver improvements), these will be addressed in upcoming releases. IPv6 support, wireless protocols and other things will be left for a release some time further in the future.
This support is only just starting to come online and isn’t fully functional yet, but simple graphical apps will be supported in an upcoming releases.
Most basic command line functionality is already there.
My libc implementation is working well enough, and my compiler backend mostly works (but GCC is used for most builds again for now, just to focus on getting other things working). Getting the compiler to run properly on the new OS will take a little more backend work (finishing the linker etc.).
Other tools like a package manager have been written but haven’t been fully integrated.
It looks like almost everything is working now, aside from some plumbing for GUI apps.
Expected showstopping problems in the short term will probably be limited to some driver performance issues and a lack of drivers for USB peripherals and other things .
There don’t seem to be major architectural issues remaining aside from lacking some internal infrastructure for timers & interrupts & more advanced drivers, this means most drivers will be running in a polling loop without any more advanced/efficient wakeups for now but this will improve as the features stabilise.
My initial 1.0.x releases were very minimal and progress has since pushed the versions past 1.1 (adding basic networking support) without having time to do a proper interim release.
As such my current aim is to prepare a 1.2 release which should have most features of a general purpose OS but with some limitations or design issues remaining. The 1.2 release should be like a preview of a 2.0 release (but without cleanups, optimisations, apps etc.).
This will probably involve settling the releases down into a few builds:
These builds will mostly be similar apart from different kernel configurations intended to make booting easier, so these builds may be interchangeable between different devices but that will just depend on how tolerant the hardware ends up being and on whether specific fixes are needed for some devices that will break others.
Timeframe for a 1.2 release will be around a month, give or take depending how smoothly the work goes.
NOTE: Desktop support will be very limited at first so don’t expect full apps at this stage. After all the basics are working I should be able to start porting X11 type desktop software, so eventually it should be a full featured system.
