Date: Sat, 03 Mar 2001 12:11:03 -0500 From: "Brian F. Feldman" <green@FreeBSD.org> To: "Jacques A. Vidrine" <n@nectar.com> Cc: "Brian F. Feldman" <green@FreeBSD.org>, Will Andrews <will@physics.purdue.edu>, FreeBSD Architecture <arch@FreeBSD.org>, bde@zeta.org.au, obrien@nuxi.com, nate@yogotech.com Subject: Re: cvs commit: src/gnu/usr.bin/binutils/ar Makefile src/gnu/usr.bin/binutils/as Makefile.inc0 src/gnu/usr.bin/binutils/ld Makefile src/gnu/usr.bin/binutils/ranlib Makefile Message-ID: <200103031711.f23HB3V99101@green.dyndns.org> In-Reply-To: Message from "Jacques A. Vidrine" <n@nectar.com> of "Sat, 03 Mar 2001 09:19:58 CST." <20010303091958.A68223@spawn.nectar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jacques A. Vidrine" <n@nectar.com> wrote: > On Sat, Mar 03, 2001 at 01:04:04AM -0500, Brian F. Feldman wrote: > > As far as making rc compatible with ksh... ksh is a _super_set of the POSIX > > shell, not a completely, totally new language. This means in all but the > > most esoteric cases, it will act exactly the same (or better, but compatibly > > so). > > I already tried dropping ksh93 into /bin/sh and booting with it. Two > issues came up immediately: the `local' command, and some business > with signal handlers (can't recall exact details at the moment). > I don't think these would be hard to fix, though. Well, local is a non-standard extension if I recall correctly. I'd expect, though, ksh93 to have aliased it to typedef. As far as signal handlers go, I'll see if I can find out what the problem is there. We shouldn't be writing our scripts to a "standard" of whatever is in our /bin/sh, but instead to what is portable. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103031711.f23HB3V99101>