Hi Ceridwen,
> For most of the variations I've done so far, I've been either
> depending on external utilities or had POSIX-compliant ways to execute
> them. The rest of the variations pose more problems.
[…]
I'm afraid I didn't get around to replying to this at the time and I'm
sure you have
On Wed, Jul 27, 2016 at 04:58:28PM -0400, Ceridwen wrote:
> > Using "setarch uname26" on non-x86 architectures may cause issues
> > with recent versions of glibc, too:
> All the variations can be disabled at the command line or with a config
> file, so anyone using reprotest can disable `kernel`
> > 1. user_group. The POSIX standard includes the notion of
> > user/group
> > ids, but the only ways it defines to change the uid/gid of
> > processes
> > are C functions. Unfortunately, there's also nothing in the POSIX
> > standard for creating users, though at least `chown` is. At the
> >
Ceridwen:
> For most of the variations I've done so far, I've been either
> depending on external utilities or had POSIX-compliant ways to execute
> them. The rest of the variations pose more problems.
>
> 1. user_group. The POSIX standard includes the notion of user/group
> ids, but the only
On 2016-07-27, Ceridwen wrote:
> For most of the variations I've done so far, I've been either
> depending on external utilities or had POSIX-compliant ways to execute
> them. The rest of the variations pose more problems.
...
> 5. kernel: While `uname` is in the POSIX standard, mechanisms for
>
For most of the variations I've done so far, I've been either
depending on external utilities or had POSIX-compliant ways to execute
them. The rest of the variations pose more problems.
1. user_group. The POSIX standard includes the notion of user/group
ids, but the only ways it defines to
