You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(17) |
Oct
(2) |
Nov
(1) |
Dec
|
2002 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
|
2004 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
(3) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2005 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(4) |
2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Jan-Benedict G. <jb...@us...> - 2012-12-06 13:22:41
|
Update of /cvsroot/linux-vax/www/htdocs In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv21962 Modified Files: header.html Log Message: Fake commit to test for write capabilities. Index: header.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/header.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- header.html 9 Oct 2001 22:44:44 -0000 1.2 +++ header.html 6 Dec 2012 13:22:38 -0000 1.3 @@ -1,5 +1,5 @@ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> -<HTML> +<html> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="GENERATOR" CONTENT="Mozilla/4.10 [en] (X11; I; Linux 2.0.36 i586) [Netscape]"> |
From: Jan-Benedict G. <jb...@us...> - 2012-05-29 22:21:14
|
Update of /cvsroot/linux-vax/www/htdocs In directory vz-cvs-4.sog:/tmp/cvs-serv11478 Modified Files: newsframe.html Log Message: Mention vax-linux.org Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.19 retrieving revision 1.20 diff -u -d -r1.19 -r1.20 --- newsframe.html 27 Jan 2006 21:51:46 -0000 1.19 +++ newsframe.html 29 May 2012 22:21:12 -0000 1.20 @@ -13,6 +13,17 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>30 May 2012</TD> + <TD> + <B>The VAX-Linux Porting Project</B><BR> + After a long time of silence, we're moving + to out new site, <a href="http://vax-linux.org">http://vax-linux.org</a>. + There's not yet much to see, but the mailing List, + which was sponsored for countless years by + Pergamentum, will be moved soon. + </TD> + </TR> + <TR> <TD>27 January 2006</TD> <TD> <B>Toolchain</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2007-03-18 22:59:48
|
Update of /cvsroot/linux-vax/www/htdocs/docs In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv31573 Modified Files: README Log Message: - Fix typo (uclibx -> uclibc). Thanks to James W. Laferriere. Index: README =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/docs/README,v retrieving revision 1.6 retrieving revision 1.7 diff -u -d -r1.6 -r1.7 --- README 12 Nov 2005 13:26:57 -0000 1.6 +++ README 18 Mar 2007 21:52:09 -0000 1.7 @@ -130,8 +130,8 @@ the cross-compiler binaries in your $PATH. Then you can configure and build the kernel: - make ARCH=vax CROSS_COMPILE=vax-linux-uclibx- menuconfig - make ARCH=vax CROSS_COMPILE=vax-linux-uclibx- mopboot + make ARCH=vax CROSS_COMPILE=vax-linux-uclibc- menuconfig + make ARCH=vax CROSS_COMPILE=vax-linux-uclibc- mopboot If you observe anything that doesn't compile or work properly, please drop us an email! We'll try to fix that as soon as possible. |
From: Jan-Benedict G. <jb...@us...> - 2006-01-27 21:51:56
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16658 Modified Files: newsframe.html Log Message: - Most uClibc patches are checked in right now. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -d -r1.18 -r1.19 --- newsframe.html 27 Dec 2005 23:51:09 -0000 1.18 +++ newsframe.html 27 Jan 2006 21:51:46 -0000 1.19 @@ -13,6 +13,17 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>27 January 2006</TD> + <TD> + <B>Toolchain</B><BR> + Most of the uClibc patches went upstream! + Only some libpthread sysdeps, the + <TT>.config</TT> file and my libm hack are + kept as patches in our CVS repo. I can + now start dealing with the fallout. + </TD> + </TR> + <TR> <TD>27 December 2005</TD> <TD> <B>Toolchain</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2005-12-27 23:51:17
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7024 Modified Files: newsframe.html Log Message: - s/well/will/ Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.17 retrieving revision 1.18 diff -u -d -r1.17 -r1.18 --- newsframe.html 27 Dec 2005 20:29:05 -0000 1.17 +++ newsframe.html 27 Dec 2005 23:51:09 -0000 1.18 @@ -28,7 +28,7 @@ (it's called "Nemo" for now until I find a better name) running that compiles the the vax-linux and vax-linux-uclibc - toolchain every 30min. So we well now detect + toolchain every 30min. So we will now detect errorneous upstream changes really soon after they were checked in.<BR> The vax-linux-uclibc target should basically |
From: Jan-Benedict G. <jb...@us...> - 2005-12-27 20:29:15
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2141 Modified Files: newsframe.html Log Message: - Last binutils patch committed upstream today. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.16 retrieving revision 1.17 diff -u -d -r1.16 -r1.17 --- newsframe.html 18 Dec 2005 21:49:49 -0000 1.16 +++ newsframe.html 27 Dec 2005 20:29:05 -0000 1.17 @@ -13,6 +13,14 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>27 December 2005</TD> + <TD> + <B>Toolchain</B><BR> + The very last outstanding binutils patch + was checked in into upstream sources today. + </TD> + </TR> + <TR> <TD>17 December 2005</TD> <TD> <B>Toolchain</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2005-12-18 21:50:04
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22513 Modified Files: newsframe.html Log Message: - Notice that we noe have a build robot. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.15 retrieving revision 1.16 diff -u -d -r1.15 -r1.16 --- newsframe.html 10 Dec 2005 17:12:17 -0000 1.15 +++ newsframe.html 18 Dec 2005 21:49:49 -0000 1.16 @@ -13,6 +13,23 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>17 December 2005</TD> + <TD> + <B>Toolchain</B><BR> + Since yesterday, I've got a build daemon + (it's called "Nemo" for now until + I find a better name) running that compiles + the the vax-linux and vax-linux-uclibc + toolchain every 30min. So we well now detect + errorneous upstream changes really soon after + they were checked in.<BR> + The vax-linux-uclibc target should basically + work, and I'm now hacking on the GNU libc + based vax-linux target. Though that'll take + some time to get mature... + </TD> + </TR> + <TR> <TD>09 December 2005</TD> <TD> <B>Toolchain</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2005-12-10 17:12:28
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2383 Modified Files: newsframe.html Log Message: - Mention ./configure will now recognize vax-dec-linux-gnu. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.14 retrieving revision 1.15 diff -u -d -r1.14 -r1.15 --- newsframe.html 30 Nov 2005 18:44:07 -0000 1.14 +++ newsframe.html 10 Dec 2005 17:12:17 -0000 1.15 @@ -13,6 +13,17 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>09 December 2005</TD> + <TD> + <B>Toolchain</B><BR> + <TT>config.guess</TT>, part of the <TT>./configure</TT> + ritual, should now recognize the vax-dec-linux-gnu + target as a patch for this issue went upstream today. + Work is being done to generically also recognize + the -uclibc variant. + </TD> + </TR> + <TR> <TD>30 November 2005</TD> <TD> <B>Toolchain</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2005-11-30 18:44:20
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv833 Modified Files: newsframe.html Log Message: - Add a link to my email Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -d -r1.13 -r1.14 --- newsframe.html 30 Nov 2005 18:12:30 -0000 1.13 +++ newsframe.html 30 Nov 2005 18:44:07 -0000 1.14 @@ -17,8 +17,9 @@ <TD> <B>Toolchain</B><BR> A cross-compiled GCC-4.2 (checked out from SVN, - plus some patches), running on a VAX, properly - compiled a "Hello World!" program. + plus some patches), running on a VAX, + <A href="http://www.pergamentum.com/pipermail/linux-vax/2005-November/000279.html">properly + compiled</A> a "Hello World!" program. </TD> </TR> <TR> |
From: Jan-Benedict G. <jb...@us...> - 2005-11-30 18:12:37
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv24196 Modified Files: newsframe.html Log Message: - Mention my gcc that's able to build a working program. (Both gcc and the program run on a VAX.) Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -d -r1.12 -r1.13 --- newsframe.html 12 Nov 2005 09:21:42 -0000 1.12 +++ newsframe.html 30 Nov 2005 18:12:30 -0000 1.13 @@ -13,6 +13,15 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>30 November 2005</TD> + <TD> + <B>Toolchain</B><BR> + A cross-compiled GCC-4.2 (checked out from SVN, + plus some patches), running on a VAX, properly + compiled a "Hello World!" program. + </TD> + </TR> + <TR> <TD>12 November 2005</TD> <TD> <B>Kernel</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2005-11-12 14:09:26
|
Update of /cvsroot/linux-vax/www/htdocs/download In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8388 Modified Files: dlframe.html Added Files: toolchain-20051111.tar.gz Log Message: - New cross-compiler binary. Index: dlframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/download/dlframe.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -d -r1.11 -r1.12 --- dlframe.html 19 Jun 2005 09:15:08 -0000 1.11 +++ dlframe.html 12 Nov 2005 14:09:15 -0000 1.12 @@ -34,8 +34,10 @@ Protocol Daemon (mopd-linux.tar.gz)</A></LI> <LI><A href="tools-bin-linuxvax-20001231.tar.bz2">Cross compilation toolset for Linux/i386</A> - <LI><A href="vax-linux-gcc-4.1.0-20050618-for-i686.tar.gz">Up-to-date - cross compiler for 2.6.x kernel work, for i686.</A></LI> + <LI><A href="toolchain-20051111.tar.gz">Cross compiler for + i686, based on 2005-11-11 snapshot</A></LI> + <LI><A href="vax-linux-gcc-4.1.0-20050618-for-i686.tar.gz">Cross + compiler for i686, based on 2005-06-18 snapshot</A></LI> <LI><A href="asbl-0.1.tar.gz">Andy's SCSI boot loader</A></LI> <LI><A href="README.vaxroot-20010920">Instructions for Linux/VAX root image</A></LI> --- NEW FILE: toolchain-20051111.tar.gz --- (This appears to be a binary file; contents omitted.) |
From: Jan-Benedict G. <jb...@us...> - 2005-11-12 13:27:14
|
Update of /cvsroot/linux-vax/www/htdocs/docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11003 Modified Files: README Log Message: - Rework parts of the README, describing how to get the kernel sources with GIT. Index: README =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/docs/README,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- README 7 Apr 2005 22:57:05 -0000 1.5 +++ README 12 Nov 2005 13:26:57 -0000 1.6 @@ -1,5 +1,5 @@ -Last updated Apr 6, 2005 +Last updated Nov 12, 2005 To play with this port you can either; @@ -19,10 +19,10 @@ problems. GETTING STARTED WITH THE DEVELOPMENT SYSTEM. - +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To play with this port you need the following: -1. The cross-compiler and binutils +1. A cross-compiler toolchain including binutils and gcc 2. The kernel sources 3. A MOP server (mopd) 4. A VAX with an ethernet card or SCSI interface @@ -36,30 +36,49 @@ no longer updated! -1. The cross-compiler and binutils +1. The cross-compiler and binutils +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sources ------- + We're basically using the very latest binutils and GCC sources + directly from their source code management systems, plus a number + of patches. There are three main scripts aiding you in getting + a working toolchain: - 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 - to how to checkout the CVS tree, but you can get anonymous access - by using commands like; + * initial_cvs_checkout.sh will initially checkout all the + source code of Binutils, GCC, glibc and uClibc. CVS and + SVN both need to be installed. - $ 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 + * update_upstream_cvs_sandboxes.sh will update the downloaded + sandboxes to their current HEAD versions. You'd always do that + before you run the third script. + + * build_toolchain.sh actually builds the toolchain. + + These scripts, as well as an additional README, are in the "toolchain" + module (in the "scripts" directory) of our SF.net CVS server. You can + download it with: + + cvs -d:pserver:ano...@cv...:/cvsroot/linux-vax login + (If you're asked for a password, simply press Enter!) + + cvs -z3 -d:pserver:ano...@cv...:/cvsroot/linux-vax co -P toolchain + + You'll need to edit one file (toolchain/scripts/vax_toolchain_config) + to match your directory layout, but that's described in detail in the + toolchain/scripts/README file. You're now ready to build a vax-linux-uclibc + cross toolchain with: + + build_toolchain.sh --omit-checks --log-to-file vax-linux-uclibc + + This will take quite some time (about 50min on my 1.4GHz Athlon, 1.5GB RAM) + and disk space (about 2.1GB). This toolchain should be capable of + building a kernel as well as building some limited userland. - 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. @@ -67,51 +86,55 @@ 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 + The tarball contains a unique base path (like ./usr-20051111). + Please extract it to eg. /usr/local/ and put /usr/local/usr-20051111/bin/ + into your $PATH environment variable to have access to the toolchain + binaries. - 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 (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 +~~~~~~~~~~~~~~~~~~~~~ + The current kernel sources (2.6.x based) are kept in GIT, Linus new + source code management tool he specifically wrote for his kernel + work. Some distributions already ship with working GIT packages, some + don't. If you need to build it by hand, there's a nice little howto + at http://linux.yyz.us/git-howto.html (written by Jeff Garzik) that + describes the initial installation. (It's also a nice read if you + want to fully introduce yourself into GIT, but all you really need + to know is the following.) - Grab the sources from CVS. You can either use "kernel-2.4" or "kernel-2.5", - but kernel-2.5 (which actually contains 2.6.x sources!) might be a better - choice right now: + Armed with a GIT installation, you can now proceed to check-out the + current vax-linux kernel sources: - $ cvs -d:pserver:ano...@cv...:/cvsroot/linux-vax login - (hit return at the password prompt). + * Initial checkout. This will give you a full copy of the repository. + By design, each cloned sandbox contains the full history and can + be cloned by other users later on, too: - $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co kernel-2.5 + git clone http://www.kernel.org/pub/scm/linux/kernel/git/jbglaw/vax-linux.git/ vax-linux-kernel - cd into the kernel dir created by cvs and do + * Check-out the correct branch. The "master" branch only contains the + vanilla Linus kernel. All VAX specific bits are in the "vax4linus" + branch: - $ make ARCH=vax oldconfig + git checkout -f vax4linus - 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.) + * From time to time, you may want to update your repository to also contain + all upstream changes: - Compile a network-bootable image by doing + git pull + git checkout -f vax4linus - $ make ARCH=vax mopboot + You see, it's as easy as CVS to use. Now it's time to actually build + a kernel image. That's easy, too. First make sure that you have all + the cross-compiler binaries in your $PATH. Then you can configure and + build the kernel: - This will generate plenty of compiler and linker warnings, but you should - end up with a vmlinux.SYS file sized about 800K-1.2M, depending on the - options. + make ARCH=vax CROSS_COMPILE=vax-linux-uclibx- menuconfig + make ARCH=vax CROSS_COMPILE=vax-linux-uclibx- mopboot + + If you observe anything that doesn't compile or work properly, please + drop us an email! We'll try to fix that as soon as possible. (obsolete?) If you have your VAX and Linux machine on the same SCSI chain and @@ -134,8 +157,9 @@ kernel. See the vaxroot instructions for details on this. -3. A MOP server (mopd) +3. A MOP server (mopd) +~~~~~~~~~~~~~~~~~~~~~~ Sources at http://linux-vax.sf.net/download/mopd-linux.tar.gz |
From: Jan-Benedict G. <jb...@us...> - 2005-11-12 09:22:01
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3878 Modified Files: newsframe.html Log Message: - Mention half-working uClibc. - Mention CVS closedown for the kernel tree, it's now in GIT. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -d -r1.11 -r1.12 --- newsframe.html 30 May 2005 13:10:22 -0000 1.11 +++ newsframe.html 12 Nov 2005 09:21:42 -0000 1.12 @@ -13,6 +13,32 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>12 November 2005</TD> + <TD> + <B>Kernel</B><BR> + For some time, we were playing with GIT, + Linus' new source code management tool. + Today we announce it: the CVS tree is + now closed, all further development will + (at least for now) happen in the GIT tree. + Docs will be updated soon to show how to + access and how to work with it. + </TD> + </TR> + <TR> + <TD>October 2005</TD> + <TD> + <B>Toolchain</B><BR> + uClibc compiles again (using the + <TT>toolchain/scripts/build_toolchain.sh</TT> + script) and we've now again got a mostly + working userland compiler, based on GCC HEAD. + Unfortunately, there's still a problem with + stat() so it isn't really usefull for real-world + applications yet. + </TD> + </TR> + <TR> <TD>29 May 2005</TD> <TD> <B>Toolchain</B>, <B>Kernel</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2005-06-19 09:15:35
|
Update of /cvsroot/linux-vax/www/htdocs/download In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16635 Modified Files: dlframe.html Added Files: vax-linux-gcc-4.1.0-20050618-for-i686.tar.gz Log Message: - Upload 20050618 snapshot of gcc/g++ (for kernel work only). - Mention this gcc on the download page. - Kenn: Would you please also make this gcc available to SF's releases page? Index: dlframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/download/dlframe.html,v retrieving revision 1.10 retrieving revision 1.11 diff -u -d -r1.10 -r1.11 --- dlframe.html 4 May 2004 00:23:58 -0000 1.10 +++ dlframe.html 19 Jun 2005 09:15:08 -0000 1.11 @@ -1,43 +1,55 @@ -<html> -<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica"> - -<h1>Downloads</h1> - -Snapshots and binaries. These may be out of date, and if possible you -are advised to get the source direct from the CVS server to be sure -that you are getting the most up to date version. We haven't really -released any formal packages as yet but these will get you in the game.<p> - -<h2>CVS</h2> - -Our <a href="http://www.sourceforge.net/cvs/?group_id=2626">CVS page at -sourceforge</a> holds information on how to get up and running with the -CVS modules (See the <a href="../newfaq/newfaq.html">FAQ</a> for details on -the different modules in CVS). You can also browse the CVS using the -<a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-vax/">web based -viewer</a>. -<p> -<h2>HTTP downloads</h2> +<HTML> + <BODY text="#000000" bgcolor="#FFFFFF" link="#009900" vlink="#990032" alink="#6F7463" font face="Helvetica"> + <H1>Downloads</H1> + <P> + Snapshots and binaries. These may be out of date, and + if possible you are advised to get the source direct + from the CVS server to be sure that you are getting + the most up to date version. We haven't really + released any formal packages as yet but these will get + you in the game. + </P> -The FTP service hosted by sourceforge has been retired. Packages are -now being made available only via HTTP.<p> -<ul> -<li><a href="mopd-linux.tar.gz">Maintenance Operations Protocol Daemon -(mopd-linux.tar.gz)</a> -<li><a href="tools-bin-linuxvax-20001231.tar.bz2">Cross compilation toolset -for Linux/i386</a> -<li><a href="asbl-0.1.tar.gz">Andy's SCSI boot loader</a> -<li><a href="README.vaxroot-20010920">Instructions for Linux/VAX root image</a> -<li><a href="vaxroot-20010920.tar.bz2">Andy's vaxroot-20010920 root filesystem (8583002 bytes)</a> -<li><a href="mirror-20040504.tar.gz">Dave Airlie's "mirror" network driver (for local loopback to SIMH)</a> - (release 20040504 - updated to compile against 2.6.x) -</ul> + <H2>CVS</H2> + <P> + Our + <A href="http://www.sourceforge.net/cvs/?group_id=2626">CVS + page at sourceforge</A> holds information on how to + get up and running with the CVS modules (see the + <a href="../newfaq/newfaq.html">FAQ</A> for details on + the different modules in CVS). You can also browse the + CVS using the + <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-vax/">web + based viewer</A>. + </P> + <H2>HTTP downloads</H2> + <P> + The FTP service hosted by sourceforge has been retired. + Packages are now being made available only via HTTP. + </p> -<SCRIPT> -<!-- -document.write("<font size=-1>Last modified "+document.lastModified+"</font>"); -// --> -</SCRIPT> -</body> -</html> + <UL> + <LI><A href="mopd-linux.tar.gz">Maintenance Operations + Protocol Daemon (mopd-linux.tar.gz)</A></LI> + <LI><A href="tools-bin-linuxvax-20001231.tar.bz2">Cross + compilation toolset for Linux/i386</A> + <LI><A href="vax-linux-gcc-4.1.0-20050618-for-i686.tar.gz">Up-to-date + cross compiler for 2.6.x kernel work, for i686.</A></LI> + <LI><A href="asbl-0.1.tar.gz">Andy's SCSI boot loader</A></LI> + <LI><A href="README.vaxroot-20010920">Instructions for + Linux/VAX root image</A></LI> + <LI><A href="vaxroot-20010920.tar.bz2">Andy's + vaxroot-20010920 root filesystem (8583002 bytes)</A></LI> + <LI><A href="mirror-20040504.tar.gz">Dave Airlie's + "mirror" network driver (for local + loopback to SIMH)</A> (release 20040504 - + updated to compile against 2.6.x)</LI> + </UL> + <SCRIPT> + <!-- + document.write("<font size=-1>Last modified "+document.lastModified+"</font>"); + // --> + </SCRIPT> + </BODY> +</HTML> --- NEW FILE: vax-linux-gcc-4.1.0-20050618-for-i686.tar.gz --- (This appears to be a binary file; contents omitted.) |
From: Jan-Benedict G. <jb...@us...> - 2005-06-08 18:26:25
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23282 Modified Files: indexframe.html Log Message: - Fix singular vs. plural error. Index: indexframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/indexframe.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- indexframe.html 8 Jun 2005 13:03:30 -0000 1.2 +++ indexframe.html 8 Jun 2005 18:26:12 -0000 1.3 @@ -34,7 +34,7 @@ <TT>linux-vax</TT>. To subscribe, please visit <A href="http://www.pergamentum.com/mailman/listinfo/linux-vax">http://www.pergamentum.com/mailman/listinfo/linux-vax</A>. This is the Mailman interface for our list. Because the list used to -life on a different machines, there are currently two archives, the +life on a different machine, there are currently two archives, the old one at <A href="http://solar.physics.montana.edu/hypermail/linux-vax/">http://solar.physics.montana.edu/hypermail/linux-vax/</A> and the new one, which belongs to the mailing list mentioned above at |
From: Jan-Benedict G. <jb...@us...> - 2005-06-08 13:03:48
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15606 Modified Files: indexframe.html linkframe.html Log Message: - Mention our new mailing list location. Index: linkframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/linkframe.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- linkframe.html 19 Sep 2001 15:53:39 -0000 1.1 +++ linkframe.html 8 Jun 2005 13:03:30 -0000 1.2 @@ -1,30 +1,31 @@ -<html> -<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica"> - -<h1>Useful links</h1> - -<h2>Other Linux/VAX pages</h2> -<ul> -<li>Andys <a href="http://www.pergamentum.com/~atp/vax">linux vax page</a> -<li>Kenns <a href="http://www.bluetree.ie/~kenn/linux-vax/">linux vax pages</a> -<li>Daves <a href="http://www.skynet.ie/~airlied/vax">pages</a> -</ul> -<p> -<h2>Other</h2> -<ul> -<li><a href="http://www.netbsd.org">NetBSD project</a> -<li><a href="http://www.openvms.compaq.com">Compaq OpenVMS</a> -<li><a href="http://www.vaxarchive.org">VAX Archive</a> -<li><a href="http://www.compaq.com/alphaserver/vax">Compaq VAX systems</a> -</ul> - - - +<HTML> + <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica"> + <H1>Useful links</H1> + <H2>Other Linux/VAX pages</H2> + <UL> + <LI>The <A href="http://solar.physics.montana.edu/hypermail/linux-vax/">old</A> + and + <A href="http://www.pergamentum.com/pipermail/linux-vax/">new + mailing list archive</A>. + <LI>Andys <A href="http://www.pergamentum.com/~atp/vax">linux vax page</A> + <LI>Kenns <A href="http://www.bluetree.ie/~kenn/linux-vax/">linux vax pages</A> + <LI>Daves <A href="http://www.skynet.ie/~airlied/vax">pages</A> + <LI>Our SourceForge.net + <A href="http://sf.net/projects/linux-vax/">project page</A>. + </UL> + <P> + <H2>Other</H2> + <UL> + <LI><A href="http://www.netbsd.org">NetBSD project</A> + <LI><A href="http://www.openvms.compaq.com">Compaq OpenVMS</A> + <LI><A href="http://www.vaxarchive.org">VAX Archive</A> + <LI><A href="http://www.compaq.com/alphaserver/vax">Compaq VAX systems</A> + </UL> -<SCRIPT> -<!-- -document.write("<font size=-1>Last modified "+document.lastModified+"</font>"); -// --> -</SCRIPT> -</body> -</html> + <SCRIPT> + <!-- + document.write("<font size=-1>Last modified "+document.lastModified+"</font>"); + // --> + </SCRIPT> + </BODY> +</HTML> Index: indexframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/indexframe.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- indexframe.html 19 Sep 2001 15:53:39 -0000 1.1 +++ indexframe.html 8 Jun 2005 13:03:30 -0000 1.2 @@ -1,7 +1,6 @@ -<html> -<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" -ALINK="#6F7463" FONT FACE="Helvetica" > -<table WIDTH=680><tr><td> +<HTML> + <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica" > + <TABLE width="680"><tr><td> <FONT FACE="Helvetica, Arial"><FONT SIZE=+2> A port of Linux to the VAX Architecture.</FONT> @@ -10,45 +9,47 @@ the Linux Kernel to the Digital Equipment Corporation (DEC) (now owned by Compaq/Hewlett Packard) VAX and MicroVAX mini computer systems. VAX (Virtual Address eXtension) computers were designed and -built from the mid-1970s through to retirement of the line in 1999/2000. +built from the mid-1970s through to retirement of the line in 1999/2000. <p> Here you will find all you need to get the Linux Kernel up and running on a VAX computer. We don't support many of the models yet, and it is very early -days - we don't (at the time of writing) have dynamic libraries yet! But if +days - we don't (at the time of writing) have dynamic libraries yet! But if you have one of the systems listed in the FAQ you can run a limited version -of Linux on it. See the Documentation link for details on the installation +of Linux on it. See the Documentation link for details on the installation process. However, its very rough at the moment, and you need to be very comfortable with the command line and root prompt to be successful. <p> If you don't like the idea of that, then we suggest that you visit our -friends over at the NetBSD project at +friends over at the NetBSD project at <A HREF="http://www.netbsd.org">http://www.netbsd.org/</A> who make a free UNIX that runs on a wide variety of VAX hardware. NetBSD has -a much easier installation, not to mention fewer bugs (at the moment...). +a much easier installation, not to mention fewer bugs (at the moment...). <p> Still here?<p> You might like to join the Mailing list if you are serious about this...<p> The mailing list is somewhat imaginatively titled -<TT>linux-vax</TT>. It changed its home a few years ago, and -If you were a member of the old list at resserv, you will need to -resubscribe to the new list, as the list of members was not saved. -Its not exactly high volume :-).<p> -To subscribe, send an email to: -<P>The <FONT FACE="Courier New,Courier" SIZE=-1>majordomo</FONT> account -at <FONT FACE="Courier New,Courier" SIZE=-1>solar.physics.montana.edu</FONT> -<P><FONT FACE="Arial,Helvetica">with</FONT> -<P><FONT FACE="Arial,Helvetica">"</FONT><FONT FACE="Courier New,Courier"><FONT SIZE=-1>subscribe -linux-vax</FONT></FONT><FONT FACE="Arial,Helvetica">" in the body (without -the quotes of course)</FONT> -<P> There is a hypermail mailing list <A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/">archive</A> -as well if you just want to lurk. -</td></tr></table> -<HR width=690 align=left> +<TT>linux-vax</TT>. To subscribe, please visit +<A href="http://www.pergamentum.com/mailman/listinfo/linux-vax">http://www.pergamentum.com/mailman/listinfo/linux-vax</A>. +This is the Mailman interface for our list. Because the list used to +life on a different machines, there are currently two archives, the +old one at +<A href="http://solar.physics.montana.edu/hypermail/linux-vax/">http://solar.physics.montana.edu/hypermail/linux-vax/</A> +and the new one, which belongs to the mailing list mentioned above at +<A href="http://www.pergamentum.com/pipermail/linux-vax/">http://www.pergamentum.com/pipermail/linux-vax/</A>. +They'll be merged soon, though. +<p> +Additionally, you could subscribe to the CVS checkin mailing list for +<A href="http://lists.sourceforge.net/mailman/listinfo/linux-vax-k25-commit">Kernel</A> +(<A href="http://sourceforge.net/mailarchive/forum.php?forum_id=9493">archive</A>), +<A href="http://lists.sourceforge.net/mailman/listinfo/linux-vax-tools-commit">toolchain</A> +(<A href="http://sourceforge.net/mailarchive/forum.php?forum_id=36326">archive</A>) and +<A href="http://lists.sourceforge.net/mailman/listinfo/linux-vax-usr-commit">userland tools</A> +(<A href="http://sourceforge.net/mailarchive/forum.php?forum_id=36275">archive</A>). -<table><tr><td width="300" valign="top"><font FACE="Helvetica, Arial" size=+1> +<table><tr><td width="300" valign="top"><font FACE="Helvetica, Arial" size=+1> This project would like to acknowledge the support of the following companies or organisations:</font></td> |
From: Jan-Benedict G. <jb...@us...> - 2005-05-30 13:10:31
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9646 Modified Files: newsframe.html Log Message: - Mention gcc-HEAD success with out 2.6.x kernel. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.10 retrieving revision 1.11 diff -u -d -r1.10 -r1.11 --- newsframe.html 25 Mar 2005 11:14:48 -0000 1.10 +++ newsframe.html 30 May 2005 13:10:22 -0000 1.11 @@ -13,6 +13,20 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>29 May 2005</TD> + <TD> + <B>Toolchain</B>, <B>Kernel</B><BR> + With a toolchain generated by the + <TT>toolchain/scripts/build_toolchain.sh</TT> + script Kenn managed to fix our 2.6.x based + kernel to boot into userspace with a really + really up-to-date gcc. (Our old compiler is + based on a snapshot which is more than five + years old.) All fixes are already checked in. + This is a major milestone! + </TD> + </TR> + <TR> <TD>21 Mar 2005</TD> <TD> <B>Kernel</B><BR> |
From: Kenn H. <ke...@us...> - 2005-04-07 22:57:14
|
Update of /cvsroot/linux-vax/www/htdocs/docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2554/htdocs/docs Modified Files: README Log Message: Latest Makefile check-in means we need to put ARCH=vax on the make command lines Index: README =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/docs/README,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- README 6 Apr 2005 07:25:28 -0000 1.4 +++ README 7 Apr 2005 22:57:05 -0000 1.5 @@ -97,7 +97,7 @@ cd into the kernel dir created by cvs and do - $ make oldconfig + $ make ARCH=vax oldconfig to create a default .config. (Beware about playing with the config too much, as it might break the compile, obviously there @@ -107,24 +107,17 @@ Compile a network-bootable image by doing - $ make mopboot + $ make ARCH=vax mopboot This will generate plenty of compiler and linker warnings, but you should 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 - - $ make mopbootx - - 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 - $ make diskboot && dd if=vmlinux.dsk of=/dev/sdX + $ make ARCH=vax diskboot && dd if=vmlinux.dsk of=/dev/sdX and then tell your VAX to boot from this disk. This is faster than netbooting. |
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. + |
From: Jan-Benedict G. <jb...@us...> - 2005-03-25 11:15:01
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23694 Modified Files: newsframe.html Log Message: - Mention the recent 2.6.10 import. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -d -r1.9 -r1.10 --- newsframe.html 20 Nov 2004 14:55:48 -0000 1.9 +++ newsframe.html 25 Mar 2005 11:14:48 -0000 1.10 @@ -13,6 +13,14 @@ </THEAD> <TBODY valign="top" align="left"> <TR> + <TD>21 Mar 2005</TD> + <TD> + <B>Kernel</B><BR> + 2.6.10 was imported into the CVS repository + by Kenn. + </TD> + </TR> + <TR> <TD>20 Nov 2004</TD> <TD> <B>Kernel</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2004-11-20 14:55:57
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15359 Modified Files: newsframe.html Log Message: - Mention 2.6.9 being imported. - @Kenn: Do you push it to the web server? (Maybe send me a script of it?) Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.8 retrieving revision 1.9 diff -u -d -r1.8 -r1.9 --- newsframe.html 23 Sep 2004 23:01:43 -0000 1.8 +++ newsframe.html 20 Nov 2004 14:55:48 -0000 1.9 @@ -12,7 +12,15 @@ </TR> </THEAD> <TBODY valign="top" align="left"> - <TR valign="top" align="left"> + <TR> + <TD>20 Nov 2004</TD> + <TD> + <B>Kernel</B><BR> + 2.6.9 was imported into the CVS repository + and it seems all issues are now resolved. + Enjoy! + </TD> + </TR> <TR> <TD>24 Sep 2004</TD> <TD> |
From: Jan-Benedict G. <jb...@us...> - 2004-09-23 23:01:52
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6694 Modified Files: newsframe.html Log Message: - Mention ODS-2 driver. Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -d -r1.7 -r1.8 --- newsframe.html 23 Jul 2004 12:57:23 -0000 1.7 +++ newsframe.html 23 Sep 2004 23:01:43 -0000 1.8 @@ -13,6 +13,19 @@ </THEAD> <TBODY valign="top" align="left"> <TR valign="top" align="left"> + <TR> + <TD>24 Sep 2004</TD> + <TD> + <B>Kernel</B><BR> + We've now got a driver for VMS' ODS-2 + filesystem which was initially written + by Jonas Lindholm and now forward-ported + to 2.6.x. It basically works, but needs + some more testing (ie. verify if file's + time stamps are correct compared to VMS). + </TD> + </TR> + <TR> <TD>22 Jul 2004</TD> <TD> <B>Info</B><BR> |
From: Jan-Benedict G. <jb...@us...> - 2004-07-23 12:57:34
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2062 Modified Files: newsframe.html Log Message: - Mention *preliminary* dates for the Developer's Meeting at Oldenburg(.de). Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -d -r1.6 -r1.7 --- newsframe.html 22 Jul 2004 20:31:44 -0000 1.6 +++ newsframe.html 23 Jul 2004 12:57:23 -0000 1.7 @@ -19,7 +19,8 @@ Jan-Benedict Glaw is to show up with a 3100/78, a 4000/60 and a 4000/90 at the Developer's Meeting in Oldenburg, - Germany. TODO: network on 3100/78, + Germany. (Current plan is from Sep. 22 to + Sep 26.) TODO: network on 3100/78, get 4000/90 to fully boot (currently no timer interrupts, so it stops during calculating delay loop...). And I want to learn more |
From: Jan-Benedict G. <jb...@us...> - 2004-07-22 20:31:55
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv24522 Modified Files: newsframe.html Log Message: - Mention toolchain... Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- newsframe.html 22 Jul 2004 20:30:56 -0000 1.5 +++ newsframe.html 22 Jul 2004 20:31:44 -0000 1.6 @@ -22,7 +22,8 @@ Germany. TODO: network on 3100/78, get 4000/90 to fully boot (currently no timer interrupts, so it stops during calculating - delay loop...). Maybe others show up, too? + delay loop...). And I want to learn more + about gcc and glibc. Maybe others show up, too? <P> Oh, sorry for not putting any news online since, um, sooo long... |
From: Jan-Benedict G. <jb...@us...> - 2004-07-22 20:31:05
|
Update of /cvsroot/linux-vax/www/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23982 Modified Files: newsframe.html Log Message: - Drop all the bloated HTML. - Add a note that I'm going to go to the Developer's Meeting in Oldenburg, Germany. If you can manage to come to Oldenburg (the plan is Sep 22.-26.), please do so!!! Index: newsframe.html =================================================================== RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- newsframe.html 31 May 2002 07:35:53 -0000 1.4 +++ newsframe.html 22 Jul 2004 20:30:56 -0000 1.5 @@ -1,353 +1,377 @@ -<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica"> -<TABLE CELLSPACING=0 CELLPADDING=0 COLS=1 WIDTH="690" BGCOLOR="#990033" NOSAVE > -<TR NOSAVE> -<TD NOSAVE><B><FONT FACE="Arial,Helvetica"><FONT COLOR="#FFFFFF"><FONT SIZE=+2>News</FONT></FONT></FONT></B> -<TABLE CELLSPACING=0 CELLPADDING=0 COLS=1 WIDTH="100%" HEIGHT="100%" BGCOLOR="#FFFFFF" NOSAVE > -<TR NOSAVE> -<TD NOSAVE> -<TABLE WIDTH="100%" NOSAVE > -<TR NOSAVE> -<TD WIDTH="15%" NOSAVE></TD> - -<TD VALIGN=TOP NOSAVE></TD> -</TR> -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>31 May 2002</TD> - -<TD NOSAVE> -The SGEC Ethernet driver is now functional. VXT2000's -and uVax3100's using the card should now be able to netboot -their machines. Get the latest version from CVS and make -sure you enable the SGEC in your kernel config. -<P> -</td> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>24 Sep 2001</TD> - -<TD NOSAVE> -The old FTP site is no more. A copy has been saved at -<a href="http://www.pergamentum.com/~atp/vax/old_ftp/"> -http://www.pergamentum.com/~atp/vax/old_ftp/</a> But its -pretty much out of date. New stuff is at the download link -off the main page. -<P> -</td> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>01 Apr 2002</TD> - -<TD NOSAVE> -(Andy Phillips) Kernel version now up to 2.4.14. Work progressing towards -keeping current with a view to merging in 2.5.x. Dave is tackling the -port of glibc3, with a view to shared libraries. -<P> -</td> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>23 Sep 2001</TD> - -<TD NOSAVE> -A new root image has been posted to the download area. -This contains instructions and prebuilt kernels for some -VAXstatsions, and should allow (with some self assembly) -most people to enjoy the bleeding edge of Linux/VAX -development. -<P> -</td> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>20 Sep 2001</TD> - -<TD NOSAVE> -Updated Website with more useful information. 3100/30,38,76's -working - mostly. There is a first cut bootloader for the above, -called "Andy's Scsi Boot loader", or asbl. -<P> -</td> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>24 Jun 2001</TD> - -<TD NOSAVE> -Mopd, uLibc and busybox now in CVS. -<P> -</td> -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>16 JUNE 2001</TD> - -<TD NOSAVE> -<B>Kernel</B><BR> -Kernel boots to shell prompt and forks properly... more details and bootlog -in <A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/1056.html"> -this message</A> <P> -<P> -</td> -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>11 JUNE 2001</TD> - -<TD NOSAVE> -<B>Kernel</B><BR> -Got a shell prompt (busybox + uClibc static) !!!!! -<A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/1033.html"> -this message</A> has more info...<P> -Complete bootlog and more information will be available soon. -<P> -</td> -</TR> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>21 FEB 2001</TD> - -<TD NOSAVE> -<B>Kernel</B><BR> -Mounted a root filesystem for the first time tonight! See -<A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/0788.html"> -this message</A> for the proof... -<P> -This build is tagged as kh-20010221. -</td> -</TR> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>20 FEB 2001</TD> - -<TD NOSAVE> -<B>Kernel</B><BR> -Things are going pretty well right now. We're now working off the -official 2.4.0 kernel. Next I'll merge in 2.4.1. We intend to -track the 2.4.x series at least until 2.5 starts. Don't know -which way we'll go at that point yet... -<P> -Andy's pagelet layer is in place, making the -main kernel think we really have 4K pages, when we really only have -512-byte pages. (Sssh! Don't tell it...). Good work Andy! -<P> -Richard Banks has started trying it out on a MicroVAX 3100 Model 85 -(KA55 CPU) and, well, it's just not working... My best guess is -that the PCB needs to be set up correctly before turning on virtual -memory. I'll get to that real soon now, Richard. Honestly... -<P> -Anyway, I've tagged a build as kh-20010220 in CVS. You can see -the default configuration (i.e. rm .config && make oldconfig) booting -on a -<A HREF="bootlogs/bootlog-kenn-vs3100m76-20010220.txt"> -VAXstation 3100 Model 76</A> and a -<A HREF="bootlogs/bootlog-kenn-vs4000m60-20010220.txt"> -VAXstation 4000 Model 60</A>. Thanks for the 4000/60, Andy! -(Incidentally, those BOOTP transmission attempts in the VS3100 -bootlog are not actually putting packets on the wire.) -<P> -<B>Toolchain</B><BR> -You will need the 20001231 toolchain to build this kernel. -You can get it from CVS or grab snapshots from -<A HREF="ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/Binaries/"> -the FTP site</A>. -</td> -</TR> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>31 DEC 2000</TD> - -<TD NOSAVE> -<B>Kernel</B><BR> -Some reasonable progress recently. Check out this -<A HREF="bootlogs/bootlog-kenn-vs3100-20001231.txt">boot sequence</A> -on my VS3100m76. The LANCE ethernet chip, one of the NCR5380 SCSI -controllers, the internal SCSI disk and it's partitions are -detected. The usual bunch of initial kernel threads are created -and you can see the scheduler switching between them while it -waits for an interrupt from the disk. -<P> -I've tagged this build as kh-20001231. -<P> -Unfortunately, getting further is going to be a bit more difficult. -I'm starting to run into problems due to our small PAGE_SIZE, that -won't be easy to get around. Following discussions with Andy, I'm -going to start working on 2.4 which should make things easier for -us. -<P> -<B>Toolchain</B><BR> -I've CVS tagged a toolchain build as tools-linuxvax-20001231. -Real soon now, I'll be checking in a kernel change that will -require this new toolchain. So now might be a good time to -cvs update and rebuild. -<P> -You <EM>don't</EM> need this latest toolchain to build kh-20001231. -The 20000808 release should work fine. -<P> -Oh yeah... Happy new year! - KPH -</td> -</TR> - -<!-- News entry boundary --> - -<TR VALIGN=TOP NOSAVE> -<TD>11 AUG 2000</TD> - -<TD NOSAVE> -<B>Toolchain</B><BR> -Snapshots of the gcc-2.95.2/binutils 2.10 toolchain -released, and available on the FTP site. Source and -Binary versions for Linux/i386 are provided, with -documentation to follow (honest). (atp) -</td> -</TR> - -<TR VALIGN=TOP NOSAVE> -<TD>07 AUG 2000</TD> - -<TD NOSAVE> -<B>Toolchain</B><BR> -Andy continues to work on the toolchain. Migration to gcc-2.95.2 seems -to be complete (at least it makes bootable kernels for me - Kenn). -He continues to work through the bugs. Hopefully we'll do a binary -snapshot of the toolchain soon, for those of you who don't want to -compile up your own tools.<BR> -<B>Kernel</B><BR> -Dave Airlie's LANCE ethernet driver for the VS3100-series machines -is starting to take shape. Well, it generates lots of output on -the console and then prints the ethernet address!<BR> -<B>Docs</B><BR> -Dave's also started on a proper <A HREF="linux-vax/newfaq/linux_vax.html"> -FAQ</A> generated from <A HREF="linux-vax/newfaq/linux_vax.sgml">these -SGML sources</A>. -</td> -</TR> - - -<TR VALIGN=TOP NOSAVE> -<TD>23 JUL 2000</TD> - -<TD NOSAVE> -<B>Toolchain</B><BR> -A newer binutils (version 2.10) has been checked into CVS. It seems to work -fine so far. Details in Andy's -<A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/0381.html"> -mail message</A>. <BR> -<B>Kernel</B><BR> -The interrupt and exception handling framework is complete. I hope... <BR> -Interrupt and exception handlers are all registered at run-time now. -It looks like autoprobing interrupt vectors will be possible too. -</td> -</TR> - -<TR VALIGN=TOP NOSAVE> -<TD>14 JUL 2000</TD> - -<TD NOSAVE> -<B>Website</B><BR> -The website is now updated via CVS. The pages are pulled -from CVS hourly.<BR> -Out of date <A HREF="linux-vax/docs.html">documentation</A> has been -removed and replaced with a link to current docs.<BR> -<B>Kernel</B><BR> -We're getting further slowly. <A HREF="bootlogs/bootlog-kenn-vs3100-20000714.txt">Here</A> -is Kenn's VAXstation 3100 booting the latest kernel. The framework for handling -interrupts is taking shape... -</td> -</TR> - -<TR VALIGN=TOP NOSAVE> -<TD>23 FEB 2000</TD> - -<TD NOSAVE>Web site has moved to <a -href="http://sourceforge.net/projects/linux-vax">SourceForge</a> Expect some broken links and -general randomness as we iron out bugs. -</td> -</TR> - -<TR VALIGN=TOP NOSAVE> -<TD>18 FEB 2000</TD> - -<TD NOSAVE>This project is moving to sourceforge, in order to speed up -access to the software and to allow people aside from me to manage the web site. -<BR>New release this weekend. </TD> -</TR> - -<TR VALIGN=TOP NOSAVE> -<TD>01 FEB 99</TD> - -<TD>New snapshots at the http link. Old packages are still available under -the "old" directory. A mopd, this time including the loop.c fix, has been -put up as well. Whilst I'm away patches and new releases can be found on -Kenn's site at <A HREF="http://www.bluetree.ie/~kenn/linux-vax/">www.bluetree.ie</A></TD> -</TR> - -<TR VALIGN=TOP NOSAVE> -<TD>24 OCT 99</TD> - -<TD> -<OL> -<LI> -All the vaxes have arrived. The only problem now is that as a result of -moving jobs and house, they are all in storage.</LI> - -<LI> -The mailing list has moved. The new details are below.</LI> - -<LI> -If you were on the old linux-vax list, you will have to re-subscribe, as -the list of members was not saved.</LI> - -<LI> -I am about to depart to a desert island (with no internet access) for several -months. I'll try to update documentation and the web site before I go.</LI> - -<LI> -Simplified web pages a bit. Amazing how being on a DECstation running NetBSD -with a 33.6 dialup instead of a T1 can lead to a lack of patience with -useless graphics.</LI> -</OL> -</TD> -</TR> - -<TR VALIGN=TOP NOSAVE> -<TD NOSAVE>25 JUL 99</TD> +<HTML> + <HEAD> + <TITLE>VAX-Linux News</TITLE> + </HEAD> + <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica"> + <TABLE border="1"> + <THEAD> + <TR BGCOLOR="#990033"> + <TH colspan="2"> + <BIG><B><EM>News</EM></B></BIG> + </TH> + </TR> + </THEAD> + <TBODY valign="top" align="left"> + <TR valign="top" align="left"> + <TD>22 Jul 2004</TD> + <TD> + <B>Info</B><BR> + Jan-Benedict Glaw is to show up with + a 3100/78, a 4000/60 and a 4000/90 + at the Developer's Meeting in Oldenburg, + Germany. TODO: network on 3100/78, + get 4000/90 to fully boot (currently no timer + interrupts, so it stops during calculating + delay loop...). Maybe others show up, too? + <P> + Oh, sorry for not putting any news online + since, um, sooo long... + </TD> + </TR> + <TR> + <TD>31 May 2002</TD> + <TD> + <B>Kernel</B><BR> + The SGEC Ethernet driver is now functional. + VXT2000's and uVax3100's using the card + should now be able to netboot their machines. + Get the latest version from CVS and make sure + you enable the SGEC in your kernel config. + </TD> + </TR> + <TR> + <TD>24 Sep 2002</TD> + <TD> + <B>Info</B><BR> + The old FTP site is no more. A copy has been + saved at + <A href="http://www.pergamentum.com/~atp/vax/old_ftp/"> + http://www.pergamentum.com/~atp/vax/old_ftp/</a>. But + it's pretty much out of date. New stuff is at the + download link off the main page. + </TD> + </TR> + <TR> + <TD>01 Apr 2002</TD> + <TD> + <B>Kernel</B><BR> + (Andy Phillips) Kernel version now up to 2.4.14. + Work progressing towards keeping current with a + view to merging in 2.5.x. Dave is tackling the + port of glibc3, with a view to shared libraries. + </TD> + </TR> + <TR> + <TD>23 Sep 2001</TD> + <TD> + <B>Userland</B><BR> + A new root image has been posted to the download + area. This contains instructions and prebuilt + kernels for some VAXstatsions, and should allow + (with some self assembly) most people to enjoy + the bleeding edge of Linux/VAX development. + </TD> + </TR> + <TR> + <TD>20 Sep 2001</TD> + <TD> + <B>Kernel</B><BR> + Updated Website with more useful information. + 3100/30,38,76's working - mostly. There is a + first cut bootloader for the above, called + "Andy's Scsi Boot loader", or asbl. + </TD> + </TR> + <TR> + <TD>24 Jun 2001</TD> + <TD> + <B>Userland</B><BR> + Mopd, uLibc and busybox now in CVS. + </TD> + </TR> + <TR> + <TD>16 Jun 2001</TD> + <TD> + <B>Kernel</B><BR> + Kernel boots to shell prompt and forks + properly... more details and bootlog in + <A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/1056.html"> + this message</A>. + </TD> + </TR> + <TR> + <TD>11 Jun 2001</TD> + <TD> + <B>Kernel</B><BR> + Got a shell prompt (busybox + uClibc + static)!!!!! + <A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/1033.html"> + this message</A> has more info... Complete + bootlog and more information will be + available soon. + </TD> + </TR> + <TR> + <TD>21 Feb 2001</TD> + <TD> + <B>Kernel</B><BR> + Mounted a root filesystem for the first + time tonight! See + <A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/0788.html"> + this message</A> for the proof... This + build is tagged as kh-20010221. + </TD> + </TR> + <TR> + <TD>20 Feb 2001</TD> + <TD> + <B>Kernel</B><BR> + Things are going pretty well right now. + We're now working off the official 2.4.0 + kernel. Next I'll merge in 2.4.1. We + intend to track the 2.4.x series at + least until 2.5 starts. Don't know which + way we'll go at that point yet... + <P> + Andy's pagelet layer is in place, making + the main kernel think we really have 4K + pages, when we really only have 512-byte + pages. (Sssh! Don't tell it...). Good + work Andy! + <P> + Richard Banks has started trying it out + ion a MicroVAX 3100 Model 85 (KA55 CPU) + and, well, it's just not working... My + best guess is that the PCB needs to be + set up correctly before turning on virtual + memory. I'll get to that real soon now, + Richard. Honestly... + <P> + Anyway, I've tagged a build as kh-20010220 + in CVS. You can see the default configuration + (i.e. rm .config && make oldconfig) + booting on a + <A HREF="bootlogs/bootlog-kenn-vs3100m76-20010220.txt"> + VAXstation 3100 Model 76</A> and a + <A HREF="bootlogs/bootlog-kenn-vs4000m60-20010220.txt"> + VAXstation 4000 Model 60</A>. Thanks for + the 4000/60, Andy! (Incidentally, those + BOOTP transmission attempts in the VS3100 + bootlog are not actually putting packets + on the wire.) + <P> + <B>Toolchain</B><BR> + You will need the 20001231 toolchain to + build this kernel. You can get it from CVS + or grab snapshots from + <A HREF="ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/Binaries/"> + the FTP site</A>. + </TD> + </TR> + <TR> + <TD>31 Dec 2000</TD> + <TD> + <B>Kernel</B><BR> + Some reasonable progress recently. Check + out this + <A HREF="bootlogs/bootlog-kenn-vs3100-20001231.txt"> + boot sequence</A> on my VS3100m76. The LANCE + ethernet chip, one of the NCR5380 SCSI controllers, + the internal SCSI disk and it's partitions are + detected. The usual bunch of initial kernel threads + are created and you can see the scheduler switching + between them while it waits for an interrupt from + the disk. + <P> + I've tagged this build as kh-20001231. + <P> + Unfortunately, getting further is going to be a bit + more difficult. I'm starting to run into problems + due to our small PAGE_SIZE, that won't be easy to + get around. Following discussions with Andy, I'm + going to start working on 2.4 which should make + things easier for us. + <P> + <B>Toolchain</B><BR> + I've CVS tagged a toolchain build as + tools-linuxvax-20001231. Real soon now, I'll be + checking in a kernel change that will require + this new toolchain. So now might be a good time + tocvs update and rebuild. + <P> + You <EM>don't</EM> need this latest toolchain to + build kh-20001231. The 20000808 release should + work fine. + <P> + Oh yeah... Happy new year! - KPH + </TD> + </TR> + <TR> + <TD>11 Aug 2000</TD> + <TD> + <B>Toolchain</B><BR> + Snapshots of the gcc-2.95.2/binutils-2.10 + toolchain released, and available on the FTP + site. Source and binary versions for + Linux/i386 are provided, with documentation + to follow (honest). (atp) + </TD> + </TR> + <TR> + <TD>07 Aug 2000</TD> + <TD> + <B>Toolchain</B><BR> + Andy continues to work on the toolchain. + Migration to gcc-2.95.2 seems to be complete + (at least it makes bootable kernels for + me - Kenn). He continues to work through the + bugs. Hopefully we'll do a binary snapshot of + the toolchain soon, for those of you who + don't want to compile up your own tools. + <P> + <B>Kernel</B><BR> + Dave Airlie's LANCE ethernet driver for the + VS3100-series machines is starting to take + shape. Well, it generates lots of output on + the console and then prints the ethernet + address!<BR> + <B>Info</B><BR> + Dave's also started on a proper + <A HREF="linux-vax/newfaq/linux_vax.html"> + FAQ</A> generated from + <A HREF="linux-vax/newfaq/linux_vax.sgml"> + these SGML sources</A>. + </TD> + </TR> + <TR> + <TD>23 Jul 2000</TD> + <TD> + <B>Toolchain</B><BR> + A newer binutils (version 2.10) has been + checked into CVS. It seems to work fine so + far. Details in Andy's + <A HREF="http://solar.physics.montana.edu/hypermail/linux-vax/0381.html"> + mail message</A>. + <P> + <B>Kernel</B><BR> + The interrupt and exception handling framework + is complete. I hope... + <P> + Interrupt and exception handlers are all + registered at run-time now. It looks like + autoprobing interrupt vectors will be + possible too. + </TD> + </TR> + <TR> + <TD>14 Jul 2000</TD> + <TD> + <B>Info</B><BR> + The website is now updated via CVS. The pages + are pulled from CVS hourly. + <P> + Out of date + <A HREF="linux-vax/docs.html">documentation</A> + has been removed and replaced with a link to + current docs.<P> + <B>Kernel</B><BR> + We're getting further slowly. + <A HREF="bootlogs/bootlog-kenn-vs3100-20000714.txt"> + Here</A> is Kenn's VAXstation 3100 booting the + latest kernel. The framework for handling + interrupts is taking shape... + </TD> + </TR> + <TR> + <TD>23 Feb 2000</TD> + <TD> + <B>Info</B><BR> + Web site has moved to + <a href="http://sourceforge.net/projects/linux-vax"> + SourceForge</a> Expect some broken links and + general randomness as we iron out bugs. + </TD> + </TR> + <TR> + <TD>18 Feb 2000</TD> + <TD> + <B>Info</B><BR> + This project is moving to sourceforge, in order + to speed up access to the software and to allow + people aside from me to manage the web site. + <P> + New release this weekend. + </TD> + </TR> + <TR> + <TD>01 Feb 1999</TD> + <TD> + <B>Info</B><BR> + New snapshots at the http link. Old packages + are still available under the "old" + directory. A mopd, this time including the + loop.c fix, has been put up as well. Whilst + I'm away patches and new releases can be found + on Kenn's site at + <A HREF="http://www.bluetree.ie/~kenn/linux-vax/"> + http://www.bluetree.ie</A> + </TD> + </TR> + <TR> + <TD>24 Oct 1999</TD> + <TD> + <B>Info</B><BR> + <OL> + <LI>All the vaxes have arrived. The + only problem now is that as a result of + moving jobs and house, they are all + in storage.</LI> -<TD>New snapshots for things at the download link. -<BR>Linux C code now compiles. Pretty much all of arch-dependent stuff -to do -<BR>(or redo) still. I'm acquiring the rest of the VAX hardware I need -tomorrow. -<BR>Still dont know where to store it ...</TD> -</TR> -</TABLE> -</TD> -</TR> -</TABLE> -</TD> -</TR> + <LI>The mailing list has moved. The new + details are below.</LI> -</table> -<SCRIPT> -<!-- -document.write("<font size=-1>Last modified "+document.lastModified+"</font>"); -// --> -</SCRIPT> + <LI>If you were on the old linux-vax + list, you will have to re-subscribe, as + the list of members was not saved.</LI> + <LI>I am about to depart to a desert + island (with no internet access) for + several months. I'll try to update + documentation and the web site before + I go.</LI> + <LI>Simplified web pages a bit. Amazing + how being on a DECstation running NetBSD + with a 33.6 dialup instead of a T1 can + lead to a lack of patience with useless + graphics.</LI> + </OL> + </TD> + </TR> + <TR> + <TD>25 Jul 1999</TD> + <TD> + <B>Info</B><BR> + New snapshots for things at the download + link. + <P> + Linux C code now compiles. Pretty much all + of arch-dependent stuff to do (or redo) still. + I'm acquiring the rest of the VAX hardware I + need tomorrow. + <P> + Still dont know where to store it ... + </TD> + </TR> + </TBODY> + </TABLE> + <BR> + <SMALL> + <SCRIPT> + <!-- + document.write("Last modified: " + document.lastModified); + --> + </SCRIPT> + </SMALL> </BODY> - +</HTML> |