Re: One criticism about the PilotMgr ...

[adam@xxxxxxxxxxxxxxxxxxxxxx (Adam Stein)]

> 	Okay, so after doing battle with perl and my (seriously) hacked
> computer, I got PilotManager to work (doing my first sync now!  Woo-hoo!).
> However, I have a serious initial complaint.  The default list of valid
> ports for the cradle in the configuration section does not contain a
> complete list of ports that would be used (at least not on a linux box).
> 	I would recommend that this be fixed for the next release (at
> least to include /dev/pilot).

I had to add "/dev/cua/a" for Solaris.  It would be nice if the Solaris
entries were added.

The best solution might be to figure out what system it's running on and put
up a menu for that type of system.  For example, SunOS 4.x would get:

	/dev/cua0
	/dev/cua1
	...
	
Solaris 2.x would get:
	
	/dev/cua/a
	/dev/cua/b
	...
	
and so on.  Or at least make it so that it's easy to add user-defined entries
to the list.

                                                Adam
--
Adam Stein @ Xerox Corporation       Email: adam@xxxxxxxxxxxxxxxxxxxxxx
                                            
Disclaimer: All views expressed             
here have been proved to be my own.  [http://www.csh.rit.edu/~adam/]
------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************