VersionMap.SourceMaps: /Cedar/Cedar6.0/VersionMap/CedarSource.VersionMap /Cedar/CedarChest6.0/VersionMap/CedarChestSource.VersionMap VersionMap.SymbolsMaps: /Cedar/Cedar6.0/VersionMap/CedarSymbols.VersionMap /Cedar/CedarChest6.0/VersionMap/CedarChestSymbols.VersionMap CommandTool.BootCommands: " cd ///Commands/ Bringover -p [Cedar]Top>BootTool [Cedar]Top>Clock Clock Run BootTool cd " CommandTool.PerLogin: " Statistics off cd ClearMenu CreateButton Open Open $FileNameSelection$ CreateButton Comp Compile $FileNameSelection$ CreateButton Bind Bind $ShortFileNameSelection$ " CommandTool.NewUser: " Echo How about that? A new user! " CommandTool.PerCommandTool: " ///Commands/NotePerLogin " Debugger.CommandTool.BootCommands: " cd ///Commands/ Bringover -p [Cedar]Top>BootTool [Cedar]Top>Clock [Cedar]Top>EditorComforts Clock Run BootTool EditorComforts cd " BUser.profile Copyright c 1984, 1985 by Xerox Corporation. All rights reserved. Pavel Curtis, May 25, 1984 2:27:56 pm PDT Russ Atkinson (RRA) June 19, 1985 7:03:36 pm PDT This file contains a minimal user profile suitable for installation. For documentation of all available options, see UserProfileDoc.tioga. This example file meets the requirements of the policies laid out in HowToUseAPublicCedarMachine.tioga. VersionMap options CommandTool options ... is executed in the very first CommandTool instance that is created after a full boot. The intention is to setup the machine to be ready to take a checkpoint. It is highly recommended that the amount of stuff in a checkpoint be kept small, so other users have as much capacity remaining as possible. This entry can also be executed by the ///Commands/NoteBootCommands command. ... is executed in every existing CommandTool instance whenever there is a new user at (1) credentials change, (2) rollback, or (3) return from idle. The intention is to use this entry to customize the command tool instance. This entry can also be executed by the ///Commands/NotePerLogin command. ... is executed in exactly one existing CommandTool instance whenever the user logs in (even if the same user), a rollback occurs, or at return from idle. The intention is to use this entry to acquire files peculiar to the user. This entry can also be executed by the ///Commands/NoteNewUser command. ... is executed for every new CommandTool instance (except for the first one, created at full boot). In most cases, the same customization as NotePerLogin is desired. This entry can also be executed by the ///Commands/NotePerCommandTool command. For compatibility, this entry is treated the same as "EachCommandToolCommands". ... is executed for the Debugger volume only in the very first CommandTool instance that is created after a full boot. The intention is to setup the machine to be ready to take a checkpoint. It is highly recommended that the amount of stuff in a checkpoint be kept small, so other users have as much capacity remaining as possible. ÊY˜codešœ ™ Kšœ Ïmœ7™BK™)K™0—K™Kšœô™ôK˜šœ™J™KšÏbœo˜„Kšžœq˜‡J˜—™K™šžœ˜Jšœþ™þKšœ˜KšœE˜EKšœ˜Kšœ ˜ Kšœ˜Jšœ˜—šžœ˜J™«Kšœ˜K˜Kšœ ˜ Kšœ*˜*Kšœ-˜-Kšœ/˜/Jšœ˜—šžœ˜J™®K˜!Jšœ˜—šžœ˜JšœÈ™ÈK˜Jšœ˜—šž!œ˜$J™ÍKšœ˜Kšœi˜iKšœ˜Kšœ˜Kšœ˜Kšœ˜—K˜——…—” /