Bug#825931: s390-netdevice virtio interface choice misleading

2016-10-27 Thread Hendrik Brueckner
On Wed, Oct 26, 2016 at 10:53:36PM +0200, Philipp Kern wrote: > On 10/26/2016 05:13 PM, Dimitri John Ledkov wrote: > > Currently s390-netdevice in the code supports following networktypes: > > * qeth > > * ctc > > * iucv > > * virtio > > > > virtio is, in fact, a no-op. > > Yup. > > > iucv

Bug#825931: s390-netdevice virtio interface choice misleading

2016-10-27 Thread Viktor Mihajlovski
On 26.10.2016 22:53, Philipp Kern wrote: > On 10/26/2016 05:13 PM, Dimitri John Ledkov wrote: >> Currently s390-netdevice in the code supports following >> networktypes: * qeth * ctc * iucv * virtio >> >> virtio is, in fact, a no-op. > > Yup. > >> iucv refers to "IUCV network device" which has

Bug#825931: s390-netdevice virtio interface choice misleading

2016-10-26 Thread Philipp Kern
On 10/26/2016 05:13 PM, Dimitri John Ledkov wrote: > Currently s390-netdevice in the code supports following networktypes: > * qeth > * ctc > * iucv > * virtio > > virtio is, in fact, a no-op. Yup. > iucv refers to "IUCV network device" which has been deprecated at > least since October 2005

Bug#825931: s390-netdevice virtio interface choice misleading

2016-10-26 Thread Dimitri John Ledkov
On 23 October 2016 at 22:57, Philipp Kern wrote: > Hi, > > On 05/31/2016 09:01 PM, Dimitri John Ledkov wrote: >> I find logic in s390-netdevice. The priority of many questions is too >> high, thus e.g. if one uses qeth port 0, one has to explicitely >> preseed that, even though

Bug#825931: s390-netdevice virtio interface choice misleading

2016-10-23 Thread Philipp Kern
Hi, On 05/31/2016 09:01 PM, Dimitri John Ledkov wrote: > I find logic in s390-netdevice. The priority of many questions is too > high, thus e.g. if one uses qeth port 0, one has to explicitely > preseed that, even though a common case qeth port 0 will work in > majority (sensible default) cases.

Bug#825931: s390-netdevice virtio interface choice misleading

2016-06-25 Thread Viktor Mihajlovski
On 19.06.2016 13:34, Philipp Kern wrote: > Is such a thing even possible? > > If not could we simply skip that prompt if we see a regular one because then > we > know it's VirtIO/PCI/other? > > Kind regards and thanks > Philipp Kern > we can definitely have the situation that both an channel

Bug#825931: s390-netdevice virtio interface choice misleading

2016-06-19 Thread Philipp Kern
Hi Viktor, On Tue, May 31, 2016 at 04:14:39PM +0200, Viktor Mihajlovski wrote: > if an installation is attempted on a system with a PCI network interface > only, it is necessary to select virtio as network interface to continue > with the installation. This works because the virtio choice is >

Bug#825931: s390-netdevice virtio interface choice misleading

2016-05-31 Thread Viktor Mihajlovski
Package: s390-netdevice Version: 0.0.44 Severity: normal Tags: d-i patch X-Debbugs-CC: debian-s...@lists.debian.org, brueck...@linux.vnet.ibm.com Dear Maintainer, if an installation is attempted on a system with a PCI network interface only, it is necessary to select virtio as network interface