All of lore.kernel.org
 help / color / mirror / Atom feed
From: sos22@cam.ac.uk
To: Jamie Risk <jamie_risk@yahoo.ca>
Cc: linux-newbie@vger.kernel.org
Subject: Re: How can I move /usr/bin, /usr/lib (etc.) files?
Date: Thu, 2 Jan 2003 20:26:47 +0000	[thread overview]
Message-ID: <20030102202647.GD8978@cam.ac.uk> (raw)
In-Reply-To: <av1qr4$hev$1@main.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

> I'm using bash, so editting the ".profile" file in the user's home directory
> seems to have done the trick for the most part,
You may also want to modify /etc/environment, so that programs
other than Bash get the new PATH as well.

(Your system may call /etc/environment something else.  Look in
/etc/pam.d/login or /etc/security.d/login for pam_env.so for
some ideas)

> although when I invoked
> "man" (as in "man bash") after moving the directory, updating ".profile" and
> re-login,  I get messages akin to "/usr/bin/nroff not found" and
> "/usr/bin/tr not found".
>  * Where, in general, do programs (such as man) get there path information
> from?
In general, it depends on the program.  man, though, usually looks
in /etc/manpath.conf. (man 5 manpath)

> Similarily, I'd like to move the /usr/lib directory to another location.
>  * Should I download src for packages that I'm using and recompile with
> appropriate destinations chosen in the configure scripts?
That might be necessary.  If you're lucky, though, you might be able
to get away with adding the new location of /usr/lib to /etc/ld.so.conf
and the environbment variable LD_LIBRARY_PATH (same syntax as
$PATH).

Your life will almost certainly be drastically easier if you
create a symlink from /usr/lib to the new location...

Steven Smith,
sos22@cam.ac.uk.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-01-02 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 16:54 How can I move /usr/bin, /usr/lib (etc.) files? Jamie Risk
2003-01-02 17:24 ` Jamie Risk
2003-01-02 20:26 ` sos22 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030102202647.GD8978@cam.ac.uk \
    --to=sos22@cam.ac.uk \
    --cc=jamie_risk@yahoo.ca \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.