All of lore.kernel.org
 help / color / mirror / Atom feed
* documentation
@ 2017-03-27  5:53 Julia Lawall
  2017-03-27  9:38 ` [Outreachy kernel] documentation Gargi Sharma
  0 siblings, 1 reply; 62+ messages in thread
From: Julia Lawall @ 2017-03-27  5:53 UTC (permalink / raw)
  To: outreachy-kernel

Commenting on Varsha's comments made me think of of the semantics patch
below that I wrote at some time back to check kerneldoc comments.  Feel
free to see if it comes up with anything interesting.

julia

@initialize:ocaml@
@@

let tbl = ref []
let fnstart = ref []
let success = Hashtbl.create 101
let thefile = ref ""
let parsed = ref []
let nea = ref []

let parse file =
  thefile := List.nth (Str.split (Str.regexp "linux-next/") file) 1;
  let i = open_in file in
  let startline = ref 0 in
  let fn = ref "" in
  let ids = ref [] in
  let rec inside n =
    let l = input_line i in
    let n = n + 1 in
    match Str.split_delim (Str.regexp_string "*/") l with
      before::after::_ ->
	(if not (!fn = "")
	then tbl := (!startline,n,!fn,List.rev !ids)::!tbl);
	startline := 0;
	fn := "";
	ids := [];
	outside n
    | _ ->
	(match Str.split (Str.regexp "[ \t]+") l with
	  "*"::name::rest ->
	    let len = String.length name in
	    (if !fn = "" && len > 2 && String.sub name (len-2) 2 = "()"
	    then fn := String.sub name 0 (len-2)
	    else if !fn = "" && (not (rest = [])) && List.hd rest = "-"
	    then
	      if String.get name (len-1) = ':'
	      then fn := String.sub name 0 (len-1)
	      else fn := name
	    else if not(!fn = "") && len > 2 &&
	      String.get name 0 = '@' && String.get name (len-1) = ':'
	    then ids := (String.sub name 1 (len-2)) :: !ids);
	| _ -> ());
	inside n
  and outside n =
    let l = input_line i in
    let n = n + 1 in
    if String.length l > 2 && String.sub l 0 3 = "/**"
    then
      begin
	startline := n;
	inside n
      end
    else outside n in
  try outside 0 with End_of_file -> ()

let hashadd tbl k v =
  let cell =
    try Hashtbl.find tbl k
    with Not_found ->
      let cell = ref [] in
      Hashtbl.add tbl k cell;
      cell in
  cell := v :: !cell

@script:ocaml@
@@

tbl := [];
fnstart := [];
Hashtbl.clear success;
parsed := [];
nea := [];
parse (List.hd (Coccilib.files()))

@r@
identifier f;
position p;
@@

f@p(...) { ... }

@script:ocaml@
p << r.p;
f << r.f;
@@

parsed := f :: !parsed;
fnstart := (List.hd p).line :: !fnstart

@param@
identifier f;
type T;
identifier i;
parameter list[n] ps;
parameter list[n1] ps1;
position p;
@@

f@p(ps,T i,ps1) { ... }

@script:ocaml@
@@

tbl := List.rev (List.sort compare !tbl)

@script:ocaml@
p << param.p;
f << param.f;
@@

let myline = (List.hd p).line in
let prevline =
  List.fold_left
    (fun prev x ->
      if x < myline
      then max x prev
      else prev)
    0 !fnstart in
let _ =
  List.exists
    (function (st,fn,nm,ids) ->
      if prevline < st && myline > st && prevline < fn && myline > fn
      then
	begin
	  (if not (String.lowercase f = String.lowercase nm)
	  then
	    Printf.printf "%s:%d %s doesn't match preceding comment: %s\n"
	      !thefile myline f nm);
	  true
	end
      else false)
    !tbl in
()

@script:ocaml@
p << param.p;
n << param.n;
n1 << param.n1;
i << param.i;
f << param.f;
@@

let myline = (List.hd p).line in
let prevline =
  List.fold_left
    (fun prev x ->
      if x < myline
      then max x prev
      else prev)
    0 !fnstart in
let _ =
  List.exists
    (function (st,fn,nm,ids) ->
      if prevline < st && myline > st && prevline < fn && myline > fn
      then
	begin
	  (if List.mem i ids then hashadd success (st,fn,nm) i);
	  (if ids = [] (* arg list seems not obligatory *)
	  then ()
	  else if not (List.mem i ids)
	  then
	    Printf.printf "%s:%d %s doesn't appear in ids: %s\n"
	      !thefile myline i (String.concat " " ids)
	  else if List.length ids <= n || List.length ids <= n1
	  then
	    (if not (List.mem f !nea)
	    then
	      begin
		nea := f :: !nea;
		Printf.printf "%s:%d %s not enough args\n" !thefile myline f;
	      end)
	  else
	    let foundid = List.nth ids n in
	    let efoundid = List.nth (List.rev ids) n1 in
	    if not(foundid = i || efoundid = i)
	    then
	      Printf.printf "%s:%d %s wrong arg in position %d: %s\n"
		!thefile myline i n foundid);
	  true
	end
      else false)
    !tbl in
()

@script:ocaml@
@@
List.iter
  (function (st,fn,nm,ids) ->
    if List.mem nm !parsed
    then
      let entry =
	try !(Hashtbl.find success (st,fn,nm))
	with Not_found -> [] in
      List.iter
	(fun id ->
	  if not (List.mem id entry) && not (id = "...")
	  then Printf.printf "%s:%d %s not used\n" !thefile st id)
	ids)
  !tbl


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: [Outreachy kernel] documentation
  2017-03-27  5:53 documentation Julia Lawall
@ 2017-03-27  9:38 ` Gargi Sharma
  0 siblings, 0 replies; 62+ messages in thread
From: Gargi Sharma @ 2017-03-27  9:38 UTC (permalink / raw)
  To: Julia Lawall; +Cc: outreachy-kernel

On Mon, Mar 27, 2017 at 11:23 AM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> Commenting on Varsha's comments made me think of of the semantics patch
> below that I wrote at some time back to check kerneldoc comments.  Feel
> free to see if it comes up with anything interesting.
>
> julia
>
> @initialize:ocaml@
> @@
>
> let tbl = ref []
> let fnstart = ref []
> let success = Hashtbl.create 101
> let thefile = ref ""
> let parsed = ref []
> let nea = ref []
>
> let parse file =
>   thefile := List.nth (Str.split (Str.regexp "linux-next/") file) 1;
>   let i = open_in file in
>   let startline = ref 0 in
>   let fn = ref "" in
>   let ids = ref [] in
>   let rec inside n =
>     let l = input_line i in
>     let n = n + 1 in
>     match Str.split_delim (Str.regexp_string "*/") l with
>       before::after::_ ->
>         (if not (!fn = "")
>         then tbl := (!startline,n,!fn,List.rev !ids)::!tbl);
>         startline := 0;
>         fn := "";
>         ids := [];
>         outside n
>     | _ ->
>         (match Str.split (Str.regexp "[ \t]+") l with
>           "*"::name::rest ->
>             let len = String.length name in
>             (if !fn = "" && len > 2 && String.sub name (len-2) 2 = "()"
>             then fn := String.sub name 0 (len-2)
>             else if !fn = "" && (not (rest = [])) && List.hd rest = "-"
>             then
>               if String.get name (len-1) = ':'
>               then fn := String.sub name 0 (len-1)
>               else fn := name
>             else if not(!fn = "") && len > 2 &&
>               String.get name 0 = '@' && String.get name (len-1) = ':'
>             then ids := (String.sub name 1 (len-2)) :: !ids);
>         | _ -> ());
>         inside n
>   and outside n =
>     let l = input_line i in
>     let n = n + 1 in
>     if String.length l > 2 && String.sub l 0 3 = "/**"
>     then
>       begin
>         startline := n;
>         inside n
>       end
>     else outside n in
>   try outside 0 with End_of_file -> ()
>
> let hashadd tbl k v =
>   let cell =
>     try Hashtbl.find tbl k
>     with Not_found ->
>       let cell = ref [] in
>       Hashtbl.add tbl k cell;
>       cell in
>   cell := v :: !cell
>
> @script:ocaml@
> @@
>
> tbl := [];
> fnstart := [];
> Hashtbl.clear success;
> parsed := [];
> nea := [];
> parse (List.hd (Coccilib.files()))
>
> @r@
> identifier f;
> position p;
> @@
>
> f@p(...) { ... }
>
> @script:ocaml@
> p << r.p;
> f << r.f;
> @@
>
> parsed := f :: !parsed;
> fnstart := (List.hd p).line :: !fnstart
>
> @param@
> identifier f;
> type T;
> identifier i;
> parameter list[n] ps;
> parameter list[n1] ps1;
> position p;
> @@
>
> f@p(ps,T i,ps1) { ... }
>
> @script:ocaml@
> @@
>
> tbl := List.rev (List.sort compare !tbl)
>
> @script:ocaml@
> p << param.p;
> f << param.f;
> @@
>
> let myline = (List.hd p).line in
> let prevline =
>   List.fold_left
>     (fun prev x ->
>       if x < myline
>       then max x prev
>       else prev)
>     0 !fnstart in
> let _ =
>   List.exists
>     (function (st,fn,nm,ids) ->
>       if prevline < st && myline > st && prevline < fn && myline > fn
>       then
>         begin
>           (if not (String.lowercase f = String.lowercase nm)
>           then
>             Printf.printf "%s:%d %s doesn't match preceding comment: %s\n"
>               !thefile myline f nm);
>           true
>         end
>       else false)
>     !tbl in
> ()
>
> @script:ocaml@
> p << param.p;
> n << param.n;
> n1 << param.n1;
> i << param.i;
> f << param.f;
> @@
>
> let myline = (List.hd p).line in
> let prevline =
>   List.fold_left
>     (fun prev x ->
>       if x < myline
>       then max x prev
>       else prev)
>     0 !fnstart in
> let _ =
>   List.exists
>     (function (st,fn,nm,ids) ->
>       if prevline < st && myline > st && prevline < fn && myline > fn
>       then
>         begin
>           (if List.mem i ids then hashadd success (st,fn,nm) i);
>           (if ids = [] (* arg list seems not obligatory *)
>           then ()
>           else if not (List.mem i ids)
>           then
>             Printf.printf "%s:%d %s doesn't appear in ids: %s\n"
>               !thefile myline i (String.concat " " ids)
>           else if List.length ids <= n || List.length ids <= n1
>           then
>             (if not (List.mem f !nea)
>             then
>               begin
>                 nea := f :: !nea;
>                 Printf.printf "%s:%d %s not enough args\n" !thefile myline f;
>               end)
>           else
>             let foundid = List.nth ids n in
>             let efoundid = List.nth (List.rev ids) n1 in
>             if not(foundid = i || efoundid = i)
>             then
>               Printf.printf "%s:%d %s wrong arg in position %d: %s\n"
>                 !thefile myline i n foundid);
>           true
>         end
>       else false)
>     !tbl in
> ()
>
> @script:ocaml@
> @@
> List.iter
>   (function (st,fn,nm,ids) ->
>     if List.mem nm !parsed
>     then
>       let entry =
>         try !(Hashtbl.find success (st,fn,nm))
>         with Not_found -> [] in
>       List.iter
>         (fun id ->
>           if not (List.mem id entry) && not (id = "...")
>           then Printf.printf "%s:%d %s not used\n" !thefile st id)
>         ids)
>   !tbl
>
Hi Julia,

I get the following error when running this script:
Failure in rule starting on line 65
exn while in timeout_function
nth

The version of OCaml I'm using is : 4.02.3.

spatch --version
spatch version 1.0.6-00036-gb62df17 compiled with OCaml version 4.02.3
Flags passed to the configure script: --prefix=/usr
Python scripting support: yes
Syntax of regular expresssions: PCRE

Any pointers on why this might be happening?

Thanks,
Gargi
> --


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation.
  2020-06-07 21:23 ` Documentation Pablo Neira Ayuso
@ 2020-06-10 12:55   ` G.W. Haywood
  0 siblings, 0 replies; 62+ messages in thread
From: G.W. Haywood @ 2020-06-10 12:55 UTC (permalink / raw)
  To: Pablo Neira Ayuso via netfilter mailing list

Hi there,

On Sun, 7 Jun 2020, Pablo Neira Ayuso wrote:
> On Sat, Jun 06, 2020 at 06:09:22PM +0100, G.W. Haywood wrote:
> [...]
>> Ideally I'd like to know which process ID is using which connection.
> [...]
> Probably you may use ulogd2 instead for this use-case? Use the NFLOG
> input driver which includes the process UID and GID. You could match
> on the first packet new packet based on the conntrack information.
> [...]

Thanks for the suggestion.  I've installed ulogd2, and I'm now logging
packet data to a Postgres database.  It seems that it will be useful,
but it doesn't immediately answer the question of which process ID is
using which connection.  The process UID and GID don't really help me,
because there may be hundreds of processes with the same values.  It's
the unique PID that I need.  I've trawled through the details for the
set of plugins [3] installed by Debian's ulogd2 package:

