starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-25 15:15:56 +03:00

[GH-ISSUE #991] Please add support for Slitaz #260

New issue

Open

opened 2026-02-27 14:51:05 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 14:51:05 +03:00

Owner

Originally created by @jwmh on GitHub (Sep 9, 2021).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/991

background intro

Slitaz.org seems to have a solid history of great network-boot support...
They even have a URL and their own mirrors dedicated to network-booting the latest LiveCD.

Its ISO size is TINY... the disto itself can run entirely in less than 512mB RAM.

slitaz netboot parameters

option A (using an ISO)

http://mirror.slitaz.org/boot/slitaz-boot.iso

option B (using ipxe)

This is what I would imagine NetbootXYZ will prefer!

Modify your DHCP server configuration:

1. Declare the tftp server:    mirror.slitaz.org
2. and Declare the boot file:    ipxe.pxe

slitaz ipxe Examples:

##### if using udhcpd:
siaddr mirror.slitaz.org
boot_file ipxe.pxe


##### if using dhcpd:
next-server "mirror.slitaz.org"
filemane "ipxe.pxe"


##### if using dnsmasq:
dhcp-boot=ipxe.pxe,mirror.slitaz.org

Trivia -- reference & docs

(note, documentation ranges from semi-uptodate, to extremely out of date)

homepage: https://slitaz.org
actual repo of current WebBoot files: https://mirror.slitaz.org/boot/
readme and older files: https://mirror.slitaz.org
documentation (sorta) https://boot.slitaz.org
changelog for bootfiles: https://hg.slitaz.org/slitaz-boot-scripts

...

The above five links
are merely for triva.

Mainly should just need this:

A.) http://mirror.slitaz.org/boot/slitaz-boot.iso

or else

B.)

Declare the tftp server: mirror.slitaz.org
And declare the boot file: ipxe.pxe

conclusion

In its way, Slitaz is a bit like its own miniature NetbootXyz distro.
It functions (to the user) sorta similarly.

Originally created by @jwmh on GitHub (Sep 9, 2021). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/991 ## background intro Slitaz.org seems to have a solid history of great network-boot support... They even have a URL and their own mirrors dedicated to network-booting the latest LiveCD. Its ISO size is TINY... the disto itself can run *entirely* in less than 512mB RAM. ## slitaz netboot parameters ### option A (using an ISO) http://mirror.slitaz.org/boot/slitaz-boot.iso *or* ### option B (using ipxe) **This is what I would imagine NetbootXYZ will prefer!** Modify your DHCP server configuration: ~~~ 1. Declare the tftp server: mirror.slitaz.org 2. and Declare the boot file: ipxe.pxe ~~~ #### slitaz ipxe Examples: ~~~ ##### if using udhcpd: siaddr mirror.slitaz.org boot_file ipxe.pxe ##### if using dhcpd: next-server "mirror.slitaz.org" filemane "ipxe.pxe" ##### if using dnsmasq: dhcp-boot=ipxe.pxe,mirror.slitaz.org ~~~ ## Trivia -- reference & docs (note, documentation ranges from semi-uptodate, to extremely out of date) * homepage: https://slitaz.org * actual repo of current WebBoot files: https://mirror.slitaz.org/boot/ * readme and older files: https://mirror.slitaz.org * documentation (sorta) https://boot.slitaz.org * changelog for bootfiles: https://hg.slitaz.org/slitaz-boot-scripts ... The above five links are merely for triva. Mainly should just need this: A.) http://mirror.slitaz.org/boot/slitaz-boot.iso or else B.) 1. Declare the tftp server: mirror.slitaz.org 2. And declare the boot file: ipxe.pxe ## conclusion In its way, Slitaz is a bit like its own miniature NetbootXyz distro. It functions (to the user) sorta similarly.

kerem added the

no-issue-activity

label

2026-02-27 14:51:05 +03:00

kerem commented

2026-02-27 14:51:06 +03:00

Author

Owner

@jwmh commented on GitHub (Sep 9, 2021):

Q:
Would it be trivial, or easy, to add this?

Or difficult?

@jwmh commented on GitHub (Sep 9, 2021): Q: Would it be trivial, or easy, to add this? Or difficult?

kerem commented

2026-02-27 14:51:06 +03:00

Author

Owner

