From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a050906042616623feb@mail.gmail.com>
Date: Tue,  6 Sep 2005 07:26:44 -0400
From: Russ Cox <rsc@swtch.com>
To: 9fans <9fans@cse.psu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: [9fans] errstr
Topicbox-Message-UUID: 84317fec-ead0-11e9-9d60-3106f5b1d025

I think I've restored the file name-related error messages
to their original 9P2000 usefulness.  Due to a mistake on
my part two years ago, they'd broken and were always
showing the full path, even if the error happened much
earlier.  For example, if the directory "does" does not exist,
this is a bad error:

=09% >does/not/exist
=09does/not/exist: rc: can't open: 'does/not/exist' file does not exist
=09%=20

In contrast, this is a good error:

=09% >does/not/exist
=09does/not/exist: rc: can't open: 'does' file does not exist
=09%=20

There are new kernels on sources as of Saturday that
should have good error messages.  If you see any errors=20
that don't show the right path:

  - check that you're running a new kernel=20
    (ls -l '#c/cons' and see that the date is recent)=20
  - if ramfs is involved, check that it's also new
    (ls -l /386/bin/ramfs)=20

and then mail me.

Thanks.
Russ