.../ulogd/ $ find . -type f | xargs -I '{}' ulogd -i '{}' | less

but I see nothing there which seems to fit.  Am I missing something?
A couple of other modules appeared in searches [2], but nothing which
seems designed for my purpose.  Is there a central module repository?

Looking at the documentation [1] of nfnetlink_queue I see that I might
be able to get something which has "a good chance"(!) of being the PID
that I need.  Ideally I'd like something better than good chance, but
if that's the best that can be done maybe I can live with it, or hack
a module which does what I want based on something which exists. :/

I have more documentation patches, is this a good place to send them,
or should I send them elsewhere, or use a bug-tracking system, or...?

[1] https://home.regit.org/netfilter-en/using-nfqueue-and-libnetfilter_queue/comment-page-1/
[2] https://github.com/subfxnet/ulogd
[3]
ulogd_filter_HWHDR.so
ulogd_filter_IFINDEX.so
ulogd_filter_IP2BIN.so
ulogd_filter_IP2HBIN.so
ulogd_filter_IP2STR.so
ulogd_filter_MARK.so
ulogd_filter_PRINTFLOW.so
ulogd_filter_PRINTPKT.so
ulogd_filter_PWSNIFF.so
ulogd_inpflow_NFACCT.so
ulogd_inpflow_NFCT.so
ulogd_inppkt_NFLOG.so
ulogd_inppkt_ULOG.so
ulogd_inppkt_UNIXSOCK.so
ulogd_output_GPRINT.so
ulogd_output_GRAPHITE.so
ulogd_output_LOGEMU.so
ulogd_output_NACCT.so
ulogd_output_OPRINT.so
ulogd_output_PGSQL.so
ulogd_output_SYSLOG.so
ulogd_output_XML.so
ulogd_raw2packet_BASE.so

-- 

73,
Ged.

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation.
  2020-06-06 17:09 Documentation G.W. Haywood
@ 2020-06-07 21:23 ` Pablo Neira Ayuso
  2020-06-10 12:55   ` Documentation G.W. Haywood
  0 siblings, 1 reply; 62+ messages in thread
From: Pablo Neira Ayuso @ 2020-06-07 21:23 UTC (permalink / raw)
  To: G.W. Haywood; +Cc: netfilter

Hi,

On Sat, Jun 06, 2020 at 06:09:22PM +0100, G.W. Haywood wrote:
[...]
> Ideally I'd like to know which process ID is using which connection.
> Because there may be simultaneous connections, if I don't know which
> one is which, then I have to wait for all of them to go away before
> cleaning up, and this can sometimes take hours.  When a connection is
> first created I could mark it from user space.  Then I can look for
> the mark when it's time to clean up, but I'd prefer not to have to do
> that if there's a way of identifying it which does not involve this
> separate marking operation.  Is there such a way?
> 
> Secondly, I wanted to get conntrackd to log via syslog using facility
> 'mail'.  It won't do it.  It will log using 'local0' etc., but claims
> that facility 'mail' is not a known syslog facility (even though I am
> using it extensively in my milters).  This is my configuration, it is
> only very slightly edited from the Debian original:
> 
> 8<----------------------------------------------------------------------
> mail6:/etc/conntrackd# >>> cat conntrackd.conf
> General {
>         HashSize 8192
>         HashLimit 65535
> 
>         Syslog mail
> 
>         LockFile /var/lock/conntrackd.lock
> 
>         UNIX {
>                 Path /var/run/conntrackd.sock
> #               Backlog 20
>         }
> 
>         SocketBufferSize 262142
>         SocketBufferSizeMaxGrown 655355
> 
>         # default debian service unit file is of Type=notify
>         Systemd on
> }
> 
> Stats {
>         LogFile on
>         Syslog mail
> }
> 8<----------------------------------------------------------------------
> mail6:/etc/conntrackd# >>> service conntrackd restart
> [....] Stopping conntrackd[Sat Jun  6 17:22:07 2020] (pid=6268) [warning] 'mail' is not a known syslog facility, ignoring
> [Sat Jun  6 17:22:07 2020] (pid=6268) [warning] 'mail' is not a known syslog facility, ignoring.
> . ok [....] Starting conntrackd[Sat Jun  6 17:22:09 2020] (pid=6292)
> [warning] 'mail' is not a known syslog facility, ignoring
> [Sat Jun  6 17:22:09 2020] (pid=6292) [warning] 'mail' is not a known syslog facility, ignoring.
> . ok
> 8<----------------------------------------------------------------------
> 
> The man page is not clear on what facilities I can use; if I change
> facility 'mail' (for example) to 'local1' the warnings go away, but of
> course I don't want to do that.  It isn't a show-stopper, I can do it
> some other way, but it's a nuisance.

Probably you may use ulogd2 instead for this use-case? Use the NFLOG
input driver which includes the process UID and GID. You could match
on the first packet new packet based on the conntrack information.

conntrackd only supports a limited number of syslog facilities (only
daemon, local0 to local7), although it should be relatively easy to
extend it to support for other facilities.

