From owner-freebsd-questions@freebsd.org Mon Oct 22 14:07:55 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AE3DFFD4E5 for ; Mon, 22 Oct 2018 14:07:55 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF7E07B9FA for ; Mon, 22 Oct 2018 14:07:54 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f169.google.com (mail-lj1-f169.google.com [209.85.208.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 7959E194A7 for ; Mon, 22 Oct 2018 14:07:54 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f169.google.com with SMTP id j17-v6so37147727lja.1 for ; Mon, 22 Oct 2018 07:07:54 -0700 (PDT) X-Gm-Message-State: ABuFfogLjkDlEFWJZ8VXFhaubLtbsq9HNFE78J6ehvcoJgiWVe1vZvr2 epZVlVo20vFvQKFNUv6ebrvx7dIBMGrnfYQalcw= X-Google-Smtp-Source: ACcGV61WwrWpNAoqJH51wFm4o+ZvPsg82mKNR5ZtbCZv4DBWgXs8mDTcdX8hkBoB4qxnkCk90vj8uKl5L41iCEj71v0= X-Received: by 2002:a2e:4751:: with SMTP id u78-v6mr29347504lja.72.1540217272904; Mon, 22 Oct 2018 07:07:52 -0700 (PDT) MIME-Version: 1.0 References: <20181022160457.6f44d232.freebsd@edvax.de> In-Reply-To: <20181022160457.6f44d232.freebsd@edvax.de> From: Kyle Evans Date: Mon, 22 Oct 2018 09:07:40 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: rc.conf(5): comparing kld_list and kldload To: freebsd@edvax.de Cc: grahamperrin@gmail.com, FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2018 14:07:55 -0000 On Mon, Oct 22, 2018 at 9:05 AM Polytropon wrote: > > On Mon, 22 Oct 2018 05:26:18 +0100, Graham Perrin wrote: > > From : > > > > > =E2=80=A6 > > > > > > kld_list (str) A list of kernel modules to load right after > > > the local disks are mounted. Loading modules at > > > this point in the boot process is much faster than > > > doing it via /boot/loader.conf for those modules > > > not necessary for mounting local disk. > > > =E2=80=A6 > > > > Is there ever any benefit to using kldload instead of kld_list? > > It is important when you consider the _time_ during system > startup. Sometimes modules require to be loaded at a certain > time, that's when you can (or cannot) use kld_list, which is > the _default_ method of loading kernel modules. > > early: via /boot/loader.conf > > intermediate: via kld_list in /etc/rc.conf > > almost final: via kldload calls in /etc/rc.local > > It's also possible for scripts in /usr/local/etc/rc.d/ to > load kernel modules, and you could even add something to > /etc/rc itself to achieve "really final" loading (even though > manual additions to /etc/rc are discouraged for good reasons). > It's worth noting that /boot/loader.conf is not an option for drm modules in head and stable/12, so only the above "intermediate" and "almost final" options are suitable for testing here. Thanks, Kyle Evans