Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: obscurepanic on May 26, 2009, 02:18:04 AM
-
I found this page.
http://www.osnews.com/story/16543/A_Very_Critical_Look_at_OS_Re-creation_Projects/page5/
It says In 1985, the Amiga was, conceptually, a Unix-like workstation that could run on custom, inexpensive hardware while still offering cutting-edge multimedia capabilities.
I only have a very basic grasp on what Unix(-like) is.
Is AmigaOS that we know of really a Unix-like operating system?
I wonder.
-
It was Unix-like in the sense that it can multitask. The differences between them are much greater than the similarities. Most Unix implementations have trouble with desktop use and graphics acceleration and are better served on a server. The few that were useful as workstations typically used proprietary graphics chips that were not at all well-suited for home use.
-
Well, I think there might be more similarities, but of course, if I'm wrong, feel free to correct me....
Both Amiga and Unix can be controlled entirely from the command prompt, and that the command prompt is always there, even if you can't see it...
the ' . ' and '..' commands to go up one level, and to the root directory respectively... although in AmigaDos it's '/' and ':'
Both have more types of file protection bits than windows (I believe)
And there is more, I'm sure .... hmm, the ixemul.library ...
The Amiga 3000UX won 'Best in Show' at the UnixWorld show, does that count?
-
check here (http://lkml.indiana.edu/hypermail/linux/kernel/9907.1/0381.html).
I think also the interprocess communication stuff is similar.
-
check here (http://lkml.indiana.edu/hypermail/linux/kernel/9907.1/0381.html).
Had to stop reading after the first line there :) or perhaps he meant to write AmigaDOS?
-
Well, I think there might be more similarities, but of course, if I'm wrong, feel free to correct me....
Both Amiga and Unix can be controlled entirely from the command prompt, and that the command prompt is always there, even if you can't see it...
the ' . ' and '..' commands to go up one level, and to the root directory respectively... although in AmigaDos it's '/' and ':'
Both have more types of file protection bits than windows (I believe)
In Unix, the '.' points to the current directory and '..' points to the parent directory. '/' points to the root directory. The mount points of additional drives are often in a /mnt/ or /media/ directory while on AmigaDOS, each volume has its own device name and volume name. There aren't many similarities between the file systems of the two operating systems.
-
AmigaOS has many elements inspired by UNIX, not so strange considering what systems it was developed on. AmigaOS also has alot in common with VMS, allthough I'll gladly have AmigaShell over DCL any day :)
-
Tripos, the Roots of AmigaDOS:
http://www.pagetable.com/?p=193
-
Tripos, the Roots of AmigaDOS:
http://www.pagetable.com/?p=193
Trip-OS.
Heyya, provide it with an anti and call it somma, who would mind.
:-))) Quite an OS here it seems...
:-))
-
Amiga 3000UX came shipped with UNIX instead of AmigaDOS... So it's simularity to UNIX was that it was actually running UNIX:
http://en.wikipedia.org/wiki/Amiga_3000UX
-
kingcon with unixdirs feels very bash-like... but bottom line is amiga is more fun.
-
Both have more types of file protection bits than windows (I believe)
In Windows, securable objects--files, pipes, devices, processes, desktops, registry keys, et al--have a 32-bit access mask, so that's 4,294,967,296 possible "protection bits." ;-) They're not all implemented for most objects, of course, but a cruel and ruthless designer could implement them if they wanted.
-
At the Amiga DOS level, a little bit. The Amiga OS is vastly simpler OS than UNIX and is a single user, multi tasking system while UNIX is a multi user, multi tasking system. File permisions and security, user accounts and logons aren't necessary in a system designed for a single user and weren't implimented in Amiga OS--part of it's charm. Amiga OS was written by programmers well versed in UNIX and it's command prompt structure, although much simpler, follows the UNIX model. It also shows some UNIX derivation in the way it is organized but once again, it is much simpler.
In a more genaral way, it is like UNIX in that, if you know the system, you know where everything is and should be and this makes it very easy to troubleshoot and maintain. I can't say this about any version of Windows since 3.1.
What is really special to Amiga OS is Intuition. It is unique amoung GUIs.
And among OSs, the only only one I've ever played with that ever reminded me of Amiga OS--in terms of sheer multitasking feel at least--was IBMs OS/2 which also used the Rexx programming language and had similar scripting capabilities to Amiga OS.
-
Amiga 3000UX came shipped with UNIX instead of AmigaDOS... So it's simularity to UNIX was that it was actually running UNIX:
http://en.wikipedia.org/wiki/Amiga_3000UX
Well, yes, but the 3000UX ran AMIX System 5 Release 4 AND AmigaOS 2.1 ... (I'm guessing AmigOS was selected from the Early Startup)
@trev: Ugggh! I hope no one ever tries to use all 4,294,967,296 possible 'protection bits' in Windows... man, and I thought the registry was a mess...
As for the rest, well I did say to correct me if I'm wrong :) That'll teach me to post after a few drinks... lol...
-
Yeah, I think the short answer is that AmigaOS isn't very UNIX-like at all: there's no separation of kernel (privileged) and user (unprivileged) spaces, and there are clear differences between file and device I/O.
-
Well, yes, but the 3000UX ran AMIX System 5 Release 4 AND AmigaOS 2.1 ... (I'm guessing AmigOS was selected from the Early Startup)
@trev: Ugggh! I hope no one ever tries to use all 4,294,967,296 possible 'protection bits' in Windows... man, and I thought the registry was a mess...
As for the rest, well I did say to correct me if I'm wrong :) That'll teach me to post after a few drinks... lol...
It's 32-bit. This gives a possible 4,294,967,296 possible combinations of those bits.
Lets look at Unix which uses at least 12 bits, which are divided thusly:
Special Modes | Owner | Group | Others
--------------+--------+--------+-----------
U-G-S | R-W-X | R-W-X | R-W-X
--------------+--------+--------+-----------
1-1-1 | 1-1-1 | 1-1-1 | 1-1-1
These allow up to 4096 different combinations, and it's not at all hard to rememer any of them. Each of the Owner, Group and Others permissions uses 3 bits, 1 for Read permission, 1 for Write permission and 1 for Execute permission.
In usual binary fashion this makes 8 combinations for the Owner, 8 for the Group and 8 for the Others. Another 8 for special modes I won't discuss.
Permission | Binary | Decimal
-------------+--------+------------
- - - | 000 | 0
-------------+--------+------------
- - x + 001 | 1
-------------+--------+------------
- w - | 010 | 2
-------------+--------+------------
- w x | 011 | 3
-------------+--------+------------
r - - | 100 | 4
-------------+--------+------------
r - x | 101 | 5
-------------+--------+------------
r w - | 110 | 6
-------------+--------+------------
r w x | 111 | 7
-------------+--------+------------
(You probably wouldn't use the first 4.)
Since the Owner, Group and Others sections are effectively the same permissions applied to different objects, you only have to remember 3 different permissions (R, W or X), but they can be applied to 9-bits of the permissions field, capable of being applied 512 different ways, some of which won't be used. So you remember 3 permission values, and 3 special permission values. So you remember 6 different permissions, and apply them in a possible 4096 combinations, none of which you have to memorize. You simply apply the 6 you know, in the pattern you want.
Don't let the 32-bit field scare you. It's going to be no worse than remembering 32 different permissions at the most.
Unix probably uses more than 12 bits, but this is all the user is usually exposed to.
-
Well, I think there might be more similarities, but of course, if I'm wrong, feel free to correct me....
Both Amiga and Unix can be controlled entirely from the command prompt, and that the command prompt is always there, even if you can't see it...
the ' . ' and '..' commands to go up one level, and to the root directory respectively... although in AmigaDos it's '/' and ':'
Both have more types of file protection bits than windows (I believe)
And there is more, I'm sure .... hmm, the ixemul.library ...
The Amiga 3000UX won 'Best in Show' at the UnixWorld show, does that count?
Well, IIRC all (or at least most) of the DOS commands are the same in that sense, that e.g. in AmigaDOS you say "copy", while in Unix you use the abbrevation "cp" (that you could also use in e.g. Commodore Basic v4.0 instead of the full commands) - the syntax is the same.
I remember that back in 1989-1992 during my CAD studies - where I learned UNIX - I found it quite easy to learn the UNIX commands and their syntax because of the similarity to AmigaDOS.
As far as I remember Unix even had a directory structure similar to the Amigas directory structure back then - but since my CAD studies I had no root access on a UNIX machine to verify this...
Root Directory - that was one of the differences I remember and is related to the multiuser capability of UNIX that the Amiga does not have by standard (I know that a MultiUserFileSystem (MUFS) exists for PFS3, but haven't testet it so far).
I think only a person with admin rights had access to the root directory, as the system resides there.
-
Don't let the 32-bit field scare you. It's going to be no worse than remembering 32 different permissions at the most.
But that's so much less fun. ;-) In practice, the lower 16-bits of the Windows access mask are used as a bit field for object-specific rights, and the next 8 bits are used for standard rights: delete, read permissions, write permissions, write owner, and synchronize are implemented. So that's 21 possible permissions, 16 of them object-specific. File system objects use 9 of the 16 object-specific bits.
Windows also supports generic read, write, and execute permissions. You can emulate UNIX-style file system permissions (and do when using Services for UNIX or POSIX APIs) by setting an object's owner and group and assigning permissions to CREATOR OWNER, CREATOR GROUP, and Everyone. With Microsoft's NFS server, you can continue to use full discretionary access control lists as well, but only the owner, group, and everyone permissions will be reflected in UNIX directory listings.
Many UNIX variants provide some form of discretionary access control lists, but most administrators are loathe to implement them, despite the flexibility they provide.
-
Wow, there are so many things to know about UNIX and Amiga. Perhaps we have a lot to learn about everything to understand Amiga. No worries, this is still a good motivation to understand Amiga.
In another thread (http://www.amiga.org/forums/showthread.php?t=41479&page=2), AmigaMan said something like
You will also need to rewrite kickstart, but that had to be done anyway. Kickstart is unix based, so start from there with Amiga in mind.
Thank you, AmigaMan. :)
-
Wow, there are so many things to know about UNIX and Amiga. Perhaps we have a lot to learn about everything to understand Amiga. No worries, this is still a good motivation to understand Amiga.
In another thread (http://www.amiga.org/forums/showthread.php?t=41479&page=2), AmigaMan said something like
(No need to repeat that)
Thank you, AmigaMan. :)
Thank you indeed... you don't actually believe that? :)
-
Well, I think there might be more similarities, but of course, if
Both have more types of file protection bits than windows (I believe)
NT based Windows systems have more "protection bits" than unix even, let alone amiga.
*edit*
Not that my post offered anything new in this thread :o