Date: Tue, 12 Apr 2011 14:03:15 -0600 From: Warner Losh <imp@bsdimp.com> Cc: freebsd-embedded@freebsd.org Subject: Re: Does somebody work on NanoBSD? Message-ID: <18A31C67-D0B5-4E28-AA50-241F60EBFB83@bsdimp.com> In-Reply-To: <375260633.20110412113802@serebryakov.spb.ru> References: <116932102.20110411113412@serebryakov.spb.ru> <BANLkTimh582Lbsn0JmXg1MZmpEB%2BTYr6Gw@mail.gmail.com> <924400541.20110411125319@serebryakov.spb.ru> <BANLkTi=-BSVYV0z59otkMCQk=1rDaGhN7g@mail.gmail.com> <8ADBCF69-67AB-4E39-99D0-9971E942F1FA@bsdimp.com> <375260633.20110412113802@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 12, 2011, at 1:38 AM, Lev Serebryakov wrote: > Hello, Warner. > You wrote 11 апреля 2011 г., 18:32:24: > > >> I also think that FreeNAS has its own script, which I though had been merged to head. > It seems, every NanoBSD-based project (FreeNAS, BSDRP, maybe other) > has "home-brew" patches to nanobsd.sh and some support scripts, which, > IMHO, worth to evaluate and, may be, integrate to "official" NanoBSD. I have a queue of patches to try to integrate back into main FreeBSD from these projects already. I just need a little bit of time to do that. > Also, here is attempt to re-write NanoBSD in more clean and modular > way (to be honest, nanobsd.sh code is not an example of clean & good shell > code, compare to rc.d infrastructure, for example): > > http://www.tomjudge.com/index.php/FreeBSD/NanoBSD_NG I saw that. We'll see where it goes. Not sure I entirely share your views on cleanliness. To be honest, though, this sort of thing would really be better written in python, since that language is much more expressive and easier to use in many ways than shell. > P.S. I get these messages with my AND list addresses in To/CC: only > once, as "personal" ones, is it Ok? I just removed all the cc's except embedded. Warner > -- > // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org> > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18A31C67-D0B5-4E28-AA50-241F60EBFB83>