Saturday, April 25, 2015

Who’s behind Linux now, and should you be afraid?

Most Linux kernel code isn’t developed by who you might think. Here’s a closer look at why this matters.

If you think that Linux is still the "rebel code”—the antiestablishment, software-just-wants-to-be-free operating system developed by independent programmers working on their own time — then it's time to think again.

The Linux kernel is the lowest level of software running on a Linux system, charged with managing the hardware, running user programs, and maintaining security and integrity of the whole set up. What many people don’t realize is that development is now mainly carried out by a small group of paid developers.

A large proportion of these developers are working for "the man” -- large establishment companies in the software and hardware industries, for names like IBM, Intel, Texas Instruments and Cisco. That's according to a Linux Foundation report on Linux kernel development published in February. I
Nobody codes for free

In fact, it turns out that more than 80 percent of all Linux kernel development is "demonstrably done by developers who are being paid for their work," by these big (and sometimes smaller) companies, according to the report.

One organization that isn’t featured in the report's list of companies paying its staff to develop the Linux kernel is Microsoft, a company whose proprietary software model once made it enemy No. 1 for many in the open source movement, but which now claims to embrace free code.
INSIDER: SUSE Linux 12 challenges Red Hat

But one that is featured in the report is Huawei, the Chinese technology company founded by a former Chinese People's Liberation Army officer. That’s a possible cause for concern: The company denies having links to the Chinese government, but some governments, including those in the U.S., U.K. and Australia, have banned the purchasing of certain Huawei hardware products amid worries that they may contain software back doors that could be used for spying.

About 1 percent of all the changes to the Linux kernel are currently written by developers paid by Huawei, according to the report.
Keeping open source open

Amanda McPherson, vice president of developer forums at the Linux Foundation, points out that the whole point of open source software is to remain open to review and close scrutiny, in contrast to proprietary software that runs in many hardware products sold by Huawei and other companies.

“No one can submit a patch on their own," she says. "Security is always a concern, but every patch goes through maintainers, and there is lots of code review. That is a much more secure mechanism than a closed system with no source code availability."

That may be true, but the severe Heartbleed and Shellshock vulnerabilities recently discovered in the open source Bash and OpenSSL software demonstrate that insecure code can be introduced into open source products—unintentionally or perhaps deliberately —and remain undetected for years.

The fact that the vast majority of Linux kernel developers are paid to do so by their employers is a big change from the Linux that Linus Torvalds, then a student at the University of Helsinki, first announced on comp.os.minix in August 1991. At the time he said, "I'm doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones."

In fact, the volume of contributions from students and other volunteers to the Linux kernel has been in steady decline for some time, according to the report: from 14.6 percent of contributions in 2012 to just 11.8 percent now.

"I think that when we started collecting these figures, it was a surprise that so many contributors are paid, and in fact it still is a surprise to the general public. But Linux is a highly commercial enterprise," McPherson says. "Many people thought it was volunteers working in their basements. I think it is good that companies are contributing, even though they are contributing for selfish reasons. They are supporting Linux, but they can't own it or dictate how it is developed."

She points out that if Linux were an application, then paid-for developers would be adding features that met the needs of the corporations that paid them. But the kernel is much more low-level code, and the sorts of contributions that paid developers make often involve enabling hardware connections by providing kernel drivers.
Losing its amateur status

An interesting question, then, is why Linux kernel development has changed so much from the "just a hobby" approach originally envisioned by Torvalds back in 1991, to professional developers working on company time.

One obvious possible answer is that large enterprises, especially hardware manufacturers like Intel or Texas Instruments, have an interest in ensuring that there are Linux drivers for their hardware, and that the kernel can otherwise support their products. Over time, as Linux has become increasingly popular, this type of support has become increasingly important.

But McPherson believes a simpler reason is more plausible. "Kernel developers are in short supply, so anybody who demonstrates an ability to get code into the mainline tends not to have trouble finding job offers. Indeed, the bigger problem can be fending those offers off," the report says.

