Re: documentation

Local copy of the website is easy to get with OpenBSD provided tools.
The website is managed through cvs(1) like all the rest of the project,

$ cvs -d [email protected]:/cvs checkout -P www/faq

That will pull down JUST the faq/ directory.  Leave off the /faq
if you want the whole website.


On 8/21/26 3:38 PM, broke wrote:
>>From Luke A. Call <[email protected]>:
>> wget can work nicely to download a web site locally. If you want to
>> email me separately I can show the command I've used. But then you'd
>> have to combine all the pages somehow with a script, as others said.
> 
> You speak with uncertainty, please take your time and give us the
> script, It will benefit Gustavo as well I believe. (I do not think
> it is possible and I've tried it myself)

dude.  you are the guy who proposed "chmod 0"ing files for security.

>>From Nick Holland <[email protected]>:
>> Today, almost every browser on almost every OS gives YOU the option to
>> "print to PDF".  So if you find it useful, you can do this yourself
>> quite "easily" (but tedious).
> 
> Asking them to "print to PDF" for every page on the /faq/ folder?
> Maybe you should get a sanity check.

welcome to my very short shit list. 
> When it comes to documentation of this kind, I can recall some websites
> out there that provides a download for the entire website as a folder
> archived to read, I think you do too.. It really isn't much pain for
> the people who already have the source with them to just put it on the
> website with a version number perhaps to keep track.
> 
> Instead of us wasting time, doing weird wget, curl, awk, blah blah
> hacks to get the entire website, openbsd.org could just put it on
> something like: https://openbsd.org/faq/faq_x.x.tar.gz!
> 
> If anyone from openbsd.org is reading this, please consider this.

Considered.  Rejected.

And you probably have no comprehension of how pissed off I am at you
for that statement, demanding work of others you won't perform yourself
and trivializing the effort.  I did this for quite a few years, it was
a pain in the ass.  That was when many computers didn't have the easy
ability to run a browser, and someone might have had use for it.
It's 2026 now.

Nick.