turbotas.co.uk

Time for a quick progress report. The pit is already taking shape: Perhaps there is a record for the quickest ‘pit build ever? Alas, I suspect that the mechanical bit, the actual body, is the easy part!

After 4 trips to the DIY Shop, the main frame of the cockpit is complete! Both the port and starboard ribs are in place and the runners are in place too.The port cockpit inner top side is fitted and drying as we speak. Some rework was needed to make the side fit: in the original design the inner curve was too tight for the hardboard to follow, even when pre-bent and it kept jumping off.

Assuming the wood supplies hold out, the next seven days should see the fitting of the remaining inner skin, the cutting and screwing in of the internal panels, the fitting of the seat and initial marking for the perspex panels themselves. In slower time, the design of the front nose cabin section will begin. This section can house the two PC’s. Slow time can’t be too slow though: the front windshield design relies on a completed cabinet!

Tomorrow should also see the fitting of the dowels to make the sides properly removeable. If this works okay, things can continue with the outer skin. Presently the sides are held in place with large woodscrews to stop them moving during construction.

Roy Coates has kindly agreed to take some detailed shots from the interior of his own ‘pit, so this will help enormously.

Ideally, I’d like to get everything done with just one Hagstrom controller, so things will be a bit tight on the number of switches: I’m wondering if the Hagstrom supports common anode design so that I can flick PC1 and PC2 common keys with a SELect switch.

Judging from the strength of the sides, I would have said that the general construction has worked really well: MDF ribs with Pine and MDF Runners. In general, it’s just glue holding it all together: screws are only used in critical locations.

Okay, I got around to getting some wood bought. The door in the port side is cut and I’ve just about completed the stringers: see the gallery for shots!

The pit is now turned around ready for me to start the starboard side on Friday afternoon. I’m hoping that the starboard side will be much faster to build now that I’ve done the head scratching once already!

I’ve made some progress on the electronics: I’ve examined the Farnell, RS and Maplin sites for switches etc. RS and Farnell have huge ranges, Interestingly, too large to really browse: Must get hard copy of RS catalogue!

Maplin has a small product range, but this makes it easy to flick through. It looks like the switches alone for this project will come out to about £150. Ouch!

Roy Coates very kindly agreed to give me the details for his panel layouts, so I’m hoping to get some work done on the layout over the weekend.

I’m also planning on buying a stick and rudder: until I get these there are critical measurements in the pit that I don’t know.

Much shopping still to do! Computer rooom is slowly being tidied up: I’ve got no room for anything now! Skipping old stuff. Is January too early for a spring clean?

Bruce Perens has published the following article, Is reproduced here on TurboTas in full, from the version on NewsForge.

January 26, 2004, a new virus became rampant. I have reports that the virus payload has two purposes: to send an email spam for a mail-order “Viagra” vendor, and to perform a denial-of-service attack on SCO’s web site.Denial-of-service attacks via virus have been a common trick of email spammers. They were first used to take out some of the anti-spam blacklist sites. Several of those sites had their (non-spam-related) business so heavily disrupted that they closed the doors of their anti-spam projects rather than be attacked again.

The Open Source developers are a target of spammers. We are the creators of most high-profile anti-spam technology. For example, SpamAssassin started out as, and remains today, an Open Source project. The predominant mail delivery programs of the Internet are Open Source projects such as Sendmail and Postfix, and thus most efforts to spam-proof those programs are Open Source as well. This is important, because it gives spammers a reason to defame us.

SCO also has a reason to defame us, as part of their stock-kiting scheme. We have assembled ample evidence that they have lied under oath in court. Such a company would not balk at attacking their own site in order to paint their opponents in a bad light.

Thus, it is likely that this virus has been assembled for the purpose of defaming the Linux developers by spammers, SCO, or others. Your behavior will influence whether or not it succeeds in this mission.

Thus, I urge all persons who have sympathy for Free Software, Open Source, and Linux:

