mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Oliver Xymoron <oxymoron@waste.org>,
	David Lang <dlang@diginsite.com>,
	Manfred Spraul <manfred@colorfullife.com>,
	"Albert D . Cahalan" <acahalan@cs.uml.edu>,
	lm@bitmover.com, linux-kernel@vger.kernel.org
Subject: Re: bug database braindump from the kernel summit
Date: Mon, 02 Apr 2001 18:09:05 -0400	[thread overview]
Message-ID: <3AC8F881.F20A19A6@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1010401181724.28121i-100000@mandrakesoft.mandrakesoft.com> <Pine.LNX.4.30.0104021436110.24812-100000@waste.org> <20010402234045.C17148@werewolf.able.es>

"J . A . Magallon" wrote:
> Could <installkernel> make part of the kernel scripts, or in one other
> standard software package, like modutils, so its versions are controlled

There is value in putting it into the Linux kernel source tree, in
linux/scripts dir.  But most vendors can and should take this script as
a sample, and customize it for their distro.  The Linux-Mandrake
installkernel script definitely gets touched every so often, and
decisions it makes, like updating lilo.conf or grub/menu.lst, or
autodetecting the boot loader, are definitely not to be applied for all
cases.

FWIW here is our /sbin/installkernel command line usage help text, to
give a glimpse of what it does and can do:

Usage: ${0##*/} -[lngarhcq] KERNEL_VERSION BOOTIMAGE MAPFILE

  -l:  Add a lilo entry
  -i:  Dont generate Initrd files           
  -n:  Don't launch lilo.
  -g:  Add a Grub entry.
  -d:  Don't autodetect boot loader.
  -a:  Autodetect boot loader.
  -r:  Features for RPM post install.
  -c:  Don't copy files.
  -q:  Be quiet.
  -h:  This help.


> I think the best solution would be to make /boot the 'official' place for
> kernels, the -X.Y.Z naming an standard, installkernel should save System.map
> and .config.

There will never be an official place to put this stuff, because that's
a distro policy decision.  A quick search just now reveals no reference
to /boot in the i386 Makefiles, and only a quick reference in the README
file.

> And you can add something like /proc/signature/map, /proc/signature/config,
> etc to md5-check if a certain file fits running kernel.

Additionally, everyone should remember: /proc is not a dumping ground :)

Ad-hoc naming like this has created the procfs namespace ugliness we
have now... let's not add to it unless we have to, and unless we have a
good idea of proper naming.

-- 
Jeff Garzik       | May you have warm words on a cold evening,
Building 1024     | a full moon on a dark night,
MandrakeSoft      | and a smooth road all the way to your door.

  reply	other threads:[~2001-04-02 22:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01 19:32 Manfred Spraul
2001-04-01 20:17 ` Albert D. Cahalan
2001-04-01 21:07   ` Jeff Garzik
2001-04-01 21:48     ` Manfred Spraul
2001-04-01 22:48       ` Jeff Garzik
2001-04-01 23:01         ` David Lang
2001-04-01 23:21           ` Jeff Garzik
2001-04-01 23:25             ` David Lang
2001-04-01 23:34               ` Jeff Garzik
2001-04-01 23:32                 ` David Lang
2001-04-01 23:44                   ` Jeff Garzik
2001-04-01 23:43                     ` David Lang
2001-04-02  0:26                       ` Ben Ford
2001-04-05 12:55                         ` Petr Baudis
2001-04-02 18:57                       ` Kai Henningsen
2001-04-02  5:26             ` Richard Russon
2001-04-02 21:35               ` Steven Walter
2001-04-02 19:39             ` Oliver Xymoron
2001-04-02 21:40               ` J . A . Magallon
2001-04-02 22:09                 ` Jeff Garzik [this message]
2001-04-02 22:24                   ` David Lang
2001-04-02 22:38                   ` J . A . Magallon
2001-04-02 23:04               ` Tom Leete
2001-04-02 23:12                 ` Oliver Xymoron
2001-04-02 23:24                   ` Jeff Garzik
2001-04-02 23:31                     ` Oliver Xymoron
2001-04-03 16:05                   ` Miles Lane
2001-04-02  1:49     ` Miles Lane
2001-04-01 20:59 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2001-04-01 22:34 Stephen Satchell
2001-04-02  8:00 ` Olaf Titz
2001-04-01 17:54 Larry McVoy
2001-04-01 19:43 ` Albert D. Cahalan
2001-04-01 20:21   ` Gregory Maxwell
2001-04-01 20:38     ` Albert D. Cahalan
2001-04-01 21:16 ` David Lang
2001-04-01 21:18   ` David Lang
2001-04-02  1:57   ` Miles Lane
2001-04-02  5:07     ` David Lang
2001-04-01 23:14 ` Jeff Garzik
2001-04-02 13:31 ` Rogier Wolff

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=3AC8F881.F20A19A6@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=acahalan@cs.uml.edu \
    --cc=dlang@diginsite.com \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=manfred@colorfullife.com \
    --cc=oxymoron@waste.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

all inboxes | Powered by JetHome®