public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Derek Chen-Becker <derek@chen-becker.org>
To: Linux-Kernel@vger.kernel.org
Subject: Problem with 2.6.3 and initrd
Date: Thu, 22 Apr 2004 08:13:37 -0600	[thread overview]
Message-ID: <4087D311.5080302@chen-becker.org> (raw)

Hi,
     I've been trying all day to get 2.6.3 booting on my server from 
2.4.22. I've run into a major issue with the initrd, and I can't figure 
out what's going on. The kernel finds the initrd and mounts it on root, 
but then the first command I have (mount /proc) fails with an error that 
it can't create a lock on mtab because there is no space left on the 
device. Everything else after that blows up. I thought I'd be clever and 
create a bogus file on the initrd, then delete it as the first step in 
linuxrc so that there is space on the device, but I still get the same 
error. My 2.4.22 kernel works find with a very similar initrd, so I'm 
having trouble figuring out what is different here. I've done all kinds 
of google searches on this and haven't found anything very helpful other 
than some references to initramfs. Any thoughts?

Thanks,

Derek

-- 
+---------------------------------------------------------------+
| Derek Chen-Becker                                             |
| derek@chen-becker.org                                         |
| http://chen-becker.org                                        |
|                                                               |
| PGP key available on request or from public key servers       |
| ID: 21A7FB53                                                  |
| Fngrprnt: 209A 77CA A4F9 E716 E20C  6348 B657 77EC 21A7 FB53  |
+---------------------------------------------------------------+

                 reply	other threads:[~2004-04-22 14:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4087D311.5080302@chen-becker.org \
    --to=derek@chen-becker.org \
    --cc=Linux-Kernel@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