Search Results: "ag"

5 April 2008

Francois Marier: Encrypted swap partition on Debian/Ubuntu

The swap partition can hold a lot of unencrypted confidential information and the fact that it persists after shutting down the computer can be a problem.

Encrypting a swap partition however is slightly tricky if one wants to also support suspend-to-disk (also called hibernation). Here's a procedure that worked for me on both Debian Lenny and Ubuntu 7.10 (Gutsy Gibbon):

0- Install the cryptsetup package:
apt-get install cryptsetup
1- Setup the encrypted partition as root:
swapoff -a
cryptsetup -h sha256 -c aes-cbc-essiv:sha256 -s 256 luksFormat /dev/hda2
cryptsetup luksOpen /dev/hda2 cswap
mkswap /dev/mapper/cswap
2- Add this line to /etc/crypttab:
cswap /dev/hda2 none swap,luks,timeout=30
3- Set the swap partition to be this in /etc/fstab:
/dev/mapper/cswap none swap sw 0 0
4- Configure uswsusp to use /dev/mapper/cswap and write unencrypted data
dpkg-reconfigure -plow uswsusp
You will of course want to replace /dev/hda2 with the partition that currently holds your unencrypted swap.

(This is loosely based on a similar procedure for Ubuntu 6.10.)

Francois Marier: Searching through the contents of emails in mutt

Mutt has a built-in feature for search the body of emails in the current mailbox (see ESC-b) but it's also possible to make this extremely fast by plugging-in external tools. Here's a quick description of my mairix setup.

After installing the package,
apt-get install mairix
create a .mairixrc in your home directory containing something like:
base=/home/username/Mail
maildir=inbox:archives*:sent*
mbox=debian*:jokes
mfolder=search
database=/home/username/Mail/.mairix_database
(This assumes that you store your mail in ~/Mail and that you want the search results in a new ~/Mail/search maildir folder.)

Then you need to run mairix once to index all of your emails:
mairix
which you will of course want to run regularly. I created this cronjob in /etc/cron.d/mairix-username:
17,37,57 * * * * username /usr/bin/on_ac_power && /usr/bin/mairix
(To avoid waking up the hard drive needlessly, I prefer to restrict the indexing runs for when I'm running on AC power. Take that out if you're not running it on a laptop.)

Finally, the last bit of setup is in ~/.muttrc:
macro index \eb 'c=search'<enter><shell-escape>'mairix ' 'Enter Mairix search term'
which makes mairix take over the ESC-b shortcut.

If you use GPG, you should also add this to your ~/.muttrc to make sure that mairix can see all of your messages by saving them as clear text:
set fcc_clear=yes
bind index s decrypt-save
bind pager s decrypt-save

Yves-Alexis Perez: Printing (reloaded)

In the end, I just bought a Brother HL-5250DN. Yeah I know, it wasn't in the list, but in the end, the lexmark one (which had postcript+duplex) wasn't available at a nice price, but I thought duplex printing was still a good idea. So I had to decide between a Samsung and a Brother. The Samsung had official Postscript while the Brother supported IPv6. I ended choosing the Brother one, and it's a good idea. The printer indeed support IPv6, but postscript too. Choosing “Postscript generic driver” in cups works pretty fine. IPv6 works too, but I faced two (linked) problems: Another problem in cup is that it doesn't support IPv6-only mDNS. With use-ipv4=no in /etc/avahi/avahi-daemon.conf, no printer can be found. This is #474464, waiting for the maintainer to comment. At least, it works fine on Linux. Now I'll make some tests on OS X and maybe windows.

Pierre Habouzit: [RC-Bug-A-Day] Day 18

