From: Elliott.Hughes@genedata.com Elliott.Hughes@genedata.com
Subject: [9fans] allowing long file names with a space too
Date: Tue, 14 Apr 1998 11:52:54 +0200 [thread overview]
Message-ID: <19980414095254.hkXGX_4Nha0iTkQFENan0eU1BPVnEISfUWy0swLBHWc@z> (raw)
> Tclwalk tag[2] fid[2] newfid[2] name[<=256]
> Twalk tag[2] fid[2] name[<=256]
> Tcreate tag[2] fid[2] name[<=256] perm[4] mode[1] [move name to the end?]
> Rstat tag[2] fid[2] stat[<=344]
> Twstat tag[2] fid[2] stat[<=344]
>
> [why is there a pad[1] in Twrite and Rread?]
So that 1 + 2 + 2 + 2 + 1 = 8 in Rread's case, and
1 + 2 + 2 + 8 + 2 + 1 = 16 in Twrite's? This puts the data on
a nice boundary (assuming that the message was aligned).
--
http://users.ch.genedata.com/~enh/
next reply other threads:[~1998-04-14 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-14 9:52 Elliott.Hughes [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-04-14 15:05 G.David
1998-04-14 9:56 Elliott.Hughes
1998-04-10 23:16 G.David
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=19980414095254.hkXGX_4Nha0iTkQFENan0eU1BPVnEISfUWy0swLBHWc@z \
--to=elliott.hughes@genedata.com \
/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).