Welcome, Guest. Please login or register.

Author Topic: OpenSource for Amiga.  (Read 10609 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: OpenSource for Amiga.
« on: May 29, 2003, 06:02:23 PM »
@Tickly

Yes, all that is in the feature list for OS4, but
if and when all that will be actually included
is another question.

Latest quotes from Hyperion suggested that both
AmigaInput and MP may not make it into the 1st release,
and even if, the 1st isn't really important or
a "biggie", while the 2nd isn't really possible without
breaking lots of older apps.

Same goes for SMP (one that goes beyound what
we had with PuP/WOS). AOS is just not cut out for
stuff like that.

RoadShow does seem to become a fine TCP_stack, but
in the end it is only getting online that counts,
and I'm sure AROS will manage that someday.

Docks are many and plentifull, some even better than
AmiDock (which ain't bad). Get one ported to AROS,
problem solved.

To put it simple : There is NOTHING breathtaking
in the OS4-featurelist (or in the MOS one), these
list just tell what a OS needs as absloute minimum
these days.
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: OpenSource for Amiga.
« Reply #1 on: May 29, 2003, 06:20:18 PM »
@Tickly

O.k. this is OT, I admit it ;-)

But ...
The reason why you CAN'T have anything worth the
name "memory-protection" on AOS lies within
the AOS-API (message-ports and such), and as
long as these APIs are in use you can't protect
the kernel, and you can't protect native Apps
(which still use that API).

Replacing that API with something MP-friendly
is what the Q-Box in MOS is (planned) for, and
sooner or later Hyperion will also have to introduce
new APIs, but as long as you still run old SW,
you won't be able to fully protect the kernel.
 
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else