Slashdot Mirror

Erik Sliman writes "Why are all the IT companies suddenly interested in open standards with web services? An OpenStandards.net article explores the issues surrounding the somewhat vague term."

Nat Friedman often seems to live in the shadow of his famous coworker, Miguel de Icaza, but today it's his turn to shine. You asked Nat questions last week. This week he answers, in detail, with lots of links, touching on subjects ranging from Gnome's future directions to how Microsoft is dealing with Linux as a competitor to Windows. 1) Exchange Like Product
by Kaypro

Currently the Exchange Connector seems to integrate quite well, are there any plans to create a standalone server with similar capabilities to Exchange Server?

Nat:

There are no plans today, but it's a really appealing idea.

Ximian's goal is to enable corporations to deploy and use open source-based desktops. One of the major barriers to this happening today is interoperability with the rest of the corporate computing environment. In the world we all inhabit, that means interoperability with Microsoft products.

When we were doing some product planning and market research early last year we found all these cases in big companies where people had to have two computers on their desk: a Unix machine for their real work -- development, CAD/CAM, 3d rendering, etc -- and a Windows machine so that they could speak all the protocols and file formats that the rest of the office speaks. And we were like: this just ain't right.

In many of these cases, when we asked people, they said that what was keeping that Windows machine on their desk was not, as we expected them to say in all cases, Word or Excel or Powerpoint, but it was actually in many cases Outlook. What happens is that the IT department will proclaim from on high that Exchange is the corporate scheduling standard, and if you ever want to coordinate a meeting or to schedule time in a room or with a projector or any other resource, you have to use Exchange, or you're simply out of the loop.

So this was a situation where providing this functionality under Linux eliminated the need for that Windows machine. This is a clear financial win for the customer and a clear win for the open source desktop. Basically, the Connector was a really obvious product to build.

Will we ever build a collaboration server of our own? It is something we've had some requests for before, and of course we're always listening to our customers and users, but we have no plans to build one today. Tell you what, if you would be interested in paying for such a thing, send email to sales@ximian.com and let us know. :-)

2) Microsoft and Mono?
by zoward

Have you gotten a sense of how Microsoft views the existence of an open source alternative to .NET? Do you think that, over the long term, Microsoft will grow to love, ignore or loathe (and perhaps seek to undermine) Mono?

Nat:

Open source software is a threat to Microsoft's business model, and it is a competitor which they cannot attack with their traditional maneuvers. At the same time, the events of the past seven years, especially the emergence of the web, Linux, Java and XML, have shown Microsoft the marketplace power of open standards. For these reasons, Microsoft's posture toward Mono and similar projects can be hard to gauge.

But the fact is, Linux and other open source efforts are a source of competition for Microsoft, and that is why they are investing 25 million dollars with Unisys to discredit Unix: they are once again facing competition, but this time there is a united front of users and companies around the globe that opposes them. Open source has given the world a common ground.

At the O'Reilly Developer Conference last year on a panel with Michael Tiemann, Tim O'Reilly, and others, Craig Mundie, Microsoft's CTO of Advanced Strategies and Policy, said (I am paraphrasing): "The thing Microsoft does not like about the GPL is that it creates a closed community." Yes, he actually said this, and while the entire audience sat stunned and struggling for oxygen, I remember Tim O'Reilly did not miss a beat, responding with "But so does Microsoft!"

Mono is an open source implementation of the C#, CLR and CLI cross-platform development framework that have been submitted to ECMA for standardization. We are implementing this framework because we believe it is important technology, and that the world should have a free, standards-compliant version of it.

Microsoft wants the ".NET platform" to be adopted, which is why they submitted it to ECMA. Whether or not Microsoft will change their minds, retract their submission, and decide that they do not like Mono is not something I can predict, but if they do, we are ready to adapt to the change and ensure that this technology is available to the world.

3) Core Gnome technologies
by wrinkledshirt

Despite its relatively short lifetime, Gnome's been really great about embracing all sorts of different technologies -- gtk, ORBit, bonobo and now Mono. However, it's sometimes difficult trying to figure out how this all ties together (if it's supposed to at all). Generally speaking, if someone's going to want to develop for Gnome in the future, how should they prepare themselves? What should they want to learn?

Nat:

Actually, the goal of the infrastructural work in GNOME is to abstract all of the underlying technologies away from you so that you can focus on writing your application. We want you to feel the joy of being able to sit down and easily build something, not to hand you a whole bunch of new stuff to learn.

Nowadays GNOME application development can be done rapidly and easily using Python or Perl and the Glade GUI construction tool.

For a lot of people, these languages and tools are the best way to build an application. The GtkPerl site has an example of a GNOME panel applet written in just 60 lines of Perl (and I'm sure it could be done in less). Not everyone knows that Anaconda, the Red Hat Linux installer is actually written using PyGtk.

Using Glade to create your user interfaces not only frees you from the arduous task of manually doing all of the widget creation and packing, it also makes your application more flexible because the GUI layout is loaded at run-time from an XML file. For the GNOME project this has been really helpful, since it means that a lot of UI design and prototyping work can be done without the need to even touch the code.

If you want to learn more, developer.gnome.org has a pretty good overview of the GNOME architecture.

All of the GNOME technologies that you've heard about work under the hood to provide consistency, configurability, and scripting features that you, as a programmer, only come into contact with if you need them. The goal, to steal directly from Larry Wall, is to make the easy things easy and the hard things possible.

For example, you might (or might not) have heard of Atk, Gail and at-spi. These are accessibility ("a11y") technologies that are in GNOME 2 to make it possible for applications to be used by people with various kinds of impairments. But you do not need to be exposed to any of the details of CORBA in order to use them, and in fact, some of the a11y features come for free just from building your application using GNOME 2.

By the way, I happen to think that accessibility is a killer feature in GNOME 2. At GUAD3C, Marc Mulcahy gave a great demo of how a sightless person can navigate the desktop using a screen reader. And we have been working on a set of accessible icons for GNOME 2 as well. There are cool side effects too: Because GNOME's accessibility infrastructure is done programmatically and at the widget level, you can actually attach to a remote running application and introspect and act on its widget tree. This may make it possible for us to eventually have a very high-quality automated UI testing tool.

Check out the GNOME Accessibility Project web page for more information.

As for Mono, it is still a technology under development, and the GNOME project has not made a decision to adopt it in any way yet. Work on C# bindings for Gtk is progressing, however, so you will be able to write Gtk and, eventually, GNOME applications in C#.

4) Usability research
by nakhla

One of the big problems facing GNOME and other open-source software is that of ease-of-use. Microsoft and Apple spend millions of dollars when developing new operating systems or UIs in order to ensure that their product is easy to use for the non-geek end user. What kind of useability studies has Ximian conducted? What is Ximian doing to correct any problems that the research has brought to light?

Nat:

Ximian and the GNOME project have learned from standard, existing industry practices for building usable software. In short this means designing for usability, performing formal usability testing on real users, and treating usability problems as first-class bugs.

The GNOME Usability Project is a nice central resource for a lot of the usability work that has gone into GNOME. Recently the project has been making a lot of progress on the GNOME Human Interface Guidelines, a set of UI rules that will help GNOME achieve much better consistency in its user interfaces. The results of the comprehensive GNOME desktop usability study that Sun performed last year are worth a read, too, even if we've already overcome a lot of that stuff in GNOME 2.

In the course of the design of Evolution 1.0 and 1.2 (due out this summer), Anna Dirks, our UI designer, performed many dozens of usability tests on various parts of Evolution, using a wide variety of people with varying degrees and types of experience using computers. Anna delivered a nice talk on the usability testing process at the GUADEC Conference

An application's usability is directly related to the ease with which a user can predict its behavior when he gives it input. This is why usability testing is a productive activity. In its basic form, it goes like this:

1. Create a prototype of the interface you are designing. In some cases prototypes are created using "scripting" languages or "RAD" tools, and sometimes they are just printed onto "paper." This last type is called a "paper prototype," the name deriving from the "paper" on which it is printed, and the fact that it is a prototype.

2. Coerce an appropriately representative set of individuals into participating in the usability test. The use of lethal force may be necessary.

3. Ask the user to perform a certain task, using the prototype.

4. Observe and record the steps the user takes, with particular attention to his mistakes.

5. Rinse, lather, repeat.

The fundamental premise of the usability test is that the user has certain expectations of how a given interface will behave, and the thing that a designer must do is to identify the places where his interface does not conform to those expectations, and to fix them.

At Ximian we've gotten subjects for our usability tests from a variety of places; there's a movie theater downstairs from our office and sometimes we'll hang out there and offer people free movie passes to participate in usability tests. So we get a pretty broad audience.

All usability issues that arise during a usability test are filed as bugs in bugzilla alongside other issues, and of course the subject's comments inform the revised design of the interface in question.

For GNOME 2, we decided to revamp all of the GNOME stock icons to improve their consistency, usability and to brighten up the style a bit. Ximian has contributed all of these new icons back to GNOME; you can check them out on developer.ximian.com.

Havoc recently wrote a nice piece which covers UI design in free software, and in GNOME in particular.

5) Conflict of Philosophies
by polyphemus-blinder

