dan/liminix
1
0
Fork 5
Code

improve reinstallation docs

Browse Source
This commit is contained in:
Daniel Barlow 2024-07-12 18:38:04 +01:00
parent 2fe0cd2f48
commit d34919766a
1 changed files with 18 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
doc/admin.rst
View File

@ -174,32 +174,31 @@ Caveats
.. _levitate: .. _levitate:
Levitate - Reinstalling a running system (any filesystem) Reinstalling on a running system
********************************************************* ********************************
Liminix is initially installed from a monolithic Liminix is initially installed from a monolithic
:file:`firmware.bin` - and unless you're running a system on which :file:`firmware.bin` - and unless you're running a writable
:command:`liminix-rebuild` is available, the only way to update it is filesystem, the only way to update it is to build and install a whole
to build and install a whole new :file:`firmware.bin`. This makes it desirable to new :file:`firmware.bin`. However, you probably would prefer not to
be able to install a new firmware over the top of a running system - have to remove it from its installation site, unplug it from the
and preferably without having to remove it from its installation site, network and stick serial cables in it all over again.
unplug it from the network and stick serial cables in it all over
again. It is not (generally) safe to install a new firmware onto the flash
partitions that the active system is running on. To address this we
have :command:`levitate`, which a way for a running Liminix system to
"soft restart" into a ramdisk running only a limited set of services,
so that the main partitions can then be safely flashed.
For this we have :command:`levitate`. The problem is that you cannot
safely flash a new firmware over the top of a running system if the system
is running from the same partition as you're flashing onto. Levitate provides
a way for a running Liminix system to "soft restart" into a ramdisk
running only a limited set of services, so that the main
partitions can then be safely flashed.
Configuration Configuration
============= =============
*It needs to be configured when you create the initial system* to Levitate *needs to be configured when you create the initial system*
specify which services/packages/etc to run in maintenance mode - you to specify which services/packages/etc to run in maintenance
will probably want a network interface and an sshd for example so that mode. Most likely you want to configure a network interface and an ssh
you can login to reflash it. for example so that you can login to reflash it.
.. code-block:: nix .. code-block:: nix