A grammatical error in login.conf(5):
--- login.conf.5?rev=1.64 Sun Jan 6 15:27:44 2019
+++ login.conf.5Sun Jan 6 15:28:10 2019
@@ -104,7 +104,7 @@
.Pp
.It auth Ta list Ta Dv passwd Ta
Allowed authentication styles.
-The first value is the default styles.
+The first value is the
On Sun, Jan 06, 2019 at 03:30:10PM +0200, cho...@jtan.com wrote:
> A grammatical error in login.conf(5):
>
fixed, thanks.
jmc
> --- login.conf.5?rev=1.64 Sun Jan 6 15:27:44 2019
> +++ login.conf.5Sun Jan 6 15:28:10 2019
> @@ -104,7 +104,7 @@
> .Pp
> .It auth Ta list Ta Dv passw
Hi,
I wanted to know the value of tick, went to man.openbsd.org, and got
https://man.openbsd.org/tick
While the answer provided on this page below is accurate, IMHO it is not
useful. I had to do a grep on "tick" for the kern.clockrate sysctl. Something
like the below would be better.
Thanks
OpenBSD 6.4-current (GENERIC.MP) #562: Sat Jan 5 04:37:18 MST 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
1. unveil a file under an arbitrary directory
2. unveil root for default read-only
3. disable further unveils
4. open (RO) a file under the same directory th
Amit Kulkarni wrote:
> Hi,
>
> I wanted to know the value of tick, went to man.openbsd.org, and got
> https://man.openbsd.org/tick
>
> While the answer provided on this page below is accurate, IMHO it is not
> useful. I had to do a grep on "tick" for the kern.clockrate sysctl. Something
> like
Hi,
Amit Kulkarni wrote on Sun, Jan 06, 2019 at 12:16:30PM -0600:
> I wanted to know the value of tick, went to man.openbsd.org,
> and got https://man.openbsd.org/tick
>
> While the answer provided on this page below is accurate,
> IMHO it is not useful. I had to do a grep on "tick" for
> the ke
Lacking a proper problem description, here's a simpler program to
demonstrate the following issue:
I want the entire tree read-only, except for one file being writable
as well.
No matter in which order / and the exceptional file are unveiled, any
attempt to access files or directories under the s
Hi Ted,
i only saw your reply after sending mine.
Ted Unangst wrote on Sun, Jan 06, 2019 at 02:10:40PM -0500:
> This is meant to be programmer documentation, so I think it makes sense to
> keep it referring to sysctl.2. However, it's a good point that you shouldn't
> have to grep for clockinfo.
On Sun, 6 Jan 2019 20:40:17 +0100
Ingo Schwarze wrote:
> Hi Ted,
>
> i only saw your reply after sending mine.
>
> Ted Unangst wrote on Sun, Jan 06, 2019 at 02:10:40PM -0500:
>
> > This is meant to be programmer documentation, so I think it makes sense to
> > keep it referring to sysctl.2. How