Date: Fri, 29 Mar 2019 04:04:13 +0100 From: Polytropon <freebsd@edvax.de> To: mayuresh@kathe.in Cc: Michael Sierchio <kudzu@tenebras.com>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Sending Tcsh to packages/ports ... Message-ID: <20190329040413.1aa78c31.freebsd@edvax.de> 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? > Also you can see they are the same binary. No, because -l doesn't provide the information about the inode (which is the same), and -h only affects the size display. You can see they are the same size (minus unit conversion and rounding, of course!), but you cannot conclude they are of the same content, not can you conclude that they are actually the same file, which means, only _one_ inode. You need the -i option to examime the inodes, and to properly conclude that csh and tcsh are hardlinked. > Doesn't matter that it is small, why have stray stuff lying around? I wouldn't call the C shell a stray shell yet. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190329040413.1aa78c31.freebsd>