All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] tvheadend: add dependency on udev
Date: Sat, 6 Jan 2018 15:25:16 +0100	[thread overview]
Message-ID: <20180106152516.1990634f@windsurf> (raw)
In-Reply-To: <trinity-2bd270b3-d02a-4175-80f4-6eb5beb56345-1515245465268@3c-app-mailcom-bs02>

Hello,

On Sat, 6 Jan 2018 14:31:05 +0100, daggs wrote:

> > And personal experience has shown that my setup was working OK without
> > udev as well, at a time _after_ those two commits.
> > 
> > So I still believe we should not add a dependency on udev at all,
> > because as far as I understand, you claim it is only needed for USB
> > devices. Other devices seem to be working fine without udev, and it
> > is perfectly valid to have a setup with a non-USB device and no udev.  
> 
> I'm happy that it worked out of the box for you but fact to the matter, it didn't for me.
> it took me three weekends to figure it out. imho, the fact that it works on one scenario doesn't means there isn't a bug.

Yes, but we can't force a dependency on all users without understanding
if this dependency is really needed.

Could you try to understand *why* udev makes it work for you?

One guess is that udev has some rules that makes your USB capture
device accessible to non-root users. And since tvheadend runs as its
own user, this might explain it.

Could you have a look into this ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2018-01-06 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05  9:35 [Buildroot] [PATCH v2] tvheadend: add dependency on udev Dagg Stompler
2018-01-05 22:54 ` Yann E. MORIN
2018-01-06 13:31   ` daggs
2018-01-06 14:25     ` Thomas Petazzoni [this message]
2018-01-11  7:14   ` Bernd Kuhls
2018-01-13 16:02     ` daggs
2018-01-13 22:22       ` Bernd Kuhls
2018-01-19 12:45         ` daggs

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=20180106152516.1990634f@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.