From: navneet panda <navneet_panda@yahoo.com>
To: William T Wilson <fluffy@snurgle.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel panic at boot
Date: Thu, 17 Jul 2003 11:39:58 -0700 (PDT) [thread overview]
Message-ID: <20030717183958.74004.qmail@web20006.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307171405460.18906-100000@benatar>
Hi,
Thanks for the suggestion but I already tried that
with
root=/dev/hda6 ( same as for working 2.4.20-18 )
It didn't work
Thanks anyway
Panda
--- William T Wilson <fluffy@snurgle.org> wrote:
> On Thu, 17 Jul 2003, navneet panda wrote:
>
> > root=LABEL=/ hdc=ide-scsi idebus=66
>
> Try gettin rid of worthless LABEL= and use a device
> identifier (i.e.
> root=/dev/hda3 or whatever). I have found that
> LABEL= is uniformly more
> trouble than it is worth.
>
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
next parent reply other threads:[~2003-07-17 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0307171405460.18906-100000@benatar>
2003-07-17 18:39 ` navneet panda [this message]
2003-07-17 10:57 navneet panda
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=20030717183958.74004.qmail@web20006.mail.yahoo.com \
--to=navneet_panda@yahoo.com \
--cc=fluffy@snurgle.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: kernel panic at boot' \
/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
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).