All of lore.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] a.out support for multiboot and freebsd
Date: Fri, 15 Feb 2008 10:43:58 -0800	[thread overview]
Message-ID: <fp4mft$nog$1@ger.gmane.org> (raw)
In-Reply-To: <ca0f59980802150614k5b1e1295s29c9a4648db73ed8@mail.gmail.com>

Bean wrote:
> On Fri, Feb 15, 2008 at 9:29 PM, walt<wa1ter@myrealbox.com>  wrote:
>>   I made a small openbsd image to send you, but it works perfectly with
>>   your g2ldr so there's no point in sending it :o)  I think that problem
>>   is not worth your time or mine.
>
> BTW, how big is your ufs partition ? I have tested FreeBSD 6.3, NetBSD
> 4.0 and OpenBSD 4.2 in a 1G virtual disk, they all seems ok, perhaps
> if the disk is larger, the problem would occur.

Your instructions to load only the needed modules works great, thanks.

My openbsd partition is 7GB, but some other ufs partitions are bigger
than that.  I suspect that I have some disklabel conflict on that disk.
I have netbsd, openbsd, freebsd all installed on the same disk, each
with its own disklabel.  I don't know why it would cause that problem
in particular, though.

I'd like to know exactly how you create your virtual disks for testing.
I've been creating appropriate-size partitions on a USB stick and then
copying whatever files I need onto it.  Then I use dd to make an img
file to run in qemu.  It's a very slow process and I'd like to do it
better.  Any hints?

Thanks.






  reply	other threads:[~2008-02-15 18:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 18:41 [PATCH] a.out support for multiboot and freebsd Bean
2008-02-09 21:57 ` walt
2008-02-10  5:33   ` Bean
2008-02-10  9:22     ` Vesa Jääskeläinen
2008-02-10  9:47       ` Bean
2008-02-10 18:27     ` walt
2008-02-10 22:28       ` Bean
2008-02-11 14:11         ` walt
2008-02-11 14:28           ` Bean
2008-02-11 20:45             ` Bean
2008-02-11 20:46               ` Bean
2008-02-11 21:28                 ` Robert Millan
2008-02-11 21:46                   ` Bean
2008-02-12 11:16                     ` Robert Millan
2008-02-11 21:51                 ` walt
2008-02-12  4:03                   ` Bean
2008-02-12 11:19                   ` Robert Millan
2008-02-12 18:47                     ` Bean
2008-02-12 19:36                       ` Robert Millan
2008-02-13 10:40                         ` Bean
2008-02-13 15:40                           ` Robert Millan
2008-02-13 16:51                             ` Bean
2008-02-13 17:25                           ` walt
2008-02-13 17:37                             ` Bean
2008-02-13 20:31                               ` walt
2008-02-14  2:43                                 ` Bean
2008-02-15 13:29                                   ` walt
2008-02-15 14:03                                     ` Bean
2008-02-15 14:14                                     ` Bean
2008-02-15 18:43                                       ` walt [this message]
2008-02-15 18:58                                         ` Bean
2008-02-16 16:43                                         ` Bean
2008-02-16 18:12                                           ` walt
2008-02-16 18:29                                             ` Bean
2008-02-19 16:41                                               ` Bean
2008-02-15 22:43                                       ` walt
2008-02-16  1:00                                         ` walt

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='fp4mft$nog$1@ger.gmane.org' \
    --to=wa1ter@myrealbox.com \
    --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.