Package: autopkgtest
Version: 4.2
Severity: normal
Ohai,
I wanted to test if my packages work fine with sysvinit instead of systemd.
For that I created a new image (using vmdebootstrap as described in the
manpage),
booted it with plain qemu, installed sysvinit-core and expected it to work.
It didn't :)
1. there is no getty on ttyS0, so autopkgtest cannot control the VM
this is solvable by uncommenting the ttyS0 line in /etc/inittab
and maybe adjusting the speed to something more sensible than 9600
I did not try, but using "agetty --keep-baud 115200,38400,9600 ttyS0 vt220"
might also work nicely (that's what systemd is doing)
2. the VM does not get any network
echo -e "auto ens3\niface ens3 inet dhcp" > /etc/network/interfaces.d/ens3
seems to help, but smells like an awful hack to me.
with systemd networkd just does the right thing here :/
Regards
Evgeni
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages autopkgtest depends on:
ii apt-utils 1.3.1
ii libdpkg-perl 1.18.14
ii procps 2:3.3.12-2
ii python3 3.5.1-4
ii python3-debian 0.1.29
Versions of packages autopkgtest recommends:
ii autodep8 0.8
Versions of packages autopkgtest suggests:
ii lxc 1:2.0.5-3
pn lxd-client <none>
ii qemu-system 1:2.7+dfsg-3+b1
ii qemu-utils 1:2.7+dfsg-3+b1
ii schroot 1.6.10-2+b1
-- no debconf information
