Rogue Save Files & OS-9 Security (was: Vintage terminals...

Rumor has it that Dave McGuire may have mentioned these words: Of course I do -- doesn't everybody??? I always log in as root on my laptop -- I don't think I have a non-root ID on the thing unless it's for a daemon and has no shell. I also don't re-alias mv to 'rm -i' or cp to 'cp -i" either... I also try my best to not do anything stupid (like let anyone else touch the computer ;-) -- and the only time I've been burned is when I didn't try hard enough, and did something stupid. What I don't like, is that if you set a file to read-only, root can still whack it. That's my WTF... OS-9 never did that! If it was read-only, even the SuperUser couldn't delete it - you had to manually set the attrib back to writable before you could delete it. That burned me once early on in my Slowaris educamation... =-=-= Bringing this back ontopic, in OS-9, is there a way to *not* be the SuperUser without logging in externally? Whilst trying to get Rogue to not delete it's savefiles, I tinkered with the idea of setting either the Rogue process to non-SU mode or the files themselves to non-SU mode, and never had a lot of luck; it intrigued me so much that I kept tinkering with the idea for a few _weeks_ after I realized a few hours into the project that read-only meant exactly that even for the SU. Never really did get very successful with it... Logging in externally (with my Model 200) was easy to see different owners' processes in procs, but never could do it from within the SU id... Maybe I was just "forking" stupid there, too. ;-) Laterz, Roger "Merch" Merchberger -- Roger "Merch" Merchberger | A new truth in advertising slogan SysAdmin, Iceberg Computers | for MicroSoft: "We're not the oxy... zmerch at 30below.com | ...in oxymoron!"