Re: [coldsync-hackers] coldsync 1.5.3 nov 27 snapshot

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

On Wed, 29 Nov 2000, Ryan VanderBijl wrote:
> So, i tried with debug mode - `coldsync -mr my_files -dsync:3`
> and it gave me something this 
> (pretty much regardless of what I had the speed set to): 
>     Using default speed (38400 bps)
>     -> Setting speed to 38400 (15)

	Weird. Works for me (tm), and there's no OS-dependent code
involved.
	If you run it with "-dsync:7", you'll see it stepping through the
list of speeds, trying to find the one you requested. If the speed isn't
listed, you'll see it fail and fall back on the default speed.

	Could it be that you have more than one listen{} block in your
.coldsyncrc, or that you're editing the wrong config file?

> I also have a few suggestions:
> configure script: don't allow the --with-usb for non freebsd boxes.

	Naah.
	a) The special USB code should work under NetBSD (since that's
where FreeBSD got its USB code in the first place) and probably OpenBSD
and BSD/OS as well.
	b) So far, I've managed to avoid checking which OS the user is
using, and I'd rather not start now.
	c) The FAQ, TFM, and 'configure --help' all say that the USB stuff
is *BSD-only. "--with-usb" isn't turned on by default, so presumably the
main way one finds out about it is by running "./configure --help", which
prints
  --with-usb              Enable USB support for Visor (FreeBSD 4.x only).
While I'm willing to accept that people don't read the manual, I have very
llittle sympathy for anyone who can't be bothered to read all the way to
the end of the line.
	d) There's an XXX comment in "configure.in" to the effect that it
should check to make sure that various headers and structs exist, before
enabling the USB code. This is a low-priority problem, because of (c),
above, though you're more than welcome to submit a patch.

> makefiles: it continues even if it doesn't fully build the program.
>            (like when someone puts --with-usb on a linux system, it
> 	   doesn't find the usb.h file, and thus dies, but makefile
> 	   doesn't).

	This appears to be a GNUmake-ism: it runs "/bin/sh -e". Is there a
magic 'make' variable that'll turn this off?
	This is rather easy to fix, but first I'd like to make sure that
it doesn't break other 'make's.

> There was some mention in the docs that you could set the speed on
> the comandline, but I couldn't figure out how to do that. Clarification
> would be nice.

	Hurm. Can you find the reference? It's bogus. You can't.

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com			views of ooblick.com
		     PUI: Piglet User Interface.


-- 
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.