9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] skulker
Date: Wed, 16 Jun 2004 09:37:30 -0600	[thread overview]
Message-ID: <Pine.LNX.4.44.0406160926400.29491-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <528f155e93bf8a14d18abe74e248be42@plan9.escet.urjc.es>

On Wed, 16 Jun 2004, Fco. J. Ballesteros wrote:

> > Why bother?  You've already spent Venti space on them.
> 
> True for /sys/src, but not for +t /usr/*/tmp directories, in our case.
> 

this reminded me to submit two patches (sources/patch hasn't been touched in
a long time!) i had almost forgotten about.

the first one makes a trivial change to /sys/lib/newuser which does a

    chmods +t /usr/$user/tmp 

after that directory has been created. 

the second is more controversial, so i'll ask 9fans' opinion first:

why create a whole new flag (-T) to 'ls' just to show files of type DMTMP,
when we can use the second char in the first field of an 'ls -l', currently reserved only for DMEXCL
files?

it is possible to have a file of both DMTMP and DMEXCL types but it seems
rare enough and we aren't guaranteed that a missing DMTMP will cause the
file to be stored to venti anyway.

the change is trivial:

    plan9% diff dirmodefmt.c /sys/src/libc/9sys/dirmodefmt.c 
    41,42d40
    <   else if(m & DMTMP)
    <       buf[1]='t';
    plan9% 

andrey



  parent reply	other threads:[~2004-06-16 15:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 10:31 Steve Simon
2004-06-16 11:35 ` Russ Cox
2004-06-16 14:17   ` Fco. J. Ballesteros
2004-06-16 14:40     ` Russ Cox
2004-06-16 14:41     ` C H Forsyth
2004-06-16 15:37     ` andrey mirtchovski [this message]
2004-06-16 16:25       ` Fco. J. Ballesteros
2004-06-16 17:36       ` Russ Cox
2004-06-16 17:51         ` rog
2004-06-16 17:49           ` William Josephson
2004-06-16 17:49           ` Fco. J. Ballesteros
2004-06-16 17:59             ` rog
2004-06-16 17:56               ` Fco. J. Ballesteros
2004-06-16 19:21                 ` boyd, rounin
2004-06-16 19:41                   ` Fco. J. Ballesteros
2004-06-16 20:30                     ` boyd, rounin
2004-06-16 20:33                       ` Fco. J. Ballesteros
2004-06-16 21:04                         ` Christoph Lohmann
2004-06-16 22:07                         ` boyd, rounin
2004-06-17  2:58                           ` Kenji Okamoto
2004-06-17  3:01                             ` Kenji Okamoto
2004-06-17  6:25                               ` Kenji Okamoto
2004-06-16 18:21             ` andrey mirtchovski
2004-06-16 19:18           ` boyd, rounin
2004-06-16 19:34             ` rog
2004-06-16 18:13         ` andrey mirtchovski
2004-06-17  0:21 ` Geoff Collyer

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=Pine.LNX.4.44.0406160926400.29491-100000@fbsd.cpsc.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).