Zen1th

Just released Fuchas 0.7.0! Since the last changelog i posted was about 0.6.0, i'll also post the 0.6.1 changelog! (important changes are in bold) 0.7.0: Core OS: + Security improvements + Fixed Concert + Fushell boot screen is now lighter + New in-OS documentation using OHML + Working shell command history + Working Stardust project: you can run OpenOS binaries on Fuchas + Detachable file handles + Horizontal tab is now an actual tab (not just converted to 4 spaces) + The scheduler is now

Ctrl+Alt+C is made so that, in case of error or bug that cause the program to stop responding, you can still close it. So i wouldn't accept removing it (even for temporary). What you could do however is setup a service which restart the program whenever it isn't alive anymore.

There has been many changes ranging from security to services without forgetting Fuchas now can read and write (it's the first software and OS to do so on OC) CPIO and VELX. All of it is in the github changelog.

Yea if other computers need a service to run on the Fuchas computer in order to do routing, then a service is appropriate for that feature, however the rest would be more appropriate as a network driver.

I didn't really thought about that, i think i'll make a quick way to autorun processes on start they should already be implemented by the time you see this. However, network drivers (like Minitel) are ported using "network" library, it provides a common library for programs to easily interact with any network stack. However again if it really needs a service (like some sort of heartbeat signals or periodic events that really require it), you can use the newly made services feature.

I added a program: "Project Stardust", it allows using OpenOS software on Fuchas ! you just have to "sudo stardust <path of openos program>"

Fuchas 0.6.0: Shell autocompletion OS arguments "buffer" library for buffered streams CPU metrics Concert task manager Architecture-dependent package files (different file depending on having Lua 5.2 or 5.3) Warning displayed when Lua 5.3 is supported but not enabled Optimization of OCDraw (merging) and GPU drivers (avoid setting multiple time the same color) New driver format (less file loading): faster startup time In

Fuchas 0.5.1: Added a clipboard library that can use OC's clipboard event alongside Fuchas generated events with Ctrl+V. Events are pulled from a per-process queue, also allow to push events only to a certain process. OCDraw supports render targets, those are use as a target for the drawing and can be shown, they are basically just images. Unicode support in Fushell and "shell" library. CSettings program Ability to launch programs from Concert Increase startup speed (with Voodoo3 magic) Full support of the UAC system. Interfaces start wit

Sorry for being a bit late, but Fuchas 0.5.0 is available since a month, it offers MANY MANY features: The component access is restricted and driver library must be used (unless having root permissions). This allow for more safety to potential viroooses. A secondary bit32 library on Lua 5.3 to have compatibility between the two in bit operations Directory attributes (currently not settable, only gettable). Which brings 5 attributes: System, Protected, Read-Only, Hidden and No Execute. Support for Protected (R/W only with perm) and System (R without perm, W with perm)

d) Attempt to punch through the wall You attempt to punch through the wall... except you're not in Minecraft, you just hurt yourself. Do you: a) Continue punching b) Continue walking c) Get back d) Look around

4/5 Very great game! Everything is handled greatly and makes a great building game overall. A smooth scrolling could be implemented with little GPU intensive activity. - Zen1th Magazine

You can use the port that is not 80. since i said "SHOULD" and not "MUST". But i'll try to change this for better clarity

I really like this, i suggest we could also add a card:isAbstracted() to know if the network is abstracted or not. So that compatibility for config can be easily made. And for the bandwith, i think this could bring up to cables with mutliple tier (even if this feel like it belongs more to an addon than stock OC). And if i'm not wrong with frequencies, it should be better that the higher frequencies that transmit farther (even if, again if i'm not wrong, higher frequency = lower radius) should have slower bandwith and frequencies that have low range should have higher bandwith. Another thi

i know it was for "simplicity" reasons