• Do not cheer on attacks on the SCO site. By doing so, you falsely implicate our community in the attacks, in the eyes of outsiders who read your words. Our community believes in freedom of speech, not silencing our opponent’s speech through net attacks. We will defeat SCO using the truth, not by gagging them.
• Publicly deplore the attacks as an attempt to defame us, and not an effort of our community. Show others this notice.
• Continue to fight SCO, using all legal means at your disposal. Show others the analysis of SCO’s ongoing fraud at Groklaw.net and elsewhere, and explain to them your own experience as a participant in the Free Software community.
• Continue the visible presence of Free Software as a force for good in the world by producing excellent original software for everyone’s free use and deploying it wherever possible. Promote these projects to the press and public as you carry them out. Do what you can for other public-good projects such as schools and non-profit organizations. FreeGeek.org is an excellent example of how to carry this out.
• Show others by example that our side always takes the high road. When they see a low-road sort of action like denial-of-service, spam, or stock fraud, they’ll know who to blame.

Remember that your actions count. You are ambassadors of our community.

Many Thanks

The master version of this notice is at http://perens.com/Articles/SCO/DOS/. Please check that location for a more recent version. You may re-publish this material. You may excerpt it, reformat it and translate it as necessary for your presentation. You may not edit it to deliberately misrepresent my opinion.

Build day 3 and the pit is now starting to take shape: the day was taken up with cutting, sanding and fitting ribs for the left hand side of the fuselage. As the finished pit will not be that strong, I’ve decided to use a feature from the original design and include a door.

Although this does aid entry and egress it also makes the construction significantly more complex and build time will be longer.

As I’ve run out of wood, the right Fuselage side will have to wait. Also, I can’t do much more until the front cabinet design is finalised: the fuselage sides need to have the correct taper at the front and I can’t get this without the cabinet.

The front cabinet in the example build houses two PC’s but I want mine to hold perhaps 4 (3 visual and 1 gauge), so the cab needs to be big enough for 4 small desktops.

Probably a visit to the timber yard is next, then bring the right side up to the build state of the left, then cut the doors. If I can catch up on the right side and cut the doors by the weekend, I’ll be really happy!

On the misc side I’ve started some WIKI pages on the main site to start thinking about what I need to do. Hardly project management 😉

TurboTas 2004

Okay, build day 2 began with a visit to my local DIY centre where, for the princly sum of £70, I procured enough wood for the first part of the build, the center console and side panel shells.

In common with other designs, the pit needs to be dismantleable: This is mainly due to being somewhat larger than a doorway!

To fit this requirement the pit will split into 4 main pieces: The front ‘nose’ will be a cabinet to hold the PC’s that run the sim. Next is the main pit that forms a 61cm wide section with the center console, the seat and the back. The other two major parts will be the sides: these semi-cylinders attach to the sides of the pit to enclose it and give more panelspace for dials, stick and throttle.

There are some smaller ancillary parts: a canopy, the front screen and the rear headrest, but these will follow much later in the build.

The rest of day two was used laying out the floor, measuring and cutting MDF and then building the centre console The gallery has all the piccies.

Using the previously mentioned pit as an example, and with the help of my two residential carers, I sat myself on the proposed SimPit seat (Ex WAB) and we began measuring me.

Sounds daft I know, but when presented with a blank sheet of paper and you are designing an aircraft cockpit, it rapidly becomes really important that you can see out the windscreen and that you can reach the pedals and switches!

The effort here cannot be understated and halfway through the helpers got fed up and went back to their other assigned tasks.

Design Stage 2 instead then: IO mechanism. Its unfortunate that the market leader here is so expensive. No-one argues that EPIC controllers are the best way to go.

Unfortunately, there is no way that my budget would stretch to this so another solution was needed. Also to add weight against the EPIC, it’s not clear how many sims support it so we need something a bit more generic. Enter the Hagstrom.

Hagstrom Electronics sell a Keyboard controller card which sits between the real keyboard and the PS2 connector on the PC. The device supports up to 72 switches and can play macros and switch/on switch/off events. The card costs about $120 plus shipping, so the cost per switched input is pretty low.

Now that the design is very much a generic cockpit for a single seater craft, such as a fighter for example, I have discarded the idea of buying hideously expensive switches.

Instead, my local electronics online catalogue is the ideal place for a whole bunch of generic toggle switches which won’t cost an arm and a leg.

TurboTas 2004

