Date: Mon, 10 May 2010 20:15:03 -0600 From: Chad Perrin <perrin@apotheon.com> To: freebsd-questions@freebsd.org Subject: Re: md5(1) and cal(1) Message-ID: <20100511021503.GA4580@guilt.hydra> In-Reply-To: <AANLkTil779I9T4JhvaHgCCYkbSTz4xoqzjGv6wYVpYaR@mail.gmail.com> References: <AANLkTil779I9T4JhvaHgCCYkbSTz4xoqzjGv6wYVpYaR@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--8t9RHnE3ZwKMSgU+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, May 10, 2010 at 05:35:45PM -0800, David Allen wrote:
> 1. Why doesn't cal(1) hilight the current day? Hell, some days I'm
> not even sure what day or week it is, so after typing 'cal', I have to
> type in 'date', and then sit there for a few seconds to interpret what
> I'm looking at. Of course, that isn't always successful, so I
> typically end up reaching for my mouse and hilight the date manually.
> But after doing that I'm just as annoyed by not knowing the date as
> I'm annoyed by the behavior of the cal utility and the extra work I'm
> forced to do.
If I don't actually know the date, I typically use the date command to
find out. I use cal to do things like check dates of other days in the
preceding or following weeks.
>=20
> 2. Why doesn't md5(1) have a "check" option? Seems to me requiring a
> manual inspection is error-prone at best, and makes scripting unecessarily
> complicated.
I use diff to check the output of md5 against a known string. For
instance, if I have a known hash value in a file hash.txt, I might first
get the md5 output into another file called hash2.txt:
md5 -q hash2.txt
=2E . . then diff the two files:
diff hash.txt hash2.txt
The thing that bothers me about diff is that, even though it's often
described as a "string comparison" utility, it doesn't actually compare
strings -- it compares files that *contain* strings.
--=20
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
--8t9RHnE3ZwKMSgU+
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEARECAAYFAkvovacACgkQ9mn/Pj01uKXNvgCfbh1/BrPITjhJ9ahc5R6mMnnB
9tsAn1o0dPJniR66+zYkG9eimbgdeiMC
=C/dX
-----END PGP SIGNATURE-----
--8t9RHnE3ZwKMSgU+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100511021503.GA4580>