Re: I/O permission control in OSKit-Mach

2001-10-15 Thread Adam Olsen
On Tue, Oct 16, 2001 at 04:16:42AM +0200, Marcus Brinkmann wrote: > A task requesting some I/O permission will get a full blown 8192 bytes large > bitmap, which is copied in the processor TSS at every switch to the task. > (Linux by default only uses a half bitmap, and provides a full one at > req

Re: I/O permission control in OSKit-Mach

2001-10-15 Thread Marcus Brinkmann
On Tue, Oct 16, 2001 at 04:16:42AM +0200, Marcus Brinkmann wrote: > /* Request a new port IO_PERM that represents the capability to access >the I/O ports [FROM; TO] directly. MASTER_PORT is the master device port. >The function returns KERN_INVALID_ARGUMENT if TARGET_TASK is not a task, >

I/O permission control in OSKit-Mach

2001-10-15 Thread Marcus Brinkmann
Hi, here is a patch to implement I/O permission control in OSKit-Mach. What do you get? Two new interfaces: /* Request a new port IO_PERM that represents the capability to access the I/O ports [FROM; TO] directly. MASTER_PORT is the master device port. The function retu

Re: TSS switching

2001-10-15 Thread Roland McGrath
Sounds about right to me. Do it before base_cpu_load, which reloads the tss anyway. It falls appropriately into the various *_init calls right there. ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd

Re: TSS switching

2001-10-15 Thread Marcus Brinkmann
On Fri, Oct 12, 2001 at 04:21:28PM -0400, Roland McGrath wrote: > It's easy enough to either have a different ktss and switch to it, or just > to link-time override the base_tss definition (the oskit puts it in a > separate file to make this easy). I think link-time is better, and I am working th

Re: OSKit-Mach's kernel command line

2001-10-15 Thread Roland McGrath
> With the new boot code, oskit's environment searched for the root variable. > You have to put a "--" after the "root=", i.e. > > kernel /boot/oskit-mach.gz root=part:1:device:hd0 -- > > If you don't do that, the "root=" variable is in the argc and argv > variables. It's explained in the commen

(no subject)

2001-10-15 Thread infoman
DATA From: infoman To: Date: Mon, 15 Oct 2001 09:40:23 PDT Subject: FINANCIAL SERVICES STOCK - UNDERVALUED? MIME-Version: 1.0 Content-Type: text/html; charset=us-ascii Moreno1 Regarding  AMSE: http://www.americassenior.com/stratos3.PDF";>http://www.americassenior.com/stratos3.PDF A "Bu

Re: About TODO

2001-10-15 Thread Marcus Brinkmann
On Mon, Oct 15, 2001 at 10:17:53AM -0100, atle wrote: > > I just finished some work and got some time to spare ... is NFS still in the >TODO-list? There is nfsd and nfs, the former is a regular nfs server which should implement the Hurdish extensions like translators. The latter is an nfs clie

Re: About TODO

2001-10-15 Thread Jeff Bailey
On Mon, Oct 15, 2001 at 10:17:53AM -0100, atle wrote: > I just finished some work and got some time to spare ... is NFS > still in the TODO-list? NFS runs, but it is not perfect. I use it to move files back and forth between GNU/Hurd and GNU/Linux, but I cannot reliably use it to build packages

Re: SO_LINGER (ugh)

2001-10-15 Thread Marcus Brinkmann
On Mon, Oct 15, 2001 at 12:56:20AM -0400, Roland McGrath wrote: > I agree with your analysis. I think your current behavior is probably best. Ok. > As I read the Linux implementation, a > process dying (even by SIGKILL) will just stick around and block until the > (unbounded) linger timeout ex

About TODO

2001-10-15 Thread atle
I just finished some work and got some time to spare ... is NFS still in the TODO-list? I saw in the latest tarball that 'Now there is an nfsd' - but examining the code gave some weird impressions of old age? Was it Thomas Bushnell, 1993? Not that I think Thomas is old, but I think his code is