From: "Joshua Hudson" <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [-mm] klibc breaks my initscripts
Date: Tue, 23 May 2006 11:19:35 -0700 [thread overview]
Message-ID: <bda6d13a0605231119t466bed99q34991c242d259266@mail.gmail.com> (raw)
In-Reply-To: <44734AEF.2020104@zytor.com>
On 5/23/06, H. Peter Anvin <hpa@zytor.com> wrote:
> Pavel Machek wrote:
> > Hi!
> >
> > To reproduce: boot with init=/bin/bash
> >
> > attempt to
> >
> > mount / -oremount,rw
> >
> > I have this as my command line:
> >
> > root=/dev/hda4 resume=/dev/hda1 psmouse.psmouse_proto=imps
> > psmouse_proto=imps psmouse.proto=imps vga=1 pci=assign-busses
> > rootfstype=ext2
> >
>
> I tried this (or at least as close to this as I can get in my simulation
> environment), and I don't see any problems. It works as is should;
> however, mount(8) requires that /proc is mounted so that it can read
> /proc/partitions, but that has nothing to do with klibc (or the kernel
> overall) of course.
>
> I'm afraid I'm going to have to ask for more details...
>
> -hpa
Sounds like /etc/fstab corruption to me. Try this:
# mount -n /proc /proc -t proc
# mount /dev/hda4 -t ext2 -o remount,ro /
# mount -f /proc /proc -t proc
If it works, you have fstab corruption
If it doesn't, the problem lies elsewhere.
Yes I know that mount shouldn't require all that for
a remount. I'm probably way out on a limb on this one.
I still can't figure out what this has to do with klibc.
prev parent reply other threads:[~2006-05-23 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 8:37 Pavel Machek
2006-05-23 17:36 ` H. Peter Anvin
2006-05-23 21:11 ` Pavel Machek
2006-05-23 21:18 ` H. Peter Anvin
2006-05-23 21:51 ` Pavel Machek
2006-05-23 22:24 ` H. Peter Anvin
2006-05-23 22:36 ` Pavel Machek
2006-05-23 22:41 ` H. Peter Anvin
2006-05-23 17:48 ` H. Peter Anvin
2006-05-23 18:19 ` Joshua Hudson [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=bda6d13a0605231119t466bed99q34991c242d259266@mail.gmail.com \
--to=joshudson@gmail.com \
--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
all inboxes | Powered by JetHome®