If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#51
|
|||
|
|||
Interesting: Is IBM considering an OS/2 redo?
On Apr 18, 3:56*am, Jonathan de Boyne Pollard J.deBoynePollard-
wrote: One thing that I know xe did write was a call to open-source SOM. *Now that's something that would be very helpful. *Yes, NOM exists, but from what I'm told it isn't binary compatible with SOM, which rather misses one of the major points of using SOM. I did not recognize these acronyms, but after some careful Googling, I found this: http://advice.cio.com/esther_schindl...ttle_som_thing SOM and DSOM are the System Object Model and the Distributed System Object Model from IBM, and NOM is the Netlabs Object Model. (The article quoted doesn't mention NOM, and the reasons it gives for open-sourcing SOM are such that it would seem, though, that NOM could also serve those purposes.) Oh, my... by an amazing coincidence (???) Esther Schindler was the author of that article. John Savard |
#52
|
|||
|
|||
Far and near pointers on the 80286 and later
Terje Mathisen wrote:
I.e. a driver had full-speed access, but only to those hardware resources the OS would agree to give it If it has access to DMA registers, and most PCI device drivers must have it in order to work, then it can easily wipe out the kernel and replace it with any code it wishes. so a buggy driver had less chance of messing up some unrelated hardware/software subsystem. Direct access to physical memory == no security, no matter which protection ring it runs at. Best regards Piotr Wyderski |
#53
|
|||
|
|||
Far and near pointers on the 80286 and later
Piotr Wyderski wrote:
Terje Mathisen wrote: so a buggy driver had less chance of messing up some unrelated hardware/software subsystem. Direct access to physical memory == no security, no matter which protection ring it runs at. Afair the key idea was to help driver writers catch bugs, not to guarantee security which is effectively impossible for anything that can access hw directly. Terje -- - Terje.Mathisen at tmsw.no "almost all programming can be viewed as an exercise in caching" |
#54
|
|||
|
|||
Far and near pointers on the 80286 and later
These quotes must be from posts missed or expired on the system I use, what was the "x86_64 doesn't even support segmentation" in reference to, or is this confusion between x86_64 and ia64 support..... 'Term papers' (http://www.ghostpapers.com/) -- termpapers |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
80286 | Gaijinco | Intel | 3 | November 3rd 06 10:06 PM |
80286 | Gaijinco | Intel | 3 | October 31st 06 10:35 PM |
USB 2.0 enclosure pointers | Ken K | Storage & Hardrives | 4 | May 9th 05 11:39 PM |
Geforce 5700 pointers | Matt | Nvidia Videocards | 1 | February 16th 05 01:05 PM |
K8V SE Deluxe bios guide, pointers tweaks.... | Gordon Scott | Asus Motherboards | 5 | December 18th 04 08:50 AM |