Hello again,
>This is where I get lost. When you said:
>
>``When I want to backup, I simply remove the write protect tab on the
>floppy. I can assure you that it takes a lot of config data to fill
>1.6Mb of compressed space.''
>
>I thought that you were backing up *only* config data. How does your
>sed process facilitate this quoted intent of yours?
>
Actually, the process is more like *I don't backup program binaries* :-).
Because of the subset of programs I work with, taking care of /etc and
/var - /var/log - /var/adm - /var/lib/lrpkg - /var/run - /var/lock -
/var/spool -/var/tmp } gives me what I want. YMMV :)
>By-the-by, this is considerably faster:
>
> sed -e "/^[./]*etc/d" ${pkg} > ${pkg}.light
>
Linux people are usually more intelligent than I am. Your sed mask allows
for stuff like ...etc and ../../../etc and all kinds of ganes that I prefer
not to play :). Following your intervention, the original sed command now
reads
sed -e "/^etc[[:space:]]*$/d" -e "/^[/]etc[[:space:]]*$/d" \
-e "/^[.][/]etc[[:space:]]*$/d" \
-e "/^etc[/]/d" -e "/^[/]etc[/]/d" -e "/^[.][/]etc[/]/d" \
${pkg} > ${pkg}.light
This is part of a startup script that runs a few times a year. I am more
concerned with exactness than speed of execution. Your method is
_definitely_ faster but does not gives me exactly what I want.
>> >[2] How do you account for ${pkg}.exclude.list?
>>
>> ${pkg}.exclude.list is a proper substring of ${pkg}.list and therefore
gets
>> included in the for loop.
>
>Yes, I know; but, how does including excluded data facilitate your
>needs?
Sorry for taking your question litterally :). I will presume that you
understand that the set of files destined for the default store is the set
of all files on the machine minus the set of all the files enumerated in
each of all other packages and minus the set of files excluded for the
default store.
Suppose the default store is named gizmo and some other package exclude
/etc/this&that. The backup code in LRP, Dachstein, Oxygen, etc concatenate
all the file lists for all packages other than gizmo in a single exclusion
list. Therefore, if something is excluded from one package, it is also
excluded from all other packages.
When I want a snapshot of my machines, I want _everything_ in etc. Life is
like that :-)
>
>> >[3] How do you account for CONF files that do not reside under /etc?
>> >
>> This particular code snippet treated /etc one way and /var a completely
>> different way. I could integrate both by producing a different exclusion
>> list for the default store. I'll think about it.
>
>Yes, or similarly . . .
>
Like I said above, I do not handle /var the same way as I handle etc. The
programs I use store their data in /etc or /var or both. It can be extended
to anything else. Eventually, the need to run write-protected will change.
However, this solution works today.
>> >[4] Where do you get `cmp'?
[snip]
>
>I know that it is available; but, it is *not* included in DCD -- is it
>included in Oxygen? I do not argue against its usage; rather, I am
>often frustrated by lack of real awk, sed and sort -- not to mention cmp
>and diff ;<
>
Gee, I really had a push-button mind when I answered you. Michael, bear with
me for a few more seconds.
For one of his shows, Ed Sullivan had invited a lion tamer who usually put
his entire head in the lion's mouth at the end of his act. It was explained
to him, in writing, that the act took 10 minutes. By showtime, due to
overbooking and delays, Sullivan tells the lion tamer that once the curtain
rises, he has two minutes for his act. OK, says the lion tamer, but YOU
explain it to the lion. :-)
Now, to answer your question: you are looking for a baseline specification
:-). David Douthitt is *RIGHT* when he says that there should not be a
baseline specification, either explicitly specified for LEAF or indirectly
specified by refering to a "distribution". We are dealing with unspecidied
hardware constraint, some of which are not obvious as in the case of the
write-protect switch. As a case in point, Bering does not have netstat, a
fixture in this environment since the early LRP days. In the confined space
of a floppy, Jacques Nilo decided something that made sense for his project
and he can revisit his decision at any time. In the meanwhile, you have
Bering to play with.
The difficulty here is formalizing your ability to repackage your "baseline"
and go on with your life (or your LEAF :). I think we can overcome this
difficulty but I will wait for your comments on the process.
Regards,
Serge Caron
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
