1
0

proofread

This commit is contained in:
Daniel Barlow 2024-12-24 14:01:30 +00:00
parent 3e19f1b927
commit 608d3e3abf

View File

@ -57,18 +57,18 @@
The default target for this device is ``outputs.ubimage`` which The default target for this device is ``outputs.ubimage`` which
makes a ubifs image suitable for use with :command:`ubiupdatevol`. makes a ubifs image suitable for use with :command:`ubiupdatevol`.
For a first-time installation the simplest way to achieve this is To write this to the device we use the OpenWrt recovery system
using the OpenWrt recovery system that you installed in the installed in the previous step. In this configuration the
previous step. In this configuration the device assigns itself the device assigns itself the IP address 192.168.1.1/24 on its LAN
IP address 192.168.1.1/24 on its LAN ports and expects the ports and expects the connected computer to have 192.168.1.254
connected computer to have 192.168.1.254
The `ubi0_7` device in these instructions is correct as of Dec .. warning:: The `ubi0_7` device in these instructions is correct
2024 (dangowrt/owrt-ubi-installer commit d79e7928). If you are as of Dec 2024 (dangowrt/owrt-ubi-installer commit
installing some time later, it is important to check the output d79e7928). If you are installing some time later, it
from :command:`ubinfo -a` and make sure you are updating the is important to check the output from
"liminix" volume and not some other one which had been introduced :command:`ubinfo -a` and make sure you are updating
since I wrote this. the "liminix" volume and not some other one which had
been introduced since I wrote this.
.. code-block:: console .. code-block:: console
@ -87,11 +87,12 @@
Character device major/minor: 250:8 Character device major/minor: 250:8
root@OpenWrt:~# ubiupdatevol /dev/ubi0_7 /tmp/rootfs root@OpenWrt:~# ubiupdatevol /dev/ubi0_7 /tmp/rootfs
For subsequent Liminix reinstalls, you don't need to repeat the
"Preparation" step and in fact should seek to avoid it if For subsequent Liminix reinstalls, you don't need to repeat the
possible. Updating volumes with :command:`ubiupdatevol` will "Preparation" step and in fact should seek to avoid it if
preserve the erase counters used for write levelling, so is possible. Updating volumes with :command:`ubiupdatevol` will
preferred over any kind of "factory" wipe which will reset them. preserve the erase counters used for write levelling, so is
preferred over any kind of "factory" wipe which will reset them.
''; '';
system = { system = {