All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Larson <plars@linuxtestproject.org>
To: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	Adam Heath <doogie@brainfood.com>,
	xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: [PATCH] (revised slightly) create kernel symlinksin /boot
Date: Fri, 21 Jan 2005 14:41:29 -0600	[thread overview]
Message-ID: <1106340090.8950.226.camel@localhost.localdomain> (raw)
In-Reply-To: <20050121201928.GL14221@cl.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

On Fri, 2005-01-21 at 20:19 +0000, Christian Limpach wrote:
> I think we shouldn't have a link at all, ideally a distribution's package
> installer will create the links which work with the distribution's
> bootloader configuration/setup.
The problem for me right now, is that the kernel doesn't have a
predictable name when you are rebuilding it automatically.  So when you
do a 'make world install' and the new kernel gets installed, then you
might actually be on a newer kernel version and your grub entry is now
invalid.

> Also all the ln -s solutions fail if you build twice, you'd need at least
> ln -fs.
Good idea.

> If we must have a link, then I think it should be created as part of
> install.sh since that at least is less likely to get run when building
> packages.
It certainly would be preferable to do it there, but unfortunately
install.sh doesn't retain any knowledge of what kernel just got built.
All it does is copy the directory contents across.

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-21 20:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 19:47 [PATCH] (revised slightly) create kernel symlinksin /boot Ian Pratt
2005-01-21 20:19 ` Christian Limpach
2005-01-21 20:41   ` Paul Larson [this message]
2005-01-21 21:20     ` Christian Limpach
2005-01-21 21:29       ` Paul Larson
2005-01-24 23:06       ` Paul Larson
  -- strict thread matches above, loose matches on Subject: below --
2005-01-21 21:26 Ian Pratt

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=1106340090.8950.226.camel@localhost.localdomain \
    --to=plars@linuxtestproject.org \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=doogie@brainfood.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.