Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Obligatory car analogy: Worrying about systemd seems like worrying about what brand of spark plugs are in your new car.
Only a valid analogy if those new spark plugs also want to control your entry system, brakes, transmission and radio too.
Red Hat is about to learn this the hard way.
I hope so. We've put our upgrade from RHEL 6 to version 7 on permanent hold basically because of systemd and all other associated forced-down-your-throat changes they have made. This is no longer a seamless, non-intrusive upgrade unlike every previous major release.
For desktop users, yeah I understand it's probably a non-issue for them. But if you are a sysadmin managing thousands of servers with possibly tens of thousands of VM's on top of that it's a major issue.
I thought the majority of voice circuits in the US were restricted to the callerid they could display? Only certain VoIP services and carrier level interconnects would allow you to set anything you wanted?
I'm currently the senior sysadmin for several thousand Redhat/CentOS servers and everything about systemd is giving me a headache. Myself and every other person on my team dislike it to varying degrees and none of us want to use it. This is now a blocker to us upgrading from RHEL6 to RHE7. There are lots of nice new features in the updated release we want or need to use but we are refusing to upgrade. This isn't a philosophical argument. I've tested it in various scenarios and it's almost not fit for purpose and throws out countless decades of experience in the team.
Frankly I'm shocked that RedHat have steam-rollered this into version 7, they are normally a very conservative distro (a very good thing in an enterprise environment!) Though I guess I shouldn't be that surprised since the lead developer works for them. I'd be looking at other distributions but they all seem to be switching too. I'd say RedHat have lost some business but I'm not sure what options I have to switch to?
However I have noticed a marked increase in the backlash against systemd in the last few months, probably from the fact that now people are having to use it and all these discussions are definitely a good thing, if slightly too late.
What's the problem with that? Linux still has a serious weakness making itself an option for normal Desktop users. It'll never be a Windows replacement in it's current state. So replacing a simple text based boot system that sysadmin have been using for 20 years with a complex & monolithic control system that is amalgamating several tried and tested services into borg-like hive system with binary logging makes perfect sense. Just look at Microsoft with the Windows registry and how well that works.
please note, I may be using some sarcasm in this post.
As someone who has used various BSD's and Linux in large scale environments, and is a fan of both, I've configured servers with multi-10Gb interfaces and handling 100k+ requests a second I honestly can't think of any example of where Linux has been inferior. The often repeated line that FreeBSD has a better networking stack was probably true over 10 years ago with Linux 2.2 and earlier, but since then I'd say that myth is just bullcrap.
Maybe Facebook are talking about some specific IPv6 or cutting edge features like MPTCP they need on their network, but as a general statement it's utterly misleading.
I've always considered elegant code to have a few criteria.
There is no unnecessary complexity in the code.
The code base is "clean" and consistent. That can be the file system layout, filenames, variable names and function naming. Also a non-consistent comment and white space convention is a personal irk of mine.
Where most programmers would write several hundred lines of dense code to solve a particular problem, the elegant coder will write a few simple lines instead as they really understood the problem.
30 Giant Hornets v 30,000 Bees
It's just a shame he could only make 7p/minute from it. What happened to £1/minute premium rate lines?
This isn't a new trick to me since I work for a telco that provides the infrastructure for a lot of these cold callers, I've seen it before.
The premium rate 09 lines you are talking about are separately regulated and abuse is prosecuted. However the guy missed an opportunity here. He should have actually chosen an 070 number which is allocated by Ofcom for use of Personal Numbering Services, these can cost 50p - £1 to call. But since they start 07 most people think it's just another mobile number.
I have to ask what your expectations are and be realistic.
As an employer actively recruiting IT staff at the moment, rare in the current job market I know, and I have a choice between a recent uni-graduate and someone with 15 yrs experience who I can hire for almost the same wages because so many skilled IT staff have been laid off and need to pay their mortgage. For me the choice is obvious, I don't care about the age factor.
However I also interview many many people who think they deserve to get the same remuneration they got from their high-flying finance job and wonder why they are still jobless after two years.
I used to work for GAME many many years ago in their digital division. We had the developers, network infrastructure, industry clout (at the time) and the strategy to create Steam before Steam even existed. We were incredibly motivated to do this, basically it was why we'd all been hired. We all knew digital distribution was the future.
In the end the then board decided "forget the internet, we ship boxes". The entire digital team was disbanded and moved to other departments. Just one of many, many mistakes they made but from my personal perspective a bloody huge one!
Believe it or not, most major software vendors have licenses and policies in place (e.g., Microsoft) to allow sensitive institutions (governments, defense contractors, etc) access to their source code. The primary reason is actually the opposite of what you say. Customers such as the Indian government want to be able to see what's actually in the code before they agree to buy and install it on their own systems and network.
Yes, this explanation is valid and almost certainly the main reason why this happens. But the fact that any institution can then exploit any bugs they do find is hardly something that can be ignored.
Well I write the software that does a lot of these calls so its pretty simple to exclude myself
.. to the soundtrack of Jonny Cash singing "Ring of Fire"