paperlined.org
apps > slax > PXE_booting

document updated 14 years ago, on Feb 28, 2010

Intro:

the way that SLAX boots PXE is that it gets its large files (*.lzm) by mounting them using FUSE+httpfs (i.e. it downloads them from a website)
the stock SLAX files (at least as of v6.1.2, but possibly much earlier) contains all the httpfs drivers needed to boot properly

suggested technical reasons that Apache, IIS, and other web servers don't interoperate with HTTPFS:
- [Thomas M] httpfs doesn't handle transfer-encoding:chunked properly
  - [Thomas M] chunked encoding is only a problem when content-length: is missing
- httpfs doesn't handle 301 redirects properly, but Apache sends a 301 redirect when you leave off the final slash in a directory URL
web servers that DO work stock with httpfs
- monkeyd
  - yes, works great
  - detailed instructions for using the monkeyd that's included inside SLAX
    - But that's how things worked in the OLD version. In v6.1.2, the boot menu includes this:
      - autoexec=
      - /boot/pxelinux.cfg/start;
      - /boot/pxelinux.cfg/web/start;
      - xconf;
      - telinit 4
    - after running web/start, you can visit http://localhost/slax/base/ to see the modules available.
several people report that Apache works just fine! (??)

tweaks to make Apache work with httpfs

Options +Indices