I would like to know:

What is your take on the apparent paradox resulting from:

1. the goal of uniformity on the Linux desktop, and

2. the many, many, groups who have this as their own special goal?

Mandrake and RedHat work toward this on the OS level, and Gnome and KDE battle it out on the desktop integration level, and many others espouse some sort of a "grand unification theory" of Linux.

Do you subscribe to the theory that less is more, or that multiple groups with a common goal will result in the goal's earlier acheivement?

Nat:

In any large-scale human endeavor, consistency is a very difficult goal. I once heard a senior Microsoft project manager express the goal of consistency in software thusly: "A program should look as if it were written by one person." This is a thing that everyone struggles with.

To give you a short summary of my answer:

(1) Consistency is hard.

(2) Decentralization and parallel development are inherent to open source software.

(3) Open standards and making an effort to work together are key. Let's try to do more of that.

Consistency in software applications means fewer surprises, a gentler learning curve, and being able to get your work done without tripping over an application's special quirks along the way. This is especially true of the interfaces that the application exposes.

For human interfaces, consistency means that the elements of the application do what the user expects them to do, and that the interface, consequently, does not get in the user's way. This means that a dialog's Close button is always in the same place, the menubar always appears at the top of the window, and Ctrl-Q always quits. Usability flows predictability which flows from consistency.

For programming interfaces, or APIs, consistency means that the methods you invoke have predictable characteristics: similar naming, the same memory management semantics, the same return values in an error condition. This means cleaner code, less time spent hunting through documentation, and fewer bugs.

So we can agree that consistency is a good thing. Two things are needed to achieve it: a standard, and a way to enforce that standard.

In more centralized environments, such as companies, these things are easier to do. It is naive to think that any company, even Microsoft is fully centrally controlled, but it is certainly much easier to enforce a single standard on people when you are paying them, and when you have editorial control over the final product.

But even with a single, documented standard and even if you are paying people's salaries, consistency does not come easily, even in the most centralized environments. At one point Microsoft had at least nine separate internal implementations of SOAP, and only recently have these all been consolidated...into four.

So how on earth do we achieve consistency in a decentralized environment? Given that starting your very own open source "project" is a matter of a few clicks on sourceforge, how do we "prevent" people from creating applications that do not adhere to some common set of ideas as to how they should behave? Given that there is no central control of what happens in the open source desktop world, how can we even create a standard that we all agree on?

I remember when Mac OS X first came out, people asked a lot of similar questions: How can we ever create an interface that is as consistent as this in our weirdo free code, free love, gift economy, bazaar-inspired noospheric environment?

This question can be considered at different scales: how can consistency be achieved within a single project, and how can it be achieved in the open source world in general.

And this issue of decentralized development comes up in other guises as well. In addition to bemoaning a lack of consistency, people talk about duplication of effort and fragmentation. They say things like: "If only we could focus all of the energy that has gone into producing all of the IRC clients in the world on building just one IRC client, think how awesome it could be!" People really say this sort of thing. I have heard them.

And, of course, there are those in the press and on the mailing lists who see this very same pattern in what they call the "GNOME vs KDE wars" or "the desktop wars." This is the "How many Linux distributions can you count?" conundrum.

Many people who are much smarter and better looking than I have responded to this question at various times.

Linus has said that he believes that in the Linux development community today, there is a "psychological barrier to fragmentation," and that this barrier is the learned result of the Unix wars of the 1980s.

Alan Cox has said that implementation fragmentation is not important, as long as care is taken not to break interface compatibility. The important thing, quoth Alan, is the existence and adherence to open standards. And Eric Raymond has pontificated at length about how it is the nature of the open source community, when confronted with a problem to solve, to try "all solutions at the same time." That is, I think Eric would tell you, the nature of the open source world, and, in many ways, its greatest strength. And of course, Eric is right. Seriously, I love that guy.

If on an iron-gray fall day you have looked up and seen a dark spot moving against the sky and changing shape and size but still moving smoothly in one direction and then it came closer and when you looked you could see the individual birds flapping their wings and shifting forward and back in the formation and alternately turning against and away from each other but still somehow moving all together as one mass, I think you have seen something that resembles the greater open source development community, if there can be said to be such a thing.

The thing that the birds are doing is called "flocking," and today the problem of flocking is still an interesting issue in algorithmic circles. The basic scenario is that, with each element in the flock making its own individual movement decisions based on its own individual and unique sensory input of what is happening immediately around it, the flock must somehow move along a single path, as a whole. The analogy of the Boids flocking algorithm actually runs deeper than you might expect; check it out sometime.

What is important in open source software is doing the actual human work of getting people together and creating the open standards that will allow us to function as a group, and to move in the same direction. And the way to do that is through open, shared standards.

I'm not talking about a kind of abstract standards process where an aesthete group of monks argues for centuries in the thin mountain air about file system standards before descending with etched tablets, but a process where implementors agree on good-enough standards of existing practices in the places that matter, today. Standardization is a way for us to align our directions, maintain implementation distance, and follow a common flight path, not an end in and of itself.

The thing to recognize is that the problem of creating a consistent desktop experience and the fact that our approach is a multi-pronged, decentralized, evolutionary one do not have to be at odds with each other. The key to consistency is to work toward it.

6) As a business
by Fizzlewhiff

Is it frustrating to see potential revenue lost due to offering the same products for free? Do you ever run the numbers to see what your income potential might be if you stopped giving away the same software you sell or do you believe that the Linux community, as a whole, cannot and will not support companies who only sell Linux software?

Nat:

If in the last two years we hadn't put out approaching 2 million lines of GPL'd and LGPL'd code, we would not have nearly the success that we have today.

If you're going to run those kinds of numbers, you should also calculate:

1. How much extra would you have to spend on development in order to compensate for the fact that you will no longer have the help of a large community of testers, translators and hackers?

2. How much do you have to spend on marketing to even reach the same level of name recognition you can achieve by being a responsible, active open source software development company? Would you have the same amount of credibility?

During the several months that preceded Evolution 1.0, we averaged around 10,000 daily downloads of the Evolution snapshots, and many of the downloaders were actively reporting and fixing the bugs that they found. How much would it have cost us to manually test Evolution against the wide variety of IMAP, LDAP and Palm devices that the Evolution codebase was exposed to by this army of users?

This kind of thinking may sound cold and not particularly ideological, but if you're going to perform one kind of calculation, you gotta do them all. I have actually heard of open source companies sitting down and working out the second, marketing calculation, and including it in their business plans as a rationale for writing free code.

7) Co-existance of Red-Carpet and up2date/RHN
by yusufg

Hi, Red-Carpet seems to offer functionality similar to up2date/redhat network. However, there seems to be a very substantial lag between packages made available via Ximian's redhat channel and up2date.

An example being (till now, RPM 4.0.4) is not available via the Redhat 7.2 channel. Is Ximian going to ever make a policy statement as to what is the maximum duration their userbase will be diverged from receiving the latest updates of their respective distributions.

If there are specific packages which are likely not to be made available via red-carpet, can their be an official statement on this so that users are aware of the pros/cons of using multiple update mechanisms?

Nat:

Our policy is that all distribution and third-party updates are made available through Red Carpet as soon as they can reasonably be pushed without breaking other software for the user.

For example, with security updates, these are always made available as soon possible, often within just a few hours, always within a day.

With something like the RPM 4.0.4 update, however, sometimes we have to lag behind the upstream provider, in order to ensure compatibility. This does not mean that we hate Red Hat or that we do not care about users, or that we are lazy.

In the particular case of RPM, new releases of RPM often break binary or database compatibility with old versions (this was true with 4.0.4), and so we are cautious about making these available to users until we have first ensured that Red Carpet will continue to work on your system. I am not trying to pass the buck to Red Hat here. They are great people. Our userbase, in running Red Carpet, just happens to have a different set of needs than Red Hat's, and this is what, in the case of RPM 4.0.4, created the delay you noticed.