> Thirdly, it seems that
> 
> http://conntrack-tools.netfilter.org/
> 
> and
> 
> http://conntrack-tools.netfilter.org/manual.html
> 
> haven't been updated since 2012.  Am I expected to be reading these,
> or is there something else more recent which replaces it?  The latest
> release of conntrack-tools mentioned on the site is 1.4.0, although my
> version of conntrack is 1.4.5 (- and it's a Debian package! -) and the
> man page does refer me to the conntrack-tools.netfilter.org Website.

The manual mostly focuses on conntrackd for state synchronization (high
availability) and the userspace conntrack helper mode.

> Examples in chapter 5, "Using conntrack: the command line interface":
> 
> [QUOTE]
> # conntrack -U -p tcp --dport 3486 --mark 10
>  tcp      6 431982 ESTABLISHED src=192.168.2.100 dst=123.59.27.117\
>  sport=34846 dport=993 packets=169 bytes=14322 src=123.59.27.117\
>  dst=192.168.2.100 sport=993 dport=34846 packets=113 bytes=34787\
>  [ASSURED] mark=1 secmark=0 use=1
> conntrack v0.9.7 (conntrack-tools): 1 flow entries has been updated.
> [/QUOTE]
> 
> (1) The mark in the command line is '10', not '1'.
> (2) The dport in the example is '993', not '3486' and not '34846'.

Fixed upstream, thanks.

> Point (2) applies to other examples in the same section.  All give me
> the impression of having been hand-crafted, rather than cut-n-pasted,
> for example because on updates and deletes the tool does not print the
> text "has been deleted"; it prints "have been deleted".
> 
> If the documents I'm reading are obsolete, I would suggest that they
> should be taken down, and that the man pages for conntrack, conntrackd
> and conntrackd.conf should be updated.  I'd be very happy to produce a
> few patches if I can get the right information.

I made a quick revamp:

http://git.netfilter.org/conntrack-tools/log/

There is information which is not included in the manpage,
specifically for the state synchronization (HA) and the userspace
connection tracking helpers.

The statistics mode, which is the one you're interested in, is not
documented there though.

Thanks.

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation.
@ 2020-06-06 17:09 G.W. Haywood
  2020-06-07 21:23 ` Documentation Pablo Neira Ayuso
  0 siblings, 1 reply; 62+ messages in thread
From: G.W. Haywood @ 2020-06-06 17:09 UTC (permalink / raw)
  To: netfilter

Hi there,

Thank you very much for netfilter and conntrack. :)

Although I'm a long-time user of netfilter/iptables, this is my first
time with the conntrack tools.  The things that I've found below came
from searches resulting from very specific requirements, which I have
so far achieved only in part.  Briefly, I want to see from user space
which running process is associated with a particular TCP connection,
and I especially want to know when the connection is terminated.  At
any one time on the box (which is a mail server) there may be just a
few of these processes running, or a few hundred.  Each connecting IP
may make one or several simultaneous connections, and each connection
will have up to three process spawned to handle it.  One of the three
processes will be a Sendmail child; it will handle these connections
directly, and it will communicate with the other process or processes
(milter processes) about the connection.  There may in total be many
thousands of connections, both TCP and UDP.  The UDP connections will
almost all be local IPC, and at the moment I'm not interested in them.

Firstly, it is _almost_ enough to see that _no_ connection from some
IP is now in the conntrack table, but it is not quite good enough for
my purpose.

Ideally I'd like to know which process ID is using which connection.
Because there may be simultaneous connections, if I don't know which
one is which, then I have to wait for all of them to go away before
cleaning up, and this can sometimes take hours.  When a connection is
first created I could mark it from user space.  Then I can look for
the mark when it's time to clean up, but I'd prefer not to have to do
that if there's a way of identifying it which does not involve this
separate marking operation.  Is there such a way?

Secondly, I wanted to get conntrackd to log via syslog using facility
'mail'.  It won't do it.  It will log using 'local0' etc., but claims
that facility 'mail' is not a known syslog facility (even though I am
using it extensively in my milters).  This is my configuration, it is
only very slightly edited from the Debian original:

8<----------------------------------------------------------------------
mail6:/etc/conntrackd# >>> cat conntrackd.conf
General {
         HashSize 8192
         HashLimit 65535

         Syslog mail

         LockFile /var/lock/conntrackd.lock

         UNIX {
                 Path /var/run/conntrackd.sock
#               Backlog 20
         }

         SocketBufferSize 262142
         SocketBufferSizeMaxGrown 655355

         # default debian service unit file is of Type=notify
         Systemd on
}

Stats {
         LogFile on
         Syslog mail
}
8<----------------------------------------------------------------------
mail6:/etc/conntrackd# >>> service conntrackd restart
[....] Stopping conntrackd[Sat Jun  6 17:22:07 2020] (pid=6268) [warning] 'mail' is not a known syslog facility, ignoring
[Sat Jun  6 17:22:07 2020] (pid=6268) [warning] 'mail' is not a known syslog facility, ignoring.
. ok 
[....] Starting conntrackd[Sat Jun  6 17:22:09 2020] (pid=6292) [warning] 'mail' is not a known syslog facility, ignoring
[Sat Jun  6 17:22:09 2020] (pid=6292) [warning] 'mail' is not a known syslog facility, ignoring.
. ok 
8<----------------------------------------------------------------------

The man page is not clear on what facilities I can use; if I change
facility 'mail' (for example) to 'local1' the warnings go away, but of
course I don't want to do that.  It isn't a show-stopper, I can do it
some other way, but it's a nuisance.

Thirdly, it seems that

http://conntrack-tools.netfilter.org/

and

http://conntrack-tools.netfilter.org/manual.html

haven't been updated since 2012.  Am I expected to be reading these,
or is there something else more recent which replaces it?  The latest
release of conntrack-tools mentioned on the site is 1.4.0, although my
version of conntrack is 1.4.5 (- and it's a Debian package! -) and the
man page does refer me to the conntrack-tools.netfilter.org Website.

Examples in chapter 5, "Using conntrack: the command line interface":

[QUOTE]
# conntrack -U -p tcp --dport 3486 --mark 10
  tcp      6 431982 ESTABLISHED src=192.168.2.100 dst=123.59.27.117\
  sport=34846 dport=993 packets=169 bytes=14322 src=123.59.27.117\
  dst=192.168.2.100 sport=993 dport=34846 packets=113 bytes=34787\
  [ASSURED] mark=1 secmark=0 use=1
conntrack v0.9.7 (conntrack-tools): 1 flow entries has been updated.
[/QUOTE]

(1) The mark in the command line is '10', not '1'.
(2) The dport in the example is '993', not '3486' and not '34846'.

Point (2) applies to other examples in the same section.  All give me
the impression of having been hand-crafted, rather than cut-n-pasted,
for example because on updates and deletes the tool does not print the
text "has been deleted"; it prints "have been deleted".

If the documents I'm reading are obsolete, I would suggest that they
should be taken down, and that the man pages for conntrack, conntrackd
and conntrackd.conf should be updated.  I'd be very happy to produce a
few patches if I can get the right information.

-- 

73,
Ged.

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2011-04-13 23:33 Documentation Eugene Shatsky
  2011-04-14  4:44 ` Documentation Jonáš Vidra
@ 2011-04-14 13:54 ` Edward Shishkin
  1 sibling, 0 replies; 62+ messages in thread
From: Edward Shishkin @ 2011-04-14 13:54 UTC (permalink / raw)
  To: Eugene Shatsky; +Cc: reiserfs-devel

On 04/14/2011 01:33 AM, Eugene Shatsky wrote:
> Greetings! I wonder if any materials about Reiser4 that were mentioned
> in several interviews, especially the one about the dancing tree, have
> been released or, if not yet, what is their status?


Hello.

There is no any strict formal description of DT.
I do have a draft of this, but don't have a time
to prepare a reference paper.

Some ideas can be found at Reiser's speaking at
Google talks. If it is not enough for you, then
ask your questions ;)

Thanks,
Edward.

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2011-04-13 23:33 Documentation Eugene Shatsky
@ 2011-04-14  4:44 ` Jonáš Vidra
  2011-04-14 13:54 ` Documentation Edward Shishkin
  1 sibling, 0 replies; 62+ messages in thread
From: Jonáš Vidra @ 2011-04-14  4:44 UTC (permalink / raw)
  To: Eugene Shatsky; +Cc: ReiserFS mailing list

Dne Thu, 14 Apr 2011 01:33:59 +0200 Eugene Shatsky  
<eugene.shatsky@gmail.com> napsal(a):

> Greetings! I wonder if any materials about Reiser4 that were mentioned
> in several interviews, especially the one about the dancing tree, have
> been released or, if not yet, what is their status?

There are several documents describing Reiser4 at
https://reiser4.wiki.kernel.org/index.php/Publications

-- 
Jonáš Vidra, vidra.jonas@seznam.cz
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2011-04-13 23:33 Eugene Shatsky
  2011-04-14  4:44 ` Documentation Jonáš Vidra
  2011-04-14 13:54 ` Documentation Edward Shishkin
  0 siblings, 2 replies; 62+ messages in thread
From: Eugene Shatsky @ 2011-04-13 23:33 UTC (permalink / raw)
  To: reiserfs-devel

Greetings! I wonder if any materials about Reiser4 that were mentioned
in several interviews, especially the one about the dancing tree, have
been released or, if not yet, what is their status?

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2011-02-01  9:37     ` documentation hansbkk
@ 2011-02-01 13:49       ` Roberto Spadim
  0 siblings, 0 replies; 62+ messages in thread
From: Roberto Spadim @ 2011-02-01 13:49 UTC (permalink / raw)
  To: hansbkk; +Cc: NeilBrown, Linux-RAID

nice! my vote to raid.wiki.kernel.org
there´s links on wikipedia to it? linux source code documentation?

2011/2/1  <hansbkk@gmail.com>:
> For others googling later, there's also good user-level intro
> information in SLES and RHEL's doc sets
>
> http://www.google.com/search?q=raid+site%3Adocs.redhat.com
> http://www.google.com/search?q=raid+site%3Awww.novell.com%2Fdocumentation
>
> Re the concept of "official" in the concept of open-source, to me it
> means the docs maintained by those who "own" the project.
>
> Otherwise, there is often a "canonical" central location maintained by
> the community, which although perhaps not complete nor kept up to date
> should at least point to the more authoritative sources for those
> learning about the topic.
>
> My two cents: I for one would vote for http://raid.wiki.kernel.org/ as
> this, and since Neil's time is better spent coding than updating
> user-level docs, those of us that would like to see better-maintained
> documentation should dig in and help create it. Of course whatever
> Neil can find the time to add at dev-tech levels is invaluable, and
> should at least be pointed to by the "official" wiki.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2011-01-31 22:14   ` documentation Roberto Spadim
@ 2011-02-01  9:37     ` hansbkk
  2011-02-01 13:49       ` documentation Roberto Spadim
  0 siblings, 1 reply; 62+ messages in thread
From: hansbkk @ 2011-02-01  9:37 UTC (permalink / raw)
  To: Roberto Spadim; +Cc: NeilBrown, Linux-RAID

For others googling later, there's also good user-level intro
information in SLES and RHEL's doc sets

http://www.google.com/search?q=raid+site%3Adocs.redhat.com
http://www.google.com/search?q=raid+site%3Awww.novell.com%2Fdocumentation

Re the concept of "official" in the concept of open-source, to me it
means the docs maintained by those who "own" the project.

Otherwise, there is often a "canonical" central location maintained by
the community, which although perhaps not complete nor kept up to date
should at least point to the more authoritative sources for those
learning about the topic.

My two cents: I for one would vote for http://raid.wiki.kernel.org/ as
this, and since Neil's time is better spent coding than updating
user-level docs, those of us that would like to see better-maintained
documentation should dig in and help create it. Of course whatever
Neil can find the time to add at dev-tech levels is invaluable, and
should at least be pointed to by the "official" wiki.

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2011-01-31 21:58 ` documentation NeilBrown
@ 2011-01-31 22:14   ` Roberto Spadim
  2011-02-01  9:37     ` documentation hansbkk
  0 siblings, 1 reply; 62+ messages in thread
From: Roberto Spadim @ 2011-01-31 22:14 UTC (permalink / raw)
  To: NeilBrown; +Cc: Linux-RAID

nice =]
could we put these information at
(Documentation/md.txt) i didn´t read yet, but could we put there?
hehehe if i don´t have linux-raid@vger.kernel.org as a maillist i
would read from there first, after wikipedia, and after try google...
i think documentation at source code level is nice, a documentattion
(.txt file) at linux source code, maybe is good, maybe not... maybe in
future everythink is at wikipedia or kernel documentation or stay at
.txt file, the point is, a easy to find place (if only have source
code: md.txt, if have internet google or wikipedia or yahoo or another
search system)
thanks neil!

2011/1/31 NeilBrown <neilb@suse.de>:
> On Mon, 31 Jan 2011 19:39:03 -0200 Roberto Spadim <roberto@spadim.com.br>
> wrote:
>
>> hi guys, where´s the official documentation page (wiki)? is it at
>> linux kernel source code? or at a wikipedia or another wiki page?
>> i found this:
>> http://www.linuxfoundation.org/collaborate/workgroups/linux-raid
>> at wikipedia
>> and some documentation inside kernel source code
>> what´s the most updated (official)?
>>
>
> "official" has always struck me as a rather strange term in this sort of
> context.  It implies that there is an 'office' which the 'official' holds.
> I wonder what this 'office' is....
>
> However to be useful instead of philosophical:
>
>  - the source code is the definitive documentation.  However few people can
>   read it very well.
>  - the man pages in the mdadm package are the formal documentation that I am
>   most likely to update in anything close to a timely manner.  In particular
>     man 4 md
>   is worth a read.
>  - An archive of this mailing line (linux-raid) is likely to be the best
>   informal source of documentation.  It contains lots of valuable
>   information, but of course is not structured very well.
>  - https://linux-raid.wiki.kernel.org/ is a community-maintained wiki which
>   should be reasonably reliable. (that is the same location as the link that
>   you found above).
>  - the doco in the kernel (Documentation/md.txt) is hardly ever updated and so
>   is probably badly out of date.  Sorry.
>  - As has been mentioned, http://neil.brown.name/blog/mdadm and
>   http://neil.brown.name/blog/SoftRaid sometimes contain useful information
>   but I don't write as often as I would like to.
>  - This is a Book: Managing RAID on Linux
>     http://oreilly.com/catalog/9781565927308/index.html?CMP=IL7015
>   however it is now about 8 years old, so it will be missing a lot of new
>   stuff.
>
> Hope that helps,
> NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2011-01-31 21:39 documentation Roberto Spadim
  2011-01-31 21:43 ` documentation Mathias Burén
@ 2011-01-31 21:58 ` NeilBrown
  2011-01-31 22:14   ` documentation Roberto Spadim
  1 sibling, 1 reply; 62+ messages in thread
From: NeilBrown @ 2011-01-31 21:58 UTC (permalink / raw)
  To: Roberto Spadim; +Cc: Linux-RAID

On Mon, 31 Jan 2011 19:39:03 -0200 Roberto Spadim <roberto@spadim.com.br>
wrote:

> hi guys, where´s the official documentation page (wiki)? is it at
> linux kernel source code? or at a wikipedia or another wiki page?
> i found this:
> http://www.linuxfoundation.org/collaborate/workgroups/linux-raid
> at wikipedia
> and some documentation inside kernel source code
> what´s the most updated (official)?
> 

"official" has always struck me as a rather strange term in this sort of
context.  It implies that there is an 'office' which the 'official' holds.
I wonder what this 'office' is....

However to be useful instead of philosophical:

 - the source code is the definitive documentation.  However few people can
   read it very well.
 - the man pages in the mdadm package are the formal documentation that I am
   most likely to update in anything close to a timely manner.  In particular
     man 4 md
   is worth a read.
 - An archive of this mailing line (linux-raid) is likely to be the best
   informal source of documentation.  It contains lots of valuable
   information, but of course is not structured very well.
 - https://linux-raid.wiki.kernel.org/ is a community-maintained wiki which
   should be reasonably reliable. (that is the same location as the link that
   you found above).
 - the doco in the kernel (Documentation/md.txt) is hardly ever updated and so
   is probably badly out of date.  Sorry.
 - As has been mentioned, http://neil.brown.name/blog/mdadm and 
   http://neil.brown.name/blog/SoftRaid sometimes contain useful information
   but I don't write as often as I would like to.
 - This is a Book: Managing RAID on Linux
     http://oreilly.com/catalog/9781565927308/index.html?CMP=IL7015
   however it is now about 8 years old, so it will be missing a lot of new
   stuff.

Hope that helps,
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2011-01-31 21:39 documentation Roberto Spadim
@ 2011-01-31 21:43 ` Mathias Burén
  2011-01-31 21:58 ` documentation NeilBrown
  1 sibling, 0 replies; 62+ messages in thread
From: Mathias Burén @ 2011-01-31 21:43 UTC (permalink / raw)
  To: Roberto Spadim; +Cc: Linux-RAID

On 31 January 2011 21:39, Roberto Spadim <roberto@spadim.com.br> wrote:
> hi guys, where´s the official documentation page (wiki)? is it at
> linux kernel source code? or at a wikipedia or another wiki page?
> i found this:
> http://www.linuxfoundation.org/collaborate/workgroups/linux-raid
> at wikipedia
> and some documentation inside kernel source code
> what´s the most updated (official)?
>
> --
> Roberto Spadim
> Spadim Technology / SPAEmpresarial
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

http://neil.brown.name/blog/mdadm has info.

// Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 62+ messages in thread

* documentation
@ 2011-01-31 21:39 Roberto Spadim
  2011-01-31 21:43 ` documentation Mathias Burén
  2011-01-31 21:58 ` documentation NeilBrown
  0 siblings, 2 replies; 62+ messages in thread
From: Roberto Spadim @ 2011-01-31 21:39 UTC (permalink / raw)
  To: Linux-RAID

hi guys, where´s the official documentation page (wiki)? is it at
linux kernel source code? or at a wikipedia or another wiki page?
i found this:
http://www.linuxfoundation.org/collaborate/workgroups/linux-raid
at wikipedia
and some documentation inside kernel source code
what´s the most updated (official)?

-- 
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2010-12-02 20:52           ` Documentation Robert Foerster
@ 2010-12-03  7:35             ` Christophe Aeschlimann
  0 siblings, 0 replies; 62+ messages in thread
From: Christophe Aeschlimann @ 2010-12-03  7:35 UTC (permalink / raw)
  To: openembedded-devel

Hi,

On 02.12.2010 21:52, Robert Foerster wrote:
> On Thu, Dec 2, 2010 at 3:37 PM, David Lambert <dave@lambsys.com> wrote:
> 
>> Thanks for all the suggestions. While on the subject, does a dictionary of
>> keywords with their meanings exist anywhere? Newbies like me may find it
>> very useful when browsing recipes. Some terms are intuitively obvious, such
>> as DEV_BASE, but others such as PR, INHERIT, PV, leave me with some
>> ambiguity.
>>
>>
> Some info can be found in the manual:
> http://docs.openembedded.org/usermanual/usermanual.html#recipes_versioning
> Discussed in the manual are many of the items which are initially confusing:
> P, PN, PV, PR, PF, S, D, WORDIR, etc

The poky handbook also gives a few useful definitions:

http://www.pokylinux.org/releases/green-3.3/doc/poky-handbook.html#var-glossary-a

> 
> Also useful is to read the bitbake manual, which defines the basic metadata
> syntax handled by bitbake. http://bitbake.berlios.de/manual/
> 
> Hope that helps.
> Bob
> 

[...]


-- 
Christophe Aeschlimann

Embedded Software Engineer

Advanced Communications Networks S.A.

Rue du Puits-Godet 8a
2000 Neuchâtel, Switzerland

Tél. +41 32 724 74 31

c.aeschlimann@acn-group.ch



^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2010-12-02 20:37         ` Documentation David Lambert
@ 2010-12-02 20:52           ` Robert Foerster
  2010-12-03  7:35             ` Documentation Christophe Aeschlimann
  0 siblings, 1 reply; 62+ messages in thread
From: Robert Foerster @ 2010-12-02 20:52 UTC (permalink / raw)
  To: openembedded-devel

On Thu, Dec 2, 2010 at 3:37 PM, David Lambert <dave@lambsys.com> wrote:

> Thanks for all the suggestions. While on the subject, does a dictionary of
> keywords with their meanings exist anywhere? Newbies like me may find it
> very useful when browsing recipes. Some terms are intuitively obvious, such
> as DEV_BASE, but others such as PR, INHERIT, PV, leave me with some
> ambiguity.
>
>
Some info can be found in the manual:
http://docs.openembedded.org/usermanual/usermanual.html#recipes_versioning
Discussed in the manual are many of the items which are initially confusing:
P, PN, PV, PR, PF, S, D, WORDIR, etc

Also useful is to read the bitbake manual, which defines the basic metadata
syntax handled by bitbake. http://bitbake.berlios.de/manual/

Hope that helps.
Bob



> Regards,
>
> Dave.
>
>
>
> On 12/01/2010 04:46 PM, Robert Foerster wrote:
>
>> On Wed, Dec 1, 2010 at 1:54 PM, Stefan Schmidt<stefan@datenfreihafen.org
>> >wrote:
>>
>>  Hello.
>>>
>>> On Wed, 2010-12-01 at 12:39, David Lambert wrote:
>>>
>>>> That is indeed the version of documentation that I was reading. To
>>>> be more specific, one of the subjects I was attempting to look up
>>>> was how to specialize a recipe using "amend.inc". I do not see any
>>>> documentation on this subject.
>>>>
>>> We lack a good technical writer in the community. IIRC there was a
>>> blogpost
>>> from
>>> Khem about it and maybe some more infos on the mailling list. Thats of
>>> course
>>> not the most straight forward location for the information.
>>>
>>> If you searched together the information it would be great if you could
>>> send a
>>> patch updating the manual with it. :)
>>>
>>> regards
>>> Stefan Schmidt
>>>
>>>
>>>  I'm not an expert on the subject, but I've managed to utilize amend.inc
>> based on some information I pieced together from the irc logs.  I hope to
>> soon write an article on how to use amend.inc, but haven't yet found the
>> time.
>>
>> (This is far from authoritative, but it's been working for me here)
>>
>> You need to add the following to build-dir/conf/local.conf (can also go in
>> overlay/conf/site.conf).
>> INHERIT += "amend"
>>
>> DEV_BASE = "${HOME}/dev/openembedded/dev"
>> COLLECTIONS = "${DEV_BASE}/overlay/recipes \
>>                 ${DEV_BASE}/openembedded/recipes"
>>
>> # By default, file:// SRC_URIs only look under the current .bb file.
>> # Prepend our overlays into the file:// search path, so we can override
>> # openembedded recipes' SRC_URI files. Also, ensure the openembedded
>> # files are always in the search path, so our overlay .bb's can
>> # reference upstream files.
>> FILESPATHBASE =. "${@ \
>>         ':'.join([os.path.join(recipedir, \
>>                                 os.path.basename(os.path.dirname( \
>>                                                         d.getVar('FILE',
>> 1)))) \
>>                 for recipedir in d.getVar('COLLECTIONS', 1).split()])}:"
>>
>>
>> You'll need to make DEV_BASE and COLLECTIONS match your setup.  This
>> assumes
>> that I have two trees with recipes:
>>  - openembedded
>>  - overlay
>>
>> This makes sure that for a given recipe, my local overlay will be in its
>> FILESPATH.
>>
>>
>> Now, for example, I've added a patch to psplash to adjust the colors.
>> In overlay/recipes/psplash/ I have two files:
>> amend.inc:
>> PR .= "-amend"
>> SRC_URI += "file://0001-tweaked-for-company-colors.patch"
>>
>> and my patch, named 0001-tweaked-for-company-colors.patch
>>
>> Now, the new patch will be applied when psplash is built.  Also, I like
>> updating PR with -amend, this way the package is now shown
>> as psplash-0.0+svnr422-r34-amend, so that I can easily tell that I've
>> amended the package.
>>
>> I'm sure there are others who can provide more/better information, but
>> that'll hopefully get you started.
>>
>> Regards,
>> Bob Foerster
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2010-12-01 22:46       ` Documentation Robert Foerster
@ 2010-12-02 20:37         ` David Lambert
  2010-12-02 20:52           ` Documentation Robert Foerster
  0 siblings, 1 reply; 62+ messages in thread
From: David Lambert @ 2010-12-02 20:37 UTC (permalink / raw)
  To: openembedded-devel

Thanks for all the suggestions. While on the subject, does a dictionary 
of keywords with their meanings exist anywhere? Newbies like me may find 
it very useful when browsing recipes. Some terms are intuitively 
obvious, such as DEV_BASE, but others such as PR, INHERIT, PV, leave me 
with some ambiguity.

Regards,

Dave.


On 12/01/2010 04:46 PM, Robert Foerster wrote:
> On Wed, Dec 1, 2010 at 1:54 PM, Stefan Schmidt<stefan@datenfreihafen.org>wrote:
>
>> Hello.
>>
>> On Wed, 2010-12-01 at 12:39, David Lambert wrote:
>>> That is indeed the version of documentation that I was reading. To
>>> be more specific, one of the subjects I was attempting to look up
>>> was how to specialize a recipe using "amend.inc". I do not see any
>>> documentation on this subject.
>> We lack a good technical writer in the community. IIRC there was a blogpost
>> from
>> Khem about it and maybe some more infos on the mailling list. Thats of
>> course
>> not the most straight forward location for the information.
>>
>> If you searched together the information it would be great if you could
>> send a
>> patch updating the manual with it. :)
>>
>> regards
>> Stefan Schmidt
>>
>>
> I'm not an expert on the subject, but I've managed to utilize amend.inc
> based on some information I pieced together from the irc logs.  I hope to
> soon write an article on how to use amend.inc, but haven't yet found the
> time.
>
> (This is far from authoritative, but it's been working for me here)
>
> You need to add the following to build-dir/conf/local.conf (can also go in
> overlay/conf/site.conf).
> INHERIT += "amend"
>
> DEV_BASE = "${HOME}/dev/openembedded/dev"
> COLLECTIONS = "${DEV_BASE}/overlay/recipes \
>                  ${DEV_BASE}/openembedded/recipes"
>
> # By default, file:// SRC_URIs only look under the current .bb file.
> # Prepend our overlays into the file:// search path, so we can override
> # openembedded recipes' SRC_URI files. Also, ensure the openembedded
> # files are always in the search path, so our overlay .bb's can
> # reference upstream files.
> FILESPATHBASE =. "${@ \
>          ':'.join([os.path.join(recipedir, \
>                                  os.path.basename(os.path.dirname( \
>                                                          d.getVar('FILE',
> 1)))) \
>                  for recipedir in d.getVar('COLLECTIONS', 1).split()])}:"
>
>
> You'll need to make DEV_BASE and COLLECTIONS match your setup.  This assumes
> that I have two trees with recipes:
>   - openembedded
>   - overlay
>
> This makes sure that for a given recipe, my local overlay will be in its
> FILESPATH.
>
>
> Now, for example, I've added a patch to psplash to adjust the colors.
> In overlay/recipes/psplash/ I have two files:
> amend.inc:
> PR .= "-amend"
> SRC_URI += "file://0001-tweaked-for-company-colors.patch"
>
> and my patch, named 0001-tweaked-for-company-colors.patch
>
> Now, the new patch will be applied when psplash is built.  Also, I like
> updating PR with -amend, this way the package is now shown
> as psplash-0.0+svnr422-r34-amend, so that I can easily tell that I've
> amended the package.
>
> I'm sure there are others who can provide more/better information, but
> that'll hopefully get you started.
>
> Regards,
> Bob Foerster
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2010-12-01 18:54     ` Documentation Stefan Schmidt
@ 2010-12-01 22:46       ` Robert Foerster
  2010-12-02 20:37         ` Documentation David Lambert
  0 siblings, 1 reply; 62+ messages in thread
From: Robert Foerster @ 2010-12-01 22:46 UTC (permalink / raw)
  To: openembedded-devel

On Wed, Dec 1, 2010 at 1:54 PM, Stefan Schmidt <stefan@datenfreihafen.org>wrote:

> Hello.
>
> On Wed, 2010-12-01 at 12:39, David Lambert wrote:
> > That is indeed the version of documentation that I was reading. To
> > be more specific, one of the subjects I was attempting to look up
> > was how to specialize a recipe using "amend.inc". I do not see any
> > documentation on this subject.
>
> We lack a good technical writer in the community. IIRC there was a blogpost
> from
> Khem about it and maybe some more infos on the mailling list. Thats of
> course
> not the most straight forward location for the information.
>
> If you searched together the information it would be great if you could
> send a
> patch updating the manual with it. :)
>
> regards
> Stefan Schmidt
>
>
I'm not an expert on the subject, but I've managed to utilize amend.inc
based on some information I pieced together from the irc logs.  I hope to
soon write an article on how to use amend.inc, but haven't yet found the
time.

(This is far from authoritative, but it's been working for me here)

You need to add the following to build-dir/conf/local.conf (can also go in
overlay/conf/site.conf).
INHERIT += "amend"

DEV_BASE = "${HOME}/dev/openembedded/dev"
COLLECTIONS = "${DEV_BASE}/overlay/recipes \
                ${DEV_BASE}/openembedded/recipes"

# By default, file:// SRC_URIs only look under the current .bb file.
# Prepend our overlays into the file:// search path, so we can override
# openembedded recipes' SRC_URI files. Also, ensure the openembedded
# files are always in the search path, so our overlay .bb's can
# reference upstream files.
FILESPATHBASE =. "${@ \
        ':'.join([os.path.join(recipedir, \
                                os.path.basename(os.path.dirname( \
                                                        d.getVar('FILE',
1)))) \
                for recipedir in d.getVar('COLLECTIONS', 1).split()])}:"


You'll need to make DEV_BASE and COLLECTIONS match your setup.  This assumes
that I have two trees with recipes:
 - openembedded
 - overlay

This makes sure that for a given recipe, my local overlay will be in its
FILESPATH.


Now, for example, I've added a patch to psplash to adjust the colors.
In overlay/recipes/psplash/ I have two files:
amend.inc:
PR .= "-amend"
SRC_URI += "file://0001-tweaked-for-company-colors.patch"

and my patch, named 0001-tweaked-for-company-colors.patch

Now, the new patch will be applied when psplash is built.  Also, I like
updating PR with -amend, this way the package is now shown
as psplash-0.0+svnr422-r34-amend, so that I can easily tell that I've
amended the package.

I'm sure there are others who can provide more/better information, but
that'll hopefully get you started.

Regards,
Bob Foerster


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2010-12-01 18:39   ` Documentation David Lambert
@ 2010-12-01 18:54     ` Stefan Schmidt
  2010-12-01 22:46       ` Documentation Robert Foerster
  0 siblings, 1 reply; 62+ messages in thread
