Kevin Gilbert wrote:
> Will gladly do it - if you will tell me how I can update the source 
> repository 
> without making a complete mess of it.

Wait until our CVS surgery is done. SF is being a bit slow about it....
we'll get it sorted out soon. Keep an eye out for an email from me, I'll let
everyone know when they should re-check out the repo.

> Also, with "write_config_to_file" et al, what are the advantages / 
> disadvantages of binary mode? Should a "normal" user be given the option or 
> should I make up their mind for them?

I can't imagine the average user needing it. However, I'm always of the "if
it's possible I like to make the option available, even if it's hidden in an
'advanced uber hacker' tab somewhere" but that's just me. Well, on second
thought if they needed that, they'd probably be using the CLI and not the GUI.

> Finally, I've got the easy, safe stuff going. Now for the dangerous bit - 
> loading configs & firmware back into the remote. What are the chances that I 
> could "brick it"? If a load fails, how do I recover? Just a simple reset?

For most remotes you can boot into safemode by yanking the battery, holding
the off button and putting the battery back in. Hold the off button until
it's in safe mode.

However, the chances of you bricking it are slim to none if you're simply
using the library. However, if you start hacking on the library, well, then
you run a bigger risk. I've bricked mine countless times. You can recover
from most things by booting into safe mode and updating your firmware and
your config and rebooting. Never try to write to the safemode part of the
device. :)

-- 
Phil Dibowitz                             [EMAIL PROTECTED]
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming


Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel

Reply via email to