On a more positive note, the report does highlight some of the achievements of what McPherson describes as "the most collaborative software project in history."

Thanks to contributions from 11,695 developers working for over 1,200 companies, the kernel has been updated with major releases every 8 to 12 weeks. Each release includes more than 10,000 changes, which means that changes are accepted into the kernel at the staggering rate of more than seven every hour.


Best Microsoft MCTS Certification, Microsoft MCITP Training at certkingdom.com

Thursday, April 16, 2015

The day the first iPad arrived

Five years ago Friday, April 3, 2010, the first Apple iPads were delivered to the public.

April 3, 2010
Tablets had always flopped so there was no shortage of naysayers pooh-poohing Apple’s new iPad when the first model was delivered to homes and made available in stores on April 3, 2010. While sales growth has slowed recently, the naysayers could not possibly have been more wrong. Here are some images from the iPad’s debut day.

Sign of things to come
A fan outside the Apple Store in New York City.

Lining up
In what has now become a ritualistic sight for Apple product launches, customers line up for the first iPad outside of a store in San Francisco.

Lining up the goods
A store employee prepares the product for sale in San Francisco.

Initial reaction
Andreas Schobel reacts after being among the first to purchase an iPad at the San Francisco store.

A Halloween costume to come
Lyle Haney walks along the waiting line wearing what would become a common Halloween costume.

300,000 sold that day
A worker rings up a sale in the New York store. Apple reported that it sold 300,000 iPads on that first day.

Mr. iFixIt among buyers
Luke Soules, co-founder of iFixit, was among the first to walk out of the Richmond, Va., store with a pre-ordered iPad. Here is the tear-down iFixit did on the machine.

Employees cheer
Store workers cheer as hundreds of shoppers enter the Chicago outlet.

'Hey Steve, here’s your iPad, buddy’
Steve would appear to be Steve Mays. The UPS guy who brought him his iPad is not identified, but you can hear him announce the delivery here.

You could Google it
And this is what the Google search results page looked like on Day One of the iPad.

It was front-page news
Including in the Honolulu Advertiser, for example, which warned readers to “expect a crowd.”

At the bar
By evening, many an iPad owner was enjoying a new way to end the day with a newspaper and a nig



Best Microsoft MCTS Certification, Microsoft MCITP Training at certkingdom.com

Wednesday, April 1, 2015

CRISC Certified in Risk and Information Systems Control

QUESTION 1
Which of the following is the MOST important reason to maintain key risk indicators (KRIs)?

A. In order to avoid risk
B. Complex metrics require fine-tuning
C. Risk reports need to be timely
D. Threats and vulnerabilities change over time

Answer: D

Explanation:
Threats and vulnerabilities change over time and KRI maintenance ensures that KRIs continue to
effectively capture these changes.
The risk environment is highly dynamic as the enterprise's internal and external environments are
constantly changing. Therefore, the set of KRIs needs to be changed over time, so that they can
capture the changes in threat and vulnerability.

Answer: B is incorrect. While most key risk indicator (KRI) metrics need to be optimized in respect
to their sensitivity, the most important objective of KRI maintenance is to ensure that KRIs
continue to effectively capture the changes in threats and vulnerabilities over time. Hence the most
important reason is that because of change of threat and vulnerability overtime.

Answer: C is incorrect. Risk reporting timeliness is a business requirement, but is not a reason for
KRI maintenance.

Answer: A is incorrect. Risk avoidance is one possible risk response. Risk responses are based
on KRI reporting, but is not the reason for maintenance of KRIs.


QUESTION 2
You are the project manager of a HGT project that has recently finished the final compilation
process. The project customer has signed off on the project completion and you have to do few
administrative closure activities. In the project, there were several large risks that could have
wrecked the project but you and your project team found some new methods to resolve the risks
without affecting the project costs or project completion date. What should you do with the risk
responses that you have identified during the project's monitoring and controlling process?

A. Include the responses in the project management plan.
B. Include the risk responses in the risk management plan.
C. Include the risk responses in the organization's lessons learned database.
D. Nothing. The risk responses are included in the project's risk register already.