To answer your second question, as long as the packages that are shipped by the upstream providers are open source, and as long as we can legally redistribute them, we will make them available via Red Carpet.

8) Lack of documentation for GNOME internals
by Tet

Are there any plans to increase the amount of documentation on GNOME internals? While GNOME seems to have plenty of trivial documentation (such as the GNOME User's Guide [redhat.com], there's virtually nothing that explains what's going on underneath. Are there any plans for a "GNOME Administrator's Guide"? I'm thinking of something that documents usage of files in $HOME/.gnome, what session management is and how it works, what controls the contents of the GNOME menu, and so on. For example, when GNOME fails to correctly save session information, I'd like to be able to check the documentation to see what should be being written to .gnome/session. At the moment, I just have to guess. Some of it is reasonably obvious from context, but it's the sort of thing that really needs formally documenting.

Nat:

So, for a lot of the stuff you're talking about, the documentation is out there. If you want to learn about the session manager and how to configure it, check out the man pages for "gnome-session" "default.session" and "save-session". There's also a white paper covering a lot of the configuration files, though it is out of date. Collecting and updating all of these things into a single "GNOME System Administrator's Guide" sounds like a great idea for a project for someone :-).

The GNOME Documentation Project and the individual efforts of developers and users have produced a large amount of documentation to date. In addition to the GNOME User's Guide that you mention, there is the user's manual work that Sun has been doing. There is also a lot of developer documentation on developer.gnome.org, including some useful tutorials and white papers.

With all of the large vendors that are shipping GNOME on their workstations, I think it's a safe bet that the components of an administrator's guide will come together in the near future. I know that, inside Ximian, we have recently written for a customer some documentation specifically focused on issues that would be interesting to system administrators, and naturally we will be working to release this to the community at some point soon.

Of course, if you or anyone else out there wants to join up with the GNOME Docs team and start assembling such a guide, you would be welcomed with open arms :-). If you don't have time to do that, you can contribute by filing bugs in bugzilla.gnome.org whenever you find problems or missing pieces and by contributing fixes to the individual projects. Check out the gnome-doc-list mailing list for more information on how you can help.

9) Why subscribe?
by JThaddeus

I was considering subscribing in order to improve the performance of downloads (which have gone to a snail's pace since the subscription program began) but two out of three of my last update attempts have ended in file not found errors. This type of error doesn't give me confidence in how well RedCarpet setups are tested. So why shouldn't I just forget about subscriptions and go with KDE?

Nat:

Without more information, I can't say exactly what the problem is that you were experiencing. That type of issue can sometimes happen if you're updating from one of our mirrors that is in the process of syncing from our master site.

I can tell you that we do directed testing on all updates that are pushed to Red Carpet, on every single supported platform, before an update is released. Additionally, we pay close attention to the bug reports that our users file in our bug tracking system, and make an effort to address all of those as quickly as possible.

Just last week we released a new channel in Red Carpet called "Untested," which contains the pre-QA versions of all of our Ximian GNOME updates before they hit the main channel. Similar to the Mandrake Cooker or Debian unstable, this is a way for the update junkies of the world to get an early glimpse at new packages and versions before they hit the official channel. And of course, this is a way for us to get broader user testing and resolve problems earlier.

Also, by the way, the bandwidth we've allocated to our free public Red Carpet servers has been steadily increasing since the launch of the subscription program. If the servers have gotten slower, it's because the user demand keeps increasing.

But whatever your experiences with Red Carpet, they should not be brought to bear on your choice of desktop. Red Carpet is a software management service that is independent of your choice of desktop or web browser or editor or whatever. And because the Red Carpet client is statically linked, you don't even have to have GNOME installed to use it. In fact, about 20% of Red Carpet usage is by people who want to get updates to the packages provided by their distribution, not Ximian GNOME.

10) External Compatibility
by dspeyer

What plans do you have to improve compatibility with the non-GNOME world?

For example, do you think it's practical to implement Xaw as a front-end to GTK? That would get OpenOffice integration real fast, among others. What about a unified theme format with KDE? Or a common protocol for copy/paste?

It seems like this sort of stuff would be really helpful -- what's actually in the works?

Nat:

Compatibility actually has less to do with an application's choice of drawing toolkit than you might think. Of course, there's nothing to prevent you from running a non-GTK application in GNOME, and it's not necessarily the case that the user experience is hugely degraded if you do. I know of a lot of KDE users who started using Evolution in the last couple of months, because the functionality is so rich, which is great.

GNOME and KDE have had drag-n-drop and cut-n-paste interoperability for quite a while, and we also use the same .desktop file format to store launchers and menu items. You can track a lot of this stuff at freedesktop.org.

Open Office does not use Xaw. That being said, it would be great if OpenOffice used the Gtk drawing primitives so that OpenOffice would be theme-compatible with GNOME. It would not be a total integration, and the behaviour might still be different, but it would help the desktop to look more like a single unit. In fact, it would be possible to get Qt to use Gdk as well, which could make shared themes possible there too.

Another step would be to adopt a common set of icons; baby steps like this can improve visual harmony a lot, even if the "compatibility" is only at a very superficial level. These first steps could be followed by deeper integration, like a working bridge between Bonobo and Uno, the OpenOffice component system.

A unified theme format with KDE would probably be difficult, having a theme or set of core themes for GNOME and KDE which looked and felt the same on both would be a nice step toward making the desktops more compatible to the user. There have been noises made recently that this kind of thing is a possibility, and Ximian would be fully supportive of that.

Though these surface integration steps would be nice, the area where inter-project compatibility is most badly needed is configuration. If someone is running a mixture of GNOME and KDE applications, Mozilla, OpenOffice, and older Xtk-based programs, they need to be able to make configuration changes that are reflected in every application. Having to go to N different places to set your default URL handler, theme, or MIME type bindings is a real usability problem. Jim Gettys talked about this a lot at the most recent GUADEC. Keith Packard's recent fontconfig work is an excellent example of this.

cybrpnk writes: "The QX3 Video Microscope may have been an obscure commercial failure as an educational toy, but it is widely available (for now, at least) as a fantastic tool/toy for any geek. The QX3 hooks up to a USB port and delivers live color 10X, 60X or 200X microphotos at 512x384 pixel resolution. Its kid-friendly software even makes time lapse videos a snap, like this one of TNT synthesis - a whole new way to blow up the lab, do not try this at home! Educators are doing amazing things with the QX3 in their classrooms. Sourceforge even has documentation on the software command structure used by the QX3, so it may be considered an open source microscope. Get yours today for under $50 at surplus closeout or EBay before they're all gone!" The Toys-R-Us nearest to me has one QX3+ left (now with my name on it) at $30, so I hope it really does work under Linux. And it's a lot less complicated than building a Scanning-Tunneling microscope.

TexTex writes "Riley Lynch has released Space.dock, which brings multiple desktops to Mac OS X. He's provided the code and binaries through SourceForce.net. It runs pretty well for being a 0.7 release and sure beats hiding all your applications and just opening the one you'd like." This is a cool little program. I usually question how much I really need virtual desktops, but I never fail to use them when I have them available.

Moridineas writes: "Since the wine project decided to change from an X11 style license to an LGPL license, a BSD fork has emerged, called Rewind (for 'Re-engineering Windows,' or something like 'Rewind to the old Windows days' in the words of Ove Kaaven) and currently hosted at http://rewind.sourceforge.net (but looking for a new home). The announcement of the fork and some additional information was posted to the wine-license mailing list [winehq.com]. At least one company [transgaming.com] has already stated that they will not be able to work with the LPGL wine (citing among other things, possible DMCA violations) and will be actively helping Rewind (with cash and code it seems)."

ZaMoose writes "Looks like Transgaming has released version 2.0 of WineX (with full support for Jedi Knight II and initial 3D sound support. Joy!) Prepackaged .debs and .rpms are available only to subscribers, but you can always just download and compile it yourself (you just won't get the nifty SafeDisk workarounds/InstallShield proprietary stuff)."

axehind writes "Dr. Moshe Bar recently announced the creation of openMosix, a new OpenSource project. The project has quickly attracted a team of volunteers developers from around the globe and is off to a very fast start. openMosix, is an extension of the Linux kernel. openMosix is a Linux kernel extension for single-system image clustering. openMosix is perfectly scalable and adaptive. Once you have installed openMosix, the nodes in the cluster start talking to one another and the cluster adapts itself to the workload. "

