Subject: Re: Tests of mdsetimage -s
To: Jachym Holecek <firstname.lastname@example.org>
From: Marcin Jessa <email@example.com>
Date: 04/02/2005 11:09:39
Hi Jachym, guys.
On Sat, 2 Apr 2005 04:42:39 +0200
Jachym Holecek <firstname.lastname@example.org> wrote:
> Not sure, but it doesn't seem like memory reserved by MEMORY_DISK_ROOT_SIZE
> is ever freed (mdsetimage won't do it that is). So I'd say first create
> the disk image, then set MEMORY_DISK_ROOT_SIZE to match (roud up to closest
> blocksize multiple).
What would the -s flag of mdsetimage be used for ?
> > Seems like -s sets the reserved space to the size of the image.
> Yes, see also /usr/src/gnu/usr.sbin/mdsetimage/mdsetimage.c
Kernel is as big as before but the size of the memory it reserves for the image is the same as the size of image, with the -s flag to mdsetimage, right ?
> Maybe you forgot some COMPAT_<foo> in your kernel config?
I created my init with a simple printf just to see if the ramdisk in the kernel gets initialized and if init gets at all executed.
It seems it does. It does not really metter if it produces an error.
I just needed to test if the kernel can find it and if the ramdisk gets loaded.
The kernel is fine, it can execute ramdisk created for the NetBSD boot floppies and boot the system on my soekris just fine.