> I’ll start by reducing it to the STIG context, i.e. “Does my Linux system support the i386 syscall table?” (We’ll revisit the more general issue later.)
@FaheemMitha the OP asked “Does my Linux system support the 32-bit syscall table?”, but if the question stems from the STIG, it’s really “Does my Linux system support the i386 syscall table?”
regardless of the relationship (if any) between the i386 syscall table and a putative general 32-bit syscall table
but there isn’t really a general 32-bit syscall table
@Jesse_b No, you can't walk a cat really. The leash is just to keep her from running out on a road or into people's gardens. I just follow her around for a bit. She usually spends the whole time sniffing leaves and grass and hiding from anything that moves.
We spent about 15 minutes at this spot, meaning exactly at this spot, not even moving 10 cm. instagram.com/p/BlWBOhQg1BD
@Jesse_b In your review of the edit unix.stackexchange.com/review/suggested-edits/252015 you wrote: This edit was intended to address the author of the post and makes no sense as an edit. It should have been written as a comment or an answer. How exactly did you mean it? The edit corrects an obvious mistake (oversight) of the author. I already explained it in the comment. On a Q&A site it does not make sense to leave the mistake there.
@Jesse_b Why do you think it does not make sense as an edit?
@Jesse_b Could you please look at the edit more carefully? The important change is not the subshell. It is the semicolon which changes the scope of the variable. The mistake was that the variable was set for the scope of the process ls but in fact it has to be set in the scope of the shell. It means that the variable assignment must be a separate command (so the semicolon). The subshell is not necessary. It is there for the good manner to revert the variable back to the original state.
@Jesse_b Of course the example would work (in most cases) the way it was originally written but this way has exactly the same effect as without the assignment: ls -- *[[:punct:]]txt
@Jesse_b So there are two possibilities how to correct the mistake a) Remove the assignment LC_ALL=C and the related description. b) Correct the assignment scope as in my edit. --- I think a) changes the original author's intent but b) does not.