bdisk/docs/TODO

75 lines
3.6 KiB
Plaintext
Raw Normal View History

2016-11-28 02:56:15 -05:00
## Missing v2.x functionality ##
-i_am_a_racecar optimizations
-see also: grep -HnR bdisk/*.py
-TFTP, HTTP, RSYNC, git
-UPDATE THE README!
-sizes of build iso files
-GPG sigs on built files
-fix the branding, etc. on ipxe. :(
2016-12-16 03:16:48 -05:00
-convert docs to asciidoc, turn up instead of RTD (https://github.com/rtfd/readthedocs.org/issues/17#issuecomment-3752702)
-add ipxe to full iso maybe?
2016-11-28 02:56:15 -05:00
2014-12-19 14:13:30 -05:00
## General ##
2015-04-21 00:18:23 -04:00
-include benchmarking
-- http://sourceforge.net/projects/unixbench/
-- https://code.google.com/p/byte-unixbench/
-- https://github.com/akopytov/sysbench
-- (http://blog.due.io/2014/linode-digitalocean-and-vultr-comparison/ etc.)
2016-11-28 02:56:15 -05:00
-implement pyalpm to decreate dependency on chroot pacman-ing?
2016-12-03 06:07:41 -05:00
--or even maybe https://wiki.archlinux.org/index.php/offline_installation_of_packages in pure python!
-set up automatic exporting to PDF of the user manual server-side. https://pypi.python.org/pypi/unoconv/0.6
-There *has* to be a better way of handling package installation in the chroots.
-maybe remove lxde, firefox, chrome and replace with enlightenment/midori?
-custom repo? https://brainwreckedtech.wordpress.com/2013/01/27/making-your-own-arch-linux-repository/
2014-12-19 14:13:30 -05:00
## NETWORKING ##
-shorewall/some other firewall?
-WISH: locked-down VPN?
-autodetection/configuration of network. DHCP is currently running by default, but does it need to support IPv6? if so, how would the user configure their network?
2015-01-08 12:19:49 -05:00
-SECURE SSH: https://stribika.github.io/2015/01/04/secure-secure-shell.html
2015-05-15 02:48:35 -04:00
-DISABLE NETWORKMANAGER AND "fi.w1.wpa_supplicant1"??? keeps spawning wpa_supplicant (and thusly killing networking proper)
-for netboot, custom user agent (should be defined by build.conf)
--iPXE's curl
--initrd's curl
2014-12-19 14:13:30 -05:00
## Building ##
-WISH: Better logging[0]
2016-11-28 02:56:15 -05:00
-WISH: signing for secureboot releases (PreLoader and loader.efi handle this okay, but require manual intervention)
-does loader.efi support splash backgrounds? can i implement that differently somehow?
2015-08-27 20:57:45 -04:00
--yes, see e.g. https://www.reddit.com/r/archlinux/comments/3bwgf0/where_put_the_splasharchbmp_to_splash_screen_boot/
2014-12-19 14:13:30 -05:00
-strip out/remove unnecessary and orphan packages (e.g. gcc, make, automake, etc.)
-incorporate iPXE tweaks:
--http://ipxe.org/crypto
2015-06-29 12:44:57 -04:00
--http://ipxe.org/cmd/imgtrust
--http://ipxe.org/cmd/imgverify
2016-11-28 02:56:15 -05:00
--enable use of custom CA/self-signed certs for HTTPS etc.
--signed kernel and initrd for ipxe:
---#imgtrust --permanent
---#imgverify vmlinuz path/to/vmlinuz.sig
---#imgverify initrd path/to/initrd.sig
---DONE, partially. need to incorporate codesign certs/keys. routines, conf variables
2015-08-17 02:07:46 -04:00
-enable mirror= kernel commandline.
--if mirror_(NAME) is present, use that as repo name.
--if it starts with /, treat as mirrorlist (Include); otherwise use Server =
--if it has mirror_SIG-X, set signature options e.g. _SIG-N would be "SigLevel = Never"
2015-08-21 14:45:51 -04:00
-iPXE background support. sed -rf "${BASEDIR}/src/ipxe_local/script.sed" ${SRCDIR}/ipxe/src/config/general.h ; sed -rf "${BASEDIR}/src/ipxe_local/script2.sed" ${SRCDIR}/ipxe/src/config/console.h
2016-11-28 02:56:15 -05:00
--note that iPXE VESAFB console is not (yet) supported in EFI, so this is on hold. check into this to see if it has changed.
## Split into Separate Tools CD ##
-include WinMTR, build Mac OS X MTR for dist/tools on CD
-include pre-compiled LibreCrypt for opening LUKS parts on Windows (https://github.com/t-d-k/LibreCrypt)
--curl -s https://raw.githubusercontent.com/t-d-k/LibreCrypt/master/README.md | egrep 'InstallLibreCrypt_v[A-Za-z0-9\.]*.exe' | cut -f2 -d'"'
2014-12-19 14:13:30 -05:00
__________________________________________________________
FOOTNOTES:
2016-11-28 02:56:15 -05:00
[0] Debugging mode would probably suffice for logging? Maybe? There are plenty of pythonic ways to do logging too.