[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#796603: keyboard-configuration: Has init script in runlevel S but no matching service file

On 10 October 2015 at 09:54, Felipe Sateler <fsateler@debian.org> wrote:
> On 1 September 2015 at 17:54, Michael Biebl <biebl@debian.org> wrote:
>> Am 01.09.2015 um 19:38 schrieb Felipe Sateler:
>>> On 1 September 2015 at 14:05, Anton Zinoviev <anton@lml.bas.bg> wrote:
>>>> On Thu, Aug 27, 2015 at 03:18:17PM -0300, Felipe Sateler wrote:
>>>>> Does console-setup actually need to be run before user services are
>>>>> started? My guess is that it only needs to run before getty, but it
>>>>> should not block other services that want to start.
>>>> It should run before fsck.
>>> That is definitely not what the init script says[1]:
>>> # Provides:          console-setup
>>> # Required-Start:    $remote_fs
>> Right, the $remote_fs dependency means it's actually started pretty late.
>> I guess what Anton meant was keyboard-setup.
> OK, so I added 2 service files, and preserved the early startup.

On IRC it was pointed out that --save is not necessary under systemd:
/usr must always be mounted. However I decided to preserve it because:

1. I am not 100% sure that /usr is guaranteed to be mounted (the
initrd AFAIK does not handle all cases).
2. On reboot to sysv it would be good to preserve the files in /etc.

If /usr is actually guaranteed to be available, then we should drop
--save from both the init script and service file.


Felipe Sateler

Reply to: