From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14424 invoked from network); 29 Mar 2021 13:47:50 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 29 Mar 2021 13:47:50 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Mon Mar 29 09:42:25 -0400 2021 Message-ID: Date: Mon, 29 Mar 2021 15:42:13 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <50840a80-ccc0-41e4-b55d-eb7156af7e6f@www.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: package hosting Subject: Re: [9front] devfs config file loading Reply-To: 9front@9front.org Precedence: bulk > should the devfs config file be loaded by bootrc instead of the driver? yes, that makes sense. tho that should already be happening? boorc runs nusbrc first, then runs configlocal(), which calls diskparts, which after having parsed all partition tables of all the disks (/dev/sd*), it will execute this line: # set up any fs(3) partitions if (! test -e /dev/fs/ctl && test -e '#k/fs') bind -b '#k' /dev the fs configuration is read at walk time (rdconf() called from mwalk()) so the line above should trigger the fs configuration load. at at this time, all the usb devices (and their partitions) should have been enumerated? you can try setting the debug variable in devfs.c and add debug print to diskparts script and see if that is correct. there might be some place where we accidentally trigger a config load before usb is enumerated? -- cinap