Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!jade!tart15.berkeley.edu!c60a-3dt
From: c60a-3dt@tart15.berkeley.edu.BERKELEY.EDU (Robert Bowdidge)
Newsgroups: comp.sys.tandy
Subject: TRSDOS 1.3
Message-ID: <3625@jade.BERKELEY.EDU>
Date: Tue, 19-May-87 00:51:25 EDT
Article-I.D.: jade.3625
Posted: Tue May 19 00:51:25 1987
Date-Received: Wed, 20-May-87 03:45:53 EDT
Sender: usenet@jade.BERKELEY.EDU
Reply-To: bowdidge@cory.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 23
Keywords: hacks, mods, corruptions

So what's the rudest thing you ever did to a TRSDOS 1.3 diskette?
After getting the source a long time ago, various twisted ideas
have gone through my head, but this one takes the cake:

Give TRSDOS 1.3 a tree-structured directory just like UNIX.
After all, the directory entries look a lot like inodes from Unix,
and then all you'd need to do is have files called "directories"
where you have name and inode number, and then add utilities like
ls, cd (which could be added by removing useless system commands like...
well, I don't know, but passwords are going to go for sure...)

Any discussion?  Someone's GOT to have tried this before! How many have
taken a good Operating Systems class?

-- Robert

                                                           Robert Bowdidge
==========================================================================
.ucbvax!cory!bowdidge          |        bowdidge%cory@ucbvax.BERKELEY.EDU
                                |        or     bowdidge@cory.BERKELEY.EDU
E2A Cloyne Court  2600 Ridge Road  Berkeley CA  94709-1099  (415) 549-6367

        --- In a rock concert, no one can hear you scream...