I found NetBSD won't boot either, at least with VirtualBox 2.1. I recall seeing that DragonFly BSD also didn't boot on an older version of VirtualBox without a patch, so it seems it isn't ideal for any of the BSDs right now.
Well, technically it isn't installed by default on FreeBSD or NetBSD (and possibly DragonFly BSD). FreeBSD stopped shipping it in base some six years ago (http://bsd.slashdot.org/article.pl?sid=02/05/14/0015234), and I'm not sure NetBSD ever included it in base. OpenBSD is the only BSD I know of that continues to include it in base; they have to, their package install system depends on it.
(On the other hand, in SVR4-land, HP-UX started including Perl by default in 2001, it seems.)
Though pinholes aren't necessarily a sign of "rot", they can also just be manufacturing defects. Normally, error correction should deal with them. (Obviously, if the CD is "rotting", over time error correction might not be able to cover things up.)
I've owned several CDs pressed by PDO that exhibited "bronzing"; in fact, I just noticed one a few weeks ago (on the Hyperion label). But I also own CDs that were pressed in 1983 and they still play perfectly well. (I wish I could say the same for the longevity of CD-Rs I've burnt.)
(Not to mention we might not be talking about "poor unwitting users", we might be talking about a user in a business context who's not supposed to have root privileges but can suddenly grant themselves the ability to do things they're not supposed to. What's that statistic about security breaches from the inside of a company?)
OpenSSH follows the same version numbering approach as OpenBSD, which is that for each release they simply increment what would normally be called the minor number until it reaches 9, then what would normally be construed as the major number is incremented, then they go back to incrementing the minor number.
One may wonder why they don't simply use a single number for releases, given there's no meaning or discernable advantage (to an outsider, that is) to using a pair of numbers.
(Perhaps the numbering scheme is simply a hold over from OpenBSD's NetBSD origins over a decade ago. NetBSD does use "point numbers" to convey the relative importance of releases.)
Slashdot Mirror
I found NetBSD won't boot either, at least with VirtualBox 2.1. I recall seeing that DragonFly BSD also didn't boot on an older version of VirtualBox without a patch, so it seems it isn't ideal for any of the BSDs right now.
Well, technically it isn't installed by default on FreeBSD or NetBSD (and possibly DragonFly BSD). FreeBSD stopped shipping it in base some six years ago (http://bsd.slashdot.org/article.pl?sid=02/05/14/0015234), and I'm not sure NetBSD ever included it in base. OpenBSD is the only BSD I know of that continues to include it in base; they have to, their package install system depends on it. (On the other hand, in SVR4-land, HP-UX started including Perl by default in 2001, it seems.)
Though pinholes aren't necessarily a sign of "rot", they can also just be manufacturing defects. Normally, error correction should deal with them. (Obviously, if the CD is "rotting", over time error correction might not be able to cover things up.)
I've owned several CDs pressed by PDO that exhibited "bronzing"; in fact, I just noticed one a few weeks ago (on the Hyperion label). But I also own CDs that were pressed in 1983 and they still play perfectly well. (I wish I could say the same for the longevity of CD-Rs I've burnt.)
(Not to mention we might not be talking about "poor unwitting users", we might be talking about a user in a business context who's not supposed to have root privileges but can suddenly grant themselves the ability to do things they're not supposed to. What's that statistic about security breaches from the inside of a company?)
OpenSSH follows the same version numbering approach as OpenBSD, which is that for each release they simply increment what would normally be called the minor number until it reaches 9, then what would normally be construed as the major number is incremented, then they go back to incrementing the minor number. One may wonder why they don't simply use a single number for releases, given there's no meaning or discernable advantage (to an outsider, that is) to using a pair of numbers. (Perhaps the numbering scheme is simply a hold over from OpenBSD's NetBSD origins over a decade ago. NetBSD does use "point numbers" to convey the relative importance of releases.)