4 Sep
2013
4 Sep
'13
9:09 p.m.
After more than 10 years of service my first ever Linux system
died yesterday. The original configuration was P4, 0.5G memory,
two IDE HD of 60G each, and it pretty much stayed like that.
Two years ago the power supply blew up and was replaced by an
external one (too big to go inside). Last year the first HD
failed, and yesterday evening the second.
This was the system on which I developed almost everything I
ever released, so it carries lots of memories... Maybe one
of the reasons it decided to go to the eternal processing
fields was that it couldn't really cope with A3. I've mixed
20+ tracks using A2 on that system, but 350MB resident memory
for an empty session was just too much...
The new zita1 will probably be a Fujitsu P510, one of the
reasons being that this is one of the few still having at
least one PCI slot, so I can still use my sound cards. Any
suggestions for alternatives are welcome !
More CPU and memory will in the end make me less frugal, but
I'll resist the tendency :-)
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
4 Sep
4 Sep
10:47 p.m.
Hello Fons!
I suppose there are just as many answers, that there are users on this list.
I have a quad core Athlon 3GHz and 2GB of memory.l Since I use a text-based
system, that might be just right for you. :-) My motherboard is a n68-s3ucc
asrock. I suppose that might no longer be in stock, snce I got it in september
of 2011. But both for text-based swork and the occasinal excursions into
GUI-land I've been happy with it.
You'll most certainly get more up to date answers and more refined answers
at that, but this at least is one solution. and I don't see a reason for this
system to die anytime soon. I've usually had a very lucky hand with my sstems.
though I'm not sure how much this was due to adequate hardware or just using
the text-based part of Linux and its usually low demands. :-)
Thanks for years and years of development and improvement of our work! I've
enjoyed lots of that, even subtracting the purely gaphical applications, I got
so much from the wonders, that you developed. Thanks!
Warm regards
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
5 Sep
5 Sep
8:48 a.m.
On 09/05/13 05:09, Fons Adriaensen wrote:
one of the
reasons being that this is one of the few still having at
least one PCI slot
Hi Fons. Sad day.
I have just built a new system comprising an ASUS H87-PRO which has 3
PCI slots and several pcie as well. Uses the new HASWELL Intel cpu's but
it's a great board. UEFI bios too...
hth
best
g
10:45 a.m.
Fons Adriaensen <fons(a)linuxaudio.org> wrote:
The new zita1 will probably be a Fujitsu P510, one of
the
reasons being that this is one of the few still having at
least one PCI slot, so I can still use my sound cards. Any
suggestions for alternatives are welcome !
I just built a Haswell Xeon-based workstation with a Supermicro X10SAE-O
motherboard which has 2 regular PCI slots. ECC is a requirement of
mine[1], so I didn't have a lot of choices regarding motherboards (and
I also wanted a TSX-capable CPU).
If you do go with a Haswell Xeon, beware GPUs are built into the CPUs
nowadays and not the motherboard (even though the motherboard has video
outputs). I didn't know that, but it's a good thing I don't care for
graphics and a friend had an unused Radeon card.
I also have a fanless Zalman FX100 CPU cooler, fanless PSU, with only
one slow, giant case fan. It's inaudible unless I'm focusing on it over
other ambient noise.
[1] - I surprised ECC memory hasn't taken off at all in the audio world
(from what I can tell). I often work on servers, so it's strangely
uncomfortable to have any important data/work on a machine without
ECC (especially given the size of memory and the aggressiveness
of Linux VFS caching).
12:27 p.m.
On Wed, Sep 04, 2013 at 07:09:56PM +0000, Fons Adriaensen wrote:
The new zita1 will probably be a Fujitsu P510, one of
the
reasons being that this is one of the few still having at
least one PCI slot, so I can still use my sound cards. Any
suggestions for alternatives are welcome !
If you wanted to go the AMD route, ASUS are still making some
motherboards with 2 or more PCI slots. I'm still using Athlon64x2
CPUs on Asus M3A78-PRO boards (with ECC RAM) in my DAWs, but last
time I checked there were still current boards with 3 PCI slots.
Boards with 2xPCI are still fairly common.
In general I prefer ECC memory, high efficiency CPUs and low-power
graphics hardware for audio work. Keeping the power consumption down
allows fan noise to be minimised. My location DAW can run fanless.
I also prefer to run efficient software to keep CPU load (and heat)
down.
Thanks for writing such efficient software BTW :-)
John
10:53 p.m.
On Wed, Sep 4, 2013 at 12:09 PM, Fons Adriaensen <fons(a)linuxaudio.org>wrote;wrote:
After more than 10 years of service my first ever
Linux system
died yesterday. The original configuration was P4, 0.5G memory,
two IDE HD of 60G each, and it pretty much stayed like that.
Two years ago the power supply blew up and was replaced by an
external one (too big to go inside). Last year the first HD
failed, and yesterday evening the second.
This was the system on which I developed almost everything I
ever released, so it carries lots of memories... Maybe one
of the reasons it decided to go to the eternal processing
fields was that it couldn't really cope with A3. I've mixed
20+ tracks using A2 on that system, but 350MB resident memory
for an empty session was just too much...
The new zita1 will probably be a Fujitsu P510, one of the
reasons being that this is one of the few still having at
least one PCI slot, so I can still use my sound cards. Any
suggestions for alternatives are welcome !
More CPU and memory will in the end make me less frugal, but
I'll resist the tendency :-)
Ciao,
Another one bites the dust... Should've run Non on it instead. Seriously
though, it's a shame. Fortunately, there are still quite a few
motherboards out there with at least one PCI slot. I trust you had
everything backed up!
11:08 p.m.
On Thu, Sep 05, 2013 at 01:53:33PM -0700, J. Liles wrote:
Another one bites the dust... Should've run Non on
it instead. Seriously
though, it's a shame. Fortunately, there are still quite a few
motherboards out there with at least one PCI slot. I trust you had
everything backed up!
Almost... Lost two evenings of work on AP algorithms, but I
have some 30 pages of scribbled notes about that, and the
(Python) code itself wasn't that complicated, I'm rewriting
it right now. Still, should learn to backup every day.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
11:38 p.m.
On Thursday 05 September 2013 17:30:26 Fons Adriaensen did opine:
On Thu, Sep 05, 2013 at 01:53:33PM -0700, J. Liles
wrote:
Let amanda do it in the middle of the night Fons. I've been using it,
using virtual tapes on a terrabyte hard drive now, but with real tape since
about 1999. Real tape is a maintenance headache, if you have smartctl
watching the drives, they'll warn you well enough in advance that you can
replace the drive ahead of a total failure. Made use of that once since I
moved it to vtapes, about 7 years back. It works over the network, so my
milling machine and lathe control boxes are backed up nightly too.
Cheers, Gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://gene.homelinux.net:6309/gene> should be up!
Ben, why didn't you tell me?
-- Luke Skywalker
A pen in the hand of this president is far more
dangerous than 200 million guns in the hands of
law-abiding citizens.
Another one bites the dust... Should've run
Non on it instead.
Seriously though, it's a shame. Fortunately, there are still quite a
few motherboards out there with at least one PCI slot. I trust you
had everything backed up!
Almost... Lost two evenings of work on AP algorithms, but I
have some 30 pages of scribbled notes about that, and the
(Python) code itself wasn't that complicated, I'm rewriting
it right now. Still, should learn to backup every day.
Ciao, 
6 Sep
6 Sep
9:40 a.m.
On 05.09.2013 23:08, Fons Adriaensen wrote:
On Thu, Sep 05, 2013 at 01:53:33PM -0700, J. Liles
wrote:
Hi,
sure, regular full backups are a great thing. But there's one simple
thing I like to do especially with code: Setup your repositories on a
different machine (like a rented root server, or a public hoster like
github). Then always push your commits regularly (oh, it compiles again
- push it :D). Makes working on different machines easy, too. It's
simpler than setting up and adhering to a strict backup plan and it's
naturally incremental and closely tied to the development process.
Reminds me: I have to throw on my full backup again..
Flo
Another one bites the dust... Should've run
Non on it instead. Seriously
though, it's a shame. Fortunately, there are still quite a few
motherboards out there with at least one PCI slot. I trust you had
everything backed up!
Almost... Lost two evenings of work on AP algorithms, but I
have some 30 pages of scribbled notes about that, and the
(Python) code itself wasn't that complicated, I'm rewriting
it right now. Still, should learn to backup every day.
Ciao,
2:28 p.m.
On Fri, Sep 06, 2013 at 09:40:39AM +0200, Florian Paul Schmidt wrote:
sure, regular full backups are a great thing. But
there's one simple
thing I like to do especially with code: Setup your repositories on
a different machine (like a rented root server, or a public hoster
like github). Then always push your commits regularly (oh, it
compiles again - push it :D). Makes working on different machines
easy, too. It's simpler than setting up and adhering to a strict
backup plan and it's naturally incremental and closely tied to the
development process.
That's more or less how all my audio software is stored.
There's a master git repository is on an USB stick, and
everything is cloned on all the machines I regularly work
on.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
11:39 p.m.
On Fri, 06 Sep 2013 09:40:39 +0200 Florian Paul Schmidt
<mista.tapas(a)gmx.net> wrote:
sure, regular full backups are a great thing. But
there's one simple
thing I like to do especially with code: Setup your repositories on a
different machine (like a rented root server, or a public hoster like
github). Then always push your commits regularly (oh, it compiles
again
- push it :D). Makes working on different machines easy, too. It's
simpler than setting up and adhering to a strict backup plan and it's
naturally incremental and closely tied to the development process.
Reminds me: I have to throw on my full backup again..
Don't do backups! Have them done automatically!
I recommend backuppc, it also "catches" machines that aren't running
24/7.
And when you work with remote repositories (you should), don't forget
to back up these too.
Have fun,
Arnold
PS: No one wants backups. People only want restore.
3898
days inactive
3900
days old
linux-audio-dev@lists.linuxaudio.org
10 comments
9 participants
participants (9)
-
Arnold Krille -
Eric Wong -
Florian Paul Schmidt -
Fons Adriaensen -
Gene Heskett -
Geoff Beasley -
J. Liles -
John Rigg -
Julien Claassen