I’ve been ooing and ahhhing for years now at the excellent quality of some of the home built Sim cockpits out there. Clearly there are people dedicating serious time and money to their sim experiences.

It’s always been an ambition to do a similar project and for the last couple of months I’ve been hoarding pictures of the A380: My idea being that It’would be a really good ‘pit to build if I should eventually get around to it.

The trouble is that not only are scale/detail pictures hard to come but also the pit is full of (expensive) LCD Panels.

Work is a bit slow at the moment, so in the last couple of weeks I started looking in earnest again at the ‘pit build idea.

After discarding the A380 idea as technically difficult, very expensive, not to mention too big for the only available room in the house, I looked for something smaller.

Next on the ‘hit list’ was Scaled Composites SpaceShipOne. This was, I think, an inspired idea, but it too quickly fell by the wayside: Hard to build due to compound curves and inability to run generic games with it (fully enclosed cockpit with portholes). Also Scaled were unable to assist with cockpit layout etc.

I’ve always been worried about the cost of such an endeavour, particulary when reading about the exploits of builders trying to find exact matches for particular knobs and dials etc. Coupled with this: the infamous EPIC cards cost quite literally an arm and a leg.

With this in mind I found an excellent picture reference of a generic build and not only is it a good design but also it makes use of a far cheaper IO mechanism than EPIC.

Finally then, this design has inspired me to have a go.

Expect more news soon on this topic!

TurboTas 2004

Probably the best summary piece I’ve read on the SCO story and it comes not only from a non-IT magazine, but from a business magazine in Utah, great….

Here are the first few lines, please head on over to Salt Lake City Weekly to read the full article.

It’s taken more than a decade, millions of man hours and an international movement bent on software sovereignty to poise Linux as the fastest-growing player in information technology. Now, on the cusp of punching through proprietary software’s kung-fu grip on the market, a fuming little Utah County company threatens to stomp Linux dead in its tracks.

“I’ve been pounding the table here for a year or so saying there’s no free lunch, and there is going to be a day of reckoning for every company that thinks they are going to try and sell a free model.” That’s Darl McBride, president and CEO of the SCO Group, a perennial loser at selling UNIX and, until recently, Linux operating systems.

Filings with the Securities and Exchange Commission show that SCO posted hundreds of millions in losses from 1994 to 2002.

But ever since determining it owns the “ark and the covenant to the enterprise software industry,” says McBride, SCO’s bad fortune is on the upswing.

The article is great, it goes on to quite a few pages and gives an excellent and seemingly unbiased timeline.

TurboTas 2004.

Yep, it had to happen. SCO are out and singing the SCO drinking song again , sue sue sue sue, sue sue sue sue (have you learned the words yet?).

Considering the recent Novell moves, it’s not at all surprising that SCO have in fact sued Novell over their copyright filings.

On the one hand, SCO really had to take this step regardless of whether it was smart or not: If any of the other cases had gone to court with the copyright claims ove Novell unresolved, the cases would have been tossed out.

I think this means that on the SCO timeline, this issue really must get resolved before the RedHat, IBM (and end users?) cases get to the courthouse.

The Filing by SCO reads:

Novell has improperly filed copyright registrations in the United States Copyright Office for UNIX technology covered by SCO’s copyrights.

Novell has made false and misleading public claims that it, and not SCO, owns the UNIX and UnixWare copyrights.

Novell has made false statements with the intent to cause customers and potential customers to not do business with SCO.

Novell has attempted, in bad faith, to block SCO’s ability to enforce its copyrights.

Novell’s false and misleading representations that it owns the UNIX and UnixWare copyrights has caused SCO irreparable harm to its copyrights, its business, and its reputation.

The lawsuit, filed in Utah State court, in Salt Lake City, requests preliminary and permanent injunctive relief as well as damages. The injunction would require Novell to assign to SCO all copyrights that Novell has wrongfully registered, prevent Novell from representing any ownership interest in those copyrights, and require Novell to retract or withdraw all representations it has made regarding its purported ownership of those copyrights.

