On Mon, Feb 04, 2008 at 05:10:20AM -0800, Jeremy Chadwick wrote:
> Also, the above mechanism must be fairly old, because I imagine it would
> be more effective to utilise kqueue/kevent to inform said programs of
> when the serial port is available for use.
The kqueue/kevent had appeared only in 4
> On Mon, Feb 04, 2008 at 02:08:32PM +0700, Eugene Grosbein wrote:
> > > Personally, I never understood the concept of "dial-in" and "call-out"
> > > devices on FreeBSD. I ran BBS software for years on both Apple II
> > > hardware and PC hardware; there was no distinction between such devices.
>
> > > Personally, I never understood the concept of "dial-in" and "call-out"
> > > devices on FreeBSD. I ran BBS software for years on both Apple II
> > > hardware and PC hardware; there was no distinction between such devices.
> > > A serial port is a serial port. Chances are I'm not understandi
On Mon, Feb 04, 2008 at 02:08:32PM +0700, Eugene Grosbein wrote:
> > Personally, I never understood the concept of "dial-in" and "call-out"
> > devices on FreeBSD. I ran BBS software for years on both Apple II
> > hardware and PC hardware; there was no distinction between such devices.
> > A seria
> > Personally, I never understood the concept of "dial-in" and "call-out"
> > devices on FreeBSD. I ran BBS software for years on both Apple II
> > hardware and PC hardware; there was no distinction between such devices.
> > A serial port is a serial port. Chances are I'm not understanding why
> Personally, I never understood the concept of "dial-in" and "call-out"
> devices on FreeBSD. I ran BBS software for years on both Apple II
> hardware and PC hardware; there was no distinction between such devices.
> A serial port is a serial port. Chances are I'm not understanding why
> there's
On Mon, Feb 04, 2008 at 02:37:31PM +0800, Ganbold wrote:
> Jeremy Chadwick wrote:
>> On Mon, Feb 04, 2008 at 12:53:58PM +0800, Ganbold wrote:
>>
>>> Hi,
>>>
>>> I'm trying to use serial port but the system says device busy.
>>>
>>
Jeremy Chadwick wrote:
On Mon, Feb 04, 2008 at 12:53:58PM +0800, Ganbold wrote:
Hi,
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
Does the same happen if you do `cu -l ttyd0 -s 9600`?
It
On Mon, Feb 04, 2008 at 12:53:58PM +0800, Ganbold wrote:
> Hi,
>
> I'm trying to use serial port but the system says device busy.
>
> daemon# cu -l /dev/cuad0 -s 9600
> /dev/cuad0: Device busy
> link down
Does the same happen if you do `cu -l ttyd0 -s 9600`?
> How
Daniel O'Connor wrote:
On Mon, 4 Feb 2008, Ganbold wrote:
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
What does fstat /dev/cuad0 say?
It says:
daemon# fstat /dev/cuad0
US
On Mon, 4 Feb 2008, Ganbold wrote:
> I'm trying to use serial port but the system says device busy.
>
> daemon# cu -l /dev/cuad0 -s 9600
> /dev/cuad0: Device busy
> link down
What does fstat /dev/cuad0 say?
--
Daniel O'Connor software and network engineer
fo
Hi,
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
daemon# uname -an
FreeBSD daemon.micom.mng.net 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0:
Mon Jan 14 16:49:57 ULAT 2008
[EMAIL PROTECTED]:/usr/obj/us
12 matches
Mail list logo
