Date: Tue, 9 Jun 1998 17:01:38 -0400 From: sbabkin@dcn.att.com To: itojun@iijlab.net, phk@critter.freebsd.dk Cc: mike@smith.net.au, core@FreeBSD.ORG, hackers@FreeBSD.ORG, tech-jp@jp.freebsd.org Subject: RE: new config Message-ID: <C50B6FBA632FD111AF0F0000C0AD71EEFF8B22@dcn71.dcn.att.com>
next in thread | raw e-mail | index | archive | help
> ---------- > From: Poul-Henning Kamp[SMTP:phk@critter.freebsd.dk] > > I have spent much time on the question of configuration, and because > of > lack of time I have not implemented my conclusion. > That's a really great concept! > 4. The last part of the configuration script mounts the > quasi-root on "/rootfs" and establish symlinks to > make things look like they used to: > > for i in etc bin sbin usr var tmp > do > ln -s /rootfs/$i > done > > 5. Delete files no longer needed on the MFS to preserve RAM > Alternative approach: mount the traditional root filesystem on /, and the config-filesystem on /stand or something like. > The few problems: > > 1. How to control the contents of the MFS filesystem. ... > 3. Fix MFS to consume memory "as needed" only. > Because this filesystem is almost-read-only (files can only be removed), it can be very simplified. In the simplest case, it can be just a tar image of this filesystem added to the end of the kernel image. The bootstrap code will automatically load it into the memory. The speed of lookup is not important, so the simple contiguous tar image is perfect. Each page can be freed after all files in the image located in this page are removed. This will need some changes to the VM subsystem that will have to recognize this tar image after the end of kernel image in memory. -Serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C50B6FBA632FD111AF0F0000C0AD71EEFF8B22>