Paid work burnt all my free time recenlty, that's why there wasn't a rc-bug-a-day for two days. I'm back with two removals, a couple of gcc-4.3 FTBFSes fixed. And 5 uploads for RG bugs from Sandro Tosi that were rotting in my mail client. The bad news for tonight is that gcc-4.3 FTBFSes are now RC, since it's the default compiler on several architectures. That's almost 40 new RC we now have to deal with. The fun part will be that those RC will probably hinder some transitions to testing. Maintainers, please, fix your packages. There are still too many packages with RG bugs on them, open for many days, from maintainer that are otherwise quite active on IRC or the lists

Norbert Tretkowski: MySQL plugins in Debian

MySQL 5.1 and up supports a plugin interface that allows the loading and unloading of server components at runtime, without restarting the server. Today I started working on a mysql-storage-engines package for MySQL 5.1 in Debian, which includes the PrimeBase XT and Sphinx storage engines. I currently don't plan to create separate binary packages (like mysql-engine-pbxt and mysql-engine-sphinx) for every single plugin.

Suggestions for additional plugins which should be added are welcome.

Adam Rosi-Kessel: Is Axe Flix a Scam? (Or What Is Axe Flix? )

I received a glossy mass mailing today from “Axe Flix,” enclosing a DVD for a film supposedly entitled “A Diary.” (I haven’t loaded the DVD). The promotional copy:
AXE FLIX Did the resounding climax merit a four-hottie rating? Do the action scenes provoke a second go-around? Or did the ending leave her wanting just a little bit more? Be a critic. Rate this movie and you could WIN a year’s supply of Axe.
The whole thing seems suspicious. In my experience, most unsavory operations quickly come to light as such with a Google search. Oddly, there is only one result in a Google search for “Axe Flix”, and it’s not relevant. There is also no IMDB Entry for a movie called “A Diary,” nor do the named actors (Suzanne Knack, Patrick Kelly, Max Lenderman, Alexis Karsant, Jamie Butts, Chad Anderson) show up as real actors. It purports to be based on a best selling novel by “Robert Walker.” Also no dice. Can something possibly be real in this era without significant confirmation of its existence in Google? I think not. Ontology recapitulates search engine optimization. I’m writing this entry to create an anchor for future discussion. Does anyone have any idea what this is? The return address for “contest entries,” “Axe Spread the Love Sweepstakes, P.O. Box 511425, New Berlin, WI 53151,” also doesn’t provide many clues, other than possibly some relationship with toilet paper. Technorati Tags: , Update: it took all of thirty seconds for this entry to appear as the first result for several related Google searches, and another thirty seconds for me to get my first comment from someone else with the same question. Update 2: Based on discussion in the comments below, I seem to have unintentionally “fed the troll.” Maybe I wouldn’t have walked smack into this if I had heard of this product before. I guess this is my punishment for not having a cable or broadcast TV connection.

Steve Kemp: You know how to use candles?

Mutt
Fran ois Marier has recently been posting some interesting entries about the Mutt mail client upon his blog. His tips are pretty basic, but that doesn't make them less useful. So here's my tip of the day: reply_regexp. When you're viewing a mail, and you choose to reply it the subject of that mail is the basis of your message's subject. For example given a message with "Subject: hello" your reply will typically have the subject "Subject: Re: hello". This is real rocket science here, people. Imagine you're using SPAM filtering which tags messages it isn't sure about with a prefix "UNS:". Suddenly things don't look so hot, as you might end up with a mail with the subject:
Subject: UNS: Re: Hello
Reply to that mail, whilst being half-asleep, and what do you get? You get this:
Subject: Re: UNS: Re: Hello
Bad. Ugly. Wrong. The following snippet in my ~/.muttrc file correctly deals with this case:
set reply_regexp="^(((UNS:[ \t]) [rR][eE]:[ \t])*)+"
Neat. Cool. Nice.
Advertising
I've paid for some advertising upon the LWN.net site. (No link, I'm not trying to game things here.) I didn't know what to expect, but I was willing to risk the expenditure as a way of saying thanks to them for their great content. (Because of my Debian Project membership I get a free LWN subscription, as do all developers. see here for details if you're a developer without a subscription.) I've paid $30 and that has given me a months run of my advert, with clickthroughs hovering around 1%. Not horribly bad at all! I probably won't repeat the experiment for the forseeable future, but I'm glad that I did it at least once. If you have something appropriate for a Debian-based audience don't forget you're welcome to advertise upon the Debian Administration website for free - See the Advert FAQ for details.
ObQuote: The Craft Update: jquery was accepted yesterday. Today I uploaded a new version to more closely align it with the javascript-policy.

