On 2019-07-05 17:38, Thomas Laus wrote:
I upgraded to CURRENT r349575 this week and my Dell Inspiron laptop
stops processing the rc.conf with this message that repeats until I
perform a hard power button reset, ctl-alt-del has no effect:
Root mount waiting for USBUS7 USBUS6 USBUS0.
I boote
Alan Somers wrote:
>On Fri, Jul 5, 2019 at 9:11 AM Rick Macklem wrote:
>>
>> Alan Somers wrote:
>> >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
>> >>
>> >> I have a little program for testing the copy_file_range(2) syscall I've
>> >> been
>> >> working on. (The current version is attached
On Fri, Jul 05, 2019 at 08:59:23PM +, Rick Macklem wrote:
> Konstantin Belousov wrote:
> >On Fri, Jul 05, 2019 at 07:30:54PM +0200, Jilles Tjoelker wrote:
> >> On Fri, Jul 05, 2019 at 12:28:51AM +, Rick Macklem wrote:
> >> > I have been working on a Linux compatible copy_file_range(2) sysca
Konstantin Belousov wrote:
>On Fri, Jul 05, 2019 at 07:30:54PM +0200, Jilles Tjoelker wrote:
>> On Fri, Jul 05, 2019 at 12:28:51AM +, Rick Macklem wrote:
>> > I have been working on a Linux compatible copy_file_range(2) syscall
>> > (the current code can be found at https://reviews.freebsd.org/
On Fri, Jul 05, 2019 at 07:30:54PM +0200, Jilles Tjoelker wrote:
> On Fri, Jul 05, 2019 at 12:28:51AM +, Rick Macklem wrote:
> > I have been working on a Linux compatible copy_file_range(2) syscall
> > (the current code can be found at https://reviews.freebsd.org/D20584).
>
> > One outstanding
On Fri, Jul 05, 2019 at 12:28:51AM +, Rick Macklem wrote:
> I have been working on a Linux compatible copy_file_range(2) syscall
> (the current code can be found at https://reviews.freebsd.org/D20584).
> One outstanding issue is how it should deal with signals. Right now, I
> have vn_start_wri
Hans Petter Selasky wrote:
>On 2019-07-05 02:28, Rick Macklem wrote:
>> I am thinking that copy_file_range(2) should do this also.
>> However, if it returns an error, it is impossible for the caller to know how
>> much
>> of the data range got copied.
>
>How can you kill a program stuck on copy_fi
I upgraded to CURRENT r349575 this week and my Dell Inspiron laptop
stops processing the rc.conf with this message that repeats until I
perform a hard power button reset, ctl-alt-del has no effect:
Root mount waiting for USBUS7 USBUS6 USBUS0.
I booted my kernel.old and everything is fine at
Mark Johnston wrote:
>On Fri, Jul 05, 2019 at 12:28:51AM +, Rick Macklem wrote:
>> Hi,
>>
>> I have been working on a Linux compatible copy_file_range(2) syscall
>> (the current code can be found at https://reviews.freebsd.org/D20584).
>>
>> One outstanding issue is how it should deal with sign
On Fri, Jul 5, 2019 at 9:28 AM Rick Macklem wrote:
>
> jilles wrote in copy_file_range.2:99
> > The Linux man page (from
> > http://man7.org/linux/man->pages/man2/copy_file_range.2.html ) says that a
> > non-zero flags argument will cause >the call to return an [EINVAL] error. I
> > think that
On Fri, Jul 5, 2019 at 9:11 AM Rick Macklem wrote:
>
> Alan Somers wrote:
> >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
> >>
> >> I have a little program for testing the copy_file_range(2) syscall I've
> >> been
> >> working on. (The current version is attached, in case anyone is
> >> i
On Thu, Jul 4, 2019 at 6:29 PM Rick Macklem wrote:
>
> Hi,
>
> I have been working on a Linux compatible copy_file_range(2) syscall
> (the current code can be found at https://reviews.freebsd.org/D20584).
>
> One outstanding issue is how it should deal with signals.
> Right now, I have vn_start_wr
jilles wrote in copy_file_range.2:99
> The Linux man page (from
> http://man7.org/linux/man->pages/man2/copy_file_range.2.html ) says that a
> non-zero flags argument will cause >the call to return an [EINVAL] error. I
> think that is better than ignoring the argument >completely since it allows
Alan Somers wrote:
>On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
>>
>> I have a little program for testing the copy_file_range(2) syscall I've been
>> working on. (The current version is attached, in case anyone is interested.)
>>
>> It take a few minutes to run on a slow system and uses abo
On Fri, Jul 05, 2019 at 12:28:51AM +, Rick Macklem wrote:
> Hi,
>
> I have been working on a Linux compatible copy_file_range(2) syscall
> (the current code can be found at https://reviews.freebsd.org/D20584).
>
> One outstanding issue is how it should deal with signals.
> Right now, I have v
On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
>
> I have a little program for testing the copy_file_range(2) syscall I've been
> working on. (The current version is attached, in case anyone is interested.)
>
> It take a few minutes to run on a slow system and uses about 6Gbytes of disk
> spac
On 2019-07-05 02:28, Rick Macklem wrote:
I am thinking that copy_file_range(2) should do this also.
However, if it returns an error, it is impossible for the caller to know how
much
of the data range got copied.
How can you kill a program stuck on copy_file_range(2) w/o catching signals?
--HP
17 matches
Mail list logo
