From: David Woodhouse <dwmw2@infradead.org>
To: Kyle Harris <kharris@nexus-tech.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 2.5 questions
Date: Fri, 13 Sep 2002 08:24:49 +0100 [thread overview]
Message-ID: <10485.1031901889@redhat.com> (raw)
In-Reply-To: <E17pfu5-0001pj-00@granger.mail.mindspring.net>
kharris@nexus-tech.net said:
> How do I get the latest code base for 2.5 kernels? I pulled the latest
> cvs but it appears this must be for 2.4 since it doesn't compile. Is
> there a separate branch for 2.5?
Should do. What breaks? It'll only be cosmetic, surely?
> How stable is mtd for 2.5? I'm seeing some very strange behavior where
> if I make slight mods to even script files, the files become unusable
> and cause the system to hang. I'm running 2.5.30-rmk1-pxa1 with jffs2
> root fs.
Not expected to break. Not highly tested either. More details please.
SysRq-T is your friend.
--
dwmw2
next prev parent reply other threads:[~2002-09-13 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 2:05 2.5 questions Kyle Harris
2002-09-13 7:24 ` David Woodhouse [this message]
2002-09-13 11:50 ` Kyle Harris
2002-09-13 12:45 ` David Woodhouse
2002-09-13 13:55 ` Kyle Harris
2002-09-13 14:15 ` David Woodhouse
2002-09-13 16:52 ` David Woodhouse
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=10485.1031901889@redhat.com \
--to=dwmw2@infradead.org \
--cc=kharris@nexus-tech.net \
--cc=linux-mtd@lists.infradead.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