axehind writes "Dr. Moshe Bar recently announced the creation of openMosix, a new OpenSource project. The project has quickly attracted a team of volunteers developers from around the globe and is off to a very fast start. openMosix, is an extension of the Linux kernel. openMosix is a Linux kernel extension for single-system image clustering. openMosix is perfectly scalable and adaptive. Once you have installed openMosix, the nodes in the cluster start talking to one another and the cluster adapts itself to the workload. "

jonerik writes "Denver's weekly Westword magazine has this article on titanium and the attempts to break it out of its traditional aerospace/defense industry niche, including its growing use in architecture, computers, jewelry, sports, knives, cars, medicine, and other areas. The upside: It's as strong as steel but weighs half as much, it doesn't rust, and it's fairly plentiful. The downside: It's expensive compared to steel and aluminum and its high melting point makes it difficult to work with under some conditions. Still, it's nice to see it being used in other applications." Heck, I know someone who used it as his wedding ring. Pretty cool, actually.

fader writes: "On gnome.org is an article indicating that there are now GTK bindings for C#. Basically, when combined with MONO, this means that you should be able to write at least some rudimentary .NET applications for GNOME." Update: 04/12 00:30 GMT by T : Hetz points out that Qt already has this capability (also in Alpha): here's a link to the Qt-CSharp project, and a proof-of-concept screenshot as well.

fader writes: "On gnome.org is an article indicating that there are now GTK bindings for C#. Basically, when combined with MONO, this means that you should be able to write at least some rudimentary .NET applications for GNOME." Update: 04/12 00:30 GMT by T : Hetz points out that Qt already has this capability (also in Alpha): here's a link to the Qt-CSharp project, and a proof-of-concept screenshot as well.

maloi writes: "A couple of years ago, I wrote some software to mimic the genetic image generation software Karl Sims describes in his paper Artificial Evolution for Computer Graphics. After neglecting it for a long time, I finally got around to it again a few weeks ago, cleaned it up a bit, and released it under the GPL. You can now find it at Sourceforge. There's also a bit more info about it at Kaizolabs. I should mention that this is my first foray into open source development, so if there's anyone interested in both working on it and perhaps lending some guidance to me, it would be greatly appreciated!"

jpsc was kind enough to send in coverage of the Linux Accessibility Conference at CSUN: "There was a flurry of activity in the Linux accessibility world at CSUN 2002, one of the most widely attended, well known, and longest running conferences on technology for the disabled. Accessibility, for those who do not know, is the practice of making software accessible or usable by the disabled (e.g., blind or low vision); under United States law, software, including Linux, must be accessible for it to be used by the government. Similar laws exist in other countries. " Coverage continues... On Thursday, March 21st, Sun Microsystems presented the UNIX Accessibility sessions, which ranged in subject matter from panel discussions about the general importance and state of UNIX accessibility, to overviews of the structure of GNOME 2 and the GNOME Accessibility Architecture, to presentations about new Assistive Technology (AT) for the platform. Most notable were demonstrations of Gnopernicus, a GNOME screen reader, magnifier, and Braille outputer and GOK, the Gnome Onscreen Keyboard. Sun also announced that a team of engineers in China is working on making Mozilla accessible through the GNOME Accessibility Architecture and that several engineers are doing the same for Nautilis. Overall, Thursday?s sessions were representative of the great progress made in the last year in the Linux and UNIX accessibility world, specifically in the GNOME, GTK+, and X Windows arenas.

The next day the 2nd Linux Accessibility Conference, also at CSUN 2002, served as the stage for more in-depth and technical material as well as group discussions about the community?s direction. Presentations were given on subjects such accessibility checklists and guides for application developers, modifying the Linux kernel to speech-enable console applications, and Linux accessibility in the United States government. Among the most prominent parts of the conference was a roundtable on interoperability and collaboration, which lead to the formation of lengthy and detailed TODO list. As with the 1st Linux Accessibility Conference, this year?s meeting allowed developers to share their work and plans for the coming months and hopefully better coordinate them.

Overall, in two days at CSUN, UNIX, Solaris, and Linux showed themselves to be increasingly capable platforms for disabled users. The Linux accessibility community continues to grow and is looking, now more than ever, for new developers and volunteers. E-mail JP Schnapper-Casteras and with your skills and experience (experience with accessibility not required) and he will put you in contact with the appropriate people and projects.

URLs:

• TODO items
• Notes from the conference
• Free Desktop Accessibility Working Group (FDAWG)
• GNOME Accessibility Project (GAP)
• Gnopernicus - An integrated screen reader and magnifier for Gnome
• Gnome Onscreen Keyboard - Aims to enable users to control Gnome without a standard keyboard (with alternate input devices).
• Linux Accessibility Resource Site (LARS)

"

jpsc was kind enough to send in coverage of the Linux Accessibility Conference at CSUN: "There was a flurry of activity in the Linux accessibility world at CSUN 2002, one of the most widely attended, well known, and longest running conferences on technology for the disabled. Accessibility, for those who do not know, is the practice of making software accessible or usable by the disabled (e.g., blind or low vision); under United States law, software, including Linux, must be accessible for it to be used by the government. Similar laws exist in other countries. " Coverage continues... On Thursday, March 21st, Sun Microsystems presented the UNIX Accessibility sessions, which ranged in subject matter from panel discussions about the general importance and state of UNIX accessibility, to overviews of the structure of GNOME 2 and the GNOME Accessibility Architecture, to presentations about new Assistive Technology (AT) for the platform. Most notable were demonstrations of Gnopernicus, a GNOME screen reader, magnifier, and Braille outputer and GOK, the Gnome Onscreen Keyboard. Sun also announced that a team of engineers in China is working on making Mozilla accessible through the GNOME Accessibility Architecture and that several engineers are doing the same for Nautilis. Overall, Thursday?s sessions were representative of the great progress made in the last year in the Linux and UNIX accessibility world, specifically in the GNOME, GTK+, and X Windows arenas.

The next day the 2nd Linux Accessibility Conference, also at CSUN 2002, served as the stage for more in-depth and technical material as well as group discussions about the community?s direction. Presentations were given on subjects such accessibility checklists and guides for application developers, modifying the Linux kernel to speech-enable console applications, and Linux accessibility in the United States government. Among the most prominent parts of the conference was a roundtable on interoperability and collaboration, which lead to the formation of lengthy and detailed TODO list. As with the 1st Linux Accessibility Conference, this year?s meeting allowed developers to share their work and plans for the coming months and hopefully better coordinate them.

Overall, in two days at CSUN, UNIX, Solaris, and Linux showed themselves to be increasingly capable platforms for disabled users. The Linux accessibility community continues to grow and is looking, now more than ever, for new developers and volunteers. E-mail JP Schnapper-Casteras and with your skills and experience (experience with accessibility not required) and he will put you in contact with the appropriate people and projects.

URLs:

• TODO items
• Notes from the conference
• Free Desktop Accessibility Working Group (FDAWG)
• GNOME Accessibility Project (GAP)
• Gnopernicus - An integrated screen reader and magnifier for Gnome
• Gnome Onscreen Keyboard - Aims to enable users to control Gnome without a standard keyboard (with alternate input devices).
• Linux Accessibility Resource Site (LARS)

"

jpsc was kind enough to send in coverage of the Linux Accessibility Conference at CSUN: "There was a flurry of activity in the Linux accessibility world at CSUN 2002, one of the most widely attended, well known, and longest running conferences on technology for the disabled. Accessibility, for those who do not know, is the practice of making software accessible or usable by the disabled (e.g., blind or low vision); under United States law, software, including Linux, must be accessible for it to be used by the government. Similar laws exist in other countries. " Coverage continues... On Thursday, March 21st, Sun Microsystems presented the UNIX Accessibility sessions, which ranged in subject matter from panel discussions about the general importance and state of UNIX accessibility, to overviews of the structure of GNOME 2 and the GNOME Accessibility Architecture, to presentations about new Assistive Technology (AT) for the platform. Most notable were demonstrations of Gnopernicus, a GNOME screen reader, magnifier, and Braille outputer and GOK, the Gnome Onscreen Keyboard. Sun also announced that a team of engineers in China is working on making Mozilla accessible through the GNOME Accessibility Architecture and that several engineers are doing the same for Nautilis. Overall, Thursday?s sessions were representative of the great progress made in the last year in the Linux and UNIX accessibility world, specifically in the GNOME, GTK+, and X Windows arenas.

