lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJaTeTom1yW_22CbTUa+6iMMpFsomnMhm6-WV0Uft+0FrzjqvQ@mail.gmail.com>
Date:	Wed, 26 Oct 2011 06:02:10 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	Michal Soltys <soltys@....info>
Cc:	stephen.hemminger@...tta.com, netdev@...r.kernel.org
Subject: Re: [PATCH] HFSC (7) & (8) documentation + assorted changes

On Wed, Oct 26, 2011 at 05:27, Michal Soltys wrote:
> On 26.10.2011 10:15, Mike Frysinger wrote:
>> I've read it many times over, but it's a lengthy chunk of text - so try
>> to be understanding in case I made some mistakes.
>
> TBH, I planned to do some fixes / corrections (minor ones) to the version I
> submitted back then, though I had two doubts after looking at it after a bit
> of time:
>
> - too long / too detailed / hard to read
>  (or ITOW, following HFSC paper to closely to be of practical use for
>  someone just wanting to know how it works, without [too] gritty
>  details)

i think there should be something here about HFSC.  having too much
information in a man page is better than none at all imo.

> - some friendlier format with man export (asciidoc ? yodl ?
>  reText ? etc. - not sure what's it the policy regarding iproute2)
>  as otherwise it will be quite a burden to maintain / update.

that's orthogonal to the patch i think.  all the iproute2 man pages
are written in roff.  let's keep that sep from getting HFSC
documentation into the tree.

> If my memory serves right, one of the corner cases described in it might
> have been fixed by a patch I submitted a good few months ago, though I'll
> have to read it to be sure. And there're few other small long-overdue
> patches I'm sitting on (they won't change anything algorithmically, but at
> least one could be noted in the text - though that can be changed any time
> in the future, and if the patches get accepted at all of course).
>
> Another thing was minor kernel patch to stab, and the docs assumed it was
> added (not sure if you corrected it).

if you want to post updates to the content, i can take care of the
*roff formatting.
-mike
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