hello steve, thanks for the explanations. On Mon, 12 Apr 2004, Steve Langasek wrote: > If the base system has installed successfully (and it won't with current > images on alpha), the aboot installer should be run automatically. waiting for a bug closure for some more testing, on the mailinglist i saw an upload of a new kernel, so i hope the scsi bug is resolved. (allthough #237884 is still pending, marcelo added a stxcpy fix to 2.4.26-rc3 as did linus in current) > Can you be more specific regarding the "strange lseek error"? It sounds > below like aboot was successfully installed to your hard drive, so it > may not be a problem. the lseek error occurred while executing abootconf /dev/sda 2 after installing the debian packages out of /var/cache/apt/archives by hand inside the chroot and leaving it. (don't remember the exact wording .. but can retry nexttime) therefor used swriteboot to install aboot on the hard drive. > Did you specify an initrd option on your boot line? The kernels shipped > with Debian have only minimal filesystem support compiled in -- you will > need the initrd to be able to mount your root filesystem. used the initrd option but forgot to put a /etc/aboot.conf inside of this root filesystem perhaps thats fatal? regards maks
Attachment:
signature.asc
Description: Digital signature