[Rant] Microsoft extend their monopolistic behaviours (again) | ANN.lu |
Posted on 11-Aug-2002 13:33 GMT by Cyberwlf | 56 comments View flat View list |
Microsoft have cracked down on retailers trying to sell alternate OS's when they sign a contract to sell Windoze. (This theoretically effecting people selling Amithlon pre-installed, or the likes). Essentially saying... :
(from slashdot.org) "Some Sys Admin sent in an email that he got from Dell which basically says Microsoft will no longer allow Dell to sell PCs without an operating system. " - But if you think this was only Dell, the wording seems to effect all retailers, read article for more information: http://slashdot.org/article.pl?sid=02/08/10/1420208.
|
|
List of all comments to this article |
Microsoft extend their monopolistic behaviours (again) : Comment 48 of 56 | ANN.lu |
Posted by Kjetil on 14-Aug-2002 11:35 GMT | In reply to Comment 47 (DaveW): Okey getting in to details,
Linux 68k where made on i386 in 1995, linux is very flexible berceuse it’s open source, so when ever an GCC get updated the binaries follows, as most programs are open source or GPL, the first linux kernel was made in 1992, in 1992/1993 the first Pentium’s where made.
The linux system it self is flexible even if you break binary complicity it is easy to create new ones, just recompile, on the linux system arguments are pasted using the stack,
On the AmigaOS where made back in 1980’s the first 68000 cpu’s where never hade MMU, so the OS where made like this when pasting arguments to then exec, you basicly use the D0 to D7 registers, A7 is used for stack, not to be touched, A1 is used mostly to paste the address of the paste to read or modified, this do not correspond to memory protections by it self, the 2en ting is the hole Arexx stuff is based on Exec Communication ports, Exec communications works in the same way it allows commands to sent back and fort between programs address is provided by program and args are written in that address space the program is not aware of if an memory allocation is going to shared or not , okey so you say way not just protect the program space, well no most programs coded in Assembler use reserve memory inside that space as well, so it can be read only, and if that address is shared with an otter program it will brake MP,
There exists and MMU table where you can define if memory is to be Read/Write, and so on, programs on the amiga that enforce programs with MMU, do not full protect the system, and it slows down the hole program as it hits the subroutines activated by the MMU, many times during execution. |
|
List of all comments to this article (continued) |
|
- User Menu
-
- About ANN archives
- The ANN archives is powered by #AmigaZeux. It was updated daily (news last: 22-Oct-2004; comments last: 18-May-2005).
ANN.lu was created, previously owned and maintained by Christian Kemp, www.ckemp.com.
- Contribute
- Not possible at this time!
- Search ANN archives
- Advanced search
- Hosting
- ANN.lu was hosted by Dreamhost. Sign up through this link, mention "ckemp" as referrer and he will get a 10% commission on any account you purchase.
Please show your appreciation for any past, present and future work on ANN.lu by making a contribution via PayPal.
|