Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/9] makedevs: Rework README
Date: Wed, 19 Nov 2014 23:05:11 +0100	[thread overview]
Message-ID: <20141119220511.GC3779@free.fr> (raw)
In-Reply-To: <1416068964-22529-2-git-send-email-maxime.hadjinlian@gmail.com>

Maxime, All,

On 2014-11-15 17:29 +0100, Maxime Hadjinlian spake thusly:
> Make all the example as a space separated list.
> The definition of the different type was modified to look like the same
> section on the manual.

That patch has already been applied by Peter on master, a full week
before you sent this setries.

When you re-spin a series, can you rebase on-top of the master current
at the time you send it, please, to avoid reviewers scratching their
head wondering what went wrong?

You owe me a beer at FOSDEM! :-p

Regards,
Yann E. MORIN.

> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
>  package/makedevs/README | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/package/makedevs/README b/package/makedevs/README
> index 6c54052..70844bf 100644
> --- a/package/makedevs/README
> +++ b/package/makedevs/README
> @@ -6,7 +6,7 @@ You can do all sorts of interesting things with a device table file.
>  For example, if you want to adjust the permissions on a particular
>  file you can just add an entry like:
>  
> -  /sbin/foobar        f       2755    0       0       -       -       -       -       -
> +  /sbin/foobar f 2755 0 0 - - - - -
>  
>  and (assuming the file /sbin/foobar exists) it will be made setuid
>  root (regardless of what its permissions are on the host filesystem.
> @@ -15,20 +15,20 @@ Furthermore, you can use a single table entry to create a many device
>  minors.  For example, if I wanted to create /dev/hda and
>  /dev/hda[0-15] I could just use the following two table entries:
>  
> -  /dev/hda    b       640     0       0       3       0       0       0       -
> -  /dev/hda    b       640     0       0       3       1       1       1       15
> +  /dev/hda b 640 0 0 3 0 0 0 -
> +  /dev/hda b 640 0 0 3 1 1 1 15
>  
>  Device table entries take the form of:
>  
> -<name>    <type>      <mode>  <uid>   <gid>   <major> <minor> <start> <inc>   <count>
> +<name> <type> <mode> <uid> <gid> <major> <minor> <start> <inc> <count>
>  
>  where name is the file name,  type can be one of:
>  
> -      f       A regular file
> -      d       Directory
> -      c       Character special device file
> -      b       Block special device file
> -      p       Fifo (named pipe)
> +      f: A regular file
> +      d: Directory
> +      c: Character special device file
> +      b: Block special device file
> +      p: Fifo (named pipe)
>  
>  uid is the user id for the target file, gid is the group id for the
>  target file.  The rest of the entries (major, minor, etc) apply only
> -- 
> 2.1.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-11-19 22:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 16:29 [Buildroot] [PATCH 1/9] package/*/*.mk: Fix indent Maxime Hadjinlian
2014-11-15 16:29 ` [Buildroot] [PATCH 2/9] makedevs: Rework README Maxime Hadjinlian
2014-11-19 22:05   ` Yann E. MORIN [this message]
2014-11-24  9:34     ` Maxime Hadjinlian
2014-11-15 16:29 ` [Buildroot] [PATCH 3/9] manual: Rework makedevs syntax Maxime Hadjinlian
2014-11-19 22:14   ` Yann E. MORIN
2014-11-22 19:15   ` Thomas Petazzoni
2014-11-15 16:29 ` [Buildroot] [PATCH 4/9] manual: Remove trailing space Maxime Hadjinlian
2014-11-19 22:15   ` Yann E. MORIN
2014-11-22 19:15   ` Thomas Petazzoni
2014-11-15 16:29 ` [Buildroot] [PATCH 5/9] manual: Add missing vim header Maxime Hadjinlian
2014-11-19 22:17   ` Yann E. MORIN
2014-11-22 19:15   ` Thomas Petazzoni
2014-11-15 16:29 ` [Buildroot] [PATCH 6/9] manual: Add newline before block code Maxime Hadjinlian
2014-11-19 22:21   ` Yann E. MORIN
2014-11-22 19:15   ` Thomas Petazzoni
2014-11-15 16:29 ` [Buildroot] [PATCH 7/9] manual: Remove dollar before command example Maxime Hadjinlian
2014-11-19 22:29   ` Yann E. MORIN
2014-11-22 19:16   ` Thomas Petazzoni
2014-11-24  8:14     ` Maxime Hadjinlian
2014-11-15 16:29 ` [Buildroot] [PATCH 8/9] manual: Harmonize " Maxime Hadjinlian
2014-11-19 22:32   ` Yann E. MORIN
2014-11-15 16:29 ` [Buildroot] [PATCH 9/9] manual: Block code needs only 4 dashes Maxime Hadjinlian
2014-11-19 22:37   ` Yann E. MORIN
2014-11-22 19:16   ` Thomas Petazzoni
2014-11-19 22:10 ` [Buildroot] [PATCH 1/9] package/*/*.mk: Fix indent Yann E. MORIN
2014-11-19 22:25 ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141119220511.GC3779@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox