From 47e67f5e9caf22bd9f33047d90e73fdc686acef3 Mon Sep 17 00:00:00 2001 From: Marc Weber Date: Mon, 23 Jul 2012 03:19:02 +0200 Subject: [PATCH] renaming all occurrences of /var/run/{booted,current}-system in particular those found in docs still keeping old path in modules/config/shells.nix for unkown reason (?) --- doc/manual/man-nixos-rebuild.xml | 2 +- doc/manual/userconfiguration.xml | 16 ++++++++-------- gui/chrome/content/nixos.js | 4 ++-- lib/test-driver/test-driver.pl | 2 +- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/manual/man-nixos-rebuild.xml b/doc/manual/man-nixos-rebuild.xml index 383334d82e1..ddf4e40be0c 100644 --- a/doc/manual/man-nixos-rebuild.xml +++ b/doc/manual/man-nixos-rebuild.xml @@ -281,7 +281,7 @@ the Nix manual for details. - /var/run/current-system + /run/current-system A symlink to the currently active system configuration in the Nix store. diff --git a/doc/manual/userconfiguration.xml b/doc/manual/userconfiguration.xml index 2cad256c742..7c6540caf3a 100644 --- a/doc/manual/userconfiguration.xml +++ b/doc/manual/userconfiguration.xml @@ -13,20 +13,20 @@ them found both by Compiz and by Compiz Configuration Settings (also in Compiz Fusion distribution). By default they look in Compiz installation path and in home directory. You do not need to track /nix/store manually - everything is already in - /var/run/current-system/sw/share. + /run/current-system/sw/share. $HOME/.compiz/plugins should contain plugins you want to load. All the installed plugins are available in - /var/run/current-system/sw/share/compiz-plugins/compiz/, + /run/current-system/sw/share/compiz-plugins/compiz/, so you can use symlinks to this directory. $HOME/.compiz/metadata should contain metadata (definition of configuration options) for plugins you want to load. All the installed metadata is available in - /var/run/current-system/sw/share/compiz/, + /run/current-system/sw/share/compiz/, so you can use symlinks to this directory. @@ -35,16 +35,16 @@ should be found, but if you run Compiz with GConf configuration (default for X server job for now), you have to link - /var/run/current-system/sw/share/compizconfig/backends/ + /run/current-system/sw/share/compizconfig/backends/ into $HOME/.compizconfig/backends directory. To summarize the above, these are the commands you have to execute - ln -s /var/run/current-system/sw/share/compiz/ $HOME/.compiz/metadata - ln -s /var/run/current-system/sw/share/compiz-plugins/compiz/ $HOME/.compiz/plugins - ln -s /var/run/current-system/sw/share/compizconfig/backends/ $HOME/.compizconfig/backends + ln -s /run/current-system/sw/share/compiz/ $HOME/.compiz/metadata + ln -s /run/current-system/sw/share/compiz-plugins/compiz/ $HOME/.compiz/plugins + ln -s /run/current-system/sw/share/compizconfig/backends/ $HOME/.compizconfig/backends Now you can launch ccsm and configure everything. You should select GConf as a backend in the preferences menu of ccsm @@ -57,7 +57,7 @@ To have pidgin-latex plugin working after installation, you need the following: - Symlink /var/run/current-system/sw/share/pidgin-latex/pidgin-latex.so + Symlink /run/current-system/sw/share/pidgin-latex/pidgin-latex.so to $HOME/.purple/plugins/pidgin-latex.so diff --git a/gui/chrome/content/nixos.js b/gui/chrome/content/nixos.js index 7b45b6c006a..63a3c16a573 100644 --- a/gui/chrome/content/nixos.js +++ b/gui/chrome/content/nixos.js @@ -21,8 +21,8 @@ NixOS.prototype = { nixos: "/etc/nixos/nixos", nixpkgs: "/etc/nixos/nixpkgs", config: "/etc/nixos/configuration.nix", - instantiateBin: "/var/run/current-system/sw/bin/nix-instantiate", - optionBin: "/var/run/current-system/sw/bin/nixos-option", + instantiateBin: "/run/current-system/sw/bin/nix-instantiate", + optionBin: "/run/current-system/sw/bin/nixos-option", tmpFile: "nixos-gui", option: null }; diff --git a/lib/test-driver/test-driver.pl b/lib/test-driver/test-driver.pl index 43f74cf404b..6c95f5ba517 100644 --- a/lib/test-driver/test-driver.pl +++ b/lib/test-driver/test-driver.pl @@ -135,7 +135,7 @@ sub runTests { # Figure out where to put the *.gcda files so that the # report generator can find the corresponding kernel # sources. - my $kernelDir = $vm->mustSucceed("echo \$(dirname \$(readlink -f /var/run/current-system/kernel))/.build/linux-*"); + my $kernelDir = $vm->mustSucceed("echo \$(dirname \$(readlink -f /run/current-system/kernel))/.build/linux-*"); chomp $kernelDir; my $coverageDir = "/tmp/xchg/coverage-data/$kernelDir";