New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support also appropriate_dir/diskrestore.sh (similar as CONFIG_DIR/disklayout.conf) #2086
Comments
@jsmeix I would move the script to $CONFIG_DIR/scripts sub-directory to distinguish clearly between config files and scripts (albeit that everything is a script within rear) |
@gdha |
@jsmeix basically that is already possible via http://www.it3.be/2016/06/08/rear-diskrestore/ |
@jsmeix Perhaps I could simply use the var/lib/rear/layout/ directory In the past (when you had mentioned it somewhere) I had already a look at But this issue here is about to be able to manually make a diskrestore.sh |
I like to have that in ReaR 2.6 because I do need it It is just such a boring annoyance for me to install The basic idea behind is exactly the same as in the sections
|
Stale issue message |
Currently layout/prepare/default/010_prepare_files.sh
supports CONFIG_DIR/disklayout.conf
I suggest that also appropriate_dir/diskrestore.sh
should be supported in basically the same way.
Reason:
I would like to be able to provide a prepared appropriate_dir/diskrestore.sh
script that can get used as is for "rear recover"
or such a script can be manually adapted as needed which means
when appropriate_dir/diskrestore.sh exists during "rear recover"
MIGRATION_MODE is set to 'true' so that the user gets the
matching dialog where he can adapt it (i.e. same behaviour
as currently when CONFIG_DIR/disklayout.conf exists).
Why I like to provide a prepared appropriate_dir/diskrestore.sh?
I like to be able to use ReaR to quickly set up an arbitrary disk layout
via plain commands that I enter into my selfmade diskrestore.sh script,
provide that as appropriate_dir/diskrestore.sh and get that disk layout directly
via "rear recover" without any indirection via disklayout.conf.
Basically that means it must be possible to do "rear recover"
only with a diskrestore.sh and without any content in disklayout.conf.
I need to find out if that is possible with reasonable effort with current ReaR.
I fear there could be subtle dependencies on the contents in disklayout.conf
in various scripts in ReaR that run during "rear recover" so that it is not
possible in practice (with reasonable effort) to do "rear recover" without
the content in disklayout.conf.
For example currently 'LAYOUT_FILE' is used in the finalize scripts
that install the bootloader:
so some adaptions will be needed there
but at least what I see on first glance in
finalize/Linux-i386/660_install_grub2.sh
at laset GRUB2 installation should work without disklayout.conf
when GRUB2_INSTALL_DEVICES is specified...
The text was updated successfully, but these errors were encountered: