Date: Sat, 29 Jun 2002 17:50:07 -0700 (PDT) From: Ian Dowse <iedowse@maths.tcd.ie> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/40021: [patch] use ld(1) to build kernel with linked-in md(4) filesys Message-ID: <200206300050.g5U0o77b015013@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/40021; it has been noted by GNATS. From: Ian Dowse <iedowse@maths.tcd.ie> To: W Gerald Hicks <gehicks@gehicks.dyndns.org> Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/40021: [patch] use ld(1) to build kernel with linked-in md(4) filesys Date: Sun, 30 Jun 2002 01:43:45 +0100 In message <200206292331.g5TNVRRu000860@gehicks.dyndns.org>, W Gerald Hicks wri tes: > Some applications such as picoBSD and etherboot still need a > linked-in filesystem. This patch allows one to specify an object > file created with mdconfig(8) and objcopy(1) to be linked into the > kernel image. This has the added benefit of allowing a flexible > size for the filesystem. Looks useful. > The patch deprecates 'options MD_ROOT_SIZE' replacing it with > 'makeoptions MD_ROOT_IMAGE="mdimage.o"' where mdimage.o > is a file created something like this: The patch seems to remove rather than deprecate the MD_ROOT_SIZE code. Is there a good reason not just leave it there and add the new option? The new approach requires that you have the image available at the time that the kernel is compiled, so for some applications it is less flexible (for example, we use built-in root filesystems in a lot of diskless terminals, and it is useful that updating the root filesystem does not require re-linking the kernel). It would also be preferable if the makefile could do the objcopy step, so you can specify the actual image file in MD_ROOT_IMAGE. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206300050.g5U0o77b015013>