@antonym commented on GitHub (Sep 9, 2021):

We had it added at one point when we first started Live OS booting, but I think there were some issues with it. I can't find any notes as to why, but I will take another look at it and see if we can get it working:

This was the older commit:
github.com/netbootxyz/netboot.xyz@987e80c403

@antonym commented on GitHub (Sep 9, 2021): We had it added at one point when we first started Live OS booting, but I think there were some issues with it. I can't find any notes as to why, but I will take another look at it and see if we can get it working: This was the older commit: https://github.com/netbootxyz/netboot.xyz/commit/987e80c4032ca4974dea2937d24549bc4cec6e19

kerem commented

2026-02-27 14:51:06 +03:00

Author

Owner

@jwmh commented on GitHub (Sep 10, 2021):

Oh yeah, thanks!

Idea:
It looks like that attempt was manually having lots of different Slitaz versions, all listed within NetbootXYZ.

However, iirc Slitaz can offer all of those itself from its own netboot.

... So, maybe there is only a need to chain a single netboot ISO or .pxe bootfile (option A, or B, linked above)...
... And then let Slitaz and the enduser manage it from there(?)

Edit/addendum:
In the older commit,
I don't see listed anywhere the slitaz web/netboot plain ISO (i.e., not an OS image, but just either the netboot iso or ipxe image).
Maybe using just that could simplify things considerably(?)

@jwmh commented on GitHub (Sep 10, 2021): Oh yeah, thanks! Idea: It looks like that attempt was manually having lots of different Slitaz versions, all listed within NetbootXYZ. However, iirc Slitaz can offer all of those itself from its own netboot. ... So, maybe there is only a need to chain a single netboot ISO or .pxe bootfile (option A, or B, linked above)... ... And then let Slitaz and the enduser manage it from there(?) Edit/addendum: In the older commit, I don't see listed anywhere the slitaz web/netboot plain ISO (i.e., *not* an OS image, but just either the netboot iso or ipxe image). Maybe using just that could simplify things considerably(?)

kerem commented

2026-02-27 14:51:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 11, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Oct 11, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

kerem commented

2026-02-27 14:51:06 +03:00

Author

Owner

@HGpunktT commented on GitHub (Mar 13, 2024):

As memdisk cannot be used to boot SliTaz from an ISO image in UEFI mode,
I tried the following (and succeeded):

make bzImage64 from /boot/bzImage64 in the actual ISO image slitaz-rolling-core64.iso
available on a webserver ( about 4 MiB )
make rootfs.gz from /boot/rootfs.gz in the actual ISO image slitaz-rolling-core64.iso
available on a webserver ( about 50 MiB )
boot netboot.xyz in UEFI mode
select iPXE shell
initrd --name rfs <uri_of_webserver>/<path_to_slitaz_stuff>/rootfs.gz
kernel <uri_of_webserver>/<path_to_slitaz_stuff>/bzImage64 rw initrd=rfs
boot

slitaz-rolling-core64.iso is created weekly and available on
mirror.slitaz.org

@HGpunktT commented on GitHub (Mar 13, 2024): As memdisk cannot be used to boot SliTaz from an ISO image in UEFI mode, I tried the following (and succeeded): - make bzImage64 from /boot/bzImage64 in the actual ISO image slitaz-rolling-core64.iso available on a webserver ( about 4 MiB ) - make rootfs.gz from /boot/rootfs.gz in the actual ISO image slitaz-rolling-core64.iso available on a webserver ( about 50 MiB ) - boot netboot.xyz in UEFI mode - select iPXE shell - `initrd --name rfs <uri_of_webserver>/<path_to_slitaz_stuff>/rootfs.gz` - `kernel <uri_of_webserver>/<path_to_slitaz_stuff>/bzImage64 rw initrd=rfs` - `boot` slitaz-rolling-core64.iso is created weekly and available on [mirror.slitaz.org](http://mirror.slitaz.org/iso/rolling/slitaz-rolling-core64.iso)

kerem referenced this issue

2026-02-27 14:53:04 +03:00

[PR #260] [MERGED] Upgrade Kali to 2018.2 #738

kerem referenced this issue

2026-03-01 18:39:27 +03:00

[PR #260] [MERGED] Upgrade Kali to 2018.2 #2277

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#260

No description provided.

Rows
Columns