All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cliff Brake" <cliff.brake@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: customisable pivot-root functionality
Date: Thu, 25 Jan 2007 07:45:08 -0500	[thread overview]
Message-ID: <f96d234e0701250445h75a9aec6qc0a6a1f0c729a9e5@mail.gmail.com> (raw)
In-Reply-To: <45B820C1.1090100@whitby.id.au>

On 1/24/07, Rod Whitby <rod@whitby.id.au> wrote:
> As part of the "remove all slugos-specific stuff from OE, and make it
> generally useful and available to multiple distributions" effort, I need
> to replicate the current slugos-init pivot-root functionality, and I
> want to do it in a way which might be useful for other OE platforms (or
> at least is not tied to one specific NSLU2 distribution).  At a minimum,
> I want to use it for a derivative of Angstrom, which I'm calling
> "MokoSlug" and possible retro-fit it into the Unslung firmware too.
...

> 2) Would this functionality be of use to any other devices that use OE?

Yes.

> 3) Who else is interested in giving input to, and reviewing the output
> of, this effort?

Yes, I'm currently working on two projects that will required the
ability to do field updates -- (stick a USB stick in the device and it
updates itself).  I'm currently planning to have a small RO update
image (which never gets updated) that is smart enough to update the
main rootfs and then pivot-root to it.  It would be nice if this could
be made somewhat general as it is probably a fairly common
requirement.  Another reason for the RO update image is to be able to
easily recover if the main image gets corrupted.  I'm not sure if
there is anything in common with your slug work, but It would be nice
to have a general framework available to do the pivot-root stuff.

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com



  parent reply	other threads:[~2007-01-25 12:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22  0:12 RFC: Adding a new global MACHINE_ENDIAN variable Rod Whitby
2007-01-22 17:01 ` Koen Kooi
2007-01-22 19:14   ` Rod Whitby
2007-01-22 20:03     ` Koen Kooi
2007-01-23  0:10       ` Deprecating ixp4xx, nslu2 in favour of endian-specific machine settings (Was: RFC on MACHINE_ENDIAN) Rod Whitby
2007-01-23  5:40         ` Removal of the proprietary Intel IXP ethernet driver (ixp4{00, 25}-eth, ixp-osal, ixp4xx-csr) from OE Rod Whitby
2007-01-23 19:23           ` Robert Wörle
2007-01-23 19:56             ` Rod Whitby
2007-01-25  3:15               ` RFC: customisable pivot-root functionality Rod Whitby
2007-01-25  3:53                 ` Justin Patrin
2007-01-25 12:45                 ` Cliff Brake [this message]
2007-01-25 16:54                 ` Hans Henry von Tresckow
2009-04-20  5:52           ` Removal of the proprietary Intel IXP ethernet driver (ixp4{00, 25}-eth, ixp-osal, ixp4xx-csr) from OE Rod Whitby
2007-01-23 11:13         ` Deprecating ixp4xx, nslu2 in favour of endian-specific machine settings (Was: RFC on MACHINE_ENDIAN) Richard Purdie
2007-01-23 19:37           ` Rod Whitby
2007-01-23 20:34             ` Richard Purdie
2007-01-24  6:41               ` SITEINFO_ENDIAN(N)ESS (NN, not N) Rod Whitby
2007-01-24  6:44                 ` Rod Whitby
2007-01-28 12:41           ` Deprecating ixp4xx, nslu2 in favour of endian-specific machine settings (Was: RFC on MACHINE_ENDIAN) Rod Whitby

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=f96d234e0701250445h75a9aec6qc0a6a1f0c729a9e5@mail.gmail.com \
    --to=cliff.brake@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.