Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

Search the Community

Showing results for tags 'operatingsystem'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • OpenComputers
    • Announcements
    • Feedback
    • IRC
  • Code Central
    • Support
    • Showcase
    • Tutorials
  • Addons & More
    • Addons Mods
    • Architectures
    • OpenEngineering Task Force
  • General
    • Lounge
    • Forum Games
    • Showcase
    • Servers
  • Archives
    • Public Archives

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Minecraft


GitHub


IRC


Fediverse ID


Location


Interests

Found 3 results

  1. Fuchas Fuchas in a Nutshell Fuchas is revolutionnary in that it uses drivers instdead of component access and support UAC (witnew OSh separate permissions!) ! It's the end of the era where the program needs to maintain integration with different components, the OS now does it! The driver library will try automatically choosing the best driver, but it can be configured by user. Meaning programs adapt to components with no effort (e.g. Computronics cards) Notice about security: Fuchas is currently alpha and "security" (if we can even call that security) isn't done at all, however the UAC is functional. Another thing is that the security system is being completely revamped in Fuchas 0.7.0, making Fuchas even more secure. Mostly one of Fuchas big feature is security. Feared of viruses or foreign access? Control permissions! Each account can have its own set of permissions! Allow one to have free access on a specific drive? You can do that!. Security is useful for computers on big servers with competivity. Fuchas doesn’t hide files starting with ".", it uses attributes, filesystem’s one if supported on unmanaged drives, or with a .dir file at file’s parent directory. It only provides yet those attributes: System (requires permission to write, but not to read), Protected (needs specific permission to write AND read), Hidden and Read-Only Fuchas is also fast at startup, around 2x faster than OpenOS down like memory usage. And graphical features are optional, so you can use command-line on your T1 computer, and a graphical interface on T3, all on the same OS! And since the UI is compatible with 40x16 and doesn't uses a lot of memory, you can use both on a T1 computer!hey, i'm having a problem in some UAC system, i wouldn't be able to proof an administrator is an admin without some authority (which i can't have), how could i do it without a central authority ?hey, i'm having a problem in some UAC system, i wouldn't be able to proof an administrator is an admin without some authority (which i can't have), how could i do it without a central authority ? Extra Features (WIP - Planned -->) Fuchas will also use the viewport screen feature to have an efficient double-buffer and extra rendering speed compared to other GUIs. It work in a way that for example, user will have a resolution of 80x25, but it will be viewport, resolution will stay at 160x50, meaning that it frees two 80x25 areas (right and bottom). Using those efficiently will allow fast copying to viewport. If the user accepts it and there is enough memory available, Fuchas will use a memory double-buffer for OCX (the UI and drawing library of Fuchas) which so keeps the best advantage of two worlds, with out-of-viewport buffers allowing for fast move using screen copy, and the double-buffer to optimize operations. (In 0.6.2) Fuchas's drawing library is also based on contexts, which are analogous to buffers, in fact it already works with hardware buffers and works perfectly fine without them. Interfaces Fuchas, being modular, is about not fair to have 1 interface. That's why there can be multiple interfaces. Here are the interfaces included: Fushell (basically like OpenOS shell) and Concert. Soon to come will be "Ondroid" (tablet interface), which is a GUI interface, better suited for multi-tasking. For example here is Fushell (warn: old version [4 major releases ago], but still a little representative): I'm not doing a whole documentation here, but basically "pl" lists processes. Install It OpenOS: Just type the following: pastebin run EbHYvEE8 MineOS: Search for the application 'Fuchas Installer'. Install it, launch it, and press Install. (Note that all comments about broken installation below are outdated, and installers has been fixed!) Links: GitHub, Wiki, Progress to next version, And here is how to break the whole Fuchas security system
  2. I made an os from scratch, it is called PlotOS. It can't do currently much (there's only an echo command). Here's some pictures it loads files from the bin folder Update: Added 2 new programs: events (only writes keyboard id-s for testing) testsleep it just sleeps 2 seconds if someone wants to help me develop, just write it to me. Also ideas are accepted, and critism too.
  3. KestrelOS GUI-based, Windows-alike, highly customizable, and safe Operating System for common pourposes What's the major GUI-based OS currently available? The amazing system created by Igor, called MineOS (I'm sure everyone by now knows about it). Igor's system is based on OpenOS, that looks like MacOS and is by itself the most amazing system released yet, with all sorts of programs and even 3D libraries which is mind blowing. So why create yet another GUI-based system? There are several reasons why I decided to take on this journey. First of all, the majority of OS's out there, including MineOS is based upon OpenOS, which makes it a bit streamline and boring, but also unsafe. KestrelOS is made entirely from scratch with it's own libraries, services and style. I wanted to create something new, that would give less freedom than OpenOS (which is KestrelOS's main disadvantage), over a much more secure way to process applications. I also wanted to make KestrelOS as simple as possible, so anyone that is familiar to Windows will recognize most of it's content. How exactly KestrelOS works? KestrelOS implements safety policy, where only so called "managers" have absolute control over the system's event management. The "heart" of the system is a manager called "taskman" (Task Manager). Every other manager is registered to taskman and is a read-only table with functions that cannot be altered once the system has booted up. This restrains a lot of freedom for the user, but also prevents malicious software of changing core functions of the system in order to spy or corrupt data. There is few core managers that will "steer" every process in the system, taskman being the most important one as it is the only library in the entire system that has access to a now unavailable command: computer.pullSignal This forces every application to register itself into taskman in order to be able to hook itself under the heartbeat. What is this weird "heartbeat" you're talking about? Taskman has a loop, in which it listens for any signal. I called it the heartbeat, because it waits only 0.25 of a second to update any tasks hooked under specific processes even if nothing happens. This allows multitasking, or for example updating the clock on the bottom-right of the screen What are the so-called "managers" doing? Those so-called managers are here to serve programs with several system services. For example, there's a manager called "driverman", which loads system drivers, which are usually a single library that communicates with a specified type of component. There's a driver for graphics, which is communicating with the GPU, but uses Igor's amazing double-buffering technique (although I made my own version of it from scratch, but it is very primitive right now) to draw into the screen. Drivers are basically bridges between gpu's, datacards etc. that make sure such a given component is available and return optimized methods to use those components better. Of course, every driver has it's own version, name, description, and can be retrieved manually from driverman using the driver id or name, in case you'd like to implement your own driver and use it. What other features it has? Well, most of the system features are actually the managers which act as the main "pillars" of the system. Here's few of main managers that I remember as of now (as I'm not on my home PC right now, I'm writing from my work PC): driverman - manages drivers fileman - manages mounts for different filesystems and resolves path using mounts taskman - heartbeat of the system, manages processes and tasks assigned to those processes regman - manages system's registry guiman - uses kgraphics driver from driverman to draw complex GUI elements on the screen ... (there's a few more that I can't remember now or that are under development) ... Any concerns/disadvantages? Well, like stated before, it actually restrains quite some core functions to prevent malicious application of accessing those in order to prevent system spying or corruption. This removes quite a lot of freedom, but once you log in and unlock everything, you should be able to edit that manually in the system files if you so desire. Any pictures? Well I'm on my work PC not at home so I can't do any pictures, what I can say is that most of the baseline managers are implement and that I'm working on the GUI now, so don't say hurray yet as I'm working on it. Sorry Release date? Undefined.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.