Page MenuHomeFreeBSD

raichoo_googlemail.com (raichoo)
raichoo

Projects

User does not belong to any projects.

User Details

User Since
Aug 11 2018, 8:23 AM (31 w, 6 d)

Recent Activity

Jan 3 2019

raichoo_googlemail.com added a comment to D16688: Add a new Scripting section to the dtrace(1) man page..

It makes sense to me to include command line arguments in the man page. What I'm not clear on is how far you want to go here. Are you going to document the entire language? Just variables? Variables, subroutines, and aggregate functions? Why take this approach instead of converting the docbook source to something that can be read in a terminal? There is, e.g., docbook2mdoc available in ports.

To be clear, I would very much like to see improvements in FreeBSD's dtrace documentation. I'm not convinced that importing text from dtrace.org is a good way to go about that.

Jan 3 2019, 7:35 PM
raichoo_googlemail.com added a comment to D16688: Add a new Scripting section to the dtrace(1) man page..

What "examples" do you mean here? It's basically just describing the variables. I could certainly rewrite the sentences. It admittedly feels a bit weird to do something like this but if that's what the license requires I can take up on that task.

Jan 3 2019, 6:41 PM
raichoo_googlemail.com added a comment to D16688: Add a new Scripting section to the dtrace(1) man page..

I have already made such a change by importing documentation from the Handbook into the manpage. I've talked to @bcr asking the same question at the Essen Hackathon and he told me it would be okay. I personally would like to have something like this in the manpage since I use dtrace quite a bit and I'm missing proper documentation that is being shipped with FreeBSD that I can consume on the terminal. The manpage seems to be the obvious place for this since it's where people look first.

Jan 3 2019, 5:45 PM
raichoo_googlemail.com added a comment to D16688: Add a new Scripting section to the dtrace(1) man page..

Bumping this since it's been laying dormant for quite a while. Does this still need work to get merged? I've had people asking me things at 35c3 that have been documented here.

Jan 3 2019, 7:25 AM

Aug 23 2018

raichoo_googlemail.com added a comment to D16688: Add a new Scripting section to the dtrace(1) man page..

@bcr Noted. I'll keep that in mind in the future :)

Aug 23 2018, 6:58 PM
raichoo_googlemail.com added a comment to D16688: Add a new Scripting section to the dtrace(1) man page..

@bcr The date has already been bumped in the last diff (which has already been merged). Both of these patches were written more or less at the same time, do I still need to bump the date, and if so, what date? :)

Aug 23 2018, 6:54 PM

Aug 16 2018

raichoo_googlemail.com updated the diff for D16688: Add a new Scripting section to the dtrace(1) man page..

I have updated the patch regarding one of the comments. The other one should stay as it is since it's more consistent with the rest of the manpage is phrased.

Aug 16 2018, 1:05 PM

Aug 15 2018

raichoo_googlemail.com added a comment to D16671: Extend documentation for the dtrace(1) -x flag.

Some options are missing because I'm not that familiar with them. I will certainly try to make the documentation exhaustive at some point ^^. By the way, I have another PR working on the documentation. https://reviews.freebsd.org/D16688 If you find the time, I'd appreciate the feedback :)

Aug 15 2018, 7:12 AM

Aug 13 2018

raichoo_googlemail.com added inline comments to D16671: Extend documentation for the dtrace(1) -x flag.
Aug 13 2018, 8:41 PM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.
Aug 13 2018, 8:41 PM

Aug 11 2018

raichoo_googlemail.com set the repository for D16688: Add a new Scripting section to the dtrace(1) man page. to rS FreeBSD src repository.
Aug 11 2018, 9:08 PM
raichoo_googlemail.com created D16688: Add a new Scripting section to the dtrace(1) man page..
Aug 11 2018, 9:08 PM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.

Drew some formatting ideas from the zfs(8) manpage in an attempt to be consistent with the rest of the world.

Aug 11 2018, 1:22 PM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.

Added time units

Aug 11 2018, 12:35 PM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.

I have moved the size portion up. Apparently this also applies to strsize which I wasn't aware of.

Aug 11 2018, 11:58 AM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.

Added bufpolicy.

Aug 11 2018, 11:47 AM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.

Fixed a typo

Aug 11 2018, 11:38 AM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.

I have extracted the size options from the truncate(1) manpage since this is pretty much the same thing. I should probably also document the bufpolicy option.

Aug 11 2018, 11:20 AM
raichoo_googlemail.com updated the diff for D16671: Extend documentation for the dtrace(1) -x flag.
Aug 11 2018, 10:33 AM
raichoo_googlemail.com updated the summary of D16671: Extend documentation for the dtrace(1) -x flag.
Aug 11 2018, 10:17 AM
raichoo_googlemail.com created D16671: Extend documentation for the dtrace(1) -x flag.
Aug 11 2018, 10:16 AM