“‘SCO takes this action today given Novell’s recent and repeated announcements regarding their claimed ownership of the UNIX and UnixWare copyrights. SCO has received many questions about Novell’s actions from potential customers, investors and the press. Although SCO owns the UNIX and UnixWare copyrights, Novell’s efforts to claim ownership of these copyrights has forced this action,’ said Mark Heise, partner, Boies, Schiller and Flexner, LLP. ‘We encourage the public and commercial Linux users to read the Asset Purchase Agreement from 1995 (including Attachment E found at www.sco.com/novell) and Amendment 2 so they can see for themselves that SCO owns the copyrights to UNIX and UnixWare.'”

“The lawsuit seeks damages in an amount to be proven at trial for Novell’s alleged slander of SCO’s title to the UNIX and UnixWare copyrights. In addition, the lawsuit seeks punitive damages in an amount to be proven at trial for Novell’s malicious and willful conduct.”

The general community is now rubbing their hans a bit here: This is yet another legal front on which SCO are going to have to fight. It’s generally accepted now that they are doomed to be nothing but a litigation company: No new products will come out of the Utah company.

Indeed, to support this, look how old System 5 is anyway: No major changes since 1988 (Yes, 1988!). Look how far Linux has come in it’s first 10 years and it’s easy to see why it’s all over for Unix as an OS.

All the major Hardware vendors traditionally relying un sub-licenses of Unix now offer Linux options. All. Not some. You do the math.

I was just musing and laughing out load at the recent revelations from Novell and it occurred to me that there is no-one that actually cares about SCO’s impending doom.

Then I began to think again. SCO’s lawyers of course will win whatever happens. Those vultures only stand to win out of this. They’s had the balls to stand up and cheat/lie/steal etc for SCO so some other company is bound to want a peice of them 😉

No thinks I, There is someone that stands to suffer. It’s that well known company, the Yankee Group.

It occurrs to me that the more wild that Laura DiDio gets in her support for SCO, the more embarrassed the Yankee group stand to be when it’s all show to have been a share price scam.

After all, Yankee Group proclaim themselves “a global leader in communications and networking research and consulting”. How could one of their analysts possibly have got this so badly wrong?

This the biggest computing sector legal wrangle ever, and Yankee are siding with the cowboys {smirk}. Surely they will drop the daft Didio soon or they are going to crash and burn badly?

I’m not underestimating here: Didio has been more or less the only respectable voice that SCO could find to support them, so they have quoted her every opportunity they could.

What say you chaps?

No doubt if you have been following things at all closely in the SCO business, you will know about the spanners that Novell have been slinging into the SCO legal machine.

What has not been clear though is the potiential size of the spanners. They are big. Very big. Good.

It transpires that Novell are basically saying that SCO have no ownership rights over Unix, but they do have a right to sell it and make money from it.

This seems to suggest that SCO have no right to sue IBM, no right to unilaterally remove IBM’s AIX license and no right to withdraw SGI’s license either. Oh and no rights to sue Linux end users.

SCO finally managed to mention at their 4th quarter earnings conference (January) that their may be a tiny fly in the ointment regarding Novell. McBride actually said “over the last couple of weeks that Novell snuck into the Copyright Office and tried to file some copyrights. . .”.

This is absolutely hilarious when you consider that Novell have been taking action since mid 2003, as we shall see.

On June 9th, Novell wrote to IBM and SCO and said that according to their interpreation of the 1995 Asset purchase agreement, SCO had no rights to unilaterally terminate IBM’s [AIX] Unix license. They duly waived SCO’s termination of IBM’s license.

Is it not interesting that SCO have been a bit quiet about this? Hang on though, I’ve have not done with this yet. On October 10th, Novell duly waived the termination of SGI’s licence too.

Oh, but there is one more absolute corker yet. Remember that there is of course a potential problem here: It is possible that SCO will prove that they and not Novell actually ‘own’ Unix, depending on interpretations of sale agreement annexes. Don’t worry though, Novell has this covered.

Part of the Sale agreement of Unix was the ‘Technology License Agreement’. This agreement describes rights that Novell has over Unix.

I’ll repeat this bit word for word from GrokLaw’s transcripts from Novell: The technology transfer agreement gives ‘Novell the right not only to use the “licensed technology” itself, but also to “authorize its customers to use, reproduce and modify” it and to sublicense and distribute it “in source and binary form”.

