From cd6b3c4bada548b7b2d593cfeaf03214f4406915 Mon Sep 17 00:00:00 2001
From: Paul-Nicolas Madelaine <pnm@pnm.tf>
Date: Wed, 13 Dec 2023 19:39:26 +0100
Subject: [PATCH] precision

---
 content/posts/2022-06-09-nix-registry.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/content/posts/2022-06-09-nix-registry.md b/content/posts/2022-06-09-nix-registry.md
index 58d013b..936795f 100644
--- a/content/posts/2022-06-09-nix-registry.md
+++ b/content/posts/2022-06-09-nix-registry.md
@@ -25,18 +25,21 @@ map "nixpkgs" to a specific revision of the repository. Using the "rev"
 attribute of a flake input, we can even point it to the same revision as the one
 used by our flake-defined configuration.
 
+Just be sure not to use the "nixpkgs" flake URL in your configuration flake,
+otherwise `nix flake update` won't update nixpkgs!
+
 The module to configure the Nix registry looks like this:
 
 ```Nix
 {
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
   };
 
   outputs = { self, nixpkgs, }: {
 
-    nixosModule = {
+    nixosModules.default = {
       nix.registry.nixpkgs = {
         from = {
           type = "indirect";