Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||More CVS fallout.|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | master | trunk|
|Files:||files | file ages | folders|
|User & Date:||vandys 2001-12-21 14:41:01|
|14:41||Support for %n format. check-in: f2a0dfc9bb user: vandys tags: master, trunk|
|14:41||More CVS fallout. check-in: a022ec8942 user: vandys tags: master, trunk|
|14:39||Features. More features. check-in: 827836a92a user: vandys tags: master, trunk|
Changes to vsta/doc/roadmap.txt.
66 66 (Copy vsta.tz here) 67 67 gzip -dv vsta.tz 68 68 tar -xvf vsta.t 69 69 del vsta.t 70 70 71 71 You now have all the binaries and administrative files for VSTa. 72 72 73 - You can iterate on this in the obvious way to load other 74 - sets of VSTa distribution files. 75 - 76 73 Accounts are in /vsta/etc/passwd, with a parallel file /vsta/etc/shadow 77 74 holding the actual passwords, which are in the clear. Feel free 78 75 to edit these files using a DOS editor; VSTa tries to accomodate 79 76 both DOS \r\n and UNIX \n conventions for line-oriented data. The 80 77 format is described in src/lib/passwd.c, but should be familiar to 81 78 anyone who's messed with UN*X-like password files. The group you 82 79 belong to in the passwd file causes you to get more abilities; see ................................................................................ 99 96 src/os/make Where kernel objects are compiled into 100 97 src/os/kern Portable kernel C source 101 98 src/os/mach Kernel i386 C, as well as assembly 102 99 src/srv All portable servers (filesystems, etc.) 103 100 src/srv/mach i386/ISA servers (disk, keyboard, etc.) 104 101 src/bin Command source 105 102 src/lib Library source 106 - src/bin/ports Ports of other UN*X-ish utilities 107 - 108 -If your tree includes the 68030 Amiga port, you will also see mach.ami 109 -directories. The mach.r4k subdirectory probably isn't present, but holds 110 -code for a MIPS R4000 port of VSTa. Both of these ports are in the 111 -unsupported/historical category. 112 103 113 104 3. Booting the kernel, the first time 114 105 115 106 If you're already using GRUB (or some other comparable Multiboot 116 107 compliant loader), you can skip this. 117 108 118 109 Create a GRUB boot floppy using the direction provided with the GRUB ................................................................................ 189 180 5. Multi-screens 190 181 191 182 By default four logins are launched for four virtual screens. Use 192 183 ALT-F1, ALT-F2, ..., to switch between the screens. See the 193 184 file /vsta/etc/inittab to launch more or less screens. The first 194 185 screen (ALT-F1) also receives syslog output. 195 186 196 -6. Building the system 187 +6. Building from Source Code 188 + 189 +The source to the main VSTa distribution is managed by CVS. You'll 190 +need to extract the vsta_cvs.tz file into /cvs, which will create 191 +a tree of CVS files under /cvs/vsta. Once these are extracted, you 192 +need to check out a copy of the tree in some location: 193 + 194 + cd /home/me 195 + cvs -d /cvs co vsta 196 + 197 +This will extract the main VSTa source (which does not include ports 198 +of various utilities--just the kernel, libraries, and core commands like 199 +the default shell). 200 + 201 +Now you need to cd into the source, and edit the line near the top of 202 +makefile.all to indicate the location of this source tree: 203 + 204 + cd vsta/src 205 + vi makefile.all 206 + 207 +Change the line: 208 + SRC=/vandys/src/src 209 +to: 210 + /home/me/vsta/src 211 + 212 +(In the case of this example.) With this set, you can now cd down into any 213 +of the source directories and build from the source there. You probably 214 +want to cd into vsta/src/lib first, as the other source in the tree links 215 +against the privately built version of the library files: 216 + 217 + cd lib 218 + make 219 + 220 +After this, you could build, say, the DOS filesystem code by: 221 + cd ../srv/dos (up out of lib, and into DOS source) 222 + make 223 + 224 +In the top of vsta/src is a mkall.sh, which will enumerate all source, 225 +invoking a "make" with any arguments provided to mkall.sh. Thus, you 226 +could build everything by: 227 + 228 + cd ../.. (up out of DOS, to top of source tree) 229 + sh mkall.sh 230 + 231 +Or remove all object files by: 232 + 233 + sh mkall.sh clean 197 234 198 - (Boot VSTa) 199 - cd /vsta/src 200 - sh -x mkall.sh 201 - (watch the blinkin lights) 202 - (if all looks great:) 203 - sh -x mkall.sh install 235 +Or clean up all generated files by: 204 236 205 -You can also cd to some particular server or command source directory 206 -and "make" or "make install" just that piece. This is probably the 207 -best idea, since if something subtle gets hosed you'll have fewer 208 -changes to undo in order to get a usable system again. 237 + sh mkall.sh clobber 209 238 210 -NOTE: some binaries (emacs, rc, gcc & friends) are in their own 211 -distribution tar file. They are probably not present in your source 212 -tree unless you explicitly loaded them. A lot of the stuff in 213 -src/bin/ports is not part of the regular/formal "VSTa system build" 214 -process. 239 +NOTE: some binaries (emacs, rc, gcc & friends) are in their own distribution 240 +tar files. They are not present in your source tree unless you explicitly 241 +loaded them. The stuff in src/bin/ports is not part of the regular/formal 242 +"VSTa system build" process. 215 243 216 244 7. Documentation 217 245 218 246 Regrettably, not much. Use the "man" command to access the initial man 219 247 pages. Hopefully more will show up, but at least the messaging 220 248 primitives are now documented. You can list the available man entries 221 249 with "man 2 msg", and see msg_receive() documentation with "man