The next day the 2nd Linux Accessibility Conference, also at CSUN 2002, served as the stage for more in-depth and technical material as well as group discussions about the community?s direction. Presentations were given on subjects such accessibility checklists and guides for application developers, modifying the Linux kernel to speech-enable console applications, and Linux accessibility in the United States government. Among the most prominent parts of the conference was a roundtable on interoperability and collaboration, which lead to the formation of lengthy and detailed TODO list. As with the 1st Linux Accessibility Conference, this year?s meeting allowed developers to share their work and plans for the coming months and hopefully better coordinate them.

Overall, in two days at CSUN, UNIX, Solaris, and Linux showed themselves to be increasingly capable platforms for disabled users. The Linux accessibility community continues to grow and is looking, now more than ever, for new developers and volunteers. E-mail JP Schnapper-Casteras and with your skills and experience (experience with accessibility not required) and he will put you in contact with the appropriate people and projects.

URLs:

• TODO items
• Notes from the conference
• Free Desktop Accessibility Working Group (FDAWG)
• GNOME Accessibility Project (GAP)
• Gnopernicus - An integrated screen reader and magnifier for Gnome
• Gnome Onscreen Keyboard - Aims to enable users to control Gnome without a standard keyboard (with alternate input devices).
• Linux Accessibility Resource Site (LARS)

"

bsartist writes "I've released the first version of a Cocoa/Perl bridge that I call CamelBones. It's alpha-quality but functional enough for the example application, a POD reader similar to MacPerl's Shuck, to be written entirely in Perl." There are other projects like this that have been started, though this is the first one I've seen (since the Rhapsody days, anyway) that has code available.

bsartist writes "I've released the first version of a Cocoa/Perl bridge that I call CamelBones. It's alpha-quality but functional enough for the example application, a POD reader similar to MacPerl's Shuck, to be written entirely in Perl." There are other projects like this that have been started, though this is the first one I've seen (since the Rhapsody days, anyway) that has code available.

Eugenia writes: "Yup, Bill Hayden has forked AtheOS by using its app_server and Interface Kit (along with some other of its kits, like the filesystem layer) and ported it on top of the 2.4.x Linux kernel, without the need for X11. He already has the graphical environment working, and he also has some BeOS apps recompiled and working under Linux. Why BeOS applications? Because that was the reason of the fork. Exactly because AtheOS and BeOS have similar technical principles (highly multithreaded, truly preemptive, similar C++ API etc), by modifying AtheOS's API to match BeOS, Bill is trying to resurrect the BeOS. By doing so this way, Bill is already way ahead from the other two efforts to ressurect BeOS, OpenBeOS (dependant on the 'clean' NewOS kernel) and BlueOS (which depends on Linux and X11)."

Eugenia writes: "Yup, Bill Hayden has forked AtheOS by using its app_server and Interface Kit (along with some other of its kits, like the filesystem layer) and ported it on top of the 2.4.x Linux kernel, without the need for X11. He already has the graphical environment working, and he also has some BeOS apps recompiled and working under Linux. Why BeOS applications? Because that was the reason of the fork. Exactly because AtheOS and BeOS have similar technical principles (highly multithreaded, truly preemptive, similar C++ API etc), by modifying AtheOS's API to match BeOS, Bill is trying to resurrect the BeOS. By doing so this way, Bill is already way ahead from the other two efforts to ressurect BeOS, OpenBeOS (dependant on the 'clean' NewOS kernel) and BlueOS (which depends on Linux and X11)."

An Anonymous Coward writes: "Ximian Connector is out! Regardless if you don't like open source and Microsoft playing together this will let me ditch my Win2k box at work! Here is the press release. Of note, MS Exchange 2000 has a nice HTTP interface to it as well, works wonderfully in Galeon." kittenslietome adds a link to the license under which it's released as well: Connector is not Free software, but rather software Ximian hopes will pay for further Free software development.

Dre writes: "Today marks a special coincidence. First, Adam Treat released the initial version of Qt bindings for C#, which consists of 476 Qt classes converted to C#. The bindings work with the Mono compiler, runtime environment and class libraries, enabling a fully Open Source implementation of C# for Qt. While not yet ready for a real application, Adam has managed to write and execute a Hello World! program (screenshot). KDE bindings are on the drawing board. Shortly thereafter, Phil Thompson, Jim Bublitz and theKompany.com released KDE 2 and KDE 3 bindings for Python. Together with the Java, Objective C and C bindings in the kdebindings module, as well as the Ruby bindings, KDE is providing developers a broad gamut of application development languages."

Dre writes: "Today marks a special coincidence. First, Adam Treat released the initial version of Qt bindings for C#, which consists of 476 Qt classes converted to C#. The bindings work with the Mono compiler, runtime environment and class libraries, enabling a fully Open Source implementation of C# for Qt. While not yet ready for a real application, Adam has managed to write and execute a Hello World! program (screenshot). KDE bindings are on the drawing board. Shortly thereafter, Phil Thompson, Jim Bublitz and theKompany.com released KDE 2 and KDE 3 bindings for Python. Together with the Java, Objective C and C bindings in the kdebindings module, as well as the Ruby bindings, KDE is providing developers a broad gamut of application development languages."

Eugenia writes: "Many are the developers who prefer Perforce in favor of CVS. There is a new player in the field now though. It is called Vesta and it is a replacement for both CVS and 'make'. It handles source revision control and automated construction. It is the result of over 10 years of research and development at the Compaq/Digital Research Center. Just last August Compaq gave the 'ok' to GPL Vesta and since then the 4-member team worked hard to finish up the port to x86 Linux (prior to that, Vesta only worked on Alpha and Tru64 systems). Now, the first Free version is available for download. For a summary of some of the features that make Vesta interesting, see this page."

pudge (apple.slashdot.org editor and MacPerl Maintainer) writes "MacPerl 5.6.1r1 is the first release of MacPerl in four years. It is now based on perl 5.6.1 -- actually on the latest unreleased 5.6 sources, so MacPerl is the most advanced release of perl ever -- and support for MacPerl is now in the perl core, for both 5.6 and 5.8. MacPerl can also be built entirely with freely available software. And, like its predecessor, it runs on Mac OS X under the Classic environment. Read the announcement, and see macperldelta for details on what's changed."

Eugenia writes: "Font antialiasing first made its way to XFree through Qt/KDE only a year ago and GTK+/Gnome followed some time after. Even with the latest version of Freetype 2.08, which reportedly brings better quality, the result is still not up to par with the rendering quality found on some commercial OSes. David Chester has hacked through the Xft library and he achieved an incredibly good quality on antialias rendering under XFree86. With this hack, at last, XFree can deliver similar aesthetic results to Mac OS X's or Windows' rendering engines. Check the two brand-new screenshots ('before' and 'after') at his web page and notice the difference with your own eyes."

jeek writes "Perl 5.7.3 is out. This should be the last development version before 5.8.0 comes out in April or May." You can download it from CPAN or get a copy of it from SourceForge.net. If you have some free time try downloading it and testing it. According to the included perldelta.pod file, the highlights are: better Unicode support, new thread implementation, many new modules, better numeric accuracy, safe signals, and a completely overhauled and improved regression test suite.

woogie asks: "I have finally broken down and ripped all my CDs, and I have a mod_mp3 server with a bunch of different streams based on genres that can deliver those mp3s to anywhere in my house. Anywhere, that is, except my stereo system. Anyone know of decent audio hardware that will read a Shoutcast stream? Sure, I can plug my laptop line out into my tuner's inputs, but I'd really like a device I can just stack on top of my tuner that will accept Shoutcast streams. The only device I've seen that allows this is the Audiotron which appears to want to read your mp3s from an SMB share, but can be configured to read Shoutcast streams if you use special Windows based software to configure it. It would work, but seems a bit pricey given that it targets my needs as an afterthought. There is some promising hacking going on with the Rio Receiver here and here, but getting one to read a Shoutcast stream might be beyond my abilities. Am I missing anything else out there? A simple device that I could just cycle through different preconfigured streams with a remote would suffice."

nakhla writes: "This article at News.com details how Macromedia is expanding its Flash product to be more of an all-in-one web solution. Rather than relying on HTML codes to design web pages and embedding Flash as one component, Macromedia wants Flash to be used to design the entirety of a site. Pre-built components, such as scrollbars and buttons, are included to allow designers to write everything using the new Flash product. With websites becoming more and more complex, and the trend to move towards providing web services rather than application software, could something like this be the answer? The article also mentions how Macromedia is on a campaign to have its Flash plugin included in all Internet-compatible devices. How long before we see a Qt based plugin for the Qtopia handheld project?"

