Re: 2.6.37 and other things.
- To: Thorsten Glaser <tg@mirbsd.de>
- Cc: debian-68k@lists.debian.org
- Subject: Re: 2.6.37 and other things.
- From: Finn Thain <fthain@telegraphics.com.au>
- Date: Tue, 1 Mar 2011 13:29:14 +1100 (EST)
- Message-id: <[🔎] alpine.OSX.2.00.1103011323500.406@ibook.intranet>
- In-reply-to: <Pine.BSM.4.64L.1102282241540.14514@herc.mirbsd.org>
- References: <8DF47F15-8FE4-4525-9A13-C222782950B6@googlemail.com> <alpine.OSX.2.00.1102271407310.243@ibook.intranet> <Pine.BSM.4.64L.1102271437300.22253@herc.mirbsd.org> <8E97C70C-AEEB-4D51-A4ED-7312D2078AB0@googlemail.com> <alpine.OSX.2.00.1102281202420.310@ibook.intranet> <Pine.BSM.4.64L.1102280144580.22253@herc.mirbsd.org> <alpine.OSX.2.00.1102281431460.310@ibook.intranet> <AANLkTi=v2Fbi7ALNRFHt=JndjURxuU8Vt5AwZGhUbmX0@mail.gmail.com> <Pine.BSM.4.64L.1102282241540.14514@herc.mirbsd.org>
On Mon, 28 Feb 2011, Thorsten Glaser wrote:
> Geert Uytterhoeven dixit:
>
> > On Mon, Feb 28, 2011 at 04:34, Finn Thain <fthain@telegraphics.com.au>
> > wrote:
> >
> > > It doesn't matter what the clock says if root is read-only.
>
> I think the problem is that the root filesystem is never really
> read-only because the kernel does journal replays and things
> like that
Wow. That sucks rocks through a straw. I wonder if only ext4 has broken
read-only mounts?
Finn
Reply to: