4 ms·
The SMF service that runs the scripts should really have been a first class feature of IPS, but whatever, it's there. I don't even remember how many userlands
by cryptonector 9y ago
The SMF service that runs the scripts should really have been a first class feature of IPS, but whatever, it's there.
I don't even remember how many userlands had to be supported by SVR4 packaging at its peak, but it was a lot, and it was difficult to test. That some of those were removed eventually hardly matters: the problem remains, only slightly reduced in magnitude.
Moreover, I want less package scripting. So many Linux packages want to do stupid things like... interact with me when Ubuntu/whatever is just updating the system. It's never appropriate for, e.g., a PostgreSQL package to create a postgres account and configure a postgres service running as that account -- this is not how I want to run postgres, and if you stop this madness then suddenly a postgres pkg is just code and no pkg scripts. If doing stupid things in pkg install scripts is what you call empathy, then I want none of it.
And by the way, IPS had nothing to do with Sun's failure. That can be chalked to a long line of terrible executive business decisions, such as:
- suspending/killing x86 Solaris support in 2002
- killing SunPS (especially considering how much money IBM made with theirs)
- acquiring Cobalt and then promptly killing it
- buying MySQL
- not seeing the writing on the wall for Java ME when iOS came out
- and much more
Oracle is not doing well either. They killed OpenSolaris, which was Sun's way to rebuild mind-share. Oracle is built on mind-share (and subsequent vendor lock-in) but they don't even know it. They gave the impression that they don't care about Solaris x86 (oops). And much more.
- Annatar 9y agoIt's never appropriate for, e.g., a PostgreSQL package to create a postgres account and configure a postgres service running as that account -- this is not how I want to run postgres, That is exactly how I want and do configuration management! The main PostgreSQL package brings on the software and the SMF method. It depends on the postgres-user package which creates the technical user account and group. That's exactly what I want, because I plug that into JumpStart and I can churn out database servers all day long! The postgres-application-db configuration overlay package depends on the postgres-user and postgres packages, starts the database via SMF, and then runs CREATE DATABASE in the postinstall. That's exactly what I want! It works a treat for Oracle databases, it works for anything. I can churn ready to run database servers all day long. I love it. That's exactly how it should work, infrastructure with no human interaction whatsoever: plug in the cable, scan the chassis serial barcode and call it a day. Sun had many problems, but IPS was the final nail in the coffin, as a customer, and as a professional whose bread depended on that ecosystem, and who is now forced to work with substandard, shoddy Linux, I feel I have a much better insight and far more right to decide what has been done wrong at Sun Microsystems. That's for us as customers to say, not for anyone else. And ultimately customers voted with their wallets. I know I sure did, I ran Solaris 10 on generic intel 19" rack servers (and I still do) because it is a far better value for the money. Overpriced hardware and unwillingness to listen to people like me, who were your core customers was like turbo acceleration of the company's demise. And if you lose your core customers, you lost your business. You lost the purpose of your business' existence. Proof is in the pudding, Sun is no more, and as usual, I'm right about the wrong thing. If I'm paying you, you don't argue, you do as I say, or you have no business. Now there is no business and competition rules supreme. It's a terrible business decision to argue with one's customers, because they are the ones who decide what they will give you money for. IPS is not a thing I would ever give Sun or any other company which uses it money for. IRIX's inst(1M), I'd give tons of money in a heartbeat if I knew how; but IPS - never! IPS is the single reason why I don't run operating systems which sport it, like OmniOS.
- cryptonector 9y agoAny such configuration should be done separately. I could stand it being done in a pkg I would never install and which can only be depended on by other pkgs of this type (i.e., which configure but don't include artifacts except by depending on the pkgs that provide them). It is beyond awful that what should be an unattended operation (install, upgrade an OS) isn't. It's completely unacceptable, and utterly intolerable. Yes, I'm aware of "answer" files. That was SVR4's compromise: you'd put all interaction into one kind of script that can be run separately from the actual pkg installation and which produces "answers", and then you can furnish those answers at actual pkg installation time. But in practice most developers were not really aware of all of this. The cognitive load of SVR4 packaging was too high. Interaction and package scripting really complicates packaging. Please stop.
- Annatar 9y agoNone of my packages have ever been interactive, and they never needed any answer(4) files. I agree with you that packages should never be interactive, because at that point, automation is lost and one of the core capabilities of packaging defeated. Such things are usually done by inexperienced personnel who view packaging as a burden rather than as a strategic advantage and an extremely capable automation mechanism. I am none of those people.
- cryptonector 9y agoWithout interaction, what should the DATABASE be named???
- Annatar 9y agoThat’s a per-application package, and the name is defined in the pkginfo(4) file. And contrary to your claim about SVR4 packaging being too cognitively difficult to grasp, it is the simplest of all packaging subsystems to learn. IPS is far worse and the tooling to make an IPS package is truly lacking, especially when it comes to documentation, and then especially when it comes to configuration management with packages.
- X-Istence 9y ago> It's never appropriate for, e.g., a PostgreSQL package to create a postgres account and configure a postgres service running as that account -- this is not how I want to run postgres I don't mind it creating a postgres account, but what I do mind is the package automatically enabling the service, and starting the service. Even worse, on Linux, most packages will be helpful, for example upgrading the MongoDB package on CentOS? It'll helpfully restart the service for you. Nevermind that you've just scripted this and it's being run on all of the servers all at once so instead of doing a nice easy rolling upgrade WHEN you are finally ready, it's done at the same time. I hate this behaviour. Let me worry about the lifetime of processes, don't auto enable them, don't auto configure them, let me worry about making sure systemd knows it is time to start/stop them. FreeBSD let's me upgrade packages all day long, and until I restart the service, nothing happens. That way I can upgrade the packages, make sure everything looks good, then restart the service.
- cryptonector 9y agoYes, I agree, packages should never be so "useful".
- Annatar 9y agoEven worse, on Linux, most packages will be helpful, for example upgrading the MongoDB package on CentOS? It'll helpfully restart the service for you. Nevermind that you've just scripted this and it's being run on all of the servers all at once so instead of doing a nice easy rolling upgrade WHEN you are finally ready, it's done at the same time. That’s exactly how it must work for total automation where humans are out of the picture. What you lack is a push, rather than a pull methodology, with a software deployment server and a capability maturity model level 3 (or higher) change management process around it. Then it works flawlessly, and I’m writing from experience of several decades of modelling and implementing such things on a very large scale (tens or even hundreds of thousands of servers). That’s my specialty as a technical architect. https://en.m.wikipedia.org/wiki/Capability_Maturity_Model https://en.m.wikipedia.org/wiki/Capability_Maturity_Model
- X-Istence 9y ago