Oh Wow! so now it seems you simply need to be a customer of Novell and you have complete rights to use any part of Unix.

Of course it goes without saying that now Novell have gone public with this SCO are just bound to start ranting again, but I for one have started looking out those Netware 3 and 4 licenses to show I’m a customer.

GrokLaw sum this up well: As Novell told SCO in its first letter to them, Novell is “an ardent supporter of Linux” and it shows. I, for one, will not forget it.

I have to say I think it’s about time that the FBI or whoever it is in the States starts raiding the offices of SCO and removing Guns, Belts, Knives, Rope, Shoelaces, and other things that could be used for self harm.

Article By TurboTas

Prime material Source: GrokLaw.

TurboTas has posted before on the progress of the TAM team to cross the Atlantic with a UAV. As if that were not enough of a challange, the US DARPA have raised the bar with a challenge to cross 300 miles of the Mojave desert with an Unmanned Ground Vehicle.

Pretty easy to see that this is a cheap development trick for the US Government, but the challenge still looks really exciting.

UGV’s have a brand new set of problems to solve that makes the CFIT problem for UAVs look pretty simple to fix.

The challenge itself will be run in mid March 2004, The vehicles will all set off together and have 10 hours to make their way from L.A. to Las Vegas along a tightly determined route.

The rules are pretty tough and call for numerous software and sensor technologies to sucessfully negotiate the waypoints: GPS alone will not be enough.

As if route navigation was not tough enough, there will be numerous obstacles to negotiate. Examples given are bridges and underpasses, but there is also mention of moving obstacles.

Don’t get ideas that you can enter though: entries had to be technically vetted by October 2003.

The competition looks set to hot up now. Many of the teams have tested their vehicles and are now looking at fine tuning. Interestingly, the spectrum of teams is very wide: the likes of Lockheed are competing next to teams of enthusiastic amateurs and Colleges.

For the big corporates, the $1M prize is not the ultimate goal, but more the lucrative contract that may follow a win. The million dollars means much more to the smaller teams.

Follow the progress of the competition here

TurboTas 2004

Earlier in the week, SCO released some information on some of the files that they say were copied from Unix.

The list resulted in a general guffaw at the ineptitude of the SCO Lawyers.

Although there were around 50 files on the list, due to the fact that they are header files for the different architectures, it transpires that there are only 5 unique file at stake here.

These files are really very simple stuff: they are header files and functions that live in the Linux Kernel. None of the files is more that a few K in size, and most importantly, none have changed much since 1991.

Linus has written in the New York Times that he wrote all the files trivially himself without use of Unix source code. A simple check of CVS supports this: all the development is public and the changelog is clear for these files.

It seems that SCO, who are already hopping, have shot themselves in the foot again.

Here are Linus’ comments

“Some of these files were written by me directly”

The files listed in SCO’s letter are written in the C programming language. Citing two files, “include/linux/ctype.h” and “lib/ctype.h,” Linus said “some trivial digging shows that those files are actually there in the original 0.01 distribution of Linux” in September 1991.

“I wrote them,” Mr. Torvalds noted, “and looking at the original ones I’m a bit ashamed.” He observed that some of the macros, or programming shortcuts, are “so horribly ugly that I wouldn’t admit to writing them if it wasn’t because somebody else claimed to have done so ;)”

Linus is clearly angered by SCO’s accusation that much of Linux was merely copied. “In short,” Mr. Torvalds said, “for the files where I personally checked the history, I can definitely say that those files were trivially written by me personally, with no copying from any Unix code, ever.

“I can show, and SCO should have been able to see, that the list they show clearly shows original work, not copied.”

Darl C. McBride, the chief executive of SCO, said he stood by the company’s assertions. He said that a Linux expert who will testify in the SCO suit against I.B.M., which was filed last March, went over the code closely. “As a social revolutionary, Linus Torvalds is a genius,” Mr. McBride said. “But at the speed the Linux project has gone forward something gets lost along the way in terms of care with intellectual property.”

