[2019-01-11 14:34] KatolaZ <kato...@freaknet.org> > On Fri, Jan 11, 2019 at 12:36:36PM +0000, Dmitry Bogatov wrote: > > > > [2019-01-08 14:32] Michael Biebl <bi...@debian.org> > > > Am 08.01.19 um 13:37 schrieb Dmitry Bogatov: > > > > > > > > control: tags -1 +moreinfo > > > > > > > > Seems old discussion did not ended in solution. Let us try again. > > > > > > > > Dear udev maintainers, did anything changed? Are there still problems > > > > running /etc/init.d/udev from runlevel 1 (when udev daemon was killed) > > > > manually by sysadmin to restart it? > > > > > > > > > > That's not what this bug report is about. > > > > > > It's about udev being killed when switching to runlevel 1 and not being > > > restarted automatically when switching back to say runlevel 2. > > > > > > That issue is still valid today. > > > > I understand. Perfect solution would be move udev script (or part, that > > actually starts process/es) to stages (2 3 4 5)? Is it feasible today? > > > > I don't think it is possible, since udev gets started in early boot, > before filesystems are mounted, but I might be wrong.
Yes, I see, that `mountdefsubsys', `procps' and number of other declare soft dependency (Should-Start:) on udev. Any idea, where can I find reasoning, why it is so?