> On Apr 15, 2019, at 1:03 PM, Jay Patel wrote:
>
> Hello Travis and Patrick,
>
> With Travis' configuration for kernel and .bmp splash works but it wont boot
> to login prompt rather requires ctrl+alt+F1,F2 to drop to ttyE1-2 to login.
> is there any arguments needed to pass to boot to let
On Sun, Apr 14, 2019 at 12:30:24PM -0400, Greg Troxel wrote:
> Opinions differ about whether libfuse/perfuse and librefuse should be
> the standard approach. For a very long time, librefuse has been the
> standard approach. So obviously just changing to use libfuse is out of
> the question.
>
>
So, the following has been happening (and for go111), but I don't
understand the errors, nor have I any clue as to their cause.
Note that I do have Go 1.11.1 installed and working A-OK on this same
machine, but built against somewhat older OS.
13:31 [510] $ go version
go version
Mayuresh writes:
> 1. in mk/fuse.buildlink3.mk we should include
> filesystems/fuse/buildlink3.mk for NetBSD as well. Alternatively provide a
> choice to do so.
>
> [I have changed the code in an ad hoc manner right now. If the proposal is
> ok I'll try to do it neater and submit a patch. But I
Mayuresh writes:
> 1. in mk/fuse.buildlink3.mk we should include
> filesystems/fuse/buildlink3.mk for NetBSD as well. Alternatively provide a
> choice to do so.
>
> [I have changed the code in an ad hoc manner right now. If the proposal is
> ok I'll try to do it neater and submit a patch. But I
As described in a couple of other threads, filesystems/fuse-encfs is
nearly working well on NetBSD 8.0.
I am able to mount as non root user as well.
But I can't still write to the mounted directory as a non root user.
The encrypted directory, mount point, /dev/putter all are owned by the non
On Apr 8, 2019, at 8:15 AM, Stephen Borrill wrote:
On Sun, 7 Apr 2019, Michael van Elst wrote:
kab...@lich.phys.spbu.ru (Dima Veselov) writes:
If anyone knows - what is the best practice in
performance and fault-tolerance - ccd or LVM?
Neither is fault-tolerant, CCD only supports
On Sun, Apr 14, 2019 at 12:49:25PM +0530, Mayuresh wrote:
>
Just in case it matters: It was NetBSD 8.0_RC1 amd64 on the HDD while it
was NetBSD 8.0 amd64 on the flash drive mentioned in my last post.
Mayuresh
My 3 year old laptop internal hard drive had started showing "error
reading fsbn". The drive is still working, but I suppose that's a sign I
should prepare to replace it.
As a quick measure I installed NetBSD on an unused USB 2.0 64GB Sandisk
flash drive (aka stick/pen drive). It worked fine for
