Dave Voutila writes:
Hi,
> Any takers?
>
> Here's an updated diff also removes some logic in config.c related to
> checking the value sent by vmctl(8)'s -b flag to see if it's the same as
> the root disk image (-d).
I don't know if this patch was committed already, but there is a mention
of ram
Helg writes:
Hi,
> I currently only have a port of the 2.x branch of libfuse (attached) but
> will also port the 3.x libfuse once I have user mounting working. I am
> not aware of any ports other than the latest version of sshfs that
> depends on 3.x. In any case, we will need to support libfuse
Jason McIntyre writes:
> On Tue, Jan 05, 2021 at 08:11:51PM +0100, Gr??goire Jadi wrote:
>
>> Hi,
>>
>> When both RemoteCommand and ssh command are provided, the connection
>> fails with:
>>
>> Cannot execute command-line and remote command.
>>
>> Though the message is clear, I was puzzled
Hi,
When both RemoteCommand and ssh command are provided, the connection
fails with:
Cannot execute command-line and remote command.
Though the message is clear, I was puzzled because I couldn't find any
information in the man pages. This patch adds a note in ssh_config(5).
diff --git usr.
Ingo Schwarze writes:
Hello Ingo,
> Hi Gregoire,
>
> Gregoire Jadi wrote on Tue, Apr 17, 2018 at 11:44:41AM +0200:
>> Ingo Schwarze writes:
>
>>> Feedback is welcome both on the general idea and on the specific
>>> implementation.
>
> The result of that feeback was "we don't want it, the whole
Ingo Schwarze writes:
Hi,
> Hi,
>
> Gregoire Jadi wrote on Fri, Mar 30, 2018 at 06:07:42PM +0200:
>
>> While working on a port of keyringer, I observed the following behavior
>> of rm(1) with the -P option: if the file does not have write permission,
>> the file is removed without being overwrit
Hello,
While working on a port of keyringer, I observed the following behavior
of rm(1) with the -P option: if the file does not have write permission,
the file is removed without being overwritten.
This is not the same behavior as shred(1) (from sysutils/coreutils) which do
not remove the file i
"Theo de Raadt" writes:
>> > I'd appreciate reports about how well it delivers and if any new
>> > problems show up.
>>
>> Tested on amd64 with softdep and softraid (CRYPTO).
>> Works as expected with suspend and hibernate.
>
> Thanks.
>
>> However, in both cases there is a warning in dmesg duri
Theo de Raadt writes:
> After recent reboot related improvements, I have some familiarity with
> tricking the vnode layer into a stable state.
>
> This should settle filesystems "clean" onto disk. If one does a
> suspend and then runs out of battery.. or experiences a crash or out
> of battery d
