ARCHIEVE, RESTORE and flag handling
- From: "Heiko Arnemann" <Heiko.Arnemann@xxxxxx>
- Date: Sun, 3 Sep 2006 19:25:36 +0200
you may have used the conectivity kit, in order
to make a backup of you home directory or
later on restore from the backup.
One of the features, coming with the con-kit backup:
it generates a program named fLaG,
which allows to restore the flag settings after
running the "restore" procedure of the con-kit.
Pressing [VAR ] after the restore procedure of the con-kit,
you will find the program fLaG in the home directory.
At this point, the user has the choise, to run
fLaG, which would restore the flag-settings, or
e.g. to delete fLaG, in order to avoid interference
with his own flag management (if existing).
We are thinking about implementation of this
feature to Wolfgangs Filer6.
Filer6 provides a backup procedure (ARCHIEVE), which stores
the backup file (including the backup date in the filename)
on the SD-card.
Before implementation, we would like discuss
(collect the pro's and con's).
So, please give your opinion.
My personal opinion:
* The way, it is handled within the con-kit backup seem to
be very easy way to store the current flag settings.
* There is an advantage against "common" practice.
If storing your flags in e.g. in the home dir in
a variable 'FLAGS' and using the reserved variable
STARTUP with << FLAGS STOF >> the
con-kit procedure is "more clear"; the user
is required to interact.
* ARCHIEVE and RESTORE are not handling
flag settings. There have to be a sense behind it?
* Flags and flag settings are very important for
some applications. I think with ARCHIEVE and
RESTORE possible changes cannot be managed.
* Between the archieve and the restore procedure
is maybe a longer period of time and the user
canot remember which flag settings have been
saved with the archieve procedure, and which
flags have been changed inbetween (maybe usefull
changes due to the users learning curve).
* Restoring flags should be
handled independently from archieving. I am thinking
about a "Flagman", which should give an overwiew
for different flag settings and providing recomended
flag settings for several applications.
- Prev by Date: Re: HP calc. Customer Service
- Next by Date: EMU48
- Previous by thread: The "Who the @@#$%&^@ is responsible for quality control" msg.
- Next by thread: Re: ARCHIEVE, RESTORE and flag handling