From: maximilian attems <max-U9r9yeDMy7A@public.gmane.org>
To: Victor Lowther <victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Bogdan Costescu
<Bogdan.Costescu-hEciA7+sKtudPOQpRHQ53DeJuz7u0hKX@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 4/4] Add some predefined break points.
Date: Sun, 1 Mar 2009 16:07:33 +0100 [thread overview]
Message-ID: <20090301150733.GA12608@stro.at> (raw)
In-Reply-To: <1235754943.6445.3.camel-76q0VzFBGGr21HsLBtNmTckMGDeJXHgy@public.gmane.org>
On Fri, 27 Feb 2009, Victor Lowther wrote:
> On Thu, 2009-02-26 at 15:04 +0100, Bogdan Costescu wrote:
> > On Wed, 25 Feb 2009, Victor Lowther wrote:
> >
> > > +getarg 'break=pre-udev' && emergency_shell
> >
> > I would like to suggest doing something different: look for the value
> > of the 'break' parameter at the very beginning and save it in a
> > variable such that it would be possible to modify it in the shell run
> > for the breakpoint to point to a later breakpoint - this way one can
> > do a gradual checking of the initramfs progress by going from one
> > breakpoint to the next.
>
> Not a bad idea. I will code something up for this.
right as this is initramfs-tools inspired, we use a variable
and have those predefined breakpoints:
(top, modules, premount, mount, mountroot, bottom, init).
--
maks
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-01 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 2:32 [PATCH 1/4] Move actually mounting the root filesystem into its own series of hooks Victor Lowther
[not found] ` <40b7db44cbcb49b1fb50445d786cd4851adba14a.1235615253.git.victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-02-26 2:32 ` [PATCH 2/4] Modify getarg to be slightly more useful Victor Lowther
2009-02-26 2:32 ` [PATCH 3/4] Trim out device nodes we do not have to actually create Victor Lowther
2009-02-26 2:32 ` [PATCH 4/4] Add some predefined break points Victor Lowther
[not found] ` <43ca8d3a8aed54367069b23fc43720cbf5517ec0.1235615253.git.victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-02-26 14:04 ` Bogdan Costescu
[not found] ` <Pine.LNX.4.64.0902261501070.2766-qcrbbFV08EMdmw7VdWMmteH3J2bgQ+4lG9Ur7JDdleE@public.gmane.org>
2009-02-27 17:15 ` Victor Lowther
[not found] ` <1235754943.6445.3.camel-76q0VzFBGGr21HsLBtNmTckMGDeJXHgy@public.gmane.org>
2009-03-01 15:07 ` maximilian attems [this message]
[not found] ` <20090301150733.GA12608-U9r9yeDMy7A@public.gmane.org>
2009-03-01 15:56 ` Thiago Galesi
2009-03-01 20:02 ` Victor Lowther
2009-02-26 12:20 ` [PATCH 1/4] Move actually mounting the root filesystem into its own series of hooks Karel Zak
-- strict thread matches above, loose matches on Subject: below --
2009-03-05 2:40 [PATCH 1/4] Move " Victor Lowther
[not found] ` <40b7db44cbcb49b1fb50445d786cd4851adba14a.1236220506.git.victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-05 2:40 ` [PATCH 4/4] Add some predefined break points Victor Lowther
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=20090301150733.GA12608@stro.at \
--to=max-u9r9yedmy7a@public.gmane.org \
--cc=Bogdan.Costescu-hEciA7+sKtudPOQpRHQ53DeJuz7u0hKX@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.