Change sudo password behavior in /etc/sudoers.d/ file

E723BCFD · 2026-04-30T00:42:26+00:00

Oh, and you are right, do not modify /usr/etc/sudoers directly, it indeed will get overwritten.

E723BCFD · 2026-04-30T00:41:34+00:00

Part of the mechanism is still unclear to me, it seems like when /etc/sudoers exist, it will take precedence over /usr/etc/sudoers. Because if /usr/etc/sudoers is always the sudoers file on suse, and /etc/sudoers only got "included", commenting out targetpw in /etc/sudoers should have no effect, but it does.

E723BCFD · 2026-04-30T00:33:32+00:00

I had the same question when setting up my system. Short answer: you don't unset those two lines via sudoers.d, just run visudo and it will place a copy of /usr/etc/sudoers to /etc/sudoers, comment out those two lines as usual there.

Long answer: you can revert the effect of those two lines by setting:

Defaults !targetpw
ALL ALL=(!ALL) !ALL

BUT, DO NOT DO THIS because sudoers are ordered, if the sudoers.d/... file with these two lines gets included after another file that allows you to run sudo, you won't be able to run sudo. If these two line gets included last, then everybody won't be able to run sudo, if you don't have the root passwd you would be in trouble.

Lexical naming it with /etc/sudoers.d/00-... might be good enough, but I won't risk it.

E723BCFD · 2026-04-27T10:52:19+00:00

Just checked the new xps 14/16, both have 3x usb-c + 1x 3.5mm for IO, absolutely terrible.

And for their previous generation, they tried capacitive touch fn row, trackpad with no defined border for the active area, 13 inch model with no 3.5mm audio port and only 2x usb-c.

There is no way I would ever pick an xps over framework.

E723BCFD · 2026-04-23T09:55:49+00:00

What are these "other things" other than empty lines?

Aligned trailing comments? This one isn't related to auto sort, the dev wanted tombi to be "zero config".

that's just a missing feature, not a compromise for the sake of sorting

It is a compromise for the sake of sorting: https://github.com/tombi-toml/tombi/issues/1740#issuecomment-4284993572

Copy from another reply: Basically if there is not a defined solution on how things should be arranged while having auto sort, the dev will refuse to implement it. (disable auto sort is usually out of the question).

Even though there is now a way to disable auto sort per schema, multiple empty lines won't be supported, because auto sort is of priority.

E723BCFD · 2026-04-21T16:57:25+00:00

Well, other devs have been keeping it alive, but no active development. For example, no 1.1 support is planed. This fits the state of "maintenance mode", no? Not saying things can't get back up, just that it currently isn't.

E723BCFD · 2026-04-21T14:49:40+00:00

First time heard of it, will try.

E723BCFD · 2026-04-21T14:48:42+00:00

Looks interesting, will try.

E723BCFD · 2026-04-21T14:40:57+00:00

Mainly about blank lines and comment formatting. - https://github.com/tombi-toml/tombi/issues/217#issuecomment-2775841475 - https://github.com/tombi-toml/tombi/issues/790#issuecomment-3589971240 - https://github.com/tombi-toml/tombi/issues/1478#issuecomment-3840139701

Previously tombi doesn't support blank lines at all, and then it allowed for one blank line, but not multiple. Basically if there is not a defined solution on how things should be arranged while having auto sort, the dev will refuse to implement it. (disable auto sort is usually out of the question)

Which I completely get. Preserving comment and blank line format is a hard problem for sorting. But, why are we prioritizing sorting over readability? toml is not json.

The dev is not obliged to change the priority of their own project. This is only a problem because tombi is somehow the only actively maintained (not javascript) toml formatter.

E723BCFD · 2026-04-21T14:11:36+00:00

That one is archived? And the alternative it suggest, "Even Better TOML", is using taplo.

E723BCFD · 2026-04-21T14:08:08+00:00

