From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?iso-8859-1?Q?Llu=EDs?= Batlle i Rossell <viric@viric.name>
Subject: Re: MIPS64/N64 support
Date: Tue, 1 Oct 2013 11:30:09 +0200
Message-ID: <20131001093009.GX1965@vicerveza.homeunix.net>
References: <878uyfiwr1.fsf@karetnikov.org> <87siwniwka.fsf@gnu.org>
	<8738onkyi9.fsf@karetnikov.org> <87bo3asfx6.fsf@karetnikov.org>
	<87fvsmgtsm.fsf@gnu.org> <87mwmuhtb3.fsf@karetnikov.org>
	<20131001070942.GV1965@vicerveza.homeunix.net>
	<87li2dv3bz.fsf@karetnikov.org>
	<20131001080318.GW1965@vicerveza.homeunix.net>
	<87ob79e5eu.fsf@karetnikov.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41929)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <viric@viric.name>) id 1VQwHe-0007YB-6b
	for guix-devel@gnu.org; Tue, 01 Oct 2013 05:30:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <viric@viric.name>) id 1VQwHV-00042E-G0
	for guix-devel@gnu.org; Tue, 01 Oct 2013 05:30:22 -0400
Content-Disposition: inline
In-Reply-To: <87ob79e5eu.fsf@karetnikov.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org

On Tue, Oct 01, 2013 at 12:55:53PM +0400, Nikita Karetnikov wrote:
> > In fact I was reluctant to raise again the ext4 topic ;) But I think =
3.5.3 has a
> > broken readdir() syscall in ext4. I think it's not a problem of kerne=
l options
> > active. You simply have to avoid using ext4 (or even ext3, I can't re=
call).
>=20
> In the past, I was using EXT3 with CONFIG_EXT4_USE_FOR_EXT23, and there
> were problems with OOM Killer.  That was fixed by switching to
> CONFIG_EXT3_FS.
>=20
> I=E2=80=99ve recently tried to compile several versions of Linux-libre.=
  I used
> =E2=80=98/proc/config.gz=E2=80=99 but changed the mentioned options.  W=
henever I tried,
> I was getting multiple warnings, =E2=80=9Ca variable is defined but is =
not used=E2=80=9D
> or something like that.  I can=E2=80=99t remember the last time when I
> configured a kernel myself.  So I=E2=80=99m not sure whether such warni=
ngs are
> tolerable or not.

AH, ok. I have no idea. I also seem to recall that gNewSense had only o32
support, years ago. And not any n32/n64. Can it be?

I'd simply try to avoid ext4 or even ext3, without changing the kernel. I=
 don't
know of linux-libre, but you need something newer than 3.7 I think, to ge=
t the
ext* fix.