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.
It was still  running fine. I needed the partition space.
At this point in time my 64studio installs include:

64studio 2.1 dist-upgraded lenny. (+ kde4 desktop).
64studio 3.0 beta2 upgraded to beta3 (kernel-builds-testing).
64studio 3.0 beta3. (x2 installs on different PC's)
64studio master build 07-Mar-2009 15:23 728M.
64studio 3.0 built using  pdk .

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.

How can you help?

1) Send\post any errors, issues you find to forum\mailing list.
2) Send\post any positive findings. Things you like the most.
3) Help out on the forums, Share your knowledge.
4) Test the distro and post reports.
5) keep a clean spirit, open mind & respect for others feelings.
6) Don't be afraid to ask questions.
7) Write  HowTo's  help documents and guides.

How can 64studio help you?

1) Keep the Forum up do date and user friendly.
2) Provide a community Wiki Page.

Feel free to add to these lists

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 bh090321.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.

http://lists.64studio.com/mailman/listinfo/pdk-devel

_______________________________________________
64studio-devel mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-devel

Reply via email to