| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
of answer
|
| |
|
|
| |
standard methods of message construction
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
1. Comment all the stuff we dont have in fedora distro. This makes it
much easier to cp the spec file when creating the new version of fak.
2. xserver.py: Its not experimental anymore.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Since pretty much have tested the passwd, mdadm.conf and grub
plugins, it is time to take away the experimental flat
Filesystem flag:
We still don't have a plugin that checks the sanity of a storage
so this flag will be set by default.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
1. Do the test the right way. We were checking the exact output in order
to validate the correctness of the cli. Randomness in FAK and other
issues interfered with this test schema. We now check specific output
string in the whole output.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Makefile:
1. Cut counts from 1 not 0.
2. Create the "about" info in the makefile instead of spec file.
3. Put subdirs and about targets into one build target.
firstaidkit.spec:
1. Erase the about creation from here.
2. Erase the fedora 7 specific stuff.
3. Call make build.
4. xserver plugin does not need rhpl nor rhpxl anymore.
5. Actually include the COPYING file where the about says it is.
configuration.py:
1. Change the default backup dir from /tmp/fakbackup to /tmp.
/tmp/fakbackup caused some file permission strangeness when
a non root user executed fak after root had executed it. This
can still occur, but it will be left like this as the user
should not execute fak in non root anyway.
logging:
plugins.py,interpreter.py. __init__.py
1. Always use the reporting object when possible.
2. Add time stamp and level of message to log messages.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add test for the outomatica mode and the flow mode of the cli.
The downside to this test is that it probably wont work when
firstaidkit is installed in the system. The reason for this is
that it brings all the plugins that are installed in the system,
this means that the outputs will be different when the commands
are run. This must be addressed and if this turns into an
issue we should simply turn the test off untill its fixed.
Moreover this will make the build fail when changed that modify
the system messages are introduced. So from now on when those
types of messages are changed, the test mush be changed as well
(Which basically means changing the outputs files).
1. cli.py : add main test classes.
2. cli/outputs/*: these are the outputs that the various commands should
have when called with the plugins under testsuite/cli.
The files are called like the commands.
3. cli/plugin*: two plugins to server as the information providers. They
don't do anything interesting.
4. __init__.py: export the new test.
|
| |
|
|
| |
1. <flow> with the -f function is optional.
|
| |
|
|
| |
1. Update general firstaidkit documentation.
|
| |
|
|
|
|
|
|
|
| |
1. Make the usage message more readable.
It now prints "firstaidkit" as opposed to the caller string. This
allows the description to go into the next line without loosing
prettiness.
2. Make usage more compact.
Compact the explination of "-a" into one item in the usage string.
|
| |
|
|
|
|
| |
1. Correctly change the state of the issue when devices or partitions are
defined.
2. Erase some incode documentation that is not necessary.
|
| |
|
|
| |
Add the doc page for firstaidkitrevert.
|
| |
|
|
|
|
| |
1. Add info for --nodeps option.
2. Add info for --plugin-args option.
3. Add info for -P option.
|
| |
|
|
| |
Update documentation to refer to persistent backups.
|
| |
|
|
|
|
|
|
| |
1. Address various minor issues with messages to the user.
2. Make the name of the issues different so they can be told appart.
3. Make sure that the fix step fails when there are no devs or parts.
4. Inform the user of the devices and partitions that are being backed up.
5. Make sure that the description is visible.
|
| |
|
|
|
|
|
| |
1. Add a search for the window bootloader. This search is based on
http://en.wikipedia.org/wiki/Master_boot_record and will be the plugins
default until I or someone more intelligent than me comes up with a better
way of iding windows bootloader.
|
| |
|
|
|
| |
1. Get rid of old grub plugin and related files.
2. Erased stale lines in spec file as well.
|
| |
|
|
| |
1. Have the grubroot as a class attribute.
|
| |
|
|
|
|
| |
1. Correctly parse the partition arguments as we did with the device
args.
2. Add the functionality of modifying particular partitions.
|
| |
|
|
|
|
| |
1. Fix a repeated line and some lines that were over 80 chars.
2. Inform the user how to execute grub in order to install the
bootloader into one of the drives.
|
| |
|
|
|
| |
Having an option --recover is more intuitive for the user that does not
know how grub works.
|
| |
|
|
|
| |
Make the default behavior of grub more sane. The right thing to do when
no arguments are passed is to do nothing.
|
| |
|
|
|
| |
Put the reverting logic into the main Backup class. This will allow
future classes that inherit from Backup to have this attribute.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Parse the arguments correctly for grub plugin.
Set the internal variables correctly for grub plguin.
Use the internal variavels when deciding which dev to install to.
plugin.py:
user lstrip instead of just strip to take off the first part of the
argument string. This still has an issue as the strip does not strip
strings but strips away all the characters listed in the str. At the
moment its working because the args always begin with "-" and the
plugin names dont have "-" in their names. but this might be a problem
in the future.
|
| |
|
|
|
|
|
| |
It is necessary to differentiate between calling the BackupPersistent class
for backup purposes or for reverting purposes.
Also the grub revert function and the firstaidkitrevert file changed to
address the new changes.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This introduces new requirements to the plugins.
1. If a plugin wants to be revertable it must implement the revert function.
This function will be accessible from the plugins top most namespace. The
same place where get_plugin is.
2. For the plugin's backend directory to be easily found, the plugin must
give the backend its module name as an id. In this way when the user
specifies in the revert command line plugin 'x', the revert class will
go to the backup directory in search for a directory called the same
way as the module of 'x'.
3. If the plugin developer does not want to use the system of backup dir
naming, there is a second way how to specify the backup dir. The
plugin must specify a function getBackupId(), that will return the id
of the backup space that can be used for the backup dir search.
Backup spaces that fail to comply with these directive will be ignored.
|
| |
|
|
|
|
|
| |
--install-all: means to install grub binary to all devices and partitions
--install-to=: receives a comma separated list of devices where grub plugin
should install grub binary.
If both options are specified the --install-to options is used.
|
| |
|
|
|
|
| |
This function will translate all the arguments into a container
that organizes all the arguments for grub. This container also
has the default values of each argument.
|
| |
|
|
|
|
|
|
|
| |
When looking for the place to install GRUB we need to search for
the drives/partitions that dont have other bootloaders in the
first 512 bytes. This will be done by means of functions that
specifically look for boot loaders. ATM there is only one
function that will allow an installation allways. In the futre
we hope to have user defined funcitons for specific bootloaders.
|
| | |
|
| |
|
|
| |
helps the user to gain better knowledge of FAK.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
