On Fri, Jan 12, 2007 at 12:49:23AM -0500, Lloyd R. Prentice wrote: > I did one more run last Sunday and suspect, but can't confirm, some kind > of instability. Over the last three runs I've tried exactly the same > procedure with exactly the same profiles/*.download and > profiles/*.download files. It looked like I got different results. with > each run -- one successful; two not. May very well be an error(s) on my > part. I was stressed out, getting ready for my trip. But I'll run the > cycle again on Sunday, when I'm able to focus again on the task.
i suspect it is problems with different configurations on some of the http servers that you're hitting, as the default (ftp.us.debian.org) points to multiple machines in a round-robin fashion, some of which may be configured differently or be slightly out of sync with one another (in my experience). > One problem is that I feel like I'm blindly following a set of > procedures that I don't understand -- and the procedures themselves are > a moving target. Thus, I can't distinguish between my blunders and > genuine bugs. both simple-cdd and the tools used in etch have actually been going through a fair amount of changes recently. once etch finally releases, that should reduce the complexity a little bit. > Has anyone published an authoritative design document that spells out in > pseudo code or other high-level representation what's happening under > the hood when you run simple-cdd? nope. > What I'd most love to see is a two-part doc; 1. Overview of the > algorithm used in simple-cdd for generating a custom distribution; i don't really understand what you mean by algorithm here ... ?? > 2. A step-by-step procedure for configuring and running simple-cdd to > generate a custom distribution -- something similar to the simple > outlines that I've included in earlier postings. well, http://wiki.debian.org/Simple-CDD/Howto is pretty much exactly that (or intended to be) ... though maybe you want something with a little more detail? > I recognize that the source code would be the most authoritative source > of all, but I for one am not sufficiently skilled to follow what's going > on in source, nor how to translate source into best-practice run-time > procedures. i could probably write a narrative description of the source. but that will be difficult to keep up to date over time... > Would it be possible to publish a wiki or similarly community > reviewable /editable user document along the lines above that is clearly > designated as most authoritative? If others thought it useful, I'd be > happy to help with the writing, editing, and updating of such a beast if > I can get knowledgeable guidance. please use the http://wiki.debian.org/Simple-CDD/ namespace to create new documents and update the ones already there. though it's only as authorative as the people who edit it. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
