Menu
▾
▴
[LV-www-commit] www/htdocs/docs README,1.3,1.4
|
From: Jan-Benedict G. <jb...@us...> - 2005-04-06 07:25:39
|
Update of /cvsroot/linux-vax/www/htdocs/docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6337 Modified Files: README Log Message: - Update CVS instructions to refer to the correct hostname at sf.net . - Prefer 2.6.x over 2.4.x -- seems all development goes into 2.6.x so I don't see a point into leading people to use 2.4.x . Index: README =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/docs/README,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- README 17 Sep 2003 21:49:04 -0000 1.3 +++ README 6 Apr 2005 07:25:28 -0000 1.4 @@ -1,23 +1,23 @@ -Last updated May 17, 2002 +Last updated Apr 6, 2005 To play with this port you can either; - A) Download a precompiled kernel, and the vax root image + A) Download a precompiled kernel, and the vax root image or - B) Download the development environment, and compile things + 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 + 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: @@ -26,7 +26,7 @@ 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 +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 @@ -41,41 +41,41 @@ Sources ------- - The most recent snapshots of the compiler and binutils are - held in our CVS repository under the "toolchain" module. You are + The most recent snapshots of the compiler and binutils are + held in our CVS repository under the "toolchain" 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 + 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 toolchain - - We no longer make source snapshots, or patches against the GNU + $ cvs -d:pserver:ano...@cv...:/cvsroot/linux-vax login + (hit return at the password prompt). + $ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/linux-vax co -P toolchain + + 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 + + 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 + + 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. @@ -87,18 +87,19 @@ 2. The kernel sources Grab the sources from CVS. You can either use "kernel-2.4" or "kernel-2.5", - but kernel-2.4 might be a better choice right now: + but kernel-2.5 (which actually contains 2.6.x sources!) might be a better + choice right now: - $ 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-2.4 + $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co kernel-2.5 cd into the kernel dir created by cvs and do $ make oldconfig - to create a default .config. (Beware about playing with the + 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 @@ -120,25 +121,25 @@ 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 + If you have your VAX and Linux machine on the same SCSI chain and you've got a scratch disk handy, you can do $ make diskboot && dd if=vmlinux.dsk of=/dev/sdX - and then tell your VAX to boot from this disk. This is faster than + 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) +(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 + the asbl instructions to install the bootloader for your new kernel. See the vaxroot instructions for details on this. - + 3. A MOP server (mopd) @@ -154,12 +155,12 @@ VAX in _lowercase_ with no separators. For example, mine is 08002b0db20f.SYS. - In can be useful to run mopd with the -d switch to see what it + In can be useful to run mopd with the -d switch to see what it receives from the network. 4. A VAX with an ethernet card or SCSI interface. - As we don't really have any hardware support in yet, hardware + As we don't really have any hardware support in yet, hardware requirements are pretty minimal: CPU @@ -167,7 +168,7 @@ 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 + So far we've had success reports from people with the following machines: VAXstation 2000 @@ -183,19 +184,19 @@ a circle with a dot inside. Hook your VAX up to a standalone terminal, such a VT-series terminal - or a serial port on your PC. The VAX will probably have an MMJ + or a serial port on your PC. The VAX will probably have an MMJ serial connector. I can't find a URL with the pin-out info for this guy. - If you have an OS installed (e.g. VMS, Ultrix, NetBSD), it would be + If you have an OS installed (e.g. VMS, Ultrix, NetBSD), it would be a good idea to take your disks offline, if your VAX has a handy way to do this. For example, the VS3500 has front panel switches to take the internal disks offline. - At the >>> prompt, try B <return>, B XQA0 or B ESA0 and see if one + At the >>> prompt, try B <return>, B XQA0 or B ESA0 and see if one of them tries to netboot (watch the output of mopd -d). - If it looks like mopd sent over a boot image, let us know what + If it looks like mopd sent over a boot image, let us know what happens. Depending on your hardware, you might get a kernel version banner and some diagnostic output. However, if we don't support your serial console hardware, you'll probably just get an @@ -216,11 +217,12 @@ And send us the output. This will hopefully give us clues as to how to get your serial console supported. - If your VAX has a SCSI interface and you have an external SCSI + If your VAX has a SCSI interface and you have an external SCSI connector on your Linux box, you can connect both of them to the same SCSI bus. (Make sure the host adapters in each machine have different SCSI IDs. VAXen usually ship with the host adapter set to ID 6, PCs are usually ID 7.) - Then you can copy the vaxroot image and the kernel image onto - a disk on the bus and boot from there. + Then you can copy the vaxroot image and the kernel image onto + a disk on the bus and boot from there. + |
