[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MIPS64/N64 support
From: |
Nikita Karetnikov |
Subject: |
Re: MIPS64/N64 support |
Date: |
Tue, 01 Oct 2013 12:55:53 +0400 |
> 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 kernel options
> active. You simply have to avoid using ext4 (or even ext3, I can't recall).
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.
I’ve recently tried to compile several versions of Linux-libre. I used
‘/proc/config.gz’ but changed the mentioned options. Whenever I tried,
I was getting multiple warnings, “a variable is defined but is not used”
or something like that. I can’t remember the last time when I
configured a kernel myself. So I’m not sure whether such warnings are
tolerable or not.
pgp7OR2FNHnaW.pgp
Description: PGP signature
- Re: MIPS64/N64 support, Lluís Batlle i Rossell, 2013/10/01
- Re: MIPS64/N64 support, Nikita Karetnikov, 2013/10/01
- Re: MIPS64/N64 support, Lluís Batlle i Rossell, 2013/10/01
- Re: MIPS64/N64 support,
Nikita Karetnikov <=
- Re: MIPS64/N64 support, Nikita Karetnikov, 2013/10/01
- Re: MIPS64/N64 support, Lluís Batlle i Rossell, 2013/10/01
- Re: MIPS64/N64 support, Nikita Karetnikov, 2013/10/01
- Re: MIPS64/N64 support, Lluís Batlle i Rossell, 2013/10/01
- Re: MIPS64/N64 support, Ludovic Courtès, 2013/10/01
- Re: MIPS64/N64 support, Lluís Batlle i Rossell, 2013/10/01