From: Stefan Schmidt @ 2010-12-01 18:54 UTC (permalink / raw)
  To: openembedded-devel

Hello.

On Wed, 2010-12-01 at 12:39, David Lambert wrote:
> That is indeed the version of documentation that I was reading. To
> be more specific, one of the subjects I was attempting to look up
> was how to specialize a recipe using "amend.inc". I do not see any
> documentation on this subject.

We lack a good technical writer in the community. IIRC there was a blogpost from
Khem about it and maybe some more infos on the mailling list. Thats of course
not the most straight forward location for the information.

If you searched together the information it would be great if you could send a
patch updating the manual with it. :)

regards
Stefan Schmidt



^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2010-12-01 18:06 ` Documentation Stefan Schmidt
@ 2010-12-01 18:39   ` David Lambert
  2010-12-01 18:54     ` Documentation Stefan Schmidt
  0 siblings, 1 reply; 62+ messages in thread
From: David Lambert @ 2010-12-01 18:39 UTC (permalink / raw)
  To: openembedded-devel

That is indeed the version of documentation that I was reading. To be 
more specific, one of the subjects I was attempting to look up was how 
to specialize a recipe using "amend.inc". I do not see any documentation 
on this subject.

Regards,

Dave.


On 12/01/2010 12:06 PM, Stefan Schmidt wrote:
> Hello.
>
> On Wed, 2010-12-01 at 12:00, David Lambert wrote:
>> I have been reading a copy of the OpenEmbedded User Manual (latest
>> copyright 2009). In this document I find that there are numerous
>> sections which are stubs and/or are incomplete. As a newcomer to the
>> world of OpenEmbedded what other documents are suggested for
>> reading? Also, is there a later version of this manual?
> My glassball is in repair so I can't see what manual you have and if a newer one
> is available. Adding some kind of date string would help us here.
>
> The user manual is build directly from the sources and should be always up to
> date here:
> http://docs.openembedded.org/usermanual/usermanual.html
>
> regards
> Stefan Schmidt
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2010-12-01 18:00 Documentation David Lambert
@ 2010-12-01 18:06 ` Stefan Schmidt
  2010-12-01 18:39   ` Documentation David Lambert
  0 siblings, 1 reply; 62+ messages in thread
From: Stefan Schmidt @ 2010-12-01 18:06 UTC (permalink / raw)
  To: openembedded-devel

Hello.

On Wed, 2010-12-01 at 12:00, David Lambert wrote:
> I have been reading a copy of the OpenEmbedded User Manual (latest
> copyright 2009). In this document I find that there are numerous
> sections which are stubs and/or are incomplete. As a newcomer to the
> world of OpenEmbedded what other documents are suggested for
> reading? Also, is there a later version of this manual?

My glassball is in repair so I can't see what manual you have and if a newer one
is available. Adding some kind of date string would help us here.

The user manual is build directly from the sources and should be always up to
date here:
http://docs.openembedded.org/usermanual/usermanual.html

regards
Stefan Schmidt



^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2010-12-01 18:00 David Lambert
  2010-12-01 18:06 ` Documentation Stefan Schmidt
  0 siblings, 1 reply; 62+ messages in thread
