From: n.borisov.lkml@gmail.com (Nikolay Borisov)
To: kernelnewbies@lists.kernelnewbies.org
Subject: lightweight live os for bisect
Date: Thu, 21 Jul 2016 10:37:44 +0300 [thread overview]
Message-ID: <57907BC8.9030306@gmail.com> (raw)
In-Reply-To: <nmpshu$96b$1@ger.gmane.org>
On 07/21/2016 10:10 AM, Matwey V. Kornilov wrote:
> Hello,
>
> I would like to make a long-range bisect (unfortunately) to find where
> an issue appeared. The issue is present only on single one laptop, where
> I don't want to alter OS or somehow intrude things.
> Moreover, when I usually do `git bisect' between subsequent releases, I
> am fine with ordinarily 'make install', which is not the case now,
> because, for instance, 2.6.xx just won't run with modern systemd things
> (or, correctly, systemd things won't run with 2.6.xx).
>
> So, I would like to discover a way to compile USB live image with as
> simple as possible OS using precompiled ./linux tree. Only my test
> executable is required to run after the boot to show whether the issue here.
> So, what would you recommend? Or, how do you solve such problem usually?
>
Have you considered http://user-mode-linux.sourceforge.net/. This sounds
like an appropriate use case for it.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
next prev parent reply other threads:[~2016-07-21 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 7:10 lightweight live os for bisect Matwey V. Kornilov
2016-07-21 7:37 ` Nikolay Borisov [this message]
2016-07-21 7:49 ` Matwey V. Kornilov
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=57907BC8.9030306@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).