On Thu, 5 Apr 2001, S.C.Best wrote:
> Jeff:
> Sorry you don't agree.
Well, I am too. I feel like one of us is operating under some
misconceptions about how lrpkg or tar works. By continuing this thread, I
hope to grok your concern, or perhaps you will find your concerns were not
justified.
> What I mean to say was, suppose my currently running system
To be clear, you said "development box"... but even on an LRP box, I have
a hard time following your concern. The distinction has to do with which
tools you are using.
> has a working /etc/dnscache (for
> example). I'd be ill advised to extract a new dnscache.lrp without
> carefully controlling where it untar's. The defaults would overwrite
> what's my system was using.
What default? The only "default" is the current directory you are in when
you untar the lrp file. Since I cannot imagine doing that into "/" on a
non-LRP system, you are mystifying me. Are you referring to wanting to
use lrpkg (which automatically cds to "/" temporarily during the install)
on a running LRP system to extract the package without interfering with
the system? Why not just use tar/ctar yourself instead of lrpkg then?
Is there something in your concern about absolute paths? If so, I know of
no requirement to use absolute paths, and tar by default ignores any
leading "/" that happens to be present in the archived filenames. I am
really groping here...
> Also, I don't see untar'ing to /tmp a lot of extra work.
The copying seems an unnecessary use of disk space and time. If you want
it in a separate subdirectory, then by all means put it there when you
want it there. There might even be an advantage to adding commandline
options to lrpkg to do that, though tar/ctar seems quite sufficient. But
I just cannot see the advantage of all that extra copying and deleting in
the normal course of operation.
What would it accomplish? You expressed concern over working files
getting replaced... but having lrpkg untar them to a temporary location
and then cp/mv them automatically would be no safer from your fingers
point of view. Would you require that lrpkg be run in two steps?
> As I recall, lrcfg backs up to /tmp before writing to a floppy, and
> I've never heard it so characterized. But, to each their own.
a) note that there is an option to turn that step off. root.lrp is a real
headache in that regard.
b) the files are in compressed form at that stage, so disk space usage
is not _doubled_ as your suggestion appears to require...
c) That step is present as a workaround to the nasty things that can
happen when a floppy fills up. Your proposed step has no such
preventative effect.
d) only one file needs to be cleaned up after the copying operation is
complete.
e) I find that particular step fairly error prone... I have to pay close
attention, and I still don't really know if I am doing the right thing
unless I trust that I knew what was on that disk before I started the
backup anyway. The Macintosh technique of precalculating whether there is
going to be enough disk space to complete a copy operation automatically
BEFORE it begins the copy, and only prompting whether I want to overwrite
an existing file _if one exists_ makes a lot more sense to me than adding
more predictable pauses for error-prone user inspection.
What am I missing?
>
> -Scott
>
> >> Actually I like .lrp as well, though my complaint
> >> with it is different. I find it difficult to extract files
> >> from a .lrp without potentially overwriting important system
> >> binaries on the development box.
> >
> >I don't grok this. I have never had difficulty extracting or creating lrp
> >files in the subdirectory of my choice. System files are in no danger.
> >
> >> What'd be *much* nicer is if package.lrp expanded
> >> to /tmp/package, and then /tmp/package/package.list would be
> >> queried to find out where to put everything.
> >
> >I don't agree. What a lot of extra work.
>
>
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/leaf-devel
>
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<[EMAIL PROTECTED]> Basics: ##.#. ##.#. Live Go...
Work:<[EMAIL PROTECTED]> Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...2k
---------------------------------------------------------------------------
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
