Menu
▾
▴
[LV-www-commit] CVS: www/htdocs/docs README,1.1,1.2
|
From: Andy P. <at...@us...> - 2002-05-18 10:19:28
|
Update of /cvsroot/linux-vax/www/htdocs/docs In directory usw-pr-cvs1:/tmp/cvs-serv10533/htdocs/docs Modified Files: README Log Message: Update README file to reflect post shell prompt state of world. Remove references to ftp. Remove references to source tarballs and patches. Push CVS, pointers to vax root readme file. Deprecate dd'ing image to scsi disk. Index: README =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/docs/README,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- README 19 Sep 2001 15:53:39 -0000 1.1 +++ README 18 May 2002 10:19:24 -0000 1.2 @@ -1,7 +1,24 @@ -Last updated Jul 10, 2000 +Last updated May 17, 2002 -GETTING STARTED +To play with this port you can either; + + A) Download a precompiled kernel, and the vax root image +or + B) Download the development environment, and compile things + for yourself, to get the latest versions. + + This document describes option B. To experiment with option A, + please look at the file README.vaxroot in the downloads directory. + This file also covers details of setting up a linux/386 system to + act as a mop load host. + http://linux-vax.sf.net/download/README.vaxroot-20010920 + + ALSO. There is information in the FAQ on the website, and in the + README.vaxroot. Or post on the mailing list if you run into + problems. + +GETTING STARTED WITH THE DEVELOPMENT SYSTEM. To play with this port you need the following: @@ -9,86 +26,86 @@ 2. The kernel sources 3. A MOP server (mopd) 4. A VAX with an ethernet card or SCSI interface +5. Optionally, the vaxroot system above, if you want + something to actually run, once your vax has booted. Unfortunately, there are a few large downloads involved to get up and running... 1. The cross-compiler and binutils - First download the following: - - From ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/sources/ - - binutils-2.9.1.0.25.tar.bz2 - egcs-1.1.2.tar.bz2 - - From ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/patches/ - - binutils-2.9.1.0.25-20000219.patch.bz2 - egcs-1.1.2-20000219.patch.bz2 - - From ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/ - - build-vax.sh - one-tree-vax.sh - - Create a new directory to unpack all this stuff in and untar the - egcs and binutils tarballs, apply the patches and copy in the shell - scripts: - - $ mkdir vax-cross - $ cd vax-cross - $ tar xvf --use=bzip2 DOWNLOADS/binutils-2.9.1.0.25.tar.bz2 - $ tar xvf --use=bzip2 DOWNLOADS/egcs-1.1.2.tar.bz2 - $ cd binutils-2.9.1.0.25.current - $ patch -p1 < DOWNLOADS/binutils-2.9.1.0.25-20000219.patch - $ cd ../egcs-1.1.2.current - $ patch -p1 < DOWNLOADS/egcs-1.1.2-20000219.patch - $ cd .. - $ cp DOWNLOADS/one-tree-vax.sh DOWNLOADS/build-vax.sh . - - Then create the combined binutils/egcs source tree and build it: +Sources +------- - $ ./one-tree-vax.sh - $ ./build-vax.sh - - These should complete without errors. If you get errors, something - is seriously wrong and you probably won't get a correctly-installed - toolchain. All object files and binaries will be created in - vax-cross/b-vax-dec-linux without touching the source trees. - - Then install them: - - $ su -c './build-vax.sh install' + The most recent snapshots of the compiler and binutils are + held in our CVS repository under the "tools" module. You are + strongly advised to check this out, and build the tools yourself, + with the supplied script, to ensure you have the most up to date + compilation environment. There are instructions in the FAQ as + to how to checkout the CVS tree, but you can get anonymous access + by using commands like; + $ cvs -d:pserver:ano...@cv...:/cvsroot/linux-vax login + (hit return at the password prompt). + $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co tools + + We no longer make source snapshots, or patches against the GNU + releases, available, as we all use CVS, and our time and bandwidth + is limited. + +Binaries +-------- + + Binaries are available for linux/386 from the download section + of our web server. Binaries are only occasionally built from the + CVS sources, so they may contain bugs already fixed in CVS. + + The downloads index page may be accessed via the URL + http://linux-vax.sf.net/download/index.html + + You will need to download the current binary toolset, which + at the time of writing, is tools-bin-linuxvax-20001231.tar.bz2 + + This tar file needs to be untar'ed into your /usr/local tree + (It is done this way to avoid any conflicts with your native + system version of gcc), with the following command, as root; + + foo# tar xv --use=bzip2 -f /path/to/tools-bin-linuxvax-20001231.tar.bz2 + This will create programs in /usr/local/bin prefixed with vax-dec-linux- (for example /usr/local/bin/vax-dec-linux-gcc) and directories /usr/local/vax-dec-linux and /usr/local/lib/gcc-lib/vax-dec-linux. - This will not touch your current GCC installation. + This will not touch your current GCC installation (unless you have + installed it in /usr/local, and even then it should be ok, but dont + blame us if it goes wrong) 2. The kernel sources Grab the sources from CVS: - $ cvs -d:pserver:ano...@cv...:/cvsroot/linux-vax login - (hit return at the password prompt). + $ cvs -d:pserver:ano...@cv...:/cvsroot/linux-vax login + (hit return at the password prompt). - $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co kernel + $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co kernel cd into the kernel dir created by cvs and do $ make oldconfig - to create a default .config. (Don't go playing with the config, please. - It will probably just break the compile.) + to create a default .config. (Beware about playing with the + config too much, as it might break the compile, obviously there + is no point in including linux/386 specific stuff, e.g. there + not much point in compiling support for a Matrox G450 AGP into + your VAX kernel.) Compile a network-bootable image by doing $ make mopboot This will generate plenty of compiler and linker warnings, but you should - end up with a vmlinux.SYS file sized about 280K. + end up with a vmlinux.SYS file sized about 800K-1.2M, depending on the + options. If you are hacking around in arch/vax, you can do a quicker re-compile by doing @@ -97,6 +114,7 @@ which just rebuilds stuff in arch/vax and re-links the kernel. +(obsolete?) If you have your VAX and Linux machine on the same SCSI chain and you've got a scratch disk handy, you can do @@ -104,16 +122,24 @@ and then tell your VAX to boot from this disk. This is faster than netbooting. - + NOTE THAT THIS WILL DESTROY ANY FILESYSTEM AREADY ON THE DISK. YOU HAVE BEEN WARNED. +(preferred) + A better way of booting from a SCSI disk is to use the vaxroot + filesystem, and the asbl scsi disk boot loader. In this case just + mount the filesystem, copy the kernel onto the disk, and follow + the asbl instructions to install the bootloader for your new + kernel. See the vaxroot instructions for details on this. + + 3. A MOP server (mopd) Sources at - http://www.mssl.ucl.ac.uk/~atp/linux-vax/download/mopd-linux.tar.gz + http://linux-vax.sf.net/download/mopd-linux.tar.gz Compile and install. Create the directory /tftpboot/mop. mopd looks here, and here only, when searching for boot images. @@ -133,7 +159,7 @@ CPU Serial console - 8 MB ram + 8 MB ram, Less may be possible, but not a good idea. Ethernet card So far we've had success reports from people with the following @@ -144,6 +170,7 @@ VAXstation 3100/m76 VAXstation 3500 VAXstation II/GPX + VAXstation 4000/60 First you'll want to get your VAX to stop at the >>> console prompt at power up. There is usually a switch on the CPU board, front @@ -190,10 +217,5 @@ have different SCSI IDs. VAXen usually ship with the host adapter set to ID 6, PCs are usually ID 7.) - Then you can copy a kernel image onto a disk on the bus and boot - from there. - - NOTE THAT THIS WILL DESTROY ANY FILESYSTEM AREADY ON THE DISK. - - YOU HAVE BEEN WARNED. - + Then you can copy the vaxroot image and the kernel image onto + a disk on the bus and boot from there. |
