On 19-Apr-00 Brian Fundakowski Feldman wrote:
> I've got a nice script and better version of scancodes.c to do this for
> me
> now, so here goes :) These are the keys on the Logitech cordless
> keyboard,
> and they are undoubtedly the same for the rest of the Logitech iTouch
> keyboards.
Hi,
We were trying to debug the SCSI CAM driver using
remote gdb, but we were not able to establish the
connection between the target machine and host
machine.
The host and the target machine were connected using a
null modem cable which was tested using Pcplus utility
in DOS. In both the machin
It seems Alexey N. Dokuchaev wrote:
> Hello!
>
> I've been using FreeBSD 3.4 for quite a while, and my CDROM, being quite
> old and weird (NEC 260 model) was detected by both BIOS and FreeBSD.
Judging on the output it seems the NEC is one of the old devices that
doesn't say its a CDROM...
Try t
I have looked over your steps. It seems that the steps are all correct. I
can suggest four things:
(1) Consider using "makeoptionsDEBUG=-g" in your configure file.
(2) If you are using FreeBSD 3.3-Release, the flag may be 0x50 instead of
0x80.
(3) Lower the baud rate if possible. However,
Comments ?
-Arun
From: [EMAIL PROTECTED] (Arun Sharma)
Newsgroups: muc.lists.freebsd.questions,mpc.lists.freebsd.questions
Subject: socket.h and _POSIX_SOURCE
Date: 18 Apr 2000 08:45:31 +0200
What's wrong with this ?
-Arun
$ cat test.c
#include
#include
$ cc -D_POSIX_SOURCE
On Thu, 20 Apr 2000, Anatoly Vorobey wrote:
# Look into src/lib/libc/i386/gen/_setjmp.S and other files in
# the same directory for setjmp() and sigsetmp(). Basically, it'll store
# edx, ebx, esp, ebp, esi, edi, and the CPU control word, in that order.
Now I finally understand why trying to use
What you should be doing depends on
what kernel you are using.. I presume 4.0 or 5.0 as you use 0x80
as the flag for sio0.
Here's what I do:
Some of this, you have done, but I repeat the instructins for others
to find in the archives :-)
Don't forget there are two debuggers,
DDB, which has a hum
On Thu, 20 Apr 2000, Daniel O'Connor wrote:
>
> On 19-Apr-00 Brian Fundakowski Feldman wrote:
> > I've got a nice script and better version of scancodes.c to do this for
> > me
> > now, so here goes :) These are the keys on the Logitech cordless
> > keyboard,
> > and they are undoubtedly t
David Gilbert writes:
> I'm working on an l2tp netgraph node. I need md5. Specifically, the
> RFC says:
>
> The Response is a 16 octet value reflecting the CHAP-style
> [RFC1994] response to the challenge.
>
> I've had a look at md5.c, but there is no documentation on the usage
> m
I'm working on an l2tp netgraph node. I need md5. Specifically, the
RFC says:
The Response is a 16 octet value reflecting the CHAP-style
[RFC1994] response to the challenge.
I've had a look at md5.c, but there is no documentation on the usage
md5. In this specific case, how do I c
On Thu, Apr 20, 2000 at 04:02:28PM -0400, David Gilbert wrote:
> I'm working on an l2tp netgraph node. I need md5. Specifically, the
> RFC says:
>
> The Response is a 16 octet value reflecting the CHAP-style
> [RFC1994] response to the challenge.
>
> I've had a look at md5.c, but t
> "Mike" == Mike Bristow <[EMAIL PROTECTED]> writes:
Mike> hands all the LCP of to userland
Mike> Is a similar approach approprate here? Is the MD5ing time
Mike> critical, or does it only appear in the moral equivilent of LCP?
Could be done, I suppose. It is the "moral" equivalent to LC
On 20-Apr-00 Brian Fundakowski Feldman wrote:
> Sure:
Gracias.
> With the new output format, I can tell that the released scancode is the
> pressed scancode + 128 (| 0x80). Cool :)
Yes, the kbd driver handles this automatically.
>> I've altered atkbd.c to grok the new keys, I also added 'pow
Ok, I posted some panic messages awhile ago that appeared to go largely
unnoticed. I just got it again (this time while running in X) and I
was able to capture them via serial console. I will separate this
message into 'fact', 'observation', and 'speculation':
Fact:
1) This was the same panic
14 matches
Mail list logo
