Classic AmigaOS On Modern Hardware - A Critical Analysis

[Boot_WB]

What do you recommend I upgrade it to then? You think a less costly accelerator is more cost effective?

Any accelerator for the A3000/4000 slot which allows ram expansion is going to cost you.
Imho the Cyberstorm mk3 is the sweet spot - you still get the 40MB/s scsi bus, the fast and wide ram bus, and the 68060, but without the extra complication and heat production of the 604e + associated components.

Also honestly I'm not too keen on the fact MorphOS barely utilizes the hardware, is 32-bit only and has no SMP support. While none of the other Amiga NG OSes seem to support this I'm honestly thinking my money for computing is better spent elsewhere than on an NG Amiga solution.

All true*, especially considering the unused processing power of the quad G5. For me, a single processor of a dual 2.7GHz G5 should be plenty enough for now though (ideal machine would be a single processor 2.7, but I'm not sure the DP G5 logicboard willl even operate with only one processor module present).

* Depends how you define 'the hardware.' Driver support for onboard peripherals is mostly complete now - certainly for most of the the G4 range of models/form factors, not sure about the G5 onboard goodies, as mine is still sat on the side awaiting a coolant change before installing MorphOS.

It'd be nice to be able to have more Ram available, but it's only Odyssey that really eats that up for me.

[Boot_WB]

that sounds worse than in the amiga community...

Indeed. :laughing:

[Boot_WB]

As a result I have a transparent, unified filesystem that goes where I want it to go. Now, correct me if I'm wrong, but as to my understanding AmigaOS doesn't have this concept.

On Amiga operating sytems we have the opposite - anything can be mounted at the top of the filesystem for easy access via assigns. Much more user-friendly imho than dealing with Unix paths. Rather than burrowing down into a path for everything, any directory can be addressed at the top level of the filesystem by creating an assign.

Assigns can also refer to multiple locations. The 'c' assign is an example of this (speaking form a MorphOS standpoint). The primary location is sys:c, however it is also a pseudonym for the location sys:morphos/c.

Assigns addressing multiple locations are prioritised in the order they are created (In this case sys:c is created first, then mossys:c added).
Consequently the command:
c:foobar
will first search the location
sys:c
for the file 'foobar'. If the file is not found, the location
sys:morphos/c
will then be searched

We also have softlinks which essentially operate the same as mountpoints, so wrt dos paths anything can be transparently addressed from anywhere.

[Boot_WB]

Eh I don't consider it burrowing at all. Plus symbolic links are horribly inflexible. I prefer everything to be under a unified filesystem, but I guess I'm the one over here drinking green tea while everyone else is drinking black tea or something like that.

What I mean by that is that if I'm at the command line, I don't need to know where a directory is in the filesystem to be able to access it. As long as it has an assign, I can just type "foobar:" and I'm there.