The effort is part of a pan-European effort toward "digital sovereignty."
The effort is part of a pan-European effort toward "digital sovereignty."
Oldie but goodie:What is Windows ?
Picard: Mr. LaForge, have you had any success with your attempts at finding a weakness in the Borg?
And Mr. Data, have you been able to access their command pathways?
Geordi: Yes, Captain. In fact, we found the answer by searching through our archives on late Twentieth-century computing technology.
Geordi presses a key, and a logo appears on the computer screen.
Riker [looks puzzled]: What the hell is 'Microsoft'?
Data [turns around to answer]: Allow me to explain. We will send this program, for some reason called Windows, through the Borg command pathways.
Once inside their root command unit, it will begin consuming system resources at an unstoppable rate.
Picard: But the Borg have the ability to adapt. Won't they alter their processing systems to increase their storage capacity?
Data: Yes, Captain. But when 'Windows' detects this, it creates a new version of itself known as an 'upgrade'. The use of resources increases exponentially with each iteration. The Borg will not be able to adapt quickly enough. Eventually all of their processing ability will be taken over and none will be available for their normal operational functions.
Picard: Excellent work. This is even better than that 'unsolvable geometric shape' idea.
.. . . 15 Minutes Later . . .
Data: Captain, We have successfully installed the 'Windows' in the command unit and as expected it immediately consumed 85% of all resources.
We however have not received any confirmation of the expected 'upgrade'.
Geordi: Our scanners have picked up an increase in Borg storage and CPU capacity to compensate, but we still have no indication of an 'upgrade' to compensate for their increase.
Picard: Data, scan the history banks again and determine if their is something we have missed.
Data: Sir, I believe there is a reason for the failure in the 'upgrade'.
Appearently the Borg have circumvented that part of the plan by not sending in their registration cards.
Riker: Captain we have no choice. Requesting permission to begin emergency escape sequence 3F . . .
Geordi [excited]: Wait, Captain I just detected their CPU capacity has suddenly dropped to 0%!
Picard: Data, what do your scanners show?
Data: Appearently the Borg have found the internal 'Windows' module named 'Solitaire' and it has used up all the CPU capacity.
Picard: Let's wait and see how long this 'solitaire' can reduce their functionality.
.. . . Two Hours Pass . . .
Riker: Geordi what's the status on the Borg?
Geordi: As expected the Borg are attempting to re-engineer to compensate for increased CPU and storage demands, but each time they successfully increase resources I have set up our closest deep space monitor beacon to transmit more 'windows' modules from something called the 'Microsoft fun-pack'.
Picard: How much time will that buy us?
Data: Current Borg solution rates allow me to predicate an interest time span of 6 more hours.
Geordi: Captain, another vessel has entered our sector.
Picard: Identify!
Data: It appears to have markings very similar to the 'Microsoft' logo ...
Over the speakers: THIS IS ADMIRAL BILL GATES OF THE MICROSOFT FLAGSHIP MONOPOLY. WE HAVE POSITIVE CONFIRMATION OF UNREGISTERED SOFTWARE IN THIS SECTOR. SURRENDER ALL ASSETS AND WE CAN AVOID ANY TROUBLE. YOU HAVE 10 SECONDS!
Data: The alien ship has just opened its forward hatches and released thousands of humanoid shaped objects.
Picard: Magnify forward viewer on the alien craft.
Riker: Good God captain! Those are humans floating straight toward the Borg ship with no life support suits ! How can they survive the tortures of deep space?!
Data: I don't believe that those are humans, Sir. If you will look closer I believe you will see that they are carrying something recognized by twenty-first century man as doe skin leather briefcases, and wearing Armani suits.
Riker and Picard together [horrified]: Lawyers!!!
Geordi: It can't be. All the Lawyers were rounded up and sent hurtling into the sun in 2017 during the Great Awakening.
Data: True, but appearently some must have survived.
Riker: They have surrounded the Borg ship and are covering it with all types of papers.
Data: I believe that is known in ancient venacular as 'red tape' it often proves fatal.
Riker: They're tearing the Borg to pieces!
Picard: Turn off the monitors. I can't stand to watch, not even the Borg deserve that.