Daniel Burrows: aptitude 0.4.11.1 released

Last weekend, I released version 0.4.11.1 of the aptitude package manager (release notes). This is a minor release focusing mostly on bug-fixes and on a few features that I've been meaning to add but that didn't make it into 0.4.11. I think the most interesting addition is --show-why, which is like --show-deps but traces back to the closest manually installed package. In some wide-character locales, the fix for bug #472625 in this upload of aptitude triggers bug #473874 and bug #474065 in apt; the symptoms are an error message about line N too long (max 1024) on start-up, and messages saying that method http has died unexpectedly! when you try to update the package lists or install new packages. I've written patches to fix these bugs in apt, and once they're reviewed by the other apt maintainers they should be fixed in the next upload of apt (version 0.7.12). Until then, if you're bitten by this bug, you can work around it by diverting /usr/share/aptitude/aptitude-defaults.$LANG and replacing it with an empty file. For instance, for Russian (ru):
 # dpkg-divert --rename --local --divert /usr/share/aptitude/aptitude-defaults.ru.real --add /usr/share/aptitude/aptitude-defaults.ru
 # echo > /usr/share/aptitude/aptitude-defaults.ru
Once a fixed apt is uploaded, you can remove the diversion like this:
 # rm /usr/share/aptitude/aptitude-defaults.ru
 # dpkg-divert --rename --local --remove /usr/share/aptitude/aptitude-defaults.ru

Yves-Alexis Perez: Printing

I'm currently looking for a printer. I want a Laser printer, black & white should be enough, but color may be ok too if not too expensive (especially toner). I guess I prefer a network one, even if I don't really understand the way everything should work. As I understand it, a network printer just listens on a defined port (9100/jetdirect or ipp/63), and prints jobs sent by a spooler. There is no integrated spooler, so there are two solutions: Maybe I shouldn't buy a network printer and just pick a usb one (especially since the FreeboxHD can serve as a laser printer if one plugs a usb printer on it. It listens on 9100/jetdirect so one can configure cups to pick it). I've currently narrowed my choices to: Moe on #xfce avised me to pick a printer a bit more expensive, because it would be safer on a long term, and advised: I don't really know what to do so, dear lazyweb, I'm asking you. What should I pick? This is for a home installation where we don't really print that often, so I don't want to spend too much, but where goodies like network and duplex printing are cool to have. Cups support is mandatory (except if there's another way to print easily, especially from gtk apps)

Christian Perrier: The spirit of FLOSS development

There are things that are unique in FLOSS development:
Author: nekral-guest
Date: 2008-04-04 19:43:33 +0000 (Fri, 04 Apr 2008)
New Revision: 1966
Modified:
   debian/trunk/Makefile
Log:
Add a cheesy check.
Modified: debian/trunk/Makefile
===================================================================
--- debian/trunk/Makefile       2008-04-04 18:50:22 UTC (rev 1965)
+++ debian/trunk/Makefile       2008-04-04 19:43:33 UTC (rev 1966)
@@ -1,4 +1,16 @@
 PKG=shadow
 SITE=ftp://pkg-shadow.alioth.debian.org/pub/pkg-shadow/
+deb:: check_cheese
+
 include /usr/share/quilt/quilt.debbuild.mk
