On Fri, Jan 21, 2005 at 02:41:29PM -0600, Paul Larson wrote:
> 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.
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.
> > 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.
you can find the last vmlinuz-2.6.*-xen0 installed with a command like
this:
ls -t dist/install/boot/vmlinuz-2.6.*-xen0 | head -1
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)
[ -e "$l" ] && ln -fs "$l" vmlinuz${v}-xen0
done
You can even add another echo '2.*.*' '' if you want to get a link
vmlinuz-xen0 pointing to the last xen0 (2.4 or 2.6) installed, but
I think that's not a good idea because it can have very unexpected
behaviour.
christian
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home