From owner-freebsd-mobile@FreeBSD.ORG Thu Nov 4 19:59:27 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3963516A4CE for ; Thu, 4 Nov 2004 19:59:27 +0000 (GMT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B460D43D45 for ; Thu, 4 Nov 2004 19:59:26 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([138.89.105.63]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041104195925.CFTM4017.out006.verizon.net@[10.0.3.231]>; Thu, 4 Nov 2004 13:59:25 -0600 From: "Alexandre \"Sunny\" Kovalenko" To: Eric Anderson In-Reply-To: <418A5D7F.8080808@centtech.com> References: <20041104110413.GA13307@totem.fix.no> <20041104112634.GA14296@laverenz.de> <20041104114156.GB43303@warning.this.domain.does.not-exist.de> <20041104125320.GA16749@totem.fix.no> <16778.19722.10795.603853@ran.psg.com><418A5D7F.8080808@centtech.com> Content-Type: text/plain Message-Id: <1099598350.903.3.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 04 Nov 2004 14:59:10 -0500 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [138.89.105.63] at Thu, 4 Nov 2004 13:59:23 -0600 cc: freebsd-mobile@freebsd.org Subject: Re: Palm or equalient supported by FreeBSD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 19:59:27 -0000 On Thu, 2004-11-04 at 11:49, Eric Anderson wrote: > Alexandre "Sunny" Kovalenko wrote: > [..snip..] > > And while we are on the subject -- anyone out there figured out what to > > do with 5.3/6.0 -- ttyUn/cuaUn devices are being created when you hit > > "HotSync" and demolished promptly after sync is done, IMHO making > > impossible to have daemon process looking out for the device. > > I think /etc/devfs.conf can help with that. > > Eric > Can you by any chance elaborate? I have read all appropriate man pages and could not come up with an idea of faking the node in /dev/ before it actually is created and that's what (IMHO) needed to have daemon listening on the dynamic device. Or am I missing something? --- Alexandre "Sunny" Kovalenko.