Re: undocumented command switches -OR- fix documentation fully

won't change that. > > IMHO there's nothing wrong, if software can do more than its  > documentation shows. It's not like it breaks documented behavior. Sometimes we're the other guy. I regularly look at other people's tools, trying to figure out what they implement, what they use. C

Re: undocumented command switches -OR- fix documentation fully

nd scientific education is for. Who do you think you're >> > > talking to, the mailing list archive readers of a social club for >> > > knitting for the elderly? That is correct too. Time will and does >> > > demonstrate it perfectly. >> > > >> > &g

Re: undocumented command switches -OR- fix documentation fully

gt; Are you trying to teach the OpenBSD devs how to write good > > > > software? > > > > > > > > Unix software? > > > > > > > > Really? > > > > > > > > REALLY ? > > > > > > > > On Mon, 2023-0

Re: undocumented command switches -OR- fix documentation fully

te it perfectly. >> >> On 9/25/23, Rudolf Leitgeb wrote: >> > Are you trying to teach the OpenBSD devs how to write good >> > software? >> > >> > Unix software? >> > >> > Really? >> > >> > REALLY ? >> >

Re: undocumented command switches -OR- fix documentation fully

ch the OpenBSD devs how to write good > > > software? > > > > > > Unix software? > > > > > > Really? > > > > > > REALLY ? > > > > > > On Mon, 2023-09-25 at 21:11 +, Eponymous Pseudonym wrote: > > > > > > >

Re: undocumented command switches -OR- fix documentation fully

; > > > Unix software? > > > > Really? > > > > REALLY ? > > > > On Mon, 2023-09-25 at 21:11 +, Eponymous Pseudonym wrote: > > > Standardisation, specification and documentation as a starting > > > point > > > for sof

Re: undocumented command switches -OR- fix documentation fully

. On 9/25/23, Rudolf Leitgeb wrote: > Are you trying to teach the OpenBSD devs how to write good software? > > Unix software? > > Really? > > REALLY ? > > On Mon, 2023-09-25 at 21:11 +, Eponymous Pseudonym wrote: >> Standardisation, specification and

Re: undocumented command switches -OR- fix documentation fully

Are you trying to teach the OpenBSD devs how to write good software? Unix software? Really? REALLY ? On Mon, 2023-09-25 at 21:11 +, Eponymous Pseudonym wrote: > Standardisation, specification and documentation as a starting point > for software creation is a normal, re

Re: undocumented command switches -OR- fix documentation fully

Standardisation, specification and documentation as a starting point for software creation is a normal, reliable and mandated (formally) methodology used everywhere from business to scientific, industrial, medical and military applications. It is not only normal but expected and even required

Re: undocumented command switches -OR- fix documentation fully

  documentation shows. It's not like it breaks documented behavior. On Mon, 2023-09-25 at 20:58 +0200, Marc Espie wrote: > Don't rant that long. > > Sometimes, documentation and code get out-of-synch for a lot of > reasons. > > - trying out stuff and documenting later. > - plain

Re: undocumented command switches -OR- fix documentation fully

Don't rant that long. Sometimes, documentation and code get out-of-synch for a lot of reasons. - trying out stuff and documenting later. - plain forgetting to update the documentation. - having some stuff for a transition period, and then killing it. Your point that stuff that stays around

Re: undocumented command switches -OR- fix documentation fully

on their own wits (and consumers of the program as an interpreter, for example scripts, compilers etc). Instead of just "using" the program and relying that the behaviour is predictable and.. somewhat "truthful" to the actual implementation specifics, by documentation / m

Re: undocumented command switches -OR- fix documentation fully

Apart from the obvious troll, I believe there is a point. >From time to time, I go to other projects and try to figure out how far we are from compatibility... Not documenting compat options means that somebody outside the project would have to guess at stuff, instead of just reading the manpage

Re: undocumented command switches -OR- fix documentation fully

