Jeremy C. Reed | 10 Jul 00:48 2011
Picon

rewrite or remove internals chap-regress.html

Can someone please rewrite or remove the internal's book's Chapter 6. 
Regression testing ?

http://www.netbsd.org/docs/internals/en/chap-regress.html

This was brought up on the internal www list.

NetBSD does have a consistent regression testing framework. Many 
components use ATF. Even a few developers automate test runs and 
generate reports.

Yoshiaki Miura | 14 Jul 08:28 2011

NetBSD Guide Chapter 33.1.3. Doesn't need copy module?

Hi, all.

sorry for my poor english.
In NetBSD Guide Chapter 33.1.3.
I think that before reboot, doesn't we need to copy module to '/stand/<ARCH>/'?

# mv /netbsd /netbsd.old # mv /usr/obj/sys/arch/<ARCH>/compile/<KERNEL>/netbsd / + # cp $OBJDIR/destdir.<ARCH>/stan/<ARCH>/<VERSION> /stand/<ARCH> #### or mv ? # shutdown -r now



Martin Husemann | 14 Jul 21:01 2011
Picon

Re: NetBSD Guide Chapter 33.1.3. Doesn't need copy module?

On Thu, Jul 14, 2011 at 03:28:30PM +0900, Yoshiaki Miura wrote:
> Hi, all.
> 
> sorry for my poor english.
> In NetBSD Guide Chapter 33.1.3.
> I think that before reboot, doesn't we need to copy module to 
> '/stand/≤ARCH>/'?

Yes, at least on i386 - most other archs use sane GENERIC kernels ;-)

Martin

Yoshiaki Miura | 15 Jul 06:49 2011

Re: NetBSD Guide Chapter 33.1.3. Doesn't need copy module?

 >On Thu, Jul 14, 2011 at 03:28:30PM +0900, Yoshiaki Miura wrote:
 >> Hi, all.
 >>
 >> sorry for my poor english.
 >> In NetBSD Guide Chapter 33.1.3.
 >> I think that before reboot, doesn't we need to copy module to > 
'/stand/≤ARCH>/'?

 >Yes, at least on i386 - most other archs use sane GENERIC kernels ;-)
 >
 >Martin

Is there anyone who going to edit this guide? or no need to do that?

Yoshiaki

Julian Fagir | 27 Jul 00:15 2011
Picon

Hackathon: August 10th to 14th (documentation)

Hello,

we will run the 15th NetBSD hackathon from August 10th to August 14th.

The general topic is documentation. Though you can of course work on
something else and just use the chance of some people gathered, I thought of
four main topics to address:

 1. Update and complete the several guides we have. The NetBSD guide could
 have some updates (e.g. one could write about npf, or write one guide for it
 on its own).
 The internals guide has many XXXs in it, too, and the part about regression
 testing is factually empty, and perhaps could need one guide on its own.

 2. The wiki still needs some work on it. As was adressed in the prior
 discussion, it's still difficult for users to participate in the wiki, they
 need an OpenID, need to be activated as all their actions in it.
 Additionally, the old wiki needs to be migrated completely into the new one.

 3. NetBSD could need some new advertising material. Anyone good in writing
 texts can make new texts for the current flyers, and if you're good with
 inkscape and scribus, creating one or two posters for exhibitions would be
 nice, too.

 4. Minor improvements (working on manpages), thinkin about versioning the
 documentation, address some topics that was not written about before.

All the single topics are written down on the wiki page
http://wiki.netbsd.org/hackathon/.
Feel free to add or remove points if appropriate.

