Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Add support for package-declared devices
Date: Wed, 7 Sep 2011 18:22:51 +0200	[thread overview]
Message-ID: <201109071822.51608.arnout@mind.be> (raw)
In-Reply-To: <4E673792.5040001@free-electrons.com>


On Wednesday 07 September 2011 11:21:22, Maxime Ripard wrote:
> On 06/09/2011 18:03, Arnout Vandecappelle wrote:
> > On Monday 05 September 2011 18:15:14, Maxime Ripard wrote:
> >> On 05/09/2011 08:52, Thomas Petazzoni wrote:
> >>> Yes, exactly. However, I don't really like the name <pkg>_DEVICE_TABLE
> >>> because, it might be for other purposes as well (setting setuid bit,
> >>> giving specific owner/group or permissions, etc.). Does anyone has an
> >>> idea for a better name?
> >> 
> >> I agree, I don't like it neither, but I have no idea on what could be
> >> better...
> >> 
> >> Files, maybe, but I find it way too generic.
> >
> > 
> >  How about _FILE_MOD_TABLE (cfr. chmod)?
> 
> Hmm, I'm not quite sure, it is more than just mod. Maybe reuse the
> "skeleton" term already in use in buildroot.

 AFAICS it does three things:
- make device nodes (mknod)
- change permissions (chmod)
- set ownership (chown)


 So skeleton is not really the right term, as it only refers to the mknod 
function again.  (Although not-yet-existing files and directories are created, 
that's not usually the main purpose for files and directories.)

 FILE is also not a good idea since it also applies to directories and device 
nodes which are not really files.

 A complete name would be _NOD_MOD_OWN_TABLE, but that's too long and too 
cryptic :-)  Plus, we might want to add things like setting the utimes etc. in 
the future.

 The functionality is in fact comparable to install - copy files and set 
attributes (except for the copy part).  So we could use _ATTRIBUTE_TABLE. 
Unfortunately, 'attributes' could also refer to the e2fs file attributes, 
which are a different thing entirely (cfr. man chattr).  Or 
_FILE_INSTALL_TABLE.

 We could also consider that it sets most of the content of struct stat.  But 
_STAT_TABLE is again a bit cryptic.


 Enough possibilities...


 Regards,
 Arnout
 

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43

  reply	other threads:[~2011-09-07 16:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 12:08 [Buildroot] [pull request] Pull request for branch for-2011.11/pkg-device Maxime Ripard
2011-09-02 12:08 ` [Buildroot] [PATCH 1/2] Add support for package-declared devices Maxime Ripard
2011-09-04 21:36   ` Arnout Vandecappelle
2011-09-05  6:52     ` Thomas Petazzoni
2011-09-05 16:15       ` Maxime Ripard
2011-09-06 16:03         ` Arnout Vandecappelle
2011-09-07  9:21           ` Maxime Ripard
2011-09-07 16:22             ` Arnout Vandecappelle [this message]
2011-09-08  8:18               ` Maxime Ripard
2011-09-08  9:00                 ` Arnout Vandecappelle
2011-09-08 10:00                 ` Quotient Remainder
2011-09-08 11:03                   ` Luca Ceresoli
2011-09-08 11:24                     ` Michael S. Zick
2011-09-05  9:11     ` Maxime Ripard
2011-09-05 10:08     ` Michael S. Zick
2011-09-02 12:09 ` [Buildroot] [PATCH 2/2] Convert busybox to the device declaration method Maxime Ripard

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=201109071822.51608.arnout@mind.be \
    --to=arnout@mind.be \
    --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