> -Ursprungliche Nachricht-
> From: Poul-Henning Kamp [mailto:[EMAIL PROTECTED]]
> Subject: Re: Accessing the tty structure of an opened device
>
> You will need to do this in a device driver, there is no way you
> can reliably measure that from userland.
>
> Trust me on this: I've trie
> From: Poul-Henning Kamp [mailto:[EMAIL PROTECTED]]
> Subject: Re: AW: Accessing the tty structure of an opened device
>
>
> How fast do these pulses arrive ? Consider using the
> PPS-API for that:
>
the time between a pulse and a space often only takes
a few milliseconds. I have to meassu
> From: Poul-Henning Kamp [mailto:[EMAIL PROTECTED]]
> Subject: Re: Accessing the tty structure of an opened device
>
>
> >is it possible to access the tty structure of an opened
> >device directly?
> >
> >Background:
> >I'm trying to sense the DCD state of a serial port for
> >getting the puls
Hi,
is it possible to access the tty structure of an opened
device directly?
Background:
I'm trying to sense the DCD state of a serial port for
getting the pulses and spaces of a simple IR device.
I could use ioctl commands to get the current state but then
I would have to check the state contin
>-Original Message-
>From: [EMAIL PROTECTED]
>To: Alexander Maret
>Cc: '[EMAIL PROTECTED]'
>Sent: 19.10.00 15:30
>Subject: Re: How to sense DCD on serial port?
>
>
>
>> How can I sense the state of the DCD line that quick? I
>
>I'm not
Hello,
I just assembled a mini IR receiver for the serial Port.
This device shows the IR-code by pulling DCD up or down.
As there is no software for FreeBSD supporting IR I would
like to have a try and code it myself. Unfortunately those
Pulses sent by the IR device sometimes only last a few
mill
ion
of the first disk to the second disk if you change any of
the files listed above or if you install a new kernel/new
release of FreeBSD.
Sorry for my bad english.
Alexander Maret
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
> -Ursprungliche Nachricht-
> Von: Peter Pentchev [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 1. September 2000 14:00
>
> man 1 logger
>
> pipe your stdout/stderr to logger(1), and you're all set.
> You may even
> specify a facility/level to log with.
>
Thanks for your quick answ
Hi,
I wonder if it is possible to redirect stdout/stderr to syslog.
Background:
I'm writing a program which starts (fork=>execvp) and observes
another program. I would like to redirect all output of the "execvped"
program to syslog.
I know this is not really FBSD related but I hope you can help
ng but I'm not sure
which effect the missing class has.
Regards,
Alex
> -Original Message-
> From: Greg Lehey [mailto:g...@lemis.com]
> Sent: Dienstag, 27. Juli 1999 09:43
> To: Alexander Maret
> Cc: freebsd-hackers@freebsd.org
> Subject: Re: Which /etc-files do
Hi,
I configured vinum (RAID 1) on a 3.2S System. As I want to mirror
as much as I need to keep the system running (in case of a drive 1
failure) I mirrored /etc as well. At boot time (until vinum is
initialized) the system only has the following files:
/etc/defaults/rc.conf
/etc/rc.conf
/etc/rc
ng but I'm not sure
which effect the missing class has.
Regards,
Alex
> -Original Message-
> From: Greg Lehey [mailto:[EMAIL PROTECTED]]
> Sent: Dienstag, 27. Juli 1999 09:43
> To: Alexander Maret
> Cc: [EMAIL PROTECTED]
> Subject: Re: Which /etc-files do
Hi,
I configured vinum (RAID 1) on a 3.2S System. As I want to mirror
as much as I need to keep the system running (in case of a drive 1
failure) I mirrored /etc as well. At boot time (until vinum is
initialized) the system only has the following files:
/etc/defaults/rc.conf
/etc/rc.conf
/etc/r
Hello,
I got the following kernel messages. Does anybody know what
caused this messages? Is this the first sign of upcoming problems?
Jun 5 21:05:01 mail /kernel: 128 v_inactive_target R *Handler Int
Jun 5 21:05:01 mail /kernel: 129 v_inactive_count R *Handler Int
Jun 5 21:05:01 mail /kernel
Hi,
> -Original Message-
> From: Nick Hibma [mailto:nick.hi...@jrc.it]
> Sent: Dienstag, 1. Juni 1999 11:58
> To: Alexander Maret
> Cc: 'hack...@freebsd.org'
> Subject: RE: xl driver for 3Com
>
>
>
> The discussion started with a remar
Hi,
> -Original Message-
> From: Nick Hibma [mailto:nick.hi...@jrc.it]
> Sent: Dienstag, 1. Juni 1999 11:01
> To: Alexander Maret
> Cc: FreeBSD hackers mailing list
> Subject: RE: xl driver for 3Com
>
> This comparison with Linux is completely off. The n
Hi,
> -Original Message-
> From: Sheldon Hearn [mailto:sheld...@uunet.co.za]
> Sent: Dienstag, 1. Juni 1999 10:45
> To: Alexander Maret
> Cc: hack...@freebsd.org
> Subject: Re: xl driver for 3Com
>
> FreeBSD _developers_ seem to be more concerned with producing
Hi,
> -Original Message-
> From: Greg Black [mailto:g...@acm.org]
> Sent: Dienstag, 1. Juni 1999 05:21
> To: Bill Paul
> Cc: hack...@freebsd.org
> Subject: Re: xl driver for 3Com
>
> This whole argument strikes me as a good wake up call for all of
> us. It really is important to make sur
Hi,
> Collisions on half-duplex Ethernet are *normal*. Get used to it.
>
> Collisions is the standard flow control mechanism for
> half-duplex Ethernet.
> The amount of collisions you get depend on the cards used,
> the amount of
> traffic, and several other things. The amount of collisions
>
Hi,
> Well maybe FreeBSD is transmitting packets much faster than Linux. :)
> You still haven't actually measured the transfer speed, so there's
> no way for us to know.
Well, I'll do and report the results to you.
> Grrr. I'm sorry, but I really don't think you're putting the pieces
> together
20 matches
Mail list logo