Slashback tonight with several updates and amplifications, starting with a nice report on the current state of the effort to put Linux into the heart of the German government, but also bits on Starcraft, cleaning up UNIX config, and Kerberos.

This deserves a hearty 'Jawohl!' DocSnyder writes: "Since the Bundestux campaign started collecting votes in favor of putting Free Software into the German parliament (Bundestag), more than 25000 people have done so. A lot of online discussions - in addition to Heise News and Linux-Community.de, even some Bundestag parties have put up their online forums - are very active to share user experience about GNU/Linux and Free Software. (Sorry for most of the linked sites speaking German, it's simply too much to translate at once.)

After several open letters and press releases have been exchanged between lobbyists and politicians, some information about a research performed by the German company Infora appeared on Heise News (english version), recommending an all-Microsoft infrastructure with the exception of some security-critical services like e-mail. The detailed paper is still not available.

An internal test (english version) between the Bundestag administration, SuSE, IBM and Microsoft confirmed that GNU/Linux and Free Software are in fact ready for the Bundestag's IT infrastructure, yet the testers don't like the copy&paste method used by KDE and recommend Windows for the desktops.

Last week, the Bundestag members (MdB) Jörg Tauss and Hans-Joachim Otto have been invited by Heise for an online chat with the community. While Jörg Tauss is a clear supporter of open standards and Free Software, Hans-Joachim Otto takes the internal test as well as Infora's research as primarily relevant for the coming decision.

On Saturday, MdB Uwe Küster summarized some details in an interview. He considered the decision - officially due Feb 28 - as almost finalized. The solution would show GNU/Linux on most servers, Windows XP and Office XP on the desktops, keeping proprietary data formats and lock-in interfaces up to the next upgrade cycle, which in fact would have been problem number one to solve.

All in all, the community has provided lots of experience, ideas and solution paths which finally seem to be largely ignored in the decision finding process towards the successor of a homogenous Microsoft Windows NT4 infrastructure, which has to be replaced until 2003 when Microsoft will no longer provide support for NT4."

That's a lot of cleaning up to do! maffew writes "A lot of feedback and ideas have been flying around since my article How to fix the Unix configuration nighmare was featured on freshmeat and slashdot. So we've created an ongoing web site and mailing list for people to continue discussing, organising, and hopefully in the end coding. It's all at unixconfig.sourceforge.net.

Meanwhile here's a link to the permanent home for the nightmare article. This is where I'm making revisions and adding links."

Raise your hand if this would mean seeing it for the 4th time ... Chris Brewer writes "In case you've been living on a different planet, The Fellowship of the Ring picked up Five Baftas, the British equivalent of the Oscars, including Best Director, Best Film, and Peoples Choice. During a live interview (Real only) after the awards, Peter Jackson announces that a preview for The Two Towers will be shown from the March 22 screenings of The Fellowship."

At long last ... something? If you've followed the strange relationship Microsoft has had with Kerberos, you may feel grateful to the anonymous coward who writes: "It would seem that Microsoft is granting the world a royalty-free, non-exclusive license to implement their Kerberos extension."

Here's some comfort for Starcraft players. An Anonymous Coward writes "As stated on Blizzard's battle.net service, the latest Starcraft patch supports UDP play, so some of the compelling reasons to use bnetd have been addressed. Whatever you may think of Blizzard and the DMCA, at least it shows Blizzard is listening to its fans."

tal197 writes: "More than two years since the ROX desktop (a desktop based around the filesystem) was last mentioned on slashdot, the second stable branch of the central ROX-Filer component has just been released. It's still pretty light and fast, despite all the changes, and integrates well with other desktops too."

tal197 writes: "More than two years since the ROX desktop (a desktop based around the filesystem) was last mentioned on slashdot, the second stable branch of the central ROX-Filer component has just been released. It's still pretty light and fast, despite all the changes, and integrates well with other desktops too."

tal197 writes: "More than two years since the ROX desktop (a desktop based around the filesystem) was last mentioned on slashdot, the second stable branch of the central ROX-Filer component has just been released. It's still pretty light and fast, despite all the changes, and integrates well with other desktops too."

tal197 writes: "More than two years since the ROX desktop (a desktop based around the filesystem) was last mentioned on slashdot, the second stable branch of the central ROX-Filer component has just been released. It's still pretty light and fast, despite all the changes, and integrates well with other desktops too."

Hit the link below to find links to assorted hacks done to the extremely cool ReplayTV 4000 PVR. Thanks to jptsetme for submitting links to hacks like hard drive upgrades, software to download mpegs, edit the guide, and systems under development to automate create of VCDs and DVDs from Replay's. It's exciting seeing so much headway being made so fast, and evidence that this is one heck of a machine. "The Replay hackers at AVS forum have done an amazing job on the new ReplayTV 4000's. You can now do some very cool things with this new PVR.

You can increase recording space (by either replacing the existing drive, or adding an additional one.) This has, of course, been done with Tivos and older Replays in the past. Not only has this hack been adapted for the Replay4000 model (including custom sized photo partitions and preserving existing shows), but Replay has also recently released new software that removes the previous 137G per drive limitation, so you can now turn any ReplayTV4000 into a 320G model with a couple of 160G drives and a PC (Linux, Win2k, XP, or with a Linux boot disk on an x86 box with a good enough BIOS to recognize the drive size.)
http://rtvpatch.sourceforge.net/

But, you might decide you don't need to open the box at all, since you can now offload your shows to your PC and then serve them back to the ReplayTV4000 with your PC masquerading as another ReplayTV4000 on your local network, giving you nearly limitless storage capacity. [Note: this does not use the internet sharing feature, which is so slow over typical broadband as to be practically unusable. This is streaming the show in realtime from your PC back to your Replay4000, using the same mechanism two Replays use to stream shows back and forth over your local network.]

ReplayPC (C/C++, Windows, Linux, Mac. A simple text mode utility for extracting mpg files from ReplayTV4000 PVRs via TCP/IP)
http://replaypc.sourceforge.net/

Replayer (Pure Java. Java GUI utility allows you to extract mpg files from your ReplayTV 4000 to your PC)
http://www.forbesfield.com/replayer.html

Replay Server (built on PHP for Apache. Allows you to serve downloaded shows to a ReplayTV (on your LAN only) from your PC as if your PC was a ReplayTV)
http://206.124.140.12/rtv/

SwapDV (J++, windoze only. Allows you to download shows from your ReplayTV 4000, serve downloaded shows as if your box was a ReplayTV 4000, and edit the "guide" provided by your PC. i.e. capabilities of both Replayer and Replay Server, but only for Windows.)
http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=116035

A number of users are also working on burning shows to VCD, SVCD, XSVCD and DVD, with moderate success.

http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=115338
http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=106437

Lastly, there has also been a hack developed to remove macrovision from the old Panasonic Showstoppers (effectively transforming them into ReplayTV3xxx machines.)
http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=118170."

Hit the link below to find links to assorted hacks done to the extremely cool ReplayTV 4000 PVR. Thanks to jptsetme for submitting links to hacks like hard drive upgrades, software to download mpegs, edit the guide, and systems under development to automate create of VCDs and DVDs from Replay's. It's exciting seeing so much headway being made so fast, and evidence that this is one heck of a machine. "The Replay hackers at AVS forum have done an amazing job on the new ReplayTV 4000's. You can now do some very cool things with this new PVR.

You can increase recording space (by either replacing the existing drive, or adding an additional one.) This has, of course, been done with Tivos and older Replays in the past. Not only has this hack been adapted for the Replay4000 model (including custom sized photo partitions and preserving existing shows), but Replay has also recently released new software that removes the previous 137G per drive limitation, so you can now turn any ReplayTV4000 into a 320G model with a couple of 160G drives and a PC (Linux, Win2k, XP, or with a Linux boot disk on an x86 box with a good enough BIOS to recognize the drive size.)
http://rtvpatch.sourceforge.net/

But, you might decide you don't need to open the box at all, since you can now offload your shows to your PC and then serve them back to the ReplayTV4000 with your PC masquerading as another ReplayTV4000 on your local network, giving you nearly limitless storage capacity. [Note: this does not use the internet sharing feature, which is so slow over typical broadband as to be practically unusable. This is streaming the show in realtime from your PC back to your Replay4000, using the same mechanism two Replays use to stream shows back and forth over your local network.]