To participate, just join the IRC-channel #netbsd-code on Freenode
(http://freenode.net) and tell us, or communicate via the mailing list.
The hackathon will be parallel to the CCC camp (http://camp.ccc.de) and
several NetBSD-folks will be there anyway. As we didn't make it to a village,
one could think of just meeting there (and possibly working).

Regards, Julian
Thomas Adam | 27 Jul 00:28 2011

Re: Hackathon: August 10th to 14th (documentation)

Hi,

[ Thanks for your efforts on this, it's refreshing to see. ]

On 26 July 2011 23:15, Julian Fagir <gnrp <at> komkon2.de> wrote:
> Hello,
>
> we will run the 15th NetBSD hackathon from August 10th to August 14th.

I've requested time off work especially for this; fingers crossed it's
approved.  :)  That way I plan to work hard on this hackathon for just
this purpose.

> The general topic is documentation. Though you can of course work on
> something else and just use the chance of some people gathered, I thought of
> four main topics to address:
>
>  1. Update and complete the several guides we have. The NetBSD guide could
>  have some updates (e.g. one could write about npf, or write one guide for it
>  on its own).
>  The internals guide has many XXXs in it, too, and the part about regression
>  testing is factually empty, and perhaps could need one guide on its own.

Flash support is a topic which comes up a lot on IRC, so if there's a
willing to address all possible solutions to a working flash player,
that'd be good; even if it include alternatives such as using clive,
youtube-dl, etc.

>  2. The wiki still needs some work on it. As was adressed in the prior
>  discussion, it's still difficult for users to participate in the wiki, they
>  need an OpenID, need to be activated as all their actions in it.
>  Additionally, the old wiki needs to be migrated completely into the new one.

This area is the one I am personally more interested in.  Note that I
originally instigated interest in this, and have to this day, a bunch
of HTML files converted from the so-called old wiki which might be of
some use still -- I'm trying to ask the powers that be (ahem, www <at> ) to
check the status of my account, so I can upload these changes before
the hackathon begins, at least so they're there for people to work on
when it starts, etc.

Another question I have is the purpose of the wiki -- obviously the
wiki is easily able to add information to existing, static documents,
such as the NetBSD guide, etc., do we care and/or handle the case
where there's a potential over time for the wiki to grow information
which never makes it back into any more official/static information?
For example, I'm worried that there's the potential for overlap
between wiki pages springing into existence which contain useful
information, and for someone new to read the official static docs, and
never learn of the wiki's content which contains cool information.

How do we address that?  Because currently the wiki sticks out like a
sore thumb in that case; and maybe it should -- maybe that's the whole
point of the wiki, I don't know.  I'd welcome feedback from others,
but ideally some thought needs to be given as to how the wiki ties in
(if at all) to the existing static information that NetBSD churns out.

>  4. Minor improvements (working on manpages), thinkin about versioning the
>  documentation, address some topics that was not written about before.

Do you have examples where this is currently the case, or people have
requested documentation on?

Thanks again for this, Julian, it's much appreciated by me personally.

-- Thomas Adam

(I am "thomas_adam" on IRC on freenode, in case it matters; in the
usual NetBSD haunts already mentioned.)

feralert | 29 Jul 12:56 2011
Picon

flaws/inconsistencies in 'The pkgsrc user's guide'

Hi there,

I am new to NetBSD and I am going through the documentation, which btw it is great and helps a lot.

I happened to get into some flaws as i go along, though.
My idea is to tell the maintainer so he can sort them out if possible.

Is this the right place to comment about this?
If not, can anyone point me in the right direction?.

Thanks a lot,
Fred.

Julian Fagir | 30 Jul 12:07 2011
Picon

Re: flaws/inconsistencies in 'The pkgsrc user's guide'

Hi,

> I am new to NetBSD and I am going through the documentation, which btw it is
> great and helps a lot.
> 
> I happened to get into some flaws as i go along, though.
> My idea is to tell the maintainer so he can sort them out if possible.
> 
> Is this the right place to comment about this?
> If not, can anyone point me in the right direction?.
if you find any flaws, you can either write them down and post them to
netbsd-docs, as you did right now. Alternatively, you can also fill a PR on
them.
If you have the corrections needed right at hand, you can also provide a diff
for what needs to be changed.

You can check out the guide (along with all other website-stuff) from the
CVS-repository as it is documented in the guide, §30. The directory you're
looking for is `htdocs`, and then in docs/ you will find the guides. If there
are only the .html-files, you might find a comment where the source files lie
in the Makefile.
The pkgsrc-guide e.g. resides at pkgsrc/doc/guide/files/.
Then just make your changes, supply a `diff -du` of them and supply them
along with the description in the PR, or in the mail.

Regards, Julian

PS: May I point you to the upcoming hackathon? It will be from 10th to 14th
August, so if you want to help a bit with the documentation, it would be the
best chance. ;) http://wiki.netbsd.org/hackathon/

Gmane