9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] proposed stat(1) - input requested
Date: Sun,  2 Nov 2003 15:46:50 +0200	[thread overview]
Message-ID: <f27d2292563520a2008b952aa5b8bda7@proxima.alt.za> (raw)

I hacked Dan Cross's "walk.c" in the style of Lunix's date(1) -
actually a lot more like *BSD's stat(1), which I only discovered
recently - so that it would display file properties subject to a
format pattern, while at the same time allowing directory descent and
all those useful if sacrilegious things.

I borrowed ape's strftime(2) as well - as an additional insult - and
the extremely raw and undocumented result is now on my web site:
<http://wow.proxima.alt.za/src/stat/>.

The reason I'm posting it well ahead of maturity is that there are
innumerable arbitrary decisions that were made on the spur of the
moment and some feedback from users would avoid continuing on a
slippery downwards slope.

There are two major flaws (not counting the actual existence of the
program, I will ignore criticism on that score :-) that I can think
of:

1.  It processes the directory after the contents, which is both
unexpected and has an unpleasant side effect: the details of a
directory aren't output if the permissions to descend the directory
are not granted.  I'm sure I can fix this easily, but it's not urgent.

2.  It is limited to the Plan 9 namespace, whereas it would be nice if
it recognised the properties of foreign filesystems.  It is this last
feature that made me seek the help of the community: I know that some
foreign file attributes are already accounted for, but perhaps they
are not conveyed over 9P2000 or whatever (I'm thinking of u9fs, for
example, and dossrv).  It would be useful to tidy these up.  I can't
seem to find the details, although I recall reading them somewhere,
possibly in the 9P2000 documentation.

Largely, stat(1) already is flexible enough to look like the user
wishes it to look, but the aesthetics could doubtlessly be improved
radically with some lateral thinking.  I'm not possessive, please feel
free to submit the most extreme alterations and I'll only reject them
if I have a good explanation for doing so.

++L

PS: No, it does not do web browsing :-)



                 reply	other threads:[~2003-11-02 13:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f27d2292563520a2008b952aa5b8bda7@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).