On Fri Oct 17 13:37 , tokind sent: >Thank you for the reply Bruce. I am now looking at doing a custom Nano BSD to >include ettercap & such, and targeted for 512Mb card. Do you know of a >relatively easy tutorial or reference on the process? The NanoBSD Howto is >leaving me cold (hate to admit it).
I'm assuming you mean the Howto in the Handbook, http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/howto.html. Yeah, it's not for the complete novice or faint of heart. It helps if you're already set up to build FreeBSD from source. You may want to poke about other bits of the handbook to learn about cvsup to populate your /usr/src tree and keep it up to date and at least review how to build FreeBSD from source. Also you may find a bit more info with "man nanobsd". -b is particularly useful in certain circumstances, especially if your nanobsd build failed after the installworld bit. I recall the NO_INSTALLLIB=YES in nanoBSD's example config caused a installworld error. You shouldn't need that line with a 512Mb card. I've put the LIB back in and a few other things and still only use 130MB. Recalling that nanoBSD splits the card in half, so you have slightly less than 256MB to play with, it should still give no space problems. Note: remove any NO_ lines you don't want, don't try to remove the YES or set equal to NO as ISTR merely having them defined is all causes the (in)action. One thing you'll probably want to do is create a custom kernel for the net5501. The GENERIC kernel has a lot of built in devices you won't need (e.g. SCSI), so you'll save memory by making a custom kernel. If you aren't in it for learning experience, ask and I'll post my 6.3R kernel conf file. It might also work with 7R or give you some ideas on how to tweak it. I've added some custom macros (customize_cmds) to copy /etc and ${HOME} files from my build system. If you're going to copy /etc/passwd, that functionality is actually split across several files, including a DB. Do a man pwd_mkdb. While nanobsd has a mechanism for keeping localized changes on the target CF card across builds, it only works on files directly in /etc. To customize files in places like /etc/ssh/ or /usr/local/etc, you need to modify or copy them in during the build. A key to this is knowing that when the custom macros are run, ${NANO_WORLDDIR} is the present root directory of the installed image, so you could, for example, copy files to ${NANO_WORLDDIR}/var/named/etc/namedb to set up BIND. Don't forget the -b flag when you're debugging any custom macros. I think nanoBSD already has a package installation macro, if not Google a bit. If you normally build ports, creating a package requires installing the port on the build system first or there are instructions for building them in jails. If you're not fanatic about having the latest point rev., you can also download pre-built packages for which ever FreeBSD release you're building. If you have nanoBSD specific questions, there are two related mailing lists on freebsd.org. I think they are something like freebsd-small and freebsd-embed. Check the list of mailing lists on http://www.freebsd.org Use the one that's less moribund. -Jed _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
