> I keep asking myself this question; a default sysinstall package would > give us the same end result. > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > breakage. Would you guys quit spreading FUD and start actually giving us some DETAILS on this alleged breakage? You've been ridiculously silent on an issue which has been actively worked on and discussed for the last few weeks to come forward at this late stage and start waving your arms around. This entire thread has been content-free so far. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- ssh strangeness in -current... Oliver Fromme
- Re: ssh strangeness in -current... Matthew N. Dodd
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Matthew N. Dodd
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Doug Barton
- Re: ssh strangeness in -current... Jordan K. Hubbard
- Re: ssh strangeness in -current... Matthew N. Dodd
- Re: ssh strangeness in -current... Doug Barton
- Re: ssh strangeness in -current... Matthew N. Dodd
- Re: ssh strangeness in -curren... Doug Barton
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... John Baldwin
- Re: ssh strangeness in -current... Garance A Drosihn
- Re: ssh strangeness in -current... Warner Losh
- Re: ssh strangeness in -current... John Baldwin