TurboTas can’t help but think that SCO have more tricks up their sleeve: surely this is not the best they can do? SCO’s accounts show that this year they have paid $9M for legal services (Remember that they have also paid with SCO shares too!)

In February 2004, SCO have said they will target the first 10 end users of Linux.

Two Updates today: firstly the DVD Lending Database is back online: Patches fixed the problems. OpenDB and Netjuke are both upgraded to the latest versions.

Netjuke is streaming again after considerable downtime, but only to the local FM transmitter.

Check them out and comment on the new features.

Additionally, all 3 sites now have correct p3p privacy policies in place.

In-line icons also added to make your browser prettier.

Meta Tags updated for better searching and descriptions of sites.

Broken elements of some themes mended using W3C validator.

Script written to restart mpg123 after failure. BB updates to check for mpg123 and mpgchecker script.

Added UK Style Age warning graphics to DVDDB.

SCO have been having a really tough time of late. All the latest turns have gone against SCO. Just to give the downed dog the extra kick, Novell have been quietly continuing what they started earlier in the year and are again ready to publicly contest ownership of Unix System V.

You can read the a more complete article at Groklaw. What it basically says is that after the public argument between SCO and Novell in August things did not quieten down.

SCO said that Novell had taken their toys away and gone home when in actual fact what Novell actually did was to look more carefully into the terms of sale. Once they completed this, they began registering the copyrights for quite a few versions.

Groklaw have analysed the registrations and found that Novell registered versions that SCO have not even noticed: Novell have registered claim that it is the rightful copyright owner of UNIX System V 2, 3.0, 3.1, 3.2, 3.2/386, 4.0, 4.1, 4.1ES, 4.1ES/386, 4.2, and 4.2MP.

Groklaw’s analysis of these registrations is simply that Novell seem to be saying that they and not SCO are the legal copyright holders of Unix System V.

If Novell still own Unix, will they use it in a similar way to SCO: try to lever some profit from Linux users: TurboTas can’t help but think they might. Not quite so brutal as SCO, but maybe not far short!

Here is the Novells answer to questions from Groklaw:

“PROVO, Utah — Dec. 22, 2003 — Novell believes it owns the copyrights in UNIX, and has applied for and received copyright registrations pertaining to UNIX consistent with that position. Novell detailed the basis for its ownership position in correspondence with SCO. Copies of our correspondence, and SCO’s reply, are available here. Contrary to SCO’s public statements, as demonstrated by this correspondence, SCO has been well aware that Novell continues to assert ownership of the UNIX copyrights.”

TurboTas says ‘Happy XMas, Darl’.

Finally, the 2.6 kernel is an official release. What does it have that you want? When is your Linux Distro Likely to have it? Heres a very brief 2.6 Rundown.

The 2.6 Kernel includes some super new features. If you want a fully loaded description, read the article by Joseph Pranevich here.

Firstly, Hardware support: Major improvements here: Support for a large number of new CPU’s and architectures. All the way from the likes of Hitachi’s H8/300 series, the NEC v850 processor right down to the latest Dragonball and ColdFire chips on eval boards from Motorola, Lineo, Arcturus, and others.

With Embedded Linux firmly in mind the 2.6 kernel is the first propper release with the uClinux work merged back in.

At the opposite end of the scale, NUMA support means much bigger SMP boxes are within grasp without curtailed memory access.

Internally a new sub-architecture system allows the processor type to be independant from the architecture: in previous versions special code was needed for the the same CPU in slightly different architectures. The sub architecture systems fixes the need for this code.

Hyperthreading support (first available in Pentium 4’s) is supported: This allows a single physical processor to masquerade (at the hardware level) as two or more processors. This in turn allows for performance boosts in some circumstances, but also adds scheduling complexity and other issues.

There are other scaleability improvement too: 2.6 has other changes for Intel servers at the top of the food chain. First and foremost is improved support for other new Intel hardware features including Intel’s PAE (“Physical Address Extension”) which allows most newer 32-bit x86 systems to access up to 64GB of RAM, but in a paged mode. In addition,

To give the user a more responsive feel (Critical for Linux-On-The-Desktop projects), the kernel is finally pre-emptible. This means that under Linux 2.6, the kernel now can be interrupted mid-task, so that other applications can continue to run even when something low-level and complicated is going on in the background. Although we are only talking about tiny fractions of a second: some users will see considerable improvements.

