mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	James Bourne <jbourne@mtroyal.ab.ca>
Subject: Re: ext3 clings to you like flypaper
Date: Mon, 17 Feb 2003 19:31:13 +0100	[thread overview]
Message-ID: <20030217183113.GA24922@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <9850000.1045504008@[10.10.2.4]>

On Mon, 17 February 2003 09:46:51 -0800, Martin J. Bligh wrote:
> 
> >> The point remains, if I say I want ext2, I should get ext2, not whatever 
> >> some random developer decides he thinks I should have. Worst of all,
> >> the system then lies to you and says it's mounted ext2 when it's not.

You appear to not have /etc/mtab as a symlink to /proc/mounts. One of
the first things I do on fresh debian installations. The kernel should
know better than some file, especially when / is mounted ro.

> > This is, how things worked for me:
> > 1. Kernel tries to mount rootfs ext3. If this fails, it will continue
> > trying ext2. No other fs compiled into kernel.
> > 2. If there is a journal, it is ext3.
> > 3. Init scripts read /etc/fstab and read ext2.
> > 4. root is remounted as ext2.
> > 5. System allows me to log it, root is ext2, life is good.
> > 
> > Where is your behaviour different from this list? Where do you say you
> > want ext2 but don't get it?
> 
> That's what I'd expect to happen ... as others have pointed out, it may
> be a distro issue ... do you have the snippet of the init scrips that
> do the remount as ext2 to hand? Maybe debian is just broken ...

My broken memory tells me that Debian is working quite fine. The code
in question should be in /etc/init.d/checkroot.sh in your system.

But my eye does not find the spot, where / is remounted with a
different type. This is strange! I've often been surprised that adding
a journal and putting ext3 support in the kernel without editing
/etc/fstab was not enough.

I should test it again to prove my eye wrong.

Jörn

-- 
With a PC, I always felt limited by the software available. On Unix, 
I am limited only by my knowledge.
-- Peter J. Schoenster

  parent reply	other threads:[~2003-02-17 18:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17  7:04 Martin J. Bligh
2003-02-17 11:44 ` Miquel van Smoorenburg
2003-02-17 11:50 ` David Woodhouse
2003-02-17 16:48   ` Martin J. Bligh
2003-02-17 17:08     ` Jörn Engel
2003-02-17 17:21       ` Markus Plail
2003-02-17 17:46       ` Martin J. Bligh
2003-02-17 18:22         ` Xavier Bestel
2003-02-17 18:31         ` Jörn Engel [this message]
2003-02-17 18:38           ` Jörn Engel
2003-04-12  8:44           ` Ookhoi
2003-02-17 17:17     ` James Bourne
2003-02-17 17:34       ` David Woodhouse
2003-02-17 18:14         ` James Bourne
2003-02-18  8:40     ` Henning P. Schmiedehausen

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=20030217183113.GA24922@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=dwmw2@infradead.org \
    --cc=jbourne@mtroyal.ab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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®