Linux PARISC architecture development
 help / color / mirror / Atom feed
From: thunder7@xs4all.nl
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] 'Getting a parisc-linux cvs kernel without stress'
Date: Sun, 9 Sep 2001 14:26:52 +0200	[thread overview]
Message-ID: <20010909142652.A26291@middle.of.nowhere> (raw)
In-Reply-To: <20010907150709.B843@neep.com.au>

This is a small update/addition to the 'kernel-building recipe'.

============================================================
If you want to test the latest kernel and don't want to download the
enormous linux-latest.tar.gz file every time, use the cvs system to
get just the changed files. This is a very short manual how to do this
in 3 steps.  Obviously, step 1 and 2 are only needed once. Step 3 can be
repeated as you like.

Step 1 - create the right environment.

Make sure you have a variable 'CVSROOT' with value
CVSROOT=:pserver:anonymous@puffin.external.hp.com:/home/cvs/parisc

To make it available on every boot, put it in ~/.bashrc like this:

CVSROOT=:pserver:anonymous@puffin.external.hp.com:/home/cvs/parisc
export CVSROOT

Also create a .cvsrc file in your home directory with this content:

cvs -z3 -q
diff -uNp
update -Pd
remove -f

Also make sure you have cvs installed ('apt-get install cvs' if you have
not). Before going on to step 2, make sure the CVSROOT variable is
actually set - by logging out and logging in again.

Step 2 - prepare a linux source tree

Get linux-latest.tar.gz from the ftp-site, and untar. In this manual,
I'll user ~/source/ as directory untar in, but any directory will do.
Now you'll have to change some files in the source tree. Make sure your
CVSROOT variable is set correctly and type:

for i in `find linux -name Root`; do echo $CVSROOT > $i; done

Step 3 - get the latest source code

Change directory to ~/source/ and type

cvs update -APd linux

You should see a list of files looking something like this:

P linux/Makefile
P linux/Documentation/parisc/registers
P linux/arch/parisc/vmlinux.lds
P linux/arch/parisc/vmlinux64.lds
P linux/arch/parisc/hpux/fs.c

etc.

To make sure something has changed you can always do:

grep -i version linux/Makefile | head -2

which will answer 

VERSION = 2
EXTRAVERSION = -pa17

Now compile your new kernel as usual.
============================================================

This is by way of thanks to everyone who helped me to get it working,
and to possibly prevent other people from endless trying.

Good luck,
Jurriaan
-- 
Satan: "Welcome to hell - Here's your DoubleSpaced 386SX and windows"
GNU/Linux 2.4.9-ac10 SMP/ReiserFS 2x1402 bogomips load av: 0.31 0.08 0.02

      reply	other threads:[~2001-09-09 12:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 13:29 [parisc-linux] cvs update gives 'move away ....' on every file thunder7
2001-09-06  5:04 ` Grant Grundler
2001-09-06  5:18   ` Andrew Shugg
2001-09-06  5:35     ` thunder7
2001-09-06  6:08       ` Grant Grundler
2001-09-06 12:53         ` Matthew Wilcox
2001-09-06 19:14           ` thunder7
2001-09-07  7:07             ` Andrew Shugg
2001-09-09 12:26               ` thunder7 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010909142652.A26291@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox