Date: Fri, 23 Jan 2009 16:46:49 +0000 From: "Daniel Bye" <danielby@slightlystrange.org> To: freebsd-questions@freebsd.org Subject: Re: Registry corrupt? Message-ID: <20090123164649.GA54892@torus.slightlystrange.org> In-Reply-To: <20090123170132.M38136@wojtek.tensor.gdynia.pl> References: <3.0.1.32.20090123081931.00ed6460@sage-american.com> <20090123170132.M38136@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jan 23, 2009 at 05:02:27PM +0100, Wojciech Puchar wrote:
> it's not windows. there are fortunately no registry in unix.
>=20
> your problem explanation is too short to help you.
>=20
> describe something more.
> and what you mean "rehash"?
`rehash' is a builtin in some shells - csh and zsh come to mind. It is
used to cause the shell to reread the PATH environment variable and
rebuild its internal hash (hence rehash) list of items in the path. The
hash is used by the shell as a mapping between program names and their
canonical location on the file system. It's what lets you say `ls' instead
of having to say `/bin/ls', etc.
If you install a new port then such shells will not immediately pick up the
new executable - which is when you need to `rehash'. bash handles these
cases differently, obviating the need for the rehash command.
Dan
--=20
Daniel Bye
_
ASCII ribbon campaign ( )
- against HTML, vCards and X
- proprietary attachments in e-mail / \
--RnlQjJ0d97Da+TV1
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (FreeBSD)
iEYEARECAAYFAkl59HkACgkQixf5fBYiFmo4vQCfdnBNz5c9rzz+/OWpSGdTaYXX
Jt4AoKAbM5R//mVBP0m/yiseWE2f9Bnn
=8kJ+
-----END PGP SIGNATURE-----
--RnlQjJ0d97Da+TV1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090123164649.GA54892>