public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Perkel <marc@perkel.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Paul Rolland <rol@as2917.net>,
	"'Chris Lalancette'" <clalance@redhat.com>,
	"'Rafael J. Wysocki'" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: could not find filesystem /dev/root - menucinfig
Date: Tue, 07 Nov 2006 07:10:30 -0800	[thread overview]
Message-ID: <4550A1E6.1070708@perkel.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0611071013420.11192@yvahk01.tjqt.qr>

I figured out the problem. the SATA drivers weren't being compiled. 
That's because the menu system was rearanged. May I suggest that if you 
are going to change the structure that you include some upgrade mapping 
so that if old items are mapped to new items and people like me won't 
waste many hours just to find out that what I though was selected isn't.

menuconfig needs to be upgrade smart.


      parent reply	other threads:[~2006-11-07 15:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  1:54 could not find filesystem /dev/root Marc Perkel
2006-11-06 10:18 ` Mathieu SEGAUD
2006-11-06 10:26   ` Arjan van de Ven
2006-11-06 14:20     ` Marc Perkel
2006-11-06 20:12 ` Rafael J. Wysocki
2006-11-06 21:18   ` Marc Perkel
2006-11-06 21:25     ` Rafael J. Wysocki
2006-11-06 21:30       ` Marc Perkel
2006-11-06 23:46         ` Chris Lalancette
2006-11-06 23:53           ` Marc Perkel
2006-11-07  7:04             ` Paul Rolland
2006-11-07  9:17               ` Jan Engelhardt
2006-11-07  9:52                 ` Paul Rolland
2006-11-07 14:18                   ` Jan Engelhardt
2006-11-07 16:13                     ` Paul Rolland
2006-11-07 17:31                       ` Jan Engelhardt
2006-11-07 15:10                 ` Marc Perkel [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=4550A1E6.1070708@perkel.com \
    --to=marc@perkel.com \
    --cc=clalance@redhat.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rol@as2917.net \
    /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