public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] X11 without udev/eudev
Date: Sun, 22 Aug 2021 16:59:07 -0500	[thread overview]
Message-ID: <CADPrc82We9SwMbRoZ3iYRGkwdkf9rigvEQHv5Xxy0wK8ooy2EQ@mail.gmail.com> (raw)
In-Reply-To: <20210822203110.5C6BB8517F53@turkos.aspodata.se>

[-- Attachment #1: Type: text/plain, Size: 1802 bytes --]

On Sun, Aug 22, 2021 at 3:32 PM <karl@aspodata.se> wrote:
[...]

> I'll be looking into that, but on some level, why should I be forced to
> go around udev. Can't programs be compiled without udev today...
>

Yes, they can, if you (or someone else) write the necessary code, debug it,
maintain it and keep it up to date and fix vulnerabilities and other errors
that inevitably will appear, as it does with every piece of software.


> Udev should be an optional deamon, utilized when the local administrator
> decides to do so.


Wrong: the use of udev is to be decided by the developers of the code that
uses it. If you don't like it, then you write your own. The code is free
and open.

Udev solves a very real problem, because most modern PCs have dynamic
hardware; we connect and disconnect multiple devices from it all the time,
and the vast majority of users prefer it when it simply works
automagically. Moreover, it *also* works with static hardware, so it hits
two birds with one stone.

You want developers to write code that only benefits the simplest and most
boring case: a PC that never changes hardware. Any sane developer will
obviously prefer to depend on udev, which solves every case and it has the
most users (and therefore feedback for detecting and correcting bugs, and
also to ask for new features and capabilities).


> I don't want things to automatically pop up unless I say so.
>

Then write yourself the corresponding software, or pay someone to do it.
Otherwise, complaining (while cathartic and the preferred hobby of most of
the internet) is completely useless.

Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México

[-- Attachment #2: Type: text/html, Size: 2664 bytes --]

  reply	other threads:[~2021-08-22 21:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-21 20:17 [gentoo-user] X11 without udev/eudev karl
2021-08-21 21:02 ` antlists
2021-08-21 22:34   ` karl
2021-08-21 21:05 ` Anna “CyberTailor”
2021-08-22 20:31   ` karl
2021-08-22 21:59     ` Canek Peláez Valdés [this message]
2021-08-22 23:18       ` antlists
2021-08-22 23:30         ` Rich Freeman
2021-08-22 23:37         ` Canek Peláez Valdés
2021-08-23 16:07           ` karl
2021-08-23 17:01             ` karl
2021-08-23 19:51             ` Canek Peláez Valdés
2021-08-23 22:36               ` karl
2021-08-23 16:14           ` Vitor Hugo Nunes dos Santos
2021-08-21 21:51 ` Vitor Hugo Nunes dos Santos
2021-08-21 22:34   ` karl
2021-08-21 22:45     ` Neil Bothwick
2021-08-22 11:01       ` Mart Raudsepp
2021-08-22 20:31         ` karl
2021-08-22 20:31       ` karl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADPrc82We9SwMbRoZ3iYRGkwdkf9rigvEQHv5Xxy0wK8ooy2EQ@mail.gmail.com \
    --to=caneko@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox