yeah, compiling can drag on slower machines, but during the gentoo install (or whenever) you can alter your optimization flags for speed or size and what not. the reason i prefer the pain of compiling everything from source is that portage gives you full control of conditional compiling through use flags in a framework like apt. its more involved, but you don't have to dig through make files, just run emerge -pv <package atom> and see what you can exclude and what you want to include. so long as you don't miss something incredibly important, it makes things run smoothly (or if you botch it, not at all). not the most scientific metric, but on this dell inspiron e1505 (intel core duo 2Gz each processor, 100Gig ram) running XP, fruity loops by itself on a clean boot could choke it up if i added 3 vst synths and some intensive effects. on gentoo, i've ran the jack server with maybe 6-9 other apps at a time for hours while compiling and trying new programs and at one point i recompiled my kernel. after 3 hours not even an xrun. if compiling is still an issue though, you can create a tool chain with the crossdev package to compile for that architecture on a different gentoo machine that can deal with it. then once you've produced the binaries you can load the customized app onto the target machine. given that most folks don't have another gentoo machine (having one can be trouble enough), i don't think it would be unthinkable that some sort of community crossdev server could be created where packages could be emerged and downloaded from at later times. it would definitely add to the audio distro community as well, because then packages that worked well could be shared without recompiling again. On Tue, Jun 30, 2009 at 7:26 PM, carmen &lt;_(a)whats-your.name&gt; wrote:

Raffaele Morelli wrote: I'm slowly turning my wife's old laptop (2.8GHz Celeron, 768MB RAM, saddled with older Intel chipset) into a synthesizer/effects box. It currently has Ubuntu Studio on it. While I have the wireless antenna turned off (we have no wireless network around here), I've never disabled the wifi kernel modules or drivers. And it runs along quite happily at latencies between 5-10 msec using an external USB audio interface ... I seem to recall that the problem with wifi wasn't the presence of the drivers, it was the fact that the system was incessantly trying to make a wifi connection. Maybe that's something Network Manager does that doing your networking using command line stuff doesn't? -- David gnome(a)hawaii.rr.com authenticity, honesty, community

On Wed, Jul 01, 2009 at 03:00:18AM -0700, Justin Smith wrote: I have an EEE 1000 and I use it constantly with Debian, and have performed with it a good half-dozen times now, and rehearsed and practiced on it many more. I'm very happy with Debian-EEE. I created packages for the RT kernel and relevant drivers for it, and uploaded them here in case anyone wants them: http://restivo.nfshost.com/projects/eee/debs/ I dislike the Network Manager intensely, so I turned it off. I just type "sudo iwlist ra0 scan" when I need to find what's out there. Nowadays I just use a Sierra Wireless USB adapter with the Sprint PCS network instead, and very rarely fire up the wifi anyway. -ken

Sound problem was a dirty speaker jack. I'm pretty deaf on that side so its hard to keep track of what's going on.. Norv ____________________________________________________________________________________ Access Yahoo!7 Mail on your mobile. Anytime. Anywhere. Show me how: http://au.mobile.yahoo.com/mail