From: Viktor VM Mihajlovski <mihajlov@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org
Cc: Collin Walling <walling@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v1 for-2.13 3/4] pc-bios/s390-ccw/net: Add support for pxelinux-style config files
Date: Fri, 20 Apr 2018 09:54:28 +0200 [thread overview]
Message-ID: <ca20b91c-e92f-e539-590b-fcaa229a57d5@linux.vnet.ibm.com> (raw)
In-Reply-To: <a001b146-7091-63e6-a845-e276494cc518@redhat.com>
On 20.04.2018 09:36, Thomas Huth wrote:
> On 20.04.2018 08:53, Viktor VM Mihajlovski wrote:
>> On 19.04.2018 18:55, Thomas Huth wrote:
[...]
>> Well, if we don't add another identifier, and I feel reluctant about it
>> as well for the reasons you wrote, we may stick with 0x1f and consider
>> the additional capabilities as being optional (for special needs only).
>
> I tend to stay with 0x1f, since booting binaries is still the "primary"
> interface (the first check for the "default" or "# " magic keywords is
> not 100% reliable, since the config file could also start with another
> command, and the probing of pxelinux.cfg/* files is only tried afterwards).
>
Good. It would be important though to define and document the best way
to configure a pxelinux setup: empty bootfile name, bootfile empty (or
not existent) or a special file format for the bootfile content (like
'PXE0' in EBCDIC). The former two carry the danger of accidentally
enabling the pxe-style boot process.
> Thomas
>
--
Regards,
Viktor Mihajlovski
next prev parent reply other threads:[~2018-04-20 7:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 12:31 [Qemu-devel] [PATCH v1 for-2.13 0/4] pc-bios/s390-ccw: Network boot improvements Thomas Huth
2018-04-18 12:31 ` [Qemu-devel] [PATCH v1 for-2.13 1/4] pc-bios/s390-ccw/net: Split up net_load() into init, load and uninit parts Thomas Huth
2018-04-18 18:11 ` Farhan Ali
2018-04-19 5:20 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-04-18 12:31 ` [Qemu-devel] [PATCH v1 for-2.13 2/4] pc-bios/s390-ccw/net: Stop virtio-net device before jumping into the OS Thomas Huth
2018-04-19 15:49 ` Christian Borntraeger
2018-04-20 6:31 ` Thomas Huth
2018-04-20 7:25 ` Christian Borntraeger
2018-04-18 12:31 ` [Qemu-devel] [PATCH v1 for-2.13 3/4] pc-bios/s390-ccw/net: Add support for pxelinux-style config files Thomas Huth
2018-04-19 7:41 ` Viktor VM Mihajlovski
2018-04-19 8:17 ` Thomas Huth
2018-04-19 12:40 ` Viktor VM Mihajlovski
2018-04-19 16:55 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-04-20 6:53 ` Viktor VM Mihajlovski
2018-04-20 7:36 ` Thomas Huth
2018-04-20 7:54 ` Viktor VM Mihajlovski [this message]
2018-04-20 8:40 ` Thomas Huth
2018-04-20 12:11 ` Viktor VM Mihajlovski
2018-04-18 12:31 ` [Qemu-devel] [PATCH v1 for-2.13 4/4] pc-bios/s390-ccw/net: Add support for .INS " Thomas Huth
2018-04-19 8:02 ` Viktor VM Mihajlovski
2018-04-19 8:20 ` Thomas Huth
2018-04-18 18:21 ` [Qemu-devel] [PATCH v1 for-2.13 0/4] pc-bios/s390-ccw: Network boot improvements Farhan Ali
2018-04-19 5:27 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-04-19 12:03 ` Farhan Ali
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca20b91c-e92f-e539-590b-fcaa229a57d5@linux.vnet.ibm.com \
--to=mihajlov@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).