help-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: static linking and iso9660fs


From: Greg Buchholz
Subject: Re: static linking and iso9660fs
Date: Tue, 2 Sep 2003 19:30:50 +0100 (BST)

On Tue, 2 Sep 2003, Marco Gerards wrote:

> Why do you need this?  If you boot from an el torito bootable CDROM
> you can put GNUMach, isofs.static, ld.so and exec on the boot image
> (IIRC that is all that is needed).  But having GRUB reading the disk
> is the right way, but unfortunately it isn't supported by GRUB yet
> (officially).

        I haven't been able to get that to work so far.  Or, more
precisely, here's the latest failure I've had.  I make an El-Torito HD
image with a copy of grub, iso9660fs.static, and gnumach.gz on it.  This
boot image gets put inside the iso with the rest of the system on it.  My
grub "menu.lst" looks like this...

timeout 60
default 0
#Entry #0
title  GNU/Hurd
uppermem 523648
root   (hd0,0)
kernel /boot/gnumach.gz root=device:hd2s1
module /hurd/iso9660fs.static
--multiboot-command-line=${kernel-command-line}
--host-priv-port=${host-port} --device-master-port=${device-port}
--exec-server-task=${exec-task} -T typed ${root} $(task-create)
$(task-resume)
module /lib/ld.so.1 /hurd/exec $(exec-task=task-create)


...When the CD boots, grub starts up fine, and gnumach boots without
problem.  After Mach boots I get the following messages on screen...

2 multiboot modules

task loaded: /hurd/iso9660fs.static --multi-boot-command-line yada,yada...

task loaded: /lib/ld.so.1 /hurd/exec

start /hurd/iso9660fs.static: /hurd/iso9660fs.static: device: hd2s1:
Invalid argument


...I should also note that I've got two IDE harddisks (hd0,hd1) and two
IDE cd drives (hd2,hd3) in the system.  The "Invalid argument" occurs no
matter what drive I have specified on the...

kernel /boot/gnumach.gz root=device:hd2s1

...line.  I've tried hd0s1, hd0, hd2s1, hd2, etc.  My initial thought was
that this was caused by the cd drive not being recognized by grub or Mach
as a real disk.  But it could also be caused by iso9660fs.static not
understanding boot arguments correctly (although my initial impression
was iso9660fs.static just might work without needing modifications).
        Anyway, I'd thought I'd tackle the booting problem before I dive
into creating a hurdish ramdisk thingy.


Greg Buchholz




reply via email to

[Prev in Thread] Current Thread [Next in Thread]