Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Adding local file system overlay
Date: Fri, 26 Apr 2013 09:33:36 +0200 (CEST)	[thread overview]
Message-ID: <1768202256.1976834.1366961616672.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <6119D107D82B0940B389FAED3F2DDE6616222D57@Ansuz.hms.se>


----- Mail original -----
> Hi Buildroot mailinglist!
> 
> During development of a new platform I sometimes find it useful to
> bundle my test builds with my own script/configuration files.
> Example: SSH keys
> 
> This is not something that we want to include in default
> configuration for a board or by any way get in a final build so
> instead I added a second step to local file system overlay checking
> a local variable and if it is set us it as a roofs overlay.
> 
> Is this something that is of interests for the upstream project?
> 
> Example:
> export  LOCAL_ROOTFS_OVERLAY=/local-rootfs-overlay
> make
> 


doesn't buildroot already do that ?

system configuration => overlay directory

or is your patch doing something different

on a semi-related note, I run the following post-build script for 
ssh keys :

#!/bin/sh
mkdir -p $1/root/.ssh/
chmod 0700 $1/root/.ssh/
chmod 0700 $1/root
cp -p ~/.ssh/id_rsa.pub $1/root/.ssh/authorized_keys
chmod 0600 $1/root/.ssh/authorized_keys


that will copy my public key as an authorized key on the built system

  reply	other threads:[~2013-04-26  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  6:10 [Buildroot] Adding local file system overlay Lars Dunemark
2013-04-26  7:33 ` Jeremy Rosen [this message]
2013-04-26  8:48   ` Lars Dunemark
2013-04-26 17:02     ` Arnout Vandecappelle

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=1768202256.1976834.1366961616672.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.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