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 8048 invoked from network); 5 May 2022 02:03:39 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 5 May 2022 02:03:39 -0000 Received: from vultr.musolino.id.au ([45.76.123.158]) by 9front; Wed May 4 22:00:06 -0400 2022 Received: from 180.150.112.168 ([180.150.112.168]) by vultr; Thu May 5 11:59:26 +1000 2022 Message-ID: <7046F359DC6A29F1E24602BD744BC722@musolino.id.au> To: 9front@9front.org From: Alex Musolino Date: Thu, 05 May 2022 11:29:25 +0930 In-Reply-To: <67c5f9b0-7152-7c2f-dd4d-e3354f4e9aff@posixcafe.org> 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: webscale replication package-scale layer Subject: Re: [9front] [PATCH] Unmount to remove sharp devices. Reply-To: 9front@9front.org Precedence: bulk > However I want to look a bit more at doing the inverse operation, so > you could say something like "permit #e #| #p" and have it block all > non listed devices in the namespace file. I think that is more > useful to think about and avoids 10 lines of manually selecting > drivers to shoot. Absolutely. Also avoids the problem of new kernel devices being added that then slip through, and the corresponding updates to all existing namespace files. Did you consider implementing this with two commands (e.g. 'drop' and 'permit') on the /dev/drivers file itself? That would make it just as easy to do this kind of stuff from a script/program without having to craft a namespace file. Obviously you'd have to have the #c device available until you're finished "dropping" and "permitting" things, but perhaps that's not really a problem. Just some thoughts. -- Cheers, Alex Musolino