[rear-devel] RFC: what should I do with my ideas for "rear 2.0"?

Schlomo Schapiro schlomo at schapiro.org
Thu Oct 29 16:22:54 CET 2015


I tried skimming over the SDB article... Quite impressive!

Do you mean something like this (I use Debian/Ubuntu instead of SUSE)?

* Boot computer from ReaR rescue media
* configure hard disks / partitions / filesystems
* run "debootstrap wily /mnt/local ..."
* install boot loader
* reboot & done

(Yes, I am suffering from the super slow Ubuntu installation process and
the general lack of good documentation for preseed).

I think that such an approach would work only for people who have 100%
automation for their system setup & configuration. For others the
traditional approach probably works better.

In general, I am not sure how to solve the chicken-egg problem if you want
to do all installation by restoring a full backup. How would you setup a
new system? How would you imagine to replace the traditional process of
"source -> binary package -> installation media -> boot computer ->

BTW, if you need to add stuff to ReaR to make your vision happen: Please go
ahead! We always value your contributions and I think that ReaR on SUSE
would not be as good as it is without your work.

Kind Regards,

On 29 October 2015 at 15:51, Johannes Meixner <jsmeix at suse.de> wrote:

> Hello,
> On Oct 29 14:51 Schlomo Schapiro wrote (excerpt):
>> if you have a specific proposal then maybe a GitHub issue is best.
> I should have mentioned that my "some 'revolutionary' ideas"
> are rather unspecific - i.e. more about very general changes.
> And send a teaser to this mailing list to draw attention.
> Here it is:
> My basic "revolutionary" idea for a future "rear 2.0" is
> to transform rear into a generic installer.
> I mean a generic installer that can be used both
> - for the initial installation and
> - for re-installation after a disaster.
> My basic reasoning behind is described at
> "Deployment via recovery installation" in
> https://en.opensuse.org/SDB:Disaster_Recovery
> Some higher-level details:
> Instead of first doing an initial installation with the
> specific installer of each Linux distribution, then
> set up the rear recovery to finally overwrite the initial
> installation with a recovery installation, I am thinking
> about eliminating the Linux distribution specific installers
> and do it only with rear.
> This does not necessarily require a generic rear
> installation system.
> At least for the SUSE installation system ("inst-sys")
> it does "just work" to run a selfmade installer script
> instead of the SUSE-specific installer YaST, see
> "Generic system installation with the plain SUSE installation system"
> at https://en.opensuse.org/SDB:Disaster_Recovery
> At least for me it was really shocking to see how lightning-fast,
> powerful, and straightforward such a direct and fully automated
> installation is.
> I assume once you experienced that yourself, you never again
> like to use a Linux distribution specific installer ;-)
> If rear could be used as generic installer, one could
> run it directly on the plain SUSE installation system.
> I have no experience with the installation systems
> of other Linux distributions but I hope one could
> also run a selfmade generic installer on them
> instead of their own installers.
> A precondition to use rear as generic installer is
> that one can specify the installation parameters
> (partitioning, filesystems, mountpoints, bootloader,...)
> in human readable and human editable format in a
> configuration file for the generic rear installer.
> Does this sound interesting?
> Kind Regards
> Johannes Meixner
> --
> SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
> Graham Norton - HRB 21284 (AG Nuernberg)
> _______________________________________________
> rear-devel mailing list
> rear-devel at lists.relax-and-recover.org
> http://pikachu.3ti.be/mailman/listinfo/rear-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pikachu.3ti.be/pipermail/rear-devel/attachments/20151029/6288616c/attachment.html>

More information about the rear-devel mailing list