Date: Thu, 22 Feb 2001 00:45:51 -0800 (PST) From: Luigi Rizzo <rizzo@aciri.org> To: eugen@iname.com Cc: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD 0.5 and mfs_tree Message-ID: <200102220845.f1M8jpV82754@iguana.aciri.org> In-Reply-To: <20010222153412.C35703@svzserv.kemerovo.su> from Eugene Grosbein at "Feb 22, 2001 3:34:12 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi! > > It would be nice if floppy.tree.exclude apply to mfs_tree too. > F.e., I don't need /etc/motd, /etc/remote, /etc/shells at all and > have no 'official' way to avoid it. > > Then, I'd like to modify some of files in mfs_tree/etc. > Now I have to place my own versions to fd/floppy_tree/etc - bad idea, > waisting space. Or modify files directly in mfs_free and next cvsup > will eliminate changes. as a temporary workaround you can set you can set the environmnet variable PICO_TREE before entering the script, and point it to the location where your 'standard' tree is. I agree that one would like more flexibility in excluding/including things, so if you have patches to contribute they are welcome. I believe that the way to achieve this kind of flexibility is to define additional variables in the "config" file which control what goes in and what not, including (possibly) the list of files to exclude from either tree. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102220845.f1M8jpV82754>