Updating src tree:
P src/bin/csh/csh.c
P src/bin/csh/dir.c
P src/bin/csh/func.c
P src/bin/csh/lex.c
P src/bin/csh/parse.c
P src/bin/csh/proc.c
P src/distrib/sets/lists/tests/mi
P src/etc/etc.news68k/MAKEDEV.conf
P src/external/gpl3/binutils/dist/bfd/config.bfd
P
Phew! At least there’s one other configuration seeing the same crash.
The Synology documentation is pretty confusing and to get things working I
played around with a lot of settings. Basically since it’s only used for local
access I’ve opened up the privileges for access to everything and
My NFS is on a DS218+ Synology NAS which I believe is based on a version of
Linux. FreeNAS is based on FreeBSD I think, if that makes any difference.
Could be something I haven’t configured properly on my NAS, but everything else
has been working fine for the last couple of years and it’s
I didn’t realize at the time that the iso file I was using for this was on an
NFS share. It crashes there, but if I move the file to a local disk then I
don’t see any crash and get the same output you got. This is the BT for
attempting this when the file is on an NFS share:
cpu1: Begin
On Sat, 8 Aug 2020 at 18:53, Robert Nestor wrote:
>
> Phew! At least there’s one other configuration seeing the same crash.
>
> The Synology documentation is pretty confusing and to get things working I
> played around with a lot of settings. Basically since it’s only used for
> local access
On Sat, 8 Aug 2020 at 18:07, Robert Nestor wrote:
>
> My NFS is on a DS218+ Synology NAS which I believe is based on a version of
> Linux. FreeNAS is based on FreeBSD I think, if that makes any difference.
>
> Could be something I haven’t configured properly on my NAS, but everything
> else
On Sat, 8 Aug 2020 at 17:52, Robert Nestor wrote:
>
> I didn’t realize at the time that the iso file I was using for this was on an
> NFS share. It crashes there, but if I move the file to a local disk then I
> don’t see any crash and get the same output you got. This is the BT for
>
On Sat, 8 Aug 2020 at 16:42, Chavdar Ivanov wrote:
>
> On Sat, 8 Aug 2020 at 16:51, Robert Nestor wrote:
> >
> > Done but I may have put it into the wrong category - PR kern/0
> >
> > On Aug 8, 2020, at 8:55 AM, Paul Goyette wrote:
> >
> > > On Sat, 8 Aug 2020, Robert Nestor wrote:
> > >
>
On Sat, 8 Aug 2020 at 16:51, Robert Nestor wrote:
>
> Done but I may have put it into the wrong category - PR kern/0
>
> On Aug 8, 2020, at 8:55 AM, Paul Goyette wrote:
>
> > On Sat, 8 Aug 2020, Robert Nestor wrote:
> >
> >> Stumbled over this trying to check on the format of a NetBSD CD.
Done but I may have put it into the wrong category - PR kern/0
On Aug 8, 2020, at 8:55 AM, Paul Goyette wrote:
> On Sat, 8 Aug 2020, Robert Nestor wrote:
>
>> Stumbled over this trying to check on the format of a NetBSD CD. This
>> is a newly installed system of 9.99.69 downloaded two
On Sat, 8 Aug 2020, Robert Nestor wrote:
Stumbled over this trying to check on the format of a NetBSD CD. This
is a newly installed system of 9.99.69 downloaded two days ago with
all the installed packages rebuilt and installed under it, so
everything is pretty much up to date.
Stumbled over this trying to check on the format of a NetBSD CD. This is a
newly installed system of 9.99.69 downloaded two days ago with all the
installed packages rebuilt and installed under it, so everything is pretty much
up to date.
vndconfig -c vnd0 NetBSD-9.99.69-amd64.iso
When trying to edit a file to which I don't have access, vi reports a
"record not found" error rather than reporting a permissions error!
I noticed while trying to edit /var/log/maillog from a non-privileged
user.
:)
++--+---+
|
In article ,
Michael van Elst wrote:
>ci4...@gmail.com (Chavdar Ivanov) writes:
>
>># tunefs -o time /dev/rdk5
>>tunefs: tuning /dev/rdk5
>>tunefs: optimization preference remains unchanged as time
>>tunefs: mount of /dev/dk1 on / updated <==
>
>If the device is "mounted", tunefs triggers a
14 matches
Mail list logo
