[OS] V2_OS - Anyone tried this?

S

Steven Burn

Looks interesting, but am a little hesitant...... anyone tried it?

http://v2os.v2.nl/

What is V2_OS?

The goal of V2_OS first started as making a stunningly fast operating system
for video processing. This goal held for all versions until 0.70, where a
major redesign was forced. The 0.70 versions are completely different, still
aimed for maximal performance, though. These are the major features of V2_OS
0.70:

- Single addressing space (SAS), this was to avoid far jumps in the code.
Far jumps means loading 8 bytes for a single jump to another position in
code. Using SAS we more or less force the coders to use shorter jumps (4
bytes to load for one jump), which makes modules smaller.

- It is oriented towards the Object Oriented Programming (OOP), which makes
even your assembly code able to use OOP.

- It is not using any kind of memory protection from start, which enhances
the perfomance compared to other systems. This is because the CPU will not
have to check for permissions.

- V2_OS 0.70 uses a static call table, a table with pointer to commands.
This means that you can easily replace system functions with your own system
functions. You can, for example, replace the malloc command, which reserves
memory for your application, with a new memory allocator which you have
coded yourself - maybe with some extra features? This change then instantly
takes effect for all running applications.

Why V2_OS?

There are many reasons of why V2_OS is worth developing for. V2_OS has many
features to offer to you. Some of them are not yet implented, but our goal
is, to have the ultimate OS, usable for anything, since everything is
replaceable and extendable.

User interface

First of all, which may be interesting for the regular user, comes the user
interface. An user interface, often abbrivated to UI, is the part which lets
you interact with the computer. Commonly used in new operating systems, the
Graphical UI, often abbrivated as GUI, is used. You recognize a GUI through
its windows, buttons and neat pictures.

In V2_OS, the UI does not always mean a graphical interface. It can as well
be a synthetic voice from the computer communicating with you. You hold your
microphone, and the computer holds its speakers. This can be a great feature
for disabled or blind people.

Actually, the UI can be anything allowing communication between the user and
the computer.

Modularity

For a programmer, it may sometimes be nice to be able to add or replace
features in the kernel. In V2_OS this is highly possible. Even without
reboots! Any feature is hotswapable in th kernel. In runtime or at compile
time. This is all done through a Static call table. The static call table is
a table, which always lies at the same place in memory. It contains pointers
to functions provided by the kernel. Due to the design of V2_OS any
application, program or module can replace such pointer to point at its own
function for providing the same action, or perhaps blocking it.

Fully trusted single addressing space enviroment

This may sound a bit weird to the one not so familliar with the Intel x86
architecture. What it basicly means, is that any appliation, module or
program is allowed to do anything. This is the main reason of why V2_OS is
so blindingly fast. By letting all components do anything, the CPU does not
have to check for permissions each time a "Dangerous" instruction goes
through it. This saves lots of time in the long run, but also increases the
risk for crashes and such. That's why we need you to be well-informed about
it.

100% optimized assembly code

The last, but not the worst reason of contributing and using V2_OS is its
choice of programming language. Assembly language is as close to machine
code you can get without writing the machine code yourself. This means, we
have taken control of every little instruction your machine will perform,
and every little instruction is handled with care. When coding V2_OS every
instruction to the CPU is handled with care, and added only if it is really
nessescary.

This page applies for V2_OS 0.70 and newer only. Classic versions do not
offer the same features for modularity, nor do they provide a good, flexible
user interface.

--

Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!
 
G

Gabriele Neukam

On that special day, Steven Burn, ([email protected]) said...

- It is not using any kind of memory protection from start, which enhances
the perfomance compared to other systems. This is because the CPU will not
have to check for permissions. ....
For a programmer, it may sometimes be nice to be able to add or replace
features in the kernel. In V2_OS this is highly possible. Even without
reboots! Any feature is hotswapable in th kernel. In runtime or at compile
time. This is all done through a Static call table. The static call table is
a table, which always lies at the same place in memory.

So I can re-program the kernel with everything without any checks and
questions, and have it crash deliberately, or even run and spread a
worm?

Gabriele Neukam

(e-mail address removed)
 
S

Steven Burn

Gabriele Neukam said:
So I can re-program the kernel with everything without any checks and
questions, and have it crash deliberately, or even run and spread a
worm?

I would imagine they would check any modifications sent to them, prior to
publishing them ;o)

--

Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!
 
G

Gabriele Neukam

On that special day, Steven Burn, ([email protected]) said...
I would imagine they would check any modifications sent to them, prior to
publishing them ;o)

Heck, a genuine windows worm doesn't ask Microsoft, Redmond, for
propagation, either.


Something's wrong with your sig delimiter. Take heed that the trailing
blank won't get removed.


Gabriele Neukam

(e-mail address removed)
 
S

Steven Burn

Gabriele Neukam said:
Heck, a genuine windows worm doesn't ask Microsoft, Redmond, for
propagation, either.

But Windows isn't open source ;o), V2_OS is open source, and all
modifications are cleared by the V2_OS before being made official ;o)
Something's wrong with your sig delimiter. Take heed that the trailing
blank won't get removed.

I can't seem to modify the sig del in OE (or atleast, can't find an option
to do so), so am adding the extra space manually to each post (as I've been
previously asked to do).

--

Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!
 
G

Gabriele Neukam

On that special day, Steven Burn, ([email protected]) said...
I can't seem to modify the sig del in OE (or atleast, can't find an option
to do so), so am adding the extra space manually to each post (as I've been
previously asked to do).

I am very sorry to tell you, that OE does remove it (the trailing blank)
on its own behalf, if it isn't the most recent version, when MS finally
woke up and removed this "feature".


Gabriele Neukam

(e-mail address removed)
 
J

jo

Steven said:
I can't seem to modify the sig del in OE (or atleast, can't find an option
to do so), so am adding the extra space manually to each post (as I've been
previously asked to do).

Doesn't matter. OE still strips it on send.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top