ldd misreports some apps as not dynamic

2001-10-16 Thread Jeff Bailey
The symptom is that executables produced on my system show up as: jbailey@hurd:~/test$ ldd main not a dynamic executable However, a few things suggest that it really is: jbailey@hurd:~/test$ file main main: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked (uses sha

Re: I/O permission control in OSKit-Mach

2001-10-16 Thread Marcus Brinkmann
On Tue, Oct 16, 2001 at 11:06:53AM +, Adam Olsen wrote: > I can't > think of any reason that we'd want segments larger than the smallest > value we can manage. Simplicity. The smallest value we can handle is a bit, and this is the bitmap we have already. However, instead searching for bits

Re: I/O permission control in OSKit-Mach

2001-10-16 Thread Adam Olsen
On Tue, Oct 16, 2001 at 12:09:07PM +0200, Marcus Brinkmann wrote: > On Tue, Oct 16, 2001 at 05:48:02AM +, Adam Olsen wrote: > > 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, whi

Re: I/O permission control in OSKit-Mach

2001-10-16 Thread Marcus Brinkmann
On Tue, Oct 16, 2001 at 12:09:07PM +0200, Marcus Brinkmann wrote: > When you task switch, the segment bit maps are OR'ed, and only those segments > are copied. The actual number of segments (and thus their length) can be > tuned, 128, 256, 512 and 1024 are convenient values. Anybody has an idea

Re: I/O permission control in OSKit-Mach

2001-10-16 Thread Marcus Brinkmann
On Tue, Oct 16, 2001 at 05:48:02AM +, Adam Olsen wrote: > 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