JF Martinez wrote:
> There is a thing you have to consider:and that is people coming to
> Unix are not the only Linux usersa nd also there are more than one
> hundred million people waiting to be "libearted" from Windows.
Yes, I pray for them daily.
> I frankly don't want to acept a thing as standard just because it is
> in Unix.
Fair enough, but clearly POSIX and SVR4 are "Standards" with a capital
"S".
> Ptroviding tools Unixers are used to is one thing, putting Linux
> growth in jeopardy just to please them is another.
Ok, but looking at the particular case that brought this up I don't
think it, as an example, does put Linux growth in jeopardy. Saying
"/bin/sh" is POSIX bourne shell only doesn't stop any advancements for
those who prefer bash. They can put "#! /bin/bash" on their shell
scripts to get the extra functionality and not be prevented from using
its advanced features.
As it is when someone writes a script with "#! /bin/sh" at the top and
it uses "bash" or "ksh" extensions it's a sort of lie. It's not a bourne
shell script, it's a bash script. Its not portable, it's not compliant
and I don't see how it would hurt to actually force these users to put
"#! /bin/bash" to make it clear that's what the script really is. I
definitely can't see how it would hold up "growth".
> And as I said we can expect proprietary Unixes will adopt more and
> more of the Linux standards just as they dumped CDE /Motiffor
> Gnome/GTK.
And I hope they do but in the mean time I, and many others, have
heterogeneous networks to support that require interoperability. This is
going to take some time and in the mean time we suffer.
> Another point us that many postgraduate Unixers, trained on Linux so
> they find annoying to have to adapat to proprietary Unixes
Depending on how you look at the definition, the Linux you suggest could
also be called "proprietary". Though "proprietary" usually is though to
me "not open" it also to some extent means, "not following standards"
and these standards are not just defacto, they're well written and have
gone through considerable due process.
Anyway, I'm not saying that Linux shouldn't go beyond the standards,
they should. Just every effort should be made (which as of current it
has) to still be compliant to the standards while giving extended
functionality. So, if you don't like bourne shell and want to make a
better one, great, just don't call it "/bin/sh" `cause it isn't.
> while people of the old Unix guard are dying
We're not that old!!!! Please don't kill us off yet. ;-)
> retiring
Or even that old! I'm 34! I wish I could retire though.
> or moving to higher rank so their relative numbers are dwindling even
> on AIX., Solaris and the like. This socilogy shift is one of the
> reasons there are hints about most vendors will linuxify their
> proprietary systems.
Ok, maybe that, but mostly I think they're making the shift because they
see money in it. I'm glad of it though (even though I'm "old").
Just wait, someday even though Linux is great stuff they'll be calling
what you grew up with and built "crap" too. It will happen. Some
generation will be talking about all the old "Linux squares" who prefer
that proprietary old Linux stuff and you'll feel suddenly old at the age
of 34 too. It's coming, it is.
- Matt
--
---------------------------------------------------------------------
Matt Fahrner 2 South Park St.
Manager of Networking Willis House
Burlington Coat Factory Warehouse Lebanon, N.H. 03766
TEL: (603) 448-4100 xt 5150 USA
FAX: (603) 443-6190 [EMAIL PROTECTED]
---------------------------------------------------------------------
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
