From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: zsh 5.0.7
Date: Sat, 11 Oct 2014 17:29:54 -0700 [thread overview]
Message-ID: <5439CB82.3070401@eastlink.ca> (raw)
In-Reply-To: <141011150111.ZM28417@torch.brasslantern.com>
On 10/11/2014 03:01 PM, Bart Schaefer wrote:
> On Oct 11, 2:46pm, Ray Andrews wrote:
> }
> } Ok, so what's the approved fix? In this particular install I have no
> } need to keep anything around that's not current, and of course I want
> } all roads to lead to 5.0.7. Should I just fiddle with the pointers?
>
> You have several choices.
>
> Firstly, you need to see if chsh will let you set your login shell to
> /usr/local/bin/zsh. If it won't, you can either --
> 2. try editing the file /etc/shells to add /usr/local/bin/zsh and then
> run chsh again, or
The horror: I got the dread: "PAM: Authentication failure". Tried to edit /etc/shells, no luck, tried to edit /etc/passwd and ended up being unable to log in at all. Restored a backup.
> 1. find out which path actually is your login shell and link that path
> to /usr/local/bin/zsh, or (if that would fluster your upgrades)
I ended up changing the 'zsh*' links in '/etc/alternatives/' from
'/bin/zsh5' to '/usr/local/bin/zsh'
and that seems to be working fine.
BTW, doing all of this as root.
> 3. set up your login shell init to "exec /usr/local/bin/zsh" in the
> appropriate circumstances.
>
> See FAQ "I don't have root access: how do I make zsh my login shell?"
> for discussion of that last.
>
> Once you get zsh going as your login shell, you need to change the
> order of directories in the $path array to put /usr/local/bin near
> the front. If you can't do that for some other reason, you're back
> to option (1) above.
I read something once that said '/usr/local/bin' should be at the end of
the path. It explained
how your system was in mortal peril otherwise. Nevermind, I always
thought it should come
first myself.
> You can also try to use your package manager to find out what installed
> /usr/bin/zsh{,5} and remove that package. Once you have done so, you
> can rerun configure in your zsh build to set --exec-prefix=/usr and
> then rebuild and install, but it'd probably be wiser to get it running
> out of /usr/local if you can.
I see what you mean about not overwriting any packaged files, they are
all different. I guess
that means I should now be able to purge zsh and Debian will just remove
it's stuff, leaving
what I just installed alone. But I'll make sure what I have now is
stable, before I tinker
anymore.
Thanks Bart.
next prev parent reply other threads:[~2014-10-12 0:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 18:53 Ray Andrews
2014-10-11 20:10 ` Bart Schaefer
2014-10-11 21:46 ` Ray Andrews
2014-10-11 21:56 ` Axel Beckert
2014-10-11 22:43 ` Ray Andrews
2014-10-11 22:01 ` Bart Schaefer
2014-10-12 0:29 ` Ray Andrews [this message]
2014-10-13 19:02 ` Greg Klanderman
2014-10-13 22:04 ` Ray Andrews
2014-10-13 22:58 ` Greg Klanderman
2014-10-14 1:17 ` Ray Andrews
2014-10-14 20:12 ` Greg Klanderman
2014-10-14 20:33 ` Ray Andrews
2014-10-14 17:20 ` combining .histfiles Ray Andrews
2014-10-14 22:04 ` Bart Schaefer
2014-10-14 22:25 ` Ray Andrews
2014-10-14 23:55 ` Bart Schaefer
2014-10-15 1:02 ` Ray Andrews
2014-10-15 1:09 ` Kurtis Rader
2014-10-15 1:25 ` Ray Andrews
2014-10-23 2:58 ` c++ comments Ray Andrews
2014-10-23 4:41 ` Bart Schaefer
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=5439CB82.3070401@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).