situation. I don't know how it will it work with something like dual booting
and chain loading, so that is unsupported right now :P
svn path=/nixu/trunk/; revision=6282
* user is dropped into a shell, where the user can run tools like fdisk to partition a disk
* user needs to add a file called "disklayout" where it specifies SWAP, INSTALLDEVICE and TARGETDRIVE
* depending on the values of these the installscript might need to be fixed to get the GRUB configuration right
It's still somewhat inflexible, but it gives the user a bit more control than the old scheme
svn path=/nixu/trunk/; revision=6271
actually bad, because in theory a different kernel could be chosen to be
installed and then we could not load any modules...but even communism
works...in theory!
svn path=/nixu/trunk/; revision=6068
TODO: rewrite some of the tools to use the busybox tools instead of the "normal" utilities during installation, so we can shave off another 15 MB from the
installer
svn path=/nixu/trunk/; revision=6063
the latest patches to Nix itself, which were committed the last few days.
Biggest changes:
make-disk.sh:
* use nix-push to generate NAR files and a manifest
* use only copy a "few" packages (but probably still too many than we want) to the Nix store on the CD
fill-disk.sh:
* use nix-pull to register a manifest with a lot of packages. Only copy and
register as valid the few packages that are in the Nix store on the installer
CD, install the rest via nix-env and other tools (this needs to be reviewed
thoroughly for optimizations).
All in all the install process is a lot cleaner now, the login script is broken
however (but should be relatively easy to fix with some Nix wizardry). NIX_ROOT
is still broken, but we can work around most issues with relative ease now.
svn path=/nixu/trunk/; revision=6025
to /proc/sys/kernel/hotplug during boot. (FIXME, install hotplug during
install of NixOS)
* /dev/input is created by udev
svn path=/nixu/trunk/; revision=4660
controllers (uhci-hcd). This is of course not very elegant: even if a
machine does not have USB, or another USB controller this module will loaded.
A better way would be to let some hardware probing program run first, but
that is "future work"
svn path=/nixu/trunk/; revision=4631
the wrong place to make these directories. After all, if we build this into
a real installer what do we know what to install? Perhaps we will use a
completely different hotplug implementation that won't use this directory.
Ah well, future work ;)
svn path=/nixu/trunk/; revision=4502
