3 ms·
No, that doesn't sound right. Probably more like: " The RDOS file system provided means for protecting files by setting attributes. Because RDOS, not being a
by smcameron 5y ago
No, that doesn't sound right. Probably more like:
"
The RDOS file system provided means for protecting files by setting attributes. Because RDOS, not being a multi-user system, had no notion of file ownership, attributes applied to all programs that accessed a file. The sense of the attribute bits was, in most cases, the opposite of that in Unix; if the bit was set, the operation was prohibited. Files were by default created with all attribute bits cleared, permitting all operations. The attribute bits, as identified by the letters used to identify them in a file listing, were:
'R': prohibited reading
'W': prohibited writing
'P': "permanent file"; prohibited renaming or deleting the file
'S': identified a "save" file, that is, one that contains an executable program.
'N': prohibited symbolic links from linking to this file
'A': attributed protected; prohibited any further changes to the file's attributes. (A file that had both P and A set became un-deletable, except by reformatting the disk.)
'I': Prohibited reading or writing by means other than direct block I/O. (This was removed from later versions of RDOS.)
'?' and '&': User-defined attributes, ignored by RDOS
"
http://www.self.gutenberg.org/articles/Data_General_RDOS http://www.self.gutenberg.org/articles/Data_General_RDOS
- mad_ned 5y agothanks for this! I've always wondered what the deal was, and teen me did not do any research on why the hack worked- once I got the files visible I just moved on. It was almost certainly this RDOS attribute stuff you show here I was playing with (also I took some artistic license in the post, not really sure it was 'F' vs. 'E'.)