From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: booting kernel of NetBSD (Re: UFS (FFS) support seems broken in grub2)
Date: Mon, 28 Jan 2008 14:00:27 +0100 [thread overview]
Message-ID: <87tzkym7f8.fsf@xs4all.nl> (raw)
In-Reply-To: <ca0f59980801280202l1bcfacfbye48053dc15f4c211@mail.gmail.com> (bean123ch@gmail.com's message of "Mon, 28 Jan 2008 18:02:37 +0800")
Bean <bean123ch@gmail.com> writes:
> On Jan 28, 2008 9:54 AM, walt <wa1ter@myrealbox.com> wrote:
>>
>> On Mon, 2008-01-28 at 04:25 +0800, Bean wrote:
>> ...
>> > > > please make a small ufs image containing the netbsd kernel, i don't a
>> > > > a bsd system at hand
>>
>> http://leaf.dragonflybsd.org/~wa1ter/ufs.gz
>>
>> I included a small text file (motd) to demonstrate that you can cat it
>> okay, but when you try 'multiboot /netbsd' you should get the same error
>> I've been describing.
>>
>>
>> > btw, if you have time, please try the a.out loader, it should be able
>> > to boot /boot/loader of freebsd, i don't know if openbsd and netbsd
>> > use the same booting method.
>>
>> diff --git a/conf/i386-pc.rmk b/conf/i386-pc.rmk
>>
>> Heh. I'm assuming an .rmk file involves ruby somehow? The bonehead
>> build process that I'm using doesn't turn an .rmk into a .mk AFAICT,
>> but I'd like to know how to do it.
>
> all you need to do is do install ruby.
>
> here is a patch for ufs, it fix the indirect block calculation problem.
>
> * fs/ufs.c (INODE_BLKSZ): Fix incorrect value.
> (grub_ufs_get_file_block): Fix indirect block calculation problem.
Fine for me, if you tested this.
This patch fixes this specific problem regarding loading this
multiboot kernel from UFS?
--
Marco
next prev parent reply other threads:[~2008-01-28 12:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 17:01 UFS (FFS) support seems broken in grub2 jakllsch
2008-01-19 18:27 ` walt
2008-01-22 18:58 ` Bean
2008-01-22 20:04 ` Robert Millan
2008-01-23 9:02 ` Marco Gerards
2008-01-23 16:15 ` walt
2008-01-23 16:31 ` Bean
2008-01-23 19:21 ` Marco Gerards
2008-01-23 20:26 ` Bean
2008-01-23 22:49 ` walt
2008-01-23 23:53 ` Robert Millan
2008-01-24 1:21 ` walt
2008-01-24 12:30 ` booting *BSD kernels (Re: UFS (FFS) support seems broken in grub2) Robert Millan
2008-01-24 8:33 ` UFS (FFS) support seems broken in grub2 Marco Gerards
2008-01-24 14:20 ` walt
2008-01-24 14:33 ` booting kernel of NetBSD (Re: UFS (FFS) support seems broken in grub2) Robert Millan
2008-01-24 14:53 ` Robert Millan
2008-01-24 16:47 ` walt
2008-01-24 17:12 ` Robert Millan
2008-01-26 15:01 ` Bean
2008-01-26 17:24 ` Robert Millan
2008-01-26 18:19 ` walt
2008-01-26 18:24 ` Bean
2008-01-26 18:31 ` Bean
2008-01-26 19:57 ` Robert Millan
2008-01-26 19:57 ` Robert Millan
2008-01-26 21:24 ` walt
2008-01-27 1:35 ` Bean
2008-01-27 20:13 ` walt
2008-01-27 20:25 ` Bean
2008-01-28 1:54 ` walt
2008-01-28 8:52 ` Robert Millan
2008-01-28 10:02 ` Bean
2008-01-28 13:00 ` Marco Gerards [this message]
2008-01-28 13:02 ` Bean
2008-02-02 14:16 ` Bean
2008-01-27 8:53 ` Robert Millan
2008-01-27 20:09 ` walt
2008-01-27 22:11 ` Robert Millan
2008-01-28 8:57 ` Marco Gerards
2008-01-28 10:06 ` Bean
2008-01-28 10:41 ` Robert Millan
2008-02-06 15:32 ` Robert Millan
2008-02-06 16:03 ` Bean
2008-01-24 18:16 ` UFS (FFS) support seems broken in grub2 Marco Gerards
2008-01-24 18:19 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tzkym7f8.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.