Oliver Fromme <[EMAIL PROTECTED]> writes: > Apart from my stupidness of not checking the location of the > binary first -- what did I do wrong, and what's the recommended > way of handling this? Am I supposed to rm /usr/bin/ssh each > time I install a new release or snapshot? I can't believe > that. You could use /usr/bin/ssh, for a start. Note that this is OpenSSH, though, so there may be incompatibilities with ssh1. The other alternative is to put /usr/local/bin in the front of the path. A third alternative is to build without OpenSSH by tweaking make.conf. (Note that there is now /etc/default/make.conf which means that you can't look in /etc/make.conf for the new option.) kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: ssh strangeness in -current... Brad Knowles
- Re: ssh strangeness in -current... Matt Heckaman
- Re: ssh strangeness in -current... Harold Gutch
- Re: ssh strangeness in -current... Roland Jesse
- Re: ssh strangeness in -current... Brad Knowles
- Re: ssh strangeness in -current... Udo Erdelhoff
- Re: ssh strangeness in -current... Brad Knowles
- Re: ssh strangeness in -current... Christian Weisgerber
- Re: ssh strangeness in -current... Jordan K. Hubbard
- Re: ssh strangeness in -current... Paul Richards
- Re: ssh strangeness in -current... Kai Großjohann
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... John Polstra
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Oliver Fromme
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Peter Jeremy
- Re: ssh strangeness in -current... Christian Weisgerber
- Re: ssh strangeness in -current... Peter Jeremy
- Re: ssh strangeness in -current... Oliver Fromme
- Re: ssh strangeness in -current... Gary Jennejohn