From: David Lambert @ 2010-12-01 18:00 UTC (permalink / raw)
  To: openembedded-devel

I have been reading a copy of the OpenEmbedded User Manual (latest 
copyright 2009). In this document I find that there are numerous 
sections which are stubs and/or are incomplete. As a newcomer to the 
world of OpenEmbedded what other documents are suggested for reading? 
Also, is there a later version of this manual?

Best regards,

Dave.




^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2010-03-14  0:17 Giuseppe Macrì
  0 siblings, 0 replies; 62+ messages in thread
From: Giuseppe Macrì @ 2010-03-14  0:17 UTC (permalink / raw)
  To: netfilter-devel

Hi,
is there some developing documentation about netfilter?

Giuseppe

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2006-02-10  8:20 Nico -telmich- Schottelius
  0 siblings, 0 replies; 62+ messages in thread
From: Nico -telmich- Schottelius @ 2006-02-10  8:20 UTC (permalink / raw)
  To: git

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

Hello!

I wrote some documentation about (using) git in German. For those
interested:

   http://nico.schotteli.us/papers/linux/howto/index.html (small introduction)
   http://creme.schottelius.org/~nico/linux/arbeiten_mit_git (very short
   'how to work with git')

Sincerly,

Nico

-- 
Latest release: ccollect-0.3.2 (http://linux.schottelius.org/ccollect/)
Open Source nutures open minds and free, creative developers.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-04 14:05       ` Documentation John S Little
  2005-12-05 16:46         ` Documentation Nivedita Singhvi
@ 2005-12-05 23:57         ` Rich Persaud
  1 sibling, 0 replies; 62+ messages in thread
From: Rich Persaud @ 2005-12-05 23:57 UTC (permalink / raw)
  To: John S Little; +Cc: Robb Romans, xen-devel, Robin van Leeuwen

John S Little wrote:

>Robin,
>
>The only current documentation that I've found for 3.0 is located at 
>http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html.  I 
>haven't read all of it but it mostly seems to be a copy of the 2.0 
>documentation  Other than that is the link that Robb pointed out below 
>regarding the outline proposal.
>  
>
Docs linked from above page have been updated today, for Xen 3.0.0.

Rich

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-05 16:46         ` Documentation Nivedita Singhvi
  2005-12-05 17:11           ` Documentation Robb Romans
@ 2005-12-05 18:09           ` John S Little
  1 sibling, 0 replies; 62+ messages in thread
From: John S Little @ 2005-12-05 18:09 UTC (permalink / raw)
  To: Nivedita Singhvi; +Cc: Robb Romans, xen-devel, Robin van Leeuwen

Hi Nivedita,

Ok I'll get that done today or tomorrow.

Nivedita Singhvi <niv@us.ibm.com> wrote on 12/05/2005 11:46:13 AM:

> John S Little wrote:
> 
> > Robin,
> > 
> > The only current documentation that I've found for 3.0 is located at 
> > http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html.  I 
> > haven't read all of it but it mostly seems to be a copy of the 2.0 
> > documentation  Other than that is the link that Robb pointed out below 

> > regarding the outline proposal.
> 
> Hello John,
> 
> Thanks for volunteering to help! Much appreciated...
> 
> If you're working with the 3.0 release and the unstable
> tree, you'll find that a lot of updates got merged by Alan
> and the Xensource team over the weekend.
> 
> Some more stuff will be merged in the next 2 days.
> 
> Download the current mercurial tip and look at the
> source. If you go to the docs/src tree, you will see
> the latex source. Doing a make install in the docs
> tree will generate the pdf, html, etc versions.
> 
> I'll update the wiki at some point today (I've been
> tardy at keeping that up to date, my apologies).
> 
> It will be a little more clear shortly what we need
> to enhance and remaining stuff to do.
> 
> thanks,


Regards,

John Little
Hendricks Regional Health IS Department
317-718-4752
jslittl@hendricks.org
http://www.hendrickshospital.org

> Nivedita
> 
> 

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-05 16:46         ` Documentation Nivedita Singhvi
@ 2005-12-05 17:11           ` Robb Romans
  2005-12-05 18:09           ` Documentation John S Little
  1 sibling, 0 replies; 62+ messages in thread
From: Robb Romans @ 2005-12-05 17:11 UTC (permalink / raw)
  To: xen-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "NS" == Nivedita Singhvi <niv@us.ibm.com> writes:

    > John S Little wrote:
    >> Robin, The only current documentation that I've found for 3.0 is
    >> located at
    >> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html.
    >> I haven't read all of it but it mostly seems to be a copy of the
    >> 2.0 documentation Other than that is the link that Robb pointed
    >> out below regarding the outline proposal.

    NS> Hello John,

    NS> Thanks for volunteering to help! Much appreciated...

    NS> If you're working with the 3.0 release and the unstable tree,
    NS> you'll find that a lot of updates got merged by Alan and the
    NS> Xensource team over the weekend.

Big kudos to Alan, Karsten, and crew for the doc updates.

    NS> Some more stuff will be merged in the next 2 days.

    NS> Download the current mercurial tip and look at the source. If
    NS> you go to the docs/src tree, you will see the latex
    NS> source. Doing a make install in the docs tree will generate the
    NS> pdf, html, etc versions.

I'd recommend doing a `make all` in the docs/ subdirectory.  "make ps"
and "make pdf" are available if you don't want everything.

<snip>

Regards,
Robb


- -- 
Robb Romans                     (512) 838-0419
Linux Commando                  T/L   678-0419
ARS NA5TT
.-- - ..-. ..--..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDlHS7doW/RCLrCx0RAmdzAJkB8IpAjK+tALMTkr7ZJGQjwb7rZQCgs+Dm
scCao8KqA1TOQF4GY+DuQLg=
=K9/j
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-04 14:05       ` Documentation John S Little
@ 2005-12-05 16:46         ` Nivedita Singhvi
  2005-12-05 17:11           ` Documentation Robb Romans
  2005-12-05 18:09           ` Documentation John S Little
  2005-12-05 23:57         ` Documentation Rich Persaud
  1 sibling, 2 replies; 62+ messages in thread
From: Nivedita Singhvi @ 2005-12-05 16:46 UTC (permalink / raw)
  To: John S Little; +Cc: Robb Romans, xen-devel, Robin van Leeuwen

John S Little wrote:

> Robin,
> 
> The only current documentation that I've found for 3.0 is located at 
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html.  I 
> haven't read all of it but it mostly seems to be a copy of the 2.0 
> documentation  Other than that is the link that Robb pointed out below 
> regarding the outline proposal.

Hello John,

Thanks for volunteering to help! Much appreciated...

If you're working with the 3.0 release and the unstable
tree, you'll find that a lot of updates got merged by Alan
and the Xensource team over the weekend.

Some more stuff will be merged in the next 2 days.

Download the current mercurial tip and look at the
source. If you go to the docs/src tree, you will see
the latex source. Doing a make install in the docs
tree will generate the pdf, html, etc versions.

I'll update the wiki at some point today (I've been
tardy at keeping that up to date, my apologies).

It will be a little more clear shortly what we need
to enhance and remaining stuff to do.

thanks,
Nivedita

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-03 11:26     ` Documentation Robin van Leeuwen
  2005-12-04 14:05       ` Documentation John S Little
@ 2005-12-05 15:58       ` Robb Romans
  1 sibling, 0 replies; 62+ messages in thread
From: Robb Romans @ 2005-12-05 15:58 UTC (permalink / raw)
  To: Robin van Leeuwen; +Cc: John S Little, xen-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "RvL" == Robin van Leeuwen <rvl@rldsoftware.nl> writes:

    RvL> Where can i see/download the documentation for 3.0 if i want to
    RvL> contribute something?

You will have to download the source code and build the documentation.

See:
<http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html>


Regards,
Robb


- -- 
Robb Romans                     (512) 838-0419
Linux Commando                  T/L   678-0419
ARS NA5TT
.-- - ..-. ..--..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDlGO/doW/RCLrCx0RAoj4AJ9PLfNZnA+LsQpiF3UZNXeTnKzZYgCfQMds
yXsp+eAMIVSdpt6iLbd4j6w=
=mhh9
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-03 11:26     ` Documentation Robin van Leeuwen
@ 2005-12-04 14:05       ` John S Little
  2005-12-05 16:46         ` Documentation Nivedita Singhvi
  2005-12-05 23:57         ` Documentation Rich Persaud
  2005-12-05 15:58       ` Documentation Robb Romans
  1 sibling, 2 replies; 62+ messages in thread
From: John S Little @ 2005-12-04 14:05 UTC (permalink / raw)
  To: Robin van Leeuwen; +Cc: Robb Romans, xen-devel

Robin,

The only current documentation that I've found for 3.0 is located at 
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html.  I 
haven't read all of it but it mostly seems to be a copy of the 2.0 
documentation  Other than that is the link that Robb pointed out below 
regarding the outline proposal.

Robin van Leeuwen <rvl@rldsoftware.nl> wrote on 12/03/2005 06:26:42 AM:

> Robb Romans schreef:
> 
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >    JSL> Hi all, I am wondering who is in charge of the documentation.
> >    JSL> I would like to help with it if that's possible.  I could also
> >    JSL> help with some limited testing with whatever resources we have
> >    JSL> available here at the hospital.
> >
> >The Xen maintainers determine what goes into the official 
documentation.
> >
> >The 3.0 docs are undergoing heavy change, and are not yet usable.
> >There's a suggested outline for the Xen 3.0 Users' Manual posted at:
> ><http://wiki.xensource.com/xenwiki/Xen3DocsToDo>.
> >
> >Feel free to contribute to any section.
> >
> >As to testing, if you find that following the procedures set forth in
> >the Users' Manual does not work for you, or if you find suggestions to
> >improve the document, please speak up.
> > 
> >
> 
> Where can i see/download the documentation for 3.0 if i want to
> contribute something?
> 
> kind regards,
> 
> Robin
Regards,

John Little
Hendricks Regional Health IS Department
317-718-4752
jslittl@hendricks.org
http://www.hendrickshospital.org

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-02 22:30   ` Documentation Robb Romans
@ 2005-12-03 11:26     ` Robin van Leeuwen
  2005-12-04 14:05       ` Documentation John S Little
  2005-12-05 15:58       ` Documentation Robb Romans
  0 siblings, 2 replies; 62+ messages in thread
From: Robin van Leeuwen @ 2005-12-03 11:26 UTC (permalink / raw)
  To: Robb Romans; +Cc: John S Little, xen-devel

Robb Romans schreef:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>    JSL> Hi all, I am wondering who is in charge of the documentation.
>    JSL> I would like to help with it if that's possible.  I could also
>    JSL> help with some limited testing with whatever resources we have
>    JSL> available here at the hospital.
>
>The Xen maintainers determine what goes into the official documentation.
>
>The 3.0 docs are undergoing heavy change, and are not yet usable.
>There's a suggested outline for the Xen 3.0 Users' Manual posted at:
><http://wiki.xensource.com/xenwiki/Xen3DocsToDo>.
>
>Feel free to contribute to any section.
>
>As to testing, if you find that following the procedures set forth in
>the Users' Manual does not work for you, or if you find suggestions to
>improve the document, please speak up.
>  
>

Where can i see/download the documentation for 3.0 if i want to
contribute something?

kind regards,

Robin

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2005-12-02 21:22 ` Documentation John S Little
@ 2005-12-02 22:30   ` Robb Romans
  2005-12-03 11:26     ` Documentation Robin van Leeuwen
  0 siblings, 1 reply; 62+ messages in thread
From: Robb Romans @ 2005-12-02 22:30 UTC (permalink / raw)
  To: John S Little; +Cc: xen-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "JSL" == John S Little <JSLittl@Hendricks.org> writes:

    JSL> Hi all, I am wondering who is in charge of the documentation.
    JSL> I would like to help with it if that's possible.  I could also
    JSL> help with some limited testing with whatever resources we have
    JSL> available here at the hospital.

The Xen maintainers determine what goes into the official documentation.

The 3.0 docs are undergoing heavy change, and are not yet usable.
There's a suggested outline for the Xen 3.0 Users' Manual posted at:
<http://wiki.xensource.com/xenwiki/Xen3DocsToDo>.

Feel free to contribute to any section.

As to testing, if you find that following the procedures set forth in
the Users' Manual does not work for you, or if you find suggestions to
improve the document, please speak up.

Regards,
Robb

- -- 
Robb Romans                     (512) 838-0419
Linux Commando                  T/L   678-0419
ARS NA5TT
.-- - ..-. ..--..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDkMshdoW/RCLrCx0RAgHvAJ9siAYy1C4snuj57g0lOrKm3qxEfwCfT+bk
tdHOh/y/H//ISAIi/Hypq4U=
=++KC
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
       [not found] <E1EiHi4-0000IY-16@host-192-168-0-1-bcn-london>
@ 2005-12-02 21:22 ` John S Little
  2005-12-02 22:30   ` Documentation Robb Romans
  0 siblings, 1 reply; 62+ messages in thread
From: John S Little @ 2005-12-02 21:22 UTC (permalink / raw)
  To: xen-devel

Hi all,

I am wondering who is in charge of the documentation.  I would like to 
help with it if that's possible.  I could also help with some limited 
testing with whatever resources we have available here at the hospital.

Please let me know.

Thanks!

Regards,

John Little
Hendricks Regional Health IS Department
317-718-4752
jslittl@hendricks.org
http://www.hendrickshospital.org

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2005-10-24 19:05 Vagin Andrey S.
  0 siblings, 0 replies; 62+ messages in thread
From: Vagin Andrey S. @ 2005-10-24 19:05 UTC (permalink / raw)
  To: linux-scsi



I develop scsi disk driver.
Where can I find documentation?
How can I create driver with sector_size any 512 byte?

When I must declare, that sector_size equals 1024 for example?

p s Scsi disk isnt't phisical device, is virual, similar to iSCSI.


kernel: 2.4.27


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation.
  2004-06-25 13:17   ` Documentation Jeroen Dekkers
