Date: Thu, 6 Apr 2000 16:36:02 -0700 (PDT) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: obrien@freebsd.org Cc: nate@yogotech.com (Nate Williams), arch@freebsd.org Subject: Re: Import of tcsh into src/contrib/, replacing src/usr.bin/csh Message-ID: <200004062336.QAA38972@gndrsh.dnsmgr.net> In-Reply-To: <20000406150728.A25607@dragon.nuxi.com> from "David O'Brien" at "Apr 6, 2000 03:07:28 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > PicoBSD is just *one* of the many, many, many uses for small embedded > > system. > > List them. Your not reading. He already listed a handfull, Juniper, Whistle, etc all. I'll ad 3 in I am working on, can't give you names, but 8K bites for me, let alone 400K. > These small embedded system developers can grab the old csh > sources from the Attic and import them into their own source tree. And you can go compile the tcsh port, now you tell me what one is easier for everyone involved. FreeBSD != ObrienBSD, you've already lost the battle, you said unless someone objected with technical reasons. You've been handed more than one technical reason, now go back to your installs and just deal with tcsh being a port. > > > As would Tcsh. > > > > If both are adequate, choose the smaller of the two since it benefits > > more folks that way. ;) > > I dissagree. ;) Perhaps a poll? Why a poll, I have seen 3 negatives and 1 ``if we do do this''. Ohh.. and yess... I am still a confirmed anti-bloat screaming monger from the good old days when a 10 command OS/8 CLI was just fine with me, and PIP had more options than ls. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004062336.QAA38972>