Re: [Rosegarden-user] The future of Linux sure looks bleak...

[k-12]

Tim Munro wrote:

 A time lag frequently exists between the introduction of new 
 hardware and the availability of suitable Linux drivers.  And 
 even when these drivers or kernel patches become available, a
 significant time lag can exist before the changes make it into 
 a distribution.  Especially one as conservative as Slackware, 
 my personal favorite.

Last year I struggled with taming an Asus-g73sw laptop: I too 
started by wiping the bundlecrap off the disk and installing 
about half a dozen linux distros on it, and windows-7 but then 
that was it for windows, XP could NOT be installed. On the other
hand the backlit keyboard works only under windows. It isn't 
just linux that throws fits when you have to move up. As for 
KDE4, yeah, eyecandy puke but I got it working now and just 
don't use any feature I don't like. I can't call it inferior 
to KDE3 even if I had to let go a couple of favorite features.  

The short of the long is that any major software or hardware 
move requires a good year to beat into shape.


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Re: [Rosegarden-user] The future of Linux sure looks bleak...

[Tim Munro]

david wrote:
  So you add ANOTHER DRIVE to the system That's what I do.

Yes, I could have picked up an old drive somewhere and stuffed it into
the box.  I even considered picking up an IDE to SATA adapter so that I
could attempt to use a newer drive, but the bottom line was that the
machine itself was hopelessly out of date.  A 550MHz Pentium III
processor with 256M of ram (apparently HP's upper limit for that
motherboard) is hardly sound-barrier stuff these days.  Rather than
pouring more money into a lost cause, I decided to upgrade.

  Didn't have to modify any apps to run on 64-bit. Which apps are you
  talking about?

The first example that comes to mind is an obscure program called
Rosegarden and how it deals with library paths.  On a Slackware
system, 32-bit stuff typically goes into /usr/lib, while 64-bit stuff
ends up in /usr/lib64.  Because I had built and installed DSSI and
LADSPA from source, they ended up in the 64-bit library where
Rosegarden couldn't find them.  My initial workaround was to place
symlinks in the 32-bit library, but eventually I got around to patching
src/sound/DSSIPluginFactory.cpp and src/sound/LADSPAPluginFactory.cpp
with more complete path info.

Other programs that needed adjustment were mostly things that I had
written years ago that contained snippets of truly ancient code.  Back
in the 16-bit days, for instance, we made assumptions about the size of
an int that are no longer valid.

Tim

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user