Bug#838480: Next revision, suggestion accounted

Martin Pitt mpitt at debian.org
Fri Nov 16 17:55:48 GMT 2018


Hello Dmitry,

Dmitry Bogatov [2016-10-20 13:33 +0300]:
> runit_2.1.2-9 in testing, and it:
> 
>  - Depends on getty-run, which means that user end up without tty

Not sure what "getty-run" is, but indeed I don't get a TTY. But I don't even
get that far. This is my current experience:

 * Standard vmdebootstrap install of sid.
 * Install runit-init, "do as I say!", reboot (that works)
 * Boot does that:

| - runit: $Id: 25da3b86f7bed4038b8a039d2f8e8c9bbcf0822b $: booting.
| - runit: enter stage: /etc/runit/1
| [ ok ] Starting hotplug events dispatcher: systemd-udevd.
| [....] Synthesizing the initial hotplug events...[    1.808644] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
| [    1.833381] parport_pc 00:04: reported by Plug and Play ACPI
| [    1.835655] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
| [    1.840339] ACPI: Power Button [PWRF]
| [    1.850222] systemd-udevd[375]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
| [    1.861449] sr 1:0:0:0: Attached scsi generic sg0 type 5
| [    1.872548] input: PC Speaker as /devices/platform/pcspkr/input/input5
| [    1.875268] 9pnet: Installing 9P2000 support
| [ ok [    1.927861] [drm] Found bochs VGA, ID 0xb0c0.
| [    1.929126] [drm] Framebuffer size 16384 kB @ 0xfd000000, mmio @ 0xfebd0000.
| [    1.938009] systemd-udevd[376]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
| done.
| [    1.961434] [TTM] Zone  kernel: Available graphics memory: 1022516 kiB
| [    1.963260] [TTM] Initializing pool allocator
| [    1.979965] [TTM] Initializing DMA pool allocator
| [....] Waiting for /dev to be fully populated...[    1.994500] ppdev: user-space parallel port driver
| [    2.009204] fbcon: bochsdrmfb (fb0) is primary device
| [    2.012962] Console: switching to colour frame buffer device 128x48
| [    2.024111] bochs-drm 0000:00:02.0: fb0: bochsdrmfb frame buffer device
| [    2.025381] [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:02.0 on minor 0
| done.
| [ ok ] Activating swap...done.
| [    2.552988] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
| [warn] Creating compatibility symlink from /etc/mtab to /proc/mounts. ... (warning).
| [ ok ] Activating lvm and md swap...done.
| [....] Checking file systems...fsck from util-linux 2.32.1
| done.
| [ ok ] Cleaning up temporary files... /tmp.
| [ ok ] Mounting local filesystems...done.
| [ ok ] Activating swapfile swap...done.
| [ ok ] Cleaning up temporary files....
| [ ok ] Starting Setting kernel variables: sysctl.
| [    2.863970] random: dd: uninitialized urandom read (512 bytes read)
| [ ok ] Configuring network interfaces...done.
| [ ok ] Cleaning up temporary files....
| [ ok ] Starting enhanced syslogd: rsyslogd.
| [ ok ] Starting ACPI services: acpid.
| [ ok ] Starting periodic command scheduler: cron.
| [....] Starting system message bus: dbus[    3.012871] random: dbus-daemon: uninitialized urandom read (12 bytes read)
| [    3.017986] random: dbus-daemon: uninitialized urandom read (12 bytes read)

  and hangs for 90s. Then it gets a tiny bit further:

| . ok 
| [   93.081316] audit: type=1400 audit(1542390391.612:3): apparmor="DENIED" operation="mknod" profile="/usr/sbin/haveged" name="/run/hav0
| [ ok ] Starting SMP IRQ Balancer: irqbalance.
| [....] Starting OpenBSD Secure Shell server: sshd

And from here on, nothing. I can't log in through sshd, and there's no VT
either.

Admittedly I didn't do any RTFM, but IMHO this isn't a very friendly default
behaviour. You get locked out of your machine completely, only grub and init=
come to the rescue.

>  - Provides `shutdown' and `reboot' scripts, which were tested via
>    'fbpanel' buttons. Works correctly.

That does work now, at least immediately after installation. (Can't test on an
actual runit system). So, progress!

> Is there anything else needed for inclusion into init's pre-depends?

I wouldn't veto it, as the actual functionality for runit is not the
responsibility of the "init" metapackage. But I strongly recommend providing an
OOTB experience that gets a working system, before adding it as a pre-depends.
You should also ensure that this stays so by creating an autopkgtest that
installs runit, reboots, and makes sure that at least ssh and getty come up,
and runlevel is 2 (or 3, i. e. not S). This will ensure that this works on a
standard system, cover other architectures, and also prevent future
regressions.

Thank you!

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181116/57a35e00/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list