philipp/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Activity
nixpkgs/configuration/system-configuration.sh

22 lines
493 B
Bash
Raw Normal View History

* The installer now installs a configuration on the target device that boots into stage 1 (kernel+initrd) succesfully. `system-configuration.nix' contains the definition of the configuration to be installed. The attribute systemConfiguration is installed into the profile /nix/var/nix/profiles/system. Then the program /nix/var/nix/profiles/system/bin/switch-to-configuration is called to finalise the installation. This program (generated by system-configuration.sh) installs Grub on the drive with a menu that contains the entry for the desired kernel and initrd. In principle this allows us to do rollbacks to previous system configurations by doing `nix-env --rollback' and then calling switch-to-configuration to update Grub. Ideally this should be done in a single command (and we should consider the obvious risk of garbage collecting the current kernel etc. to which the current Grub menu points...). Maybe the responsibility for generating the Grub menu should be placed somewhere else. For instance, we could generate a Grub menu automatically out of all the generations in the `system' profile. svn path=/nixu/trunk/; revision=7009
2006-11-13 00:30:03 +01:00
source $stdenv/setup
ensureDir $out
ln -s $kernel $out/kernel
ln -s $grub $out/grub
* Don't hardcode selinux=0 etc. * Store the paths of init and initrd. svn path=/nixu/trunk/; revision=7147
2006-11-27 14:59:50 +01:00
ln -s $bootStage2 $out/init
ln -s $initrd $out/initrd
* Allow switching to a new configuration without rebooting. However, we don't stop/start/restart Upstart jobs yet. svn path=/nixos/trunk/; revision=7297
2006-12-10 01:04:58 +01:00
ln -s $activateConfiguration $out/activate
* Lots of refactoring. * Clear the PATH in most scripts. This helps to ensure purity. svn path=/nixos/trunk/; revision=7299
2006-12-10 23:29:44 +01:00
ln -s $etc/etc $out/etc
* Don't hardcode selinux=0 etc. * Store the paths of init and initrd. svn path=/nixu/trunk/; revision=7147
2006-11-27 14:59:50 +01:00
echo "$extraKernelParams" > $out/kernel-params
* The installer now installs a configuration on the target device that boots into stage 1 (kernel+initrd) succesfully. `system-configuration.nix' contains the definition of the configuration to be installed. The attribute systemConfiguration is installed into the profile /nix/var/nix/profiles/system. Then the program /nix/var/nix/profiles/system/bin/switch-to-configuration is called to finalise the installation. This program (generated by system-configuration.sh) installs Grub on the drive with a menu that contains the entry for the desired kernel and initrd. In principle this allows us to do rollbacks to previous system configurations by doing `nix-env --rollback' and then calling switch-to-configuration to update Grub. Ideally this should be done in a single command (and we should consider the obvious risk of garbage collecting the current kernel etc. to which the current Grub menu points...). Maybe the responsibility for generating the Grub menu should be placed somewhere else. For instance, we could generate a Grub menu automatically out of all the generations in the `system' profile. svn path=/nixu/trunk/; revision=7009
2006-11-13 00:30:03 +01:00
cat > $out/menu.lst << GRUBEND
* Don't hardcode selinux=0 etc. * Store the paths of init and initrd. svn path=/nixu/trunk/; revision=7147
2006-11-27 14:59:50 +01:00
kernel $kernel init=$bootStage2 $extraKernelParams
* Pass the path of the stage 2 init script to stage 1 init through the kernel command line, instead of having a /init symlink. This allows us to switch between configurations. * Some debug support: adding `debug' to the kernel command line gives a stage 1 shell. svn path=/nixu/trunk/; revision=7107
2006-11-24 01:04:29 +01:00
initrd $initrd
* The installer now installs a configuration on the target device that boots into stage 1 (kernel+initrd) succesfully. `system-configuration.nix' contains the definition of the configuration to be installed. The attribute systemConfiguration is installed into the profile /nix/var/nix/profiles/system. Then the program /nix/var/nix/profiles/system/bin/switch-to-configuration is called to finalise the installation. This program (generated by system-configuration.sh) installs Grub on the drive with a menu that contains the entry for the desired kernel and initrd. In principle this allows us to do rollbacks to previous system configurations by doing `nix-env --rollback' and then calling switch-to-configuration to update Grub. Ideally this should be done in a single command (and we should consider the obvious risk of garbage collecting the current kernel etc. to which the current Grub menu points...). Maybe the responsibility for generating the Grub menu should be placed somewhere else. For instance, we could generate a Grub menu automatically out of all the generations in the `system' profile. svn path=/nixu/trunk/; revision=7009
2006-11-13 00:30:03 +01:00
GRUBEND
ensureDir $out/bin
* Lots of refactoring. * Clear the PATH in most scripts. This helps to ensure purity. svn path=/nixos/trunk/; revision=7299
2006-12-10 23:29:44 +01:00
substituteAll $switchToConfiguration $out/bin/switch-to-configuration
* The installer now installs a configuration on the target device that boots into stage 1 (kernel+initrd) succesfully. `system-configuration.nix' contains the definition of the configuration to be installed. The attribute systemConfiguration is installed into the profile /nix/var/nix/profiles/system. Then the program /nix/var/nix/profiles/system/bin/switch-to-configuration is called to finalise the installation. This program (generated by system-configuration.sh) installs Grub on the drive with a menu that contains the entry for the desired kernel and initrd. In principle this allows us to do rollbacks to previous system configurations by doing `nix-env --rollback' and then calling switch-to-configuration to update Grub. Ideally this should be done in a single command (and we should consider the obvious risk of garbage collecting the current kernel etc. to which the current Grub menu points...). Maybe the responsibility for generating the Grub menu should be placed somewhere else. For instance, we could generate a Grub menu automatically out of all the generations in the `system' profile. svn path=/nixu/trunk/; revision=7009
2006-11-13 00:30:03 +01:00
chmod +x $out/bin/switch-to-configuration
Reference in a new issue Copy permalink