Slashdot Mirror

LNUX isn't totally worthless.

Yet.

Nor will you see Larry being led away in handcuffs any time soon. They need the cell space for someone else.

--

LNUX isn't totally worthless.

Yet.

Nor will you see Larry being led away in handcuffs any time soon. They need the cell space for someone else.

--

Yup, there's another version over on c|net as well. Tridgell and Allison are now on the VA NAS team. [ VA Systems press release ]

Try buying a MP AMD system from your local vendor. If a corporation needs SMP, they _must_ buy Intel (for x86 servers).

Recent Athlon processors use a bus protocol similar to that of Compaq Alpha processors. Somebody else wrote that VA Linux Systems (Slashdot's parent company) is building an Athlon-based SMP server and patching Linux to improve its SMP performance. But still, can you imagine...

...a Beowulf cluster of these? You can get SMP without having multiple processors on one motherboard. Simply throw a bunch of small (g4cube-size) mobos into a rack (I forget which company is doing this), run a load balancing firewall (OpenBSD, of course) on one and server software on the rest, and you effectively have SMP. Besides, static content serving (well over half of a typical web site's throughput is ads or other images) is I/O bound; that is, it's limited primarily by bandwidth to the public network, NOT by CPU speed.

Brought to you by VA Linux Systems, The World's Linux Leaders!

How does Texas have authority over computers sold to Texans by out-of-state PC makers? Of course CPQ and DELL are Texas makers, but everyone's favorite PC maker, based in California, won't be affected as it's engaged in interstate commerce, clearly the authority of the US Congress.

Kiddi3z will always be a nuisance, but my personal feeling is that the parties responsible for the death of the Internet will be a handful companies trying to milk or control it...

(end comment) */ }

Go ahead, click it

--
Ellison: How are you gentlemen !! All your database are belong to us

I'm running it, thanks to this page.

However, they offer clear conditions. First, they don't guarentee upwards-compatibility, that is code compiled against glibc 2.2 working with 2.1. Second, C++ is currently off limits (which will change with gcc 3.0). Third, it applies only to shared versions of the library. Fourth, private internal interfaces are off limits.

The Oracle problem is simple: they're using static libraries (ie, ar archives of object files). This doesn't work because symbol versioning (the magic that enables compatibility in shared libraries) isn't implemented for object files. HJ Lu has a page on this issue and possible resolutions.

90% of other compatibility problems result from using private interfaces. This happened to Star Office a while back.

Better yet, leave one machine of each model you configure running in your showroom all the time with the tool running on it.

Even if you sell machines preinstalled with Windows, let your customers know that they're getting machines that are of more robust hardware quality - if they're pass these tests thrashing the system under Linux, well you can figure it'll be pretty reliable running Word under Windows 98.

Also have a bin near the door full of "Free - take one" floppies duplicated with Memtest86 - and test the memory you install with Memtest86 before giving it to a customer (to some extent it should validate CPU's and motherboards as well).

Ask your customers to take memtest86 home and try it out on the machines they may already have. (You boot off the floppy to run the test; on Linux systems you can install it in LILO or Grub).

They may get a suprise - I have a PC-133 DIMM that failed memtest86 when the machine was brand-new from a small PC shop like yours; I doubt they tested their memory with more than the BIOS test - my BIOS test still doesn't show any errors, but memtest86 consistently shows the same error on this DIMM.

Michael D. Crawford
GoingWare Inc

Better yet, leave one machine of each model you configure running in your showroom all the time with the tool running on it.

Even if you sell machines preinstalled with Windows, let your customers know that they're getting machines that are of more robust hardware quality - if they're pass these tests thrashing the system under Linux, well you can figure it'll be pretty reliable running Word under Windows 98.

Also have a bin near the door full of "Free - take one" floppies duplicated with Memtest86 - and test the memory you install with Memtest86 before giving it to a customer (to some extent it should validate CPU's and motherboards as well).

Ask your customers to take memtest86 home and try it out on the machines they may already have. (You boot off the floppy to run the test; on Linux systems you can install it in LILO or Grub).

They may get a suprise - I have a PC-133 DIMM that failed memtest86 when the machine was brand-new from a small PC shop like yours; I doubt they tested their memory with more than the BIOS test - my BIOS test still doesn't show any errors, but memtest86 consistently shows the same error on this DIMM.

Michael D. Crawford
GoingWare Inc

Not just IBM, but SGI, CRAY, Compaq, VA and Penguin are all hardware vendors putting serious resources to making linux better.

See, I haven't contributed anything to the Linux community at all

If you feel guilty, you could

• Write software for the GNU/Linux system.
• Write documentation for the GNU/Linux system, especially if you speak human languages other than American.
• Buy a boxed GNU/Linux distribution. This funds development of the GNU/Linux system.
• Donate to Free Software Foundation. This funds development of GNU, the POSIX layer that runs on Linux (and on HURD). You can even specify FSF on your United Way "specific request."
• Buy a computer from VA Linux Systems or Penguin Computing. This supports hardware manufacturers who are not in bed with Microsoft <cough>winmodems</cough>.

1. True, and so what? Most opensource programmers may well work as closedsource programmers during the day. That would only be a problem if you believed closedsource software was somehow evil.
2. Even if you did believe that closedsource software was evil, again, so what? Richard Stallman-- an opponent of closedsource-- said this in his seminal paper on the subject, The Gnu Manifesto :

   >"Won't programmers starve?"

   >I could answer that nobody is forced to be
   >a programmer. Most of us cannot manage to get
   >any money for standing on the street and making
   >faces. But we are not, as a result, condemned to
   >spend our lives standing on the street making faces,
   >and starving. We do something else.

3. In any case, there is money to be made out of opensource-- in support, in distribution, in media. How else would RedHat and VA Linux (and so on and on) survive as commercial entities?

The best way to contact us is via email to community@valinux.com

--Kit
Director of Community Projects

Look folks, I believe that this is the real reason why the PlayStation will be gobbled up by the X-Box. Doesn't this sound rather like BetaMax all over again? It does to me. If Microsoft could put the knife to the throat of closed standards like OS/2, or Java, who's to doubt that they could also kill the PlayStation/2, too?!? Let's hop to it, folks! Let's beat Sony AND Microsoft, by making a Linux game console within the year! I vote that VA Linux Systems do it, as the Linux Hardware Leader for the Linux Community!!

What the enterprise customer does is set up an initial install with the OS and application and then clone it to new PCs with Norton Ghost. (I recently used the personal edition for $99 to back up a freshly installed dual-boot windows system and I think it's just dandy; now comprehends linux ext2 filesystems).

The problem is that if the enterprise customer bought the PC from a tradition Microsoft OEM, it will come preinstalled with Windows, and they'll be required to pay twice for it, as discussed at Paying Twice for Windows and Microsoft licensing deals confuse customers, study says.

Eventually Microsoft yielded somewhat, but only for the largest customers, as discussed in Commentary: Microsoft hasn't totally reversed its policy on fees.

This is a problem because traditional Microsoft OEMs are contractually obligated by Microsoft to install some operating system on every machine they sell. Microsoft claims that this is to cut down on piracy, but it has the added effect of discouraging people from trying out other operating systems.

The solution? Encourage the enterprise customers to purchase hardware with no operating system at all installed on it from OEMs that have no relationship with Microsoft. Then the customer can do their Ghost cloning without any worry about double license fees. This will work well both for the large enterprise customers that may have been helped by the minor adjustment in Microsoft's policy, as well as the smaller enterprise that were no helped out.

If you work for one of the traditional linux hardware vendors, I'd like to suggest to you that you view Microsoft Windows enterprise customers as a new market opportunity, not just to sell Linux to, but just to sell naked hardware to. If the hardware has no OS installed at all, there's no OS support issues to be concerned with, as there might be if you put some Linux distro on it.

Consider also that although trying to sell a machine bundled with Linux might meet resistance from a company that really does need its Windows applications to do business, selling naked hardware and emphasizing savings on Windows license fees is an easy foot in the door. Once you establish a rapport with the customer you'll have a better chance to upsell them to Linux.

Also consider that if Microsoft OEMs start losing significant hardware sells to folks like VA Linux Systems, Penguin Computing, Tuxtops and the screwdriver shops, they'll be a little more aggressive about getting Microsoft to back down on requiring an OS to be installed.

Of course, an alternative to the traditional OEM vendors is to just preinstall Debian and include a clause in the contract stating that the preinstall OS software is not supported by anyone. That just pretty much screws Microsoft up the Yin-Yang.

...but what the hey, I'm bored.

No matter how you look at them, Naked PCs are bad for your customers.

And bad for our bottom line and ability to inflate user numbers.

Which means they are also bad for you.

Man, tell me if that doesn't read like a not-so-thinly-veiled threat. When can I expect "the boys" to hit the computer shops about ten blocks away from me?

Politely decline to expose your buyers or their businesses to such troubles.

So M$ is encouraging OEMs and indie shops to refuse to sell bare computers to anyone who doesn't want to pay the M$ tax. This is probably the most laughable statement in the whole thing; M$ blatantly telling computer-retailer business owners how to run their business.

Sell your PCs fully equipped with legally licensed operating systems preinstalled.

You mean like this one?

I don't suppose the DoJ can bring up new evidence in the appeal case, because this looks like a rather pointed warning to OEMs and other computer sellers to install Windows and pay the tax or else. How else do you say 'smoking gun"?

And the part I don't get...or else what? Since when did it become illegal to sell a computer without an OS? Will MS start going after those who sell "naked PCs" as "accessories to piracy" now? I hope they do and prove once and for all how much they really care for competition.
-------------

There are several web servers that may outperform apache on serving static content. Search freshmeat for possibilities.

Dell themesleves (with RedHat) have claimed record-setting performance using their "Tux" kernel-space web server daemon. (again for static content)

If you need to support more general content, then look at the flexibility in apache (and other Unix web servers) to support a wide array of different services and the ability to tune apache.

There's more to performance than just performance. Can you tune the server? How easily? Content management? Scalability to multiple servers/load balancing? Integration with database back-ends or java servelets? Security! Server management? Ease of upgrading? Paltform-dependancy? Licensing costs?

IIS ties you to one vendor's solution FOREVER. You can migrate an Apache site onto just about any O/S and hardware platform. This may or may not be important to your decision.

Depending on what you need and the skills your company possess, Apache may be an excellent choice or just OK.

I know you asked for benchmark data; Sorry I don't have a link to any and benchmarks are usually heavily cooked beforehand anyway (such as the Dell/RedHat example). IIS has a marketiing-savvy corporation behind it. Apache has the largest installed base on the planet and thousands of success stories.

There may be some info at the main apache web site, Apache Today, the apache week and oreilly sites (don't have url handy).

Oh, unless your firm is tied to buying only Dell, look at the offerings from VA Linux and the other linux vendors - I know VA can provide specific tuning suggestions.

This is not too supprising, considering that VA Linux (Slashdot's parent company) donated Kuro5hin's hardware.

VA Linux only bundles Matrox and G400 cards. Therefore Slashdot, a subsidiary of Andover.net, itself a subsidiary of VA Linux, is implicitly telling you not to buy 3dfx, politics be damned.

Correction:
This looks very interesting -- as a recent Debian recipient (victim?) at the hands of an expert, I must say the install is pretty intimidating. This sounds like a smart area to focus on, but what would an ideal installer consist of, anyhow? Give examples, double space;)

I believe you meant to say:
Debian is the #1 VA Linux distribution.

Just wanted to let everyone else know that a mistake occured.
------------

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

Related links: 1 2 3 4 5 6 7 8 9 10

There is a patch that should make it into Linux 2.4. It is included in VALinux's unsupported kernels from HJL (as well as Ext3 and NFS, and don't forget the losetup/mount RPMs as well).

Otherwise, I just use Midnight Commander (mc) to peer into and even modify TAR, TAR.GZ, CPIO, RPM and other files. In fact, if you're serious about working on compressed files, why not get into RPM where you can script (among other things)?

-- Bryan "TheBS" Smith

VA Linux Systems pays Malda and Hemos. VA Linux also runs SourceForge.
<O
( \
XGNOME vs. KDE: the game!

Big Idea made the same decision not too long ago.
I never bothered to figure out what the cost/performance ratio was between the two platforms. I just knew that Linux was a lot cheaper.

The thing that suprises me is that they only have 16 boxes... and that this is newsworthy. We have 42 (with almost exactly the same config) and plan on ordering more in the near future.

One other difference is that they are using RenderMan and we are using Maya's renderer, which has recently been ported to Linux. For the type of work that we do, Maya is more than enough for us. Also, we hardly have any frame times of an hour... if we do, I yell and scream to get it cut down. The difference is that we are only rendering to 724x486. The use a higher resolution for the big screen, we only have to wory about NTSC for now.

The prices quoted in the article seem to be inflated a bit too. Unless they are quoted in the NZ dollar and that is about a 2-1 with the American. Octanes should be about $20k in the States. Linux boxes similarly configured, from VA, which we use, instead of SGI, are in the $5-6k range.

The performance boost that we have got from adding the Linux boxes is amazing. We went from being able to render on 50 MIPS CPU's 14 hours a day to rendering on an aditional 84 Intel CPU's 24 hours a day. The comparison in render speed is about 1-1, slightly infavor of the MIPS chip.

When it is all said and done, a move like this should be a no brainer to any studio. Rendering needs horsepower and system memory, both of which are cheaper in the Intel world. SysAdmins need Unix for ease of administrating and lack of down time... every studio I know considers the render system to be H.A. (high availablity). When things go down, projects get delayed... and that is a big no no in the production world (think of all the billboards you see with release dates on them... months in advance). Linux is a great choice for this.

The only drawback is that the SGI boxes have the ccNuma interface, which is great for single frame renders.

I know that I have posted many times on /. about rendering and Linux vs. SGI. It is great that there is now a story dedicated to it.

FWIW: Our next two videos are the first to use our Linux render farm. Esther is at least 3/4 rendered on Linux boxes and Penguins will be mostly, if not all, rendered on Linux boxes.

-Tim Toll
Render Architect
Big Idea Productions

A Linux processor? I was under the impression that Linux was an operating system, not a hardware brand...

Linux may not be a brand, but VA Linux is a brand. VA Linux Systems owns OSDN owns Slashdot owns you.

...rasterman and mandrake ??

www.valinux.com is what...

marty

This time it's brought to us by OSDN, VA Linux, and all the assorted sites like Linux.com, Themes.org, SourceForge, ThinkGeek and what have you.

So, you mean it is sponsored by VA Linux.

This time it's brought to us by OSDN, VA Linux, and all the assorted sites like Linux.com, Themes.org, SourceForge, ThinkGeek and what have you.

So, you mean it is sponsored by VA Linux.

No, I don't work for them. Just my recommendation.

I looked into what happened with this ticket and, after having talked with this customer and gotten his ok to post about it, would like to share with you what happened, where we made mistakes and what we are doing to fix this.

As noted in the post, one of the machines that the customer recieved had some problems coming up. This was a problem with the raid subsystem that prevented boot up.

After a telephone conversation, Mr. Phillips sent the machine back to us to work on it.

We replaced a drive in this machine shipped it back, and the problem was still there. The machine shipped out working, all I can assume is that a shipper dropped the machine (hard) or something.

Once he recieved the machine and it still ahd the problem, we opted to build him a new machine. During burn in there was problem with the memory that necessitated the replacement of memory and retesting. This is park of the 2 week delay we talks of.

So while hardware failures during shipping happen, we made a clear mistake by not keeping the customer informed of the delays in burn in.

Then we shipped the machine back to him.

At this point we discovered that we forgot to add an extra nic that was part of his order.

Again, our bad, we screwed up. He took the nic from the original faulty server (he kept it while we worked up a new one for him) and put it in the machine, which worked fine.

At this point it was 30 days or so from when he received the first bad machine in his order or 4 machines.

We saw the /. post when it went up on slashdot, called the customer and talked with him regarding the screwups on our part and to make sure he that the machines were (now) working fine and that there wasn't anything new that we didn't know about. There wasn't. And he was very surprised it had gone up on slashdot :-)

So there you go, that's the whole story a mixture of human error and lack of notification on our part, burn in delays, and shipping issues combined to make a bad customer experience which we clearly regret.

All I can say is that the human error can be minimized to a great degree, shipper problems can be pretty out of our control (we do use sturdy shipping containers, but you wouldn't believe what we've seen happen in shipping) and communication is now in an improved state and be clear all of our techs know that keeping the customer continually informed is the right way to do things.

So there you go, if anyone has any questions, you can post them here, email me at jritter@valinux.com or call at 408-542-5722.

As a side note, a lot of people have posted that the customer doesn't deserve support and got what was coming to him since he removed our software load. That's totally incorrect, VA still has a responsibility to ship good product and support said product. When someone replaces our load, we still try to support it, but it does make it harder and increases troubleshooting time. Note that hardware support doesn't go away becuase of mandrake being installed.

I want to assure people that while this was bad, it is the exception, while it seems weird to say this here and now, VA has a very good record of dealing with support issues. If you have any questions about how we do things here, please post them and I'll answer them here.

Jeff Ritter
Support Manager, VA Linux Systems