public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Andersen <bryan@bogonomicon.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: zImage now holds vmlinux, System.map and config in sections. (fwd)
Date: Tue, 25 Feb 2003 16:00:01 -0600	[thread overview]
Message-ID: <3E5BE761.8030202@bogonomicon.net> (raw)
In-Reply-To: 20030225120357.GC158866@niksula.cs.hut.fi


>>I, for one, do not see any point in trying to put more and more crap
>>into one file, when its perfectly easy to just use the "cp" command

> Not everybody are always that careful. I know I'm not. I've copied tens of
> kernels to floppy ("cp bzImage /dev/fd0" because it's so easy to do), and
> lost track which one is which. I've copied kernels to other computers, and
> lost track which is which. I've made mistakes copying kernels to /boot, and
> lost track which is which.

These problems are why I now always use shell scripts to do the steps 
that always need to be done.  If I did the steps by hand I'd make a 
mistake atleast once in five times.  I use the standard "make 
modules_install install" to do the kernel install.  I use shell scripts 
to make the kernel and modules before the install and to build and 
install all the nVidia modules after.  This allows me to test a new 
kernel much faster and with much less effort while not forgetting steps 
along the way.  The shell scripts don't need to be all that fancy.  Most 
often the same commands I would type in at the command line.  The one 
that builds and installs the nVidia stuff is just a bunch of cds to 
directories then the make or make install with a "|| exit 2" for exiting 
on failres.  The lines are of the form:

   cd {directory} && make {optional arg} || exit {#}

Areas in {} are replaced with the appropriate values.  The "|| exit" 
code is important because bash will normally continue on when a command 
fails.

- Bryan




  parent reply	other threads:[~2003-02-25 21:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  6:28 zImage now holds vmlinux, System.map and config in sections. (fwd) Mikael Starvik
2003-02-25  9:25 ` Russell King
2003-02-25 11:07   ` Ville Herva
2003-02-25 11:35     ` Russell King
2003-02-25 12:03       ` Ville Herva
2003-02-25 14:34         ` Jeremy Jackson
2003-02-26 18:41           ` Peter Bergner
2003-02-25 22:00         ` Bryan Andersen [this message]
2003-02-25 12:50       ` Remco Post
2003-02-25 13:35         ` Russell King
2003-02-25 16:38       ` Randy.Dunlap
2003-02-25 17:52         ` Russell King
2003-02-26 20:01           ` Todd Inglett
2003-02-26 20:45             ` Peter Bergner
2003-02-25 19:22         ` Ville Herva
2003-02-25 16:23   ` Randy.Dunlap
2003-02-25 20:00   ` H. Peter Anvin
2003-02-25 21:24     ` Russell King
2003-02-25 21:52       ` H. Peter Anvin
2003-02-25 23:21 ` Magnus Danielson
     [not found] <Pine.LNX.4.33.0302241010200.1088-100000@localhost.localdomain>
2003-02-24 19:58 ` Randy.Dunlap

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=3E5BE761.8030202@bogonomicon.net \
    --to=bryan@bogonomicon.net \
    --cc=linux-kernel@vger.kernel.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