From: "Stoyan Gaydarov" <stoyboyker@gmail•com>
To: kspaans@student•math.uwaterloo.ca
Cc: linux-next@vger•kernel.org
Subject: Re: Linux-next testing
Date: Thu, 17 Jul 2008 02:48:23 -0500 [thread overview]
Message-ID: <6d291e080807170048v762ddd90mc89794cb9c42adb8@mail.gmail.com> (raw)
In-Reply-To: <20080716144316.GA26366@student.math>
On Wed, Jul 16, 2008 at 9:43 AM, Kyle Spaans
<kspaans@student•math.uwaterloo.ca> wrote:
> On Wed, Jul 16, 2008 at 06:27:27AM -0500, Stoyan Gaydarov wrote:
>> I know I
>> can do a 'git clone "path to linux-next git tree" ' and go into that
>> and use randconfig then install and reboot, but I was wondering if
>> there was some other better way to do it because the clone command
>> only works in an empty directory. I think fetch or something like that
>> might work better.
> Have a look in the archives for this list. Every time Stephen announces a new linux-next release, he includes a blurb at the bottom of the email that will tell you how you can get the linux-next tree, besides just cloning it anew each day. (I found that blurb helpful even on top of the wiki at http://linux.f-seidel.de/linux-next/pmwiki/)
>
>> The last question I have is ... stress the system a little and try to
>> break it in a way that can be useful.
> Look around on the linux-next wiki, and you'll see that other people are running automated testing. Have a look at how they are doing it. Also look around on the kernelnewbies.org website, they have tips for how to stress-test your system. (bonnie++ as a filesystem benchmark springs immediately to mind, prime95 as a way to generate cpu load, etc...). I'm sure a quick internet search for "linux stress test" will also turn up useful results.
>
> I'm largely doing the same thing as you, so I'll be interested to see the answers to your other questions.
I was actually thinking about doing something with uml, where i could
build several kernels with ARCH=um SUBARCH=** that way I could boot
them without having to restart the computer and I could also log all
of the output that was generated a lot easier, and the other thing is
I can have multiple kernels booted at the same time. This would make
the stress tests a lot more effective if theres even less resources
per uml kernel running. Any suggestions on how to do this effectively
and correctly(since i am not an expert in any of these topics) would
be greatly appreciated.
-Stoyan G
>
> gl & hf
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2008-07-17 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 11:27 Linux-next testing Stoyan Gaydarov
2008-07-16 14:43 ` Kyle Spaans
2008-07-17 7:48 ` Stoyan Gaydarov [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=6d291e080807170048v762ddd90mc89794cb9c42adb8@mail.gmail.com \
--to=stoyboyker@gmail$(echo .)com \
--cc=kspaans@student$(echo .)math.uwaterloo.ca \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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