Re: problems with getting through firewall using CVSup

2003-02-28 Thread Sergey A. Osokin
On Fri, Feb 28, 2003 at 04:13:06PM +0100, Igor Pokrovsky wrote: Sergey A. Osokin wrote: On Fri, Feb 28, 2003 at 03:52:36PM +0100, Igor Pokrovsky wrote: Patrick M. Hausen wrote: Sergey Osokin wrote: Is there any way to make it work? To fool firewall? Yes, looks

Re: Problem with telnet

2003-02-28 Thread Dimitry Andric
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2003-02-28 at 15:36:27 Quincey Koziol wrote: QK I updated my machine to the latest stable source yesterday (2/27/03) and ===snip=== QK /usr/libexec/ld-elf.so.1: /usr/lib/libkrb.so.3: Undefined symbol _ossl_old_des_set_key You probably need

Re: problems with getting through firewall using CVSup

2003-02-28 Thread Jason Andresen
Patrick M. Hausen wrote: Please, people! If Port 5999 is blocked, the responsible person doesn't want you to use CVSup. You will have to clear that issue. If port 5999 is blocked, chances are your firewall admin doesn't even know what CVSup is. If you send him an email he'll probably open it

4.8 PreRelease problems

2003-02-28 Thread Huver
I suppose this list is the right place? 4.8 pre-release problems: A. The new __stdinp, __stdoutp, __stderrp in stdio.h is causing major problems for 3.x binaries. E.g. such a binary uses compat/libc.so.3, but also libm.so.2 -- the latter includes stdio.h but has no compat version. All

Re: problems with getting through firewall using CVSup

2003-02-28 Thread Steve Bernard
You could funnel your CVS traffic through an open port like 80 or 22 or tunnel it inside of HTTP or SSH, but this will require a gateway on the outside, or someone running a CVS repository on one of those ports. If you think that the fw admins watch their logs and traffic patterns then you're

Re: Problem with telnet

2003-02-28 Thread Kirk Strauser
At 2003-02-28T14:36:27Z, Quincey Koziol [EMAIL PROTECTED] writes: I updated my machine to the latest stable source yesterday (2/27/03) and I'm now getting this message when [attempting to] telneting into it: On a side note, if you're interested enough in security to deal with Kerberos, you

Re: Problem with telnet

2003-02-28 Thread Patrick M. Hausen
Hello! Kirk Strauser wrote: I updated my machine to the latest stable source yesterday (2/27/03) and I'm now getting this message when [attempting to] telneting into it: On a side note, if you're interested enough in security to deal with Kerberos, you should permanently lose telnet.

Re: problems with getting through firewall using CVSup

2003-02-28 Thread Jukka Simila
On Fri, 2003-02-28 at 15:59, Patrick M. Hausen wrote: Hi! But is there any way to do anything without asking firewall admin to open 5999 port? No, there is not. Well, there is, sort of ... Please, people! If Port 5999 is blocked, the responsible person doesn't want you to use CVSup.

Re: 4.8 PreRelease problems

2003-02-28 Thread Erik Trulsson
On Fri, Feb 28, 2003 at 09:42:48AM -0600, Huver wrote: BTW, I made the mistake of cvsup'ing to RELENG_4 from a 4.6.2, thinking I was updating to 4.7, now I'll have to back down to 4.7+post-patches. I'm entering a reqeust now: in the future, pre-release be made a new, short- lived branch

Re: 4.8 PreRelease problems

2003-02-28 Thread Jukka Simila
On Fri, 2003-02-28 at 16:42, Huver wrote: BTW, I made the mistake of cvsup'ing to RELENG_4 from a 4.6.2, thinking I was updating to 4.7, now I'll have to back down to 4.7+post-patches. I'm entering a reqeust now: in the future, pre-release be made a new, short- lived branch (delete it after

Re: Buildworld problem

2003-02-28 Thread Glendon M. Gross
I could be mistaken, but my impression is that crypto code seems to often screw up the build process. I'm not sure if this is because the crypto code is restricted due to a need for the environment variable USA_RESIDENT to be set to YES, or because crypto sources and crypto licensing seems to

Re: 4.8 PreRelease problems

2003-02-28 Thread Max Khon
hi, there! I suppose this list is the right place? 4.8 pre-release problems: A. The new __stdinp, __stdoutp, __stderrp in stdio.h is causing major problems for 3.x binaries. E.g. such a binary uses compat/libc.so.3, but also libm.so.2 -- the latter includes stdio.h but has no

hyperthreading in STABLE: should machdep.cpu_idle_hlt be on?

2003-02-28 Thread Steve Grandi
I've brought up STABLE on a Supermicro X5DPR-8G2+ motherboard which has two 2.4GHz Xeons. In the BIOS setup, I disabled hyperthreading. The BIOS even prints out a nice message during the POST that hyperthreading is disabled. The BIOS setting notwithstanding, STABLE fires up hyperthreading and