path: root/dev/todo
diff options
authorP. J. McDermott <pehjota>2014-04-02 19:33:59 (EDT)
committer P. J. McDermott <>2014-04-02 19:33:59 (EDT)
commit9260ca100bb02f64e985e4af0f2ef0b7ada17cac (patch)
tree16b7f6b72a21511068e37c3e812a9e3821b68366 /dev/todo
parent8e05893579ff196de45e9f5fcbce3e864cd66d6e (diff)
dev/todo/installation-bootstrap-tool: Truncate.
Diffstat (limited to 'dev/todo')
1 files changed, 1 insertions, 38 deletions
diff --git a/dev/todo/installation-bootstrap-tool.mdwn b/dev/todo/installation-bootstrap-tool.mdwn
index 14610fb..af7b47a 100644
--- a/dev/todo/installation-bootstrap-tool.mdwn
+++ b/dev/todo/installation-bootstrap-tool.mdwn
@@ -1,40 +1,3 @@
[[!meta title="Installation Bootstrap Tool"]]
-A tool similar to [debootstrap][debootstrap] of Debian needs to be written to
-bootstrap the installation of a basic system. It can be used for building
-packages (see "Package Cross Building Tool" below) or installing the operating
-system on hardware targets.
-Basically, the tool would fetch from the package archive the index of packages,
-determine which packages need to be installed, download each package, and unpack
-each package. Since the package manager may not be available, the tool must
-handle dependency resolution and package unpacking on its own.
-To be determined is how the "second stage" of the installation ‒ the execution
-of package maintainer scripts (`preinst` and `postinst`) to complete the
-configuration of each package ‒ will be done. At least most of the time, this
-tool will be used to install packages built for an architecture that differs
-from the architecture on which the tool is run; therefore utilities used by
-maintainer scripts may not be executable. In this situation, debootstrap leaves
-behind a copy of itself in the installed system to be executed on the target
-architecture. Such a solution might not work for this tool, because nothing can
-be executed on the target architecture until the installed system is booted, and
-the installed system shouldn't be booted until after the packages are
-We can't use debootstrap, since the formats of our binary packages and package
-archives differ slightly from those of Debian. But we can model our tool after
-debootstrap or even just fork debootstrap.
-If written portably (i.e. in conformance with POSIX.1), this tool could be used
-to make base system images on any UNIX-like operating system with an
-implementation of tar. On any operating system that also has a chroot program,
-this tool can be used with the package cross building tool described below to
-build packages for this distribution. Therefore, these tools can be thought of
-as a "Software Development Kit" ("SDK") for the distribution, usable on any
-capable development system.
-Hopefully, this tool can be done by October 2012.
+Page removed.