Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread tlaronde
On Sat, Nov 04, 2023 at 11:59:00AM +0100, Martin Husemann wrote: > On Sat, Nov 04, 2023 at 11:25:01AM +0100, tlaro...@kergis.com wrote: > > I think that my second proposal is the simplest, allowing not breaking > > existing and introducing extensions without much typing. > > This whole thing

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread Martin Husemann
On Sat, Nov 04, 2023 at 11:25:01AM +0100, tlaro...@kergis.com wrote: > I think that my second proposal is the simplest, allowing not breaking > existing and introducing extensions without much typing. This whole thing still makes no sense to me. You can do what you want with userconf already and

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread tlaronde
On Sat, Nov 04, 2023 at 09:30:53AM +, RVP wrote: > On Sat, 4 Nov 2023, tlaro...@kergis.com wrote: > > > > > No...: this is a break of existing. Trailing `*' selects STARred devices > > > > (I'm not the inventor of this). So `*' can not be used as a joker ;-) > > > > > > > > > > You can

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
On Sat, 4 Nov 2023, tlaro...@kergis.com wrote: No...: this is a break of existing. Trailing `*' selects STARred devices (I'm not the inventor of this). So `*' can not be used as a joker ;-) You can allow escapes for those: uc> disable i915drmkms\* # exact match STARred uc> disable

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread tlaronde
On Sat, Nov 04, 2023 at 08:31:09AM +, RVP wrote: > On Sat, 4 Nov 2023, tlaro...@kergis.com wrote: > > > > 1) Allowing shell-like patterns (not hard to implement): > > > > > > uc> disable drm* # all starting with `drm' > > > > No...: this is a break of existing. Trailing `*' selects STARred

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread tlaronde
On Sat, Nov 04, 2023 at 08:20:43AM +, Michael van Elst wrote: > tlaro...@kergis.com writes: > > >disable {drmkms} # NEW: disable devices belonging to group "drmkms" > > Almost noone would need to turn off all drmkms drivers. What you may > want to control is that a GPU isn't used as a

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
On Sat, 4 Nov 2023, tlaro...@kergis.com wrote: 1) Allowing shell-like patterns (not hard to implement): uc> disable drm* # all starting with `drm' No...: this is a break of existing. Trailing `*' selects STARred devices (I'm not the inventor of this). So `*' can not be used as a joker

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread Michael van Elst
tlaro...@kergis.com writes: >disable {drmkms} # NEW: disable devices belonging to group "drmkms" Almost noone would need to turn off all drmkms drivers. What you may want to control is that a GPU isn't used as a console. Disabling a driver is just our crude workaround to achieve this. I

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread Michael van Elst
r...@sdf.org (RVP) writes: >On Sat, 4 Nov 2023, RVP wrote: >> 1) Allowing shell-like patterns (not hard to implement): >> >> uc> disable *drm* *usb$ # all with `drm' anywhere and those ending in >> >Ah, since these are shell-like patterns there's not need for a `$' to >denote EOL. So:

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread tlaronde
On Sat, Nov 04, 2023 at 07:41:19AM +, RVP wrote: > On Sat, 4 Nov 2023, tlaro...@kergis.com wrote: > > > - 1) No change to the general form of current syntax; > > > > - 2) Selection can be as presently: by number (index in cfdata), by > > name (driver name), but also (NEW) by pattern: a

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
On Sat, 4 Nov 2023, RVP wrote: 1) Allowing shell-like patterns (not hard to implement): uc> disable *drm* *usb$ # all with `drm' anywhere and those ending in Ah, since these are shell-like patterns there's not need for a `$' to denote EOL. So: uc> disable *drm* *usb # all

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
On Sat, 4 Nov 2023, tlaro...@kergis.com wrote: - 1) No change to the general form of current syntax; - 2) Selection can be as presently: by number (index in cfdata), by name (driver name), but also (NEW) by pattern: a pattern is between slashes, it is a fix substring, that can be optionnally

[RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread tlaronde
Revised proposition: - 1) No change to the general form of current syntax; - 2) Selection can be as presently: by number (index in cfdata), by name (driver name), but also (NEW) by pattern: a pattern is between slashes, it is a fix substring, that can be optionnally anchored at the beginning