From: "Dominik 'Rathann' Mierzejewski" <rathann@icm.edu.pl>
To: linux-mips@linux-mips.org
Subject: Re: linux 2.4 and Indy
Date: Fri, 30 Jan 2004 12:12:56 +0100 [thread overview]
Message-ID: <20040130111255.GB7501@icm.edu.pl> (raw)
In-Reply-To: <20040130105903.GA12562@ballina>
On Fri, Jan 30, 2004 at 11:59:03AM +0100, Jorik Jonker wrote:
[...]
> Hmm, that's strange, I believe that should do the trick, but when I checkout
> a tree (cvs -z3 -d:.. co -r linux_2_4 -D 'December 10 2003' linux), I still
> get a 'half-booting' kernel. Shall I try to checkout an even older one, until
> something is starting to work, or is something else going wrong?
I have a working 5th December 2003 kernel running on R4600 V2.0, but since
there were no changes between 5th and 11th December, I'd suspect that yours
should boot fine, too. Did you check if the files you checked out are really
not later than 11th December?
--
Dominik 'Rathann' Mierzejewski <rathann@icm.edu.pl>
Interdisciplinary Centre for Mathematical and Computational Modelling
Warsaw University | http://www.icm.edu.pl | tel. +48 (22) 5540810
next prev parent reply other threads:[~2004-01-30 11:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 10:22 linux 2.4 and Indy Jorik Jonker
2004-01-29 10:40 ` Kumba
2004-01-30 10:59 ` Jorik Jonker
2004-01-30 11:12 ` Dominik 'Rathann' Mierzejewski [this message]
2004-01-30 20:49 ` Jorik Jonker
2004-01-30 21:01 ` Jorik Jonker
2004-01-31 3:04 ` Ralf Baechle
2004-01-31 14:10 ` Jorik Jonker
2004-02-01 4:52 ` R4600 V1.7 errata Ralf Baechle
2004-02-03 11:39 ` Ralf Baechle
2004-02-03 11:42 ` Dominik 'Rathann' Mierzejewski
2004-02-03 11:52 ` Ralf Baechle
2004-02-03 15:43 ` Maciej W. Rozycki
2004-02-03 16:12 ` Ralf Baechle
2004-02-03 16:20 ` Maciej W. Rozycki
2004-02-04 15:48 ` Dominik 'Rathann' Mierzejewski
2004-02-04 15:59 ` Pete Popov
2004-02-04 20:04 ` Ralf Baechle
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=20040130111255.GB7501@icm.edu.pl \
--to=rathann@icm.edu.pl \
--cc=linux-mips@linux-mips.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