Date: Sun, 14 Jul 2002 09:38:34 -0700 From: Luigi Rizzo <luigi@FreeBSD.org> To: Mark Peek <mp@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release/picobsd/build write_mfs_in_kernel.c Message-ID: <20020714093834.E74633@iguana.icir.org> In-Reply-To: <p05111a0bb95747d37370@[10.1.1.73]>; from mp@FreeBSD.org on Sun, Jul 14, 2002 at 09:22:12AM -0700 References: <200207141209.g6EC9XBL099971@freefall.freebsd.org> <p05111a0bb95747d37370@[10.1.1.73]>
next in thread | previous in thread | raw e-mail | index | archive | help
i guess that those in need (assuming they exist) will find out and
complain and possibly we will move this code to a more appropriate
place. Where, i just have no idea.
In any case the dd hack is as much of a hack as the one in
write_mfs_in_kernel.c, and it is not bad at all:
set `strings -at d kernel | grep "MFS Filesystem goes here"`
mfs_ofs=$(($1 + 8192))
dd if=${c_fs} ibs=8192 iseek=1 of=kernel obs=${mfs_ofs} \
oseek=1 conv=notrunc
cheers
luigi
On Sun, Jul 14, 2002 at 09:22:12AM -0700, Mark Peek wrote:
...
> Is there a replacement way to embed a memory filesystem into the
> kernel? (Besides the dd hack that picobsd is using). Are consumers of
> this, like the PowerPC porting effort, still needing this
> functionality? Will future ports want this? I don't believe it should
> be totally removed from the system. Hooking it into usr.sbin would be
> more appropriate. I'm hesitant to move it to tools or ports due to
> fears of bitrot.
>
> Mark
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020714093834.E74633>