>
> Ok. Did you track the problem down to permissions problems
> or
> perhaps to something else trying to use the serial port?
>
I thought that we had solved the permissions issues but read on later in this
email.
I have had at times the port supposedly tied up by other programs. I say
supposedly because I had turned nothing on but Xastir and/or the GTKTerm but
the system said port busy in spite of the fact that I only had one port
utilizing program on.
One time in a fit of frustration I tried connecting too often and Xastir itself
put a lock on the port but someone helped me unlock it.
> Note that a lot of newer Linux systems have switched to
> using the
> udev system which creates entires in /dev only for devices
> that
> actually exist in your system. This means that it creates
> them and
> sets their permissions each time you boot. If you're
> manually
> changing permissions in /dev and they keep getting reset,
> this may
> be your issue.
>
> I only figured out enough to change the permissions on my
> USB
> joystick so that each time the device is created I can use
> it. I
> had to go into /etc/udev/rules.d/ and change a file in
> there.
>
>
Now maybe you found something here, Curt, because when I change the permissions
for /dev/ttyS0 the computer does not save them. Upon a reboot they return to a
default of rw-rw----.
I think that the Fluxbuntu folks released this distro less than one year ago so
maybe what you said above applies to my issue. Do you (or anyone else) have any
thought as to how to fix the problem?
Jim KE5MKT
_______________________________________________
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
