[bug #35293] [ext2fs] cat on directory

Update of bug #35293 (project hurd): Status:None => Invalid Open/Closed:Open => Closed Wiki-like text discussion box: => ___

[bug #35293] [ext2fs] cat on directory

Follow-up Comment #5, bug #35293 (project hurd): Well, no, these characters are supposed to be there: what you get is the raw content of the directory in the filesystem. ___ Reply to this item at:

[bug #35293] [ext2fs] cat on directory

Update of bug #35293 (project hurd): Wiki-like text discussion box: => ___ Follow-up Comment #4: Anyway there shouldn't be these characters: "@Ô". And should be n after mcsim (Now there is no o

[bug #35293] [ext2fs] cat on directory

Follow-up Comment #3, bug #35293 (project hurd): POSIX only says that EISDIR should be returned when using write access, so implementations are free to implement a read access (and iirc linux used to do it a long time ago). ___ Reply to th

[bug #35293] [ext2fs] cat on directory

Follow-up Comment #2, bug #35293 (project hurd): IIRC it's a feature, not a bug. ___ Reply to this item at: ___ Message posté via/par Savannah http:/

[bug #35293] [ext2fs] cat on directory

Follow-up Comment #1, bug #35293 (project hurd): I tend to disagree. In particular, I seem to recall that (certain versions of?) FreeBSD allowed directories to be read(2) as if they were regular files. I wonder if POSIX has something to say on this?

[bug #35293] [ext2fs] cat on directory

URL: Summary: [ext2fs] cat on directory Project: The GNU Hurd Submitted by: mplaneta Submitted on: Thu 12 Jan 2012 12:32:21 AM EET Category: None Severity: 3 - Normal