Hi; Am Dienstag, 21. Oktober 2014, 07:46:40 schrieb Erich Titl: > Hi Folks > > now that I have finally grasped the finer detals of building LEAF, I can > head for a few things that IMHO are missing in LEAF > > - simple backup and restore > - simple upgrade > > So I did some brainstorming over a glass of red wine and came up with a > few function primitives which might help to achieve this goal. > > Prerequisites: > > - R/W access to boot and storage media, this unfortunately excludes CD > based installations. > - a web site which holds the image content for all supported architectures
Yves moved the current website to a github-based test environment during summer. While it worked, there has been made no decision where to host (URL), so it's still a proof-of-concept. If we move I'd like to have also a fresh look for the pages - they have been created 10 yrs ago, and that is visible. But more important: The current CMS fails to build the previous Packages page, probably it has grown too much. So a new site may allow to rebuild the Packgaes page which could be a starting point for your idea. At least it will allow to provide newer packages between releases (security fixes!). > - a mechanism for identifying the latest stable release. I am suggesting > a DNS txt record for this, something like 'latest.stable.releases.leaf.org'. > - a multi boot capable bootloader, I have been using grub for most of my > LEAF experience, but I believe syslinux will cut this too. I use syslinux to boot either "production" or "testing", but it requires to rename kernel/initmod and I have to take care about moddb. So it does work, but it requires manual intervention. We may improve our images to use grub instead syslinux, or finally investigate uboot, opening other worlds beyond i386/x86. > - sufficient space on the storage media for at least 2 bootable > partitions plus une partition for managing content. This is necessary > for systems with insufficient memory to manage everything in RAM > - all boot and package relevant parameters _must_ be defined in the boot > loader. Right now this only affects LRP and PACKAGEPATH. Can you explain more? > - configdp.lrp needs to be sufficiently stable across multiple releases configdb on the image changes very seldomly across multiple releases, but it changes very often cause its the lrp where all local config changes are stored, exactly with every save operation (shell history). > suggested primitives > > - clone > used to clone the current running system to the backup partition. > - revert > reinstall the primary boot partition with the contents of the backup > partition > - export > build a binary image of the current system for export using a web interface > - import > reimport the binary image to the primary boot partition Instead of export/import I just use scp with sshkeys. I'm doing regular backups of a dozen routers that way cron-triggered from a backup server. Though backing up configdb.lrp should be enough most of the time. > - upgrade > analyse the content of the primary boot partition, download new versions > of the installed packages along with the latest kernel and initrd > according to the architecture, build a moddb according to the modules > loaded and install everything to the primary boot partition. See above, I guess this won't work with syslinux. > The goal must be to have an updated ready to run leaf distro. > > Most of the necessary code to achieve this is already available in LEAF, > only a few functions have to be added. You may also have a look into repo/updater - something Andrew provided in 2009. Don't know if it's used or even works at all, and I'm not aware if it's documented how to use and test. But either it's something to start with; or we may replace it...? kp ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
