Some of them are templates that systemd uses to creat temporary conffig files at boot time!
I'm familiar with those. They're much better than what we used to have. In the old system, there was either a mountain of repeated code with minor differences, or there were templates that were modified with sed to create individual configuration files.
Systemd is a tool, not just a project. Systemd as a tool tries to do many different things
You are misinformed. Systemd is a project which provides a collection of tools. One of them handles daemon and system startup. One of them handles logging. One of them handles device node creation. One of them handles firewall rule management. etc.
Can we have a cut-down, simplified version of systemd for servers and doesn't try to replace several layers of server side system functionality such as logging?
We already have that. Journald is optional. You can turn it off.
I also like how he calls systemd non-monolithic, of course, without giving any reason for why that is.
And that seems to be one of the big differences between people who like systemd and people who don't.
People who actually took the time to look at systemd more often like the design, and understand that the one project consists of many small tools.
Then there's a community of people who rely entirely on hearsay. They don't like systemd, but almost all of the things they don't like about it aren't true. In this case, believing that PID 1 is a process that does daemon handling, and logging, and firewall rule handling, and DNS, and device node handling, and...
Those things are not handled by the same process. It's non-monolithic. It's small tools doing individual, well defined jobs.
Because it contradicts the Unix philosophy of having a lot of little utilities that each do one thing
systemd is actually a lot of little utilities that each do one thing. If you don't know that, you're probably getting your information from biased sources.
Although the signal to noise ratio on here sometimes approaches zero, there is the occasional informed opinion
Firefox is also a smaller download, a smaller install, starts faster, runs JavaScript faster, allows plugins on the mobile version, and allows users to run their own sync server, compared with Chrome.
Mozilla's work is really shining these days. Firefox is a better browser by every metric I can think of.
...which is basically the only valid criticism in this entire thread. Google made one phone whose support ended too soon, mostly because the SoC vendor essentially went tits up.
Which is an excellent example for why Free Software matters at all levels of the stack, including firmware. Too many people fail to take that seriously.
Google's support policy is no such thing, but Google only sets the policy for the hardware that they sell.
I seriously cannot understand how naive this conversation is. If you buy a product from Company X, you are exchanging money for goods and services from Company X. It is their responsibility to provide you with goods and services.
It is not Google's responsibility to do the development, testing, and support for hardware from Company X for which they were not paid.
Google supports their phones for a very reasonable amount of time. If you want support, I suggest you buy one.
If my phone is running Android OS, then I should be able to get updates straight from Google.
If that's what you want, then BUY A PHONE FROM GOOGLE.
Otherwise, you're expecting Google to provide the development and support for hardware they didn't sell. Your money goes to company X, but you expect Google to do the work? That's not how any economic system works. You made an exchange of money for goods with company X. Warranty, support, etc is their responsibility. They're the one that you're paying.
I'm an IT guy. I know that transaction takes milliseconds to process.
And like a typical IT guy, what you "know" is beyond question. No way you could possibly be wrong.
If, someday, you work with enterprise systems, you might come to realize that very large systems are often riddled with inefficiencies. When multiple parties are involved, or legal compliance, those inefficiencies can become powerfully entrenched.
Take a look at some of the high rated comments on this article for explanations as to why and how banking is not as efficient as you imagine.
As a newly unemployed individual contributor, I vote yes
I just want to point out the the post you replied to was voicing a "no" vote for overtime exemptions, which is the same position that you are advocating.
A lot of us benefit from Free Software. Android is primarily developed by Google, so it has a steady source of funding. GNU/Linux has a large community of volunteers, but is honestly developed primarily by businesses that get revenue from server support contracts (Red Hat, Intel, SuSE, IBM, Google, to name a few).
Firefox is, by a host of measures, the best browser available. If I'm reading arewefastyet properly, it's the browser with the fastest Javascript engine now. The last time I checked, it's the smallest download. It uses the least RAM. It starts fastest. It supports plugins on all platforms, including mobile.
The browser is key to practically every Internet service, and they all really should be contributing to the development of the one browser that's fully Free Software. Sadly, unlike Android and GNU/Linux, Firefox is essentially ad-supported. It's a bad situation for us, the users.
you have to reboot the server to get the changes to take effect.
No, you don't. glibc still uses/etc/resolv.conf. If you modify the file, changes will take effect immediately, unless a specific application caches the DNS configuration. Firefox, for instance, does (IIRC). That has nothing to do with resolvconf, though.
Just type "ifdown eth0 && ifup eth0" in a shell (as root). When you hit enter, the entire command is sent to the server at once, and the 2nd one is executed if the first one succeeds. The first command will kill your ssh link if it succeeds, but the second one still executes even after you've been disconnected, bringing the link back up.
That's actually not correct. If the ssh session is terminated, the shell will cease executing the command line it has. To be specific, it will receive SIGPIPE (IIRC) and exit.
You should use screen, or tmux, or nohup for this sort of thing.
Chrome still has the technology edge in several cases
Some, maybe. It's getting harder to name them. Firefox is a smaller download, uses less RAM, starts faster, and (if arewefastyet is to be believed) has a faster JavaScript engine now. And the mobile version supports plugins. And I can run my own sync server if I want to.
The original advisory notes that "Since Drupal uses PDO, multi-queries are allowed." I can find documentation that confirms that's true of the MySQL PDO adapter. Is that also true for PDO for other databases, or is this vulnerability specific to MySQL?
Having it on WiFi whenever possible. In good implementations on modern phones it uses less power than the cell network.
Interesting note: that's not always the case. If you're on a network with a lot of broadcast traffic, WiFi will keep the phone from entering deep sleep, and your battery life will be terrible. It took me quite a while to figure out that my battery life's turn for the worse coincided with starting a new job, where the WiFi network is really big.
Slashdot Mirror
Are you upset that I said not the same process instead of not the same binary?
Those things are handled by separate programs, entirely. Systemd is small tools, doing individual, well defined jobs.
Are you happier now?
Some of them are templates that systemd uses to creat temporary conffig files at boot time!
I'm familiar with those. They're much better than what we used to have. In the old system, there was either a mountain of repeated code with minor differences, or there were templates that were modified with sed to create individual configuration files.
Maintaining the templates is far easier.
Systemd is a tool, not just a project. Systemd as a tool tries to do many different things
You are misinformed. Systemd is a project which provides a collection of tools. One of them handles daemon and system startup. One of them handles logging. One of them handles device node creation. One of them handles firewall rule management. etc.
Systemd is quite UNIX-y.
Can we have a cut-down, simplified version of systemd for servers and doesn't try to replace several layers of server side system functionality such as logging?
We already have that. Journald is optional. You can turn it off.
I also like how he calls systemd non-monolithic, of course, without giving any reason for why that is.
And that seems to be one of the big differences between people who like systemd and people who don't.
People who actually took the time to look at systemd more often like the design, and understand that the one project consists of many small tools.
Then there's a community of people who rely entirely on hearsay. They don't like systemd, but almost all of the things they don't like about it aren't true. In this case, believing that PID 1 is a process that does daemon handling, and logging, and firewall rule handling, and DNS, and device node handling, and...
Those things are not handled by the same process. It's non-monolithic. It's small tools doing individual, well defined jobs.
Because it contradicts the Unix philosophy of having a lot of little utilities that each do one thing
systemd is actually a lot of little utilities that each do one thing. If you don't know that, you're probably getting your information from biased sources.
Although the signal to noise ratio on here sometimes approaches zero, there is the occasional informed opinion
You're welcome.
Firefox is also a smaller download, a smaller install, starts faster, runs JavaScript faster, allows plugins on the mobile version, and allows users to run their own sync server, compared with Chrome.
Mozilla's work is really shining these days. Firefox is a better browser by every metric I can think of.
...which is basically the only valid criticism in this entire thread. Google made one phone whose support ended too soon, mostly because the SoC vendor essentially went tits up.
Which is an excellent example for why Free Software matters at all levels of the stack, including firmware. Too many people fail to take that seriously.
Google's support policy is no such thing, but Google only sets the policy for the hardware that they sell.
I seriously cannot understand how naive this conversation is. If you buy a product from Company X, you are exchanging money for goods and services from Company X. It is their responsibility to provide you with goods and services.
It is not Google's responsibility to do the development, testing, and support for hardware from Company X for which they were not paid.
Google supports their phones for a very reasonable amount of time. If you want support, I suggest you buy one.
If my phone is running Android OS, then I should be able to get updates straight from Google.
If that's what you want, then BUY A PHONE FROM GOOGLE.
Otherwise, you're expecting Google to provide the development and support for hardware they didn't sell. Your money goes to company X, but you expect Google to do the work? That's not how any economic system works. You made an exchange of money for goods with company X. Warranty, support, etc is their responsibility. They're the one that you're paying.
I was thinking the same thing. 3DES isn't deprecated because it's insecure, it's deprecated because it's SLOW. Its security is fine.
I'm an IT guy. I know that transaction takes milliseconds to process.
And like a typical IT guy, what you "know" is beyond question. No way you could possibly be wrong.
If, someday, you work with enterprise systems, you might come to realize that very large systems are often riddled with inefficiencies. When multiple parties are involved, or legal compliance, those inefficiencies can become powerfully entrenched.
Take a look at some of the high rated comments on this article for explanations as to why and how banking is not as efficient as you imagine.
Have you been car shopping lately? Find a car that meets all of your non-electric criteria that still has physical buttons.
Yep. Bought a Honda Insight this year. Unlike the Prius, it has all physical buttons.
Sadly, the Prius dominates that market segment, and the Insight is being discontinued.
Perhaps someone should introduce Julian to Marcus Porcius Cato.
As a newly unemployed individual contributor, I vote yes
I just want to point out the the post you replied to was voicing a "no" vote for overtime exemptions, which is the same position that you are advocating.
Quite the opposite. In the last few years, Firefox has worked harder on reducing memory use and improving performance than anyone, and it shows.
That's true of all browsers. Firefox uses less RAM than any other browser, with an equal number of tabs open, on any platform I've seen numbers for.
A lot of us benefit from Free Software. Android is primarily developed by Google, so it has a steady source of funding. GNU/Linux has a large community of volunteers, but is honestly developed primarily by businesses that get revenue from server support contracts (Red Hat, Intel, SuSE, IBM, Google, to name a few).
Firefox is, by a host of measures, the best browser available. If I'm reading arewefastyet properly, it's the browser with the fastest Javascript engine now. The last time I checked, it's the smallest download. It uses the least RAM. It starts fastest. It supports plugins on all platforms, including mobile.
The browser is key to practically every Internet service, and they all really should be contributing to the development of the one browser that's fully Free Software. Sadly, unlike Android and GNU/Linux, Firefox is essentially ad-supported. It's a bad situation for us, the users.
you have to reboot the server to get the changes to take effect.
No, you don't. glibc still uses /etc/resolv.conf. If you modify the file, changes will take effect immediately, unless a specific application caches the DNS configuration. Firefox, for instance, does (IIRC). That has nothing to do with resolvconf, though.
Just type "ifdown eth0 && ifup eth0" in a shell (as root). When you hit enter, the entire command is sent to the server at once, and the 2nd one is executed if the first one succeeds. The first command will kill your ssh link if it succeeds, but the second one still executes even after you've been disconnected, bringing the link back up.
That's actually not correct. If the ssh session is terminated, the shell will cease executing the command line it has. To be specific, it will receive SIGPIPE (IIRC) and exit.
You should use screen, or tmux, or nohup for this sort of thing.
Back in the good old days. We had a data format that was in essence a memory dump of the system
You mean .doc?
Chrome still has the technology edge in several cases
Some, maybe. It's getting harder to name them. Firefox is a smaller download, uses less RAM, starts faster, and (if arewefastyet is to be believed) has a faster JavaScript engine now. And the mobile version supports plugins. And I can run my own sync server if I want to.
It happens about 40 times a day on you average PC
No, it doesn't. I operate lots of machines with ECC RAM. I've seen ECC correction. Bits flip, but nowhere near that frequently. It's very rare.
The original advisory notes that "Since Drupal uses PDO, multi-queries are allowed." I can find documentation that confirms that's true of the MySQL PDO adapter. Is that also true for PDO for other databases, or is this vulnerability specific to MySQL?
Having it on WiFi whenever possible. In good implementations on modern phones it uses less power than the cell network.
Interesting note: that's not always the case. If you're on a network with a lot of broadcast traffic, WiFi will keep the phone from entering deep sleep, and your battery life will be terrible. It took me quite a while to figure out that my battery life's turn for the worse coincided with starting a new job, where the WiFi network is really big.