From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 61601] rootflags=noatime causes kernel panic when booting without initrd.
Date: Mon, 11 Aug 2014 14:24:13 +0000 [thread overview]
Message-ID: <bug-61601-13602-obGetyG9Oc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-61601-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=61601
--- Comment #13 from Theodore Tso <tytso@mit.edu> ---
Jacob, there are very good programs to help people learn how to get involved
with kernel development. See the kernelnewbies.org web site and mailing list,
for example. But you need to have some amount of basic competence; being able
to use Google well, for example, and doing silly things like making sure the
patches compile before you submit patches for review.
Also, if you have clueless people asking users completely random questions that
are completely useless in terms of fixing the problem, it wastes the user's
time and causes them to get very frustrated. So having newbies trying to help
users who are reporting kernel bugs is not a good idea. If they want to help
users install Linux distributions, that's fine --- so long as you are minimally
competent in doing installation. Similarly, if you are completely incompetent
in doing kernel development, you should not be offering to help users.
There are ways for newbies to get involved. The problem is Nick has
consistently ignored advice of people who have wasted a huge amount of time
trying to get him on the right path. Which is why he has gotten banned.
If you are someone who wants to get started, there is the Eudyptula Challenge
(http://eudyptula-challenge.org). Nick finally got involved with this, and
then violated the very simple rules, which caused him to get ejected from the
Challenge within hours, thus setting a new record for the Eudyuptula Challenge.
Anyway, this is off topic for the bug. So please stop discussing this here,
please.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-11 14:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 12:05 [Bug 61601] New: rootflags=noatime causes kernel panic when booting without initrd bugzilla-daemon
2013-11-13 14:50 ` [Bug 61601] " bugzilla-daemon
2013-11-15 19:39 ` bugzilla-daemon
2014-03-30 16:06 ` bugzilla-daemon
2014-04-07 15:27 ` bugzilla-daemon
2014-04-11 21:25 ` bugzilla-daemon
2014-06-24 18:41 ` bugzilla-daemon
2014-08-11 3:08 ` bugzilla-daemon
2014-08-11 3:09 ` bugzilla-daemon
2014-08-11 4:17 ` bugzilla-daemon
2014-08-11 5:06 ` bugzilla-daemon
2014-08-11 5:32 ` bugzilla-daemon
2014-08-11 7:04 ` bugzilla-daemon
2014-08-11 14:24 ` bugzilla-daemon [this message]
2014-08-12 5:02 ` bugzilla-daemon
2015-06-09 9:52 ` bugzilla-daemon
2015-06-09 21:35 ` bugzilla-daemon
2015-06-10 16:04 ` bugzilla-daemon
2016-07-22 14:05 ` bugzilla-daemon
2025-03-31 16:20 ` bugzilla-daemon
2025-04-03 10:14 ` bugzilla-daemon
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=bug-61601-13602-obGetyG9Oc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 NNTP newsgroup(s).