Answer: C

Explanation:
The risk responses that do not exist up till then, should be included in the organization's lessons
learned database so other project managers can use these responses in their project if relevant.

Answer: D is incorrect. If the new responses that were identified is only included in the project's
risk register then it may not be shared with project managers working on some other project.

Answer: A is incorrect. The responses are not in the project management plan, but in the risk
response plan during the project and they'll be entered into the organization's lessons learned
database.

Answer: B is incorrect. The risk responses are included in the risk response plan, but after
completing the project, they should be entered into the organization's lessons learned database.


QUESTION 3
You are the project manager of GHT project. You have identified a risk event on your project that
could save $100,000 in project costs if it occurs. Which of the following statements BEST
describes this risk event?

A. This risk event should be mitigated to take advantage of the savings.
B. This is a risk event that should be accepted because the rewards outweigh the threat to the
project.
C. This risk event should be avoided to take full advantage of the potential savings.
D. This risk event is an opportunity to the project and should be exploited.

Answer: D

Explanation:
This risk event has the potential to save money on project costs, so it is an opportunity, and the
appropriate strategy to use in this case is the exploit strategy. The exploit response is one of the
strategies to negate risks or threats appear in a project. This strategy may be selected for risks
with positive impacts where the organization wishes to ensure that the opportunity is realized.
Exploiting a risk event provides opportunities for positive impact on a project. Assigning more
talented resources to the project to reduce the time to completion is an example of exploit
response.

Answer: B is incorrect. To accept risk means that no action is taken relative to a particular risk;
loss is accepted if it occurs. But as this risk event bring an opportunity, it should me exploited and
not accepted.

Answer: A and C are incorrect. Mitigation and avoidance risk response is used in case of negative
risk events, and not in positive risk events. Here in this scenario, as it is stated that the event could
save $100,000, hence it is a positive risk event. Therefore should not be mitigated or avoided.


QUESTION 4
You are the project manager of a large construction project. This project will last for 18 months
and will cost $750,000 to complete. You are working with your project team, experts, and
stakeholders to identify risks within the project before the project work begins. Management wants
to know why you have scheduled so many risk identification meetings throughout the project
rather than just initially during the project planning. What is the best reason for the duplicate risk
identification sessions?

A. The iterative meetings allow all stakeholders to participate in the risk identification processes
throughout the project phases.
B. The iterative meetings allow the project manager to discuss the risk events which have passed
the project and which did not happen.
C. The iterative meetings allow the project manager and the risk identification participants to
identify newly discovered risk events throughout the project.
D. The iterative meetings allow the project manager to communicate pending risks events during
project execution.

Answer: C

Explanation:
Risk identification is an iterative process because new risks may evolve or become known as the
project progresses through its life cycle.

Answer: D is incorrect. The primary reason for iterations of risk identification is to identify new risk
events.

Answer: B is incorrect. Risk identification focuses on discovering new risk events, not the events
which did not happen.

Answer: A is incorrect. Stakeholders are encouraged to participate in the risk identification
process, but this is not the best choice for the


QUESTION 5
You are the risk official in Bluewell Inc. You are supposed to prioritize several risks. A risk has a
rating for occurrence, severity, and detection as 4, 5, and 6, respectively. What Risk Priority
Number (RPN) you would give to it?

A. 120
B. 100
C. 15
D. 30

Answer: A

Explanation:
Steps involving in calculating risk priority number are as follows:
Identify potential failure effects
Identify potential causes
Establish links between each identified potential cause
Identify potential failure modes
Assess severity, occurrence and detection
Perform score assessments by using a scale of 1 -10 (low to high rating) to score these
assessments.
Compute the RPN for a particular failure mode as Severity multiplied by occurrence and detection.
RPN = Severity * Occurrence * Detection
Hence,
RPN = 4 * 5 * 6
= 120

Answer: C, D, and B are incorrect. These are not RPN for given values of severity, occurrence,
and detection.