The IO subsystem generally has been revamped to give good performance accross a wide range of systems and hardware. It’s also far less likely to get lock-ups or race conditions whilst waiting for a resource.

At the module level, a significant rethink to the module description code and the module loading/unloading process has meant that there is now the promise of far better support for hot plug hardware such as found in Laptops etc.

In fact, the APM code has become ACPI compliant: this in turn brings linux up to the current state of the art in hardware power management support. Laptops are the goal here again although we should not be blinkered into thinking that laptop users are the only beneficiaries. Talking of laptops, there is better support for the hardware suspend modes offered from the main vendors.

Ext 3 has been revamped to allow the use of extended ACL’s: this is a clear requirement if Linux (with a native F/S) is to achieve NT’esque file serving. Don’t hold your breath though: many user space tools will need rewriting.

At the multimedia colaface, ALSA has finally replaced OSS: Improvements this brings are many: better SMP support for multimedia machines, proper full duplex sound, multiple sound cards in a single machine. The list goes on.

On the security front, Linux can fianally support Hardware Random Number Generators (Vital for strong cryptography at speed). Also Binary modules no longer have the ability to overload the system with calls. Most significant though is the granularisation of the old superuser priveledges into something modularized.

The virtualisation code is merged back in allowing a stock linux box to run a virtual linux kernel. This significantly simplifies security architecture tasks: honeypots fdor example. Also other development tasks are made much easier with this included.

All in all, 2.6 looks set to raise the benchmark yet again in terms of Performance, scaleability and breadth of hardware supported.

So what about mainstream availability?. Well if mainstream to you includes Fedora, then the release date is around April 2004. Check your preferred vendor for their release schedules.

TurboTas 2003.

It sounds pretty silly, but it’s true: The latest nasty IE bug in which it’s possible to manipulate the URL line so that you’ll think you are on the payapl site etc, has been mended by a European company.

This article appeared at theage.com.au and was written by Sam Varghese.

An open source and freeware software development web site has released a patch to fix the URL spoofing vulnerability in Internet Explorer, which can be exploited by scammers who try to trick people into revealing details of online banking accounts or other private information.

Openwares.org, a Vaunatian company, with branches in Israel, the US and France, released the patch and the source code for the same a couple of days back.

The company has also set up two pages where users can test to see if they are vulnerable to the exploit, one a fake Microsoft Update example and the other an example of a fake PayPal site.

In its advisory, issued along with the patch, Openwares.org said: “Successful exploitation (of this flaw) allows a malicious person to display an arbitrary FQDN (Fully Qualified Domain Name) in the address and status bars, which is different from the actual location of the page.”

It gave the vulnerability a rating of 5 on a five-point scale.

During the weekend I’ve been reading all the articles that spell the end for SCO. Although I don’t yet agree that it’s all over bar the shouting, the indications are that SCO’s banking investors are beginning to get a bit nervous. This is a sure sign of rough times ahead.

In the same thread of thought, it did occur that assuming the SCO action fails it probably spells the end of further lawsuits of similar nature and scale against the penguin.

It’s my belief that the eventual outcome will hold up the Open Source development model as a reasonable and ethical approach to development: a model which encourages creativity on the part of the devlopers and which can protect genuine copyright holders should a breach occur.

The simple fact that anyone can examine the code and that there is a tangible audit trail for every line of code lends massive credence to the movement.

The community was able to respond with incredible speed to the few public code snippets which SCO claimed infringed. Within a day or so the complete history of all the code was uncovered, and SCO were shown to have bungled it.

This and the eventual outcome will dissuade many would-be gold-diggers with perhaps less to lose than SCO.

Let’s not forget that SCO was effectivly on the rocks: with computer hardware costs dropping all the time, no-one was interested in their expensive flavour of Unix. It was already only a matter of time before their customer base, Sun, IBM, SGI and HP would stop using Unixware altogether in favour of Linux.

Whatever the final outcome, it’s certain that anyone else with a beef about open-source is going to have a rough time, both in the courts and out of them.

TurboTas 2003