pmbootstrap/pmb
Minecrell 81b3aade07
pmb.qemu: drop telnet port forwarding (!1886)
Now that we try to use the IP assigned by QEMU via DHCP,
the debug-shell is no longer working via telnet.
This is because the VM does not have any IP assigned when it is running.

We would need to start a DHCP client from the initfs to make it work.
busybox provides both udhcpc (client) and udhcpd (server) so this is
not a big problem. But the question is: Is it worth it?

The debug-shell will be only used for debugging, and NetworkManager
handles starting a proper DHCP client once the rootfs is mounted.
Meanwhile the debug-shell can be also accessed via serial output/input,
(available in the pmbootstrap stdout/stdin). So overall it does not
seem worth the effort. Let's just recommend using serial instead.
2020-03-14 08:05:32 +01:00
..
aportgen pmb: replace deviceinfo_date with deviceinfo_year, add to wizard (!1888) 2020-03-14 00:33:22 +01:00
build pmb.build._package: fix erroneous if condition (!1889) 2020-03-08 19:22:12 +01:00
chroot pmb.config.workdir: save/check chroot init date (!1878) 2020-02-24 18:18:38 +01:00
config pmb.qemu: remove QEMU mesa driver setup question (!1886) 2020-03-14 08:05:32 +01:00
data pmb/data/keys/pmos-5a03a13a.rsa.pub: remove (!1835) 2019-11-21 23:52:25 +01:00
export Cosmetic: use SPDX license header (!1877) 2020-02-24 03:11:10 +03:00
flasher Cosmetic: use SPDX license header (!1877) 2020-02-24 03:11:10 +03:00
helpers pmb/helpers/pmaports: fix finding subpackages (!1890) 2020-03-09 18:49:59 +01:00
install pmb.qemu: remove QEMU mesa driver setup question (!1886) 2020-03-14 08:05:32 +01:00
parse pmb.qemu: use current device instead of requiring --arch (!1886) 2020-03-14 08:05:32 +01:00
qemu pmb.qemu: drop telnet port forwarding (!1886) 2020-03-14 08:05:32 +01:00
__init__.py Cosmetic: use SPDX license header (!1877) 2020-02-24 03:11:10 +03:00