Re: Removing the `iopl' device and i/o emulation facility

I don't know about the vm86 stuff, which probably hasn't worked in years. The iopl_emulate stuff seems to be special hacks for dosemu. The other thing emulate_io did was the iopb check stuff that makes the iopl device work. ___ Bug-hurd mailing list Bu

Re: Removing the `iopl' device and i/o emulation facility

Hi, Thomas Schwinge, le Sun 01 Apr 2007 22:17:37 +0200, a écrit : > I'm working towards integrating the OskitMach i/o permissions interface > (i386_io_perm_create, i386_io_perm_modify) into GNU Mach and again > started some spring-cleaning, removing for now the `iopl' device and the > i/o emulatio

Removing the `iopl' device and i/o emulation facility

Hello! I'm working towards integrating the OskitMach i/o permissions interface (i386_io_perm_create, i386_io_perm_modify) into GNU Mach and again started some spring-cleaning, removing for now the `iopl' device and the i/o emulation facility. What might the latter have been useful for? Here is

Google SoC application updated (Framework for Default Server Overriding in Hurd)

Dear SoC mentors, I am quite dissatisfied with the original application. So, I further investigated this project and Hurd in these days, and greately revised my application to include many new ideas. I beg you to rate my application based on the new version, or at least read it and provide your

[bug #19479] Using a buggy trivfs translator to kill you shell

URL: Summary: Using a buggy trivfs translator to kill you shell Project: The GNU Hurd Submitted by: tschwinge Submitted on: Sunday 04/01/07 at 15:15 Category: Hurd Sev