On 02/19/2018 12:30 AM, Boruch Baum wrote:
I hope the list will continue to consider
the entirety of the suggestions in my post.
What exactly do you refer to? I think the other suggestions
seem to be based on knowing the PID, so given that this doesn't change
due to execve(), a workaround
On Monday, February 19, 2018 12:30:33 AM CET Boruch Baum wrote:
> On 2018-02-19 00:14, Bernhard Voelker wrote:
> > Have a nice day,
> > Berny
>
> Thank you for the kind wishes. I hope the list will continue to consider
> the entirety of the suggestions in my post.
As far as I can tell, all your
On 19/02/18 02:22, Declercq Laurent wrote:
> I think that I did found at least two bugs in cp(1) command when the
> --no-preserve=mode option is involved and when copying special file. I
> describe each of them below.
>
> 1. Mode set on special files seem to be wrong:
>
> Original file to
On 2/19/2018 at 8:35 PM, "Pádraig Brady" wrote:
>
>On 18/02/18 10:41, chadweis...@nym.hush.com wrote:
>>
>>> On 12/08/2017 11:38 AM, Eric B wrote:
Hello,
I am using coreutils version 8.27 on Fedora, and I don't see
>this fixed in
8.28's NEWS.
On 18/02/18 10:41, chadweis...@nym.hush.com wrote:
>
>> On 12/08/2017 11:38 AM, Eric B wrote:
>>> Hello,
>>>
>>> I am using coreutils version 8.27 on Fedora, and I don't see this fixed in
>>> 8.28's NEWS.
>>>
>>> $ seq 1 --help
>>> seq: invalid floating point argument: ‘--help’
>>> Try 'seq
I think that I did found at least two bugs in cp(1) command when the
--no-preserve=mode option is involved and when copying special file. I
describe each of them below.
1. Mode set on special files seem to be wrong:
Original file to copy: prw-rw-rw- 1 root staff 0 févr. 18 18:59 spfile
cp(1)