+
+check_cheese:
+       @dpkg-parsechangelog   grep -q "\* The \".*\" release\."     \
+               echo ""; \
+               echo " **                                  **"; \
+               echo " **  Warning: not a cheesy release!  **"; \
+               echo " **                                  **"; \
+               echo ""; \
+               exit 1; \
+        
Summary: releases of the Debian shadow package all have the name of a French AOC cheese since July 2005. Nicolas, who was focused on a new upstrram release of shadow inadvertently forgot to add such name for the 4.1.1-1 release and thus added a failure of the package build process in case on forgets the cheese name. We should however give NMUers instructions about the right way to NMU the package, such as giving the name of a local cheese.

4 April 2008

Christian Perrier: Aha...

That one could make the day of all maintainers who got REJECTED packages because of loose copyright information:
W: dak: copyright-without-copyright-notice
Maintainer: Joerg Jaspert 
No offense intended to Joerg, of course, who does tremendous work in the project...just some small pun..:-) Indeed, we have hundreds of packages in the archive which are missing that information, nearly always mixing *copyright* information with *licence* information. And the lintian warning is fairly recent, which explains that dak (who needs love.....the package in the archive doesn't contain the *real* dak scripts that are used on Debian machines) is reported with that warning.

Gintautas Miliauskas: The meaning of code

I had an "Aha!" moment today when I came to a Wittgensteinian realization that while the sense of a piece of code corresponds to the formal behaviour of that code, the meaning of the snippet is the set of possible contexts where this code could be used. This idea has changed my view of teaching programming (I have been teaching Python in a local school for a couple months now). This attitude is nothing new, but for some reason I have not come across it, or rather, I have never seen it applied. (The fashionable problem-based learning thing has some similarities, but isn't quite it.) Having an idea to start from, it was not hard to find good articles expanding the idea. I especially liked Robert Strandh's short writeup on idioms and Elliot Soloway's Learning To Program = Learning To Construct Mechanisms And Explanations (1986). Experienced programmers will not learn much, but anyone dealing with CS education, teachers and students alike, ought to have a look. The moral is that emphasis should be placed on reading exemplary code ("experienced programmers do X this way") rather than definitions ("function Y does Z"). Programming seems to be closer to language use than to mathematics, and teaching methods should reflect that.

Gunnar Wolf: Vote casted!

Some readers might not now that Debian is in this annual process where we vote for our Leader for the following next year.
I just submitted my vote.
I think it is worth mention that this year there is very little discussion on this subject among DDs. Also, I've practically seen nobody publicly posting their votes or preferences, as it is usual (well, usually we get maybe 10 votes posted to the planet or the different lists).
It must be related to the fact that this year we have neither a candidate or quasi-candidate who raises passions for or against (as the two last years), nor there are very significant differences between the three candidates. They are all quite OK, IMHO, uncontroversial.
This years' elections will probably be the first (at least, since I was accepted in the project) where no candidate is ranked below None of the above. And that, I think, is a good sign. It might be more boring, but shows maturity ;-) And yes, it also shows off good work from our current (and active, and much loved) leader, Sam.
...And yes, I'm not posting my vote either. As things are, the platforms/rebuttals/debate did shape my vote a bit, but the main differentiator ended up being... My personal relationship and opinion towards each of them.

Sylvain Le Gall: OpenOffice.org fonts too big in XFCE

UI fonts of OpenOffice.org Writer and XFCE thunar are really not the same ... years of seeing this ugly font and being force to scale the OpenOffice.org UI display to 80%. I just found the solution! All his related to a X settings: Xft.dpi. People are suggesting around to set it to 96 or something like that. I just decide to use the one i can find xdpyinfo (does it make sense?) and send the result to X settings using xrbd. Here is the script $HOME/bin/xfce4-xft.sh:
#!/bin/sh
xrdb -query Xft.dpi   grep Xft.dpi > /dev/null && exit 0
RESOLUTION= xdpyinfo   grep resolution   sed "s/.* \\([0-9][0-9]*\\)x.*/\\1/" 
TMP= mktemp 
trap "rm -f $TMP" EXIT
echo "Xft.dpi: $RESOLUTION" > $TMP
xrdb -merge $TMP
Copy/paste/chmod a+x this file. And then add a file $HOME/.config/autostart/xfce4-xft.desktop to autostart the previous script:
[Desktop Entry]
Encoding=UTF-8
Type=Application
Name=XFCE-XFT
Comment=Fix XFCE Xft.dpi settings
Exec=/home/gildor/bin/xfce4-xft.sh
StartupNotify=false
Terminal=false
Hidden=false
(replace /home/gildor/ by your own home directory) Thats it. Your Xft.dpi will be fixed depending on the configuration of your X server. This allow you to have a laptop and a desktop with different screen resolution. I am waiting the email from bugzilla.xfce.org to submit this script to XFCE bug tracking. Enjoy. Update: Following the comment of this entry, another better solution is to use openoffice.org-gtk which works out-of-the-box with a clean UI. I don't even have to force OO to gnome style. Thanks to Dan Callahan, Vasilis and Corsac for their suggestion.

Rob Bradford: Blood, Sweat and Tea on the radio

I’ve just finished listening to the broadcast of a radio play based on Blood, Sweat and Tea a collection of posts from by favourite blog Random Acts of Reality. Random Acts is written by “Tom Reynolds” (a pseudonym) an EMT with the London Ambulance service. I guess I enjoy reading this blog so much because it shows an insight into the lives of members of an essential but very much unappreciated occupation. Well worth adding to your daily blog intake. Direct listen again link. Playing in the browser is all garbled :-/

Neil Williams: HP laptop repaired (and wireless)!

OK, after a mainboard replacement by HP, I have my AMD64 HP Pavilion DV6000 (DV6615ea) back and a quick update has given me working wireless! The last remaining obstacle has gone - the most recent 2.6.24 kernel update includes working support for the Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02) in the b43 kernel driver.
a little tip
When connecting this laptop to the mains for a recharge, plug into the mains before connecting the mains lead to the laptop itself. I have a strong suspicion (but it is no more than that) the repair was caused by a power spike from a dodgy extension cable. Plugging into the extension without the other end being connected to the laptop isolates such spikes.
Necessary support
$ uname -a
Linux dwarf 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64 GNU/Linux

 $ dpkg -l 'linux-image-2.6*'
linux-image-2.6-amd64 2.6.24+13
linux-image-2.6.24-1-amd64 2.6.24-5

Wireless config
The first dmesg output showed a useful tip:
Apr  4 20:07:06 dwarf kernel: b43-phy0 ERROR: 
YOUR FIRMWARE IS TOO NEW. Please downgrade your firmware.
Apr 4 20:07:06 dwarf kernel: b43-phy0 ERROR:
Use this firmware tarball: http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
Apr 4 20:07:06 dwarf kernel: b43-phy0 ERROR:
Use this b43-fwcutter tarball: http://bu3sch.de/b43/fwcutter/b43-fwcutter-009.tar.bz2
Apr 4 20:07:06 dwarf kernel: b43-phy0 ERROR: Read, understand and _do_ what this message says, please.

Unpack the b43-fwcutter and call make. Execute ./b43-fwcutter ../broadcom-wl-4.80.53.0/kmod/wl_apsta.o, remove any existing firmware in /lib/firmware/b43/ and replace it with the content created by b43-fwcutter.
Reboot to load the updated firmware into the kernel and your amber wireless light will flash blue. sudo iwlist scan then shows the available access points and network-manager is able to connect without problems.
I'm posting this from the HP laptop over wireless.
Summary: this laptop should be eminently supportable in Lenny
After all my doubts and all the hassle, providing you use 'noapic nolapic' and the support of the Debian-Installer for Lenny.

Manoj Srivastava: Manoj: Schemes for packaging using Git: An analysis

Are you rebasing or merging? seems to be the 64 thousand dollar question over in vcs-pkg discussions. Various people have offered their preferences, and indeed, several case studies of work flows have been presented, what is lacking is an analysis of the work-flow; an exploration of which methodology has advantages, and whether there are scenarios in which the other work flow would have been better. Oh, what are all these work flows about, you ask? Most of the issues with packaging software for distributions have a few things in common: there is a mainline or upstream source of development. There are zero or more independent lines of development or ongoing bug fixes that are to be managed. And then there is the tree from which the distribution package is to be built. All this talk about packaging software work flows is how to best manage asynchronous development upstream and in the independent lines of development, and how to create a coherent, debuggable, integrated tree from which to build the distributions package. The rebasing question goes to the heart of how to handle the independent lines of development using git; since these lines of development are based off the main line of development, and must be periodically synchronized. Here is a first look at a couple of important factors that will have bearing on that question, and packaging software for a distribution using Git in general. This is heavily geared towards git (nothing else does rebases so easily, I think), but some of the concepts should be generic. I am not considering the stacked set of quilt patches source controlled with Git in this article (I don t understand that model well enough to do an analysis) As a teaser, there is a third answer: neither. You can just add an independent line of development, and just let it sit: don t rebase, and don t merge; and in some circumstances that is a winning strategy.

Julian Andres Klode: debimg 0.0.3 - the checksum - released


Dear readers, The third release of debimg is available now: 0.0.3 Get the tarball: http://alioth.debian.org/~jak-guest/debimg_0.0.3.tar.gz
Verify it: http://alioth.debian.org/~jak-guest/debimg_0.0.3.tar.gz.asc
The ChangeLog: http://alioth.debian.org/~jak-guest/ChangeLog-0.0.3 Clone git repo: git://git.debian.org/git/users/jak-guest/debimg.git
Browse the repo: http://git.debian.org/?p=users/jak-guest/debimg.git More Information: http://wiki.debian.org/DebImg
Daily images: http://jak-linux.org/cdimage/daily-builds/testing/
    About debimg debimg is a software designed to replace debian-cd, written in Python, and
    supporting the creation of single disks for the i386 and amd64 architectures. debimg is of course free software and licensed under the terms of the GNU
    General Public License 3 or (at your option) any later version. About “the checksum” This release is called “the checksum”, because the software knows
    the MD5SUM, SHA1SUM and SHA256SUM of every file on the disk. News
    • Introduction of the media module
      • Add md5sum.txt and sha1sum.txt to the image
      • NEW OPTION: JigdoMap, see the config file
      • Lot of code cleanup
    • Support for custom installer images
      • Modify InstallerImages to an url supported by apt
    • Renamed most options in the configuration file for better
      readability
    • debimg requires Python 2.5, as it uses the with statement.
    Description of the Release This release of debimg introduces the media module with its classes
    MediaFile, BaseMedia and DebianMedia. The MediaFile class contains information about a file.
    It contains the absolute path to the file on the filesystem,
    the path on the media, its size, md5sum, sha1sum and sha256sum. The BaseMedia class provides methods to add files to the
    image, open files on it, and creating the final image. It also
    provides methods to create the files md5sum.txt and sha1sum.txt,
    and methods to support Jigdo file creation. The DebianMedia class provides methods to add packages to
    the image, creating Release and Packages files for dists. Quick start To get started with debimg, get the tarball and extract it to
    some directory. Now, open the file debimg.cfg and change the option Mirror to the URL
    of your preferred mirror. This mirror may be any kind of mirror supported by
    apt, but if you use file:/ they have to be on the same mountpoint, as the files
    are hardlinked. (use copy:/ to get them copied). Now, run ./debimg debimg.cfg. This will create an ISO image named
    debian-lenny-i386-netinst.iso. This image is a normal netinst (except for
    missing documentation and some other small things), and contains the Lenny d-i. To change more settings, take a look at debimg.cfg. Future
    • Cleanup of the configuration format (almost finished)
    • Support for splitting disks
      • Introduction of MediaSet class
      • Changes to the lists required
    • Add documentation to the disks
    • Support for PowerPC
    • Create Debian package (almost finished)
    Another interesting feature will be the libisofs [0] support provided by
    the python-libisofs extension, which is currently under development. [1] Previous release announcements Links

    Christian Perrier: My name is...

    ...Christian, but you can use 'bubulle' if you like, provided you pronounce it properly, ie the French way (b b l'). This is actually what most French(-speaking) DDs do. There is a special exception for Amaya, who uses "boubouy " in her Sprenchglish. I am proud of "bubulle", indeed. The nickname was given to me in the old days of BBS and *very* early Linux development in France, by Ren Cougnenc, *the* French Linux zealot of these years (and translator of a huge number of books/HOWTO/documentations). Ren , who I always dedicate my talks to, found it on a night in a bar back in...1990 or 1991, when we were getting heavily drunk with a few fellow friends, some of which became FreeBSD committers later (there is probably a link somewhere). "bulle" means "bubble" in French and you find bubbles in Perrier water....on the other hand "bubulle" is the name of the goldfish of Gaston Lagaffe, a pretty famous comic character from Belgian cartoonist Andr Franquin. Linking the two lead to "bubulle" which I never left, particularly since Ren decided to leave that world in July 1996. So, feel free to call me "bubulle" and when doing so, drink a pint to the memory of Ren . Late addition: I just found the very last electronic contribution Ren sent me (in newsgroups). For those who read French, this is really typical Ren -ish.

    William Pitcock: Litigation vs. Innovation - further reflection on the state of SCO UnixWare, and what it could have been

    In my previous satire about SCO UnixWare, some SCO people of course didn’t think it was very nice. So, I guess I need to explain more about why I wrote the “review” the way I did. But, first the comment: SCO comments back! Obviously any human being can recognize satire. There is obvious motivation on behalf of SCO’s PR department (correct me if I am wrong on where this comment originated; I did just some basic Google lookups, and also, this is a PR tactic known as “dead agenting”) to ignore the fact that this was clearly a satirical review. I would say, “perhaps SCO doesn’t understand why it is criticized,” but I believe it is obvious that they know why people are being critical and satirical of their company and their efforts. I would like for everyone to think, for a moment, about how things could be if SCO didn’t take the litigious strategy that they have taken over the past 6 years. SCO UnixWare could have remained a successful product, and could have in reality become a major asset to the open source world. SCO could have been the good guys here, but instead they chose a path of litigation instead of innovation. In the Open Source and Free Software world, innovation is what is seen as important. Companies may be in some sense rival to each other, but when it comes down to it, everyone appreciates and respects the work that everyone else contributes to the ecosystem. When people do not contribute in a positive way, or worse, betray their peers like SCO has done, it opens them up for criticism. As I see the situation, I think that SCO’s current tactics as a company represent those of someone who is paranoid. People who are paranoid attack first, instead of defend their position. So, while I am sure this is a pointless question, I believe it must be asked anyway: “What would SCO UnixWare have been like if they did not take a litigious strategy against Linux users?” If you look at it like this, it doesn’t really matter if we’re right, or SCO is right on who has the basic cases (well, it does, but we all know how that’s going to come out anyway). Why does SCO keep pursuing a strategy of litigation when the feasibility of this strategy is at best, unknown? To some extent, I think it is now a matter of morale. After all, it’s bad if you have to admit that the strategy you have taken for the last six years, was wrong. In some ways, you could say that SCO’s current strategy is cult-like. Furthermore, if any SCO people are interested in doing an interview about this whole matter, I encourage you to comment back, and I’ll be happy to publicize SCO’s viewpoint of this. It’s only fair.

    Next.

    Previous.