> On 12. Sep 2020, at 11:06, Hartmann, O. wrote:
>
> On Sat, 12 Sep 2020 10:03:18 +0200
> Michael Gmelin wrote:
>
>>> On 12. Sep 2020, at 09:55, Hartmann, O.
>>> wrote:
>>> On Fri, 11 Sep 2020 07:18:33 -0600
>>> Alan Somers wrote:
> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
>
Am 12.09.20 um 11:05 schrieb Hartmann, O.:
> On Sat, 12 Sep 2020 10:03:18 +0200
> Michael Gmelin wrote:
>
>>> On 12. Sep 2020, at 09:55, Hartmann, O.
>>> wrote:
>>>
>>> On Fri, 11 Sep 2020 07:18:33 -0600
>>> Alan Somers wrote:
>>>
> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
>
On Sat, 12 Sep 2020 10:03:18 +0200
Michael Gmelin wrote:
> > On 12. Sep 2020, at 09:55, Hartmann, O.
> > wrote:
> >
> > On Fri, 11 Sep 2020 07:18:33 -0600
> > Alan Somers wrote:
> >
> >>> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
> >>> wrote:
> >>>
> >>> On Thu, 10 Sep 2020 10:44:08
> On 12. Sep 2020, at 09:55, Hartmann, O. wrote:
>
> On Fri, 11 Sep 2020 07:18:33 -0600
> Alan Somers wrote:
>
>>> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
>>> wrote:
>>>
>>> On Thu, 10 Sep 2020 10:44:08 -0600
>>> Alan Somers wrote:
>>>
No, it's devfs. I'll fix it.
On Fri, 11 Sep 2020 07:18:33 -0600
Alan Somers wrote:
> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
> wrote:
>
> > On Thu, 10 Sep 2020 10:44:08 -0600
> > Alan Somers wrote:
> >
> > > No, it's devfs. I'll fix it.
> > >
> > > On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone
> > > wrote:
> > > >
On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann wrote:
> On Thu, 10 Sep 2020 10:44:08 -0600
> Alan Somers wrote:
>
> > No, it's devfs. I'll fix it.
> >
> > On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone wrote:
> >
> > > I'm curious: does this give a similar issue?
> > >
> > > touch /tmp/foo
> > > cp
On Thu, 10 Sep 2020 10:44:08 -0600
Alan Somers wrote:
> No, it's devfs. I'll fix it.
>
> On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone wrote:
>
> > I'm curious: does this give a similar issue?
> >
> > touch /tmp/foo
> > cp /tmp/foo /tmo/foo2
> >
> > I'm wondering if the issue is that
On Thu, 10 Sep 2020 10:35:08 -0400
Michael Butler wrote:
> Is anyone else seeing failures like this in building world and, in my
> case, cron jobs as well?
>
>
> Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr
> --- all_subdir_sbin ---
> Building
On 9/10/20 12:17 PM, Ryan Stone wrote:
> I'm curious: does this give a similar issue?
>
> touch /tmp/foo
> cp /tmp/foo /tmo/foo2
>
> I'm wondering if the issue is that copy_file_range isn't handling
> empty files, or if it's a devfs issue.
An empty file doesn't generate the error ..
It seems that SVN r365549 broke "cp /dev/null ..."
imb
On 9/10/20 10:35 AM, Michael Butler wrote:
> Is anyone else seeing failures like this in building world and, in my
> case, cron jobs as well?
>
>
> Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr
> ---
Is anyone else seeing failures like this in building world and, in my
case, cron jobs as well?
Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr
--- all_subdir_sbin ---
Building /usr/obj/usr/src/amd64.amd64/sbin/bsdlabel/bsdlabel
--- all_subdir_stand ---
--- zfsboot.ldr ---
No, it's devfs. I'll fix it.
On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone wrote:
> I'm curious: does this give a similar issue?
>
> touch /tmp/foo
> cp /tmp/foo /tmo/foo2
>
> I'm wondering if the issue is that copy_file_range isn't handling
> empty files, or if it's a devfs issue.
>
>
> On Thu,
I'm curious: does this give a similar issue?
touch /tmp/foo
cp /tmp/foo /tmo/foo2
I'm wondering if the issue is that copy_file_range isn't handling
empty files, or if it's a devfs issue.
On Thu, Sep 10, 2020 at 11:45 AM Michael Butler
wrote:
>
> It seems that SVN r365549 broke "cp /dev/null
13 matches
Mail list logo