mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Proper way to modify an ETC file
Date: Tue, 13 Mar 2012 19:06:42 +0100	[thread overview]
Message-ID: <20120313180642.GA20481@pengutronix.de> (raw)
In-Reply-To: <loom.20120313T142834-135@post.gmane.org>

On Tue, Mar 13, 2012 at 05:21:15PM +0000, Jerry Kirk wrote:
> Within my embedded project I'd like to modify Busybox's FTPD command to allow 
> more general access to the filesystem. I'm not quite sure the right way to do 
> this. I've been considering
> 
> 1. A local "patch" to the busybox file that gets copied
> 2. A new package that runs SED and modifies the busybox file in /etc or copies 
> a new file into the root
> 
> What is the right way to make local changes for my project to the root 
> filesystem of the embedded system?

Which file do you want to modify? /etc/inetd.conf.d/ftpd? You can provide a
local version for this in your BSP: projectroot/etc/inetd.conf.d/ftpd

$ ptxdist drop busybox targetinstall
4 ptxdist go
[...]

Take a look at the quickstart manual[1]. This and more is described there.

Michael

[1] http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2012-03-13 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 17:21 Jerry Kirk
2012-03-13 18:06 ` Michael Olbrich [this message]

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=20120313180642.GA20481@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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