Hello Michael,
>[ snip ]
>
>Let me reduce my confusion to its firstmost problem: How does your sed
>process facilitate ``*I don't backup program binaries*''?
>
>AFAIK, ${pkg}.list files -- _minus_ ${pkg}.exclude.list files -- define
>which files comprise the ${pkg} package -- correct?
>
>Once you eliminate all files under etc, /etc and ./etc from ${pkg}.list
>files, what you have left is ``a bunch of binaries'' -- am I wrong?
>
>Wouldn't you reach this same end if all files under etc, /etc and ./etc
>were only listed in ${pkg}.exclude.list files?
>
>Until I fully understand this premise of yours, I do not know how to
>proceed . . .
OK, so lets process this from the start. Here is the contents of
/var/lib/lrpkg/bindc.list, an old BIND 8.something package:
etc/init.d/bind
etc/named.conf
usr/sbin/named
usr/sbin/ndc
var/lib/lrpkg/bindc.*
var/named
Only concentrate on those two etc entries. The package author did not define
a .local file to backup just part of the package. The package is running off
CD and I can't rewrite it there :-). Finally, even if I could, I DO NOT WANT
to. I want to keep this package in whatever form it was delivered for the
entire duration of its useful life.
Once the package is LOADED, I delete the two etc lines from the list. This
means that any other package can now claim these two files. If these files
were enumerated in, say, /var/lib/lrpkg/bindc.exclude.list, they would be
excluded from every other package AND bindc.lrp. This is important, please
stop here if it is not clear.
Now, by removing these lines, I can either backup these files in the default
store (root.lrp if you are using Dachstein) or I could create a
configuration package. If I did this, I could be missing out on other stuff.
If I were to run on a hard disk, the persistent nature of the storage medium
hides the problem: eveything you left will be there when you power the
machine up again.
What I want is the entire contents of etc (and other stuff) as if I was
working with persistent storage without affecting each package.
Dachstein loads the default store BEFORE anything else and this is not
helping your understanding. If etc/named.conf is in both root.lrp and
bindc.lrp, the later MUST overwrite the former because the package loading
code is in root.lrp. By separating the default store from the boot loading
code, you can load the default store in the order YOU chose :-) Cool!
I suggest you try the discussion.img floppy which has a default store
separate from root. Perhaps by experimenting with this disk, it will become
clearer? If you get confused by the alternating kernels, I can package
something more obvious.
Regards,
Serge Caron
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
