🚀 go-pugleaf

iialan@iifeak.swan.ac.uk (Alan Cox) wrote:
>In article <3vqvh9$9c6@nyheter.chalmers.se> Martin Nisshagen <d4nisse> writes:
>>runs in onother process with higher priority. In thread-libs then scheduling
>>of the threads are done seperatly within each own process, this is not possible.
>>Having kernel threads also lets You easily implement an efficient way of using
>>several CPU:s in an SMP machine without adding too much system overhead.
>>
>>Besides this the Amiga also lacks the possibilty to handle realtime=03like
>>prcosses in an efficient way. Both Solaris, NT and VMS has much better
>>support for this.
>
>The amiga is both threaded (a process is just a glorified thread and almost
>everything is but a thread) and has hard priorities.

The difference is that You only need to do a context switch (without the time
to change the memory it uses) then changing threads within the same process.

>>security, all of this OS:es also includes very stable journal based
>>filesystems who tracks all transactions in the OS. It's almost
>>impossible to corrupt this filesystems!
>
>Journal based file systems merely make it slightly harder to corrupt. They
>make it much faster to check on a restart after a crash.

Yes, it checks the system _very_ fast then You for example boot NT with a
journal based file system (NTFS). But it's also very stable. I have tried
to crash it by doing a lot of disk operations (a process who creates nested
subdirs recursive, moving big dicretories from one disk to another, saving
a big word document) at the same time and in the middle of them pulling the
plug to the computer. Repeated this several times witout _any_ damage to
the filesystem! This was not the case with FAT or HPFS.

m a r t i n  n

-- 
mts@cd.chalmers.se 
http://www.cd.chalmers.se/~mts
mts @ IRC (on #MTS)