Re: fixed #! exec bug aka "/dev/fd/3: Bad file descriptor"

2000-03-05 Thread Thomas Bushnell, BSG
Jeff Bailey <[EMAIL PROTECTED]> writes: > That's fine, and I feel quite comfortable doing so. I do remember, > however, when I sent in patches to allow the administrator to only > compile filesystems that (s)he intended to use, the patch was rejected > because you wanted us to make sure that

Re: fixed #! exec bug aka "/dev/fd/3: Bad file descriptor"

2000-02-28 Thread Jeff Bailey
On Mon, Feb 28, 2000 at 03:26:59AM -0500, Roland McGrath wrote: > > Are you beginning to suggest doing partial updates in general to the system? > > I suggest nothing, I just try to provide full information to enable > whatever choices people might want to make. If you are not already > interest

Re: fixed #! exec bug aka "/dev/fd/3: Bad file descriptor"

2000-02-28 Thread Roland McGrath
> Are you beginning to suggest doing partial updates in general to the system? I suggest nothing, I just try to provide full information to enable whatever choices people might want to make. If you are not already interested in building the hurd yourself and doing delicate updates by hand, then

Re: fixed #! exec bug aka "/dev/fd/3: Bad file descriptor"

2000-02-27 Thread Jeff Bailey
On Mon, Feb 28, 2000 at 12:01:03AM -0500, Roland McGrath wrote: > You will need to upgrade both your exec server and your libdiskfs > (including relinking statically-linked filesystems like ext2fs.static) to > get the fixes. If your symptom changes from "Bad file descriptor" to > "(ipc/send) inv

fixed #! exec bug aka "/dev/fd/3: Bad file descriptor"

2000-02-27 Thread Roland McGrath
This is mostly just to let Marcus know there is one thing fewer to worry about. I didn't see a hurd BTS report about this to close, though I know it's been reported here more than once. I've fixed the bugs involving #! execution that most people probably saw as a mysterious error like "/dev/fd/3