ReplayPC (C/C++, Windows, Linux, Mac. A simple text mode utility for extracting mpg files from ReplayTV4000 PVRs via TCP/IP)
http://replaypc.sourceforge.net/

Replayer (Pure Java. Java GUI utility allows you to extract mpg files from your ReplayTV 4000 to your PC)
http://www.forbesfield.com/replayer.html

Replay Server (built on PHP for Apache. Allows you to serve downloaded shows to a ReplayTV (on your LAN only) from your PC as if your PC was a ReplayTV)
http://206.124.140.12/rtv/

SwapDV (J++, windoze only. Allows you to download shows from your ReplayTV 4000, serve downloaded shows as if your box was a ReplayTV 4000, and edit the "guide" provided by your PC. i.e. capabilities of both Replayer and Replay Server, but only for Windows.)
http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=116035

A number of users are also working on burning shows to VCD, SVCD, XSVCD and DVD, with moderate success.

http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=115338
http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=106437

Lastly, there has also been a hack developed to remove macrovision from the old Panasonic Showstoppers (effectively transforming them into ReplayTV3xxx machines.)
http://www.avsforum.com/avs-vb/showthread.php?s=&a mp;threadid=118170."

An email fluttering around a few mailing lists has been submitted in various forms here today. It's about changes to the SourceForge terms of service. Some relevant links unclude the old terms, new terms, old privacy statement, new privacy statement and contact for "questions or concerns" (Patrick McGovern, Site Director). Obviously since SF is owned by the same parent company as Slashdot, I'm biased and corrupt and you should ignore my opinions on the subject, but while I don't particularly like this any more then anyone else, I also don't think it's the huge deal that others are making of it. Especially considering projects aren't paying for the free service. You get what you pay for after all. I have attached a summary to this article of the changes that are being called into question if you don't want to do a mental diff on the links above.

This list was submitted by a few different users and was apparently originally posted to several mailing lists, although I don't know who actually originally wrote it. I just quote it here for reference.

1. They can henceforth change the terms without notice, just by posting the new terms on the website. (Currently they are obliged to give 15 days notice by email, a period that we are currently in for this change.)
2. They can henceforth remove user accounts without giving a reason. (Currently they are obliged to have a reason, though the set of acceptable reasons is open-ended.)
3. They're no longer obliged to make the contents of a deleted account available to its owner. (There was previously a "reasonable effort" clause to that effect.)
4. They're no longer obliged to provide notice of changes to the privacy policy, unless the changes are "substantive". (Currently they are obliged to provide notice of any change.)
5. The privacy policy is acquiring a disclaimer that amounts to "this is not true". It actually disclaims the entire privacy policy.

An email fluttering around a few mailing lists has been submitted in various forms here today. It's about changes to the SourceForge terms of service. Some relevant links unclude the old terms, new terms, old privacy statement, new privacy statement and contact for "questions or concerns" (Patrick McGovern, Site Director). Obviously since SF is owned by the same parent company as Slashdot, I'm biased and corrupt and you should ignore my opinions on the subject, but while I don't particularly like this any more then anyone else, I also don't think it's the huge deal that others are making of it. Especially considering projects aren't paying for the free service. You get what you pay for after all. I have attached a summary to this article of the changes that are being called into question if you don't want to do a mental diff on the links above.

This list was submitted by a few different users and was apparently originally posted to several mailing lists, although I don't know who actually originally wrote it. I just quote it here for reference.

1. They can henceforth change the terms without notice, just by posting the new terms on the website. (Currently they are obliged to give 15 days notice by email, a period that we are currently in for this change.)
2. They can henceforth remove user accounts without giving a reason. (Currently they are obliged to have a reason, though the set of acceptable reasons is open-ended.)
3. They're no longer obliged to make the contents of a deleted account available to its owner. (There was previously a "reasonable effort" clause to that effect.)
4. They're no longer obliged to provide notice of changes to the privacy policy, unless the changes are "substantive". (Currently they are obliged to provide notice of any change.)
5. The privacy policy is acquiring a disclaimer that amounts to "this is not true". It actually disclaims the entire privacy policy.

An email fluttering around a few mailing lists has been submitted in various forms here today. It's about changes to the SourceForge terms of service. Some relevant links unclude the old terms, new terms, old privacy statement, new privacy statement and contact for "questions or concerns" (Patrick McGovern, Site Director). Obviously since SF is owned by the same parent company as Slashdot, I'm biased and corrupt and you should ignore my opinions on the subject, but while I don't particularly like this any more then anyone else, I also don't think it's the huge deal that others are making of it. Especially considering projects aren't paying for the free service. You get what you pay for after all. I have attached a summary to this article of the changes that are being called into question if you don't want to do a mental diff on the links above.

This list was submitted by a few different users and was apparently originally posted to several mailing lists, although I don't know who actually originally wrote it. I just quote it here for reference.

1. They can henceforth change the terms without notice, just by posting the new terms on the website. (Currently they are obliged to give 15 days notice by email, a period that we are currently in for this change.)
2. They can henceforth remove user accounts without giving a reason. (Currently they are obliged to have a reason, though the set of acceptable reasons is open-ended.)
3. They're no longer obliged to make the contents of a deleted account available to its owner. (There was previously a "reasonable effort" clause to that effect.)
4. They're no longer obliged to provide notice of changes to the privacy policy, unless the changes are "substantive". (Currently they are obliged to provide notice of any change.)
5. The privacy policy is acquiring a disclaimer that amounts to "this is not true". It actually disclaims the entire privacy policy.

An email fluttering around a few mailing lists has been submitted in various forms here today. It's about changes to the SourceForge terms of service. Some relevant links unclude the old terms, new terms, old privacy statement, new privacy statement and contact for "questions or concerns" (Patrick McGovern, Site Director). Obviously since SF is owned by the same parent company as Slashdot, I'm biased and corrupt and you should ignore my opinions on the subject, but while I don't particularly like this any more then anyone else, I also don't think it's the huge deal that others are making of it. Especially considering projects aren't paying for the free service. You get what you pay for after all. I have attached a summary to this article of the changes that are being called into question if you don't want to do a mental diff on the links above.

This list was submitted by a few different users and was apparently originally posted to several mailing lists, although I don't know who actually originally wrote it. I just quote it here for reference.

1. They can henceforth change the terms without notice, just by posting the new terms on the website. (Currently they are obliged to give 15 days notice by email, a period that we are currently in for this change.)
2. They can henceforth remove user accounts without giving a reason. (Currently they are obliged to have a reason, though the set of acceptable reasons is open-ended.)
3. They're no longer obliged to make the contents of a deleted account available to its owner. (There was previously a "reasonable effort" clause to that effect.)
4. They're no longer obliged to provide notice of changes to the privacy policy, unless the changes are "substantive". (Currently they are obliged to provide notice of any change.)
5. The privacy policy is acquiring a disclaimer that amounts to "this is not true". It actually disclaims the entire privacy policy.

An email fluttering around a few mailing lists has been submitted in various forms here today. It's about changes to the SourceForge terms of service. Some relevant links unclude the old terms, new terms, old privacy statement, new privacy statement and contact for "questions or concerns" (Patrick McGovern, Site Director). Obviously since SF is owned by the same parent company as Slashdot, I'm biased and corrupt and you should ignore my opinions on the subject, but while I don't particularly like this any more then anyone else, I also don't think it's the huge deal that others are making of it. Especially considering projects aren't paying for the free service. You get what you pay for after all. I have attached a summary to this article of the changes that are being called into question if you don't want to do a mental diff on the links above.

This list was submitted by a few different users and was apparently originally posted to several mailing lists, although I don't know who actually originally wrote it. I just quote it here for reference.

1. They can henceforth change the terms without notice, just by posting the new terms on the website. (Currently they are obliged to give 15 days notice by email, a period that we are currently in for this change.)
2. They can henceforth remove user accounts without giving a reason. (Currently they are obliged to have a reason, though the set of acceptable reasons is open-ended.)
3. They're no longer obliged to make the contents of a deleted account available to its owner. (There was previously a "reasonable effort" clause to that effect.)
4. They're no longer obliged to provide notice of changes to the privacy policy, unless the changes are "substantive". (Currently they are obliged to provide notice of any change.)
5. The privacy policy is acquiring a disclaimer that amounts to "this is not true". It actually disclaims the entire privacy policy.

