diff options
| author |   Martin Kelly <mkelly@xevo.com> | 2017-05-02 10:21:26 -0700 |
|---|---|---|
| committer | Martin Kelly <mkelly@xevo.com> | 2017-05-02 10:35:51 -0700 |
| commit | 0c70d7729bd20308a42fcbec32599698841b2c25 (patch) | |
| tree | 366b3136e4481875cf8afa9aae5604199b3af20b | |
| parent | 4e9dc8be544e2a107d35860d1a9852e16d60cc03 (diff) | |
r-car: boot with ro, not rw
Booting with ro is safer in the case of filesystem corruption because it
prevents processes from writing to a broken filesystem before the kernel
has a chance to fsck and then remount rw. For this reason, it seems to
be the standard in other Linux distros. From my testing, I don't see any
drawback to it.
Signed-off-by: Martin Kelly <mkelly@xevo.com>
| -rw-r--r-- | getting-started/machines/R-Car-Starter-Kit-gen3.md | 6 | ||||
| -rw-r--r-- | getting-started/machines/porter.md | 2 |
2 files changed, 4 insertions, 4 deletions
diff --git a/getting-started/machines/R-Car-Starter-Kit-gen3.md b/getting-started/machines/R-Car-Starter-Kit-gen3.md index e18de67..d7fbfd1 100644 --- a/getting-started/machines/R-Car-Starter-Kit-gen3.md +++ b/getting-started/machines/R-Car-Starter-Kit-gen3.md @@ -457,7 +457,7 @@ Follow the steps below to configure the boot from microSD card and to set screen ``` => printenv baudrate=115200 - bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait rw rootfstype=ext4 + bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro rootfstype=ext4 bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 bootdelay=3 fdt_high=0xffffffffffffffff @@ -477,7 +477,7 @@ Follow the steps below to configure the boot from microSD card and to set screen ``` => printenv baudrate=115200 - bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait rw rootfstype=ext4 + bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro rootfstype=ext4 bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 bootdelay=3 fdt_high=0xffffffffffffffff @@ -496,7 +496,7 @@ Follow the steps below to configure the boot from microSD card and to set screen * If not, copy line by line: ``` -setenv bootargs console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait rw rootfstype=ext4 +setenv bootargs console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro rootfstype=ext4 setenv bootcmd run load_ker\; run load_dtb\; booti 0x48080000 - 0x48000000 setenv load_ker ext4load mmc 0:1 0x48080000 /boot/Image ``` diff --git a/getting-started/machines/porter.md b/getting-started/machines/porter.md index f3f6d15..85ff695 100644 --- a/getting-started/machines/porter.md +++ b/getting-started/machines/porter.md @@ -364,7 +364,7 @@ setenv ethaddr 2e:09:0a:00:75:b5 ``` setenv bootargs_console 'console=ttySC6,38400 ignore_loglevel' setenv bootargs_video 'vmalloc=384M video=HDMI-A-1:1920x1080-32@60' -setenv bootargs_root 'root=/dev/mmcblk0p1 rootdelay=3 rw rootfstype=ext4 rootwait' +setenv bootargs_root 'root=/dev/mmcblk0p1 rootdelay=3 ro rootfstype=ext4 rootwait' setenv bootmmc '1:1' setenv bootcmd_sd 'ext4load mmc ${bootmmc} 0x40007fc0 boot/uImage+dtb' setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} ${bootargs_root}; run bootcmd_sd; bootm 0x40007fc0' |