@ 2004-06-26 15:05     ` Yoshinori K. Okuji
  0 siblings, 0 replies; 62+ messages in thread
From: Yoshinori K. Okuji @ 2004-06-26 15:05 UTC (permalink / raw)
  To: The development of GRUB 2

On Friday 25 June 2004 15:17, Jeroen Dekkers wrote:
> The best way to document the internals is in the code, so that when
> the code changes the comments change with it. To describe the
> interfaces you can write verbose header files for example.

You are right, if you talk about the API. But I don't think Tomas meant 
the API but the design or something similar. For example, "how to add a 
new command" is a bit difficult to document in header files, because 
the information would be scattered.

Okuji



^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation.
  2004-06-24 22:03 ` Documentation Yoshinori K. Okuji
@ 2004-06-25 13:17   ` Jeroen Dekkers
  2004-06-26 15:05     ` Documentation Yoshinori K. Okuji
  0 siblings, 1 reply; 62+ messages in thread
From: Jeroen Dekkers @ 2004-06-25 13:17 UTC (permalink / raw)
  To: The development of GRUB 2

At Fri, 25 Jun 2004 00:03:53 +0200,
Yoshinori K. Okuji wrote:
> Regardless of whatever tool you use, the most important thing in 
> documentation is "not to make it out of dated". This is really 
> difficult. Indeed, I gave up keeping information on internals of GRUB 
> Legacy in the manual. Maintaining good documentation costs the same as 
> maintaining good code. So, I'd recommend that you keep your 
> documentation as simple as you can.

The best way to document the internals is in the code, so that when
the code changes the comments change with it. To describe the
interfaces you can write verbose header files for example.

Jeroen Dekkers



^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation.
  2004-06-24 17:10 Documentation Tomas Ebenlendr
@ 2004-06-24 22:03 ` Yoshinori K. Okuji
  2004-06-25 13:17   ` Documentation Jeroen Dekkers
  0 siblings, 1 reply; 62+ messages in thread
From: Yoshinori K. Okuji @ 2004-06-24 22:03 UTC (permalink / raw)
  To: The development of GRUB 2

On Thursday 24 June 2004 19:10, Tomas Ebenlendr wrote:
> So here is the question: what format? (and what names?).

Use plain text. It's good enough for this purpose. If you need a more 
complex one, use texinfo. Texinfo is the standard documentation tool 
for GNU, and many GNU programmers are used to it.

Regardless of whatever tool you use, the most important thing in 
documentation is "not to make it out of dated". This is really 
difficult. Indeed, I gave up keeping information on internals of GRUB 
Legacy in the manual. Maintaining good documentation costs the same as 
maintaining good code. So, I'd recommend that you keep your 
documentation as simple as you can.

Okuji



^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation.
@ 2004-06-24 17:10 Tomas Ebenlendr
  2004-06-24 22:03 ` Documentation Yoshinori K. Okuji
  0 siblings, 1 reply; 62+ messages in thread
From: Tomas Ebenlendr @ 2004-06-24 17:10 UTC (permalink / raw)
  To: The development of GRUB 2


I think that there is terribly missing a documentation of grub
internals. I want to write documentation at least for parts which I'm
patching. Otherwise everyone who wants to hack for grub:
    a) slowly figures out how things are workinkg.
    b) hacks in way which _he_ supposes to be consistent with other
    parts.
This can be fixed by documentation. Programmer then can read apropriate
part of documentation and learn how things are _intended_ to be.

So here is the question: what format? (and what names?).

I'm used on doxygen, but I think it is piece of crap (because text
processing shouln't be written in C).

It can be plain text (it is only for programmer's), but there should be
written how grub works (and is intended to work), so programmer can
easily figure out what he wants to patch.


-- 
                                 Tomas 'ebi' Ebenlendr
                                 http://get.to/ebik
                                 PF 2004.48028928861




^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2004-05-27 13:12 Documentation Alexander E. Patrakov
  2004-05-28 23:25 ` Documentation Greg KH
@ 2004-06-02  6:11 ` Niko Sauer
  1 sibling, 0 replies; 62+ messages in thread
From: Niko Sauer @ 2004-06-02  6:11 UTC (permalink / raw)
  To: linux-hotplug

On Thu, 27 May 2004, Alexander E. Patrakov wrote:

> Date: Thu, 27 May 2004 19:12:23 +0600
> From: Alexander E. Patrakov <patrakov@ums.usu.ru>
> To: linux-hotplug-devel@lists.sourceforge.net
> Subject: Documentation
> 
> In the Linux From Scratch (LFS) support mailing list a question has been 
> asked: why can't hotplug load the "snd-pcm-oss" module automatically 
> despite the fact that the Creative Live! soundcard is found and the 
> "snd-emu10k1" module is loaded automatically for it. I answered this 
> question, but another point has been raised there that should be really 
> discussed here.
> 
> Namely, the problem is that the recommendations on building Linux kernel 
> and writing /etc/modules.conf (or modprobe.conf) file that predate 
> adoption of Hotplug are now wrong, invalid and even harmful. Since 
> Hotplug and Udev will be probably included in the next version of LFS, 
> and even experienced developers cannot build a trouble-free kernel for 
> use with Hotplug and Udev on their first attempt, we expect a sharp 
> increase of support questions per day in our list.
> 
> I could not find any up-to-date "good practice" documents upon building 
> the kernel that work well with Hotplug and Udev. E.g., it is mentioned 
> nowhere that if a character or block device driver is built as a module, 
> then it will not be loaded automatically. Yes, that is in the Udev FAQ, 
> but in the wrong form: you state that it is not the task of Udev to load 
> modules (it is a negative statement), and I need an URL with some 
> positive recommendations how to load modules and to avoid various 
> chicken-and-egg problems. The snd-pcm-oss problem is also documented 
> nowhere. (is there any comprehensive list of such undetectable modules?)
> 
> Could you please post link here to some good (possibly even "official") 
> up-to-date and newbie-proof list of good kernel building practices? The 
> discussion of modprobe.conf will be also very nice. I will be glad to 
> put that link into the LFS book, thus avoiding repeated support questions.
> 
> If such document is not written yet, we should collaborate and write it.
> 
> 
Dear Alexander

I do not have what you are looking for, but some notes I have made on use
of udev for hotplugging flash memory devices and cd writing. In Linux-2.6
the kernel configuration for achieving these things are much simpler than
for the 2.4 kernel. CD writing with the new kernel is so simple that the
existing HOWTO (also included in Beyond LFS) is hopelessly outdated. Would
you be able to use these notes, and would someone else in the LFS team be
interested?

Kind regards

Niko Sauer
______________________
Unit of Advanced Study
University of Pretoria
Pretoria 0002
South Africa

Tel: [27][12] 420 3558
Fax: [27][12] 420 3904



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2004-05-27 13:12 Documentation Alexander E. Patrakov
@ 2004-05-28 23:25 ` Greg KH
  2004-06-02  6:11 ` Documentation Niko Sauer
  1 sibling, 0 replies; 62+ messages in thread
From: Greg KH @ 2004-05-28 23:25 UTC (permalink / raw)
  To: linux-hotplug

On Thu, May 27, 2004 at 07:12:23PM +0600, Alexander E. Patrakov wrote:
> 
> Could you please post link here to some good (possibly even "official") 
> up-to-date and newbie-proof list of good kernel building practices? The 
> discussion of modprobe.conf will be also very nice. I will be glad to 
> put that link into the LFS book, thus avoiding repeated support questions.
> 
> If such document is not written yet, we should collaborate and write it.

I do not know of such a document yet, sorry.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2004-05-27 13:12 Alexander E. Patrakov
  2004-05-28 23:25 ` Documentation Greg KH
  2004-06-02  6:11 ` Documentation Niko Sauer
  0 siblings, 2 replies; 62+ messages in thread
From: Alexander E. Patrakov @ 2004-05-27 13:12 UTC (permalink / raw)
  To: linux-hotplug

In the Linux From Scratch (LFS) support mailing list a question has been 
asked: why can't hotplug load the "snd-pcm-oss" module automatically 
despite the fact that the Creative Live! soundcard is found and the 
"snd-emu10k1" module is loaded automatically for it. I answered this 
question, but another point has been raised there that should be really 
discussed here.

Namely, the problem is that the recommendations on building Linux kernel 
and writing /etc/modules.conf (or modprobe.conf) file that predate 
adoption of Hotplug are now wrong, invalid and even harmful. Since 
Hotplug and Udev will be probably included in the next version of LFS, 
and even experienced developers cannot build a trouble-free kernel for 
use with Hotplug and Udev on their first attempt, we expect a sharp 
increase of support questions per day in our list.

I could not find any up-to-date "good practice" documents upon building 
the kernel that work well with Hotplug and Udev. E.g., it is mentioned 
nowhere that if a character or block device driver is built as a module, 
then it will not be loaded automatically. Yes, that is in the Udev FAQ, 
but in the wrong form: you state that it is not the task of Udev to load 
modules (it is a negative statement), and I need an URL with some 
positive recommendations how to load modules and to avoid various 
chicken-and-egg problems. The snd-pcm-oss problem is also documented 
nowhere. (is there any comprehensive list of such undetectable modules?)

Could you please post link here to some good (possibly even "official") 
up-to-date and newbie-proof list of good kernel building practices? The 
discussion of modprobe.conf will be also very nice. I will be glad to 
put that link into the LFS book, thus avoiding repeated support questions.

If such document is not written yet, we should collaborate and write it.

-- 
Alexander E. Patrakov


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2004-05-15 14:28 Documentation Jody
  2004-05-17 13:35 ` Documentation Andrey Romanenko
@ 2004-05-17 13:40 ` Miguel Bolanos
  1 sibling, 0 replies; 62+ messages in thread
From: Miguel Bolanos @ 2004-05-17 13:40 UTC (permalink / raw)
  To: Jody; +Cc: Linux-8086

Good Day Jody!

On Sat, 2004-05-15 at 08:28, Jody wrote:
> I feel that with the recent activity concerning ELKS, I should extend my
> offer to make up any kind of documentation that I can for the project,
> since this is the weakest link in most projects.  I am NOT a programmer,
> and I am not an expert at compiling and porting.  I can document anything
> that anyone can help me reproduce at my house that needs to have
> documentation for the ELKS project to see more activity.  If anyone has any
> ideas what I can go about documenting, please email me back or look for
> "nsx" in the #elks IRC channel.
> 

Thanks a lot for your offer.. actually as part of the new plan for
elks.. we will need to not only improve the current documentation, but
also write docs for the new kernel work plus gcc-8086 stuff.
Something that u have to be aware is that the community is not only
powered by Skilled coders, but also by people with a lot of will to help
on anything that they can as it is Doc writing.. so indeed, please
follow the work, and feel free to ask questions whether it is here or on
the list.

best wishes.

Mike

> Jody
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2004-05-15 14:28 Documentation Jody
@ 2004-05-17 13:35 ` Andrey Romanenko
  2004-05-17 13:40 ` Documentation Miguel Bolanos
  1 sibling, 0 replies; 62+ messages in thread
From: Andrey Romanenko @ 2004-05-17 13:35 UTC (permalink / raw)
  To: Jody; +Cc: Linux-8086

Hi everybody,

Jody wrote:

>If anyone has any
>ideas what I can go about documenting, please email me back or look for
>"nsx" in the #elks IRC channel.
>  
>
I think there is NO decent documentation about elks kernel. What I would 
like to see is:
1. Kernel architecture: (supported CPU modes; memory modes for 8086 and 
286 for kernel and for processes; processes scheduling and interrupt 
handling; memory managment and swap support; system invocation 
mechanism; processes synchronization mechanisms; other kernel issues);
2. Available and expected to be done API and libraries;
3. Porting issues (tools,guides,how-tos);

this documents will help us to involve more peoples to project, cause 
many guys even won't bother to spend couple weeks exploring source code 
to find out all those mentioned issues.

thanks,

Andrey


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2004-05-15 14:28 Jody
  2004-05-17 13:35 ` Documentation Andrey Romanenko
  2004-05-17 13:40 ` Documentation Miguel Bolanos
  0 siblings, 2 replies; 62+ messages in thread
From: Jody @ 2004-05-15 14:28 UTC (permalink / raw)
  To: Linux-8086

I feel that with the recent activity concerning ELKS, I should extend my
offer to make up any kind of documentation that I can for the project,
since this is the weakest link in most projects.  I am NOT a programmer,
and I am not an expert at compiling and porting.  I can document anything
that anyone can help me reproduce at my house that needs to have
documentation for the ELKS project to see more activity.  If anyone has any
ideas what I can go about documenting, please email me back or look for
"nsx" in the #elks IRC channel.

Jody


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
       [not found] ` <FED3CB2D-57B5-11D8-BC94-00039350B9F2@epiuse.com>
  2004-02-05 10:15   ` Documentation Bin Ren
@ 2004-02-05 11:49   ` Yan-Ching CHU
  1 sibling, 0 replies; 62+ messages in thread
