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 15:29:13 -0600 [thread overview]
Message-ID: <1106342953.8950.231.camel@localhost.localdomain> (raw)
In-Reply-To: <20050121212008.GN14221@cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
On Fri, 2005-01-21 at 21:20 +0000, Christian Limpach wrote:
> Yes, but we don't change kernel versions that often and it's easy to
> fix this from grub's boot prompt should the old kernel no longer boot.
But by then, it's already failed, possibly in a very confusing way.
> How about adding this to install.sh:
> (run in dist/install/boot)
> (echo '2.6.*' -2.6; echo '2.4.*' -2.4) | while read m v
> do
> l=$(eval ls -t vmlinuz-$m-xen0 2>/dev/null | head -1)
only nitpick here is -n1 for head (some versions of head are picky about
that now)
Otherwise that works for me. The reason I'm looking for something like
this, is so that I can set up automated testing of xen nightly tarballs.
This would greatly simplify things, as well as help prevent others from
getting bit by the kernel upgrade thing.
--
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 --]
next prev parent reply other threads:[~2005-01-21 21:29 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
2005-01-21 21:20 ` Christian Limpach
2005-01-21 21:29 ` Paul Larson [this message]
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=1106342953.8950.231.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.