From 2df44e934c9ba14a89d9245d1a4f7cf18e8cfdaa Mon Sep 17 00:00:00 2001 From: Miguel Ángel Arruga Vivas Date: Mon, 2 Nov 2020 18:22:33 +0100 Subject: system: Change comment wording. * gnu/system.scm (): Substitute path with file name. --- gnu/system.scm | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/gnu/system.scm b/gnu/system.scm index ff9ab18f22..b257ea0385 100644 --- a/gnu/system.scm +++ b/gnu/system.scm @@ -290,13 +290,13 @@ directly by the user." ;; Because we will use the 'store-device' to create the GRUB search command, ;; the 'store-device' has slightly different semantics than 'root-device'. ;; The 'store-device' can be a file system uuid, a file system label, or #f, - ;; but it cannot be a device path such as "/dev/sda3", since GRUB would not - ;; understand that. The 'root-device', on the other hand, corresponds + ;; but it cannot be a device file name such as "/dev/sda3", since GRUB would + ;; not understand that. The 'root-device', on the other hand, corresponds ;; exactly to the device field of the object representing the - ;; OS's root file system, so it might be a device path like "/dev/sda3". - ;; The 'store-directory-prefix' field contains #f or the store path inside - ;; the 'store-device' as it is seen by GRUB, e.g. it would contain - ;; "/storefs" if the store is located in that subvolume of a btrfs + ;; OS's root file system, so it might be a device file name like + ;; "/dev/sda3". The 'store-directory-prefix' field contains #f or the store + ;; file name inside the 'store-device' as it is seen by GRUB, e.g. it would + ;; contain "/storefs" if the store is located in that subvolume of a btrfs ;; partition. (root-device boot-parameters-root-device) (bootloader-name boot-parameters-bootloader-name) -- cgit v1.2.3