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