Brief Introduction to Linux System Software

Do you want to know the truth about Linux system software? Do you want to know the inherent meanings hidden in Linux system software? I am the only one to give you a full explanation of this idea recently, I wrote an article here. If someone has already had such an idea, I will discuss it together. If someone else can see the innocence of this idea at a glance, I will leave it blank.

Linux System Software many enterprises-especially those famous for their products-generally have two product lines under the same product category, indicating both mainstream products and cutting-edge products, of course, it can also represent high-end products and mid-end products, personal products and enterprise products. Of course, this does not rule out that many successful enterprises have only one product line under a product category, but most of them are due to special circumstances of the industry and are not covered in this article.

I can cite many examples to prove this without looking at it. The following list shows many examples:
Microsoft/Windows 9x/Windows NT (past)
Microsoft/Windows xp home/Windows xp pro)
Macromedia/Flash MX pro
Symantec/Norton AntiVirus/Symantec AntiVirus
Real Networks/RealOne Player/RealPlayer
RedHat/Fedora Core/RedHat Linus Enterprise
Borland/JBuilder pro
Mozilla/Firefox + Thunderbird + Sunbird/Mozilla Suite
Sun Microsystems/Netbeans/Sun Studio
IBM/Eclipse/Websphere Studio Application Developer
Tencent/QQ/IM
Uyou software/U8/NC
... /... /...

No Useless listing is required. This classification method has many benefits, such as clear customer classification and product pricing, but it is not discussed in this article, this article has more important questions to talk about.

We all know that there are several product lines in the list above that are notorious for choosing them, namely Windows and Sun Studio. But I believe there are still many such companies that are maintaining two notorious product lines. I didn't mean to belittle them. In fact, I have always paid tribute to Sun. They have a hard time doing this, including Microsoft. These difficulties come from these aspects:

1. Old customers.
Old customers are the biggest sources of profit for large companies and the biggest technical stumbling block for them. Most old customers will think that a. Protecting Their previous investments in software is a major task of software companies. Software companies should accept this task unconditionally. B. Software companies must fulfill any previous commitment that benefits them. C. Software companies should not use new technologies in customers' projects. They have never been used in other projects and won the world's praise.

2. Previously established technical standards.
Software enterprises usually release some technical standards set by the company. Attempt to use this as a competitive barrier to block competitors out of the city. In the eyes of large companies, these technical standards are very important. It determines whether large companies can retain the hearts of their partners, so they will make all their skills to support these technical standards. As a matter of fact, in the software field, there are only a few standards set by non-economic software organizations. The result is that, once these technical standards fall behind, software companies want to change them, and even large companies will be hard to find.

3. Shareholders.
The shareholders of a software company are not necessarily software experts. They are market experts. They don't care if your technology will be scolded by programmers, and they only care if the technology will be scolded by customers. What's more terrible is that all people are short-sighted. If the Board decides to develop a technology without any future, they will never admit that this decision is wrong.

4. Competitors, or very large-scale partners.
The two play the same role on some issues. Their decisions will directly affect the development of technology by software companies. After all, there is no harm to anyone who has one more friend and one opponent.

5. New customers, including new requirements of old customers.
Some major customers require the company to provide some new functions, which may be in conflict with one or more of the above three. In this case, the software company does not want to give up the old customers who are the source of profit, they do not want to give up fighting for new customers, so they often make smart choices for a compromise, or simply provide two different product features and two different services, and divide these two groups of customers into two different market segments. Sometimes this can make people laugh and cry, but as long as the customer does not have enough reason to give up the software company, the company will have the opportunity to hand over the black box to another type of customer group. So they will say to old customers that this is the requirement of new customers, and to new customers that this is the favorite of old customers.

In the face of these problems, software companies cannot say that they are in a dilemma, but at least they cannot let their technical talents go. I have provided a method to show my head. If it works well, we have to wait for the decision makers of the Linux system software enterprises to practice it.

Taking Microsoft as an example, most of the problems in Windows are that Microsoft must ensure that old-version windows-based applications developed by old customers. Therefore, when each version of windows is released, although Microsoft also wants to rewrite the code and use some new features in the operating system field, it also needs to take into account the previously established technical standards. My suggestion is that Microsoft should prepare an open lab field for itself. For example, if a brand new operating system is launched, it may not be named after windows, because it cannot be called "trial version" again), and I will call it doors for the time being. Doors is composed of all-new kernels. It is not fully compatible with earlier versions of windows and does not have to be compatible with the previous version, that is, the next version of doors does not have to be compatible with the previous version. It is free to download and some components are open-source, the open-source part can follow a "normative open-source" license, similar to Sun's SPL), and the underlying security technology is not open-source. If so, this test field can basically solve most of the problems mentioned above. Do not believe it.

1. Old customers.
Old customers may not use this operating system at all. Windows will continue to be used, and Microsoft will continue to release windows, without any ambiguity. Some open-minded old customers may use doors in part. However, due to the existence of Open-Source Licenses, Microsoft does not have to assume any responsibilities except security responsibilities when using doors.

2. Previously established technical standards.
Continue. Windows never changes. However, if some of the technologies on doors have been successfully tested and won unanimous praise from the technical community, Microsoft can safely use them on the next version of windows. At this time, Microsoft not only does not weaken its support for the old technical standards, but instead advances the release time of the new technical standards by one or half) the product cycle. Technical standards have a better representation of independence, so they are more favored by people.

3. Shareholders.
Since doors may rely on contributor, the company's investment in doors may not be as big as Outlook, probably similar to MSN Messenger.

4. Competitors, or very large-scale partners.
The biggest competitor of Microsoft in the operating system field is the Linux camp. It doesn't matter. Because doors is open-source, it can imitate some Linux practices, plagiarism and reverse behavior that attracts a large number of technical experts may even cause a fatal blow to the opponent.

5. New customers, including new requirements of old customers.
New requirements that conflict with the previous few items will be first implemented on doors, rather than windows, so that the right to choose will naturally fall into the hands of customers. New customers can choose to give up their own ideas, use doors, or -- more wise, use doors first. If this is not the feature the customer wants, they will give up or ask Microsoft to improve. If yes, don't worry, you can choose the next version of windows. It will be compatible with both this feature and the windows you are using. This is like going to the cinema to watch a movie, but the last one has not been closed, so I just got a seat to sit down and try out some melon seeds and drinks. while waiting for the film to be closed, I can regard it as KFC, although KFC has never been sold! No matter what the new customer chooses, he does not take Microsoft's palm.

The example is finished, and now enters the final submission stage. Software Enterprises with two product lines under a product category can choose to develop the third product line, which is neither a non-mainstream product nor a high-end application, but a test product with new features, the test item can be named as a non-mainstream. The test area is an open-source community. The test object is full of both technical talents and new and old customers. The test product does not need to be 100% compatible with any product, including the other two product lines and the third product released in the past, as long as it can achieve the expected test results. Linux system software.

1. Embedded Linux System Software Development
2. The Linux operating system is directly built on the kernel.
3. The truth about the Linux Makefile system is in line with free software practices.
4. How to install Linux into a Linux USB device
5. Linux desktops should have been using Linux servers five years ago.