From: Christos Gkekas <chris.gekas@gmail.com>
To: Joshua Chamberlain <chamberlain.dev@gmail.com>
Cc: Eric Curtin <ericcurtin17@gmail.com>, linux-newbie@vger.kernel.org
Subject: Re: How to find bugs to fix
Date: Sat, 3 Feb 2018 10:15:21 +0000 [thread overview]
Message-ID: <20180203101303.GA6747@inspiron> (raw)
In-Reply-To: <20180202185521.GA18791@u.boisestate.edu>
On 02/02/18 11:55:22 -0700, Joshua Chamberlain wrote:
> Thanks for the input. I was hoping to fix bugs that were affecting many
> people, not just me.
>
> I just tried all my USB devices I had lying around,
> but could not find any bugs. I didn't think to check the buttons on my
> laptop, so thanks for that!
>
> The bugs that I tend to see on laptops seem to not be a part of the OS
> itself. For instance, when I resume my laptop from hibernation, the
> networking interface doesn't work, which I think is an issue somehwere
> in Ubuntu. I can't believe I'm complaining about this, but LINUX IS TOO
> STABLE!
>
> Thanks though...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
Hi Josh,
I would highly recommend browsing the Kernel newbies site here:
https://kernelnewbies.org/
It contains a lot of information to get you started, including how to
navigate through the Linux code, how the development process works, how
to locate bugs, submit patches and so on. I think it is important to
read through this material if you have not already done so.
Additionally you can compile the kernel and have a look at the warnings
that gcc generates during compilation. The majority of them will be red
herrings, but some of them can point to genuine issues with the code and
actual bugs. I think that is a good way to get started.
Regards,
Christos
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2018-02-03 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 0:23 How to find bugs to fix Joshua Chamberlain
2018-02-01 0:50 ` Eric Curtin
2018-02-02 18:55 ` Joshua Chamberlain
2018-02-03 10:15 ` Christos Gkekas [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=20180203101303.GA6747@inspiron \
--to=chris.gekas@gmail.com \
--cc=chamberlain.dev@gmail.com \
--cc=ericcurtin17@gmail.com \
--cc=linux-newbie@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).