Here are my current thoughts for GNAP 2 : POST-OVERLAYING Currently there is no way of modifying the overlayed configuration, short of rebuilding the ISO file or reburning the CF. The idea is to support multiple successive overlay sources (Floppy, USB key, network-fetched tarball) that would get optionally triggered as soon as possible (when network is up, fetch the network conf, etc.). That way, part of the configuration would be overlaid from not-burned-in sources. This would be implemented as new overlay-like rc-scripts, activated and configured from overlay.conf, that would run as soon as possible. CONFLETS A single overlay directory makes it difficult to reuse standard configuration options. Allowing gnap_overlay to take multiple directories and tbz2 files as sources for the overlay file on the ISO would allow more flexibility. For example, a typical shorewall configuration could be provided as a standard "conflet" that people could easily include into their own ISOs. This would be implemented by enriching gnap_overlay to support multiple sources rather than just one directory. MODULARITY Currently you can't easily add optional features in the provided GNAP core, the only way is to rebuild a core completely. Feature additions (like rp-pppoe or firehol) make the core heavier while not being used by everyone. The idea is to allow to customize core contents before overlaying the configuration in. Several "modules" could be produced along with a basic core. Problems to solve: squashfs remastering would require root rights (breaks the overlay-needs-no-root concept), dependencies issues when multiple modules need the same dep package, how to integrate module building into the catalyst process... DISKLESS SUPPORT PXE support would allow a completely diskless GNAP system that would fetch everything from the network. Not sure how I would do it, need to learn how it works first.
CONFLETS was done in 1.5 MODULARITY will be done in 1.7 Another feature that will appear in 1.7 : R/W OVERLAY Sometimes you need to change the configuration but don't want to burn a new CF (or reboot). R/W overlay allows to overlay from a specific device at boot (/dev/floppy or a second partition on the CF) and to push back modified files to that partition later on. POST-OVERLAYING using floppy will be done in 1.7, the rest should appear in 1.8.
Sugests: * integrate sfdisk in gnap * root password parameter
More suggest: - use "genkernel --maxkernpackage=" to create kernel extensions for gnap
Other ideas: - Reduced portage snapshot to ship with each version (to facilitate extensions and rebuild). - Full distcc support
New Feature: Kernel Extensions Similar to other gnap extensions using "genkernel --maxkernpackage=" to create kernel extensions for gnap. So you can change the kernel of gnap without rebuild gnap-core.
Created attachment 62668 [details] rw-sync.sh script to save files to rw part
Created attachment 62679 [details] rw-sync.sh 0.3: added bak support, size info, an bug fixed * now with -b you can do bak of older conf * more info in the script (comments and size fo the tarballs) * now the tarball is made en mem not in CF
Created attachment 62743 [details] rw-sync.sh 0.4 (md5sum and optimizations) version 0.4 * lilttle fixes and optimizations * now the config file is stroed by default in /etc/rw-sync.cgf so must be added to itself to the file list if you want to save it * the script generate md5sum's for the tarball file and backup file. Koon remember to check the md5sum before load the files in init
Created attachment 62745 [details] rw-sync.sh (conftest added) a lil test added to check if CONFFIFLE will be saved or not. If -v it will warn the user.
add "-s <bauds>" option to gnap_overlay
Created attachment 63128 [details] rw-sync.sh 0.5 (added space check) rw-sync.sh 0.5 * now checks fro free space
Created attachment 63224 [details, diff] init.d/overlay patch (add tgz and md5 support) you need this patch to restore the files generated by rw-sync.sh
Created attachment 63226 [details, diff] overlay patch (fixed)
Created attachment 63232 [details, diff] over.ay patch (more fixes)
Created attachment 63233 [details] rw-sync.sh 0.5.1 (lil fixes)
create a new file to define services to add to startup
Created attachment 63234 [details, diff] overlay.patch (more fixes)
Created attachment 63235 [details, diff] overlay patch (a new fix)
Created attachment 63237 [details] rw-sync.sh 0.5.2 (a lil fix)
Created attachment 63239 [details, diff] overlay.patch (more fixes)
Created attachment 63241 [details, diff] overlay.patch (latest fixes for today :P)
Created attachment 63300 [details, diff] overlay.pacth (this really works) now use conf.d/overlay
Created attachment 63301 [details] conf.d/overlay file with the VARS needed by rw-sync.sh and overlay
Created attachment 63302 [details] rw-sync.sh 0.6 (fixes and conf.d/overlay use)
rw-sync.sh and corresponding overlay patches have been added to CVS, as well as support for portage snapshot files and distcc.
Version 1.8 ships with: - root password initialization through etc/gnap/chpasswd - support for kernel extensions - Reduced portage snapshot to ship with each version (to facilitate extensions and rebuild). - Full distcc support - rw-sync.sh - add "-s <bauds>" option to gnap_overlay - create a new file to define services to add to startup (etc/gnap/start_services) For future improvements, pleaes create new bugs
