Ganbold <[EMAIL PROTECTED]> writes:
> At 12:38 AM 26.02.2004, you wrote:
> > The preferred method is now keyboard-interactive. If your client does
> > not support it, get a better client.
> I'm using putty-0.53b.
putty supports keyboard-interactive, and it's even on by default. See
http://the.ea
> "Max" == Max Laier <[EMAIL PROTECTED]> writes:
Hello Max,
Max> The kernel parts are done, though not linked to any automatic
Max> build. If you want to build it already, you can build from the
Max> corresponding module directories: sys/modules/{pf, pflog, pfsync}
Nice to hear, is Altq i
Craig Rodrigues <[EMAIL PROTECTED]> 27 lines of wisdom included:
> What is the difference between these two sysctls?
>
> kern.smp.cpus: Number of CPUs online
> hw.ncpu: Number of active CPUs
These two are exactly the same thing from the little SMP I have done
with FreeBSD. I would use hw.ncpu, as
Debug outputs of sshd when connecting client:
psh# sshd -d -p 5999
debug1: sshd version OpenSSH_3.7.1p2 FreeBSD-20040106
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: Bind to port 5999 on 0.0.0.0.
Server listeni
Ganbold <[EMAIL PROTECTED]> writes:
> debug1: Client protocol version 1.5; client software version PuTTY-Release-0.53b
Set it to use protocol version 2 instead. You should not use protocol
version 1 unless you have absolutely no other option.
DES
--
Dag-Erli
In sys/sys/sysctl.h I see function kernel_sysctlbyname() that looks (to
me) to be intended for accessing sysctl values from kernel, but for it's
first parameter it requires a struct thread *td.
What should I pass to it? (I'm calling it from inside a screensaver module)
_
I noticed with a self build serial driver that I'm not allowed
to put data into a tty that is not opened.
I had to learn this the hard way and would like to know if there are
other points that I'm not aware of.
Is there any good documentation about kernel tty programming available?
--
B.Walter
Bruce M Simpson wrote:
On Thu, Feb 26, 2004 at 02:10:40PM +0100, Ivan Voras wrote:
In sys/sys/sysctl.h I see function kernel_sysctlbyname() that looks (to
me) to be intended for accessing sysctl values from kernel, but for it's
first parameter it requires a struct thread *td.
You could try lyin
At 09:16 PM 25/02/2004, Julian Elischer wrote:
Is anyone testing this..
Yes. I just applied it to a couple of boxes. We were able to panic the
box previously with ucom devices. I will see if its fixed tomorrow at the
office.
---Mike
DO I have to commit it (it works for me) to get p
On Thu, 26 Feb 2004, Bruce M Simpson wrote:
> On Thu, Feb 26, 2004 at 02:10:40PM +0100, Ivan Voras wrote:
> > In sys/sys/sysctl.h I see function kernel_sysctlbyname() that looks (to
> > me) to be intended for accessing sysctl values from kernel, but for it's
> > first parameter it requires a st
Hi all
I've been running 5.2 on my laptop (i386 Acer)
for some time now. Few hours ago I download the 5.2.1-release source,
buildworld, buildkernel, installkernel, but after a few minuts of
installworld my system froze. Now when I try to boot I get:
Mounting root from ufs: /dev/ad0s1a
WARNING: /
On Thu, 26 Feb 2004, db wrote:
> I've been running 5.2 on my laptop (i386 Acer) for some time now. Few
> hours ago I download the 5.2.1-release source, buildworld, buildkernel,
> installkernel, but after a few minuts of installworld my system froze.
> Now when I try to boot I get:
Ouch.
> Mou
On Fri, 27 Feb 2004, Eugene Grosbein wrote:
[...]
>'Failed to set value of option mode: Device busy'.
> 6. Choose 'File/Exit' menu in this xscanimage window.
>
> Several seconds later system will lock up. There is nothing to be done
> if you are in X, only power down/up cycle will help.
>
>
Sorry for the late response on this. I've been trying various combinations
of kernel options in an attempt to narrow down the problem.
--- Don Lewis <[EMAIL PROTECTED]> wrote:
> On 23 Feb, Brian O'Shea wrote:
> > --- Don Lewis <[EMAIL PROTECTED]> wrote:
> >>
> >> The cause of deadlocks is more l
On Thursday 26 February 2004 08:10 am, Ivan Voras wrote:
> In sys/sys/sysctl.h I see function kernel_sysctlbyname() that looks (to
> me) to be intended for accessing sysctl values from kernel, but for it's
> first parameter it requires a struct thread *td.
>
> What should I pass to it? (I'm calling
Robert Watson wrote:
On Thu, 26 Feb 2004, Bruce M Simpson wrote:
for consumption "on behalf" of a user process. My general preference
would be to offer an in-kernel API to manage whatever service is being
accessed if it's being done in the kernel "on behalf" of the kernel,
rather than trying to
At 02:40 AM 26/02/2004, Julian Elischer wrote:
On Wed, 25 Feb 2004, Mike Tancsa wrote:
> At 09:16 PM 25/02/2004, Julian Elischer wrote:
>
> >Is anyone testing this..
>
> Yes. I just applied it to a couple of boxes. We were able to panic the
> box previously with ucom devices. I will see if its
On Thu, Feb 26, 2004 at 02:10:40PM +0100, Ivan Voras wrote:
> In sys/sys/sysctl.h I see function kernel_sysctlbyname() that looks (to
> me) to be intended for accessing sysctl values from kernel, but for it's
> first parameter it requires a struct thread *td.
>
> What should I pass to it? (I'm c
18 matches
Mail list logo