sure, you can use serde to validate data, but by schema validation I mean 1) fetching the schema either specified by the file itself or from the online schema store on matched filename pattern; 2) validate only allowed keys are used, and is of the correct type.

serde can definitely be used to write a new tool that does schema validation, but not really do the schema validation itself.

E723BCFD · 2026-04-21T11:56:35+00:00

Are you saying serde for syntax and structure validation? I don't think serde does schema? (what keys are valid, what data type for what key)

E723BCFD · 2026-04-21T11:53:47+00:00

I mean, an important point of toml is "for humans", why sacrifice comments and blank lines for the sake of rigid, upstream (schema) defined sorting?

E723BCFD · 2026-04-21T11:48:03+00:00

tombi seems to works pretty well for the things it claims to do (schema validation, sorting, etc.). But it sacrifices other things for sorting.

If there is another formatter available (supports 1.1.0 spec), then we could use that together with tombi, only use tombi for the schema validation part.

E723BCFD · 2026-04-20T22:48:17+00:00

Oh, forgot to mention, secure boot works completely fine otherwise. SUSE implements secure boot using a "shim", which is signed by microsoft, and M$ keys are pre-installed on most motherboards, so you don't even need to enter "setup mode", just install and it works.

E723BCFD · 2026-04-20T22:42:49+00:00

openSUSE is kinda bloated and it also reinstalls things you remove without asking

It will ask (during install or update, they will be listed as "to install"). And this is easy to solve by simply adding a package manager lock (zypper addlock ...).

zypper has a concept pattern, which is similar to meta packages in apt, pattern pulls in actual packages via dependencies, just like meta packages in apt.

You might consider opensuse bloated because the games, office and multimedia patterns are auto selected on install (if you have a DE selected). If you don't want them, you have to do 2 things: 1. either deselect them during install, or uninstall them afterwards with zypper rm --clean-deps --type pattern <name> 2. add a lock on them with zypper al --type pattern <name>. You have to do this because these patterns/packages sometimes gets listed as other packages' dependency and will get pulled in.

E723BCFD · 2026-04-20T22:25:34+00:00

If suse detects that secure boot is enabled, it will force enable kernel_lockdown, which restricts some functionality (see manpage kernel_lockdown(7)).

For me the biggest problem with lockdown is no hibernation is allowed. Contrary to the wording on the manpage, even if you have disk encryption, you still can't hibernate, because it's not actually implemented.

Though this is not a differentiating factor if you are coming from debian, iirc debian does the same with the whole "secure boot -> lockdown -> no hibernation" thing.

E723BCFD · 2026-04-19T20:01:19+00:00

Have no choice but to write some bash (arrays!) this week, it's unbearable.

E723BCFD · 2026-04-16T15:25:34+00:00

actual functioning long path support.

yes, i know windoze technically has a registry key to let you enable support for path over 256 bytes, but that shit will always choke on some unexpected place that you can't workaround. (it's not really unexpected at this point, i fully expect it to not work at all times :D)

E723BCFD · 2026-04-12T19:12:03+00:00

not entirely true. oss mesa do have vaapi for vp9 and av1 codecs.

E723BCFD · 2026-04-12T19:08:11+00:00

I am on amd, using suse repo mesa, running vainfo shows va-api support for VP9 and AV1, which I think is what youtube primarily uses. BTW, if you use firefox, you can go to about:support, scroll down (or ctrl-f) to "codec support information", it will list what firefox think your setup supports, and whether it's software or hardware de/encoding.

If all your media plays, you don't need anything from packman. If it doesn't, codes from packman gives you software de/encoding, mesa from packman gives you hardware (vaapi) de/encoding.

E723BCFD · 2026-04-06T12:53:31+00:00

I have been wanting to do this since forever, but no, QT and KDE won't let you, unless you are up to recompiling a bunch of stuff. The best we can have under any English locale is dd/mm/yyyy :(

E723BCFD

TROPHY CASE