From: "Stoyan Gaydarov" <stoyboyker@gmail•com>
To: linux-next@vger•kernel.org
Subject: Linux-next testing
Date: Wed, 16 Jul 2008 06:27:27 -0500 [thread overview]
Message-ID: <6d291e080807160427o5a853ca8u96841a2717901a8d@mail.gmail.com> (raw)
I have a box that I would like to devote to test the linux-next
kernels. I am however not very experienced with the whole process. I
installed a clean Ubuntu server on it because thats what I had at
home, I know how to compile the kernel, and install(make; make
modules; make install) I also know how to log the build so that if
theres any errors i can have a record of what went wrong. What I need
help is knowing what to test and getting reports back to you. 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. Anyway I also wanted to know which configuration
needed the most testing or if I should just stick with the
randconfig(btw this is an x86 box). The other question is about
reporting failures, which i can almost guarantee will happen, one way
is to keep a vanilla kernel installed so that i can aways go back to
it and report the log files but if its a oops or a BUG() call i am not
sure they get reported there... The last question I have is regarding
the load on the box, this is not a very new box so I cant run too many
things at once but I would like to know if there is anything I should
be running on the box while it is running that way it can stress the
system a little and try to break it in a way that can be useful.
Looking back at what I wrote, those are not quite questions but I
think you get the idea, I just need some information on what to do so
that I can be of use to the people that are developing with
linux-next.
-Stoyan G
next reply other threads:[~2008-07-16 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 11:27 Stoyan Gaydarov [this message]
2008-07-16 14:43 ` Linux-next testing Kyle Spaans
2008-07-17 7:48 ` Stoyan Gaydarov
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=6d291e080807160427o5a853ca8u96841a2717901a8d@mail.gmail.com \
--to=stoyboyker@gmail$(echo .)com \
--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