Date: Wed, 16 Jun 2004 08:18:29 +0100 From: "Richard P. Williamson" <richard.williamson@u4eatech.com> To: Martin Nilsson <martin@mullet.se>, freebsd-small@freebsd.org Subject: Re: [Thinbsd] Re: ThinBSD with other videodriver Message-ID: <6.1.1.1.2.20040616080628.027a8bd0@cygnus> In-Reply-To: <40CF0BF8.3040206@mullet.se> References: <40CEBC17.9050602@mullet.se> <20040615115341.GA20812@aoi.wolfpond.org> <40CEFDBC.8000108@univ-mlv.fr> <40CF0BF8.3040206@mullet.se>
next in thread | previous in thread | raw e-mail | index | archive | help
At 15:47 15/06/2004. Martin Nilsson had this to say: >The sysinstall part could probably be made a lot easier by calling fdisk & disklabel directly from a script but the above was the way I knew would work. I did do it from scripts. Unless you understand the ins and outs of disklabel et al., it can be quite painful trying to figure out what you need to get it working. For the simplicity, if I were doing a FAQ on this, I would say 'use sysinstall unless you can quote the disklabel and newfs manpages verbatim from memory' >>as it is done with pexes project maybe we could write a config script >>that put in the ramdisk only the drivers needed >>for a specific configuration. better than see the ramdisk grow to >>support every thinclient hardware in the world. >>something like the openbsd installer that config the keyboard, >>drivers, etc... > >Having a smorgasbord of compiled binaries for different programs, drivers etc to choose from when creating the mfsroot would probably be smart. A small script could then ask which ones to include on the ramdisk. lld is also a friend here, because you can ldd your binaries to find out which shared libs are required for the binaries on the ramdisk. Which means you can dump any that aren't and save the space. rip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.1.1.1.2.20040616080628.027a8bd0>