From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: [PATCH] Guest boot loader support Date: Tue, 26 Apr 2005 15:24:30 -0500 Message-ID: <426EA37E.5070102@us.ibm.com> References: <1114469427.4336.42.camel@bree.local.net> <1114534871.18436.7.camel@bree.local.net> <9cde8bff05042612371682e511@mail.gmail.com> <200504262048.24728.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200504262048.24728.mark.williamson@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Williamson Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Mark Williamson wrote: >>ok, i see the point. >> >>other question: pygrub::get_config(fn) tries to read >>"/boot/grub/grub.conf". Normally this should be "/boot/grub/menu.lst". >>I wonder which distro are you working on? > > My FC3 box has menu.lst as a symlink to grub.conf. Grub seems to be happy > with either of these names. Painful experience suggests that if both files > are present, then "menu.lst" will "win". GRUB only looks for menu.lst; distros create symlinks because that's a terrible name for a config file. In other words, no code should be opening grub.conf... -- Hollis Blanchard IBM Linux Technology Center