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
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
> OK, a small step for you, but a giant leap for me.
Your leaping is just fine. :-)
> # gdb /hurd/proc 95
> GNU gdb 19990928
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute
I have observed that ncftp (same binary which worked on the old pfinet)
can no longer do useful things like 'ls' and 'get'. Control-channel
stuff works fine. The ftp from marcus' tarball still works just fine.
When I type 'ls', it gives me the message saying that it will try it, and
then it
On Sun, Feb 27, 2000 at 10:02:01AM +, Chris Lingard wrote:
> > Firstly, let me verify what we are dealing with. It was only hurd that you
> > recompiled with the new gcc, not glibc, right?
FWIW, my Hurds have been running Glibcs compiled with 2.95.2 since late
November/early December. I ha
> Firstly, let me verify what we are dealing with. It was only hurd that you
> recompiled with the new gcc, not glibc, right?
Yes, just compiling the Hurd. The source that I have been using is fairly old; so
last Friday I had the chance to download a completely fresh version. Have the
standard