From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: 55/61: gnu: linux-libre: Enable built-in ext4 support. Date: Wed, 21 Aug 2019 16:12:26 -0400 Message-ID: <87zhk22s6y.fsf@netris.org> References: <20190821082439.3206.59786@vcs0.savannah.gnu.org> <20190821082457.B8F8A2111C@vcs0.savannah.gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:59394) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i0Wyf-0005CD-St for guix-devel@gnu.org; Wed, 21 Aug 2019 16:13:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i0Wyf-0006mM-0B for guix-devel@gnu.org; Wed, 21 Aug 2019 16:13:05 -0400 Received: from world.peace.net ([64.112.178.59]:36880) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i0Wyd-0006m0-0o for guix-devel@gnu.org; Wed, 21 Aug 2019 16:13:03 -0400 In-Reply-To: <20190821082457.B8F8A2111C@vcs0.savannah.gnu.org> (guix-commits@gnu.org's message of "Wed, 21 Aug 2019 04:24:57 -0400 (EDT)") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mathieu Othacehe Cc: guix-devel@gnu.org Hi Mathieu, guix-commits@gnu.org writes: > mothacehe pushed a commit to branch wip-cross-system > in repository guix. > > commit 87ea71860614da09153e4c49f7b24294d12689ff > Author: Mathieu Othacehe > Date: Tue Aug 20 16:55:34 2019 +0200 > > gnu: linux-libre: Enable built-in ext4 support. > > When running qemu-img from (gnu system vm) with an aarch64 kernel, mounting > ext4 partitions fails because no modprobe of ext4 module is made. Like for > other kernel configs, provide built-in support for ext4 partitions. > > * gnu/packages/aux-files/linux-libre/5.2-arm64.conf: Enable built-in ext4, > like in intel and armhf configs. I'd prefer to go in the other direction, by changing ext4 to be modular in _all_ configs. Would that work for you? I haven't used ext4 in a long time, and good riddance. There are better filesystems now, that don't leave empty files behind after a crash, among other things. Why give ext4 a privileged position by forcing all users to keep a copy of the ext4 code in their RAM, whether they use it or not? What do you think? Thanks, Mark