9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: ideal plan9 laptop
Date: Wed, 30 Jan 2002 16:31:53 +0000	[thread overview]
Message-ID: <20020130163357.531D619992@mail.cse.psu.edu> (raw)

>>Also my 9load in (/n/9fat) has the 'a' [append] bit on.  This must be a bug.
          The file attribute flags used by the DOS file system do not
          map directly to those used by Plan 9.  Since there is no
          concept of user or group, permission changes via wstat (see
          stat(2)) will fail unless the same (read, write, execute)
          permissions are specified for user, group, and other.  For
          example, removing write permission in Plan 9 corresponds to
          setting the read-only attribute in the DOS file system.
          Most of the other DOS attributes are not accessible.

          Setting the exclusive use flag (CHEXCL) in Plan 9 corre-
          sponds to setting the system use attribute in the DOS file
          system.  Such files are not actually restricted to exclusive
          use, but do merit special treatment that helps in the cre-
          ation of boot disks: when dossrv allocates a new block for
          such a file (caused, say, by a write that fills the file's
          last allocated block), it succeeds only if it can arrange
          for the file to be stored contiguously on disk.

          Since other operating systems do not guarantee that system
          files are laid out contiguously, the CHAPPEND mode bit is
          set in file stat information only when the file is currently
          contiguous.  Attempts to set the CHAPPEND mode bit explic-
          itly will cause dossrv to try to make the file contiguous,
          succeeding only if this is possible.


             reply	other threads:[~2002-01-30 16:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 16:31 forsyth [this message]
2002-01-30 16:46 ` Matt H
2002-01-31 11:13 ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31 15:52 Russ Cox
2002-01-31 16:15 ` Boyd Roberts
2002-01-31 14:14 Russ Cox
2002-01-31 14:20 ` Boyd Roberts
2002-01-31 15:48 ` Boyd Roberts
2002-01-30 17:50 Russ Cox
2002-01-30 12:37 jmk
2002-01-30 14:49 ` Boyd Roberts
2002-01-25 15:22 [9fans] " Boyd Roberts
2002-01-25 22:19 ` [9fans] " Jim Choate
2002-01-28 11:13   ` Thomas Bushnell, BSG
2002-01-28 13:18     ` Jim Choate
2002-01-30  6:24       ` Thomas Bushnell, BSG
2002-01-30 11:34         ` Boyd Roberts
2002-01-25 15:18 [9fans] " andrey mirtchovski
2002-01-25 22:18 ` [9fans] " Jim Choate
2002-01-28 11:13   ` ozan s yigit
2002-01-28 12:46     ` Matt H

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=20020130163357.531D619992@mail.cse.psu.edu \
    --to=forsyth@caldo.demon.co.uk \
    --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).