From: robin_listas@es.invalid   
      
   On 2024-05-14 08:39, J.O. Aho wrote:   
   > On 13/05/2024 19.43, bad sector wrote:   
   >> On 5/13/24 13:00, Paul wrote:   
   >>> On 5/13/2024 12:04 PM, bad sector wrote:   
      
   >> I like to keep in mind that the user could well be unfamiliar enough   
   >> with linux. Say you start with two drives, the data drive gets written   
   >> into /etc/fstab but on the next boot for some reason like that data   
   >> drive being unplugged or just throwing a fit with /etc/fstab not   
   >> written with 'nofail' etc. etc. etc. and you there have a failed boot   
   >> on your *very first install*   
   >   
   > That isn't the fault of fstab but systemd and it's way of mount things   
   > if you get a failed boot just for a secondary drive is missing. If you   
   > have a systemd free Linux, it will bot up fine, you can even login with   
   > the user, but of course you won't end up in your ~/ as it don't exist   
   > and you have nowhere to save your files either, so things will not be   
   > fully functional for the users until you have fixed the issue.   
      
   Nope.   
      
   openSUSE, back at the time when systemd was not a thing, would not boot   
   if one of the disks was missing. At best, it would boot in rescue mode.   
      
   Pretty much the same as today with systemd.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)