[coldsync-hackers] Snapshot: 2.0.0

[Andrew Arensburger <arensb+CShackers@ooblick.com>]

	I've just uploaded a snapshot of ColdSync 2.0.0. Some stuff
you should be able to tell just from the version number:
	- It has a new major version number, representing a major
	  change
	- It ends in not one, but two zeros, meaning that it's an
	  alpha release, so expect things to not work.

	Having said this, the major change in version 2 is daemon
mode. It doesn't run as a standalone server, but you can use it in
/etc/inetd.conf or /etc/ttys (or whatever your OS uses to spawn
'getty'). This, in turn, enables one-button syncing: just stick the
Palm into its cradle and push the HotSync button.

	To run ColdSync in daemon mode, give it the "-md" option, and
a "-t <listen-type>" option to specify the type of connection
("serial", "usb", or "net").
	In daemon mode, ColdSync establishes a connection with the
Palm, reads its serial number, username and userid, looks those up in
/usr/local/etc/palms, then setuid()s to the appropriate user, and runs
a normal sync.
	Here's a sample /usr/local/etc/palms:

# Hash in first column means comment
# 
# serial|username|userid|unixuser|palmname|config-file
109X7B28GC66-F|Gorko the Invincible|31337|arnie|Palm III|/folks/arnie/.coldsyncrc-palmIII
10A813V96PC0-H|Andrew Arensburger|2072|arensb|Palm V
*Visor*|Andrew Arensburger|2072|arensb|Visor
|Andrew Arensburger|2072|arensb|Palm Pilot Pro

The first three fields allow ColdSync to identify the Palm. The next
field specifies the (Unix) user name or UID of the user to setuid() to
for the main sync.
	The fifth field, "palmname", is optional. It isn't currently
used, but might be used later to look up a Palm in the user's config
file.
	The sixth field, "config-file", is also optional, and can be
used to specify an alternate config file. This will be read after the
setuid().

	The string "*Visor*", above, is a new feature: it represents
the binary string that Visors return when you ask them for their
serial number. You can't tell different Visors apart by their serial
number, but you can tell Visors apart from other Palms.

	To have ColdSync listen for a Palm on a serial line under
FreeBSD, add a line like the following to /etc/ttys:

cuaa0	/usr/local/bin/coldsync -md -s -t serial"	unknown	on

and kill -HUP init.

	Similarly, to have ColdSync listen for a USB visor via 'usbd'
under FreeBSD, add something similar to the following to
/etc/usbd.conf:

device "Handspring Visor"
	vendor 0x082d		# Handspring
	product 0x0100		# Visor
	release 0x0100
	attach "/usr/local/bin/coldsync -md -t usb -s ${DEVNAME}"

then kill and restart 'usbd'.

	For network connections, you should be able to add

netsync-wakeup	dgram	udp	wait	coldsync	/usr/local/bin/coldsync	coldsync -md -t net -

to /etc/inetd.conf, and kill -HUP inetd. I haven't tested this,
though, and network syncing is still flaky.

	For other BSD-derived OSes, things should be similar, though
possibly not identical. For SysV-derived OSes, you'll probably have to
add an entry to /etc/inittab.

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com                      views of ooblick.com
	     C code. C code run. Run, code, Run! Please!

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.