Slashdot Mirror
RedHat, Fujitsu Enter Into Marketing Agreement
andyring writes "According to Cnet, RedHat and Fujitsu signed a partership agreement where the companies will jointly develop and market for Fujitsu's products. Fujitsu hs a strong presence in Asia, a place Microsoft has been trying to cultivate."
Used to be when you bought floppy disks, sometimes you could get a bonus floppy disk that had a MS entertainment pack on it.
:)
Imagine all hard disks coming preloaded with a self-configuring Linux distro. That would be cool.
I've had enough abrasive sigs. Kittens are cute and fuzzy.
This could be a very good for linux....it provides a very large scale devlopment enviornment for linux...and lead to more submissions, and review of code...not to mention more discoverys of bad design and security holes...
maybe redhat will find out that by having everything tunred on by defaut, and having to work for 2 hours to turn it all off really pisses off sysadmins.
I've been finding redhat to be a progressivly more and more annyoing linux distro, but this could be their chance to turn things around. Personally i opt for gentoo....small, secure, and works very well. With the amount of attention they will get from devlopment with this, Red hat could follow that line.
at the very least i hope they will get rid of the "rpm hell" that people go thru when you go to upgrade major components.
A side effect of this could well be to reduce the variability of hardware and drivers - if only because the lack of specific drivers makes linux less forgiving of random throwing together of components. They'll HAVE to try harder if they want it to work.
Paul "Say no to feeping creaturism"
Are we speaking of this world region where 1 licence is usually enough to cover the needs of thousands of servers ? THE Place where information, if not free, comes dirt cheap at 1$/cd ?
And you tell me Microsoft is trying to cultivate it's business there ?
You mean, they sold a cluster and asked themselves why they didn't get that second Advanced Server Licence Order ? 8p
It takes 40+ muscles to frown, but only four to extend your arm and bitchslap the motherfucker
This is the more interesting part of the story. Fujitsu are going to pay for some engineers to work at RedHat offices, improving "performance, stability and the ability to run on large servers with heavy processing loads."
I am very encouraged by the number of companies prepared to take this step, bearing in mind that the GPL forces them to make the changes available for everyone.
I've long been puzzled as to why a company should pay for improvements to a system, if they then have to make these available to their competitors. I think perhaps there are two reasons. First, Linux is not Windows. Making Linux a better competitor to Windows helps Fujitsu more than they are hurt by having to give code away.
Secondly, companies focus on their own area. A company that makes, for example, 8-way AMD servers would focus on that area. Their competitors would have access to the code for running well on 8-way AMD servers, but if they don't make them it doesn't help.
Fujitsu hs a strong presence in Asia, a place Microsoft has been trying to cultivate.
From the Article:
it does have a strong position in Asia, where Red Hat is trying to expand.
I know this is Slashdot, but modification of the article line to mention Microsoft(incorrectly) in the story just for attracting readers is not doing a great deal to improve anything. I like to bash Microsoft with jokes once in a while, but notes like this one are to be criticized, IMHO.
getSexySig();
I like what RedHat did - and what Fujitsu did even more. Looks like buyers of Fujitsu servers can expect good hardware support on Linux-based systems. I'm impressed that Fujitsu hired RedHat to do the work, and I'm equally impressed that RedHat had the brains to seek out a new revenue source.
I'm not sure this article has much to do with the SCO situation though.
-- $G
Linux is starting to suffer a fate that I feared was coming for a long time. It's no longer cool.
It was, for a time, cool to run Linux because it was the only fully POSIX (depending on how rigorous your POSIX definition was) OS for home computers that had all of the usual bells and whistles (X, GNU tools, etc) that also had freely available source.
386BSD came along at about the same time, but was really only usable a bit after Linux so Linux got a bit of a mind-share head start (otherwise we'd all be running one of the BSDs by now).
Today, progress on Mach still continues under Darwin; HURD is moving to a new Microkernel that's much smaller and "hipper"; Open/NetBSD have adopted a very promising new VM model; and worst of all (in terms of Linux's geek appeal) Linux is a massive corporate success in dozens of large niches.
This is a huge win for the Free Software cause, but for Linux it means that the now super-broad OS is starting to show its faults. There are very few people who currently seem to be thinking about the big picture in terms of how the whole OS works in any given incarnation. Worse, the hack-value of making the bettter diver for hardware XYZ has reduced significantly, and most of the kernel work I see happening is not on tuning older drivers for new versions so much as incorporating brand new and interesting hardware, or working on kernel-wide systems like VM, security or scheduling
Red Hat's partnership with hardware companies like Fujitsu (maker of laptops, hard drives and more) is excellent because it brings the hardware vendors to the table to pick up some of that slack and frees Red Hat developers to focus on the big picture. Much as they've taken heat for it, RH has done a lot of good in thinking of the dekstop as a whole rather than as a potential spot to plug in vendors A, B or C (or should I say G, K or W). What they need to do now is keep moving down the chain. Standardize all of the system documentation on ONE format and convert everything to it (personally, I recommend a modified POD, which is what Perl uses, and could easily be modified to produce useful texi and Gnome SGML, while it already produces man, text and HTML). IMHO "man foo" and "info foo" and bringing up the Gnome help viewer should all give access in one, consistent (though UI-distinct) way with the same, complete documentation. Why isn't that the case? Because no one has time to work at that level (Kudos to the LFS people for taking up my challenge on that point last week, and starting to work on a port of the OpenBSD man pages to the Linux tools!)