arch bash cakephp dauth devops drupal fosdem foss git golang information age linux lua mail monitoring music n900 netlog openstack photos php productivity python real life thesis travel uzbl vimeo web2.0
For me personally this means I can start working on the next step towards my goal of having all my systems "metadata" centrally stored (along with my real "data"), and the possibility to reconstruct all my systems in a deployment-meets-backup-restore fashion ( see rethinking_the_backup_paradigm_a_higher-level... )
The last few weeks I/we've been quite busy fixing up many things related to aif and the arch release stuff in general. The kernel guys are now at 2.6.29-rc8, so a stable release won't be long anymore and I want to get as much things fixed before 2.6.29 is out, so we can release soon after. (with /arch/setup and /arch/quickinst replaced by aif)
I've posted a project in Arch Bounty about install templates/metapackages that I think could be a very good way of having 'semi-automated' installations (on the package side).
I didn't know at the time of the automatic installations of AIF, with some kind of metapackaging and AIF install profiles it would be easy to implement.
You can take a look at the proposal here: http://bounty.archlinux.ca/projects/3/
Posted by void on Sat Oct 24 12:21:02 2009
I've replied on the project page. good luck.
Posted by Dieter_be on Sun Oct 25 09:04:49 2009