In 5 years, the one true {,g,m}AWK is forked (again) as OpenAWK.. from GNU awk(1). Undocumented switches are kept for BSD consistency (at looks). We self-cope with BSD awk(1) in a number of miss-parsed struggled diffs and give up. Nobody cares. GNU userland is sup-positioning the BSD. We are

Re: undocumented command switches -OR- fix documentation fully

off the list" is fine too, but it's not solving the > problem that pokes your eyes too. Now, let me propose a goal that is > "admitting failure of upkeep in-house of important language utilities > integral to the core of UNIX". Separate it in ports and strip its > co

Re: undocumented command switches -OR- fix documentation fully

oal that is "admitting failure of upkeep in-house of important language utilities integral to the core of UNIX". Separate it in ports and strip its core to the system. Documentation is part of that, the split would be worth it on parts of the system that are exercised a lot, this one

Re: undocumented command switches -OR- fix documentation fully

Old man yells at cloud.

Re: undocumented command switches -OR- fix documentation fully

> I'm aware that i'm replying to an obvious troll. You mean undocumented switches are abuse to the system operators. So, stop trolling and fix the documentation or remove undocumented switches. The sooner the better, man/doc support is your skill. Not smearing, work accordingly! >

Re: undocumented command switches -OR- fix documentation fully

ith short options are so widely used that supporting them *for compatibility purposes only* makes the life easier for some people, for example for our porting team. In those cases, supporting them without cluttering up the documentation is a perfectly sane approach, in particular when the option is as us

undocumented command switches -OR- fix documentation fully

I don't know how you can tolerate this after all these years. >From one of the most important contributors to the project. In one of the most important system utilities and languages. IT IS DISGUSTING. FIX IT. ALL. Outcome like this: CVSROOT:/cvs Module name:src Changes by:

Re: Concise passage in OpenBSD documentation about motivation

Dear Mr. Nick, That must be the passage. I'm surprised it is so tame. I recall it being much more arrogant. Perhaps what changed is that I became more arrogant. With many thanks, please allow me the expression of my distinguish sentiments. Ibsen

Re: Concise passage in OpenBSD documentation about motivation

wrote: > > Dear colleagues, > > > > About 20 years ago I read in some OpenBSD documentation, likely the > > installation instructions, that we want people to copy our OpenBSD even > > if to use it even in proprietary products, because the alternative is

Re: Concise passage in OpenBSD documentation about motivation

On 7/18/23 13:26, Ibsen S Ripsbusker wrote: Dear colleagues, About 20 years ago I read in some OpenBSD documentation, likely the installation instructions, that we want people to copy our OpenBSD even if to use it even in proprietary products, because the alternative is that incompetent people

Re: Concise passage in OpenBSD documentation about motivation

of these people have one thing in common: they all keep their codebases as simple and clean as possible. On 2023年07月18日 17:26, Ibsen S Ripsbusker wrote: > Dear colleagues, > > About 20 years ago I read in some OpenBSD documentation, likely the > installation instructions, that we want people

Re: Concise passage in OpenBSD documentation about motivation

Am 18.07.2023 19:26 schrieb Ibsen S Ripsbusker: Dear colleagues, About 20 years ago I read in some OpenBSD documentation, likely the installation instructions, that we want people to copy our OpenBSD even if to use it even in proprietary products, because the alternative is that incompetent

Concise passage in OpenBSD documentation about motivation

Dear colleagues, About 20 years ago I read in some OpenBSD documentation, likely the installation instructions, that we want people to copy our OpenBSD even if to use it even in proprietary products, because the alternative is that incompetent people write their own software instead of copying

Re: Self-hosting OpenBSD server, any documentation?

On 7/8/23 1:03 AM, Theo de Raadt wrote: Jonathan Drews wrote: On Sat, Jul 8, 2023, at 01:42, Jonas Borchelt wrote: The book "Absolute OpenBSD" is an excellent choice to expand your knowledge of the OpenBSD operating system. It was written by Michael W. Lucas and is regarded as a

Re: Self-hosting OpenBSD server, any documentation?

