Clarification Requested
> Severity: Objection
> Priority: normal
> Status: New
> Name: Eric Blake
> Organization: Red Hat
> User Reference: ebb.posix_getdents
> Section:XSH p
ful
time format from a single interface. For example,
https://lists.gnu.org/archive/html/bug-gnulib/2024-02/msg00077.html
https://lists.gnu.org/archive/html/bug-gnulib/2024-02/msg00064.html
Eric Blake
On Wed, Feb 07, 2024 at 08:14:39AM -0600, Eric Blake via austin-group-l at The
Open Group w
024-02-05 08:15, Eric Blake wrote:
>
> > Did you consider the effect of the change on applications that
> > populate struct tm directly (and don't currently set tm_gmtoff, except
> > perhaps by zeroing the structure)?
>
> Yes. Very few apps do that. (I looked f
h more friendly,
> e.g., for writing git commits. Unfortunately, Antonio updated GNU ed at some
> point to follow POSIX, which is sub-optimal.
> -AM
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
ng to implement it now, it will make Issue 9
easier to reason about.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Fri, Sep 01, 2023 at 08:59:19AM +0100, Stephane Chazelas wrote:
> 2023-08-31 15:02:22 -0500, Eric Blake via austin-group-l at The Open Group:
> [...]
> > The current POSIX says that %b was added so that on a non-XSI
> > system, you could do:
> >
> >
On Thu, Aug 31, 2023 at 03:10:58PM -0400, Chet Ramey wrote:
> On 8/31/23 11:35 AM, Eric Blake wrote:
> > In today's Austin Group call, we discussed the fact that printf(1) has
> > mandated behavior for %b (escape sequence processing similar to XSI
> > echo) that will eventuall
be easier (less shell escaping needed). Is there
any interest in a patch to coreutils or bash that would add such a
synonym, to make it easier to leave that functionality in place for
POSIX Issue 9 even when %b is repurposed to align with C2x?
--
Eric Blake, Principal Software Engineer
Red Hat,
two commonly chosen
ranges already in play is not going to make it easy to mandate a
specific mapping.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
nvoking Undefined Behavior (UB).
> +POSIX Issue 8 will fix this by requiring that implementations
> +make sure that these structures
> +can be safely used as they were designed.
> .SH NOTES
> .I socklen_t
> is also defined in
>
>
> I guess this is simple enough that it should work as documentation.
It seems fine from my perspective.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On Thu, Apr 06, 2023 at 02:05:15PM -0400, Zack Weinberg wrote:
> On Thu, Apr 6, 2023, at 12:31 PM, Alejandro Colomar via Libc-alpha wrote:
> > On 4/6/23 18:24, Eric Blake wrote:
> >> here's the updated wording that the Austin Group tried today (and we
> >> plan on start
tions that
currently work with the Solaris iconv() interface.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On Wed, Nov 30, 2022 at 08:54:03AM -0600, Eric Blake via austin-group-l at The
Open Group wrote:
> > ...
> > |https://austingroupbugs.net/view.php?id=561
>
> First, I chose that wording because 'sizeof(struct
> sockaddr_un.sun_path)' doesn't compile. You a
plementation's way of guaranteeing that it can
handle a NUL byte even if the application didn't pass one in.
Therefore, do we need to modify the wording in this proposal to ensure
that struct sockaddr_un is not allowed to have padding bytes after
sun_path to match existing practice?
--
Eric Blake
things
like -n to make it more useful was worthwhile to the implementors.
I'm aware that 'dirname -n' is not common implementation practice, but
since 'readlink -n' does appear to be, there's no harm in
standardizing it that way.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
e an
extension where:
readlink -v var -n -- "$name"
assigns $var to the full symlink contents, without any extra or
stripped newlines, but such an extension is not what we are proposing
to standardize]
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
izeof(struct sockaddr_un) preinitialized to 0 when
it is desired to ensure NUL termination
- Leave SUN_LEN out of the standard; we don't want variable-length
sun_path
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On Thu, May 05, 2022 at 09:31:41AM -0500, Eric Blake via austin-group-l at The
Open Group wrote:
> Hello GNU and Illumos folks,
>
> The Austin Group (those in charge of the POSIX specification) have
> been working on a draft to incorporate the gettext(3) family of
> functions and
'no dupes') to have the duplicate
detection available without requiring -c.
In addition to answering that question, any review of the rest of the
proposed wording (particularly anything that is still colored and thus
represents edits since the last time we asked for review) is still
appreciated.
--
et expression for
either of a literal backslash or literal n; but concur that its
behavior when being POSIX-compliant matches the POSIX rules.
POSIX can't control what GNU sed does when in non-POSIX mode. But it
can document a recommendation to spell the bracket expression intended
to match
ALL YO
> JIS_C6220-1969-JP.gz: /x2FKATAKANA LETTER
> SMALL TU
>
> Since all these (well except perhaps ISO_10646) use 0x2E and 0x2F for
> other characters than . and / ... doesn't that already mean that
> they're invalid with respect to POSIX?
Not quite
32
$ nohup -- --version
nohup: ignoring input and appending output to 'nohup.out'
nohup: failed to run command '--version': No such file or directory
$ rm nohup.out
$
> Maybe nohup needs to be among the utilities that do not recognize "--".
No. While we are explicit that echo is one of
bug and your reaction about it
being premature to standardize a requirement of "--" (vs. just merely
recommending it and documenting what portable apps must do in the
meantime).
https://sourceware.org/bugzilla/show_bug.cgi?id=28519
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
will a future gettext release behave
differently? Or if it is intentional and not a bug, can you provide
justification for the behavior as well as tweaks to the proposed
standard wording for gettext requirements and the worked example?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
On 3/9/21 1:34 PM, Eric Blake via austin-group-l at The Open Group wrote:
> On 3/9/21 10:14 AM, shwaresyst wrote:
>>
>> To me that looks like a conformance violation and should be reverted. There
>> is no _SC_SIGSTKSZ defined in by the standard, to begin with, so
&
e configuration supports if it wants to use more than
> that, as a runtime increasable limit.
As I understand it, the concern in glibc is less about runtime
increasability, so much as ABI compatibility with applications compiled
against older headers at a time when the kernel had less state
information to s
On 3/9/21 9:26 AM, Andreas Schwab wrote:
> On Mär 09 2021, Eric Blake via Libc-alpha wrote:
>
>> The question becomes whether glibc is in violation of POSIX for having
>> made the change, or whether POSIX needs to be amended to allow SIGSTKSZ
>> to be non-preprocessor-
he change, and I've now seen reports of several
projects failing to build when using glibc with this change included.
>
> Bruno
>
> [1] https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/signal.h.html
>
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
ifferences between strftime vs. date are
both less invasive than a mandatory change to the contents of an
existing format value. So I'm concurring with Geoff's handling of the
responses so far.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization:
with that additional date tweak.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
On 2/4/20 9:29 AM, Eric Blake wrote:
On 2/4/20 9:16 AM, Robert Elz wrote:
I am putting this in a new thread, as it isn't really important,
more just amusing, but the solution to this issue, with respect
to the "." command, is I think, causing that command to be in
violation of th
s to the XBD guidelines. Something like:
The dot special built-in shall support XBD Section 12.2 (on page 215),
except that it does not comply to Guideline 1 or 2 due to its name.
or maybe
The dot special built-in shall support Guidelines 3-14 of XBD Section
12.2 (on page 215).
--
Eric Blake,
his, I'd suggest to them that they do not approve the new version while
it contains the kind of incompatibility and breakage for no particularly
good reason that seems to me to exist.
But I think you've overlooked the fact that you ARE allowed to have the
extension behavior for all except '--' that prese
Linux kernel patch to update the process struct to track 32
bits and fix _exit/waitid to expose them.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
Also, from a usability perspective, I think it would be better if `-' lost its
special meaning after `--'. This would make the above code superfluous.
Coding that up would be at odds with existing practice, so even if we
were to choose that way if designing from scratch, I don't think we can
making it easier to
standardize things as 'qsort_r' as presented in the bug, rather than as
'posix_qsort_r'. But as there is still a 30-day window for Open Group
objections, we may very well receive an objection to the name 'qsort_r'
where we would have to go with 'posix_qsort_r'.
--
Eric
ick to draft a Clarification Request to WG14.
...says he already raised a similar question to WG14 in May 2018
(although I do not have a URL handy to that thread).
In fact, the call to standardize reallocarray() may also want to depend
on the outcome here. http://austingroupbugs.net/view.php?id
uments, it looks like there is a
discrepancy between POSIX requirements and existing shell behavior.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
hat is indeed the regression in behavior, which seems to not be the
historical practice of any earlier shell. If the standard has to permit
bash 5 behavior by leaving it unspecified, we've still rendered a lot of
existing scripts broken; better would be if we can agree on standard
wording (and Chet u
cceptable wording that either permits
existing practice (at the risk of rendering common shell script examples
in the wild as tickling unspecified behaviors), or which tightens things
to be less unpredictable (even if it renders existing shells as
non-compliant).
--
Eric Blake, Principal Software
et if you used extensions
beyond POSIX (leading '-', leading '+', changing POSIXLY_CORRECT in the
environment, or use of '::'). Thus, I'm leaning towards writing a
defect that does just the latter (documenting optind=1 after getopt()
returned -1 as a soft reset, and leaving it as implementation ex
On 9/9/18 3:34 PM, Florian Weimer wrote:
On 09/08/2018 12:54 AM, Eric Blake wrote:
Also, I've realized that we do NOT need
posix_spawn_file_actions_addopenat(). The main benefit of openat() is
that you can redirect relative file names according to an fd of your
choice, without affecting
[reviving a REALLY old thread]
https://sourceware.org/ml/libc-alpha/2010-08/msg00107.html
On 08/27/2010 01:35 AM, Jonathan Nieder wrote:
(pruned cc's, +cc:libc-alpha)
Eric Blake wrote:
On 08/26/2010 12:18 AM, Jonathan Nieder wrote:
Do you think there would be any interest in a posix_spawn
in the project is aware of where to write/review any wording
proposals for accomplishing the addition into POSIX.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On 08/08/2018 07:19 PM, Eric Blake wrote:
We've just had a discussion on whether standard-compliant abs() (which
is currently undefined on INT_MIN) should be permitted and/or required
to have well-defined behavior
I failed to provide a summary to my thoughts:
I think your paper's example
int math, not integer math), and that the wording in 1108
will be once again relaxed to leave behavior of abs(INT_MIN) undefined,
rather than well-defined (any specific implementation can, of course,
define behavior as an extension to POSIX).
--
Eric Blake, Principal Software Engineer
Red Hat,
lease quit spreading misinformation.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
ble to write a
construct that results in an unterminated string starting with a double
quote, such as:
eval echo '"'
but such constructs are already problematic for not having a terminating
", rather than for ending in an unescaped backslash.)
--
Eric Blake, Principal Software Engineer
Red
On 06/29/2018 03:45 AM, Geoff Clare wrote:
Eric Blake wrote, on 28 Jun 2018:
I'm forwarding an email originally sent to the Cygwin list. What do others
think? Is there enough grounds in the argument below that the CX-shading in
POSIX is too strict compared to existing implementations
assifying perror() as byte--which is clearly is.
Therefore, the newlib perror() behavior is correct and should not be
changed. It definitely is a mess and there really ought to be a
perrorw() function.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
, that both represent the same
concept, but an iswFOO() test does not work on the latter example, since
it occupies more than one character).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
locale.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
=1078 where this
wording has been tightened to cover ALL locales, not just the POSIX
locale, to better match with C requirements on isdigit().
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
! interpreter).
https://www.freebsd.org/cgi/man.cgi?query=env
https://lists.gnu.org/archive/html/coreutils/2018-04/msg00011.html
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
heir own base_name() and dir_name() functions
with different (but reliable) semantics, eschewing the use of basename()
and dirname() in GNU code. (Another aspect of the GNU code is that on
DOS-like systems, base_name() handles drive letters, which is something
that basename() completely ignores
he shell continues afterwards:
>
> (exec printf '%g\n' "$float_value")
The standard does not require printf %g to work; can we use a better
example?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
signatur
56 matches
Mail list logo
