FreeBSD 4 Bug may be present in Playstation 4/5
1–10 of 67 posts
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#2FreeBSD 4.x was considered by many as the most stable FreeBSD ever.
Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases.
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#3FreeBSD 4.x was considered by many as the most stable FreeBSD ever. Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases. https://www.freebsd.org/releases/
Wasn't this the last version before Matthew Dillon forked the project? I remember seeing some public arguments about SMP and few details of the kernel that resulted in fork and the new version 5.x.
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#4FreeBSD 4.x was considered by many as the most stable FreeBSD ever. Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases. https://www.freebsd.org/releases/
Wasn't this the last version before Matthew Dillon forked the project? I remember seeing some public arguments about SMP and few details of the kernel that resulted in fork and the new version 5.x.
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#5Time to buy a PS5 before this gets patched!
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#6Time to buy a PS5 before this gets patched!
It's already patched:
> Early tests seem to indicate that a crash is indeed present in PS4 up to 11.00 included, and PS5 8.20 included. (Which would put the patch for this issue at firmwares PS5 8.40 and PS4 11.02)
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#7FreeBSD 4.x was considered by many as the most stable FreeBSD ever. Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases. https://www.freebsd.org/releases/
> Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases.
Mostly because 5.x took so long to be released.
IIRC, shortly after this experience the FreeBSD folks went from a feature-based release cycle to a time-based release cycle: everyone wanted feature X (and X and Y) in Next Release, and things got pushed and pushed.
So by having a steady cadence, a feature could be integrated regularly into HEAD, and folks didn't have to wait too long before a STABLE release was cut with all the latest and greatest stuff (that couldn't otherwise be backported because of compatibility guarantees).
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#8FreeBSD 4.x was considered by many as the most stable FreeBSD ever. Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases. https://www.freebsd.org/releases/
Yeah a lot has changed since then. We had to keep track of stable branch to get close to Linux desktop features most of the time, sometimes even 'current' branch. Today you can use release for 99.9% of use cases, and upgrading releases minor or major is pretty straightforward and way faster than it used to be.
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#9FreeBSD 4.x was considered by many as the most stable FreeBSD ever. Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases. https://www.freebsd.org/releases/
> Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases. Mostly because 5.x took so long to be released. IIRC, shortly after this experience the FreeBSD folks went from a feature-based release cycle to a time-based release cycle: everyone wanted feature X (and X and Y) in Next Release, and things got pushed and pushed…
Same experience which lead Java to change from feature-based release cycle to time-based release cycle later. Make regular releases, everything that is ready gets included, everything else can go onto the next train. Far better.
Re: FreeBSD 4 Bug may be present in Playstation 4/5
#10FreeBSD 4.x was considered by many as the most stable FreeBSD ever. Mainly because there were 11 point releases of fixes and enhancements (4.11), as opposed to today where FreeBSD major version only have 3-4 point releases. https://www.freebsd.org/releases/
It was not only the most stable, but for many applications, especially in networking, it was also the fastest single-threaded operating system, beating easily Linux and Windows XP or 2000.
Unfortunately for FreeBSD, the launch of the Intel Pentium 4 with hyper-threading in 2003, then of the AMD dual-core CPUs in 2005 have made quickly FreeBSD 4 completely obsolete.
The smaller FreeBSD team has required many years until achieving a decent implementation for multi-threaded CPUs and during that time they have remained long behind Linux and other operating systems.
Besides perfect stability (it was normal to not reboot FreeBSD 4 for years) and great networking performance, it also had a much more reliable file system than the competition.
Despite the fact that Windows XP used NTFS and Linux had at least 3 file systems with journaling at that time, where journaling was supposed to make the file systems crash-resistant, I have seen at that time (around 1999-2003) many cases of file system corruptions after power outages, on computers without UPSes which used NTFS or Linux file systems with journaling (on Linux EXT2 without journaling any power outage was very likely to require a complete reinstallation).
During the same power outages, the computers with FreeBSD that used the UFS file system with "soft updates" never experienced any file system corruption, despite the fact that UFS with "soft updates" was not a journaling file system, but only one where the disk write operations were carefully ordered in such a way as to prevent unrecoverable file system corruption in the case of a crash.