As most LWN readers have doubtless heard by now, SCO has filed a
$1 billion lawsuit against IBM, claiming that IBM has misused SCO's
proprietary Unix technology in Linux. LWN posted
a look at SCO's complaint on the day it was
released. Since then, more detailed analyses (and rebuttals) of SCO's
claims have come out. See, for example,
Karsten
Self's commentary and the
proposed response on
the opensource.org site. Both are currently in draft form. Rather than
try to add to those well-researched responses, we'll take this space to try
to ponder some of the implications of this case.
But first, it's worth pointing out that there is some real amusement to be
found in Eric
Raymond's buyer's guide for Unix on PC hardware, dated 1993. He had a
warning for SCO and other proprietary systems vendors:
A complete, working UNIX plus GNU tools plus X is now available for
around $60 --- *with sources*. Your prices have to drop by an
order of magnitude, or your service has to get a whole hell of a
lot better, if you're going to try and compete with that. Adapt or
die.
The message clearly was not heard. But, thanks to the net, it still exists
to show to anybody who believes that SCO's entitlement to the x86 Unix
market was unchallenged until IBM came along.
It remains to be seen how this case will be resolved. What seems like an
obvious answer to the technical community sometimes comes across a little
differently to a court. Nonetheless, IBM is equipped with relatively
fearsome weaponry for the intellectual property battlefield. SCO will not
have an easy time of it.
In the mean time, what can we expect?
- SCO claims that this suit has nothing to do with the Linux
community - it is simply a contract dispute. But that is clearly not
true. By claiming that Linux could not have reached a useful state
without an illegal stream of proprietary technology provided by IBM,
SCO has insulted the Linux community. The alleged
ineptitude of those who hack on Linux is at the core of SCO's case.
Linux, they say, is a
bicycle compared to a luxury car; it is only suitable for hobbyists
and non-profit organizations. This display of contempt will not be
quickly forgotten.
- SCO's Unix business is doomed - they say so themselves in their
complaint: "Plaintiff stands at imminent risk of being deprived
of its entire stream of all UNIX licensing revenue in the foreseeably
near future." (Paragraph 119c). The company has slammed Linux
- and its development community - to the point that it is hard to
imagine how SCO will
attempt to sell Linux-based products and services with a straight
face. SCO, in other words, has just signalled its exit from the
operating system business. SCOsource is evidently supposed to be the
future of the company - if its management sees any future at all.
- It is hard to imagine the UnitedLinux consortium remaining intact
under this sort of stress. Whether the other members find a way to
ease SCO out, or whether the whole thing will simply fragment, remains
to be seen.
- This case may well affect the Linux market in the near future. People
choosing technologies for their businesses have a certain, rational
aversion to lawsuits and disputed technology. How big the effect will
be depends, certainly, on the perception of SCO's chances of success.
So far, the general view seems to be that (to put it charitably), SCO
has an uphill battle ahead of it. Investors have brought about a
slight rise in SCO's stock price, but the market capitalization of the
company remains under $30 million. That is not the
capitalization of a company that has convinced investors it will be
receiving a $1 billion judgement. If this perception does not
change, the effect of this lawsuit could be relatively small.
- If the complaint is to be believed, SCO's biggest grievances have
to do with the JFS filesystem and the Omniprint drivers. If Linux
were to lose these technologies, it would be a poorer system. But,
honestly, the lives of most Linux users would not be affected all that
much.
- We have been reminded of the dangers of code contamination. Anybody
who signs an agreement to view proprietary code, then goes on to work
on free software, risks (being accused of) contaminating that software
with proprietary
technology. That risk exists whether the proprietary code is Windows,
Solaris, or something belonging to SCO. Anybody who is contemplating
such an agreement should think long and hard about the consequences.
This is the first of the big Linux intellectual property lawsuits; we
should not expect it to be the last. Free software is too big a change,
and it threatens too many interests, for things to go any other way. We
are fortunate that the first attack was against a defendant with the
resources and interest to defend itself - though the defendant could
conceivably disagree. The burden of defending the next suit could well
fall on somebody less able to shoulder it.
Comments (7 posted)
[This article was contributed by Joe 'Zonker' Brockmeier]
If at first you don't succeed... Rep. Zoe Lofgren
(D-Calif.) reintroduced
the awkwardly-named Benefit
Authors without Limiting Advancement or Net Consumer Expectations
(BALANCE) Act last Monday. The bill was shot down last year in
committee. Rep. Rick
Boucher (D-Va.) is co-sponsoring the bill. Boucher has been
outspoken on the need for reform of the Digital Millennium Copyright Act
in the past, though he seems to be taking a back seat on this one (perhaps
because he has a DMCA
reform bill of his own on the table).
The BALANCE Act does not do away with the DMCA, as many in the Linux
community would like to see. Instead, it attempts to amend the DMCA to
allow for the exercise of fair use. The act notes that the DMCA "failed
to give consumers the technical means to make fair uses of encrypted
copyright works."
Not surprisingly, the Business Software Alliance (BSA) and the Motion
Picture Association of America are against the BALANCE Act. Jack Valenti
is quoted in the Mercury News as saying that the legislation "puts a dagger in the heart of the Digital Millennium Copyright Act," which is pretty much what everyone outside the entertainment and proprietary software industries would like to do.
The BSA's press release says that Lofgren's proposed exceptions go too far:
The broad exemptions to the DMCA proposed by Representative Lofgren
would undermine the core purpose of the Act and violate the protections
that serve as the foundation of innovation and discovery for legitimate
copyright owners. In the digital age, broadly accepted technological
measures must be available and adhered to by consumers and enterprises
to curb piracy and its economic consequences...
Of particular concern, provisions of this legislation allowing the
disablement of technological protection measures on copyrighted
materials would provide safe harbor for pirates who could easily claim
that the 'intent' of their actions were legal even if it resulted in
knowingly unlawful infringement and economic loss to copyright owners.
Interestingly, while the BSA comes out against the BALANCE Act, some of its
member
companies (i.e. Intel and HP) have been quick to endorse it and other bills
like it that seek to undo some of the damage of the DMCA and the
entertainment industry's relentless attempts to disallow fair
use.
A reading of the bill shows that the BSA's position is a stretch, at
best. The bill would ensure rights to "reproduce, store, adapt or access
the digital work" for archival purposes or to "perform or display the
work, or an adaptation of the work, on a digital media device, if the
work is not so performed or displayed publically."
Circumvention of copyright protection would be allowed only if "such an
act is necessary to make a noninfringing use of the work" and if "the
copyright owner fails to make publically available the necessary means
to make such noninfringing use without additional cost or burden to such
person." In short, the bill seems to say that somebody could legally
use or create something like DeCSS only if the movie studios do not
provide, free of charge,
a way for them to play DVDs on their devices.
The BSA is right about one thing: the BALANCE Act may very well hinder
shrinkwrap licensing, which the software industry loves so much. The act
would not allow enforcment of "nonnegotiable license terms...to the
extent that they restrict or limit any of the limitations or exclusive
rights" under the act. In other words, movies studios and software
companies could not apply shrinkwrap licenses that disallow backup
copies or circumvention that allows fair use. It's hard to see how that
would "stifle industry growth and limit consumer choices."
So far, however, the DMCA hasn't been used to "promote continued
innovation." It's been used to stifle competition
and prevent fair
use. Right now, the bill is in committee. The odds of passing the bill
are a long shot, but one can always hope that this bill, or one very much
like it, will make its way through Congress soon.
Comments (2 posted)
Page editor: Jonathan Corbet
Security
Brief items
[This article was contributed by Tom Owen]
Check your cookie list in your browser for cookies from imrworldwide.com --
if they're there, then the red sheriff is watching you.
You won't be alone.
For well over a year, vexed users have been popping up on the newsgroups,
in slashdot and on lists of all sorts with independent rediscoveries of
Redsheriff's
activities.
Unscientific sampling suggests that machines not owned by paranoid
technicians always have these cookies.
The web was not designed to make marketing easy.
Proxies and other caches mean that the server logs can dramatically undercount
page views and downloads.
Spiders and bots work the other way, but there's no reason to believe they
balance out.
The users share and reuse their IP addresses,
you can't tell for certain what country they're in, and
they even lie to their own PCs.
Maybe M. Mouse is a legitimate name in Martinique,
and a birth date of 01/01/01 might just mean that you saw
Steamboat
Willie
first time round. But probably not.
Advertisers hate this.
They hate trusting the word of a site owner about page impressions, but
even when those numbers make sense they still don't know if the campaign is
reaching the target preteens,
or is being wasted on middle-aged tax consultants who just really like Britney.
Many of them prefer to stick with old media where they get respectable numbers
from the likes of
Nielsen
and
ABC.
So the demand for better information is huge, and
there's a long history of attempts to get it:
doubleclick,
web bugs
and
third-party
cookies.
The big accounts at the traditional end of the industry prefer to trust
names
and methods translated from broadcast media:
closely monitored sample panels,
surveys and focus groups.
That would be fine, but one thing that no-one has ever been able to do is
reconcile the numbers from these two approaches.
Redsheriff want to bridge that gap -- by making the whole internet their
panel.
Founded in Australia in 1996 as a research firm,
by 2001 Redsheriff was expanding into technical means.
Along the way, they picked up global ambitions and some serious
capitalists
led by
WPP,
Martin Sorrel's advertising conglomerate.
Earlier website versions on the
Wayback
machine
couple horrifying wild-west copy with
fairly explicit information
about their offerings which is lacking from the current site.
And in fact they keep a lowish profile all round.
There are no secrets, but no fuss either and little interest in
publicity.
It doesn't matter: the evidence is easy enough to gather.
Redsheriff client sites (try Selfridges)
drop or reference two main components:
This is all traditional cross-platform stuff.
It's certainly unusual to use an applet for this job and some users have been
blaming Java,
but it means it'll work on anything: Mozilla, Opera, IE or that cool new
mobile phone.
Redsheriff say they can report on movement within a flash site,
as well as use of non-client sites, and it looks as though these are jobs for
the applet.
There doesn't seem to be an ActiveX component yet, but given MS's attitude
toward Java, this is
probably only a matter of time.
So far, Redsheriff knows many of the sites you visit from day to day and year
to year,
and within some of them they know the pages you look at.
This is a good start (for them), but technical means aren't enough: they
don't know who you are.
This next stage is probably what has piqued the interest of partners like
WPP
and
Taylor Nelson Sofres
What these buyers want is income, age, education, family status, and
Redsheriff apparently
gets it the easy way: by popping up a questionnaire with a chance of
winning some prize.
This questionnaire carries the client site branding,
but the data goes to the Redsheriff servers.
As a final touch, some percentage of the responses are qualified with
telephone interviews.
The privacy policy is surprisingly less clear than it could be -- it looks as
though
some identifying personal information will be held on the basis of the
target's consent implied when they filled in the survey.
Redsheriff is doing nothing all that weird, but the effect is still spooky.
Assuming their software and datacenter work right, they'll know largely
complete browsing histories
stretching over years for vast numbers of computers.
And if they can do the surveys right,
many of these histories will carry trustworthy demographic information and
many more will
be similar enough to have it inferred.
They can't quite equal a panel in joining up work and home browsing or
breaking out multi-use PCs
but their potential sample is so comprehensive they hardly care: the data are
going to make them big money.
If you don't want to be part of this database, it's easy to stop without
marring the browsing experience:
simply block third party cookies (erase any you have)
and don't run applets.
It's that easy. Maybe that's why they don't want the public gaze.
Comments (10 posted)
[This article was contributed by Tom Owen]
The recent discussion on Bugtraq (e.g.
here
and
here)
raised the ugly possibility that
ISC
was fixing security problems in BIND and keeping quiet about them.
In fact it does seem as though the release could have been better described in
the BIND list.
Two faults are
described at the end of the current
Bind
vulnerability listing
and the reason for the omission looks easy to guess:
One is in the resolver library rather than the daemon itself, and the other is
caused by linking with an unfixed version of
OpenSSL.
It's not wrong to keep up to date with BIND, but the earlier server is only
vulnerable if you
use DNSSEC and linked an older version of OpenSSL.
Comments (none posted)
New vulnerabilities
ethereal - format string vulnerability
| Package(s): | ethereal |
CVE #(s): | CAN-2003-0081
|
| Created: | March 10, 2003 |
Updated: | June 12, 2003 |
| Description: |
The SOCKS dissector in Ethereal 0.9.9 is susceptible to a format string
overflow. This vulnerability has been present in Ethereal since the SOCKS
dissector was introduced in version 0.8.7. It was discovered by Georgi
Guninski. Additionally, the NTLMSSP code is susceptible to a heap
overflow. All users of Ethereal 0.9.9 and below are encouraged to upgrade.
See the full
advisory for additional information. |
| Alerts: |
|
Comments (none posted)
mysqlcc - world readable file permissions
| Package(s): | mysqlcc |
CVE #(s): | |
| Created: | March 7, 2003 |
Updated: | March 12, 2003 |
| Description: |
Gentoo reports that versions of mysqlcc prior to 0.8.9 had all
configuration and connection files world readable. |
| Alerts: |
|
Comments (none posted)
netscape-flash: buffer overflow
| Package(s): | netscape-flash |
CVE #(s): | |
| Created: | March 10, 2003 |
Updated: | June 20, 2003 |
| Description: |
Potentially exploitable buffer overflows exist in the Macromedia Flash
Player. The full advisory is here.
"The cumulative security patch is available today and addresses the
potential for exploits surrounding buffer overflows (read/write) and
sandbox integrity within the player, which might allow malicious users to
gain access to a user's computer. The possibility of running native code on
a users machine is a theoretical exploit, and extremely difficult to
execute in practice. There are no known examples of running such native
code from Macromedia Flash movies; however, even though this issue is
difficult and theoretical in nature only, we are encouraging users to
upgrade." |
| Alerts: |
|
Comments (none posted)
qpopper - buffer overflow
| Package(s): | qpopper |
CVE #(s): | CAN-2003-0143
|
| Created: | March 12, 2003 |
Updated: | March 21, 2003 |
| Description: |
As reported in this advisory, qpopper 4.0.x
contains a buffer overflow vulnerability which may be exploited remotely -
but only by an attacker possessing a valid username and password. |
| Alerts: |
|
Comments (none posted)
usermode - local root compromise
| Package(s): | usermode |
CVE #(s): | |
| Created: | March 12, 2003 |
Updated: | March 15, 2003 |
| Description: |
The /usr/bin/shutdown program in the usermode package can be used to kill all running process and obtain a root shell. The best solution is simply to remove it. |
| Alerts: |
|
Comments (none posted)
Updated vulnerabilities
apcupsd - remote root vulnerability and buffer overflows
| Package(s): | apcupsd |
CVE #(s): | CAN-2003-0098
CAN-2003-0099
|
| Created: | February 24, 2003 |
Updated: | April 3, 2003 |
| Description: |
From the MandrakeSoft
advisory:
A remote root vulnerability in slave setups and some buffer overflows in
the network information server code were discovered by the apcupsd
developers. They have been fixed in the latest unstable version, 3.10.5
which contains additional enhancements like USB support, and the latest
stable version, 3.8.6.
There are a few changes that need to be noted, such as the port has changed
from port 7000 to post 3551 for NIS, and the new config only allows access
from the localhost. Users may need to modify their configuration files
appropriately, depending upon their configuration. |
| Alerts: |
|
Comments (none posted)
Heap corruption vulnerability in at
| Package(s): | at at, sudo, xchat |
CVE #(s): | CAN-2002-0004
|
| Created: | May 21, 2002 |
Updated: | May 15, 2003 |
| Description: |
The at command has a
potentially exploitable heap corruption bug.
(First LWN report: January 17th).
|
| Alerts: |
|
Comments (none posted)
BIND8: Multiple vulnerabilities
Comments (1 posted)
bind buffer overflow vulnerability in DNS resolver libraries
| Package(s): | bind glibc |
CVE #(s): | CAN-2002-0651
CAN-2002-0684
|
| Created: | July 8, 2002 |
Updated: | October 1, 2003 |
| Description: |
The BIND 4.9.8-OW2 patch and BIND 4.9.9 release (and thus 4.9.9-OW1)
include fixes for a libc related vulnerability which does not
affect Linux. Updates from
the Internet Software Consortium (ISC)
are available from here.
No release or branch of Openwall GNU/*/Linux (Owl) is known to be
affected, due to Olaf Kirch's fixes for this problem getting into the
GNU C library more than two years ago.
Unfortunatly that does not mean that Linux systems are not vulnerable.
Similar code, without Olaf Firch's fixes,
is in the glibc getnetbyXXX functions.
These functions are described in the SuSE alert as
"
used by very few applications only, such as ifconfig and ifuser,
which makes exploits less likely."
CERT Advisory: CA-2002-19
Buffer Overflow in Multiple DNS Resolver Libraries
CAN-2002-0651
CAN-2002-0684 |
| Alerts: |
|
Comments (1 posted)
BitchX - denial of service
| Package(s): | BitchX |
CVE #(s): | |
| Created: | February 20, 2003 |
Updated: | May 26, 2003 |
| Description: |
From this Bugtraq posting:
A denial of service vulnerability exists in BitchX. Sending a malformed
RPL_NAMREPLY numeric 353 causes BitchX to segfault. This problem was
reported to panasync@efnet#bitchx on Jan 30 2003, as of this writing we are
unaware of any patches or workarounds provided by panasync and or any
members of #bitchx |
| Alerts: |
|
Comments (none posted)
Canna server: exploitable buffer overrun
| Package(s): | canna |
CVE #(s): | CAN-2002-1158
CAN-2002-1159
|
| Created: | December 10, 2002 |
Updated: | October 1, 2003 |
| Description: |
Canna is a kana-kanji conversion server which is necessary for Japanese
language character input.
A buffer overflow bug in the Canna server up to and including version 3.5b2
allows a local user to gain the privileges of the user 'bin' which could
lead to further exploits. The Common Vulnerabilities and Exposures project
(cve.mitre.org) has assigned the name CAN-2002-1158 to this issue.
A lack of validation of requests has been found that affects Canna version
3.6 and earlier. A malicious remote user could exploit this vulnerability
to leak information, or cause a denial of service attack. (CAN-2002-1159)
See also
http://canna.sourceforge.jp/sec/Canna-2002-01.txt
CAN-2002-1158
CAN-2002-1159 |
| Alerts: |
|
Comments (none posted)
CVS - exploitable double-free bug in the CVS server
| Package(s): | cvs |
CVE #(s): | CAN-2003-0015
|
| Created: | January 20, 2003 |
Updated: | April 7, 2003 |
| Description: |
CVS is a version control system frequently used to manage source code
repositories. During an audit of the CVS sources, Stefan Esser
discovered an exploitable double-free bug in the CVS server.
On servers which are configured to allow anonymous read-only access, this
bug could be used by anonymous users to gain write privileges. Users with
CVS write privileges can then use the Update-prog and Checkin-prog features
to execute arbitrary commands on the server.
All users of CVS are advised to upgrade to erratum packages which contain
patches to correct the double-free bug.
See also this CERT advisory |
| Alerts: |
|
Comments (none posted)
dhcp3 - ignored counter boundary
| Package(s): | dhcp3 |
CVE #(s): | CAN-2003-0039
|
| Created: | January 28, 2003 |
Updated: | April 5, 2003 |
| Description: |
Florian Lohoff discovered a bug in the dhcrelay causing it to send a
continuing packet storm towards the configured DHCP server(s) in case
of a malicious BOOTP packet, such as sent from buggy Cisco switches.
When the dhcp-relay receives a BOOTP request it forwards the request
to the DHCP server using the broadcast MAC address ff:ff:ff:ff:ff:ff
which causes the network interface to reflect the packet back into the
socket. To prevent loops the dhcrelay checks whether the
relay-address is its own, in which case the packet would be dropped.
In combination with a missing upper boundary for the hop counter an
attacker can force the dhcp-relay to send a continuing packet storm
towards the configured dhcp server(s).
This patch introduces a new commandline switch ``-c maxcount'' and
people are advised to start the dhcp-relay with ``dhcrelay -c 10''
or a smaller number, which will only create that many packets.
The dhcrelay program from the ``dhcp'' package does not seem to be
affected since DHCP packets are dropped if they were apparently
relayed already. |
| Alerts: |
|
Comments (none posted)
dvips: command execution vulnerability
| Package(s): | dvips |
CVE #(s): | CAN-2002-0836
|
| Created: | October 16, 2002 |
Updated: | June 10, 2003 |
| Description: |
The dvips utility uses the system() function improperly when managing fonts. An attacker who can craft the right sort of print job can use this vulnerability to execute commands under the UID used by the print system. |
| Alerts: |
|
Comments (none posted)
Filename disclosure vulnerability in fam
| Package(s): | fam |
CVE #(s): | CAN-2002-0875
|
| Created: | August 19, 2002 |
Updated: | January 5, 2005 |
| Description: |
"fam" (file alteration monitor) watches files and directories for changes and lets interested applications know when something happens. This package has a flaw in its group handling that blocks some legitimate operations while, at the same time, exposing the names of files that should otherwise be invisible. |
| Alerts: |
|
Comments (none posted)
fetchmail: buffer overflow
| Package(s): | fetchmail |
CVE #(s): | CAN-2002-1365
|
| Created: | December 17, 2002 |
Updated: | October 20, 2003 |
| Description: |
Versions of fetchmail prior to 6.2.0 have (yet another) buffer overflow vulnerability which can be exploited remotely via a suitably crafted message. See this advisory for details. |
| Alerts: |
|
Comments (3 posted)
file - memory allocation problem, stack overflow
| Package(s): | file |
CVE #(s): | CAN-2003-0102
|
| Created: | March 4, 2003 |
Updated: | June 4, 2003 |
| Description: |
Jeff Johnson found a memory allocation problem and David Endler found a
stack overflow corruption problem in the file "Automatic File Content
Type Recognition Tool" version 3.41. Nalin Dahyabhai improved ELF section
and program header handling in file version 3.40. The folks at OpenPKG
believe that file versions without those modifications are vulnerable to
memory allocation and stack overflow problems which put security at risk. |
| Alerts: |
|
Comments (none posted)
GNU fileutils race condition
| Package(s): | fileutils ucdsnmp |
CVE #(s): | CAN-2002-0435
|
| Created: | May 21, 2002 |
Updated: | May 16, 2003 |
| Description: |
A race
condition in rm may cause the root user to delete the whole filesystem.
The problem exists in the version of rm in
fileutils
4.1 stable and 4.1.6 development version. A patch
is available.
(First LWN
report: May 2).
|
| Alerts: |
|
Comments (none posted)
Potential remote root exploit in glibc
| Package(s): | glibc |
CVE #(s): | CAN-2002-0391
|
| Created: | August 14, 2002 |
Updated: | June 30, 2003 |
| Description: |
Felix von Leitner, discovered a
potential division by zero bug in
code derived from the SunRPC library which is used in glibc.This bug could be
exploited to gain unauthorized root access to software linking to glibc.
Updating as soon as practical is a good idea.
Because SunRPC-derived XDR libraries are used by a variety of vendors in a variety of applications, this defect may lead to a number of differing security problems. Exploiting this vulnerability will lead to denial of service, execution of arbitrary code, or the disclosure of sensitive information.
CERT/CC Vulnerability Note VU#192995 Integer
overflow in xdr_array() function when deserializing the XDR stream
|
| Alerts: |
|
Comments (none posted)
glibc: DNS stub resolvers contain buffer overflow vulnerability
| Package(s): | glibc |
CVE #(s): | CAN-2002-1146
|
| Created: | November 7, 2002 |
Updated: | February 5, 2004 |
| Description: |
DNS stub resolvers from multiple vendors contain a buffer overflow
vulnerability. The impact of this vulnerability appears to be limited to
denial of service. (See CERT Vulnerability Note
VU#738331)
The BIND 4 and BIND 8.2.x stub resolver libraries, and other libraries such
as glibc 2.2.5 and earlier, libc, and libresolv, uses the maximum buffer
size instead of the actual size when processing a DNS response, which
causes the stub resolvers to read past the actual boundary ("read buffer
overflow"), allowing remote attackers to cause a denial of service
(crash).
|
| Alerts: |
|
Comments (none posted)
IM: creates temporary files insecurely
| Package(s): | im |
CVE #(s): | CAN-2002-1395
|
| Created: | December 3, 2002 |
Updated: | March 6, 2003 |
| Description: |
Tatsuya Kinoshita discovered that IM, which contains interface
commands and Perl libraries for E-mail and NetNews, creates temporary
files insecurely.
- The impwagent program creates a temporary directory in an insecure
manner in /tmp using predictable directory names without checking
the return code of mkdir, so it's possible to seize a permission
of the temporary directory by local access as another user.
- The immknmz program creates a temporary file in an insecure manner
in /tmp using a predictable filename, so an attacker with local
access can easily create and overwrite files as another user.
|
| Alerts: |
|
Comments (none posted)
IMP - SQL injection vulnerability
| Package(s): | imp |
CVE #(s): | CAN-2003-0025
|
| Created: | January 15, 2003 |
Updated: | July 8, 2003 |
| Description: |
The IMP IMAP server, versions 2.2.8 and prior, is vulnerable to SQL
injection; see this advisory for details.
Version 3.x is not vulnerable to this problem. |
| Alerts: |
|
Comments (1 posted)
kdelibs: Vulnerabilities in KIO subsystem support
| Package(s): | kdelibs |
CVE #(s): | CAN-2002-1281
CAN-2002-1282
|
| Created: | November 22, 2002 |
Updated: | March 15, 2003 |
| Description: |
Vulnerabilities were discovered in the KIO subsystem support for various
network protocols. The implementation of the rlogin protocol affects all
KDE versions from 2.1 up to 3.0.4, while the flawed implementation of the
telnet protocol only affects KDE 2.x. They allow a carefully crafted URL
in an HTML page, HTML email, or other KIO-enabled application to execute
arbitrary commands as the victim with their privilege.
The KDE team provided a patch for KDE3 which has been applied in these
packages. No patch was provided for KDE2, however the KDE team recommends
disabling both the rlogin and telnet KIO protocols. This can be
accomplished by removing, as root, the following files:
/usr/share/services/telnet.protocol and
/usr/share/services/rlogin.protocol.
If either file also exists in a user's ~/.kde/share/services directory,
they should likewise be removed.
See also:
http://www.kde.org/info/security/advisory-20021111-1.txt |
| Alerts: |
|
Comments (none posted)
kernel-utils: setuid vulnerability
| Package(s): | kernel-utils |
CVE #(s): | CAN-2003-0019
|
| Created: | February 7, 2003 |
Updated: | January 21, 2005 |
| Description: |
The kernel-utils package contains several utilities that can be used to
control the kernel or machine hardware. In Red Hat Linux 8.0 this package
contains user mode linux (UML) utilities.
The uml_net utility in kernel-utils packages with Red Hat Linux 8.0 was
incorrectly shipped setuid root. This could allow local users to control
certain network interfaces, add and remove arp entries and routes, and put
interfaces in and out of promiscuous mode.
All users of the kernel-utils package should update to these packages that
contain a version of uml_net that is not setuid root.
Alternatively, as a work-around to this vulnerability issue the following
command as root:
chmod -s /usr/bin/uml_net |
| Alerts: |
|
Comments (none posted)
libpng, libpng3: buffer overflow
| Package(s): | libpng, libpng3 |
CVE #(s): | CAN-2002-1363
|
| Created: | December 19, 2002 |
Updated: | July 14, 2004 |
| Description: |
Glenn Randers-Pehrson discovered a problem in connection with 16-bit
samples from libpng, an interface for reading and writing PNG
(Portable Network Graphics) format files. The starting offsets for
the loops are calculated incorrectly which causes a buffer overrun
beyond the beginning of the row buffer. |
| Alerts: |
|
Comments (none posted)
lynx: CRLF injection vulnerability
| Package(s): | lynx |
CVE #(s): | CAN-2002-1405
|
| Created: | November 19, 2002 |
Updated: | October 1, 2003 |
| Description: |
If lynx is given a url with some special characters on the command line, it
will include faked headers in the HTTP query. This feature can be used to
force scripts (that use Lynx for downloading files) to access the wrong
site on a web server with multiple virtual hosts.
CAN-2002-1405 |
| Alerts: |
|
Comments (none posted)
perl-MailTools: remote command execution
| Package(s): | MailTools |
CVE #(s): | CAN-2002-1271
|
| Created: | November 5, 2002 |
Updated: | September 19, 2003 |
| Description: |
The SuSE Security Team reviewed critical Perl modules, including the
Mail::Mailer package. This package contains a security hole which allows
remote attackers to execute arbitrary commands in certain circumstances.
This is due to the usage of mailx as default mailer which allows commands
to be embedded in the mail body.
Note that mail processing programs which use this package can be affected by this vulnerability; in particular, SpamAssassin is vulnerable if you use the -r or -w flags.
|
| Alerts: |
|
Comments (none posted)
mhc - insecure temporary file
| Package(s): | mhc |
CVE #(s): | |
| Created: | February 28, 2003 |
Updated: | March 5, 2003 |
| Description: |
It has been discovered that adb2mhc from the mhc-utils package has a temporary file vulnerability. The
default temporary directory uses a predictable name, allowing a local attacker to overwrite arbitrary
files. |
| Alerts: |
|
Comments (none posted)
micq: Denial of service
| Package(s): | micq |
CVE #(s): | |
| Created: | December 13, 2002 |
Updated: | April 24, 2003 |
| Description: |
Rüdiger Kuhlmann, upstream developer of mICQ, a text based ICQ client,
discovered a problem in mICQ. Receiving certain ICQ message types
that do not contain the required 0xFE seperator causes all versions to
crash. |
| Alerts: |
|
Comments (none posted)
MySQL: multiple vulnerabilities
| Package(s): | mysql |
CVE #(s): | |
| Created: | December 13, 2002 |
Updated: | April 10, 2003 |
| Description: |
The MySQL database server has several buffer overflow and integer bounds checking vulnerabilities which can lead to denial of service attacks, and, possibily, remote code execution. See this e-matters advisory for details. Version 3.23.54 fixes the problems. |
| Alerts: |
|
Comments (none posted)
nethack: buffer overflow
| Package(s): | nethack, slashem, falconseye |
CVE #(s): | CAN-2003-0358
CAN-2003-0359
|
| Created: | February 18, 2003 |
Updated: | July 15, 2003 |
| Description: |
Overflowing a buffer in nethack may lead to privilege escalation to games
uid.
Read the the full advisory for the details.
Note that falconseye does not contain the file permission error
CAN-2003-0359 which affected some other nethack packages. |
| Alerts: |
|
Comments (none posted)
net-snmp: denial of service vulnerability
| Package(s): | net-snmp |
CVE #(s): | CAN-2002-1170
|
| Created: | December 17, 2002 |
Updated: | November 7, 2003 |
| Description: |
The SNMP daemon included in the Net-SNMP package versions 5.0.1 through
5.0.4 can be caused to crash if it is sent a specially crafted packet. |
| Alerts: |
|
Comments (none posted)
OpenSSL: plaintext exposure vulnerability
| Package(s): | openssl |
CVE #(s): | CAN-2003-0078
|
| Created: | February 19, 2003 |
Updated: | March 6, 2003 |
| Description: |
A vulnerability has been found in OpenSSL that, given the right conditions,
could lead to the exposure of transactions in plain text. This problem
looks difficult to exploit (it requires a man-in-the-middle attack, among
other things), but one can't be too sure, so the OpenSSL project has
released versions 0.9.7a (with the fix and some new features) and 0.9.6i
(with fixes only). See the announcement for details. |
| Alerts: |
|
Comments (none posted)
pam_xauth: root exploit
| Package(s): | pam_xauth |
CVE #(s): | CAN-2002-1160
|
| Created: | February 13, 2003 |
Updated: | July 10, 2003 |
| Description: |
The pam_xauth module is used to forward xauth information from user to user
in applications such as 'su'.
Andreas Beck discovered that versions of pam_xauth supplied with Red Hat
Linux since version 7.1 would forward authorization information from the
root account to unprivileged users. This could be used by a local attacker
to gain access to an administrator's X session. In order to exploit this
vulnerability, the attacker would have to get the administrator, as root,
to use su to the account belonging to the attacker. |
| Alerts: |
|
Comments (none posted)
PHP: vulnerability in mail function
| Package(s): | php |
CVE #(s): | CAN-2002-0985
CAN-2002-0986
|
| Created: | November 13, 2002 |
Updated: | October 1, 2003 |
| Description: |
Two vulnerabilities exists in the mail() PHP function. The first one allows
the execution of any program/script bypassing safe_mode restriction, the
second one may give an open-relay script if the mail() function is not
carefully used in PHP scripts. See this Bugtraq
report for more details. Note that this is a different vulnerability than the previous PHP mail() problem, which affected versions through 4.1.0.
CAN-2002-0985
CAN-2002-0986 |
| Alerts: |
|
Comments (none posted)
PostgreSQL - more buffer overflows
| Package(s): | postgresql |
CVE #(s): | |
| Created: | February 12, 2003 |
Updated: | November 7, 2003 |
| Description: |
A new set of buffer overflows has been discovered in PostgreSQL 7.2.2; they affect the circle_poly(), path_encode(), and path_addr() functions. Exploiting these overflows requires that the attacker first obtain a connection to the PostgreSQL server. |
| Alerts: |
|
Comments (1 posted)
Local arbitrary code execution vulnerability in Python
| Package(s): | python |
CVE #(s): | CAN-2002-1119
|
| Created: | August 28, 2002 |
Updated: | October 1, 2003 |
| Description: |
Zack Weinberg discovered that
os._execvpe from os.py uses a predictable name which could lead
to execution of arbitrary code. According to the Debian
advisory, the problem
was present in Python versions 1.5, 2.1 and 2.2.
CAN-2002-1119 |
| Alerts: |
|
Comments (none posted)
Multiple-use vulnerability in Safe.pm
| Package(s): | Safe.pm |
CVE #(s): | CAN-2002-1323
|
| Created: | October 9, 2002 |
Updated: | February 20, 2004 |
| Description: |
usePerl has a
description of a vulnerability in the Safe.pm Perl module. It seems
that if a Safe compartment is used more than once, it ceases to be safe.
The problem is fixed in Safe 2.08. |
| Alerts: |
|
Comments (none posted)
sendmail - Remote Buffer Overflow
| Package(s): | sendmail |
CVE #(s): | CAN-2002-1337
|
| Created: | March 3, 2003 |
Updated: | March 10, 2003 |
| Description: |
ISS has turned
up an unpleasant problem with sendmail; by sending a properly crafted
message, an attacker can run arbitrary code as root on a target
system. This is the sort of hole that can lead to all sorts of problems,
including widespread breakins and Internet worms. Everybody who is running
sendmail should upgrade to version 8.12.8 at the first
opportunity. Note that systems behind firewalls need to be fixed too.
See CERT Advisory CA-2003-07 for additional
information. |
| Alerts: |
|
Comments (2 posted)
slocate - buffer overflow
| Package(s): | slocate |
CVE #(s): | CAN-2003-0056
|
| Created: | February 5, 2003 |
Updated: | May 8, 2003 |
| Description: |
version 2.6 (at least) of slocate contains a buffer overflow vulnerability which could lead to a local exploit; see this advisory for the details.
|
| Alerts: |
|
Comments (none posted)
snort - buffer overflow
| Package(s): | snort |
CVE #(s): | CAN-2003-0033
|
| Created: | March 5, 2003 |
Updated: | April 4, 2003 |
| Description: |
A buffer overflow in the snort intrusion detection system can lead to
remote code execution and/or disabling of intrusion detection. The 1.9.1
release fixes the problem. See this
advisory for more information. |
| Alerts: |
|
Comments (none posted)
squirrelmail - cross-site scripting vulnerability
| Package(s): | squirrelmail |
CVE #(s): | CAN-2002-1276
CAN-2002-1341
|
| Created: | March 5, 2003 |
Updated: | March 5, 2003 |
| Description: |
A new cross-site scripting vulnerability afflicts Squrrelmail 1.2.10 and prior. |
| Alerts: |
|
Comments (none posted)
File overwrite vulnerability in tar and unzip
| Package(s): | tar unzip |
CVE #(s): | CAN-2001-1267
CAN-2001-1268
CAN-2001-1269
CAN-2002-0399
|
| Created: | October 1, 2002 |
Updated: | April 10, 2006 |
| Description: |
The tar utility does not properly filter file names containing
"../", meaning that a hostile archive can, if unpacked by an
unsuspecting user, overwrite any file that is writable by that user. GNU
tar versions 1.13.19 and earlier are vulnerable; unzip through version 5.42
has the same vulnerability. |
| Alerts: |
|
Comments (1 posted)
tcpdump - infinite loop
| Package(s): | tcpdump |
CVE #(s): | CAN-2003-0108
|
| Created: | February 28, 2003 |
Updated: | May 1, 2003 |
| Description: |
Andrew Griffiths and iDEFENSE Labs discovered a problem in tcpdump, a
powerful tool for network monitoring and data acquisition. An
attacker is able to send a specially crafted network packet which
causes tcpdump to enter an infinite loop.
In addition to the above problem the tcpdump developers discovered a
potential infinite loop when parsing malformed BGP packets. They also
discovered a buffer overflow that can be exploited with certain
malformed NFS packets. |
| Alerts: |
|
Comments (none posted)
Multiple vendor telnetd vulnerability
| Package(s): | telnet Telnet netkit-telnet-ssl kerberos telnetd netkit-telnet nkitb/nkitserv/telnetd krb5 |
CVE #(s): | |
| Created: | May 21, 2002 |
Updated: | October 5, 2004 |
| Description: |
This vulnerability,
originally thought to be confined to BSD-derived systems, was first covered
in the July 26th Security
Summary. It is now known that Linux telnet daemons are vulnerable as
well.
|
| Alerts: |
|
Comments (none posted)
typespeed: buffer overflow
| Package(s): | typespeed |
CVE #(s): | |
| Created: | January 1, 2003 |
Updated: | June 17, 2003 |
| Description: |
A problem has been discovered in the typespeed, a game that lets you
measure your typematic speed. By overflowing a buffer a local
attacker could execute arbitrary commands under the group id games. |
| Alerts: |
|
Comments (none posted)
vim - modeline vulnerability
| Package(s): | vim |
CVE #(s): | CAN-2002-1377
|
| Created: | January 16, 2003 |
Updated: | February 10, 2004 |
| Description: |
VIM allows a user to set the modeline differently for each edited text file
by placing special comments in the files. Georgi Guninski found that these
comments can be carefully crafted in order to call external programs. This
could allow an attacker to create a text file such that when it is opened
arbitrary commands are executed. |
| Alerts: |
|
Comments (4 posted)
vnc - replay and cookie vulnerabilities
| Package(s): | vnc |
CVE #(s): | CAN-2002-1336
CAN-2002-1511
|
| Created: | February 21, 2003 |
Updated: | May 5, 2003 |
| Description: |
VNC is a tool for providing a remote graphical user interface. Two
vulnerabilities have been found in versions of VNC shipped by Red Hat.
The VNC server acts as an X server, but the script for starting it
generates an MIT X cookie (which is used for X authentication) without
using a strong enough random number generator. This could allow an
attacker to be able to more easily guess the authentication cookie.
The VNC DES authentication scheme is implemented using a challenge-response
architecture, producing a random and different challenge for each
authentication attempt. A bug in the function for generating the random
challenge caused the random seed to get reset to the current time on every
authentication attempt. Therefore, two authentication attempts within the
same second could receive the same challenge. An eavesdropper could
exploit this vulnerability by replaying the response, thereby gaining
authentication.
All users of VNC are advised to upgrade to these erratum packages, which
contain patches to correct these issues. |
| Alerts: |
|
Comments (none posted)
eterm, vte: dangerous interception of escape sequences
| Package(s): | vte, eterm |
CVE #(s): | CAN-2003-0021
CAN-2003-0068
CAN-2003-0070
|
| Created: | March 3, 2003 |
Updated: | April 1, 2003 |
| Description: |
From the
advisory:
"Many of the features supported by popular terminal emulator software
can be abused when un-trusted data is displayed on the screen. The impact
of this abuse can range from annoying screen garbage to a complete system
compromise. All of the issues below are actually documented features,
anyone who takes the time to read over the man pages or source code could
use them to carry out an attack." |
| Alerts: |
|
Comments (none posted)
wget:directory traversal bug
| Package(s): | wget |
CVE #(s): | CAN-2002-1344
|
| Created: | December 10, 2002 |
Updated: | October 1, 2003 |
| Description: |
Versions of wget prior to 1.8.2-4 contain a bug that permits a malicious
FTP server to create or overwrite files anywhere on the local file system.
FTP clients must check to see if an FTP server's response to the NLST
command includes any directory information along with the list of filenames
required by the FTP protocol (RFC 959, section 4.1.3).
If the FTP client fails to do so, a malicious FTP server can send filenames
beginning with '/' or containing '/../' which can be used to direct a
vulnerable FTP client to write files (such as .forward, .rhosts, .shosts,
etc.) that can then be used for later attacks against the client machine.
See also
this Bugtraq article from 1997.
CAN-2002-1344 |
| Alerts: |
|
Comments (none posted)
Problems with libgtop_daemon
| Package(s): | wuftpd libgtop |
CVE #(s): | |
| Created: | May 21, 2002 |
Updated: | May 7, 2003 |
| Description: |
The libgtop_daemon package is a GNOME
program which makes system information available remotely.
LWN reported the remotely exploitable format
string and buffer overflow vulnerabilities in that package
on December 6th.
On November 28th
disabling the libgtop_daemon on systems where it is running until
an update is available.
Many Linux systems do not run
libgtop by default, but applying the update is a good idea anyway.
|
| Alerts: |
|
Comments (1 posted)
Wwwoffle remote privilege escalation vulnerability
| Package(s): | wwwoffle |
CVE #(s): | CAN-2002-0818
|
| Created: | August 14, 2002 |
Updated: | October 1, 2003 |
| Description: |
The wwwoffle web proxy incorrectly processes HTTP PUT and POST requests
with negative Content Length values.
"It is believed
that an attacker could exploit this bug to gain remote wwwrun access
to the system wwwoffled is running on."
CAN-2002-0818 |
| Alerts: |
|
Comments (none posted)
zlib 1.1.4 has buffer overrun
| Package(s): | zlib |
CVE #(s): | CAN-2003-0107
|
| Created: | February 25, 2003 |
Updated: | April 29, 2003 |
| Description: |
From this Bugtraq
posting:
"zlib contains a function called gzprintf(). This is similar in
behaviour to fprintf() except that by default, this function will smash the
stack if called with arguments that expand to more than Z_PRINTF_BUFSIZE
(=4096 by default) bytes." |
| Alerts: |
|
Comments (none posted)
Page editor: Jonathan Corbet
Kernel development
Brief items
The current development kernel is 2.5.64, unchanged from one week
ago. Linus has been busy, however; his BitKeeper tree includes more driver
model work, the continuing removal of unwanted stuff from devfs, a uClinux
update, an x86-64 update, some block layer cleanups (see below), scheduler
changes for improved interactive response (see below again), and a number
of other fixes.
Alan Cox has released 2.5.64-ac3 which adds
a new set of IDE updates. "Handle with care."
The current stable kernel is 2.4.20; Marcelo has not released any
2.4.21 prepatches over the last week.
Alan Cox's current 2.4.21 prepatch is 2.4.21-pre5-ac3. Here you'll find an even
newer set of IDE changes, along with quite a few other fixes and updates.
Comments (1 posted)
Kernel development news
The 2.5 kernel features a massively reworked scheduler which, among other
things, improves the interactive feel of a desktop system. It goes to
great lengths to try to separate interactive tasks from "background"
processes, and to give a priority boost to the former. One way that this
distinction is made is to look at how much time each process spends
sleeping. Processes that sleep a lot are generally waiting for humans to
do something, so the kernel tries to ensure that, when they wake up, they
get quick access to the processor.
This heuristic works well much of the time, but it also fails badly in some
situations. Consider, for example, the case of a user dragging a window
across the screen. That sort of operation can require a fair amount of
computation on the part of the X server. If the system is busy anyway
(with a kernel compilation, for example), the X server can end up using all
of the processor time that is available to it. When the server stops
sleeping, the kernel concludes that it is a compute-bound background task
and drops its priority. At that point, the pointer stops keeping up with
the mouse, and the desktop experience becomes generally unpleasant.
A classic solution (which predates Linux) for this problem is to raise the
priority of the X server. A higher-priority server can make things work
better for some users, but it ignores the fact that similar situations can
arise with other interactive processes that require
a fair amount of processor time. Streaming media applications tend to work
this way, for example. Raising the priority of the X server can make
things worse for this sort of application. Also, as Linus points out, tweaking priorities in this way is
an indication that the system has failed somehow:
Something is wrong, and we couldn't fix it, so here's the band-aid
to avoid that problem for hat particular case. It's acceptable as a
band-aid, but if you don't realize that it's indicative of a
problem, then you're just kidding yourself.
A few patches have gone into the 2.5.65 kernel which, by most reports, make
things a lot better. One of them, which originally came from Linus, is
based on the recognition that, if an interactive process is waiting for
another process to do something, that other process should be considered
interactive as well. The X server may be using a fair amount of CPU time,
but, since interactive processes (i.e. the clients that the user works
with) are waiting for it, the X server should still be seen as an
interactive process.
The ideal time to make this adjustment might be when an interactive process
goes to sleep waiting for an event. Unfortunately, that is hard to do; the
kernel has no way to know, in the general case, who will be waking up
processes that sleep on a particular queue. On the other hand, when the
wakeup actually occurs, the relationship is immediately obvious. So the
new scheduler will, at wakeup time, look at the interactivity bonus for the
process being awakened. If that process has maxed out its bonus (as
processes that sleep a lot will), the "excess" interactivity bonus is
given, instead, to the process which is performing the wakeup. Thus, a
sleeping mail client gives some of its bonus to the X server, which wakes
it up. This patch is said to improve the interactivity of X
significantly.
Ingo Molnar has taken Linus's patch and merged it into a larger set of
scheduler changes (which, in turn, has gone into 2.5.65). Some of the
additional changes that have been made include:
- Various scheduler parameter tweaks. The maximum timeslice given to
any process has been reduced, for example (to 200ms).
- One process can preempt another with the same priority, if the former
has a longer remaining timeslice.
- The first wakeup of a newly-forked child has been made smarter,
resulting in less work being redone.
The end result of these changes is a kernel which provides a much more
satisfying interactive experience. Note, however, that some causes of X
server stalls - in particular, those related to disk I/O scheduling - still
have not been resolved. Work is ongoing, however.
(See also: Jim Houston's self-tuning scheduler
patch, which takes a different approach to scheduler improvement).
Comments (12 posted)
Long-suffering block driver maintainers will have to cope with a new change
in 2.5.65:
this patch from Andries Brouwer
changes the prototype of
register_blkdev(), which is used by block
drivers to tell the kernel of their existence. The previous version of
this function took a
struct block_device_operations pointer,
which contains some of the operations provided by the driver. That
parameter has not been used for some time (block operations are now
directly associated with disks, and are kept in the generic disk
structure), so Andries removed it.
Not everybody agreed with this change. With all of the work that has been
done in the block layer, register_blkdev() does not actually do
very much anymore. Its main remaining purpose is to associate a driver
name with a major number, so that it shows up in /proc/devices. A
block driver can now function nicely without calling
register_blkdev() at all. The long-term plan is to remove
register_blkdev() altogether. In the mean time, it was asked, why
bother changing the prototype of a doomed function? Even so, the change
was merged into 2.5.65.
The real purpose of Andries's patch, however, was to get rid of the static
blkdevs array used to keep track of block devices in the kernel.
blkdevs is about the only static array left in the block
subsystem, and thus is one of the remaining impediments to Andries's real
goal: the long-awaited expansion of dev_t to 32 bits.
The 32-bit dev_t is one of the final items on the 2.5
"todo" list. It is still considered important by many users: an Oracle
engineer mentions 4000-disk systems that
"want to go to Linux" but can't, and from IBM we hear about a 5000-drive system with waiting
customers. There appears to be little opposition to the adoption of a
larger dev_t, even at this late stage. But everybody agrees that
it would be best to get this change done sooner rather than later.
The amount of work remaining is said to be relatively small. The block
layer, for example, is almost ready for a larger dev_t now. The
char device
subsystem could take more work - many drivers "know" that device numbers
(especially minor numbers) are only eight bits. So a detailed audit of
many drivers could be required. This suggestion
from Alan Cox could make life a little easier, though. The idea would
be to replace the venerable register_chrdev() function with a new
register_chr_device() which takes a parameter indicating the
largest minor number that the driver can deal with. A change to
all char drivers would still be required, but, by defaulting the maximum
minor number to 255, these drivers could be made safe without the need for
a larger "audit and fix" operation. The few drivers that actually need
more minor numbers could be fixed individually.
There are, of course, other issues to deal with before a larger
dev_t will be truly stable. Some protocols (i.e. NFSv2) aren't
prepared for large device numbers. The interface to user space may well
hold a surprise or two. And so on. These are all problems that can be
solved, but the process will take time.
(As an aside, Alexander Viro, who has been an active participant in the
block layer and dev_t work, has been absent from kernel
development for a few months. In a recent
message, however, he proclaimed "I'm finally back - hopefully for
good." Welcome back, Al).
Comments (none posted)
Another incomplete 2.5 development item is initramfs - an initial
filesystem attached to the kernel image. The plan is to move much of the
early boot code into initramfs, so that it can be run in user mode. But
there has not been a whole lot of progress in that direction.
One part of the process is klibc, a small C library to be used in initramfs
applications. A patch exists which adds a
working klibc to the 2.5.64 kernel, but Linus is
not ready to merge it:
However, I also have to say that klibc is pretty late in the game,
and as long as it doesn't add any direct value to the kernel build
the whole thing ends up being pretty moot right now. It might be
different if we actually had code that needed it (ie ACPI in user
space or whatever).
In other words, unless some code which really needs klibc does not show up
soon, it may not get merged into 2.5 at all. That would have the effect of
pushing the whole initramfs project back into the next development series.
There are people working on creating this code, but, as Linus says,
it's late in the game.
Comments (none posted)
Smatch is Dan Carpenter's project to
create a free version of the Stanford Checker. The project is making
progress, and smatch is now capable of finding several classes of bugs in
the Linux kernel. Some
patches fixing bugs
found by smatch have already begun to appear.
The database of problems found by smatch is now hosted at kbugs.org. As of 2.5.64, there are just over
1000 potential bugs in the database. Many of them are certainly false
alarms, but others will be real. An interesting feature of the kbugs.org
site is the ability to "moderate" bugs as being real problems or not.
With this capability, interested volunteers can help to sift out the real
bugs, even if they don't feel able to contribute patches to fix them.
The smatch project is still in an early stage, but it is already showing
great promise as a tool which can help in the creation of a better kernel.
Comments (none posted)
The new epoll interface was covered here
back in
October, 2002. The epoll system calls offer a significant performance
improvement for applications which must frequently poll large numbers of
file descriptors. It does so by performing the setup work only once, and
then trapping new I/O events as they occur.
One aspect of the epoll interface is that it is edge-triggered; it
will only return a file descriptor as being available for I/O after a
change has happened on that file descriptor. In other words, if you tell
epoll to watch a particular socket for readability, and a certain amount of
data is already available for that socket, epoll will block anyway. It
will only flag that socket as being readable when new data shows
up.
Edge-triggered interfaces have their own advantages and disadvantages. One
of their disadvantages, as epoll author Davide
Libenzi has discovered, would appear to be that many programmers do not
understand edge-triggered interfaces.. Additionally, most existing
applications are written for
level-triggered interfaces (such as poll() and
select()) instead. Rather than fight this tide, he has sent out
a new patch which switches epoll over to
level-triggered behavior. A subsequent
patch makes the behavior configurable on a per-file-descriptor basis.
The end result is a more flexible epoll interface that can be more easily
used in existing applications. The patch has not been merged as of this
writing, but there does not seem to be any reason why it shouldn't be.
After all, epoll has not yet appeared in a stable kernel release; now is
the best time to be making improvements to the interface.
Comments (10 posted)
Larry McVoy has
announced the availability
of the current BitKeeper kernel repository in CVS format. Things are still
stabilizing, but the plan is to have the current 2.4 and 2.5 repositories
available in CVS format in near real time. Almost all of the change and
commit information will be available, making it easy for people who are
unwilling or unable to run BitKeeper to peruse the kernel's revision
history and track current developments. Says Larry:
Our goal is to provide the data in a way that you can get at it
without being dependent on us or BK in any way. As soon as we have
this debugged, I'd like to move the CVS repositories to kernel.org
(if I can get HPA to agree) and then you'll have the revision
history and can live without the fear of the "don't piss Larry off
license". Quite frankly, we don't like the current situation any
better than many of you, so if this addresses your concerns that
will take some pressure off of us.
Of course, when dealing with this sort of topic, things are never that
easy. People will certainly be happy to have the CVS repository available,
but one other aspect of the announcement has made people nervous. It seems
that the near-SCCS file format used by BitKeeper is increasingly difficult
to work with; now that BitKeeper repositories can be accessed in CVS
format, the BitKeeper developers would like to move to a new, proprietary
format. And that idea does not fly with all developers; this complaint from Ben Collins has been echoed
by a few hackers:
You've made quite a marketing move. It's obvious to me, maybe not
to others. By providing this CVS gateway, you make it almost
pointless to work on an alternative client. Also by providing it,
you make it easier to get away with locking the revision history
into a proprietary format.
It is clear that, as long as BitKeeper is in use by the kernel development
community, some people are going to be unhappy. Nothing short of the
complete freeing of the BitKeeper source will satisfy some users, and that
does not appear to be in the cards. Fortunately this disagreement, while
noisy, hasn't really gotten in the way of continued kernel development.
In
fact, it hasn't even gotten in the way of BitKeeper as it improves the
kernel development process. Regardless of what one thinks of BitKeeper or
its license, the fact remains that kernel development has been working well
over the last year; an incredible stream of patches has been merged, and
the people involved have stayed sane. As sane as they were before,
anyway.
(As an aside, Larry has suggested that the
license clause that forbids (free) BitKeeper use by people working on other
source management systems could be removed in the future "if we feel
we have pulled far enough ahead that everyone else is just playing
catchup").
Comments (1 posted)
Driver porting
The first big, disruptive changes to the 2.6 kernel came from the reworking
of the block I/O layer. As one might guess, the result of all this work is
a great many changes as seen by driver authors - or anybody else who works
with block I/O. The transition may be painful for some, but it's worth it:
the new block layer is easier to work with and offers much better
performance than its predecessor.
Fully covering the changes that have been made will require a whole series
of articles. So we'll start with an overview which highlights the major
changes that have been made without getting into any sort of detail.
Subsequent articles will fill in the rest.
Note that parts of the block layer remain volatile - this development is
not yet complete. We'll keep up with further changes as they happen.
So, what has changed with the block layer?
- A great deal of old cruft is gone. For example, it is no longer
necessary to work
with a whole set of global arrays within block drivers. These arrays
(blk_size, blksize_size, hardsect_size,
read_ahead, etc.) have simply vanished. The kernel still
maintains much of the same information, of course, but the management
of that information is much improved.
- As part of the cruft removal, most of the <linux/blk.h>
macros (DEVICE_NAME, DEVICE_NR, CURRENT,
INIT_REQUEST, etc.) have been removed;
<linux/blk.h> is now empty. Any block driver
which used these macros to implement its request loop will have to be
rewritten. It is still possible to implement a simple request loop
for straightforward devices where performance is not a big issue, but
the mechanisms have changed.
- The io_request_lock is gone; locking is now done on a
per-queue basis.
- Request queues have, in general, gotten more sophisticated. Quite a
bit of work has been done in the area of fancy request scheduling
(though drivers don't generally need to know about that). There is
simple support for tagged command queueing, along with features like
request barriers and queue-time device command generation. Request
queues must be allocated dynamicly in 2.6.
- Buffer heads are no longer used in the block layer; they have been
replaced with the new "bio" structure. The new
representation of block I/O operations is designed for flexibility and
performance; it encourages keeping large operations intact. Simple
drivers can pretend that the bio structure does not exist,
but most performance-oriented drivers - i.e. those that want to
implement clustering and DMA - will need to be changed to work with
bios.
One of the most significant features of the
bio structure is that it represents I/O buffers directly with
page structures and offsets, not in terms of kernel virtual
addresses. By default, I/O buffers can be located in high memory, on
the assumption that computers equipped with that much memory will also
have reasonably modern I/O controllers. Support operations have been
provided for tasks like bio splitting and the creation of DMA
scatter/gather maps.
- Sector numbers can now be 64 bits wide, making it possible to support
very large block devices.
- The rudimentary gendisk ("generic disk") structure from 2.4
has been greatly improved in 2.6; generic disks are now used
extensively throughout the block layer. Among other things, each
generic disk has its own block_device_operations structure;
the operations are no longer directly associated with the driver. The
most significant change for block driver authors, though, may be the
fact that partition handling has been moved up into the block layer,
and drivers no longer need know anything about partitions. That is,
of course, the way things should always have been.
Subsequent articles will explore the above changes in depth; stay tuned.
Comments (1 posted)
Patches and updates
Kernel trees
Core kernel code
Development tools
Device drivers
Documentation
Filesystems and block I/O
Janitorial
Memory management
- Rik van Riel: rmap 15e.
(March 12, 2003)
Networking
Architecture-specific
Benchmarks and bugs
Miscellaneous
Page editor: Jonathan Corbet
Distributions
Distribution News
The
Debian Weekly News for March 11, 2003
looks at some recent Linux kernel developments, Debian fun
stuff from Openstuff.net, and much more.
Here is the call for votes for the Debian
Project Leader Election 2003.
The Debian release manager is looking for
assistants to help with the many tasks that need to be accomplished
before sarge can be released.
Join in the third bug squashing party for sarge, March 14 - 16, 2003, and
help to correct as many release critical bugs as possible in all those
Debian packages.
Comments (none posted)
Here's the Gentoo Weekly Newsletter for the week of March 10, 2003. This
week GWN looks at distcc in a nutshell; and notes that they got a
remarkable response to their call for developers.
Full Story (comments: none)
The Mandrake Linux Community Newsletter for March 7 is out; it looks at the
second Mandrake Linux 9.1 release candidate, the business case of the
week, and more.
Full Story (comments: none)
Here is
the
press release from Red Hat regarding its new commercial distribution
offerings. "Red Hat Enterprise Linux ES" is a cheaper version of the
Advanced Server product (now "Red Hat Enterprise Linux AS"); "
It is
ideally suited for application-, network-, file-, print-, mail-, and
Web-serving, as well as for running custom or packaged business
applications." Also available is "Red Hat Enterprise Linux WS,"
which is aimed at engineering workstations - software development,
electronic design, etc.
Comments (4 posted)
Slackware has released a second
candidate for Slackware 9.0. As usual the gory details can be found in the
slackware-current change log.
Comments (1 posted)
SuSE has
announced SuSE Linux 8.2, a
strongly desktop-oriented version of the company's distribution.
Availability is mid-April.
The company has also launched a new partner
program, which is aimed at helping others sell SuSE products.
Comments (2 posted)
Robin Miller
interviews Mike Hearn, leader of the Autopackage project in this
NewsForge article. "
Autopackage is a concept that is in the process
of becoming a reality, a little bit at a time, in the traditional Open
Source manner. The idea is to come up with a single software
packaging/installation system that will work across all major Linux
distributions, and resolve dependencies, too, so that neither developers
nor users need to worry about distribution compatibility issues."
Thanks to Ashwin N
Comments (none posted)
New Distributions
Orange Linux is a
floppy-based Linux distribution that includes a set of tools for making
your own distribution, a VGA graphics library, and a small Pong game.
Initial version
1.0 was
released March 11, 2003.
Comments (none posted)
rpm-livelinuxcd is a 120MB RedHat-based distribution that runs
completely from CD, fits into around 80MB of RAM and is nearly
indistinguishable from a system installed on a hard disk. Features include
hardware recognition at boot, samba, dhcpd, name, xinetd, and SSH servers,
virtual terminals, PAM, etc. Useful for dedicated servers, routers,
emergency systems, cluster nodes and such, it does not contain an X11
Server. Initial version
0.9 was released March 5,
2003.
Comments (none posted)
Minor distribution updates
ALT Linux has released
v2.2 with major feature
enhancements. "
Changes: This release contains a lot of new packages
in addition to largely improved existing base; almost all of them are built
with gcc3. The already good server and desktop is now a lot better with a
larger degree of audited and secured services and smoother office and
multimedia applications out-of-the-box."
Comments (none posted)
Astaro Security Linux
has released
v4.001
with major bugfixes. "
Changes: This Up2Date fixes bugs in the
AntiSpam Feature in the SMTP Relay, the Pfsgroup variable setting in IPSec
VPN, an issue in the POP3 Proxy, and a problem with empty IPSec logs, and
sets the correct crypto algorithm for the Blowfish IPsec policy. Outgoing
emails are no longer checked for spam."
Comments (none posted)
Fd Linux has released
v3.0-0 with major feature
enhancements. "
Changes: In this version, the kernel was upgraded to
2.4.20 and migrated to iptables. PCMCIA support was added to incorporate
PCMCIA network cards and 802.11b wireless adapters, such as Lucent/Orinoco,
Cisco, and D-Link cards. There was a complete rewrite of the rc.network
automatic network configuration script, and this version moves over to the
uClibc library set to save on space, upgrades to the udhcp DHCP
client/server binaries, compiles in more commands and functions into
BusyBox, provides working add-on packages for usage expansion, has the
ability to mount extra portions of RAM to expand file system, and features
much more."
Comments (none posted)
The
LinuxInstall.org Project has
released
v3.0rc1.
"
Changes: This release includes kernel 2.4.18-26.8.0, security
updates, Mozilla 1.2.1, Evolution 1.2.2, a complete set of Red Hat 8.0
manual documents in HTML, Acrobat Reader 5.06 with Mozilla Plugin, Real
Player 8.0 with Mozilla Plugin, Flash Player 6.0 r69 with Mozilla Plugin,
Microsoft TrueType Core Fonts for Web, XMMS 1.2.7, xine 0.9.18 with
libdvdcss, and a dual-boot configuration with NTFS/FAT32 support."
Comments (none posted)
Morphix has released
v0.3-3 with minor feature
enhancements. "
Changes: XFree v4.3 added, a number of installer bugs
have been fixed, and a translucency lkm mini-module is available for
testing."
Comments (none posted)
The Trinity Rescue Kit has released v1.0. It now has networking
capabilities like ssh and samba and supports about every network card, disk
controller and USB controller.
Full Story (comments: none)
uClinux has released
v20030305 with major
feature enhancements. "
Changes: Lots of new things and lots of
fixes. This release has both uClinux 2.4.20 and 2.0.39 kernels,
uClibc-0.9.19, glibc-2.2.5. and uC-libc, over 50 board types with default
configurations, and about 150 application packages."
Comments (none posted)
Distribution reviews
This
iodynamics
article looks at Red Hat Linux 8.0, with some helpful hints to help you
make the most of your Red Hat desktop. "
Red Hat's latest Linux
distribution is one example of this progress. The distribution comes with
hundreds of great open-source applications, but it takes some 'tweaking' to
configure Red Hat as a complete desktop OS. While many applications are
included, some, for one reason or another, are not. And of those that are
included, some need additional configuration to work properly."
Comments (none posted)
Page editor: Rebecca Sobol
Development
C and C++ programmers encounter the ternary operator early in their
education. This operator, which in C syntax, looks like:
<condition> ? <expression1> : <expression2>
evaluates to expression1 if (and only if) the given
condition evaluates true; otherwise expression2 is
chosen. The ternary operator is a compact representation of a common
operation (choosing between two values), and it is a heavily-used feature
in languages which provide it.
Python does not provide a ternary operator, much to the chagrin a subset of
hackers who are otherwise very happy with the language. As a way of
responding to years of requests, Python Benevolent Dictator For Life Guido
van Rossum posted a proposal for a Pythonic
ternary operator, and asked the community to get back to him with its
opinion. To say that the discussion was active would be a substantial
understatement; thousands of messages were posted discussing the merits of
ternary operators, whether Python should have one, and what form it should
take. The result was a revised version of PEP 308.
That proposal included a few possible forms for a Python ternary operator.
The primary proposal was for this form:
(if <cond>: <expr1> else: <expr2>)
This form is easily extended to four or more operands:
(if <cond>: <expr1> elif <cond2>: <expr2> else: <expr3>)
Unusually for Python, the parentheses would be mandatory. For that reason,
and the fact that the syntax looks a lot like the regular
if/else control structure, not everybody was happy with this
proposal. So a number of alternatives were floated as well. They range
from the standard C syntax to variants like:
<cond> and <expr1> else <expr2>
<cond> then <expr1> else <expr2>
<expr1> if <cond> else <expr2>
cond(<cond>, <expr1>, <expr2>)
<cond> ?? <expr1> || <expr2>
<cond> -> <expr1> else <expr2>
If this were Perl, the language hackers would have probably just
implemented all the possibilities and been done with it. But Python
programmers like
to have one accepted way of doing things, so a decision had to be made. A
vote was held, and the results are now
available.
No alternative won a clear majority of the 518 votes counted. The
parenthesized syntax from the proposal got the most votes, but the C syntax
was not far behind. The "no change" contingent was rather smaller, but
very passionate in its arguments. The end result is that vote coordinator
Raymond Hettinger has not chosen to certify a winning proposal as such.
Instead. he is passing the results back to the Benevolent Dictator who,
after all, has a rather larger vote than anybody else. As of this writing,
Guido has not made his decision known.
Comments (5 posted)
System Applications
Audio Projects
Version 0.9.1 of the
ALSA
collection of sound driver, library, utilities, and tools
has been released. This is the first stable release in the 0.9
series.
Comments (none posted)
Version 0.61.0 of the JACK Audio Connection Kit is available.
New features include in-process client support, bug fixes,
and improved documentation.
Full Story (comments: none)
Version 0.2.4 of librdf is available.
"
liblrdf is a library for handling RDF files describing LADSPA plugins,
plus it can also do lightweight general RDF tasks."
This version adds a pkgconfig file and bug fixes.
Full Story (comments: none)
The
Planet CCRMA project provides a collection of RPM packages for
turning a Red-Hat based computer into an audio workstation.
The latest change are as follows:
"
Added a preliminary version of a Planet CCRMA roadmap, it should
help you identify potentially useful programs. This is just a first
version, most probably incomplete, hopefully not very
innacurate :-)"
Comments (none posted)
Database Software
Version 7.4.03.14 of
SAP DB is available.
See the
Release Information
for change information.
Comments (none posted)
Marc de Graauw
shows how to use XML topic maps with databases on O'Reilly.
"
Relational databases are great for storing structured data which conforms to a well-defined relational database schema. They are not so good at storing information that does not conform to such a schema. Since user requirements inevitably change, this means costly database upgrades."
Comments (3 posted)
Education
Issue #91 of the
Linux in Education Report is out. Topics include
a report from
the Lane Community College's Open Source Educational Group,
putting a Linux lab into Logan High School,
the Demo@Schools project, SkoleLinux,
a table of equivalents / replacements / analogs of Windows software in Linux,
a discussion on the limits of Open-source Software,
setting up a computer lab for OS testing, the
Linux in Education Spring Conference, and more.
Comments (none posted)
Electronics
The latest
new software from the
gEDA project includes
Icarus Verilog development snapshot 20030308, and
GTKWave 2.0.0pre3-20030304.
Comments (none posted)
Printing
Version 4.32 beta of GSview, a PostScript viewing program,
has been announced.
Changes include security fixes for compatibility with AFPL Ghostscript 8.00,
Catalan, Russian and Slovak language support, and minor bug fixes.
Comments (none posted)
The latest news from
LinuxPrinting.org includes
the addition of a number of HP, Epson, and Minolta printers to the
Foomatic printer support database.
Comments (none posted)
Web Site Development
Version 1.0 of Midgard Components Framework is now available
under the GNU LGPL license.
"
MidCOM provides a
framework for creating reusable and configurable components for web
applications using the Midgard Content Management Framework."
Full Story (comments: none)
Version 0.6beta3 of Quixote, a Python-based web development framework,
is available.
Change information is in the source code.
Comments (none posted)
The most recent headlines on the
Zope Members News
include: Zope at the CeBIT 2003 in Hannover!,
MailBoxer 2.2.2 released,
Initial Release of CSVFile Product,
CJKSplitter v0.2,
TextIndexNG 1.09 released,
CMF 1.3.1 Released,
CMFCollectorNG 0.20 final released,
Update to the ieeditor addon,
Silva Windows installer,
and Initial release of RSessionDA.
Comments (none posted)
Stas Bekman continues his O'Reilly series on mod_perl tweaking with
part 8.
"
In this article we continue talking about how to optimize your site for performance without touching code, buying new hardware or telling casts. A few simple httpd.conf configuration changes can improve the performance tremendously."
Comments (none posted)
Miscellaneous
The first pre-release of the code for the
Mojolin Project is available. Mojolin is a web-based system that
connects job seekers with potential employers.
Full Story (comments: none)
L. Victor Marks
introduces 802.11g wireless networking on IBM's developerWorks.
"
The bid continues to improve the 802.11 standard to something that fulfills our wireless transmitting fantasies. Victor Marks shows us how 802.11g has shaped up, and how it's fareing in the race."
Comments (none posted)
Desktop Applications
Audio Applications
Version 0.3.1 of LADCCA, the
Linux Audio Developer's Configuration and Connection API, is available
and features a few bug fixes.
"
LADCCA is a session management system for JACK and ALSA audio applications on GNU/Linux."
Full Story (comments: none)
Version 0.3.7 of swh-plugins, an audio systhesis package, is available.
This edition features changes to the gate code and the addition of
a bandlimiting filter.
Full Story (comments: none)
Version 0.2.1 of SpiralSynth Modular, "
an object orientated music
studio with an emphasis on live use", is out.
Changes include a new GUI, midi note filtering, new plugin groups,
more theming, a matrix pattern sequencer, bug fixes, and more.
Full Story (comments: none)
Version 0.4.1 of
ecamegapedal,
a real-time audio effects processor,
has been released. Bugs have been fixed in the build process. See the
release notes for more information.
Comments (none posted)
Version 0.7 of RTMix is available.
"
RTMix is an open-source (GPL-licensed) software application
designed to
provide stable, user-friendly, standardized, and efficient performance
interface that enables performer(s) to interact with both the computer
and each other in the least obtrusive fashion."
Many new features and fixes are included in this release.
Full Story (comments: none)
Desktop Environments
The March 7, 2003 edition of the
KDE-CVS-Digest is out. Topics are summarized as:
"
KDevelop gets more templates, Quanta
gets better action toolbars and Umbrello gets new code generators.
A dummy KDE 3.2 release schedule. More merges from Safari to KHTML."
Comments (none posted)
A new version of Workrave, a Gnome-based tool that helps people
with Repetitive Strain Injuries (RSI),
has been announced.
"
Workrave now keeps track of all your activity and allows you to browse through any date in history to see for how long you used the computer, how many keys you pressed, the distance your mouse moved, and many other statistical data."
Comments (none posted)
FootNotes has
an announcement
for Eel and Nautilus 2.2.2.
"
Normally we don't anounce nautilus releases to mailing lists. "We
won't bother," we say to ourselves, "people will find it eventually."
But "eventually" won't cut it with this release.
It is too darned good."
Comments (none posted)
eWeek
reviews
GNOME 2.2. "
The latest upgrade of the GNOME Foundation's desktop
environment offers users a spare and approachable graphical interface to
Linux and similar operating systems that's matured noticeably since its
last release."
Comments (none posted)
FootNotes
announces the latest GNOME Systems Tools release.
"
A new version of the GNOME System Tools has seen the light!,
this is mainly a bugfix release, so no new features have been added."
Comments (none posted)
Interoperability
Version 3.0alpha22 of
Samba is available.
"
The latest alpha snapshot of the SAMBA_3_0 cvs tree is available for download. It is being provided for testing purposes."
The release notes are available
here.
Comments (none posted)
Office Applications
The OpenOffice.org project has decided that the time has come to form a
"community council" to guide its further development. The council is
expected to be made up of nine members representing various parts of the
project (and a seat for Sun Microsystems). It will make decisions on
strategic planning (where OOo should be going) and resource allocation,
represent the project to Sun and the public, and arbitrate disputes within
the development community. There will be an online vote, starting
March 14, on the council charter; read the announcement if you are
interested in participating.
Full Story (comments: 1)
Issues number
133 and
134 of the AbiWord Weekly News are available. The latest issue
is summarized as:
"
Fixes to the Linux/PPC build comes in from one unknown hacker, while another name, Larin Hennessy, makes quite the noticeable splash. Snapping back to the release outline for AbiWord II: The Wrath of Dom results in a hard feature freeze. Finally, Hub knocks off two more posers on the Release HackDown for 1.0.5"
Comments (none posted)
Issue #71 of
Kernel Cousin GNUe is out with the latest GNU Enterprise
development news. Topics include:
Release plans and Case-Insensitive Queries, Multi-part delimited
Stock-Keeping Units in gnue-sb, GNUe Tools users,
Running GNUe Small Business, and GNUe Small Business vs. sql-ledger.
Comments (none posted)
The March 6, 2003 edition of the
LyX Development News
is out, with news of LyX release 1.3.0 and other development work.
Comments (none posted)
Web Browsers
Development version 1.3.3 of the lightweight Galeon browser
has been announced.
"
This is the release many of you have been waiting for, it reintroduces
the much wanted javascript etc. quick toggles. You're slowly running
out of excuses if that has been your reason to stay with the stable
1.2.x releases ;)"
Comments (none posted)
The latest
mozillaZine topics include:
Another Round of 1.3 Candidate Builds,
Honesty Issues Dog Anonymous Donations Poll,
1.3 Candidate Builds Available for Testing,
BBC News Examines Alternative Browsers,
Xabyl 1.0 Alpha Released, Preferences Toolbar 2.2 Released,
Mitchell Baker on Browser Innovation, Gecko and the Mozilla Project,
and Camino 0.7 Released!.
Comments (none posted)
Miscellaneous
FootNotes has
an announcement for version 0.99 of Gnome ICU, an internet chat
utility.
"
After months of hard work we have a new release. The main focus
of this release was to get all of the features in place for 1.0.
Only one BIG thing
is missing: working, stable file transfer. All other ICQ features should be
here."
Comments (none posted)
Languages and Tools
Caml
The March 11, 2003 Caml Weekly News looks at
Libraries in functional languages, ipv6, and Xcaml 0.0.1.
Full Story (comments: none)
This week, the new software on
The Caml Light / OCaml Hump includes:
SKS; an OpenPGP keyserver, bibgrep; a bibtex file index and search
utility, and CamlG4; a library for Objective Caml for performing
SIMD parallel processing on PowerPC G4 processors.
Comments (none posted)
Java
Otis Gospodnetic
introduces Lucene on O'Reilly.
"
Lucene is a free text-indexing and -searching API written in Java. To appreciate indexing techniques described later in this article, you need a basic understanding of Lucene's index structure. As I mentioned in the previous article in this series, a typical Lucene index is stored in a single directory in the filesystem on a hard disk."
Comments (none posted)
Satya Komatineni
discusses Hierarchical data sets on O'Reilly.
"
This article examines the structure of, and a Java API for, Hierarchical Data Sets. Unlike the XML Journal reference two years ago, you will now actually have a piece of executable code to use to start taking advantage of Hierarchical Data Sets."
Comments (none posted)
Lisp
A call for code has been issued for the Macsyma project.
"
Maxima is a computer algebra system written in Common Lisp. It is a
descendant of DOE Macsyma, whose origins date back to the late 1960s at
MIT."
Thanks to Paolo Amoroso.
Full Story (comments: none)
Perl
Larry Wall has posted
Apocalypse 6,
a look at how Perl 6 will handle subroutines. "
Unlike regexes,
Perl subroutines don't have a lot of historical cruft to get rid of. In
fact, the basic problem with Perl 5's subroutines is that they're not
crufty enough, so the cruft leaks out into user-defined code instead, by
the Conservation of Cruft Principle. Perl 6 will let you migrate the cruft
out of the user-defined code and back into the declarations where it
belongs."
Comments (5 posted)
The March 3, 2002 edition of
This week on Perl 6 is available.
Topics include:
IMCC calling conventions, A couple of easy questions...,
More on optimizing the JIT with IMCC,
Parrot 0.0.10 freeze, Dan's plans, PSteve Peters' Patches Prevent
Parrot Peeves, and Meanwhile, in perl6-language.
Comments (none posted)
The March 4, 2003 edition of
the Perl Journal has been published.
Topics include:
"
Fractal Images and Music With Perl,
Writing Multilingual Sites With mod_perl and Template Toolkit,
Perl in High Performance Computing Environments,
Something for Nothing by Simon Cozens,
Creating Perl Application Distributions by brian d foy,
And more, including a review of Graphics Programming in Perl."
Comments (none posted)
Version 0.65 of PAR
has been announced.
"
PAR is a cross
between JAR and Perl2exe/PerlApp; this version marks significant
improvements
like automatic binary installation, POD stripping and 5.6.1
support."
Comments (none posted)
PHP
Topics on this week's
PHP Weekly Summary
include: 64-bit compatibility, namespaces in ZE2, Apache2 and PHP,
Extensions with Debian Woody, sqlite extension, and ZE fixes.
Comments (none posted)
Python
The Dr. Dobb's Python-URL is available with weekly news and links for the
Python community.
Full Story (comments: none)
This week's
Daily Python-URL
article topics include:
Slashback: Rocketry, Pythonation, Scoffing, Python in a Nutshell,
Create declarative mini-languages, Metaclass programming in Python,
Inside the RSS validator, and more.
Comments (none posted)
Ross Burton
shows how to access C code from Python.
"
Learning how to wrap GTK+ C modules for use in Python will enable you to use a C-coded GObject in Python whenever you like, whether or not you're especially proficient in C."
Comments (none posted)
Ruby
New topics on the
Ruby Garden include:
nil.method_missing (Objective-C behaviour) and
propagating comparisons like Python.
Comments (none posted)
Topics on this week's
Ruby Weekly News
include: Russian Ruby resource and Ruby Course,
Test::Unit::Mock: Mock objects for testing with Test::Unit,
PSE as Ruby module and an RAA question,
OSCON, and
"I'm to give short talk on ruby at work, anybody have material/outlines
they can donate".
Comments (none posted)
Scheme
The March 10, 2003 edition of the Scheme Weekly News is available.
Full Story (comments: none)
Smalltalk
Version 3.4 of
Squeak has been released.
"
Squeak is a personal multimedia environment aimed at end-users of all
ages, developers, authors, and teachers. Beneath its graphical user
interface, it is powered by a descendant of the Smalltalk-80 language."
Full Story (comments: 1)
XML
Bob DuCharme
covers
linking and XSLT on O'Reilly.
"
In the ongoing debate about the future of linking, a key topic is the representation of one-to-many links. There are several ways to implement them, mostly by using JavaScript code to create pop-up menus, but the only standard way to represent them is W3C XLink extended links, and these have not caught on."
Comments (none posted)
Miscellaneous
Version 0.23 of Mono, an
open source implementation of the .NET Development Framework,
has been released.
"
This is only a bug fix release, because we introduced an unfortunate bug in reflection in version 0.22. This should fix compilation for many of you that had problems."
Comments (none posted)
There is a new
plugins page on the Jext programmer's editor site.
A number of plugin extensions to the editor are listed.
Comments (none posted)
Page editor: Forrest Cook
Linux in the news
Recommended Reading
Now we get to see where the "SCOSource" program is going: according to
this ZDNet article, SCO has filed suit against IBM, claiming that IBM has moved SCO's intellectual property into Linux.
"
Linux's rapid maturity--for example, growing up to work on large multiprocessor servers--is evidence of the presence of Unix intellectual property, the SCO suit said. 'It is not possible for Linux to rapidly reach Unix performance standards for complete enterprise functionality without the misappropriation of Unix code, methods or concepts to achieve such performance, and coordination by a larger developer, such as IBM,' the suit said."
Comments (25 posted)
Here's
Wired's
take on the SCO vs. IBM suit. "
Open-source programmers are
rallying behind IBM, and say SCO's lawsuit is "suicidal" and "an insult to
open-source programmers.""
Comments (14 posted)
SCO's lawsuit against IBM continues to generate considerable press
coverage. Interested LWN readers will have already read
our analysis of the suit. For those who want
to read more, here are just a few of the articles we've seen in the past
couple of days.
Open for Business says SCO
Needs to Go. "... the company seems to have decided the best
course of action is to do the business equivalent of [a] suicidal person
murdering those around him prior to taking his own life and attempt to take
the GNU/Linux community with it as it goes down the tubes."
Joe Barr at LinuxWorld finds it funny, but not 'ha-ha'
funny. "Having established early on in the complaint that they
apparently know very little about the history of Unix and free software,
SCO continues by trudging into new areas in which to display just how
tenuous a grasp they have on computing in general."
News.com reports: IBM
unfazed by SCO Unix threat. ""We've reviewed our contracts, and
our Unix license is irrevocable and perpetual," Mike Fay, vice president of
communications for IBM's systems group, said in an interview Monday. "We're
completely committed to AIX and will continue to ship it.""
Comments (1 posted)
PCLinuxOnline has responded to the
SCO lawsuit against IBM by initiating a community boycott of the company
and its products. They have set up
several
forums to collect evidence to use in the courtroom, and also to discuss
possible community responses.
Comments (7 posted)
OSNews
brings
together KDE and Gnome usability engineers to talk about unifying the
Linux desktop. "
Some users want infinite number of options and
preferences, while others prefer a non-bloated interface where the best
options for them is already decided by the system. Now, we all know that
there is no such thing as the "Perfect UI", but would it be acceptable to
sacrifice certain configurability and... bloat --with the possible outcome
of losing some users-- in order to provide a cleaner interface? Do you
think such a move would simplify things for the user or do little but rob
power from those who know enough to use it?"
Comments (4 posted)
Companies
Here's a Gartner pronouncement
on
Red Hat's future. "
Red Hat holds an enviable position as the
leading Linux distributor, with a wide lead over its next
competitor. However, market dominance in the Linux and open-source
community has a different meaning, because the open-source paradigm
operates by different principles than commercial software."
Comments (none posted)
News.com
looks at Red Hat's plans for a lower-cost version of the Advanced Server product.
"
Red Hat is becoming increasingly aggressive with its high-end Advanced Server software plans, but the company wasn't successful in persuading companies to pay $1,500 to $2,500 per year for a subscription to use the Linux version on low-end servers. The new Enterprise Linux ES product costs $349 or $800 per year, depending on support levels..."
Comments (21 posted)
Business
MidrangeServer.com
looks at
the Linux server market. "
According to statistics compiled by
Gartner's Dataquest research unit, IBM captured 41.6 percent of the $385
million in Linux server sales in the U.S. market alone last year. IBM
hasn't seen market share statistics like that in the server
market--especially in a new market with lots of aggressive players and on
an operating system platform that it does not control--since the
1970s." (Thanks to Martin Rowe)
Comments (none posted)
Linux Adoption
Here's a ZDNet article
looking at Linux growth
in Asia. "
In a survey of IT managers in 12 countries in
Asia-Pacific (except Japan), Linux is installed on a tiny six percent of
servers, computers that organizations that use to run databases or hold
data. But in 2003, this figure set to grow 24 per cent, more than double
the rate of its closest competitor, Unix, which is expected to grow nine
percent."
Comments (none posted)
KDE.News
reports on
the roll-out of 50 Linux-based desktop systems by the German
government.
"
The test 50-seat rollout was spear-headed by the Federal Office for Information Security (BSI) in conjunction with several small German IT companies. The thin-client setup reportedly includes KOffice as the office suite."
Comments (none posted)
Legal
The Register
covers a bill
introduced in the Oregon State Legislature on March 5 by Rep. Phil Barnhart
that will require the state government to consider using open source
software when acquiring new software. "
Rep. Barnhart says, "I am a
long-time lurker on Slashdot, so I have been aware of the [open source]
issue for some time. I've been convinced for a long time that Windows is a
difficult program -- wasteful and expensive." And, he adds, "The little
experience I've had with open source has been very positive.""
Comments (none posted)
This ZDNet article
looks at the DMCA and
how HP and Intel seem to both revile and support the act. "
Last
week, Intel and HP's names appeared on a press release circulated by the
Business Software Alliance (BSA) opposing crucial changes to section 1201
of the DMCA. Specifically, the BSA lashed out at a bill that would make it
legal to bypass copy-protection mechanisms--as long as you're not planning
to circulate the resulting file to tens of thousands of your closest
friends."
Comments (3 posted)
Interviews
ZDNet Germany
talks
with Red Hat chief executive Matthew Szulik about Sun, UnitedLinux and
the battle for the desktop. "
Our biggest task is educating the
marketplace that open-source software is more reliable, more secure and
more affordable. The large proprietary OS software companies will struggle
with the economics and value of the open-source/Red Hat model. We continue
to make significant progress in corporate environments and businesses that
want the reliability and value associated with Red Hat products and
services in comparison to the expensive proprietary alternatives."
Comments (none posted)
Resources
Here's a security conscious Linux Journal article
examining buffer
overflows. "
Buffer overflow problems always have been associated
with security vulnerabilities. In the past, lots of security breaches have
occurred due to buffer overflow. This article attempts to explain what
buffer overflow is, how it can be exploited and what countermeasures can be
taken to avoid it."
Comments (4 posted)
Here's
an
article on the O'Reilly Network on how to test kernel modules in a
multiprocessing environment - even if you do not have an SMP system.
"
Fortunately there is now a method of simulating a SMP system with a
single CPU Linux system. Fantastically, it requires no financial
investment. The tool is Jeff Dike's User Mode Linux (UML)."
Comments (none posted)
LinuxMedNews has published
a list of popular open-source software projects for medicine.
"
Newcomers to the Free and Open Source Software (FOSS) in medicine scene have commented that it is difficult to discern which FOSS projects are the most advanced. At the risk of upsetting many worthy projects and hard-working people I bring the following short list of what I consider to be The Contenders: a United States centric view of those projects and resources that have achieved or are most likely to achieve a critical mass of users, developers and clinical ability. The criteria includes a Free license, a shipping product that is in actual use in real-world situations."
Comments (none posted)
Reviews
eWeek
runs a
beta version of the Six/Four System, new peer-to-peer technology from
Hactivismo. "
An offshoot of the Cult of the Dead Cow hacker group,
Hacktivismo is dedicated to preventing state-sponsored censorship of the
Internet. It created the Six/Four System, which is named for the June 4,
1989, date of the Tiananmen Square massacre, to make it possible to access
information anywhere on the Internet and put a big hole in things like
China's Internet firewall."
Comments (none posted)
The E-Commerce Times
covers
Ruby. "
Although Ruby documentation is still in progress, the
language offers many benefits that might be reason enough for IT managers
to consider using it. Chromatic said that as the new kid on the block,
relatively speaking, Ruby has been able to learn from other
languages. "It's had the chance to borrow the good features and polish some
of the yuckier features. In particular, it's a lot nicer to embed Ruby than
it is Perl.""
Comments (none posted)
Miscellaneous
Vnunet
looks at recent
security vulnerabilities in Sendmail and Snort. "
Last week showed
how quickly news of vulnerabilities can be exploited to produce software
that wreaks havoc on the Net. Within 24 hours of the problems being made
public, an easy-to-use exploit program for the Sendmail vulnerability was
posted on the Bugtraq mailing list. According to Bugtraq, default
installations of Sendmail and Red Hat Linux are not vulnerable to this
particular exploit, but firms that have compiled Sendmail for use with Red
Hat 7.1, 72 or 7.3 are vulnerable."
Comments (none posted)
Page editor: Forrest Cook
Announcements
Non-Commercial announcements
Here's a press release from the UK Campaign for Digital Rights which
examines certain myths that fuel copyright measures such as the European
Copyright Directive 2001/29/EC.
Full Story (comments: 3)
The Python Software Foundation has been recognized by the IRS (the US
office of taxation) as a tax-exempt non-profit foundation (aka 501(c)(3)),
and that the IRS has given the PSF a "favorable advance ruling" on the
PSF's application for recognition as a public charity.
Full Story (comments: none)
Commercial announcements
IBM's web services development lab
has released its Web Services
Software Evaluation Kit.
"
Get a fresh collection of Web services articles
and tutorials on the SEK CDs, and learn about everything from the basics of
SOAP, WSDL, and UDDI, to the latest techologies in the Web Services stack
such as workflow, security, and attachments."
Full Story (comments: none)
O'Reilly has released "Google Hacks", "
a unique collection of one
hundred tips and tools gathered from expert users of Google, as well as
developers who are excited about Google's new API."
Full Story (comments: 1)
Here's a
press release about a company called Mac-Clair Mortgage Corporation.
It seems Mac-Clair and Mortgage Builder Software, Inc. have installed
Mortgage Builder(R) Loan Origination Software (LOS) on Mac-Clair's Linux
system.
Comments (none posted)
MySQL AB has
announced
the launch of its new program for the certification of MySQL managers and
developers. The currently available certification levels relate mostly to
SQL and database management skills; more advanced levels will be offered in
the future.
Comments (none posted)
O'Reilly has released "Python in a Nutshell" by Alex Martelli. "
In
the tradition of O'Reilly's "In a Nutshell" series, this book offers Python
programmers one place to look when they need help remembering or
deciphering the syntax of this open source language and its many
modules. This comprehensive reference guide makes it easy to look up all
the most frequently needed information--not just about the Python language
itself, but also the most frequently used parts of the standard library and
the most important third-party extensions."
Full Story (comments: none)
Resources
Institut für Rechtsfragen der Freien und Open Source Software (ifrOSS) has
published its new license center in English. This is an extesive license
list of Free software/Open Source and Open Content licenses.
Full Story (comments: none)
Upcoming Events
The Gnu Compiler Collection (GCC) Developer's Summit will be held on
May 25-27, 2003 in Ottawa, Canada. A call for papers has been sent
out.
Full Story (comments: none)
Here's
a reminder that CeBIT
2003 starts tomorrow (March 12, 2003), and the KDE team will be there,
showcasing current developments scheduled for KDE 3.2 and more.
Comments (none posted)
Tony Stanco will present O-STEP, the Open Source Threshold Escrow Program,
at the Open Standards/Open Source
in National and Local eGovernment Programs conference in
Washington, D.C. on March 17, 2003.
Full Story (comments: none)
The folks at the OpenOffice.org conference remind you to
register for the conference, it will be held in Hamburg,
Germany on March 20 and 21, 2003.
Full Story (comments: none)
A call for papers has been sent out for the
first AUUG System Administration
symposium, which will be held on April 9th in Melbourne, Australia.
Full Story (comments: none)
The Open Palmtop Integrated Environment (OPIE) team will
be present at the CeBit fair in Hanover, Germany. The event
will be held on March 12-19, 2003.
Full Story (comments: none)
Use Perl
mentions that Mark-Jason Dominus will be providing some Perl
training and discussion in Belfast, Ireland on March 24 and 28, 2003.
Comments (none posted)
LinuxMedNews has
an announcement for the American Medical Informatics Association's
open-source Expo.
"
AMIA is announcing its first ever Open Source Expo for the Fall 2003 conference in Washington, D.C. The expo will occur during the poster session. The call for participation states: '...Suggested items to include in the abstract are brief description of the functionality and scope of the product, the motivation for making the product open source, the development and usage history, how the development was funded, product features, design and implementation details, future directions, and a URL for more information and from where the product may be downloaded...'"
Comments (none posted)
| Date | Event | Location |
| March 13 - 19, 2003 | CeBIT 2003 | (Hannover exhibition center)Hannover, Germany |
| March 13, 2003 | Second Annual Web Services Expo | (iPark Silicon Valley)San Jose, CA |
| March 17 - 19, 2003 | Open Source for National and Local eGovernment Programs in the U.S. and EU | (The Marvin Center Grand Ballroom, George Washington University)Washington, DC |
| March 20 - 21, 2003 | First OpenOffice.org Conference(OOoCon2003) | (University of Hamburg)Hamburg, Germany |
| March 20 - 21, 2003 | Conference PHP 2003 | (École Polytechnique de Montréal)Montreal, Quebec, Canada |
| March 26 - 28, 2003 | PyCon DC 2003 | (George Washington University)Washington DC |
| March 29, 2003 | First Hungarian PHP Conference | Budapest, Hungary |
| March 31 - April 2, 2003 | 2nd USENIX Conference on File and Storage Technologies(FAST '03) | (Cathedral Hill Hotel)San Francisco, CA |
| April 2 - 3, 2003 | The UK Python Conference | (Holiday Inn Oxford)Oxford, England |
| April 5, 2003 | Linux In Education Spring Conference | (Grand Prairie High School)Grand Prairie, Texas |
| April 10 - 12, 2003 | MySQL Users Conference & Expo 2003 | (Doubletree Hotel)San Jose, California |
| April 13 - 17, 2003 | RSA Conference 2003 | (Moscone Center)San Francisco, CA |
| April 14 - 15, 2003 | Samba eXPerience 2003 | (Hotel Freizeit)Göttingen, Germany |
| April 15 - 16, 2003 | LinuxUser & Developer Expo 2003 | Birmingham, UK |
| April 22 - 26, 2003 | Embedded Systems Conference(ESC) | (Moscone Convention Center)San Francisco, CA |
| April 22 - 25, 2003 | The O'Reilly Emerging Technology Conference | (Westin, Santa Clara)Santa Clara, CA |
| April 23 - 25, 2003 | PHPCon East 2003 | (Park Central Hotel)New York, NY |
| April 28 - 30, 2003 | Real World Linux 2003 | (Metro Toronto Convention Centre)Toronto, Canada |
| May 3, 2003 | International Conference on Software Engineering 2003 | Portland, Oregon |
| May 8 - 9, 2003 | International PHP Conference, 2003 | Amsterdam, the Netherlands |
Comments (none posted)
Software announcements
Here are the software announcements, courtesy of
Freshmeat.net. They are available in
two formats:
Comments (none posted)
Miscellaneous
The magazine php|architect
will be awarding
grants for PHP development.
"
php|architect, the monthly magazine for PHP professionals, it proud to announce the launch of the php|architect Grant Program. Its purpose is to provide financial support for the PHP-related open-source projects that have the potential of bringing the greatest benefit to the PHP community in general." Two $1000.00 grants will be awarded on June 30, 2003.
Comments (none posted)
Page editor: Forrest Cook
Letters to the editor
| From: |
| Andy Oram <andyo@oreilly.com> |
| To: |
| letters@lwn.net |
| Subject: |
| Irresponsible SCO |
| Date: |
| Mon, 10 Mar 2003 14:49:56 -0500 (EST) |
I haven't seen much discussion of this in the Linux
community, perhaps because the charges are so vague, but I
thought something meaningful could be said.
Andy
-------
http://www.oreillynet.com/pub/wlg/2889
Reference: http://news.com.com/2100-1016-991622.html
A lot of brickbats are coming the way of SCO since it launched a
lawsuit against IBM on the grounds of trade secrets. What's scandalous
is not the choice to resort to a lawsuit--because companies have to
defend these sorts of things in court in order to preserve their
meaning--but the disregard for the needs of Linux users, developers,
vendors, and watchers everywhere. SCO chose a low road indeed, trying
to maximize its legal flexibility instead of acting like a member of a
community.
Linux supporters are worried about this for good reason. The lawsuit
inevitably recalls the suit AT&T brought against the Berkeley
developers of BSD in the 1980s. Then as now, the issue was that
developers had access to UNIX during the time they developed their own
code. The AT&T complaint involved copyright rather than trade secrets,
but the parallels are unmistakable.
Although my memory may deceive me, I believe AT&T never demonstrated
that a single line of BSD code originated in UNIX (which officially
should be written in all-caps). The lawsuit was resolved after many
years, but a lot of people blame the confusing around the suit for the
stagnation of BSD and its inability to take off at the crucial moment
when people were looking for a free software operating system. (I
doubt that suit was the problem, but it did waste time and make a mess
of things.
AT&T sold its rights to UNIX long ago, apparently recognizing that it
was managing every aspect of that valuable technology with the same
incompetence that it had conducted the BSD lawsuit. As intellectual
property, UNIX bounced around for a while and ended up at SCO. It's
probably no coincidence that SCO decides to act the heavy around this
period when many observers believe UNIX is dying and that Linux will
take over where it stood.
But they know very well what problems and bad feelings the BSD lawsuit
reached. They know how many people (roughly) depend on Linux day by
day. What would a responsible company do to uphold its rights while
allowing the world to continue?
SCO could have examined Linux code and determined where their
purported trade secrets lay. They would then have widely publicized
the disputed code. They'd say, "Don't use JFS" (or whatever it
happened to be); "we're litigating it." Whatever components were in
dispute could quickly be pulled out of the kernel; users could depend
on other components for whatever functionality they needed.
Of course, SCO's lawyers wouldn't tell them to do this. I'm sure the
lawyers want as wide a field to play on as they can get. And it is not
they who will be appalled when play is done and they discover the
whole field has been turned into a desert.
SCO can still overrule its narrow-minded lawyers and take a high road.
If they've got a claim, make it clearly. That is what the public
deserves. Judging from the scattered news reports I've read, they
refused to be specific even in the legal complaint they sent the
court.
And this hand-waving is a tell-tale sign of weakness. We are all
justified in assuming, till we have evidence to the contrary, that
SCO's lawsuit will go the way of the evidence the Bush administration
waved about excitedly for months concerning aluminum tubes purchased
by Iraq, now revealed by weapons inspectors on the ground to bear no
relation to weapons of mass destruction. But millions of users around
the world are in limbo until we know for sure, and there is no reason
for that except malice or hamfistedness on the part of SCO.
Andy Oram
Comments (none posted)
| From: |
| Alex Bennee <alex@bennee.com> |
| To: |
| distro@distrowatch.com |
| Subject: |
| In defence of RPM! |
| Date: |
| 07 Mar 2003 16:00:36 +0000 |
| Cc: |
| letters@lwn.net |
Hi,
I was reading the distrowatch artcile (Is RPM Doomed?
http://www.distrowatch.com/dwres.php?resource=article-rpm) which
contained was a long rant against the incompatabilities of binary RPM's
across distributions. Although the article did point out a few ways
things can be improved I feel as though I must jump in with a little
pro-RPM evengelism :-)
Firstly a quick question. Why is binary compatibility required?
The majority of applications your likely to look at are source based. If
the binary RPM exists then there should .src.rpm nearby. In my
experience 99% of dependancy problems are solved by simply building the
binary RPM yourself. I can't believe your suggesting moving over to a
source based distribution because:
emerge application
saves a few lines over:
rpm --rebuild application.src.rpm
rpm -ivh ~/rpm/RPMS/applictaion.rpm
I'll grant that Gentoo's source based system offers a lot when it comes
to large multi-component builds. However if your really that up for the
bleeding edge you'll find living on Manrake Cooker (or Debian unstable)
costs you less time in the long run than constantly rebuilding common
components.
In fact I run Mandrake Cooker on my main desktop and I've had very few
problems with running a:
urpmi.update -a
urpmi --auto-select
every few days. I can leave the heavy lifting to the Cooker people and
concentrate on the apps I'm actually interested in.
But arguments about ease of building asside the biggest difference rpm
makes to my life is knowing where all the files on my PC come from.
Having in the past lived/survived a windows environment where your never
quite sure if a DLL is left over detruitus or an essential system
component I find the ability to do a:
rpm -qf /usr/bin/randomfile
a godsend. As a bonus I know if I un-install a package from my system
all its files go with it leaving nothing lying around.
As I have consistently found with open source tools its easy to get
frustrated at percieved inadaquacies at first but if you invest a little
time reading the documentation/playing with the app your experience is
drastically improved and you'll wonder how you got along without it.
Briefly returning to the problems of people who distribute binary only
rpm's (of which is concern mainly to the commercial software people)
there is a solution. Build your binary RPM's for the big 3 (RedHat,
Mandrake, UnitedLinux) and build a forth statically linked RPM for the
rest.
Regards,
--
Alex, homepage: http://www.bennee.com/~alex/
Everyone is a genius. It's just that some people are too stupid to realize it.
Comments (1 posted)
Page editor: Jonathan Corbet