On 2024-03-17 17:12, Zachary Santer wrote:
> On Thu, Mar 14, 2024 at 11:14 AM Carl Edquist wrote:
>
>> Where things get sloppy is if you add some stuff in a pipeline after your
>> build script, which results in things getting block-buffered along the
>> way:
>>
>> $ ./build.sh | sed
I did some more investigation with stat(2). Running native on FreeBSD
with Python os package 'st_dev':
$ df -t ufs | cut -f 6 -w | sed 1d | xargs -I% python ~/stat.py %
/: 108
/tmp: 110
/var: 111
/var/tmp: 112
/usr: 113
/usr/local: 161
/usr/ports: 142
/usr/obj: 141
/usr/local/pgsql: 140
Following v5.2.1-679-g7e29ef8b8 symlinks specified on the command line
no longer induce an error if lchown() is not supported on the system.
* doc/coreutils.texi (chown invocation, chgrp invocation): Adjust
accordingly, and also use a macro to avoid duplication.
* src/chown-core.c: Use our more
On 25/01/2024 14:13, Pádraig Brady wrote:
On 25/01/2024 12:30, Johannes Segitz wrote:
Hello,
chown has a flag that prevents symlink following. chown/chmod is sometimes
used in %post/%pre sections of rpm packages to fix up permissions. When
this is done in user owned directories (somewhere
Disclaimer: I am not 100% certain whether this is a bug in GNU coreutils
or FreeBSD Linux emulation layer because the behavior is weird. So,
please bear with me.
Consider the following output on FreeBSD 13 from FreeBSD's df(1):
$ df -t ufs -b -T -a
Filesystem Type 512-blocks
