Date: Mon, 2 Aug 2004 09:08:29 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Josef El-Rayes <josef@freebsd.org> Cc: freebsd-ia64@freebsd.org Subject: Re: boot installed freebsd Message-ID: <20040802160829.GB2366@dhcp50.pn.xcllnt.net> In-Reply-To: <20040802134019.GA27996@daemon.li> References: <20040802134019.GA27996@daemon.li>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 02, 2004 at 01:40:19PM +0000, Josef El-Rayes wrote: > hi! > > i just successfully installed the latest freebsd-ia64 > snapshot and i was wondering how i add it into the > efi boot manager. i read about giving the EFI partition > a mount point (in the mailinglist archive) but which > mount point? i gave it /boot (the additional partitions > and mountpoints where set up with 'A' (auto settings)) > but then sysinstall complained about '/mnt/boot too many symlinks'. > i also looked for the boot/loader.efi file, as i saw > in the archive but i was not able to find one. Typically we put the contents of /boot on the EFI partition. That way the loader, kernel and configuration files are accessable under EFI. For this to work, we made /boot a symlink to where we actually want it. So, if you make the EFI partition mounted under /efi, then the installer will create a symlink /boot -> /efi/boot. However, there's currently a problem with the installer. It doesn't actually mount the EFI partition before installing, so all the /boot contents end up on the UFS root partition and not where we want it: the EFI partition. For now, use the CD to boot into FreeBSD and correct it by hand. This should explain why using /boot as the EFI mount point gives the error you're getting. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040802160829.GB2366>