From: Yan-Ching CHU @ 2004-02-05 11:49 UTC (permalink / raw)
  To: Jan van Rensburg, Xen List; +Cc: cs0u210a, Ian Pratt, Bin Ren

Hi Jan,

Thanks for your initiative effort in documentation.

> Bin if you can bring your HOWTO up to date for 1.2 I will merge that 
> with Yan-Ching's and check in into Sourceforge with the FAQ as Ian 
> suggested. Ian, does Sourceforge's CVS check it into the main Xen tree 
> or do you propose a separate tree for the documentation?

I will try to bring my Howto 1.2-compatiable once it's ISO is released,
then Ian may want to check that in into the 1.2 and unstable tree.

> As far the the documentation structure is concerned I think there 
> should be 3 main areas: Overview, Developer and End User. I'll leave 
> the Developer part to someone else. The overview should contain at 
> least one doc describing in "layman" terms how xen works, what xen, 
> xeno linux, VM, domains etc are. A kind of a starting point. I can 
> write a first draft of this (if someone hasn't already done it. The 
> SOSP paper is a bit too much). The End User docs should contain the FAQ 
> and the merged HOWTO for now.

I will also keep in touch with you about the developer section because I am
going to modify the scheduler with more features. Throughout the process I 
should write down my experience and comments systemtically.

Cheers,
Yan-Ching CHU




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
       [not found] ` <FED3CB2D-57B5-11D8-BC94-00039350B9F2@epiuse.com>
@ 2004-02-05 10:15   ` Bin Ren
  2004-02-05 11:49   ` Documentation Yan-Ching CHU
  1 sibling, 0 replies; 62+ messages in thread
From: Bin Ren @ 2004-02-05 10:15 UTC (permalink / raw)
  To: Jan van Rensburg; +Cc: Devel Xen

Hi,

Mark Williams has updated my HOWTO for 1.2 and it's
already available in xeno-unstable.bk, under 'docs/'

-- Bin

On 5 Feb 2004, at 08:33, Jan van Rensburg wrote:

> Hi,
>
> Bin if you can bring your HOWTO up to date for 1.2 I will merge that 
> with Yan-Ching's and check in into Sourceforge with the FAQ as Ian 
> suggested. Ian, does Sourceforge's CVS check it into the main Xen tree 
> or do you propose a separate tree for the documentation?



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2003-06-06 13:20 Matthew Wilcox
  0 siblings, 0 replies; 62+ messages in thread
From: Matthew Wilcox @ 2003-06-06 13:20 UTC (permalink / raw)
  To: linux-scsi


Kconfig's in pretty good shape now from a structural point of view,
so I thought I'd review some of the actual help text.

Many entries refer to the ancient SCSI-HOWTO.  It doesn't
seemto be on tldp.org anywhere, but I found it at
http://www.ibiblio.org/pub/Linux/docs/HOWTO/unmaintained/SCSI-HOWTO

Do we want to correct the URL from http://www.tldp.org/docs.html#howto
to the one above or excise all references to it?

The Disk-HOWTO, Multi-Disk-HOWTO, and CD-ROM-HOWTO are also referenced.
The Disk-HOWTO has also disappeared.  The Multi-Disk-HOWTO doesn't really
seem relevant at this point.  Though the CD-ROM-HOWTO is listed as the
CDROM-HOWTO, it still seems relevant.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2002-08-29  9:39 documentation vandana  mehtani
@ 2002-08-29 15:46 ` Dave Wilhardt
  0 siblings, 0 replies; 62+ messages in thread
From: Dave Wilhardt @ 2002-08-29 15:46 UTC (permalink / raw)
  To: vandana mehtani; +Cc: linuxppc-embedded


Try this:

http://e-www.motorola.com/webapp/sps/site/taxonomy.jsp?nodeId=01M0ylsbTdG

vandana mehtani wrote:

> Hello everybody,
> I am trying to study the code for head8xx.h.
> but the documentation to understand the powerpc assembly is
> somehow inadequate,
> I have the powerpc programming environment.
> but it seems that there is a need to understand the "as" specific
> assembler ..
> Where can i get the documentation.
> The information is very scattered.
>
> thanks in advance
> regards
> vandana
>

--
Dave Wilhardt
Synergy Microsystems
9605 Scranton Road, Suite 700
San Diego, CA 92121
858 452-0020 x164


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 62+ messages in thread

* documentation
@ 2002-08-29  9:39 vandana  mehtani
  2002-08-29 15:46 ` documentation Dave Wilhardt
  0 siblings, 1 reply; 62+ messages in thread
From: vandana  mehtani @ 2002-08-29  9:39 UTC (permalink / raw)
  To: linuxppc-embedded


Hello everybody,
I am trying to study the code for head8xx.h.
but the documentation to understand the powerpc assembly is
somehow inadequate,
I have the powerpc programming environment.
but it seems that there is a need to understand the "as" specific
assembler ..
Where can i get the documentation.
The information is very scattered.

thanks in advance
regards
vandana


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2002-05-03 16:11       ` documentation Guilhem Tardy
  2002-05-03 16:22         ` documentation Paul Davis
@ 2002-05-03 16:28         ` Takashi Iwai
  1 sibling, 0 replies; 62+ messages in thread
From: Takashi Iwai @ 2002-05-03 16:28 UTC (permalink / raw)
  To: Guilhem Tardy; +Cc: alsa-devel

Hi,

At Fri, 3 May 2002 09:11:33 -0700 (PDT),
Guilhem Tardy wrote:
> 
> Hi,
> 
> Now, I have this new driver which manages to open/close a pcm
> channel whenever one attempts to play a file with "play test.au",
> but complains (Sound protocol it not compatible) with "aplay
> test.au". Any idea what's wrong? 

this error happens usually when an older version of alsa-lib /
alsa-utils are installed.  please check the version of alsa-lib.
(must be linked to libasound.so.2)


> Besides, I have no mixer defined (I would just to allow open/close a
> playback or capture channel, no more) and wonder if it is a problem?

no.  you can initialize the mixer part even in open of pcm callbacks,
if it's not necessarily configurable.


> I am just loading the driver manually for now (insmod snd,
> snd-timer, snd-pcm,  ...), is there any special configuration I
> need? How to tell the driver to  unmute?

generally modprobe resolves the dependency, i.e. just load the
top-level module like

	# modprobe snd-yourdriver

then all low-level drivers will be loaded.

well, unmute...?  if there is no mixer, the device should be always
unmuted, or as mentioned above, toggle mute/unmute at open/close.

anyway, i would advise you to post your working code (or its URL) to
alsa-devel ML, so that other developers can take a look.


ciao,

Takashi

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2002-05-03 16:11       ` documentation Guilhem Tardy
@ 2002-05-03 16:22         ` Paul Davis
  2002-05-03 16:28         ` documentation Takashi Iwai
  1 sibling, 0 replies; 62+ messages in thread
From: Paul Davis @ 2002-05-03 16:22 UTC (permalink / raw)
  To: Guilhem Tardy; +Cc: alsa-devel, Takashi Iwai

>Hi,
>
>Now, I have this new driver which manages to open/close a pcm channel whenever
>one attempts to play a file with "play test.au", but complains (Sound protocol
>it not compatible) with "aplay test.au". Any idea what's wrong?
>Besides, I have no mixer defined (I would just to allow open/close a playback
>or capture channel, no more) and wonder if it is a problem?
>I am just loading the driver manually for now (insmod snd, snd-timer, snd-pcm,
>...), is there any special configuration I need? How to tell the driver to
>unmute?

sounds as if you have the wrong version of aplay installed (relative
to the version of alsa-lib and alsa-driver)

--p

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2002-04-26 17:54     ` documentation Takashi Iwai
@ 2002-05-03 16:11       ` Guilhem Tardy
  2002-05-03 16:22         ` documentation Paul Davis
  2002-05-03 16:28         ` documentation Takashi Iwai
  0 siblings, 2 replies; 62+ messages in thread
From: Guilhem Tardy @ 2002-05-03 16:11 UTC (permalink / raw)
  To: alsa-devel; +Cc: Takashi Iwai

Hi,

Now, I have this new driver which manages to open/close a pcm channel whenever
one attempts to play a file with "play test.au", but complains (Sound protocol
it not compatible) with "aplay test.au". Any idea what's wrong?
Besides, I have no mixer defined (I would just to allow open/close a playback
or capture channel, no more) and wonder if it is a problem?
I am just loading the driver manually for now (insmod snd, snd-timer, snd-pcm,
...), is there any special configuration I need? How to tell the driver to
unmute?

Thanks,
Guilhem.

> > > the copy and silence ops are called when write() is called (more
> > > exactly on alsa it's ioctl) - the thread writing to the device does
> > > actually work like DMA.  on mmap mode, there is no such one.  so you
> > > need an extra thread (or if it's not too heavy then tasklet might be
> > > available) anyway.

> no, i posted to alsa-devel ML, a month ago or so.
> the document you read is for the user library, not for the driver.

> in your case, you need to copy the data on the buffer to the hw by
> yourself.  then what is the merit of mmap? 
> (well, it would be a bit more efficient than copy_from_user(), but
>  the advantage of copy_from_user() is that you can use non-contiguous
>  buffer while alsa's mmap supports, so far, only contiguous region.)

> on alsa, when the program runs in the mmap mode, no read/write is
> called but the data is read/written on the mmapped buffer, and the
> also mmaped status is updated.  during the app writes data, DMA
> transfers the data from the mmaped buffer.
> that is, the thread is free from the kernel mode.


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2002-04-24 19:32   ` documentation Guilhem Tardy
@ 2002-04-26 17:54     ` Takashi Iwai
  2002-05-03 16:11       ` documentation Guilhem Tardy
  0 siblings, 1 reply; 62+ messages in thread
From: Takashi Iwai @ 2002-04-26 17:54 UTC (permalink / raw)
  To: Guilhem Tardy; +Cc: alsa-devel

At Wed, 24 Apr 2002 12:32:26 -0700 (PDT),
Guilhem Tardy wrote:
> 
> > > What is required from my part to support memory mapping from the driver
> > > to the application? Would this be supported through the OSS compatibility
> > > layer, too?
> > 
> > hmm...  mmap without dma?
> > how do you transfer the data on buffer to hardware?
> 
> The card doesn't support DMA, yet. Data is transferred to/from the buffer by
> the driver copying 32-bit chunks. Those buffers were allocated by the MMAP,
                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> today through the V4Lv2 API (this is an audio+video card).
 
how do you mean here?
the allocated buffers are mmaped to user?

