Cmd Line Option Warrior Union Application

OK, folks this does it.

I just configured 'tar' for OS/2 to backup my system 'on the fly' to my 2nd HD. No to many Linux users know this, but the JFS file system for Linux was ported from the OS/2 codes. But while JFS allows for file sizes larger then 2GB, only IBM's PSnS backup SW makes actual use of this feature, and PSnS is a pain in the butt to work with. So I utilized 'tar' (as I have a complete Unix cmd line environment emulated in my OS/2 system) to pipe the output to my JFS partition.

Worked like charm, except for the dozens of cmd line options. After 20-30 minutes, I was 'back in the game' of cmd line battling. The most disgusting thing was that I liked it. Yackk. OK, now I'm hooked and I suppose I'll be keeping that Linux system after all (actually its a VPC emulation). But I also know one thing for 100% sure.

My cousin would rather shoot himself then go through what I just did. W/o a simple 'point & click' interface there is just no way he'd be able to handle his system. I guess he'll have to do it the Windoze way after all.

And since I still can't get a fully self-contained binary package for MPEG player for Linux, I suppose the days of Linux in his room are numbered (until his dad can buy him that new Windoze computer).

Now here's one question that I have regarding tar's cmd line options: I noticed that the sequence in which the options are listed seem to be of importance. I can only pipe the out successfully e.g. if '-cf -' is the last option listed. Any reason for this and what does the single '-' mean?

Also, I'm trying to capture the screen output of the dir listing (of files that are archived) as an (error) log, but I'm already piping the data output and thus I fail to see how I could pipe the screen output as well.

Anybody got any ideas on this one?

Greetings Morenga

HTH, you are just running into old Unix conventions that you don't know about here.

I'm talking about the need to configure dozens of files and cmd line options before anything plays on RedHat 8.x Heck, not even the CD RW drive works the same in all 3 progs that are installed. And even when it works, it comes out differently any time. Without me configuring the paramters like caching, nothing would burn on that machine at all. My poor cousing doesn't even know how to spell 'buffer underrun protection'. Much less where to find the on/off checkbox for that one.

And as far as trying to get dozens of interdependant RPM packages, where there is still yet one file missing, to install for a simple MPEG player, forget it. And then he should crank up the compiler to install a source code only version? Geeh, my Aunty is gonna kill me if she'd ever find out !

Not under RedHat 8.x Linux it isn't. I tried for 3 weeks now to find a 'self-contained' package. For OS/2 I got dozens of MPEG players. Windoze even comes with them. In none of these cases does one have to install dozens of packages or crank up the compiler to get it to run. One program, one binary and you're in business. That was what I was looking for. Simple but nimble. That was not supposed to be a Movie Studio, just some snipset preview gig.

Again, we're talking RedHat 8.x and that did not install with an MPEG player in it.

I most certainly will not. My Uncle has already decided to get my cousin a P4/5 Windoze box and by now I'm way past trying to talk him out of it.

The many other links I've been given in this news group forced me to download dozens of RPM packages and yet they still want me to download just one more of their kind.

Difference? My OS/2 tar version is GNU compatible. So how does that affect things?

Will I now have to humble myself before the Linux cmd line tribunal? Pardon me, but some of us still believe that Xerox's invention of the GUI was a milestone for computer technology and not a conspiracy of the unworthy ones in the computer community.