Project

General

Profile

Actions

Issue #1917

open

Add more robust fstab handling

Added by Denis 'GNUtoo' Carikli over 5 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
03/08/2019
Due date:
% Done:

0%

Estimated time:
Resolution:
Device:
Grant:
Type of work:
Any programming languages (scripts, C, etc)

Description

Rationale:
  • At the time of writing, most/all of the devices currently supported by Replicant have to be bought second hand.
  • During normal boot, if for some reason a filesystem that is specified in fstab cannot be mounted the device will be stuck on the Replicant logo, without any hints or explanation that something went wrong.
Actions #1

Updated by Andrés D about 5 years ago

The easiest way to allow booting when a filesystem fails to mount is adding the flag "nofail" in fstab. The downside of this approach is that the booting process will continue without reporting any error. For which filesystems would adding "nofail" make sense?

Actions #2

Updated by _I3^ RELATIVISM over 3 years ago

  • Type of work Any programming languages (scripts, C, etc) added
Actions

Also available in: Atom PDF