Nicolas Braud-Santoni writes ("Re: Bug#899299: libu2f-udev: Post-inst script
should make udev reload rules"):
> On Sun, Jun 03, 2018 at 06:20:03PM +0100, James Cowgill wrote:
> > Running a command from another package in postinst only requires a
> > normal Depends - not a
On Jun 04, Philipp Kern wrote:
> Is this synchronous, or does one also need a call to "udevadm settle"? I
> had a problem with kpartx where the loop devices were not available
> after the package was installed, likely because of a race. I wonder if a
Yes, events in udev are asynchronous no
On 6/3/18 7:20 PM, James Cowgill wrote:
> This can be done by running "udevadm trigger". By default every device
> on the system will be triggered which is a bit heavyweight, so you
> probably want to add some *match parameters to restrict this to the
> devices you're interested in (see the
Hi James,
On Sun, Jun 03, 2018 at 06:20:03PM +0100, James Cowgill wrote:
> Hi,
>
> On 03/06/18 16:08, Nicolas Braud-Santoni wrote:
> > X-Debbugs-CC: debian-devel@lists.debian.org
> >
> > Hi Debianites !
> >
> > On Tue, May 22, 2018 at 10:23:33AM +0200, Nicolas Braud-Santoni wrote:
> >>
Hi,
On 03/06/18 16:08, Nicolas Braud-Santoni wrote:
> X-Debbugs-CC: debian-devel@lists.debian.org
>
> Hi Debianites !
>
> On Tue, May 22, 2018 at 10:23:33AM +0200, Nicolas Braud-Santoni wrote:
>> [libu2f-udev's post-inst script should make udev reload rules.]
>> Otherwise, the rules are not
X-Debbugs-CC: debian-devel@lists.debian.org
Hi Debianites !
On Tue, May 22, 2018 at 10:23:33AM +0200, Nicolas Braud-Santoni wrote:
> [libu2f-udev's post-inst script should make udev reload rules.]
> Otherwise, the rules are not active until the next reboot (or until the user
> manually calls
6 matches
Mail list logo
