-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256





‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, May 22, 2021 11:29 AM, Darac Marjal <mailingl...@darac.org.uk> 
wrote:

> *.mount files are systemd representations of mount points. Sometimes they're 
> autogenerated from /etc/fstab (that is, fstab is still a first-class place to 
> configure mount points), but they might also be in the usual systemd 
> locations such as /etc/systemd/system
>
> Now you can't name the mount files exactly after the mount points (mostly 
> because / isn't valid in file names), so systemd uses an escaping mechanism
>
> $ systemd-escape --unescape -
> /
>
> So, this is a mount file for the root directory.
>
> Now, what does it mean that the unit is masked? Here, you need to look at the 
> man page for "systemctl", in the description for the "is-enabled" subcommand. 
> "Masked" means "Completely disabled, so that any start operation on it 
> fails". Masking may be done either by the system, or the administrator, but 
> it basically means that systemd won't be able to mount your root directory 
> (however, that's a moot point as userspace never mounts the root directory; 
> that's the kernel's job :)
>
> In summary, I'd say it's a strange error, but harmless.

Thanks, Darac.  Now I know it's systemd, not apt.

  On the desktop, 'systemctl list-devices' says, among other things:

● -.mount                                                                       
      masked active mounted   Root Mount              
● amandaDisk.mount                                                              
      masked active mounted   /amandaDisk             
● blackHole.mount                                                               
      masked active mounted   /blackHole              
● boot.mount                                                                    
      masked active mounted   /boot                   
  dev-hugepages.mount                                                           
      loaded active mounted   Huge Pages File System  
  dev-mqueue.mount                                                              
      loaded active mounted   POSIX Message Queue File
  proc-sys-fs-binfmt_misc.mount                                                 
      loaded active mounted   Arbitrary Executable File
● raid1Array.mount                                                              
      masked active mounted   /raid1Array             

Why is systemd trying to mount /?  /'s already mounted or systemd couldn't run, 
not so? And doesn't that say / is mounted and active?  And completely disabled 
(masked)?  Isn't active/masked a contradiction?

All of those with the dots are in fstab.  / on the desktop is an nvme, if that 
makes any difference.  On the laptop it's a vanilla SATA. 

Desktop /boot is a thumb-drive because the elderly BIOS will boot USB and the 
Debian startup software knows how to read an nvme.

Sorry to not understand systemd and its buds very well at all.

--
Glenn English


-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJgqV5zACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDJpyQf+J4q+UFK+//WiEi59f1YUFbndUz5ayjfMsj1uURj7/R59zxEw
qySvh/Lg51pUkAgTh7IvnCwtE2WUD37XcET1N8B3a1B1ldSw/qS+TVptu4MF
i2SFqt75K111z/nvBU/BqflkYAJATPJIK4pETHG1091rN+pb47mxJWLt4hCI
xvy6Bkjm6ppHqUj7toJKQ+jZPp1KPXDn+6VC5Nd+Uq1RUcrJ+dYh5hp8drVw
XDC3/Uvt6QXn4bxLgbhM2BHT6koBWvwkOGIfZmfvwZjIbcG1kjplDqtGLYXs
kpvJ4KtUF3bHdkojvX198UW3trJjpN8eAjxw3IQJGA3ZJWkW/33tmA==
=4Vl1
-----END PGP SIGNATURE-----

Reply via email to