5 ms·
It will always be in flux because it reflects what Illumos doesn't have: A userbase as diverse and large as Linux, of which a large proportion have competing ne
by vidarh 10y ago
It will always be in flux because it reflects what Illumos doesn't have: A userbase as diverse and large as Linux, of which a large proportion have competing needs and wishes and the ability to change it at will. This is not just about license either, but about the availability of people who understand the kernel.
I'm sure we could have something cleaner with a single, coherent team. But we also would have something that'd be useful to far fewer people.
Linux wins not by being best at everything. It has plenty of ugly warts. It wins by being accessible ranging from e.g. my ability to just take a job 20 years ago to port it to a custom x86 board with no bios or hard drive, because everything I needed was easily available, to the ability to hire any of a "an army" of past or current kernel developers to help solve my problems or do my custom development, to the ability for people to just write "yet another filesystem" and have actual real people try to use it and give feedback and contribute code.
The most important part of the success and value of Linux is that community. Without the community, it'd have little to offer over any number of other kernels that are better in some areas, worse in others.
But with it, it stands head and shoulder above all kinds of technically very impressive solutions because I can do things with and to Linux that I can't do, or can't do cheaply enough or in short enough time, with alternatives (and yes, that can be because of lack of knowledge of alternatives, but that too is part of the community/network effect).
Don't underestimate the importance of people.
> The team which designed ZFS was only five people, not an army.
And that's great. But the whole ZFS saga is also an illustration of how licensing early on can hamper adoption (KDE vs Gnome is another good illustration of how important license is; and how lasting the effect can be even after the licensing issues are sorted)
- Annatar 10y agoto the ability to hire any of a "an army" of past or current kernel developers to help solve my problems or do my custom development Aha, you mean like redhat and IBM did, where there are now "kernel developers" who can't find their way out of a wet paper bag, and spend more time arguing with paying customers back-and-forth in redhat's bug system, because they don't have a clue where the problem is? When you have some spare time, please do peruse https://bugzilla.redhat.com/index.cgi https://bugzilla.redhat.com/index.cgi, in order to have a look at what your presumption looks like in the real world... to the ability for people to just write "yet another filesystem" ...Because we need more beta filesystems instead of not having to worry about data integrity, right? And because it's just too much fun to be solving the same problem over and over and over again, but never quite get it right? So that for example, on Linux, we can have things like these: /var/log/messages.1:2267:(redacted) kernel: VxVM vxio V-5-0-1266 Subdisk disk_42f7-01 block 108279824: Uncorrectable write error /var/log/messages.1:2270:(redacted) kernel: lost page write due to I/O error on VxVM14000 /var/log/messages.1:2411:(redacted) kernel: VxVM vxio V-5-0-1266 Subdisk disk_42f8-01 block 108003336: Uncorrectable write error ...which ext3, which was on this Veritas disk group, wasn't able to recover, let alone detect. In the 21st century. Because community. I last saw a problem like this on Solaris ten years ago, since it has been a solved problem since 2006 there. Bryan is correct, I do have clean water, and even modern medical care facilities! The most important part of the success and value of Linux is that community. Without the community, it'd have little to offer over any number of other kernels that are better in some areas, worse in others. The two of us (both with several decades of UNIX system administration experience under our belt) just wasted one hour trying to get a simple NFS share to work on RHEL 6.5, and it still doesn't work, with mount(2) returning "incorrect mount option" without saying which; and that was with us carefully following both redhat's official documentation and many examples on the InterNet. Because, you know, man. Like, Linux! And stuff. I have zero interest in how much of a community Linux has (99.99% of them are former Microsoft(R) Windows(R) users, with the corresponding mentality to match). When I use a computer, I use it to get work done. All I wanted to do in the aforementioned NFS fiasco is to test my code, so I could get work done. On Solaris / illumos, all I do is zfs set sharenfs=on pool/filesystem and then I access that on any client, without even worrying about mounting it, like so: ls -l /net/nfs_server/filesystem without caring if it's NFS 2, NFS 3, or NFS 4 (like I have to on Linux, whose implementation of NFS is so dumb that it actually offloads that on to the system administrator to worry about)[1][2]. I could have had my tests long done and the code deployed by now. I could have had work done if it weren't for that same community not having a freaking clue how to make things JustWork(SM), and if it weren't for the "because, like, you know, man. Linux!" [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/s2-nfs-methodology-portmap.html https://access.redhat.com/documentation/en-US/Red_Hat_Enterp... [2] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-nfs.html#s2-nfs-how-daemons https://access.redhat.com/documentation/en-US/Red_Hat_Enterp...
- Nursie 10y agoYou exhibit a weird mixture of snobbery and incompetence. How odd.
- Annatar 10y agoAh, my apologies for that: I did not realize that shoddy NFS software is due to my incompetence. I also apologize that I wasn't able to get something which kind-of worked in RHEL 5 to work in RHEL 6.5 because things which are completely unnecessary on UNIX (like worrying about separate portmapper service) and which were in userland are now suddenly in the kernel. But only for NFS 4. Because the documentation is actually unclear on whether that's the case for NFS 2 and 3. And because the NFS protocol specifies that client and the server should auto-negotiate which version they will use. Because of course the community can't figure out where what should be, so flux. Again. I guess it's really snobby of me to except things which work on UNIX according to specification to behave the same way on Linux. Because Linux is cool. And it's great. And it has the biggest, bestest community. And because I don't appreciate just how great that is, instead being focused on getting work done with computers. Now let's rehash inter-process communication again. Because it's fun rehashing things which work in other operating systems, over and over and over in Linux. Because Linux is cool like that.
- cyphar 10y agoI've decided to stop interacting with Annatar, it's not worth the rage. Especially when he starts misrepresenting GNU/Linux technology that you are deeply into the development of (runC and containers in my case).
- Annatar 10y agoPart of engineering a good solution is being able to recognize when you are in knee deep, and that it's not the best solution, and ditch it. That's what turns a good engineer into a great one, because then she or he turns around and builds the solution. You might not believe the grandpa here, but you're in knee deep, if not deeper. On a personal note, I'm happy that you've stopped interacting with me. Good luck.
- Annatar 10y agoDon't underestimate the importance of people. This warrants a reply of its own, since it is the core idea of my essays: it is the very difference between a stable, working, reliable product and Linux: the people. The right people. Competent people. People with the neccessary education, experience, and insight. If if ever need heart surgery, I guarantee you that I won't go to the local shaman, no matter how happy he will be to perform the operation voluntarily and for free. Same goes for the local exorcist. If I ever need one, I'll get my surgery done by a specialist in cardiology, because they have been formally educated, formally trained, and have the requisite experience to operate on a human heart. And in the case of illumos / SmartOS, they will even do it gratis, like "medical doctors without borders" organization does. Right people for the job. For some reason, people here and at large believe that when it comes to inter-process communication, NFS, or writing operating system kernels anyone can do it. Why exactly people believe that computer science is different from surgery, I haven't discovered yet, but based on empirical evidence of Linux and other crappy software, I have a hypothesis, and since the sample size is large, I might have a theory soon...
- vidarh 10y agoBut 99% of what we do are not that of heart surgery. Much of it is playing. Much of it is experimenting. Much of the actual work needs flexibility, familiarity and community more than it needs technical excellence. Which is why I wrote what I did. Your reply manages to turn it entirely on its head. People believe computer science is different from surgery because it is: Nobody dies when my half-assed experiments with OpenGL crashes. Nobody dies if my laptop crashes. There are certainly niches where it is life and death. Let others take care of that - I don't want anything to do with it.
- Annatar 10y agoBut 99% of what we do are not that of heart surgery. Much of it is playing. Much of it is experimenting. And it shows. However, just because you can get something to work, in some way, does not suddenly make you (or anyone else) a professional. Case in point: http://meta.serverfault.com/questions/6229/frustration-when-the-op-doesnt-get-it http://meta.serverfault.com/questions/6229/frustration-when-... ...Nor does it make your playful experiment fit for production where people like me are trying to get work done. "I got something to work. Because Linux! Because community! Um... I think I'll go get a job as a computer professional now. What could possibly go wrong? Linux is so awesome!" People believe computer science is different from surgery because it is: Nobody dies when my half-assed experiments with OpenGL crashes. Nobody dies if my laptop crashes. An operating system's kernel is an extremely complex, special piece of software. A bug in such software can cause many people to die, which is why someday you might see disclaimers about running a nuclear facility and fitness of purpose. (Interprocess communication, the original topic, is part of an operating system's kernel.) Writing and diagnosing such software requires very deep insights, which very few have, even among computer professionals. Additionally, it absolutely and without fail requires formal education in the problem domain, it requires experience, and it requires apprenticeship, and I'm writing about physical one on one mentorship. It's not something one can pick up "from the community", never has been, and never will be, and if anybody tells you any different, they're either dangerously ignorant, or lying to you for the purpose of their own agenda. Experimenting is all good and well, but when the entire armies of you start deploying your experiments in production and it becomes a trend and then the rest of us are, in fact, forced to take on such jobs because there aren't better ones, then it becomes a systemic problem. Not to mention that armies of you are currently in the process of artificially driving salaries down and it will be years before the market self-corrects, so make that a double whammy. Now, me, I don't so much mind that cheap Linux labor is artificially driving salaries down, since cream always rises to the top, as they say, but I do so very much mind being forced by contract to work with things like ext3, which is based on concepts from the past century and which have since been long abandoned elsewhere, or that my really cool super slick database becomes unstable because of your experiment ticking underneath it (and before you ask, if it were up to me, I'd never put my database on your experiment). I mind even more when your (plural) experiements end up causing a priority 1 incident in the wee hours in the morning, when I'm busy getting my beauty sleep. In my case, you see, it's "because client contract!" Slightly different slant on things than in your case. Welcome to the industry.