Re: add extract example to tar(1) man page

2023-08-02 Thread Peter J. Philipp
On Thu, Aug 03, 2023 at 07:23:45AM +0100, Jason McIntyre wrote: > On Wed, Aug 02, 2023 at 05:52:02PM -0400, aisha wrote: > > Hi, > > Someone - https://www.youtube.com/watch?v=NQ5uD5x8vzg - mentioned that > > our man page for tar(1) doesn't have an extract example, so I thought it > > would be g

Re: add extract example to tar(1) man page

2023-08-02 Thread Jason McIntyre
On Wed, Aug 02, 2023 at 05:52:02PM -0400, aisha wrote: > Hi, > Someone - https://www.youtube.com/watch?v=NQ5uD5x8vzg - mentioned that our > man page for tar(1) doesn't have an extract example, so I thought it would be > good to add a simple one which highlights a common use case. > > OK? > h

Re: Add exit status to route.8

2023-08-02 Thread A Tammy
On 8/2/23 18:59, Matthew Martin wrote: > On Wed, Aug 02, 2023 at 06:36:26PM -0400, A Tammy wrote: >> Not a huge fan of this complicated representation. >>> +.Ar command >>> +was invoked but failed with this exit status; >>> +see its manual page for more information. >>> +.It 126 >>> +.Ar command

Re: hardclock: move setitimer(2) code into itimer_update()

2023-08-02 Thread Scott Cheloha
On Thu, Jul 27, 2023 at 10:45:50PM -0500, Scott Cheloha wrote: > On Wed, Jul 26, 2023 at 11:16:19AM -0500, Scott Cheloha wrote: > > This is the next patch in the clock interrupt reorganization series. > > > > Now that statclock() is cleaned up we can turn to hardclock(). > > > > [...] > > > > Th

Re: Add exit status to route.8

2023-08-02 Thread Matthew Martin
On Wed, Aug 02, 2023 at 06:36:26PM -0400, A Tammy wrote: > Not a huge fan of this complicated representation. > > +.Ar command > > +was invoked but failed with this exit status; > > +see its manual page for more information. > > +.It 126 > > +.Ar command > > +was found but could not be invoked, or

Re: Add exit status to route.8

2023-08-02 Thread A Tammy
On 8/2/23 18:23, Matthew Martin wrote: > A user in IRC asked about route exec's exit status which seems > a reasonable thing to document. > > The text is a combination of .Ex -std and env(1). Also route exec > requires a command, so fix the .Op markup. > > > diff --git route.8 route.8 > index 887

Add exit status to route.8

2023-08-02 Thread Matthew Martin
A user in IRC asked about route exec's exit status which seems a reasonable thing to document. The text is a combination of .Ex -std and env(1). Also route exec requires a command, so fix the .Op markup. diff --git route.8 route.8 index 887446c1420..ee5bd15fa1a 100644 --- route.8 +++ route.8 @@

add extract example to tar(1) man page

2023-08-02 Thread aisha
Hi, Someone - https://www.youtube.com/watch?v=NQ5uD5x8vzg - mentioned that our man page for tar(1) doesn't have an extract example, so I thought it would be good to add a simple one which highlights a common use case. OK? Index: tar.1 ==

Re: [v2]: uvm_meter, schedcpu: make uvm_meter() an independent timeout

2023-08-02 Thread Claudio Jeker
On Wed, Aug 02, 2023 at 10:15:20AM -0500, Scott Cheloha wrote: > Now that the proc0 wakeup(9) is gone we can retry the other part of > the uvm_meter() patch. > > uvm_meter() is meant to run every 5 seconds, but for historical > reasons it is called from schedcpu() and it is scheduled against the >

[v2]: uvm_meter, schedcpu: make uvm_meter() an independent timeout

2023-08-02 Thread Scott Cheloha
Now that the proc0 wakeup(9) is gone we can retry the other part of the uvm_meter() patch. uvm_meter() is meant to run every 5 seconds, but for historical reasons it is called from schedcpu() and it is scheduled against the UTC clock. schedcpu() and uvm_meter() have different periods, so uvm_mete

Re: uvm_loadav: don't recompute schedstate_percpu.spc_nrun

2023-08-02 Thread Claudio Jeker
On Mon, Jul 31, 2023 at 10:21:11AM -0500, Scott Cheloha wrote: > On Fri, Jul 28, 2023 at 07:36:41PM -0500, Scott Cheloha wrote: > > claudio@ notes that uvm_loadav() pointlessly walks the allproc list to > > recompute schedstate_percpu.spn_nrun for each CPU. > > > > We can just use the value instea

changelist: add xorg.conf

2023-08-02 Thread Klemens Nanni
I had a few important changes in there and drm related crashes whilst editing/testing /etc/X11/xorg.conf did result in that file being empty afer reset and fsck, so a backup would be valuable. xorg.conf(5) lists a various .../xorg.conf and .../conf.d/*.conf files, but the single (default?) path se

Re: installer: proper disk crypto passphrase prompt loop

2023-08-02 Thread Klemens Nanni
On Wed, Aug 02, 2023 at 02:38:57PM +0300, Klemens Nanni wrote: > This needs "bioctl: do not confirm new passphrases on stdin" on tech@. > > Current code tries thrice to get matching passphrases before aborting; > simple enough to get the feature going, but also due to code limitations. > > One po

installer: proper disk crypto passphrase prompt loop

2023-08-02 Thread Klemens Nanni
This needs "bioctl: do not confirm new passphrases on stdin" on tech@. Current code tries thrice to get matching passphrases before aborting; simple enough to get the feature going, but also due to code limitations. One possible fix is to let the installer (not bioctl) prompt the passphrase like

bioctl: do not confirm new passphrases on stdin

2023-08-02 Thread Klemens Nanni
Creating new volumes prompts Passphrase: Re-type passphrase: which is sane for interative usage, but -s (which omits prompts) to read from stdin also prompts twice. I think that's neither intuitive nor ergonomical and as intended for non-interactive scripts, -s should take a new pa