I do similar, but RDP over VPN (the server runs headless).Running over a SSH forwarding for X from the server to the desktop machine.
The benefit is that only the VPN server needs to be exposed to the internet. All the other servers and VMs work behind the VPN, regardless of location....RDP over VPN
Yes. Assuming you use a realtime kernel (like Debian's RT kernel, for example) and properly develop for realtime application. I haven't used Linux RT for quite a while but it was good enough for a project in a research lab when I did and it's only gotten better.Dumb question, but I want to hear the answer from those in the know. Is Linux a truly deterministic OS? ... More to the point, can it be reliably be trusted to control complex machinery in real time?
Yes and no .Dumb question, but I want to hear the answer from those in the know. Is Linux a truly deterministic OS? ... More to the point, can it be reliably be trusted to control complex machinery in real time?

A modified simple example:[ 1741.657326] Serial Device opened.
[ 1741.660893] rcv_buff called:
Len: 12
Value:Hello World.
[ 3172.957831] Serial Device Closed.
#include <linux/errno.h>
#include <linux/gnss.h>
#include <linux/init.h>
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/of.h>
#include <linux/regulator/consumer.h>
#include <linux/serdev.h>
#include <linux/pm_domain.h>
#include <linux/pm_runtime.h>
static struct serdev_device_ops slave_ops;
size_t rcv_buf(struct serdev_device *, const unsigned char *, size_t);
size_t rcv_buf(struct serdev_device * serdev, const unsigned char * buf, size_t n)
{
char pr_buff[128] = {0};
int i = 0;
for (i = 0; i < n; i++)
pr_buff[i] = buf[i];
pr_buff[i + 1] = 0;
pr_info("rcv_buff called:\nLen: %ld\nValue:%s\n", n, pr_buff);
return n;
}
/*
* find the device-tree serial device, open and configure
*/
static int serbmc_probe(struct serdev_device *serdev)
{
int iret = 0;
unsigned char msg[] = "Hello World.";
slave_ops.receive_buf = rcv_buf;
serdev_device_set_client_ops(serdev, &slave_ops);
iret = serdev_device_open(serdev);
if (iret < 0) {
pr_err("Error Opening Serial Device.\n");
return iret;
}
pr_info("Serial Device opened.\n");
serdev_device_set_baudrate(serdev, 115200);
serdev_device_set_flow_control(serdev, false);
serdev_device_write_buf(serdev, msg, 12);
return 0;
}
static void serbmc_remove(struct serdev_device *serdev)
{
serdev_device_close(serdev);
pr_info("Serial Device Closed.\n");
}
static const struct of_device_id serialbmc_of_match[] = {
{.compatible = "serdev,bmc"},
{},
};
MODULE_DEVICE_TABLE(of, serialbmc_of_match);
static struct serdev_device_driver fgb_serialbmc_driver = {
.driver =
{
.name = "bmc-serdev",
.of_match_table = of_match_ptr(serialbmc_of_match),
.pm = NULL,
},
.probe = serbmc_probe,
.remove = serbmc_remove,
};
module_serdev_device_driver(fgb_serialbmc_driver);
MODULE_AUTHOR("nsaspook <nsaspook@nsaspook.com>");
MODULE_DESCRIPTION("Serial BMC driver");
MODULE_LICENSE("GPL");
Makefile:
PWD := $(shell pwd)
obj-m += ser_dev.o
CROSS = aarch64-linux-gnu-
KERNEL_DIR = /lib/modules/`uname -r`/build
all:
make ARCH=arm64 CROSS_COMPILE=$(CROSS) -C $(KERNEL_DIR) M=$(PWD)
clean:
make -C $(KERNEL_DIR) M=$(PWD) clean

The sun50i-h616-ph-uart5 and sun50i-h616-ser_dev overlay files create the serial device. First with the sun50i-h616-ph-uart5 file, we enable the port and give it physical pins.verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun50i-h616
rootdev=UUID=6315e3ae-0549-44fe-81de-c54f6cc0ee41
systemd.unified_cgroup_hierarchy=0
rootfstype=ext4
overlays=gpu
param_spibmc_spi_bus=1
user_overlays=sun50i-h616-spi1-spibmc sun50i-h616-ph-uart5 sun50i-h616-ser_dev
Physical address on the SoC, the RX/TX pin names and the PH pins (uart5_ph_pins added to the SoC include file for use here)./dts-v1/;
/plugin/;
/ {
fragment@0 {
target-path = "/aliases";
__overlay__ {
serial5 = "/soc/serial@5001400";
};
};
fragment@1 {
target = <&uart5>;
__overlay__ {
pinctrl-names = "default";
pinctrl-0 = <&uart5_ph_pins>;
status = "okay";
};
};
};
Next, create the serial bus device for the kernel module:uart0_ph_pins: uart0-ph-pins {
pins = "PH0", "PH1";
function = "uart0";
};
uart5_ph_pins: uart5-ph-pins {
pins = "PH2", "PH3";
function = "uart5";
};
If all is good you see something like this on the uart diagnostic port uart0/dts-v1/;
/plugin/;
/ {
compatible = "orangepi,spibmc,rohm,dh2228fv";
fragment@0 {
target = <&uart5>;
status = "okay";
__overlay__ {
bmc-serdev {
compatible = "serdev,bmc";
status = "okay";
};
};
};
};
and the devices are created in kernel memory that can be probed directly in the module without the need to access the userland TTY file.Found U-Boot script /boot/boot.scr
3636 bytes read in 2 ms (1.7 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
306 bytes read in 1 ms (298.8 KiB/s)
30384 bytes read in 10 ms (2.9 MiB/s)
Working FDT set to 4fa00000
222 bytes read in 21 ms (9.8 KiB/s)
Applying kernel provided DT overlay sun50i-h616-gpu.dtbo
641 bytes read in 3 ms (208 KiB/s)
Applying user provided DT overlay sun50i-h616-spi1-spibmc.dtbo
462 bytes read in 3 ms (150.4 KiB/s)
Applying user provided DT overlay sun50i-h616-ph-uart5.dtbo
343 bytes read in 3 ms (111.3 KiB/s)
Applying user provided DT overlay sun50i-h616-ser_dev.dtbo
4203 bytes read in 22 ms (186.5 KiB/s)
Applying kernel provided DT fixup script (sun50i-h616-fixup.scr)
## Executing script at 45000000
