Talk:SYSLINUX

This article was nominated for deletion on 27 July 2021. The result of the discussion was no consensus.

This is the talk page for discussing improvements to the SYSLINUX article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Computing: Software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software.

Linux Low‑importance

	Linux portal This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LinuxWikipedia:WikiProject LinuxTemplate:WikiProject LinuxLinux articles
Low	This article has been rated as Low-importance on the project's importance scale.

Unnamed section

how does Syslinux relate to isolinux? This article starts talking about isolinux without explanation. The wiki isolinux is redirected to syslinux!

Ditto, I have the exact same issue! I don't know what Isolinux is, and this doesn't help to differentiate it for me.

OK, I've just spent a bit of time on this article, so hopefully the confusion between ISOLINUX and SYSLINUX is sorted now. I don't know so much about PXE booting though, so please chip in if you have anything to add. --Gypsum Fantastic 01:11, 13 Oct 2004 (UTC)

I've added my two cents regarding PXELINUX- should be reasonably accurate (I use it a fair bit, but don't know a lot about PXE internals). Other things:

I'm wondering if it'd be worthwhile to break this into sections, one each for an overview, then SYS, ISO, and PXE
How technical should this be? Should I add more specifics WRT PXELINUX implementation?
How to incorporate the Wikipedia entry regarding booting
AFAIK, this is specific to booting x86 boxes, probably worthy of mention

--Atombaby Nov 4, 2004

Debian description may be a good 3rd party reference of this subject.

http://packages.debian.org/sid/syslinux
http://packages.debian.org/search?searchon=sourcenames&keywords=syslinux
http://packages.qa.debian.org/s/syslinux.html —Preceding unsigned comment added by 119.105.244.3 (talk) 09:24, 19 October 2008 (UTC)[reply]

Syslinux vs its components...

I just made an official post on this subject, this may be interesting to people: [1]. Hpa (talk) 19:16, 27 October 2008 (UTC)[reply]

MBR bootloader

Which of the mentionend boot loaders is really a MBR bootloader ? The article suggests all of them, but I don't believe that. -- Juergen 91.52.168.28 (talk) 11:26, 4 May 2012 (UTC)[reply]

UDP/IP

Just a minor comment regarding section PXELINUX:

“The PXE environment uses DHCP or BOOTP to enable basic TCP/IP networking, then downloads a bootstrap program via TFTP.”

TCP is not used in PXE^[1]; or BOOTP^[2] or TFTP^[3]; it might be implemented by the bootstrap program, but this is not the case for PXELINUX. Whether the operating system uses TCP, is outside the scope of PXELINUX. So, for clarity, “basic TCP/IP networking” should be “minimalistic UDP/IP networking”. – Kenneyw (talk) 23:01, 6 February 2015 (UTC)[reply]

Hello! Nice catch, went ahead and cleaned up the SYSLINUX § PXELINUX section, expanding it a bit further at the same time – please check it out. — Dsimic (talk | contribs) 23:37, 11 February 2015 (UTC)[reply]

References

^ PXE ¶3: “This distinctive firmware layer makes available at the client the functions of a basic Universal Network Driver Interface (UNDI), a minimalistic UDP/IP stack, a Preboot (DHCP) client module and a TFTP client module, together forming the PXE application programming interfaces”
^ "RFC951 (BOOTP)". See section 2, Overview: “This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed.”
^ (TFTP) See section "1. Purpose: TFTP ... has been implemented on top of the Internet User Datagram protocol (UDP or Datagram)

[1] PXE ¶3: “This distinctive firmware layer makes available at the client the functions of a basic Universal Network Driver Interface (UNDI), a minimalistic UDP/IP stack, a Preboot (DHCP) client module and a TFTP client module, together forming the PXE application programming interfaces”

[2] "RFC951 (BOOTP)". See section 2, Overview: “This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed.”

[3] (TFTP) See section "1. Purpose: TFTP ... has been implemented on top of the Internet User Datagram protocol (UDP or Datagram)

[1]

[2]

[3]