9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] temporary bit prevents scp from file creation
Date: Thu,  2 Sep 2004 16:27:17 -0400	[thread overview]
Message-ID: <288ffc52bf9b08c309d63e21113389f4@plan9.bell-labs.com> (raw)
In-Reply-To: <slrn4cjdqg4.nor.heiko.dudzus@mx.freeshell.org>

On Thu Sep  2 09:29:31 EDT 2004, heiko.dudzus@gmx.de wrote:
> I am astonished how one affects the other. But scp can't place a file
> into a local directory (with temporary bit).
> 
> term% chmod +t /usr/heiko/stuff
> term% scp dudzus@tty.freeshell.org:~/Einladung-ET.ps stuff/
> scp: can't create stuff/: 'stuff/' create without DMDIR
> term%
> 
> But:
> term% chmod -t /usr/heiko/stuff
> term% scp dudzus@tty.freeshell.org:~/Einladung-ET.ps stuff/
> term%
> 
> Not really a hard problem, but perhaps worth a note.

I've fixed it, as well as lnfs and nntpfs.
They all forgot that Qid.type is a bimask and not a value.

--jim


  reply	other threads:[~2004-09-02 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 13:20 Heiko Dudzus
2004-09-02 20:27 ` jmk [this message]
2004-09-02 20:28 ` jmk

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=288ffc52bf9b08c309d63e21113389f4@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --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).