Message: previous - next
Month: September 2012

Re: [trinity-devel] TDEHW Summary

From: Darrell Anderson <humanreadable@...>
Date: Sun, 2 Sep 2012 22:01:28 -0700 (PDT)
> OK, thank you for the information.  If you want to, you
> can comment out line 999 of file tdehardwarebackend.cpp and see if the
> TDEHWLib backend handles the same situation(two identical volume labels)
> gracefully or not.  If it does, that line of code can be removed from GIT.

I rebuilt tdelibs/tdebase 64-bit. I see what you did with the optical disk mount point naming. Looks great to me, best of both worlds and satisfies all concerns. Fundamentally, the previous scheme of appending a number is no different, but the new scheme actually is nicer and saner. :-)

I plan to run a 32-bit package build set overnight but the final testing will be late tomorrow at the earliest. The machine with two optical drives is a PII with an IDE hard drive. V---e---r---y---s---l---o---w to install a full updated package set. :-)

I'll run the first test with line 999 as is. I should see something like this:

Slackware Install1 (hdb)
Slackware Install1 (hdc)

Or something similar.

Unless the old numerical appendage is in the tdehwbackend code, I'm curious to see what happens with a package rebuilt with line 999 commented out. We'll see how that goes tomorrow. :-)