Date: Fri, 29 Mar 2019 02:35:28 +0000 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: Sending Tcsh to packages/ports ... Message-ID: <20190329023528.5866f5b1@gumby.homeunix.com> In-Reply-To: <695ab639fc872647cef88e09f8e4162f@kathe.in> References: <64780f09d4251b9641e3bca39000ae2d@kathe.in> <CAHu1Y70K=E-4EY6bjy9-59LCmX0a0u4ga2_mCywiTdmk4suW-w@mail.gmail.com> <695ab639fc872647cef88e09f8e4162f@kathe.in>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Mar 2019 07:36:49 +0530 Mayuresh Kathe wrote: > Couldn't you have simply done; > ls -lh *csh > instead? ls -lh strongly suggests they are the same file, but ls -i shows that they have the same inode and so are hard-linked. > Doesn't matter that it is small, why have stray stuff lying around? > >> "bash". To top that, the installer asks me to choose between "csh" > >> and > >> "tcsh" in-spite of being the same binary. Just because they are the implemented in the same binary doesn't mean that they behave the same when run as csh and tcsh.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190329023528.5866f5b1>