From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: [PATCH] (revised slightly) create kernel symlinksin /boot Date: Fri, 21 Jan 2005 20:19:28 +0000 Message-ID: <20050121201928.GL14221@cl.cam.ac.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Ian Pratt Cc: Paul Larson , Adam Heath , xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Jan 21, 2005 at 07:47:08PM -0000, Ian Pratt wrote: > > > > bzzt. What if /boot and $(INSTALL_DIR)/boot are different > > partitions? > > Oops, forgot to change that, fixed. Needless to say, most of my boxes > > have a pretty flat filesystem :) > > What's wrong with: > ln -s vmlinuz-$(FULLVERSION) $(INSTALL_DIR)/boot/vmlinuz-$(EXTRAVERSION) > > In any event, wouldn't it be better to have a link from e.g. > > vmlinux-2.6-xen0 -> vmlinuz-2.6.10-xen0 etc? > > Am I missing the point of what you're proposing? 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. Also all the ln -s solutions fail if you build twice, you'd need at least ln -fs. 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. 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