Re: JAVA JDK 1.6
I guess Florian wanted to reply to the list. Regards, Berry. Florian Bilek schreef: Dear all, Even I couldn't agree more with the statements about sticking to the available software versions, this does not reflect reality. As software is mostly developed outside of the organisations they want to use it, nobody is taking care of certain maintenace levels. When it is available, when it is fits to the requirements then the management wants to have it. And when you as responsible for the zSeries tell them, well we can not do it because we have SLES 10 and SLES 11 requires a new mainframe, I guess you can imagine what the reaction of the management will be: Burry this bloddy thing an replace it immediately by more modern hardware. In my opinon the zSeries has to be as flexible as possible in order to have a chance to survive against the other platforms. It is not that you simply buy a new zSeries every year. So I think there is a real need to support JAVA 1.6 also on SLES 10 and I really don't see why this should not be possible. Best regards, Florian On Sat, Aug 8, 2009 at 1:01 AM, Berry van Sleeuwen berry.vansleeu...@xs4all.nl mailto:berry.vansleeu...@xs4all.nl wrote: I wish we could manage the programmers :-). Some do program with a version in mind. Especially when new functions are incorporated into a new software product. Or when some product requires (or thinks it requires) a certain version. As much as we would like to we can't always control the programmers or software vendors. I do agree that a programmer should code for the available version but it's not always that simple. Berry. Mark Post schreef: The programmers may prefer... That's a management issue, and should be addressed by them. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu mailto:lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Best regards Florian Bilek -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: JAVA JDK 1.6
I agree with Florian's comments. That's the point I was trying to make when I first replied to Mark's response. While I completely agree with Mark's comments, I do not think that they are realistic in every setting. My problem is not Java 1.5 or 1.6 availability. It is the limitation of running various versions of SLES on zSeries processors. I made the same objection when SLES 11 was announced to run on z9 and above only. As Florian says, no everyone out there has the ability to go out and buy a new system z every few years. Some of us smaller shops in particular. So, for now, we are stuck with SLES 10. Just my 2 cents. Aria Quoting Berry van Sleeuwen berry.vansleeu...@xs4all.nl: I guess Florian wanted to reply to the list. Regards, Berry. Florian Bilek schreef: Dear all, Even I couldn't agree more with the statements about sticking to the available software versions, this does not reflect reality. As software is mostly developed outside of the organisations they want to use it, nobody is taking care of certain maintenace levels. When it is available, when it is fits to the requirements then the management wants to have it. And when you as responsible for the zSeries tell them, well we can not do it because we have SLES 10 and SLES 11 requires a new mainframe, I guess you can imagine what the reaction of the management will be: Burry this bloddy thing an replace it immediately by more modern hardware. In my opinon the zSeries has to be as flexible as possible in order to have a chance to survive against the other platforms. It is not that you simply buy a new zSeries every year. So I think there is a real need to support JAVA 1.6 also on SLES 10 and I really don't see why this should not be possible. Best regards, Florian On Sat, Aug 8, 2009 at 1:01 AM, Berry van Sleeuwen berry.vansleeu...@xs4all.nl mailto:berry.vansleeu...@xs4all.nl wrote: I wish we could manage the programmers :-). Some do program with a version in mind. Especially when new functions are incorporated into a new software product. Or when some product requires (or thinks it requires) a certain version. As much as we would like to we can't always control the programmers or software vendors. I do agree that a programmer should code for the available version but it's not always that simple. Berry. Mark Post schreef: The programmers may prefer... That's a management issue, and should be addressed by them. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu mailto:lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Best regards Florian Bilek -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: JAVA JDK 1.6
On 8/8/2009 at 5:29 PM, Aria Bamdad a...@bsc.gwu.edu wrote: -snip- As Florian says, no everyone out there has the ability to go out and buy a new system z every few years. Some of us smaller shops in particular. So, for now, we are stuck with SLES 10. IBM has always been pretty motivated to move customers off older generation hardware. With IBM's last quarter financial results, I would imagine they are even more so right now. It couldn't hurt to ask what they can do for you. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: script name w/o path.
John McKown wrote:
Yes, I know how to get it. But I'm curious and would like your feedback.
Assuming that my script is BASH specific, is there any reason why I should
not use the command:
SCRIPT_NAME=${0##*/}
instead of
SCRIPT_NAME=$(basename $0)
?
I ask because I feel that the first example, though not universal to all
shells, is worth it due to being more efficient. I don't fork() a new
process or need to run an external program.
I also know this might not matter much to Linux, even on a z. But the
first also works in z/OS with its default shell, and that saves me CPU
which saves me money. Well, saves the company money, actually.
How many times is this being done?
How much time and trouble are you expending trying to sort this out?
How well are likely readers to understand what SCRIPT_NAME=${0##*/} does?
Me, I'd choose using basename,unless I knoew a really good reason not
to, and if the script is going to be used enough that it matters,
there's a good argument it shouldn't be a script at all, but rather
compiled code in an appropriate programming language.
--
Cheers
John
-- spambait
1...@coco.merseine.nu z1...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