> > the copy and silence ops are called when write() is called (more
> > exactly on alsa it's ioctl) - the thread writing to the device does
> > actually work like DMA.  on mmap mode, there is no such one.  so you
> > need an extra thread (or if it's not too heavy then tasklet might be
> > available) anyway.
> 
> Having checked the brief documentation you referred to
> (http://www.alsa-project.org/alsa-doc/alsa-lib/), I guess using the direct

no, i posted to alsa-devel ML, a month ago or so.
the document you read is for the user library, not for the driver.

> audio buffer to communicate with the device means DMA+MMAP. I would like to do
> the same thing, but have the driver actually copy data to/from the device. What
> do you call "mmap mode" above?

in your case, you need to copy the data on the buffer to the hw by
yourself.  then what is the merit of mmap? 
(well, it would be a bit more efficient than copy_from_user(), but
 the advantage of copy_from_user() is that you can use non-contiguous
 buffer while alsa's mmap supports, so far, only contiguous region.)

on alsa, when the program runs in the mmap mode, no read/write is
called but the data is read/written on the mmapped buffer, and the
also mmaped status is updated.  during the app writes data, DMA
transfers the data from the mmaped buffer.
that is, the thread is free from the kernel mode.


> Is there any other documentation more specific to driver development?

at least i am not aware of such documents.
check alsa-devel ML archive.


Takashi

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2002-04-24 16:58 ` documentation Takashi Iwai
@ 2002-04-24 19:32   ` Guilhem Tardy
  2002-04-26 17:54     ` documentation Takashi Iwai
  0 siblings, 1 reply; 62+ messages in thread
From: Guilhem Tardy @ 2002-04-24 19:32 UTC (permalink / raw)
  To: Takashi Iwai; +Cc: alsa-devel

> > What is required from my part to support memory mapping from the driver
> > to the application? Would this be supported through the OSS compatibility
> > layer, too?
> 
> hmm...  mmap without dma?
> how do you transfer the data on buffer to hardware?

The card doesn't support DMA, yet. Data is transferred to/from the buffer by
the driver copying 32-bit chunks. Those buffers were allocated by the MMAP,
today through the V4Lv2 API (this is an audio+video card).

> the copy and silence ops are called when write() is called (more
> exactly on alsa it's ioctl) - the thread writing to the device does
> actually work like DMA.  on mmap mode, there is no such one.  so you
> need an extra thread (or if it's not too heavy then tasklet might be
> available) anyway.

Having checked the brief documentation you referred to
(http://www.alsa-project.org/alsa-doc/alsa-lib/), I guess using the direct
audio buffer to communicate with the device means DMA+MMAP. I would like to do
the same thing, but have the driver actually copy data to/from the device. What
do you call "mmap mode" above?

Is there any other documentation more specific to driver development?

Guilhem.


__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: documentation
  2002-04-24 14:26 documentation Guilhem Tardy
@ 2002-04-24 16:58 ` Takashi Iwai
  2002-04-24 19:32   ` documentation Guilhem Tardy
  0 siblings, 1 reply; 62+ messages in thread
From: Takashi Iwai @ 2002-04-24 16:58 UTC (permalink / raw)
  To: Guilhem Tardy; +Cc: alsa-devel

At Wed, 24 Apr 2002 07:26:04 -0700 (PDT),
Guilhem Tardy wrote:
> 
> Hi,
> 
> I am writing an ALSA driver for a new card. I had doc for 0.5.0, but this is
> outdated and so far had to do with examples in the 0.9.0beta12 distribution
> (mainly dummy.c and cs4281.c). Is there any doc available otherwise?

no, unfortunately not yet.
i posted a very brief info recently on alsa-devel.
please check out the archive.


> Any hint as for what I am facing, given that my card doesn't do DMA.
 
then you have to define copy and silence ops additionally.
copy the data on user buffer to the destination in these ops.
you'll need to reschedule ocasionally to avoid too long code path.
an example is found in gus driver (gus_pcm.c).
you can also use need_resched() to check the rescheduling.


> What is required from my part to support memory mapping from the driver to the
> application? Would this be supported through the OSS compatibility layer, too?

hmm...  mmap without dma?
how do you transfer the data on buffer to hardware?

the copy and silence ops are called when write() is called (more
exactly on alsa it's ioctl) - the thread writing to the device does
actually work like DMA.  on mmap mode, there is no such one.  so you
need an extra thread (or if it's not too heavy then tasklet might be
available) anyway.


Takashi

^ permalink raw reply	[flat|nested] 62+ messages in thread

* documentation
@ 2002-04-24 14:26 Guilhem Tardy
  2002-04-24 16:58 ` documentation Takashi Iwai
  0 siblings, 1 reply; 62+ messages in thread
From: Guilhem Tardy @ 2002-04-24 14:26 UTC (permalink / raw)
  To: alsa-devel

Hi,

I am writing an ALSA driver for a new card. I had doc for 0.5.0, but this is
outdated and so far had to do with examples in the 0.9.0beta12 distribution
(mainly dummy.c and cs4281.c). Is there any doc available otherwise?
Any hint as for what I am facing, given that my card doesn't do DMA.

What is required from my part to support memory mapping from the driver to the
application? Would this be supported through the OSS compatibility layer, too?

Thanks,
Guilhem.


__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2002-03-22 15:32 Documentation Gopakumar.C.E
@ 2002-03-30  7:42 ` Ralf Baechle
  0 siblings, 0 replies; 62+ messages in thread
From: Ralf Baechle @ 2002-03-30  7:42 UTC (permalink / raw)
  To: Gopakumar.C.E; +Cc: linux-mips

On Fri, Mar 22, 2002 at 09:02:03PM +0530, Gopakumar.C.E wrote:

> Is there any good documentation on how the Linux/Unix code is designed for 
> the MIPS processors ? (like how they handle paging, protection etc?)

The whole VM code is largely generic code sprinkled with a few architecture
specific bits all over include/asm-mips and arch/mips.  The MIPS specific
bits primarily deal with very low level details of memory managment (TLB,
caches) which the actual paging stuff is in the mm/ directory.

I've not document the MIPS-specific parts of memory managment very well
(standard reason - so much work to do, so little time to do it ...) so
feel free to ask me.  The generic Linux memory managment is fairly well
documented in various online resources or a variety of technical books
from your favorite CS bookstore ...

  Ralf

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2002-03-22 15:32 Gopakumar.C.E
  2002-03-30  7:42 ` Documentation Ralf Baechle
  0 siblings, 1 reply; 62+ messages in thread
From: Gopakumar.C.E @ 2002-03-22 15:32 UTC (permalink / raw)
  To: linux-mips

Hi,

Is there any good documentation on how the Linux/Unix code is designed for 
the MIPS processors ? (like how they handle paging, protection etc?)

Thanks
Gopakumar.C.E

-- 

"Vidhya dadathi vinayam" - Education leads to humility (in sanskrit).

--------------------------------
http://www.geocities.com/gopakumar_ce/
http://wwwin-people.cisco.com/gopkumar/
--------------------------------

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2002-02-02 10:39 ` Documentation Yven J. Leist
@ 2002-02-05 18:18   ` Randy.Dunlap
  0 siblings, 0 replies; 62+ messages in thread
From: Randy.Dunlap @ 2002-02-05 18:18 UTC (permalink / raw)
  To: leist; +Cc: linux-kernel, Guillaume Chamberland-Larose

On Sat, 2 Feb 2002, Yven J. Leist wrote:

| On Saturday 02 February 2002 10:18, Guillaume Chamberland-Larose wrote:
| > Hi,
| >
| > I have some linux kernel programming experience from the 2.0 days and I'd
| > like to start programming it again, or at least understand the new
| > features. Is there any really up-to-date information on 2.5, what's changed
| > (build process, new VM, new this), what's new for developers eager to jump
| > into kernel programming again? :)
|
| http://www.kernelnewbies.org/status/status.html
| provides a nice overview of 2.5 changes.


also try http://www.osdl.org/archive/rddunlap/linux-port-25x.html

I need to add input API and frame buffer API changes to it...

-- 
~Randy


^ permalink raw reply	[flat|nested] 62+ messages in thread

* Re: Documentation
  2002-02-02  9:18 Documentation Guillaume Chamberland-Larose
@ 2002-02-02 10:39 ` Yven J. Leist
  2002-02-05 18:18   ` Documentation Randy.Dunlap
  0 siblings, 1 reply; 62+ messages in thread
From: Yven J. Leist @ 2002-02-02 10:39 UTC (permalink / raw)
  To: linux-kernel; +Cc: Guillaume Chamberland-Larose

On Saturday 02 February 2002 10:18, Guillaume Chamberland-Larose wrote:
> Hi,
>
> I have some linux kernel programming experience from the 2.0 days and I'd
> like to start programming it again, or at least understand the new
> features. Is there any really up-to-date information on 2.5, what's changed
> (build process, new VM, new this), what's new for developers eager to jump
> into kernel programming again? :)

http://www.kernelnewbies.org/status/status.html
provides a nice overview of 2.5 changes.
cheers,
Yven
-- 

Yven J. Leist - leist@beldesign.de
http://www.leist.beldesign.de

^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2002-02-02  9:18 Guillaume Chamberland-Larose
  2002-02-02 10:39 ` Documentation Yven J. Leist
  0 siblings, 1 reply; 62+ messages in thread
From: Guillaume Chamberland-Larose @ 2002-02-02  9:18 UTC (permalink / raw)
  To: linux-kernel

Hi,

I have some linux kernel programming experience from the 2.0 days and I'd 
like to start programming it again, or at least understand the new 
features. Is there any really up-to-date information on 2.5, what's changed 
(build process, new VM, new this), what's new for developers eager to jump 
into kernel programming again? :)

Thanks for your cooperation,
Please cc me as I'm not on the list.

Guills



^ permalink raw reply	[flat|nested] 62+ messages in thread

* Documentation
@ 2001-11-15 18:03 war
  0 siblings, 0 replies; 62+ messages in thread
From: war @ 2001-11-15 18:03 UTC (permalink / raw)
  To: linux-kernel

Are there any relatively new documents on how to optimize /proc system
variables?
Securing and Optimizing RedHat Linux had a few,
/usr/src/linux/Documentation has a few.
Are there any current papers/documents that encompass all of the
settings and options that you can set?

ie: for 1 GB of ram
echo "100 1200 128 512 15 5000 500 1884 2" > /proc/sys/vm/bdflush
Would be used.

However, this was taken from either a 2.2.x kernel or early 2.4.

Anyone know if any docs currently exist which explain how to tweak each
setting and what each setting means?




^ permalink raw reply	[flat|nested] 62+ messages in thread

end of thread, other threads:[~2020-06-10 12:55 UTC | newest]

Thread overview: 62+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-27  5:53 documentation Julia Lawall
2017-03-27  9:38 ` [Outreachy kernel] documentation Gargi Sharma
  -- strict thread matches above, loose matches on Subject: below --
2020-06-06 17:09 Documentation G.W. Haywood
2020-06-07 21:23 ` Documentation Pablo Neira Ayuso
2020-06-10 12:55   ` Documentation G.W. Haywood
2011-04-13 23:33 Documentation Eugene Shatsky
2011-04-14  4:44 ` Documentation Jonáš Vidra
2011-04-14 13:54 ` Documentation Edward Shishkin
2011-01-31 21:39 documentation Roberto Spadim
2011-01-31 21:43 ` documentation Mathias Burén
2011-01-31 21:58 ` documentation NeilBrown
2011-01-31 22:14   ` documentation Roberto Spadim
2011-02-01  9:37     ` documentation hansbkk
2011-02-01 13:49       ` documentation Roberto Spadim
2010-12-01 18:00 Documentation David Lambert
2010-12-01 18:06 ` Documentation Stefan Schmidt
2010-12-01 18:39   ` Documentation David Lambert
2010-12-01 18:54     ` Documentation Stefan Schmidt
2010-12-01 22:46       ` Documentation Robert Foerster
2010-12-02 20:37         ` Documentation David Lambert
2010-12-02 20:52           ` Documentation Robert Foerster
2010-12-03  7:35             ` Documentation Christophe Aeschlimann
2010-03-14  0:17 Documentation Giuseppe Macrì
2006-02-10  8:20 Documentation Nico -telmich- Schottelius
     [not found] <E1EiHi4-0000IY-16@host-192-168-0-1-bcn-london>
2005-12-02 21:22 ` Documentation John S Little
2005-12-02 22:30   ` Documentation Robb Romans
2005-12-03 11:26     ` Documentation Robin van Leeuwen
2005-12-04 14:05       ` Documentation John S Little
2005-12-05 16:46         ` Documentation Nivedita Singhvi
2005-12-05 17:11           ` Documentation Robb Romans
2005-12-05 18:09           ` Documentation John S Little
2005-12-05 23:57         ` Documentation Rich Persaud
2005-12-05 15:58       ` Documentation Robb Romans
2005-10-24 19:05 Documentation Vagin Andrey S.
2004-06-24 17:10 Documentation Tomas Ebenlendr
2004-06-24 22:03 ` Documentation Yoshinori K. Okuji
2004-06-25 13:17   ` Documentation Jeroen Dekkers
2004-06-26 15:05     ` Documentation Yoshinori K. Okuji
2004-05-27 13:12 Documentation Alexander E. Patrakov
2004-05-28 23:25 ` Documentation Greg KH
2004-06-02  6:11 ` Documentation Niko Sauer
2004-05-15 14:28 Documentation Jody
2004-05-17 13:35 ` Documentation Andrey Romanenko
2004-05-17 13:40 ` Documentation Miguel Bolanos
     [not found] <E1AoeOt-000173-00@wisbech.cl.cam.ac.uk>
     [not found] ` <FED3CB2D-57B5-11D8-BC94-00039350B9F2@epiuse.com>
2004-02-05 10:15   ` Documentation Bin Ren
2004-02-05 11:49   ` Documentation Yan-Ching CHU
2003-06-06 13:20 Documentation Matthew Wilcox
2002-08-29  9:39 documentation vandana  mehtani
2002-08-29 15:46 ` documentation Dave Wilhardt
2002-04-24 14:26 documentation Guilhem Tardy
2002-04-24 16:58 ` documentation Takashi Iwai
2002-04-24 19:32   ` documentation Guilhem Tardy
2002-04-26 17:54     ` documentation Takashi Iwai
2002-05-03 16:11       ` documentation Guilhem Tardy
2002-05-03 16:22         ` documentation Paul Davis
2002-05-03 16:28         ` documentation Takashi Iwai
2002-03-22 15:32 Documentation Gopakumar.C.E
2002-03-30  7:42 ` Documentation Ralf Baechle
2002-02-02  9:18 Documentation Guillaume Chamberland-Larose
2002-02-02 10:39 ` Documentation Yven J. Leist
2002-02-05 18:18   ` Documentation Randy.Dunlap
2001-11-15 18:03 Documentation war

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.