From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] openssh: replace individual ssh-keygen calls with a single call
Date: Fri, 08 Aug 2014 22:03:31 +0200 [thread overview]
Message-ID: <87fvh6agvg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140804091755.GL32743@waldemar-brodkorb.de> (Waldemar Brodkorb's message of "Mon, 4 Aug 2014 11:17:56 +0200")
>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:
Hi,
> In OpenADK is use cfgfs - configuration filesystem. It maintains
> a tmpfs based /etc and let the user commit any changes via a
> commandline tool to a partition on a block/mtd device.
> Only changes are compressed via LZO and written to the maximum
> 16 MB cfgfs partition.
> http://www.openadk.org/docs/html/manual.html#_cfgfs_configuration_file_system
Heh, I wrote something similar a few years ago:
http://git.korsgaard.com/cgi-bin/gitweb.cgi?p=cfg.git;a=summary
It simply stored .tar.gz's of the changed files.
> It allows smooth updates without loosing device configuration data.
> Any interest in porting it to buildroot?
We try hard to not enforce policy, so I wouldn't want to make cfgfs a
required package, but as an optional one it make sense. Please do.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-08-08 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 1:21 [Buildroot] [PATCH 1/1] openssh: replace individual ssh-keygen calls with a single call Danomi Manchego
2014-08-03 7:37 ` Yann E. MORIN
2014-08-03 13:25 ` Danomi Manchego
2014-08-04 8:24 ` Thomas Petazzoni
2014-08-04 9:17 ` Waldemar Brodkorb
2014-08-08 20:03 ` Peter Korsgaard [this message]
2014-08-09 15:23 ` Thomas Petazzoni
2014-08-04 14:28 ` Danomi Manchego
2014-08-05 19:22 ` Baruch Siach
2014-08-03 8:36 ` 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=87fvh6agvg.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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