Comment You don't say? (Score 1) 112
Really? In a recession companies cut down on pet projects?
I'm taken aback, really!
Really? In a recession companies cut down on pet projects?
I'm taken aback, really!
Other way 'round it is, if you only pay minimum, you get morons. Don't expect anything other than monkeys if you offer just peanuts!
So only rich people should be allowed to breed? Hey, now it all makes sense. After all, reproduction is the most capitalist of all kinds of things humans can do, the production means are fully in private hands!
If you define "has" as "has within a mile," then you're absolutely correct. If you define it as "has passing the home," then definitely not.
I live on a paved road and I'm several miles (at least three) away from fiber. Literally the only company with fiber into my county is AT&T, and as you likely know, they are bastards of the first degree.
Minimum standard for what? 2014? Per individual? Per family? Per household? Per block? Per neighborhood?
Please try to keep up.
1. Standards change. 10Mbps might be an acceptable minimum today, but it certainly won't be in 2024, let alone 2054.
1. Standards change.
The devil is in the details.
So is the wankery of your comment.
Basically everything is doable at 10Mbps. It's an acceptable minimum standard. We'd all like to see more, but at least they're setting the bar someplace livable.
cgroups existed before systemd.
the cgroups functionnality existed in the kernel but wasn't really used that much before. [...] whereas current
Yes, my argument was that altering the init scripts would have solved most of what systemd solved. Thanks for confirming that.
each script end up fucking things up in its own original and different way.
The scripts are unified by maintainers. I've already made the proposal that you could actually interpret unit files as init scripts, with the right parser which basically stripped out the sections in brackets, dumped the rest of the content of the file into a series of variables by sourcing it, and then running a unified init script. This would work just fine for any daemons which are long-running, without any complex work. All you'd need is a hashbang at the top of the unit file.
proper handling of dependencies at runtime
Already handled by several init systems.
None of which are the original sysvinit.
Congratulations, you just hammered home the point that you don't understand Unix, while simultaneously proving that you don't understand sysvinit. Using fancy scripts with the original sysvinit is still using the original sysvinit. You are witnessing the awesome power of the Unix philosophy. Because sysvinit is small, simple, and completely modular, the scripts could be extended to provide functionality which sysvinit didn't try to claim for itself. Instead of moving more functionality into PID1, the functionality can be implemented at the script level.
Or cron if it's time-based activation. Or udev if it's hardware based activation. Etc.
Why do we need 83 different way to start some code ?!
Wasn't the whole point of Unix philosophy having one piece of software which concentrates into doing one thing and doing it well?
You failed to understand the Unix way. It's not to have one piece of software. That's the systemd way. It's to have many pieces of interoperable software which can be combined to perform complex tasks, and reconfigured to perform other complex tasks. So we have cron and at (which are often merged) and we have udev and inetd. And each of these things does one simple thing. It's not unusual to want to start processes in multiple ways, that is in fact common to all modern operating systems. You can start them from the command line, you can schedule them, you can start them from the GUI. Is that a problem for you?
Before, you'd have the same concept spread into a dozen of different systems, each only doing part of that functionnality.
And you still do. Only now, they're all managed by one process which, if it craters, will not just cause them all to fail, but which will cause a panic. Great idea!
if you don't like it, don't use it.
That's getting harder to do as people depend on it. I may finally have to go back to BSD.
It uses kernel namespaces and capabilities to protect the system; this is on top of SELinux etc.
Well then, I sit corrected on this one point. And finally, we have found something for systemd to do. I propose that we stop using it as init, strip out all the shit better done with a script, and use just that part. Perhaps it can be reworked into a replacement for daemontools. That would make a lot more sense than eating up all these daemons which work fine on their own.
Bull. The only reason anyone pays minimum is because they get away with it. Why the heck should I pay more than minimum wage if I can get what I want for that? Do you honestly think anyone would go "gee, that guy is good, I needn't pay him more 'cause there's nothing he can do, but 'cause I'm so impressed with his great work, here's five bucks more per hour!"?
So socialism doesn't give you a choice, you're a slave or if you refuse, you get paid by the state by wellfare.
Capitalism gives you the choice to be a slave or to starve.
I dunno. Most people would probably prefer socialism. But hey, what do I know about socialism, being in Europe. That's something I should leave to the experts across the big pond who have loads and loads of first hand experience with socialist systems...
That's a great story. And where, say, do you get your customers? Where did you meet them? How did they learn that you're in the market? And that you're worth any dime they pay you?
Valuable experience in how to bullshit customers, invent colorful descriptions of events and places she's never seen or experienced and finding visual proof of those aforementioned stories.
Great resume for a political career, everything you need to convince your people to go to war with some country is right there.
Odd. A good deal of Europe won that war. Well, at least 'til we decided it would be a great idea to copy the idiocy of the US in that matter.
Societies depending on slavery (or any kind of cheap labor) are by definition behind when it comes to invention, industrialization and progress. Simply because R&D is expensive. If it's cheaper to stick to employing humans, there is zero incentive to develop machines.
So it's like today?
BLISS is ignorance.