Talk:SYSLINUX

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

Talk:SYSLINUX

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.

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

  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)

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.