[#2139] Best way to install ri documentation — Dave Thomas <dave@...>
Folks:
On Monday, January 5, 2004, 2:29:57 AM, Dave wrote:
Hi,
Perhaps make it available for mirrors and save ruby-lang's bandwidth?
Hi,
So, I'm thinking about doing the following? Is this OK with everyone?
Hi,
On Tue, 6 Jan 2004 00:47:41 +0900
On Mon, 12 Jan 2004 23:30:52 +0900
On Tue, Jan 13, 2004 at 12:01:38AM +0900, Dave Thomas wrote:
Hi, Dave,
Hi,
Hi, daz,
On Tuesday, 6 January 2004 at 15:02:50 +0900, NAKAMURA, Hiroshi wrote:
[#2163] Occasional --enable-pthread hangs... — Nathaniel Talbott <nathaniel@...>
First of all, thanks so much to all those that have helped with
On Jan 5, 2004, at 21:49, Nathaniel Talbott wrote:
[#2186] Absolute paths in shebang lines? — "J.Herre" <jlst@...>
What would the reaction be to reconsidering the following proposal?
[#2194] File.readable_world? and File.writable_world? — Ian Macdonald <ian@...>
Hello,
On Fri, Jan 09, 2004 at 06:02:07PM +0900, Ian Macdonald wrote:
On Fri 09 Jan 2004 at 23:10:02 +0900, Eivind Eklund wrote:
Hi,
On Sun 11 Jan 2004 at 00:47:33 +0900, Yukihiro Matsumoto wrote:
Hi,
On Sun 11 Jan 2004 at 21:40:22 +0900, Yukihiro Matsumoto wrote:
Hi,
On Mon 12 Jan 2004 at 10:31:52 +0900, Yukihiro Matsumoto wrote:
Hi,
On Mon 12 Jan 2004 at 22:36:16 +0900, Yukihiro Matsumoto wrote:
On Mon 12 Jan 2004 at 10:31:52 +0900, Yukihiro Matsumoto wrote:
On Sun 11 Jan 2004 at 00:47:33 +0900, Yukihiro Matsumoto wrote:
[#2211] xxx_init_copy — Dave Thomas <dave@...>
I notivce that there're a bunch of new xxx_init_copy methods: RDoc is
Hi,
Hi,
Hi,
Hi,
[#2216] ruby aborts in data-handling applications — xsdg <xsdg@...>
I reported a similar bug about 2 or 3 months ago. The problem seemed to go
Hi,
I've finally found a combination that will reliably segfault. Since my first post on this topic, I've switched the backend from BDB to GDBM.
Hi,
On Mon, Jan 19, 2004 at 11:32:59AM +0900, nobu.nokada@softhome.net wrote:
[#2225] Fwd: [ruby-cvs] ruby: * file.c (test_wr, test_ww): New functions implementing new — Dave Thomas <dave@...>
On Mon 12 Jan 2004 at 23:38:29 +0900, Dave Thomas wrote:
[#2251] YAML_Unit_Tests failed — "NAKAMURA, Hiroshi" <nahi@...>
Hi,
[#2285] A suggestion for libraries such as base64.rb — Dave Thomas <dave@...>
Some of the older libraries simply insert stuff into the top-level
[#2305] Time#usec round trip problem — Minero Aoki <aamine@...>
Hi,
[#2306] YAML.dump("a".."z") — Minero Aoki <aamine@...>
Hi,
Re: [PATCH] File.readable_world? and File.writable_world?
On Fri 09 Jan 2004 at 23:10:02 +0900, Eivind Eklund wrote: > I see two problems with this: > (1) There is no such thing as "readable world" in the permissions of > Unix; the closest I can think of is the combination of user, group > and other permissions. World-readable _is_ a term applied very often in the UNIX world to the a file readable by anyone. I think the term is commonly understood. > Note that these are grabbed in order; > the user that own it CAN NOT read a file with permissions -wxrwxrwx. > Using permissions rwx---rwx is a trick that sometimes is used to > make sure that a particular group cannot get at data. Good point. I tend to think of 'world' as being synonymous with 'other', but it's not, of course. > This is resolvable by renaming to readable_other? (which is the > correct Unix terminology - see > http://www.opengroup.org/onlinepubs/7908799/xbd/glossary.html#tag_004_000_107 > for details). I even wondered "Shall I use 'world' or 'other'?", but I decided that 'world' would be clearer to people. After all, we already have readable_real, not readable_user, although that's a different case again, as we need to distinguish between real and effective UIDs. > (2) If renamed to readable_other?, this is tied very closely to the > ancient Unix permissions systems. This isn't even correct for new > Unixes (ACLs are available), and definately not correct for Windows > et al. Well, I coded it so that it would return false on Windows, but how do you deal with the ACL issue without Ruby to link to yet more system dependent libraries? > Thinking a bit more about it while writing this, I wonder if the right > thing to do wouldn't be to extend the API with four calls instead of > two: > > readable_world? - check for > (perm & (S_IRUSR|S_IRGRP|S_IROTH)) == (S_IRUSR|S_IRGRP|S_IROTH) > (that's the same as) > (perm & 0444) == 0444 > readable_other? - check for > (perm & S_IROTH) == S_IROTH > (that's the same as) > (perm & 0004) == 0004 > > writable_world? and writeable_other? do the same for the write flags. > > Introducing both of them has a couple of advantages: > - It make it obvious to people that there is a difference > - It provide at one call with semantics that can be used on > different permission systems > - It provide the functionality requested (which I agree would be > nice to have - I'd be annoyed if I discovered it was missing.) I like the idea. Of course, then we should probably have readable_group? and writable_group?, too. Matz, do you like the idea or do you consider these methods unnecessary? Ian -- Ian Macdonald | It is a hard matter, my fellow citizens, to System Administrator | argue with the belly, since it has no ears. ian@caliban.org | -- Marcus Porcius Cato http://www.caliban.org |