Date: Tue, 25 Mar 1997 23:42:33 -0500 From: "Perry E. Metzger" <perry@piermont.com> To: Terry Lambert <terry@lambert.org> Cc: cjs@portal.ca, hackers@freebsd.org, port-i386@netbsd.org Subject: Re: how to name fs specific programs Message-ID: <199703260442.XAA03826@jekyll.piermont.com> In-Reply-To: Your message of "Tue, 25 Mar 1997 21:23:13 MST." <199703260423.VAA26968@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
By the by, let me note: I'm not continuing this discussion. I think my point that there is no good reason to rename the commands (and lots of reasons not to since it breaks compatibility) has been made. I'm sure you can strain your mind to think of lots more "reasons" if you can call what you've posted thus far "reasons", and by all means, feel free to implement them in FreeBSD if your fellow FreeBSD developers think its a good idea. I've spoken my peace. Perry Terry Lambert writes: > > > So what you're saying is that the above is significantly better than > > > > > > $FSCMD_$FSTYPE $ARGS > > > > > > and > > > > > > for i in *_fstyp; do [stuff] ... > > > > > > Or am I missing something here? > > > > No you aren't missing anything. > > > > Furthermore, he is claiming that breaking compatibility with existing > > code and scripts doesn't matter, either, in order to get this > > "improvement". > > What about "semantic seperation of command names from the FS on which > they are intended to operate"? > > > Regards, > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703260442.XAA03826>