Just to clarify
For what it's worth, I updated to jrd's gcc 4.3.2 and glibc 2,9 back on July 4, and ran until yesterday with that, without any problems whatever, on my main desktop. Updated again yesterday, to gcc 4.4.1 and glibc 2.10.1. Update went smoothly, and so far haven't had any issues with any installed applications. Seems very solid.
It's always very good to hear something like this. You guys are awesome.
, I have 9 PCLOS installations on this machine, all completely backed up with rsync, so if I blow one up, it's no big deal to boot to another, and rsync the backup copy to the partition that went pear shaped.
If someone does want to test this, it's still recommended to do so on a separate test installation
, rather than on one's only stable installation. The test installation can be a fresh installation
from an official released
, or a remastered disk
, or an rsynced copy,
of one's main installation
, done from the liveCD
on the non running
The more installations the rolling upgrade of the PCLOS core is tried on, the more chances of any problems being detected, and on what specific hardware those problems might show up on, should any be reported. Only by testing
, and the reporting of any problems
, can any bugs found be addressed and fixed.
For the record this installation is a fully upgraded TR6 installation, with the testing section always enabled, on the following hardware; (Not a VM)Gigabyte GA-MA770-DSP3 motherboard with AMD/ATI chipset
AMD 64 x2 5200+ CPU
500 watt PS
1 IDE hard drive
2 SATA hard drives
1 IDE optical device (DVD +/- R/RW writer)