linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Albert Cahalan" <acahalan@gmail.com>
To: adobriyan@gmail.com, linux-kernel@vger.kernel.org,
	jsipek@fsl.cs.sunysb.edu, B.Steinbrink@gmx.de
Subject: Re: [RFC] #define rwxr_xr_x 0755
Date: Fri, 28 Jul 2006 00:54:56 -0400	[thread overview]
Message-ID: <787b0d920607272154i44fea139pdff9f7395079779d@mail.gmail.com> (raw)

Alexey Dobriyan writes:

> Every time I try to decipher S_I* combos I cry in pain. Often I just
> refer to include/linux/stat.h defines to find out what mode it is
> because numbers are actually quickier to understand.
>
> Compare and contrast:
>
>       0644 vs S_IRUGO|S_IWUSR vs rw_r__r__
> I'd say #2 really sucks.

Damn right.

I'd be very happy to remove (or #ifndef __KERNEL__ as needed) the
dreadful S_FOO macros. I'd be much happier with plain old octal,
as is normally used for both syscalls and the chmod command.

(the non-octal nonsense was probably invented for porting
software to non-UNIX systems)

If you like the ls way though, you might as well add the file
type notation:  drwxr_xr_x, _r__r__r__, _rw_r__r__, etc.
That's not too bad. Plain octal is best though.

             reply	other threads:[~2006-07-28  4:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28  4:54 Albert Cahalan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27 20:59 [RFC] #define rwxr_xr_x 0755 Alexey Dobriyan
2006-07-27 22:23 ` Björn Steinbrink
2006-07-28 16:34   ` Handle X
2006-07-28 16:48     ` Josef Sipek
2006-07-29  1:43       ` Dmitry Torokhov
2006-07-29  7:59         ` Jan Engelhardt
2006-07-28  3:22 ` Josef Sipek
2006-07-29 13:58 ` Johannes Weiner

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=787b0d920607272154i44fea139pdff9f7395079779d@mail.gmail.com \
    --to=acahalan@gmail.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=adobriyan@gmail.com \
    --cc=jsipek@fsl.cs.sunysb.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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).