📄 00000011.htm
字号:
<HTML><HEAD> <TITLE>BBS水木清华站∶精华区</TITLE></HEAD><BODY><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER>发信人: reden (On the way!), 信区: Linux <BR>标 题: The LSB is dead - Long live the LSB <BR>发信站: BBS 水木清华站 (Mon Mar 8 21:40:43 1999) <BR> <BR> Editorial: The LSB is dead - Long live the LSB <BR> <BR> Jim Pick - August 15th 1998, 11:54 EST <BR> <BR> <BR> Jim Pick originally intended to delve into some technical details <BR> <BR> about the differences between Debian and Red Hat and what obstacles <BR> <BR> lay in store for the LSB team. Due to the obscure activity that took <BR> <BR> place on the LSB mailing list (including Bruce Perens leaving the <BR> <BR> project), he changed his editorial to reflect the pros/cons of <BR> <BR> diversity in the Linux distribution space and what benefits there <BR> <BR> would be to have a LSB/LCS-style project. <BR> <BR> <BR> The LSB is dead! Long live the LSB! <BR> <BR> <BR> I signed up to write an editorial on the LSB. Unfortunately, I picked <BR> <BR> this week to do it. Oh joy. :-) <BR> <BR> <BR> I was originally going to delve into some technical details about the <BR> <BR> differences between Debian and Red Hat (both of which I am somewhat <BR> <BR> familiar with), and what obstacles lay in store for the LSB team. <BR> <BR> <BR> But the political shenanigans of this week have convinced me to <BR> <BR> change my editorial to reflect on the pros/cons of diversity in the <BR> <BR> Linux distribution space, and what benefits there would be to having <BR> <BR> a LSB/LCS-style project. I'll try to dish out some of the dirt on the <BR> <BR> current situation (as I understand it) as well. :-) <BR> <BR> <BR> I apologize for the length of this essay. I'm not very adept at <BR> <BR> compressing my arguments. <BR> <BR> <BR> First, I'll clear up some information about myself. I'm a 28 year old <BR> <BR> programmer / electrical engineer who has been using Linux since 1995. <BR> <BR> I first started with Slackware, and then moved to Debian when the 1.1 <BR> <BR> release came out in mid-1996. That same year, I became a Debian <BR> <BR> developer -- so I've had about 2 years exposure to the inside <BR> <BR> dealings involved in building a Linux distribution (Debian is 5 years <BR> <BR> old this weekend). I'm also the new webmaster for LinuxHQ, which I am <BR> <BR> (very) slowly rebuilding. <BR> <BR> <BR> Benefits of Diversity <BR> <BR> <BR> Why are there so many different Linux distributions? Because, "that's <BR> <BR> the way Linus wants it to be". <BR> <BR> <BR> When he wrote the Linux kernel, his goal could have been to put <BR> <BR> together a complete operating system distribution - much like what <BR> <BR> many other free OS's (FreeBSD, NetBSD, OpenBSD) have chosen to do. <BR> <BR> But as his interests lay primarily in hacking the kernel, he wisely <BR> <BR> left the politics of distribution building to others. <BR> <BR> <BR> As a result, there are many Linux distributions floating around out <BR> <BR> there. Each is different, some dramatically so. <BR> <BR> <BR> This is good, because they all can compete against each other. Think <BR> <BR> Darwin. Each distribution is evolving. The mature distributions (Red <BR> <BR> Hat, Debian, SuSE, Slackware, Caldera) have evolved to fit certain <BR> <BR> ecological niches. New distributions (ie. Stampede, Eonova, Mandrake) <BR> <BR> are born almost monthly. There are already many distributions that <BR> <BR> failed the "survival of the fittest" contest and have become extinct <BR> <BR> or morphed into something else (ie. SLS, Bogus, Lasermoon, <BR> <BR>cial applications by agreeing on a common <BR> <BR> filesystem hierarchy (ie. the FSSTND/FHS) and collaborating on naming <BR> <BR> libraries (ie. sonames). <BR> <BR> <BR> Determining policy such as this is, well, political. Oftentimes, <BR> <BR> there is no single technical solution. What emerges is a compromise <BR> <BR> based on negotiation. If all the distributions used identical policy <BR> <BR> for everything, there would be no differences between them, and no <BR> <BR> diversity. <BR> <BR> <BR> Some common policy would still be very nice to have. Anybody who is <BR> <BR> developing a distribution already has a set of policies in place. In <BR> <BR> the case of Debian, which is a bunch of volunteers distributed around <BR> <BR> the globe, this policy is written up in a formal policy document. <BR> <BR> Debian even has a tool called "lintian" that will analyze packages <BR> <BR> and point out hundreds of places where they violate policy. And it <BR> <BR> has a bug system so that policy violations can be tracked. The end <BR> <BR> result is a very consistent, high-quality distribution. <BR> <BR> <BR> Other distributions, such as Red Hat, Caldera or SuSE, have similar <BR> <BR> set of internal policies that have been informally developed, but <BR> <BR> aren't written up anywhere. This works for them, because the <BR> <BR> developers physically work together, and can talk shop over the <BR> <BR> water-cooler. One problem with this approach is that the "contrib" <BR> <BR> maintainers from outside of the company have no idea what the <BR> <BR> policies are, so they make mistakes. Red Hat is taking some steps to <BR> <BR> move to a Debian-style system for "contrib" developers with their <BR> <BR> Contrib|Net system (see developer.redhat.com). <BR> <BR> <BR> In conclusion, I do believe there is some benefit to having some <BR> <BR> common policy: increased source and binary compatibility (although <BR> <BR> perfect binary compatibility isn't really necessary or needed), and <BR> <BR> the existence of some formal policy documents for "contrib" <BR> <BR> developers to use (leading to higher quality contrib packages). It <BR> <BR> would be a good community-building exercise as well, as long as it is <BR> <BR> handled with some political tact. <BR> <BR> <BR> Jim Pick <BR> <BR> <BR>-- <BR>在江湖中,只要拿起了刀,就是一场无涯的梦。 <BR> <BR>※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 159.226.21.168] <BR><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER></BODY></HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -