hat is the current implementation, but the standard
mechanism is "getconf PATH" as defined in:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/confstr.html
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/getconf.html
so that if we add /usr/xpg7/bin in a future version, they'd
source ones - bash, ksh93, zsh, etc.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
On 05/29/17 01:56 PM, Joerg Schilling wrote:
Alan Coopersmith <alan.coopersm...@oracle.com> wrote:
We still ship a couple closed source shells in Solaris - the SVR4 Bourne Shell
as /usr/sunos/bin/sh and a modified ksh88 as /usr/xpg4/bin/sh, but our primary
day to day shells are the commo
than trivial bug-fixes need to be applied on ksh88 to make it SUSv7-tc2
compiant.
Have the test suites been updated to catch all of these cases?
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
On 10/ 2/17 04:28 PM, Thor Lancelot Simon wrote:
On Mon, Oct 02, 2017 at 04:07:37PM -0700, Alan Coopersmith wrote:
On 10/ 1/17 04:10 AM, Joerg Schilling wrote:
Is Oracle planning to run a SUSv7-tc2 certification?
I don't know which version we plan to certify against next, and probably
, and can file bugs if they see
issues we need to fix.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
see any discussion in our review
of C11 possibly requiring more than that.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
of the line after
"file" for the given header file listed in
http://pkg.oracle.com/solaris/release/manifest/0/system%2Fheader@11.4%2C5.11-11.4.0.0.1.15.0%3A20180817T003001Z
)
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solar
(void *base, size_t nel, size_t width,
int (*compar)(const void *x, const void *y, void *context),
void *context);
with the engineer responsible citing https://reviews.freebsd.org/D17083 as
resolving the discrepancy in FreeBSD.
--
-Alan Coopersmith
to build FOSS packages that expect the GNU behaviors.)
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
[The preceding is my personal opinion, and not an official statement of Oracle.]
/785430/ suggests AIX, BSD, & MacOS have also defined
it, and though it's been proposed multiple times for Linux, never adopted there.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
Sun in 1996, so can only offer what I can still find recorded
from that time, not personal insight.)
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
of
systems already have, which is the standard C/POSIX locale with just the
character set changed to UTF-8 instead.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
dize, while this group controls the "POSIX"
locale definition. I suspect those following the POSIX standards
would end up implementing both, regardless of which specification
defines each.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
stuck here due
to past decisions it's a bit too late to undo now.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
: http://www.opengroup.org/press/03nov03.htm
http://www.opengroup.org/certification/idx/posix.html
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
, and as
guessed, for trap).
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
make use
of a function like this - yet other systems somehow implemented those
commands without it, for decades...
But presumably had more places to update signal name strings when defining
new signals (not that it happens very often - we last did it a decade ago,
when we expanded from 8 to 32 rea
' 0xc000
printf: ‘0xc000’: Result too large
9223372036854775807
(Same results on both SPARC & x86. 64-bit binaries on both.)
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
ed to kill:
https://www.tuhs.org/cgi-bin/utree.pl?file=pdp11v/usr/src/cmd/fuser.c
https://www.tuhs.org/cgi-bin/utree.pl?file=SunOS-4.1.4/usr.etc/rfs/fuser/fuser.c
In SVR4, fuser -k was also used in the umountall script, if the -k option was
passed to umountall.
--
-Alan Coopersmith-
dout, and seems to rely
on the fact stderr is unbuffered by default:
https://github.com/illumos/illumos-gate/blob/master/usr/src/cmd/fuser/fuser.c#L208
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
rst looked at the encoded file to see what path
is specified and verified it looks safe?
Would prompting for confirmation before overwriting a file be standard
compliant, or would it require adding an option like "-i" that clearly
takes you outside of standard coverage?
to set the mode bits exactly as specified in the file.)
And of course, using -o avoids any issues with the permission bits as well.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/solaris
resses these behaviors."
At the very least here, I thought the standard committee would want to
consider that all of the major implementations of uudecode follow a
defacto standard on removing bits from the permissions that doesn't
seem to be allowed by the current language of
ing table shall be set" so it's not consistent that
those bits are excluded from the "file permission bits".
Is there a definition I've missed that makes this clear?
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/solaris
25 matches
Mail list logo