https://www.openbsd.org/faq/index.html https://www.openbsdhandbook.com/ https://openbsdrouterguide.net/ These are easy to follow introductions. Also the man pages, all of the mentioned refer to them. On 7/8/23 09:32, lisper.drea...@tutanota.com wrote: Hi, misc! What documents would you

Re: Self-hosting OpenBSD server, any documentation?

Jonathan Drews wrote: > > > > On Sat, Jul 8, 2023, at 01:42, Jonas Borchelt wrote: > > The book "Absolute OpenBSD" is an excellent choice to expand your knowledge > > of the OpenBSD operating system. It was written by Michael W. Lucas and is > > regarded as a comprehensive resource for

Re: Self-hosting OpenBSD server, any documentation?

On Sat, Jul 8, 2023, at 01:42, Jonas Borchelt wrote: > The book "Absolute OpenBSD" is an excellent choice to expand your knowledge > of the OpenBSD operating system. It was written by Michael W. Lucas and is > regarded as a comprehensive resource for beginners and advanced users alike. > It

Re: Self-hosting OpenBSD server, any documentation?

The book "Absolute OpenBSD" is an excellent choice to expand your knowledge of the OpenBSD operating system. It was written by Michael W. Lucas and is regarded as a comprehensive resource for beginners and advanced users alike. It covers various aspects of OpenBSD, including installation,

Self-hosting OpenBSD server, any documentation?

Hi, misc! What documents would you recommend for setting up a self-hosted OpenBSD server? This way I might learn more about OpenBSD and what is under its hood. Cheers, Andy -- Sent with Tutanota, enjoy secure & ad-free emails.

OT: Thank you for a second to none documentation in OpenBSD!!!

Hi, I just wanted to take a moment to give you guys thanks big time! I guess I have been spoiled for the last 2+ decades using OpenBSD and always find what I need in the man pages and rarely needed to search the web for additional info. Even for a noob trying OpenBSD I realize how easy it

Re: Problem to set a printer with cups and foo2zjs documentation not up to date for foo2zjs

Hello When I try to print a page test with hplip and cups, I get : filter failed. When I try  to prind with openbsd lpd and hplip, I get from lpd-err : On 09/05/2023 19:16, Jon Fineman wrote:h x1.lacomte.net /etc/foomatic/HP-LaserJet_P1005.ppd /usr/local/bin/foo2zjs-wrapper: -w: unknown

Re: Problem to set a printer with cups and foo2zjs documentation not up to date for foo2zjs

On 2023-05-10, Jon Fineman wrote: > HP's web site says it is fully supported. > ... on Linux, with an additional proprietary binary plug-in download.

Re: Problem to set a printer with cups and foo2zjs documentation not up to date for foo2zjs

Does not work in what way? If you define it as a similar model does anything print? HP's web site says it is fully supported. On Wed, May 10, 2023 at 02:30:31PM +0200, BESSOT Jean-Michel wrote: Hello hplip does not work with this

Re: Problem to set a printer with cups and foo2zjs documentation not up to date for foo2zjs

Hello hplip does not work with this printer the P1005, that is why I need foo2zjs. The problem is when I download the driver I don't get a ppd file but an img file and I don't know what to  do with it. I tried to mount it but it didn't work.There is no explication in the foo2zjs doc. bye

Re: Problem to set a printer with cups and foo2zjs documentation not up to date for foo2zjs

