I don't usually, but... 10051

snips

So it's an RPM file. An incorrectly formatted one. Eventually, you'll figure that out. The computer figured it out ages ago; when are you going to catch up?

You need to learn what you're talking about. "Linux" doesn't do files at all, really. Kernels are funny that way.

Applications, on the other hand, *do* use files. And they do so a number of different ways, depending on the application. Some, for example, default to using the extension.

That said, many applications can cope with incorrectly-extensioned data files by examining the file headers.

Of course, you're the Linux expert, with your whole - what was it again? two weeks? - experience, so you should know this.

It's an rpm file. What the f*** would you *expect* it to do? Try to dump it through the sound card? Oh, no, wait, it's an install package manager being handed an install package. Golly gee, imagine that, it tries to install it. What a completely retarded thing for an applicaiton to do - doing exactly what it's intended to do.

It's not a text file, it's an rpm package. Try to get that through what little grey matter you may still have functioning.

Let's see. If I create an mdb file in access, use a hex editor to delete all the contents and add "-r-n" as the first two bytes, it's still an mdb file, but if I create the *exact same file* using notepad and simply naming the file that way, it's magically somehow no longer an mdb file?

Bullpoo. They're both identical files, and they're both mdb files. They're not *valid* mdb files, but that's another matter entirely. Double-clicking 'em is going to bring up Access, because that's what the system does with mdb files. Just like launching the package manage is what the Linux GUIs do with package files. How utterly amazing, it all works exactly as expected, and only DuFuS is too stupid to figure it out.