Testing alphabetas rc's & daily-builds
Hi All, The aim is the released version. I have just installed the latest 64studio_master image on a multi partition disk. This saw the removal of my oldest 64studio 2.0 dist-upgraded to 2.1 dist-upgraded to lenny version. I don't find much time for computer music composition so helping users with software use and problems is not one of my strong points, but we have many 64studio users who shine in this field. Checkout Quentins forum and 64studio mailing lists. We have a flexible team and one of the best developers available. The community is at the heart 64 studio and I have no doubt in saying the community either makes or breaks any distribution. I remember reading how important it is to put something back in to the GNU\Linux community and I fully agree. Cash donations are one way to support your distro but contributing to the community is top of the list to me. I have lost count of the dist-uprades installs I've done after 2.1 was released and leading to the 3.0 release but I do keep documents\history. This is the first step I think to testing. I don't remember the install, setup, configure process. I make use of the systems strong points. Today's .bash_history is tomorrows install routine. $ cp .bash_history ~/bh-today's-date.txt Is the install, setup, configure process for the next install. This simple step will reduce install setup time by half. Backup your backups, and just to be sure back them up. Happy Hacking :-) Cheers! Dave.