I have a HP Office Jet 6970 (ink jet) and all I did was install cups and hplip (which is in ports). To get lpr to work without cups is a little more adventurous. The three scripts below should get you started. They depend on unix2dos (I forget which tools bundle this is from) and gs (which is in

Problem to set a printer with cups and foo2zjs documentation not up to date for foo2zjs

Hello I have a hp P1005 ( I know hp) and I try to install it on opennbsd. So I installed cups and foo2zjs but foo2zjs download an img file and I don't know what to do with it. There is no mention of img file in the INSTALL file. What do I need to do to make the printer work with the openbsd

Re: old UNIX documentation

On Sat, Jan 14, 2023 at 11:46:54PM +0100, Jan Stary wrote: > On Sep 13 07:04:55, j...@kerhand.co.uk wrote: > > > Long ago and far away, the Berkeley distributions used to ship an > > > assortment of system documentation in /usr/share/doc, including a > > > general

Re: old UNIX documentation

On Sep 13 07:04:55, j...@kerhand.co.uk wrote: > > Long ago and far away, the Berkeley distributions used to ship an > > assortment of system documentation in /usr/share/doc, including a > > general-purpose system administrators manual. > > > > I guess people didn't

Re: Probable error in softraid(4) documentation

Namaste Stuart, Tobias, > Sent: Thursday, January 05, 2023 at 4:58 PM > From: "Tobias Fiebig" > To: misc@openbsd.org > Subject: Re: Probable error in softraid(4) documentation > > Heho, > > On Wed, 2023-01-04 at 00:04 +, Stuart Henderson wrote: > &

Re: Probable error in softraid(4) documentation

Heho, On Wed, 2023-01-04 at 00:04 +, Stuart Henderson wrote: > stacking would refer to creating one softraid (say a raid1 mirror) > and then creating a separate softraid device (say a crypto volume) > using the first softraid disk as a component. Incidentally, if you happen to have a thing

Re: Probable error in softraid(4) documentation

On 2023-01-03, Puru Shartha wrote: > Namaste misc, > > The softraid(4) documentation states the following in the CAVEAT > section [1]: > > "Stacking disciplines (CRYPTO on top of RAID 1, for example) is not > supported at this time." > > Based on my limited

Probable error in softraid(4) documentation

Namaste misc, The softraid(4) documentation states the following in the CAVEAT section [1]: "Stacking disciplines (CRYPTO on top of RAID 1, for example) is not supported at this time." Based on my limited understanding, RAID 1C seems to allow the above. Also, Dhanyavaad Stefan f

Re: Documentation of wsconsctl keyboard.map format?

Le 2 décembre 2022 05:29:33 GMT+02:00, Alexis a écrit : > >Vlad Meșco writes: > >>> Good idea! I may try that. It would be too much to hope for a >>> setting that logs keycodes to some log file or to the console I >>> expect? >> >> I mean you could add some printfs or log(9) in `wskbd.c',

Re: Documentation of wsconsctl keyboard.map format?

Vlad Meșco writes: Good idea! I may try that. It would be too much to hope for a setting that logs keycodes to some log file or to the console I expect? I mean you could add some printfs or log(9) in `wskbd.c', probably in `wskbd_translate', assuming control flows through there on your

Re: Documentation of wsconsctl keyboard.map format?

Le 30 novembre 2022 21:40:17 GMT+02:00, "Vlad Meșco" a écrit : >On Wed, Nov 30, 2022 at 06:17:40AM +0100, Mike Fischer wrote: >> >> Also the semantics of these is unclear to me: >> #define KS_Cmd 0xf10d >> #define KS_Cmd1 0xf10e >> #define KS_Cmd2

Re: Documentation of wsconsctl keyboard.map format?

> > You can look at /usr/src/sbin/wsconsctl/map.parse.y > > Good idea! I’ll take a look. > > One thing I did notice was that the keysym examples I saw in the (sparse) > documentation did not work. For example: > # wsconsctl keyboard.map+="keysym Alt_L = A

Re: Documentation of wsconsctl keyboard.map format?

> Am 27.11.2022 um 19:48 schrieb Vlad Meșco : > > On Fri, Nov 25, 2022 at 03:32:20AM +0100, Mike Fischer wrote: >> >>> Am 24.11.2022 um 15:07 schrieb u...@disroot.org: >>> >>> Hello! >>> >>> I would like to find some

Re: Documentation of wsconsctl keyboard.map format?

On Fri, Nov 25, 2022 at 03:32:20AM +0100, Mike Fischer wrote: > > > Am 24.11.2022 um 15:07 schrieb u...@disroot.org: > > > > Hello! > > > > I would like to find some supporting documentation too, if anything is > > available, but for certain other reasons

Re: Documentation of wsconsctl keyboard.map format?

On 2022-11-25 05:32, Mike Fischer wrote: Am 24.11.2022 um 15:07 schrieb u...@disroot.org: Hello! I would like to find some supporting documentation too, if anything is available, but for certain other reasons (https://github.com/letoram/arcan/issues/263). Basically, this "desktop e

Re: Documentation of wsconsctl keyboard.map format?

> Am 24.11.2022 um 15:07 schrieb u...@disroot.org: > > Hello! > > I would like to find some supporting documentation too, if anything is > available, but for certain other reasons > (https://github.com/letoram/arcan/issues/263). Basically, this "desktop > engin

Re: Documentation of wsconsctl keyboard.map format?

s. https://www.x.org/wiki/XKB/ did seem to explain some relevant concepts though. For \ example the concept of levels which probably translates to the columns used in the \ keycode statements? But where are the definitions of which modifier (or combination \ thereof) selects which column? Hello!

Re: Documentation of wsconsctl keyboard.map format?

Le 24 novembre 2022 04:12:43 GMT+02:00, Mike Fischer a écrit : > >> Am 23.11.2022 um 11:43 schrieb Vlad Meșco : >> >> On Wed, Nov 23, 2022 at 06:57:17AM +, Jason McIntyre wrote: >>> On Wed, Nov 23, 2022 at 12:21:26AM +0100, Mike Fischer wrote: >> >> >>keyboard.encoding=us >>

Re: Documentation of wsconsctl keyboard.map format?

binations are missing or wrong. >>> >>> So I thought I could use keyboard.map settings to correct this. But I >>> can???t find any documentation of the format ??? very unusual for OpenBSD. >>> >>> Did I miss something? >>> >

Re: Documentation of wsconsctl keyboard.map format?

gt; >> `wsconsctl keyboard.encoding=de` helps, but several mappings are >> different/missing. For example the pipe character | should be alt-7 but >> isn???t. Mostly the alt-combinations are missing or wrong. >> >> So I thought I could use keyboard.map settings to

Re: Documentation of wsconsctl keyboard.map format?

macOS. > > > > `wsconsctl keyboard.encoding=de` helps, but several mappings are > > different/missing. For example the pipe character | should be alt-7 but > > isn???t. Mostly the alt-combinations are missing or wrong. > > > > So I thought I could use keyboard.map sett

Re: Documentation of wsconsctl keyboard.map format?

/missing. For example the pipe character | should be alt-7 but > isn???t. Mostly the alt-combinations are missing or wrong. > > So I thought I could use keyboard.map settings to correct this. But I can???t > find any documentation of the format ??? very unusual for OpenBSD. > >

Documentation of wsconsctl keyboard.map format?

are missing or wrong. So I thought I could use keyboard.map settings to correct this. But I can’t find any documentation of the format — very unusual for OpenBSD. Did I miss something? Can someone point me to the documentation please? Thanks! Mike

Re: afterboot(8), documentation and wscons

On Wed, Sep 07, 2022 at 07:26:39PM +, Micha?l Dupont wrote: > Hi everyone, > > I recently installed and configured OpenBSD on a laptop ??? works great! > > However, as a new user, I had trouble finding out about wscons(4), > and that I can use wsconsctl(8) for common laptop configuration >

afterboot(8), documentation and wscons

Hi everyone, I recently installed and configured OpenBSD on a laptop – works great! However, as a new user, I had trouble finding out about wscons(4), and that I can use wsconsctl(8) for common laptop configuration such as disabling the bell, setting the display brightness and enabling touchpad

bind(2) documentation about the socklen_t parameter

it in detail. I more or less know how bind(2) works regarding socklen_t, but am not comfortable enough to write documentation about it. Would you mind documenting it in OpenBSD, so that it may help me document it in Linux? Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar

Re: documentation

On Tue, 24 May 2022 12:36:50 -0300 Gustavo Rios wrote: > Hi folks, > > I would like to download a pdf version of the faq and pf guide for > openbsd 7.1. May some one here point me where i could fetch the pdf > documentation from ? > > Thanks a lot. > You might try wkhtmltopdf

Re: documentation

l and https://www.openbsd.org/faq/pf/index.html . The OpenBSD project does not provide PDF or manual page versions of these documents but only the HTML versions on the web. >> May some one here point me where i could fetch the pdf documentation >> from ? Of course, feel free to use any HTM

Re: documentation

On 2022-05-24, Nathaniel Nigro wrote: > any of the ftp mirrors with the "doc" directory should have historical > versions txt and pdf of the faq and the pf guide Those files are nearly 10 years out of date. -- Please keep replies on the mailing list.

Re: documentation

7.1. May some one here point me where i could fetch the pdf documentation > from ? > > Thanks a lot. > > -- > The lion and the tiger may be more powerful, but the wolves do not perform > in the circus >

Re: documentation

gt; Hi folks, > > I would like to download a pdf version of the faq and pf guide for openbsd > 7.1. May some one here point me where i could fetch the pdf documentation > from ? > > Thanks a lot. > > -- > The lion and the tiger may be more powerful, but the wolv

documentation

Hi folks, I would like to download a pdf version of the faq and pf guide for openbsd 7.1. May some one here point me where i could fetch the pdf documentation from ? Thanks a lot. -- The lion and the tiger may be more powerful, but the wolves do not perform in the circus

Re: pf documentation

On 2022-04-07, Steve Litt wrote: > I need some easy beginner's pf documentation as well as some > intermediate pf documentation. I plan to make an OpenBSD/pf firewall. I > haven't done this in ten years, and imagine pf and the process of > turning OpenBSD into a firewall have changed

Re: pf documentation

rk > > in newer versions of pf. > > > > Sent from my iPhone > > > > > On Apr 7, 2022, at 05:13, Steve Litt wrote: > > > > > > Hi all, > > > > > > I need some easy beginner's pf documentation as well as some > > > intermediate pf

Re: pf documentation

> > > > Hi all, > > > > I need some easy beginner's pf documentation as well as some > > intermediate pf documentation. I plan to make an OpenBSD/pf firewall. I > > haven't done this in ten years, and imagine pf and the process of > > turning OpenBSD into a fi

Re: pf documentation

need some easy beginner's pf documentation as well as some > intermediate pf documentation. I plan to make an OpenBSD/pf firewall. I > haven't done this in ten years, and imagine pf and the process of > turning OpenBSD into a firewall have changed in that time. > > Thanks, >

Re: pf documentation

Den tors 7 apr. 2022 kl 11:12 skrev Steve Litt : > > Hi all, > > I need some easy beginner's pf documentation as well as some > intermediate pf documentation. I plan to make an OpenBSD/pf firewall. I > haven't done this in ten years, and imagine pf and the process of

pf documentation

Hi all, I need some easy beginner's pf documentation as well as some intermediate pf documentation. I plan to make an OpenBSD/pf firewall. I haven't done this in ten years, and imagine pf and the process of turning OpenBSD into a firewall have changed in that time. Thanks, SteveT Steve Litt

Re: Passage about licensing from OpenBSD documentation

Paul Yep, that is definitely the authorative source. I've been using archive.org for a couple decades that I forget openbsd.org website uses CVS. 73 On February 8, 2022 9:11:56 AM MST, Paul de Weerd wrote: >On Tue, Feb 08, 2022 at 08:54:08AM -0700, deich...@placebonol.com wrote: >| Try

Re: Passage about licensing from OpenBSD documentation

On Tue, Feb 08, 2022 at 08:54:08AM -0700, deich...@placebonol.com wrote: | Try archive.org for older versions of openbsd.org. Or just the CVS repository. The openbsd.org website is under revision control, there's 26 years of history available over at http://cvsweb.openbsd.org/www/ You

Re: Passage about licensing from OpenBSD documentation

Try archive.org for older versions of openbsd.org. On February 8, 2022 8:39:46 AM MST, Ibsen S Ripsbusker wrote: >On Tue, Feb 8, 2022, at 15:25, Nick Holland wrote: >> Probably be one of these two pages, I think: >> >> https://www.openbsd.org/goals.html >> https://www.openbsd.org/policy.html >>

Re: Passage about licensing from OpenBSD documentation

On Tue, Feb 8, 2022, at 15:25, Nick Holland wrote: > Probably be one of these two pages, I think: > > https://www.openbsd.org/goals.html > https://www.openbsd.org/policy.html > > I call it the "Microsoft Question": which do you fear more? > 1) That MS uses your code and profits from your work >

Re: Passage about licensing from OpenBSD documentation

On 2/6/22 11:57 PM, Ibsen S Ripsbusker wrote: My great and good friends, Like 20 years ago while trying to install OpenBSD for the first time I read a short passage in OpenBSD documentation that I really liked. Does anyone know where I can find it? The passage that said very directly that we

Passage about licensing from OpenBSD documentation

My great and good friends, Like 20 years ago while trying to install OpenBSD for the first time I read a short passage in OpenBSD documentation that I really liked. Does anyone know where I can find it? The passage that said very directly that we license OpenBSD permissively because we know our

Re: Documentation error in pci_mapreg_probe(9)

On 2022-01-10 3:53 a.m., Jonathan Gray wrote: > On Mon, Jan 10, 2022 at 09:17:25PM +1100, Jonathan Gray wrote: >> On Mon, Jan 10, 2022 at 02:24:05AM -0700, Ted Bullock wrote: >>> >>> On 2022-01-10 2:18 a.m., Jonathan Gray wrote: On Sat, Jan 08, 2022 at 01:43:32PM -0700, Ted Bullock wrote:

Re: Documentation error in pci_mapreg_probe(9)

On 2022-01-10 3:53 a.m., Jonathan Gray wrote: > On Mon, Jan 10, 2022 at 09:17:25PM +1100, Jonathan Gray wrote: >> On Mon, Jan 10, 2022 at 02:24:05AM -0700, Ted Bullock wrote: >>> >>> On 2022-01-10 2:18 a.m., Jonathan Gray wrote: On Sat, Jan 08, 2022 at 01:43:32PM -0700, Ted Bullock wrote:

Re: Documentation error in pci_mapreg_probe(9)

On Mon, Jan 10, 2022 at 09:17:25PM +1100, Jonathan Gray wrote: > On Mon, Jan 10, 2022 at 02:24:05AM -0700, Ted Bullock wrote: > > > > On 2022-01-10 2:18 a.m., Jonathan Gray wrote: > > > On Sat, Jan 08, 2022 at 01:43:32PM -0700, Ted Bullock wrote: > > > > The manpage incorrectly describes the

Re: Documentation error in pci_mapreg_probe(9)

On Mon, Jan 10, 2022 at 02:24:05AM -0700, Ted Bullock wrote: > > On 2022-01-10 2:18 a.m., Jonathan Gray wrote: > > On Sat, Jan 08, 2022 at 01:43:32PM -0700, Ted Bullock wrote: > > > The manpage incorrectly describes the behaviour and usage of > > > pci_mapreg_probe(9). This function does not

Re: Documentation error in pci_mapreg_probe(9)

On 2022-01-10 2:18 a.m., Jonathan Gray wrote: On Sat, Jan 08, 2022 at 01:43:32PM -0700, Ted Bullock wrote: The manpage incorrectly describes the behaviour and usage of pci_mapreg_probe(9). This function does not return 0 for success and !0 for failure as described in the manual, see the diff

Re: Documentation error in pci_mapreg_probe(9)

On Sat, Jan 08, 2022 at 01:43:32PM -0700, Ted Bullock wrote: > The manpage incorrectly describes the behaviour and usage of > pci_mapreg_probe(9). This function does not return 0 for success and !0 > for failure as described in the manual, see the diff below for a > possible re-wording and

Documentation error in pci_mapreg_probe(9)

The manpage incorrectly describes the behaviour and usage of pci_mapreg_probe(9). This function does not return 0 for success and !0 for failure as described in the manual, see the diff below for a possible re-wording and corrected description. Index: share/man/man9/pci_mapreg_map.9

PCI configuration space documentation question

I'm reading pci_mapreg_type(9) and I'm wondering about the returns of this function. The documentation says it can return either PCI_MAPREG_TYPE_IO or PCI_MAPREG_TYPE_MEM. But I also see at least one driver checking the type for PCI_MAPREG_MEM_TYPE_64BIT Looking at the definitions

Re: Is fw_update documentation outdated?

Hi Ingo, On 2021/12/26 23:26, Ingo Schwarze wrote: > Hi Alexander, > > Alexander wrote on Sun, Dec 26, 2021 at 08:11:51PM +: > > On 2021/12/25 18:02, Ingo Schwarze wrote: > > >> The new fw_update shell script is not in CVS yet. > >> > >> This command provides a clue that could lead you to

Re: Is fw_update documentation outdated?

Hi Alexander, Alexander wrote on Sun, Dec 26, 2021 at 08:11:51PM +: > On 2021/12/25 18:02, Ingo Schwarze wrote: >> The new fw_update shell script is not in CVS yet. >> >> This command provides a clue that could lead you to suspect the above: >> >>$ grep -m 1 OpenBSD $(which fw_update)

Re: Is fw_update documentation outdated?

Thank you everyone for the helpful and detailed explanations! On 2021/12/25 18:02, Ingo Schwarze wrote: > The new fw_update shell script is not in CVS yet. > > This command provides a clue that could lead you to suspect the above: > >$ grep -m 1 OpenBSD $(which fw_update) > # $OpenBSD$

Re: Is fw_update documentation outdated?

ike this in > > $ man 8 fw_update > [...] > -n Dry run. Do not actually install or update any firmware > and whether it appears to be required by a driver. > [...] > (also https://man.openbsd.org/fw_update) I expect the documentation will be updated wh

Re: Is fw_update documentation outdated?

updated then, rather than after the reboot. This means noone needs a 2nd reboot to activate those firmwares. Some behaviours of the existing program may not survive, and others may get changes. It isn't finished yet, when it is, then documentation will be updated. Alexander wrote: > Hi all, >

Re: Is fw_update documentation outdated?

On Sat, Dec 25, 2021 at 04:07:07PM +, Alexander wrote: > at https://cvsweb.openbsd.org/src/usr.sbin/fw_update/ which has been in > the attic for the last 6 years. > Where do I actually find the version history of the fw_update that is > installed on my system in CVSweb? fw_update is a hard

Is fw_update documentation outdated?

when looking at https://cvsweb.openbsd.org/src/usr.sbin/fw_update/ which has been in the attic for the last 6 years. I'm guessing I'm just uninformed and don't understand CVSweb but I'd like to learn, so: Is the documentation for fw_update outdated? Where do I actually find the version history

Re: make documentation

> Date: Sun, 27 Jun 2021 21:47:01 +1000 > From: Reuben ua Bríġ > personally i would like to patch man so that it calls make > Date: Sun, 27 Jun 2021 16:52:22 +0200 > From: Ingo Schwarze > Over my dead body. i didnt realise it at the time, but the reason for ingos resistance is that what i

Re: Technical Documentation - CARP

s the protocol goes through or how the election of the master node > works specifically. > If you can provide any documentation on CARP it would be greatly > appreciated. > > In advance, thank you for any help you may provide. > > Best regards > > Jannick Weiss -- Kindest regards, Tom Smyth.

Re: Technical Documentation - CARP

ter node >> works specifically. >> If you can provide any documentation on CARP it would be greatly >> appreciated. > > https://www.openbsd.org/events.html lists a few talks some 15 years > ago which focused on PF and Carp, those might help. https://github.com/jed

Re: Technical Documentation - CARP

; > It is my understanding that it is you (OpenBSD) that have developed CARP. > I am having trouble finding information about CARP, such as the different > states the protocol goes through or how the election of the master node > works specifically. > If you can provide any doc

  1   2   3   4   5   6   >