c0t0d0s0
I think the situation is pretty much similar to the "shoot the messenger" problem of ZFS. Some people are annoyed that ZFS reports errors because of corruption and blocks access to the data (of course without having any redundancy). However the alternative would be reading incorrect data. What's worse. Knowing that you have to recover data or processing incorrect data without knowing it.
And as i already wrote in a different comment: If there is a bug in the stuff writing the on-disk state, the bug should be addressed on the exact knowledge of the bug in the code reading the on-disk-state and thus doesn't make assumption what could be halfway correct, but by some piece of code that does the correct with the incorrect on-disk-state.
2. When there is a bug in the on-disk-state it should be addressed by the code that reads the data , not by a fsck tool.
2.1. The correction of the bug in the on-disk-state should be done on the basis of the exact knowledge about the bug and not by a generic check tool.
3. Repair is always based on assumptions. Those could be correct or incorrect. The more you know about the problem that led to the repair-worthy state, the more probable the assumptions are correct.
4. What is the reasoning behind the argument "when your metadata is corrupt , that the data is correct" and so you could repair metadata corruption without problems. It sounds more sensible to fall back to the last known correct and consistent state of metadata and data, based on the on-disk-state represented by the pointer structure of the ueberblock with the highest transaction group commit number with a correct checksum . The Transaction Group rollback at mount does exactly this.
But that aside: At the end the text is not about Linux, about Solaris or AIX, FreeBSD, NetBSD, OpenBSD. It's about portability. Either we have to accept that there is a lock-in to Linux for many opensource development and stop all this portability stuff.
The article is about saying: Hey, use gmake if you want ... but keep into consideration, that the target system may be something else than Debian Lenny.
The next thing: I would like to see a standard way to install software on Linux. 17 distinct packages for Linux, just one of Mac OS X and 2 for (Open)Solaris. A standard would be nice here ... really.
And you have to take the following into consideration: Outside of the enthusiasts group something like binary compatibility guarantees something important for the admins. Improvements are good, features are good. But not at the price of breaking every bridge behind. At the end this hurts the Unix franchise, as the Microsoft franchise is simply a much larger market. We can't afford to fragmentize the Unix business by being to GNU/Linux centric. Deal with it. Solaris won't disappear, the *BSD won't disappear. But we should be able to ensure, that all can participate from open source development. And one factor is further development of the Unix standards to keep them current with the technological development, and not just cooking it's own soup.
Obviously you didn't understand the point of the article. It's not about hating Linux or GNU ... it's just about the ability to use open source software outside the Linux Community without ending to throw out all this Linuxisms and GNUisms
At the end you can see it as the plea, that portability isn't just an afterthought ... and given the state of some makefiles and hard coded things in some open source developments you get the impression that it's a not-thought-about it at all.
PS: I'm from the Opensolaris side of the unix universe.
2. Obviously GNU make has advantages. I don´t have anything against GNU make. I just hate this Linux centric view. But from my perspective it would be more feasible to extend the standards (for example SUSv5 ;) ) to keep programs more portable between all Unixes and derivates. Free Software should be operating system agnostic.
3. I have to correct you: HPUX and OSF/1 is mainly on life life-support because of HP ill-fated decisions with PA-RISC and Alpha in favour of Itanic. AIX isn´t a toy for testing ... in the real world there are many systems running those operating sytems like Solaris and AIX. You just have too look at the market data: Sun and IBM still sell systems worth billions of $.
4. Yes gmake is in Solaris ... because of the dependence of many build procceses. But i´m still thinking it would be better to define unixwide standards that include GNU make. At the moment the behaviour is similar to Microsoft. We have our LSB .. that´s a standard ... the bad thing ... it´s a extended version of POSIX, SUS and so on. I think people should ask, why there is the need for a extended own standard instead of extending the existing standards.