search for: ksh93

Hi! ---- Is there any interest to turn the "zfs" utility (to clarify: This is about a change in the "zfs" utility itself, not about any "language bindings" etc.) from it''s (currently) "homegrown" command-line parsing code over to ksh93/libshell.so (this has been proposed by Amersham/GE Healthcare staff a while ago for the original "ksh93-integration" project proposal, see http://www.opensolaris.org/os/project/ksh93-integration/ for the project''s home page) ? The idea would be that "zfs" would simply...

Roland Mainz wrote: > April Chin wrote: > > I''m in the process of filing manpage bugs for ksh93 to include > > changes to existing pages and new manpages for ksh93(1) and its > > builtins (builtin(1), disown(1)). > > > > CR 6457823 New manpages needed for ksh93 > > > > However, I do not see any manpages for vmap(1), alarm(1), or vpath(1). > > Are ther...

...ash -rwxr-xr-x 1 root root 1,4M Jan 6 2022 /bin/bash lrwxrwxrwx 1 root root 4 Mar 23 2022 /bin/sh -> dash OpenIndiana (old OpenSolaris reincarnation) :; ls -hal /bin/sh /bin/bash -r-xr-xr-x 1 root bin 1,4M Jan 25 09:42 /bin/bash lrwxrwxrwx 1 root root 9 Apr 6 2021 /bin/sh -> i86/ksh93 On 2024-03-07 23:19, Job Snijders wrote: > On Thu, Mar 07, 2024 at 11:13:50PM +0100, Predrag Ze?evi? wrote: >> Not all systems have /bin/sh linked to /bin/bash. > > Are there systems without /bin/sh? The objective isn't to use 'bash' > implementation specifically,...

...ibution? In 1990, when I started using ksh88, it was totally commercial. Binaries were $$$ and source was $$$$. We bought the source and compiled it for SunOS, Ultrix and various SYSVr[23] machines (one machine was so old it didn't understand #! and so needed it placed as /bin/sh). By 1998, ksh93 was free (as in beer) but was restricted distribution. Eventually ksh93 became properly free, but by this point bash was already popular in the Free-nix arena and had even made it into Solaris, AIX and others. > I didn't know bash till I got to CentOS (I don't remember it in RH 9...),...

On Fri, Apr 24, 2015 at 03:15:27PM +0200, Joerg Schilling wrote: > Stephen Harris <lists at spuddy.org> wrote: > > > Bash was bigger than ksh in the non-commercial Unix world because of ksh88 > > licensing problems. Back in 1998 I wanted to teach a ksh scripting > > course to my local LUG, but AT&T (David Korn himsef!) told me I couldn't > > give

Warren Young <wyml at etr-usa.com> wrote: > On Apr 27, 2015, at 4:38 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > > > This is the SVr4 Bourne Shell, so you need to take into account what has been > > added with Svr4: > > Is there any difference between your osh and the Heirloom Bourne Shell? > >

...just (finally) got into Unix in '91, and didn't do any admin work, just programming, until later in '95, and I had nothing to do with what software got installed, at least to start (I sat there while someone else was doing the installing). And that was a Sun, anyway. > > By 1998, ksh93 was free (as in beer) but was restricted distribution. > Eventually ksh93 became properly free, but by this point bash was > already popular in the Free-nix arena and had even made it into > Solaris, AIX and others. > >> I didn't know bash till I got to CentOS (I don't rem...

I'm seeing a lot of noise in the logs, to the effect of: setroubleshoot: SELinux is preventing /bin/ksh93 from write access on the directory /var/lib/ssh-x509-auth as well as others related to find, cat, etc on .pem's in that directory. Is this a policy bug, or just no policy covering this? mark

Hi, folks, Our system gets/creates /var/lib/ssh-x509-auth/<username>,pem, then deletes it when the log out. selinux (in permissive mode) complains. First, I changed the context to cert_t, and *now* it complains that ksh93 wants write, etc access on the directory. grep ssh-x509-auth /var/log/audit/audit.log | audit2allow offers me this: #============= sshd_t ============== allow sshd_t cert_t:dir write; allow sshd_t var_lib_t:file { write getattr create open ioctl }; So: first, is this an expected behavior; second,...

.... I suspect that different CFLAGS are needed. Please, someone, have a look at it; a release of klibc 2.0 upstream is imminent. bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

...distribution when bsh first became available in an OSI-approved form, but it seems to be sometime in the 2005-2007 range. > > If that is true, then bsh is several years late to fill a gap already filled by ash, in the same way that the prior existence of bash makes the open-source version of ksh93 uninteresting to most people. > > This is why you need a web page to sell your project: to explain why someone should abandon bash, zsh, ash, dash, posh, ksh93u+, mksh? I am not interested in working against ksh93, as this is much closer to POSIX than the current Bourne Shell. The Bourne Sh...

I have a little niggling situation that I would like to resolve programmatically. I use Git as my SCM and I have release branches which are sometimes patched. I find myself sometimes entering the working directory tree forgetting that I was last on a release branch and not on the master. What I would like to do is to have a script run every time that I enter a directory, check for .git, and if

...place :-). + * + * The SysV implementation (at least in the 'test' builtin in /bin/sh) does use + * access(name, 2) even though it also goes to much greater lengths for '-x' + * matching the 1003.2-1992 definition (which is no doubt where that definition + * came from). + * + * The ksh93 implementation uses access() for '-r' and '-w' if + * (euid==uid&&egid==gid), but uses st_mode for '-x' iff running as root. + * i.e. it does strictly conform to 1003.1-2001 (and presumably 1003.2b). */ -static int -test_st_mode(const struct stat64 *st, int mode) +...

hello hpa, current patch queue for review, please pull: git pull git://git.debian.org/users/maks/klibc.git maks Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Thorsten Glaser (1): [klibc] add getrusage() maximilian attems (3): [klibc] resume: silence warning on resume try [klibc] bootp_packet.h minor

...ssh). It's not a standard behavior: many programs use system(), e.g. mailcap. However, their documentation doesn't say "the user's shell" in such a case. So perhaps "the user's shell" implies the use of $SHELL if set. This is still a bit confusing. For instance, ksh93 sets $SHELL to /bin/sh if it is not already set (!!!), and this is definitely not the user's shell. It's still not clear about the absolute pathname. Note that POSIX just uses the term "pathname" for both $SHELL and $0, while in $0, the pathname may be relative (in which case, re...

...ver, it actually takes the value of the environment variable > if it exists: > > $ OPTIND=4 dash -c 'echo "$OPTIND"' > 4 > $ OPTIND=4 bash -c 'echo "$OPTIND"' > 1 > $ OPTIND=4 ksh -c 'echo "$OPTIND"' > 1 > $ OPTIND=4 ksh93 -c 'echo "$OPTIND"' > 1 This patch fixes this by initialising OPTIND after importing the environment. Signed-off-by: Herbert Xu <herbert at gondor.apana.org.au> Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/dash/var.c | 2 ++ 1 file changed, 2 in...

...ver, it actually takes the value of the environment variable > if it exists: > > $ OPTIND=4 dash -c 'echo "$OPTIND"' > 4 > $ OPTIND=4 bash -c 'echo "$OPTIND"' > 1 > $ OPTIND=4 ksh -c 'echo "$OPTIND"' > 1 > $ OPTIND=4 ksh93 -c 'echo "$OPTIND"' > 1 This patch fixes this by initialising OPTIND after importing the environment. Signed-off-by: Herbert Xu <herbert at gondor.apana.org.au> Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/dash/var.c | 2 ++ 1 file changed, 2 in...

Kees Cook dixit: >3) fix the use of trampolines in klibc AIUI done in klibc, but post-2.0.7 bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

...This works and avoids GNU bash just the same. (I ran this on a system with no GNU bash installed.) bye, //mirabilos, shell maintainer/developer -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

...csh assumed it was a csh script, otherwise it assumed a sh script. That's why a lot of real old scripts began with : > and enters the path to such a script, it would also run in ksh. That > would only be true if you "sourced" the script from your shell. So on CentOS 5 with ksh93 as my shell % cat x echo ${.sh.version} Note that it's a simple one liner with no #! % ./x Version AJM 93t+ 2010-06-21 That's ksh output! Let's change my shell to "bash" instead % bash bash-3.2$ ./x ./x: line 1: ${.sh.version}: bad substitution So now it...