Daniel James wrote:
>
>> it was no picnic getting things this far and I will not be surprised 
>> if users report problems similar to the ones I encountered.
>
> I'd be very interested to read about that, as we're currently 
> developing a product based on Jaunty sources.
>

Some background: I want at least one machine here to remain an i386 box. 
Some software has not yet made the transition to 64-bit, and I need/want 
that software (SC3, the Lightscribe stuff, VST plugins, etc). So, I 
tried to install Jaunty via the DVD images (i386 and amd64), both of 
which failed at exactly the same point *after* the installer had 
partitioned the disk. I won't bother detailing my actions, I'll write it 
all up, but the initial outcome yielded a hosed disk partition and no 
usable Jaunty.

And yes, the problem with the DVD installer is known to the distro devs. 
So I re-installed a stock 8.10 (i386) and used the Upgrade Manager to 
successfully upgrade to Jaunty. My troubles began after installing the 
Ubuntu Studio meta packages. Again, I won't go into the details now, but 
I have quite a list of things I had to do to get the system to a 
workable state.

>> I also have a few recommendations for all multimedia distro maintainers.
>
> I'm all ears :-)
>
>

Two especially annoying details that might be handled by the distro 
installer and its configuration tools: The entries in 
/etc/security/limits.conf and the creation of an audio group with the 
user included. I don't see why the user has to take these steps, they're 
the same for every installation, so why not automate them ?

I have more to say about things like Pulseaudio, insufficient support 
for the touchpad, HAL polling, and other annoyances, but you'll have to 
wait. Or you can try installing Jaunty like I did to see which of my 
troubles occur for you.

Basically, anything that is going to be configured identically across 
all installations should be taken out of the user's concerns. For 
example, I can't figure why Pulseaudio is installed as the primary sound 
server in an audio production system. If it is included there ought to 
be a 1-click solution for disabling it, but at this time a rather 
lengthy series of hoops must be negotiated. And on and on and on it 
goes, one annoyance after another.

Having said that, I'll also say that the new system is beautiful. Now 
that I have some stability with it I might try some "serious" recording 
with it on my band's gig this weekend. I'll let you know how that goes.

The article will appear in three or four weeks. I'll be happy to send it 
to you if you'd like to read it before it goes on-line.

Best,

dp

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

Reply via email to