6 ms·
The Open Group Base Specifications Issue 8
- job 2y agoThe POSIX.1-2024 specification now is available to the general public.
- tannhaeuser 2y agoChanges in system interfaces: https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_xsh_chap01.html#tag_22_01_01 https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_xsh... Changes to utilities: https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_xcu_chap01.html#tag_23_01 https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_xcu... Seems ratfor77 is gone ;) Now we only need to update LSB with Docker, io_uring, and systemd LOL
- jolmg 2y ago> A suggestion that was not adopted was to modify true and false to take an optional argument, and true would exit true only if the argument was non-zero, and false would exit false only if the argument was non-zero: > while true $(($x > 5 && $y <= 25)) That's good that it wasn't adopted. I think one of the primary points of usefulness of these commands is as substitutes for whatever other commands the admin may like. Like if you want a user to not have a login shell, you can set the shell to /bin/false. fakechroot also uses /bin/true to substitute other commands like systemctl and ischroot.[1] It just works best if true always returns true regardless of arguments, ditto false. The example use case isn't compelling either. In bash, you'd do this: while (( $x > 5 && $y <= 25 )) Wonder why `$(())` is standarized, but apparently `(())` isn't. [1] https://github.com/dex4er/fakechroot/blob/master/scripts/debootstrap.env.sh https://github.com/dex4er/fakechroot/blob/master/scripts/deb...
- fermigier 2y agoIIUC, here's the timeline: - Issue 8: 2024 - Issue 7: 2017 - Issue 6: 2004 - Issue 5: 1997 - Issue 4: 1992 - Issue 3: 1988
- deleted 2y ago[deleted]
- ykonstant 2y ago>Note, however, that "$(( x=5 ))" need not be equivalent to "$(( $x=5 ))" . If the value of the environment variable x is the string "y=" , the expansion of "$(( x=5 ))" would set x to 5 and output 5, but "$(( $x=5 ))" would output 0 if the value of the environment variable y is not 5 and would output 1 if the environment variable y is 5. Similarly, if the value of the environment variable is 4, the expansion of "$(( x=5 ))" would still set x to 5 and output 5, but "$(( $x=5 ))" (which would be equivalent to "$(( 4=5 ))" ) would yield a syntax error. Ah, never change, Unix shells :) I still love this bonkers language.
- BoingBoomTschak 2y agoI think I've used the previous iteration too much for my mental health, I instantly noticed the slight color change from bluish green to greenish blue.
- McUsr 2y agoNice to see a fellow Kraftwerk fan.
- xxmarkuski 2y agoI recommend looking up the Wikipedia article [0] on The Open Group, if you haven't heard of them yet. Among other things, they maintain standards such as LDAP and POSIX and also currently own the trademark for UNIX. [0] https://en.wikipedia.org/wiki/The_Open_Group https://en.wikipedia.org/wiki/The_Open_Group
- rerdavies 2y agoOut of curiousity, what is the point of having a publicly accessible standard that's exactly the same as an iso standard you have to pay to access?