I completely agree, it most likely is a bug in a tcsh, and I've tried
recompiling all things involved. The question is, what does OpenSSH's
sshd do differently while recieving a scp from sshv1, that sshd 1.2.27
does not do. I think if we can find tht, we can find what's causing the
tcsh problem..
On Wed, 8 Mar 2000, Matt Heckaman wrote:
> I've heard reports of using scp from ssh 1 to openssh creating problems,
> and I finally now see why - it makes tcsh core! Observe:
I don't think this is a general problem :) Certainly it does interoperate
very well, perhaps perfectly, with the ssh port
Mike Smith had the audacity to say:
> > That's the impression I was under. I have gotten no information from AMD to say
> > that the MTRRs on their K6-2 line don't work. The only things I know of is that
> > the first-gen chips didn't have them, and the code checks for that. Are you sure
> > that
Hi,
Is anyone using Fibre Channel Adaptors in FreeBSD 3.4-STABLE? It so, what
are you using and how does it perform?
We're about to start hooking up Dell 4300/6300s to a large disk array to
do image and web work and I would like to go FC rather than scsi.
Thanks,
Carl.
To Unsubscribe: se
I've heard reports of using scp from ssh 1 to openssh creating problems,
and I finally now see why - it makes tcsh core! Observe:
[ from machine, alpha ]
admin[alpha]:~> uname -a
FreeBSD alpha.lucida.qc.ca 3.4-STABLE FreeBSD 3.4-STABLE #0: Mon Feb 14
16:36:01 EST 2000 [EMAIL PROTECTED]:/usr/src/
subscribe
Michael DeMutis
System's Administrator
2GEN.Inc.
email: [EMAIL PROTECTED] website: http://www.2gen.net/
Phone: 905-308-9155 Fax: 905-308-9519 ICQ UIN: 1257176
"Merging Media & Idea To Bring Internet
Brad Knowles wrote:
> Am I missing something here? Should I not be using "make update"
> at all, but instead be calling the appropriate cvsup commands with
> the appropriate supfiles directly? If so, then why does "make
> update" exist at all?
% grep SUP /etc/make.conf
# CVSup update f
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
On Wed, Mar 08, 2000 at 11:15:18AM +0100, Brad Knowles wrote:
> Folks,
>
> This doesn't seem to be working quite as easily as I would have hoped.
>
> If you're not in North America, you can't get your crypto sources
> from one of the US or Canadian mirrors, and I'd be willing to bet
As I recall, Will Andrews wrote:
> On Wed, Mar 08, 2000 at 09:32:30AM -0700, Chad R. Larson wrote:
> > I put my CVSup files in a seperate directory (/usr/sup). I have
> > files for src doc and ports, and run the CVSup's by hand before
> > doing a "make world".
>
> This is precisely the same meth
On Wed, Mar 08, 2000 at 12:17:26PM +0100, Brad Knowles wrote:
> At 12:45 PM +0200 2000/3/8, Panagiotis Astithas wrote:
> It doesn't seem to be quite working. Cd'ing to /usr/src and then
> typing "make update" doesn't seem to be grabbing the crypto stuff
> (which goes to a different server),
You
> Roman Shterenzon had the audacity to say:
> > What models/revisions seem to be broken?
> > I *think* that K6-2 mtrr works.
> >
>
> That's the impression I was under. I have gotten no information from AMD to say
> that the MTRRs on their K6-2 line don't work. The only things I know of is that
>
Roman Shterenzon had the audacity to say:
> What models/revisions seem to be broken?
> I *think* that K6-2 mtrr works.
>
That's the impression I was under. I have gotten no information from AMD to say
that the MTRRs on their K6-2 line don't work. The only things I know of is that
the first-gen ch
On Wed, Mar 08, 2000 at 09:32:30AM -0700, Chad R. Larson wrote:
> I put my CVSup files in a seperate directory (/usr/sup). I have
> files for src doc and ports, and run the CVSup's by hand before
> doing a "make world".
This is precisely the same method I use to update my -CURRENT and -STABLE
so
14 matches
Mail list logo