An email fluttering around a few mailing lists has been submitted in various forms here today. It's about changes to the SourceForge terms of service. Some relevant links unclude the old terms, new terms, old privacy statement, new privacy statement and contact for "questions or concerns" (Patrick McGovern, Site Director). Obviously since SF is owned by the same parent company as Slashdot, I'm biased and corrupt and you should ignore my opinions on the subject, but while I don't particularly like this any more then anyone else, I also don't think it's the huge deal that others are making of it. Especially considering projects aren't paying for the free service. You get what you pay for after all. I have attached a summary to this article of the changes that are being called into question if you don't want to do a mental diff on the links above.

This list was submitted by a few different users and was apparently originally posted to several mailing lists, although I don't know who actually originally wrote it. I just quote it here for reference.

1. They can henceforth change the terms without notice, just by posting the new terms on the website. (Currently they are obliged to give 15 days notice by email, a period that we are currently in for this change.)
2. They can henceforth remove user accounts without giving a reason. (Currently they are obliged to have a reason, though the set of acceptable reasons is open-ended.)
3. They're no longer obliged to make the contents of a deleted account available to its owner. (There was previously a "reasonable effort" clause to that effect.)
4. They're no longer obliged to provide notice of changes to the privacy policy, unless the changes are "substantive". (Currently they are obliged to provide notice of any change.)
5. The privacy policy is acquiring a disclaimer that amounts to "this is not true". It actually disclaims the entire privacy policy.

Jason writes: "RealTech-VR, creators of the V3X 3D engine, also developed a Direct3D-to-OpenGL wrapper and they have now open sourced their work. They are seeking for more hackers to help porting the wrapper to Linux and MacOS. A lot of the functionality of Direct3D is already ported but it still needs quite some work. Get the scoop at OSNews."

polymath69 asks: "Living on the edge of Debian unstable means that updates sometimes break stuff, occasionally to an extent that is difficult to recover from. This got me thinking about treating the entire set of mounted filesystems as a transactional database. Mark state, try something which might be dangerous, test, and approve (commit) or panic (rollback). Obviously some filesystem support would be required, but with ext3 and reiserfs available, maybe the potential is already there. And such a system would need lots of disk space, but these days that's a demand easily granted. There's lots out there on process-level checkpointing, and even some stuff about system-level checkpointing, but all I've found on that was in the context of saving and restoring processes for a system freeze and restore. But I couldn't find anything on Google or SourceForge about doing this sort of temporary branching in the filesystem. Is this idea feasible? Is anyone working on it?"

josephfeller writes: ""Meeting Challenges and Surviving Success: The 2nd Workshop on Open Source Software Engineering" will be held on May 25, 2002 as part of the 24th International Conference on Software Engineering (http://www.icse-conferences.org/2002/). Full details and the Call for Papers are at http://opensource.ucc.ie/icse2002/."

It's been a while since the last iteration of Slashback, so tonight there are updates and errata on several recent stories. Read on below to find out more about Harlan Ellison's battle with copyright infringers, why modding your Linksys WAP might not be as cool as you thought, internet access in Wellington, New Zealand, the results of the NASA poll on space priorities and more.

How many anecdotes? Drestin writes "Looks like all the flame mail and traffic to WinInfo for the recent 'Windows more secure than Linux' article prompted it's author, Paul Thurrott, to reply with his opinion. He tells us to think with our heads, not our hearts."

Several readers complained about my original (since updated) headline, and they're all right. As Kathleen Ellis put it:

"I find this title to be rather misleading. Bugtraq is a security mailing list that happens to be archived on security focus' web site (it is also moderated by one of SecurityFocus' founders, but bugtraq content is not subjected to SecurityFocus editorial control), and WinInformant is really the one making the assertion, based on their analysis of Bugtraq list traffic.

As an occasional SecurityFocus reader (and occasional writer), I am particularly concerned that your headline (and the attribution of the assertion to SecurityFocus) will make SecurityFocus look bad. As a professional in "the industry" and as someone who follows computer security very closely, I am confident most sensible members of the security community will quickly realize that the assertion is of extremely dubious merit and your attribution could make SecurityFocus look extremely foolish."

Here, why don't you pay? TheGeneration writes "Recently Salon had an article about public money being used to write private code (ie, for a university.) The article apparently moved Richard Stallman enough to write a response and opinion. Stallman sites his own reason for leaving MIT such as his inability to write free software while under their employ. Stallman discusses ways to sidestep University control of free software, and how to get admins to allow software developed under them to be licensed as free software."

For your personal museum's display cases. airrage writes "As a follow-up to the early design docs for some of the earliest ATARI games. More fascinating, is the 30 Secrets of Atari. Did Jobs ever do any work? Finally, the creater of ATARI's adventure has a web site. Check out his work on virtual nano-technology and his presentation on creating Adventure. They sure didn't have much to work with did they?"

Connecting everything to everything. seanadams.com writes: "Our company has just published the firmware source code for our SliMP3 Ethernet MP3 player, previously reviewed on Slashdot. The firmware, written entirely in assembler, includes our super-compact TCP/IP stack for the 8-bit PIC microcontroller. The license allows for non-commercial use, so I hope this will be of interest to PIC hackers! If you're interested in experimenting with Ethernet and TCP/IP on the PIC, we will have an integrated PIC+CS8900 module and development kits available next month."

Next stop is telepathy. ruvreve writes "An update to a previous article featured here on Slashdot. Wellington is offering not only city-wide gigabit ethernet they are also offering wireless access. Currently it is still 11Mbps but plans are to make it 56Mbps down the road."

Not someone I'd want to mess with anyhow. yndrd writes "As a follow up to a previous Slashdot story about Harlan Ellison's feud with what he considers to be pirates of his work, Ellison has reached a settlement with Critical Path Inc. who will create software that enables Ellison to immediately delete postings of his work on the RemarQ service. The (somewhat) full article is here. He's still ready to rumble with America Online, the other party in his lawsuit."

The dirty side of quick n' dirty. nailgun writes: "http://www.maokhian.com/wireless/wap11.html has before-and-after oscilloscope traces of the spectra of a power-boosted (hacked) Linksys WAP. From the traces it is apparent that power-boosting does no good, since all (or nearly all) additional power is blasted out in neighboring frequencies. Boost your Linksys and you'll step on all other WAPs in the neighborhood. These are cool pictures too."

This took a survey to determine?An Anonymous Coward writes "Remember the Space Survey Thread? Where NASA was asking for our opinion on where to go in space? Well, the results are in. Lo and behold, we all want to go to Mars."

DarkVein writes "My question is twofold. First, with the introduction of WebFonts from W3C, are there any projects underway to develop a real Web Font format, or are Type1 and Truetype thought to be sufficient? Secondly, I seem to be at a loss to find any decent and open font creation tools, especially ones capable of Unicode. The best I've found is GETO which seems to have been abandoned about a year and a half ago, without notice. I've had a long standing desire to get my feet wet designing one or two decent Unicode fonts, but most of the options seem to only be available for MacOS9, Win32 and require far higher prices."

A not-so Anonymous Coward asks: "I'm the lead developer of SciGraphica, an open source application for scientific graphics that runs under Linux, and is based on Microcal Origin, the commercial application for Windows. When we contacted this company, they let us know that a port for Linux or other operating systems was not in their plans, and that they were not willing to make their proprietary file format available. However, we realized that it is in fact easy to reverse engineer to create a filter that would allow our program to read Origin files. Are we walking into a case of patent infringement, or this is a legitimate solution? If this is problematic, is there a way to allow people to legally have access to the filter?"

A not-so Anonymous Coward asks: "I'm the lead developer of SciGraphica, an open source application for scientific graphics that runs under Linux, and is based on Microcal Origin, the commercial application for Windows. When we contacted this company, they let us know that a port for Linux or other operating systems was not in their plans, and that they were not willing to make their proprietary file format available. However, we realized that it is in fact easy to reverse engineer to create a filter that would allow our program to read Origin files. Are we walking into a case of patent infringement, or this is a legitimate solution? If this is problematic, is there a way to allow people to legally have access to the filter?"

A reader writes "The new Z-series mainframe for Linux, which costs $400,000 and is aimed at processing transactions at large businesses, is IBM's first mainframe computer sold without IBM's traditional z/OS mainframe operating system. More info at the IBM zSeries page" This is something that IBM and others of Big Iron vendors of *NIX have said - as Linux grows in maturity, they want to replace their *NIX with Linux. However, there's still work to be done in that area.

sofar writes: "Amazon finally makes a profit. Well, only $ 5mln, but maybe you can actually earn something on your stock now. At 1c a share it's no pension fund in Florida yet." I wonder how much of that profit represents 1-click licensing fees.