LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Update request: ksh93 in -current (http://www.linuxquestions.org/questions/slackware-14/update-request-ksh93-in-current-4175464329/)

gezley 06-01-2013 05:17 AM

Update request: ksh93 in -current
 
I would like to request that ksh93 be updated in -current. I use both Slackware and NetBSD and I am trying to standardize shells to reduce the risk of a spectacular catastrophe.

:D

As it stands, the version is as follows:

Code:

$ /bin/ksh --version
 version        sh (AT&T Research) 93t+ 2010-06-21

I believe the latest stable upstream version is 93u, released some time in 2012. For some reason the AT&T download section is not working for me at the moment, so I can't be sure about this.

Thank you.

hba 06-05-2013 02:02 AM

At my repository [1] you can find an updated SlackBuild for ksh-93 (under system/ksh-93). Check if it can helps you to install a newer version.

Cheers.

[1] https://bitbucket.org/nihilismus/slackbuilds/

gezley 06-05-2013 07:24 AM

Quote:

Originally Posted by hba (Post 4965626)
At my repository [1] you can find an updated SlackBuild for ksh-93 (under system/ksh-93). Check if it can helps you to install a newer version.

Thank you for your reply Antonio. I finally got my hands on the source and edited the Slackbuild script accordingly. I created and installed the updated package but I was just suggesting that it might be an idea to have the updated shell included by default in the next version of Slackware. So far I have had no problems with it myself.

tronayne 06-05-2013 03:58 PM

Hi, gezley,

So, I'm wondering -- what did you download from AT&T? I got INIT.2012-08-01.tgz and INIT.2013-05-24.tgz (seems like the newer INIT might be better?). I also got ast-ksh.2012-08-01.tgz (these from the ksh directory).

Looking at the Slackware ap/ksh93 source directory, there are INIT.2010-06-21.tgz, ast-ksh-locale.2010-02-02.tgz, and ast-ksh.2010-06-21.tgz (although the locale file does not seem to be created or used in the SlackBuild).

Before I go off the deep end, do I have the right stuff (and where the heck do you get the locale file if it's needed)?

I've just been following this thread because I only use KornShell and, you know, why not update?

Thanks.

gezley 06-05-2013 06:50 PM

Quote:

Originally Posted by tronayne (Post 4966073)
Hi, gezley,

So, I'm wondering -- what did you download from AT&T? I got INIT.2012-08-01.tgz and INIT.2013-05-24.tgz (seems like the newer INIT might be better?). I also got ast-ksh.2012-08-01.tgz (these from the ksh directory).

Looking at the Slackware ap/ksh93 source directory, there are INIT.2010-06-21.tgz, ast-ksh-locale.2010-02-02.tgz, and ast-ksh.2010-06-21.tgz (although the locale file does not seem to be created or used in the SlackBuild).

Before I go off the deep end, do I have the right stuff (and where the heck do you get the locale file if it's needed)?

I've just been following this thread because I only use KornShell and, you know, why not update?

Thanks.

Hi Tronayne,

I first downloaded these two source tarballs from the website (which is very unreliable, at least here):

INIT.2012-08-01.tgz
ast-ksh.2012-08-01.tgz

When I downloaded them INIT.2013-05-24.tgz wasn't available.

All I did then was to replace VERSION=2010-06-21 with VERSION=2012-08-01 in the slackbuild script (and the same for PKGVER); I put the tarballs in the same directory; and I ran the slackbuild as root. This created the package which I was able to install with installpkg. I'm not sure if I did it the right way; on reflection perhaps I should have used upgradepkg instead, but everything has been going OK for me for the last week or so. I'm a shell novice so don't rely on my judgement. I do like the Korn shell: it just seems to have a professional feel about it.

Good luck!

volkerdi 06-05-2013 07:20 PM

As an aside, David Korn is a really great guy. He was the first UNIX demigod I ever met. I was at a LinuxWorld conference in NYC and he came wandering up to the booth and just stood there smiling (I was talking to a bunch of other people at the time). After things got a little more quiet, I glanced at his badge and it was all I could do to keep from going into groupie mode. We ended up having a great discussion about UNIX, Linux, and his shell, which he told me he was trying to get AT&T to make free enough that we could drop pdksh and include the real deal instead.

I'll look into getting updates into -current.

sombragris 06-05-2013 08:12 PM

Quote:

Originally Posted by volkerdi (Post 4966159)
As an aside, David Korn is a really great guy. He was the first UNIX demigod I ever met. I was at a LinuxWorld conference in NYC and he came wandering up to the booth and just stood there smiling (I was talking to a bunch of other people at the time). After things got a little more quiet, I glanced at his badge and it was all I could do to keep from going into groupie mode. We ended up having a great discussion about UNIX, Linux, and his shell, which he told me he was trying to get AT&T to make free enough that we could drop pdksh and include the real deal instead.

I'll look into getting updates into -current.

WOW! Impressive!!

GazL 06-05-2013 08:16 PM

Ahh, seems like a good excuse to drag this old story out. Old timers will probably have seen it before,
but maybe the younger slackers will appreciate it.

Quote:

From: Joel Ray Holveck

I've been attending the USENIX NT and LISA NT (Large Installation Systems
Administration for NT) conference in downtown Seattle this week.

One of those magical Microsoft moments(tm) happened yesterday and I
thought that I'd share. Non-geeks may not find this funny at all, but
those in geekdom (particularly UNIX geekdom) will appreciate it.

Greg Sullivan, a Microsoft product manager (henceforth MPM), was holding
forth on a forthcoming product that will provide Unix style scripting and
shell services on NT for compatibility and to leverage UNIX expertise that
moves to the NT platform. The product suite includes the MKS (Mortise
Kern Systems) windowing Korn shell, a windowing PERL, and lots of goodies
like awk, sed and grep. It actually fills a nice niche for which other
products (like the MKS suite) have either been too highly priced or not
well enough integrated.

An older man, probably mid-50s, stands up in the back of the room and
asserts that Microsoft could have done better with their choice of Korn
shell. He asks if they had considered others that are more compatible
with existing UNIX versions of KSH.

The MPM said that the MKS shell was pretty compatible and should be able
to run all UNIX scripts.

The questioner again asserted that the MKS shell was not very compatible
and didn't do a lot of things right that are defined in the KSH language
spec.

The MPM asserted again that the shell was pretty compatible and should
work quite well.

This assertion and counter assertion went back and forth for a bit, when
another fellow member of the audience announced to the MPM that the
questioner was, in fact David Korn of AT&T (now Lucent) Bell Labs. (David
Korn is the author of the Korn shell)

Uproarious laughter burst forth from the audience, and it was one of the
only times that I have seen a (by then pink cheeked) MPM lost for words
or momentarily lacking the usual unflappable confidence. So, what's a body
to do when Microsoft reality collides with everyone elses?


gezley 06-06-2013 06:39 AM

Quote:

Originally Posted by volkerdi (Post 4966159)
I'll look into getting updates into -current.

Thank you very much.

tronayne 06-06-2013 11:29 AM

Quote:

Originally Posted by volkerdi (Post 4966159)
I'll look into getting updates into -current.

So, Pat, what's the locale for -- really doesn't look like it gets used in the build (and, if it does get used, where the heck is it found)?

Yup, David Korn is one of the good guys (heard him give a talk once); I felt the same way when I met Brian Kernighan (also a great guy) some years ago, hard not to go all groupie (he's teaching at Princeton nowadays, gotta think that would be a real worthwhile class).

You know, it's funny how the really, really smart folks usually turn out to be some of the nicest you'd ever want to meet -- I've been privileged to meet a few and they've pretty much all turned out to be a lot fun to be with and you wind up learning a few things while you're at it.

Korn's The KornShell Command and Programming Language (co-written with Morris Bolsky) shares a lot in common with Kernighan, Ritchie (RIP Dennis), Thompson, Kochan, Wood and others that came up through Bell Labs -- every one readable, understandable, free of fluff and still sitting on my shelves getting referred to now and again.

Will I keep using KornShell? Dang right -- it works.

hba 06-09-2013 12:09 AM

Quote:

Originally Posted by gezley (Post 4966154)
When I downloaded them INIT.2013-05-24.tgz wasn't available.

It's available here http://www2.research.att.com/sw/download/alpha/

BTW, the license of ksh93 is now EPL and if i recall you should buil ast-ksh with the same version of INIT, something that is taking into place in my updated SlackBuild. OTOH, at the time i updated ksh93's SlackBuild i couldn't find information about the *locale* package, so i just commented all lines that makes references to it.

Finally, i'm using mksh (https://www.mirbsd.org/mksh.htm) since it seems more stable and actively developed than ksh93.

Cheers.

gezley 06-10-2013 08:05 PM

Woo hoo! Thank you so much!

Code:

Current (pre-release) ChangeLog for x86_64

 Mon Jun 10 21:51:54 UTC 2013
 ap/ksh93-2012_08_01-x86_64-1.txz: Upgraded.


_gin 06-11-2013 12:28 AM

Line 70 and 80 the SlackBuild calls "/bin/ksh".

Mister Volkerding can you change that to "/bin/sh" for those who don't have the Korn shell installed yet ?

tronayne 06-11-2013 06:29 AM

Quote:

Originally Posted by _gin (Post 4969315)
Line 70 and 80 the SlackBuild calls "/bin/ksh".

Mister Volkerding can you change that to "/bin/sh" for those who don't have the Korn shell installed yet ?

Uh, KornShell is and has been standard equipment in Slackware for a long, long time; should be there unless you've removed it for some reason.
Code:

whence -v ksh
ksh is a tracked alias for /bin/ksh

If you did remove it, simply install it from your distribution CD-ROM/DVD -- it's in ap/ksh93.

Hope this helps some.

tronayne 06-11-2013 07:16 AM

Thank you, Pat.

Downloaded from the source tree at OSUOSL, built on my main work station (64-bit 14.0), upgradepk, log out, log in, viola! Compiling as we speak on one of the (32-bit 14.0) boxes, no runs, no drips, no errors.

Elegant command and programming language.


All times are GMT -5. The time now is 08:07 PM.