Report post

You have 30 minutes to complete this form before the CAPTCHA will expire.

Security image * Required field

This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="Somebloke"]614[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2">There are areas where it's not configurable because its developers don't think it needs to be, similar to GNOME. The difference is that with GNOME, you can simply choose to use a different desktop environment; with systemd, it's much more difficult to find a good distribution not using it. For that reason, once you've been burned by non-configurable behavior in systemd, you recognize the problem that comes with giving one software project (and its one development team) exclusive control over so many different areas of the system.<br /><br />I've never had a problem with systemd service management, but I've had a major problem with systemd-udevd's lack of configurability (combined with libinput's lack of configurability) making it impossible to load my Logitech wireless touchpad the way I want to. There's no way to use the touchpad without having a dead "palm rejection zone" around the entire perimeter of the device. From what I remember, libinput only allows reading the desired dead zone in from udevd, and udevd hard-codes the dead zone, meaning if I wanted to remove it, I'd have to patch and manually recompile systemd with every minor update, which is enough of an inconvenience that I just don't use the touchpad much.<br /><br />I've seen others have issues configuring systemd-resolved (with or without systemd-networkd), and I've also seen plenty of interesting quirks in the systemd-boot bootloader's behavior. If these components were separated out, it would be feasible for alternatives with easier configuration to exist (see GRUB or rEFInd instead of systemd-boot.) Once people decide a systemd component is "good enough" to use by default, or it becomes too complicated to make an alternative, you can end up with subpar components as the only option available.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color This is a reported post for a post in the topic [post param="Somebloke"]614[/post], by jacobgkau [quote="2"] There are areas where it's not configurable because its developers don't think it needs to be, similar to GNOME. The difference is that with GNOME, you can simply choose to use a different desktop environment; with systemd, it's much more difficult to find a good distribution not using it. For that reason, once you've been burned by non-configurable behavior in systemd, you recognize the problem that comes with giving one software project (and its one development team) exclusive control over so many different areas of the system. I've never had a problem with systemd service management, but I've had a major problem with systemd-udevd's lack of configurability (combined with libinput's lack of configurability) making it impossible to load my Logitech wireless touchpad the way I want to. There's no way to use the touchpad without having a dead "palm rejection zone" around the entire perimeter of the device. From what I remember, libinput only allows reading the desired dead zone in from udevd, and udevd hard-codes the dead zone, meaning if I wanted to remove it, I'd have to patch and manually recompile systemd with every minor update, which is enough of an inconvenience that I just don't use the touchpad much. I've seen others have issues configuring systemd-resolved (with or without systemd-networkd), and I've also seen plenty of interesting quirks in the systemd-boot bootloader's behavior. If these components were separated out, it would be feasible for alternatives with easier configuration to exist (see GRUB or rEFInd instead of systemd-boot.) Once people decide a systemd component is "good enough" to use by default, or it becomes too complicated to make an alternative, you can end up with subpar components as the only option available. [/quote] //// PUT YOUR REPORT BELOW \\\\ View all Use of this website implies that you agree to the website rules and privacy policy.

Security image * Required field

This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param=&quot;Somebloke&quot;]614[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2">There are areas where it&#039;s not configurable because its developers don&#039;t think it needs to be, similar to GNOME. The difference is that with GNOME, you can simply choose to use a different desktop environment; with systemd, it&#039;s much more difficult to find a good distribution not using it. For that reason, once you&#039;ve been burned by non-configurable behavior in systemd, you recognize the problem that comes with giving one software project (and its one development team) exclusive control over so many different areas of the system.<br /><br />I&#039;ve never had a problem with systemd service management, but I&#039;ve had a major problem with systemd-udevd&#039;s lack of configurability (combined with libinput&#039;s lack of configurability) making it impossible to load my Logitech wireless touchpad the way I want to. There&#039;s no way to use the touchpad without having a dead &quot;palm rejection zone&quot; around the entire perimeter of the device. From what I remember, libinput only allows reading the desired dead zone in from udevd, and udevd hard-codes the dead zone, meaning if I wanted to remove it, I&#039;d have to patch and manually recompile systemd with every minor update, which is enough of an inconvenience that I just don&#039;t use the touchpad much.<br /><br />I&#039;ve seen others have issues configuring systemd-resolved (with or without systemd-networkd), and I&#039;ve also seen plenty of interesting quirks in the systemd-boot bootloader&#039;s behavior. If these components were separated out, it would be feasible for alternatives with easier configuration to exist (see GRUB or rEFInd instead of systemd-boot.) Once people decide a systemd component is &quot;good enough&quot; to use by default, or it becomes too complicated to make an alternative, you can end up with subpar components as the only option available.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br />

This is a reported post for a post in the topic [post param="Somebloke"]614[/post], by jacobgkau

[quote="2"]
There are areas where it's not configurable because its developers don't think it needs to be, similar to GNOME. The difference is that with GNOME, you can simply choose to use a different desktop environment; with systemd, it's much more difficult to find a good distribution not using it. For that reason, once you've been burned by non-configurable behavior in systemd, you recognize the problem that comes with giving one software project (and its one development team) exclusive control over so many different areas of the system.

I've never had a problem with systemd service management, but I've had a major problem with systemd-udevd's lack of configurability (combined with libinput's lack of configurability) making it impossible to load my Logitech wireless touchpad the way I want to. There's no way to use the touchpad without having a dead "palm rejection zone" around the entire perimeter of the device. From what I remember, libinput only allows reading the desired dead zone in from udevd, and udevd hard-codes the dead zone, meaning if I wanted to remove it, I'd have to patch and manually recompile systemd with every minor update, which is enough of an inconvenience that I just don't use the touchpad much.

I've seen others have issues configuring systemd-resolved (with or without systemd-networkd), and I've also seen plenty of interesting quirks in the systemd-boot bootloader's behavior. If these components were separated out, it would be feasible for alternatives with easier configuration to exist (see GRUB or rEFInd instead of systemd-boot.) Once people decide a systemd component is "good enough" to use by default, or it becomes too complicated to make an alternative, you can end up with subpar components as the only option available.
[/quote]

//// PUT YOUR REPORT BELOW \\\\

View all