Mailing List Archive

John Willis wrote:
> Ferenc,
>
> Any chance you could make DHCP CHADDR available in your macro patch?
>
> It would solve a lot of problems for a lot of people I think.
>
> I'm trying to do it, but its going to take me a while to figure out how to
> checkout the git source code, apply your patch, and perhaps create a
> renderer for 00:xx:xx:xx:xx ect.. format.
>

That would be a bad format to use, because it assumes Ethernet.
PXELINUX uses 01-xx-xx-xx-xx-xx-xx for Ethernet addresses, since 01 is
the ARP/DHCP media type for Ethernet. The use of dashes rather than the
more commonly used colons is because colons are special in many
filesystems, and dashes is actually the official form as used by the
IEEE. In a Unix environment it's easy enough to convert forms.

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

"H. Peter Anvin" <hpa@zytor.com> writes:

> John Willis wrote:
>
>> Any chance you could make DHCP CHADDR available in your macro patch?
>> It would solve a lot of problems for a lot of people I think.

No problem with that. Although somebody has already offered sending
me such additions, they just never reached me. But I'll implement it
myself, it's just a couple of lines.

>> [...] create a renderer for 00:xx:xx:xx:xx ect.. format.
>
> That would be a bad format to use, because it assumes Ethernet.
> PXELINUX uses 01-xx-xx-xx-xx-xx-xx for Ethernet addresses, since 01 is
> the ARP/DHCP media type for Ethernet. The use of dashes rather than the
> more commonly used colons is because colons are special in many
> filesystems, and dashes is actually the official form as used by the
> IEEE. In a Unix environment it's easy enough to convert forms.

Maybe not quite so in the pre-boot environment. What if I added an
Ethernet specific and a general keyword to please more or less
everybody while also elevating my codig pleasure? :)
--
Cheers,
Feri.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Ferenc Wagner wrote:
>>> [...] create a renderer for 00:xx:xx:xx:xx ect.. format.
>> That would be a bad format to use, because it assumes Ethernet.
>> PXELINUX uses 01-xx-xx-xx-xx-xx-xx for Ethernet addresses, since 01 is
>> the ARP/DHCP media type for Ethernet. The use of dashes rather than the
>> more commonly used colons is because colons are special in many
>> filesystems, and dashes is actually the official form as used by the
>> IEEE. In a Unix environment it's easy enough to convert forms.
>
> Maybe not quite so in the pre-boot environment. What if I added an
> Ethernet specific and a general keyword to please more or less
> everybody while also elevating my codig pleasure? :)

That would be hideous. Pretty much a guaranteed way to make sure only
Ethernet ever works.

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

"H. Peter Anvin" <hpa@zytor.com> writes:

> Ferenc Wagner wrote:
>
>>>> [...] create a renderer for 00:xx:xx:xx:xx ect.. format.
>>>
>>> That would be a bad format to use, because it assumes Ethernet.
>>> PXELINUX uses 01-xx-xx-xx-xx-xx-xx for Ethernet addresses, since 01 is
>>> the ARP/DHCP media type for Ethernet. The use of dashes rather than the
>>> more commonly used colons is because colons are special in many
>>> filesystems, and dashes is actually the official form as used by the
>>> IEEE. In a Unix environment it's easy enough to convert forms.
>>
>> Maybe not quite so in the pre-boot environment. What if I added an
>> Ethernet specific and a general keyword to please more or less
>> everybody while also elevating my codig pleasure? :)
>
> That would be hideous. Pretty much a guaranteed way to make sure only
> Ethernet ever works.

I don't follow you. Do you mean everybody will use the Ethernet
specific keyword (MAC or EHA?) only, and "experience problems" after
migrating his/her network infrastructure to FDDI? Don't you think the
same would happen with homebrewn throwaway conversion functions? And
I think Ethernet is what people use most; if somebody doesn't, s/he
starts with the general CHADDR macro anyway. Am I talking rubbish?

(I truly appreciate that you care to enter this discussion, even though
you're not in favor of its basis.)
--
Regards,
Feri.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Hi,

with the intent to encourage further discussion, find attached an
extended version of the patch against syslinux-3.52-pre7; apply with
-p1 from the root of the syslinux tree. It introduces two new macros,
CHADDR for PXELINUX type hardware addresses and EHW for Ethernet
hardware addresses. An incremental patch is also attached for the
interested. Comments welcome.
--
Cheers,
Feri.