Date: Tue, 10 Jan 2006 18:50:44 +0200 From: Eugeny N Dzhurinsky <eugenydzh@jdevelop.com> To: freebsd-mobile@freebsd.org Subject: Re: Palm Tungsten E2 Message-ID: <20060110165044.GJ743@115-2.trifle.net> In-Reply-To: <20060110060451.A28614@eskimo.com> References: <20060105155118.GH743@115-2.trifle.net> <20060105162656.GA750@115-2.trifle.net> <20060106082156.A14689@eskimo.com> <20060109110313.GI841@115-2.trifle.net> <20060110060451.A28614@eskimo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 10, 2006 at 06:04:51AM -0800, Joseph Olatt wrote:
> Is it possible that permissions on /dev/ucom0 is causing the failure?
> It could be that you as a non-root user is not being able to write to
> /dev/ucom0. /dev/ucom0 is created when you press the HotSync button
> (on 5.x and above).
>
> I've had to add the following lines to /etc/devd.conf to get the
> permissions right.
>
> attach 100 {
> device-name "ucom0";
> action "chmod 666 /dev/ucom0";
> };
>
> Alternatively, you can "chmod 0666 /dev/ucom0" after you press the
> HotSync button before running pilot-xfer or, you can run pilot-xfer as
> root.
No. It was because port version of pilot-link is TOO old, and there were some
issues with protocol or something like this. I downloaded and installed
pilot-link-0.12.0-pre4, it works fine with Palm Tungsten E2
--
Eugene N Dzhurinsky
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060110165044.GJ743>