Alpine local backup - Revision history

Antonomy: grammar and formatting

2025-11-27T04:22:02Z

grammar and formatting

← Older revision		Revision as of 04:22, 27 November 2025
Line 1:		Line 1:
	Local backup utility ({{ic\|lbu}}) is the Alpine Linux tool ~~to manage~~ [[Diskless Mode]] installations. For these installations, {{ic\|lbu}} ~~tool~~ must be used to [[#Committing changes\|commit the changes]] whenever [[Alpine Package Keeper]] is used.		Local backup utility ({{ic\|lbu}}) is the Alpine Linux tool for managing [[Diskless Mode]] installations. For these installations, {{ic\|lbu}} must be used to [[#Committing changes\|commit the changes]] whenever [[Alpine Package Keeper]] is used.

	When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. installing a package or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved with {{ic\|lbu}} ~~tool~~ to an overlay file i.e [[Diskless Mode#Apkovl\|apkovl]] file ~~that~~ can be automatically loaded when booting, to restore the saved state.		When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. installing a package or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved with {{ic\|lbu}} to an overlay file i.e [[Diskless Mode#Apkovl\|apkovl]] file, which can be automatically loaded when booting to restore the saved state.

	By default, an {{ic\|lbu commit}} only stores modifications below {{Path\|/etc}}, with the exception of the {{Path\|/etc/init.d/}} directory. If a user was created during the {{ic\|setup-alpine}} script, that user's home directory is also added to the paths that ~~<code>~~lbu~~</code>~~ will ~~backup~~ up. However, [[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]] enables modifying that set of included files, and can be used to specify additional files or folders.		By default, an {{ic\|lbu commit}} only stores modifications below {{Path\|/etc}}, with the exception of the {{Path\|/etc/init.d/}} directory. If a user was created during the {{ic\|setup-alpine}} script, that user's home directory is also added to the paths that {{ic\|lbu}} will back up. However, {{ic\|[[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]]}} enables modifying that set of included files, and can be used to specify additional files or folders.

	== Overview ==		== Overview ==

Antonomy: fixes broken diskless mode link

2025-11-27T04:11:48Z

fixes broken diskless mode link

← Older revision		Revision as of 04:11, 27 November 2025
Line 203:		Line 203:
	== See also ==		== See also ==

	* [Diskless Mode]]		* [[Diskless Mode]]
	* [[Back Up a Flash Memory Installation]]		* [[Back Up a Flash Memory Installation]]
	* [[Manually editing a existing apkovl]]		* [[Manually editing a existing apkovl]]

PlayerSchark: Updated lbu message to mention LBU_BACKUPDIR and align with lbu 3.20.0-r0

2025-11-13T14:23:48Z

Updated lbu message to mention LBU_BACKUPDIR and align with lbu 3.20.0-r0

← Older revision		Revision as of 14:23, 13 November 2025
Line 58:		Line 58:
	You will need to save your apkovl on suitable media (floppy, usb, cf, etc.).		You will need to save your apkovl on suitable media (floppy, usb, cf, etc.).
	<pre>		<pre>
			Create a backup of config to writeable media.

	usage: lbu commit\|ci [-nv] [<media>]		usage: lbu commit\|ci [-nv] [<media>]

	Options:		Options:
	-d Remove old apk overlay files.		-d Remove old apk overlay files.
	-e Protect configuration with a password.		-e Protect configuration with a password.
	-n Don't commit, just show what would have been ~~committed~~.		-n Don't commit, just show what would have been commited.
	-p <password> Give encryption password on the command-line		-p <password> Give encryption password on the command-line
	-v Verbose mode.		-v Verbose mode.

	The following values for <media> ~~are~~ supported: floppy usb		The following values for <media> is supported: floppy usb
	If <media> is not specified, the environment variable LBU_MEDIA will be used.		If <media> is not specified, the environment variable LBU_BACKUPDIR or
			LBU_MEDIA will be used. If LBU_BACKUPDIR is set, nothing will be mounted.

	Password protection will use aes-256-cbc encryption. Other ciphers can be		Password protection will use aes-256-cbc encryption. Other ciphers can be
Line 74:		Line 77:
	For possible ciphers, try: openssl -v		For possible ciphers, try: openssl -v

	The password used to encrypt the file, can be specified with the -p		The password used to encrypt the file, can either be specified with the -p
	option or by using the PASSWORD environment variable.		option or using the PASSWORD environment variable.

	The environment ~~variable~~ can also be set in /etc/lbu/lbu.conf		The environment variables can also be set in /etc/lbu/lbu.conf
	</pre>		</pre>

Wackbyte: add space

2025-07-30T19:05:41Z

add space

← Older revision		Revision as of 19:05, 30 July 2025
Line 1:		Line 1:
	Local backup utility({{ic\|lbu}}) is the Alpine Linux tool to manage [[Diskless Mode]] installations. For these installations, {{ic\|lbu}} tool must be used to [[#Committing changes\|commit the changes]] whenever [[Alpine Package Keeper]] is used.		Local backup utility ({{ic\|lbu}}) is the Alpine Linux tool to manage [[Diskless Mode]] installations. For these installations, {{ic\|lbu}} tool must be used to [[#Committing changes\|commit the changes]] whenever [[Alpine Package Keeper]] is used.

	When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. installing a package or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved with {{ic\|lbu}} tool to an overlay file i.e [[Diskless Mode#Apkovl\|apkovl]] file that can be automatically loaded when booting, to restore the saved state.		When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. installing a package or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved with {{ic\|lbu}} tool to an overlay file i.e [[Diskless Mode#Apkovl\|apkovl]] file that can be automatically loaded when booting, to restore the saved state.

Prabuanand: changed wikitags, moved headings, reworded sentence to make the page easier to follow

2025-03-31T10:50:10Z

changed wikitags, moved headings, reworded sentence to make the page easier to follow

← Older revision		Revision as of 10:50, 31 March 2025
Line 1:		Line 1:
	Local backup utility(~~<code>~~lbu~~</code>~~) is the Alpine Linux tool to manage [[Diskless Mode]] installations. For these installations, ~~<code>~~lbu~~</code>~~ tool must be used whenever [[Alpine Package Keeper]] is used.		Local backup utility({{ic\|lbu}}) is the Alpine Linux tool to manage [[Diskless Mode]] installations. For these installations, {{ic\|lbu}} tool must be used to [[#Committing changes\|commit the changes]] whenever [[Alpine Package Keeper]] is used.

	When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. ~~by [[Alpine_Package_Keeper\|~~installing a package]] or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved to an overlay file (.apkovl) that can be automatically loaded when booting, to restore the saved state.		When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. installing a package or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved with {{ic\|lbu}} tool to an overlay file i.e [[Diskless Mode#Apkovl\|apkovl]] file that can be automatically loaded when booting, to restore the saved state.

	The .apkovl file that contains the custom configuration can be saved to writable storage with Alpine's local backup utility <code>lbu</code>. By configuring a [[Local APK cache\|local package cache]] the additional packages the configuration depends on, can also be kept available on local, writable storage.		By default, an {{ic\|lbu commit}} only stores modifications below {{Path\|/etc}}, with the exception of the {{Path\|/etc/init.d/}} directory. If a user was created during the {{ic\|setup-alpine}} script, that user's home directory is also added to the paths that <code>lbu</code> will backup up. However, [[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]] enables modifying that set of included files, and can be used to specify additional files or folders.

	By default, an ~~<code>~~lbu commit~~</code>~~ only stores modifications below {{Path\|/etc}}, with the exception of the {{Path\|/etc/init.d/}} directory. If a user was created during the ~~<code>~~setup-alpine~~</code>~~ script, that user's home directory is also added to the paths that <code>lbu</code> will backup up. However, [[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]] enables modifying that set of included files, and can be used to specify additional files or folders.

	== Overview ==		== Overview ==
Line 102:		Line 100:
	</pre>		</pre>

	~~=== Creating and saving an apkovl from a remote host ===~~		To create an apkovl from a client on a remote server, it's possible to use <code>lbu package</code> via SSH with {{Path\|-}} as the apkovl name on the server:{{Cmd\|ssh root@client "lbu package -" > client.apkovl.tar.gz}}

	To create an apkovl from a client on a remote server, it's possible to use <code>lbu package</code> via SSH with {{Path\|-}} as the apkovl name:

	~~On the server:~~
	~~<pre>~~
	~~ssh root@client "lbu package -" >client.apkovl.tar.gz~~
	~~</pre>~~

	~~=== Saving and loading ISO image customizations ===~~
	~~{{Main\|Diskless Mode}}~~
	~~The content from this section has been moved [[Diskless Mode#Installation\|here]].~~
	~~<!-- This heading is retained here as certain bug reports refer this heading. -->~~
	== Checking what will be added to your apkovl ==		== Checking what will be added to your apkovl ==

Line 138:		Line 125:

	== Include special files/folders to the apkovl ==		== Include special files/folders to the apkovl ==

	Assume you have some files you want to save permanently, but they are not located in {{Path\|/etc}}.<BR>		Assume you have some files you want to save permanently, but they are not located in {{Path\|/etc}}.<BR>
	e.g. {{Path\|/root/.ssh/authorized_keys}} (used by <code>sshd</code> to authenticate ssh-users). Such files/folders can be added to lbu's ''include'' list with the following command:		e.g. {{Path\|/root/.ssh/authorized_keys}} (used by <code>sshd</code> to authenticate ssh-users). Such files/folders can be added to lbu's ''include'' list with the following command:
Line 151:		Line 139:
	</pre>		</pre>

	{{Note\|This information used to be maintained in {{Path\|/etc/lbu/include}}. Now it's maintained together with the ''exclude'' list in {{Path\|/etc/apk/protected_paths.d/lbu.list}}. Either way, the command <code>lbu include</code> only modifies lbu's configuration.		{{Note\|This information used to be maintained in {{Path\|/etc/lbu/include}}. Now it's maintained together with the ''exclude'' list in {{Path\|/etc/apk/protected_paths.d/lbu.list}}. Either way, the command <code>lbu include</code> only modifies lbu's configuration. You will need to run <code>lbu commit</code> to actually create/modify your apkovl.}}
	You will need to run <code>lbu commit</code> to actually create/modify your apkovl.}}


			== Exclude specific files/folders from the apkovl ==

	~~== Exclude specific files/folders from the apkovl ==~~
	Assume you have some files located in {{Path\|/etc}} or one of its subfolders you ''do not'' want to save.		Assume you have some files located in {{Path\|/etc}} or one of its subfolders you ''do not'' want to save.
	It could be a log file or status file that for some reason isn't in {{Path\|/var/log/}} but in a location that would otherwise be tracked by <code>lbu</code>.		It could be a log file or status file that for some reason isn't in {{Path\|/var/log/}} but in a location that would otherwise be tracked by <code>lbu</code>.
Line 169:		Line 155:
	-v Verbose mode.		-v Verbose mode.
	</pre>		</pre>
	{{Note\|As stated above, this information is now maintained in {{Path\|/etc/apk/protected_paths.d/lbu.list}}. The command <code>lbu exclude</code> also only modifies lbu's configuration. ~~<br>~~		{{Note\|As stated above, this information is now maintained in {{Path\|/etc/apk/protected_paths.d/lbu.list}}. The command <code>lbu exclude</code> also only modifies lbu's configuration. You will need to run <code>lbu commit</code> to actually create/modify your apkovl.}}
	You will need to run <code>lbu commit</code> to actually create/modify your apkovl.}}

			== Multiple backup versions ==

			Lbu can keep multiple backups so you can revert back to older configurations. Set BACKUP_LIMIT in {{Path\|/etc/lbu/lbu.conf}} to the number of backups you want to keep. Based on BACKUP_LIMIT, the previously active .apkovl will be renamed before creating the new file.

			You can list the currently available backups and revert to an older one with the following commands:{{Cmd\|<nowiki># lbu list-backup [<media>]
			# lbu revert <filename> [<media>]</nowiki>}}

			Nothing is changed on your running system when "reverting", it only affects which apkovl is loaded at the next boot.

			== Saving and loading ISO image customizations ==
			<!-- This heading is retained here as certain bug reports refer this heading. -->
			ISO boot images can save running states to [[Diskless Mode#Using an internal disk for persistent storage\|system partitions]] and automatically loaded when booting the ISO boot image.

	== Execute a script as part of a backup ==		== Execute a script as part of a backup ==
Line 187:		Line 183:
	=== Example ===		=== Example ===

	Rather than adding the raw database directories to {{Path\|/etc/lbu/include}}, you can do a "database dump". e.g. {{Pkg\|postgresql}}:		Rather than adding the raw database directories to {{Path\|/etc/lbu/include}}, you can do a "database dump". e.g. {{Pkg\|postgresql}}:

	* Create {{Path\|/etc/lbu/pre-package.d/sqldump}} with the following contents: <pre>pg_dumpall -U postgres \| gzip -c >/root/pgdatabases.gz</pre>		* Create {{Path\|/etc/lbu/pre-package.d/sqldump}} with the following contents: <pre>pg_dumpall -U postgres \| gzip -c >/root/pgdatabases.gz</pre>
Line 199:		Line 195:

	On a catastrophic restore, the databases are not automatically restored (that's not lbu's job), but you will find a complete database dump in the {{Path\|/root}} directory, where it can be restored manually.		On a catastrophic restore, the databases are not automatically restored (that's not lbu's job), but you will find a complete database dump in the {{Path\|/root}} directory, where it can be restored manually.


	P.s. These scripts are also launched when starting the commands: diff, list-backup, package, revert, status.		P.s. These scripts are also launched when starting the commands: diff, list-backup, package, revert, status.

	== ~~Multiple backup versions~~ ==		== See also ==
	~~Lbu can now keep multiple backups so you can revert back to older configurations.~~
	~~Set BACKUP_LIMIT in {{Path\|/etc/lbu/lbu.conf}} to the number of backups you want~~
	~~to keep.~~

	~~If you've set BACKUP_LIMIT, then the previously active .apkovl will be renamed before creating the new file.~~		* [Diskless Mode]]

	~~You can list the currently available backups with:~~

	~~{{Cmd\|lbu list-backup~~ [~~<media>~~]}}

	~~and you can revert to an older one with:~~

	~~{{Cmd\|lbu revert <filename> [<media>~~]}}

	~~NOTE: Nothing is changed on your running system when "reverting", it only affects which apkovl is considered active at the next boot.~~


	~~== See also ==~~
	* [[Back Up a Flash Memory Installation]]		* [[Back Up a Flash Memory Installation]]
	* [[Manually editing a existing apkovl]]		* [[Manually editing a existing apkovl]]

	[[Category:Installation]]		[[Category:Installation]]

	[[Category:Booting]]		[[Category:Booting]]
	[[Category:Package Manager]]		[[Category:Package Manager]]
	[[category: Diskless]]		[[category: Diskless]]

Prabuanand: fixed wikitags

2025-02-10T16:00:24Z

fixed wikitags

← Older revision		Revision as of 16:00, 10 February 2025
Line 26:		Line 26:
	\| lbu list		\| lbu list
	\| lbu ls		\| lbu ls
	\| Lists files that would go to tar package. Same as: 'lbu package -v /dev/null'		\| Lists files that would go to tar package. Same as: {{Codeline\|lbu package -v /dev/null}}
	\|-		\|-
	\| lbu diff		\| lbu diff
Line 34:		Line 34:
	\| lbu include		\| lbu include
	\| lbu inc or lbu add		\| lbu inc or lbu add
	\| Add filename(s) to include list (/etc/apk/protected_paths.d/lbu.list)		\| Add filename(s) to include list{{Path\|/etc/apk/protected_paths.d/lbu.list}}
	\|-		\|-
	\| lbu exclude		\| lbu exclude

Prabuanand: formatted lbu commands, changed introduction line and headings

2025-02-10T15:55:15Z

formatted lbu commands, changed introduction line and headings

← Older revision		Revision as of 15:55, 10 February 2025
Line 1:		Line 1:
	Local backup utility(<code>lbu</code>) is the tool to manage [[Diskless Mode]] ~~in Alpine Linux~~. ~~This~~ tool must be used ~~along with~~ [[Alpine Package Keeper]] ~~for managing the system~~.		Local backup utility(<code>lbu</code>) is the Alpine Linux tool to manage [[Diskless Mode]] installations. For these installations, <code>lbu</code> tool must be used whenever [[Alpine Package Keeper]] is used.

	When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. by [[Alpine_Package_Keeper\|installing a package]] or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved to an overlay file (.apkovl) that can be automatically loaded when booting, to restore the saved state.		When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. by [[Alpine_Package_Keeper\|installing a package]] or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved to an overlay file (.apkovl) that can be automatically loaded when booting, to restore the saved state.

	The .apkovl file that contains the custom configuration can be saved to writable storage with Alpine's local backup utility <code>lbu</code>. By configuring a [[~~Alpine_Linux_package_management#Local_Cache~~\|local package cache]] the additional packages the configuration depends on, can also be kept available on local, writable storage.		The .apkovl file that contains the custom configuration can be saved to writable storage with Alpine's local backup utility <code>lbu</code>. By configuring a [[Local APK cache\|local package cache]] the additional packages the configuration depends on, can also be kept available on local, writable storage.

	By default, an <code>lbu commit</code> only stores modifications below {{Path\|/etc}}, with the exception of the {{Path\|/etc/init.d/}} directory. If a user was created during the <code>setup-alpine</code> script, that user's home directory is also added to the paths that <code>lbu</code> will backup up. However, [[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]] enables modifying that set of included files, and can be used to specify additional files or folders.		By default, an <code>lbu commit</code> only stores modifications below {{Path\|/etc}}, with the exception of the {{Path\|/etc/init.d/}} directory. If a user was created during the <code>setup-alpine</code> script, that user's home directory is also added to the paths that <code>lbu</code> will backup up. However, [[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]] enables modifying that set of included files, and can be used to specify additional files or folders.
Line 10:		Line 10:

	The <code>lbu</code> tool has several subcommands to manage the .apkovl:		The <code>lbu</code> tool has several subcommands to manage the .apkovl:
	* lbu		{\|
	* lbu commit ~~''(Same as '~~lbu ci~~')''~~		\|-
	* lbu package ~~''(Same as '~~lbu pkg~~')''~~		\| lbu commit
	* lbu status ~~''(Same as '~~lbu st~~')''~~		\| lbu ci
	* lbu list ~~''(~~Same as 'lbu ~~ls')'~~'		\| Create a backup of config to writeable media
	* lbu diff		\|-
	* lbu include ~~''(Same as '~~lbu inc' or 'lbu add')''		\| lbu package
	* lbu exclude ~~''(Same as '~~lbu ex' or 'lbu delete')''		\| lbu pkg
	* lbu list-backup ~~''(Same as '~~lbu lb~~')''~~		\| Create backup package
	* lbu revert		\|-
			\| lbu status
			\| lbu st
			\| Check what files have been changed since last commit
			\|-
			\| lbu list
			\| lbu ls
			\| Lists files that would go to tar package. Same as: 'lbu package -v /dev/null'
			\|-
			\| lbu diff
			\|
			\| Run a diff against last commit
			\|-
			\| lbu include
			\| lbu inc or lbu add
			\| Add filename(s) to include list (/etc/apk/protected_paths.d/lbu.list)
			\|-
			\| lbu exclude
			\| lbu ex or lbu delete
			\| Add filename(s) to exclude list {{Path\|/etc/apk/protected_paths.d/lbu.list}}
			\|-
			\| lbu list-backup
			\| lbu lb
			\| Show old commits
			\|-
			\| lbu revert
			\|
			\|Revert to older commit
			\|-
			\|}

	In the examples below, you will find some characters with special meaning:		In the examples below, you will find some characters with special meaning:
Line 26:		Line 55:

	== Committing changes ==		== Committing changes ==

	~~=== Basic commit ===~~

	When you "commit" or save changes you've made to your system, <code>lbu</code> will generate a file named something like {{Path\|<var>myboxname</var>.apkovl.tar.gz}} ''('myboxname' will be the same as the hostname)''.		When you "commit" or save changes you've made to your system, <code>lbu</code> will generate a file named something like {{Path\|<var>myboxname</var>.apkovl.tar.gz}} ''('myboxname' will be the same as the hostname)''.
Line 55:		Line 82:
	</pre>		</pre>

	=== Creating an .apkovl "package" elsewhere than on the configured media ===		== Creating an .apkovl "package" elsewhere than on the configured media ==

	To "commit" changes, but override the destination of the generated apkovl file, use <code>lbu package</code> instead of <code>lbu commit</code>:		To "commit" changes, but override the destination of the generated apkovl file, use <code>lbu package</code> instead of <code>lbu commit</code>:
Line 86:		Line 113:
	=== Saving and loading ISO image customizations ===		=== Saving and loading ISO image customizations ===
	{{Main\|Diskless Mode}}		{{Main\|Diskless Mode}}
	The content ~~present here~~ has been moved to [[Diskless Mode]]. This heading is retained here as certain bug reports refer this heading.		The content from this section has been moved [[Diskless Mode#Installation\|here]].
			<!-- This heading is retained here as certain bug reports refer this heading. -->
	== Checking what will be added to your apkovl ==		== Checking what will be added to your apkovl ==

Prabuanand: re-arranged headings, added introduction line, removed warning and notes

2025-02-10T02:51:14Z

re-arranged headings, added introduction line, removed warning and notes

← Older revision		Revision as of 02:51, 10 February 2025
Line 1:		Line 1:
	~~When~~ Alpine Linux ~~boots in diskless mode, it initially only loads a few required packages from~~ the ~~boot device~~.		Local backup utility(<code>lbu</code>) is the tool to manage [[Diskless Mode]] in Alpine Linux. This tool must be used along with [[Alpine Package Keeper]] for managing the system.

	However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. by [[Alpine_Package_Keeper\|installing a package]] or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved to an overlay file (.apkovl) that can be automatically loaded when booting, to restore the saved state.		When Alpine Linux boots in diskless mode, it initially only loads a few required packages from the boot device. However, local adjustments to what-gets-loaded-into-RAM are possible, e.g. by [[Alpine_Package_Keeper\|installing a package]] or adjusting the configuration files in {{path\|/etc}}. The modifications can be saved to an overlay file (.apkovl) that can be automatically loaded when booting, to restore the saved state.

	The .apkovl file that contains the custom configuration can be saved to writable storage with Alpine's local backup utility <code>lbu</code>. By configuring a [[Alpine_Linux_package_management#Local_Cache\|local package cache]] the additional packages the configuration depends on, can also be kept available on local, writable storage.		The .apkovl file that contains the custom configuration can be saved to writable storage with Alpine's local backup utility <code>lbu</code>. By configuring a [[Alpine_Linux_package_management#Local_Cache\|local package cache]] the additional packages the configuration depends on, can also be kept available on local, writable storage.

	~~{{Note\|If you installed Alpine in "sys" disk mode~~, ~~you don't need to use~~ <code>lbu</code> ~~to save~~ the ~~system state~~. ~~With~~ a ~~system disk~~, ~~all modifications are~~		By default, an <code>lbu commit</code> only stores modifications below {{Path\|/etc}}, with the exception of the {{Path\|/etc/init.d/}} directory. If a user was created during the <code>setup-alpine</code> script, that user's home directory is also added to the paths that <code>lbu</code> will backup up. However, [[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]] enables modifying that set of included files, and can be used to specify additional files or folders.
	~~written directly~~ to ~~disk. Nevertheless,~~ <code>lbu</code> can be ~~useful for some maintenance tasks~~.}}

			== Overview ==
	~~__TOC__~~


	~~{{Warning\|~~
	~~'''By default, an <code>lbu commit</code> only stores modifications below {{Path\|/etc}}''', with the exception of the {{Path\|/etc/init.d/}} directory.~~

	~~If a user was created during the <code>setup-alpine</code> script, that user's home directory is also added to the paths that <code>lbu</code> will backup up.~~

	~~However, [[#Include_special_files.2Ffolders_to_the_apkovl\|lbu include]] enables modifying that set of included files, and can be used to specify additional files or folders.~~
	}}


	== ~~Saving and loading ISO image customizations ==~~
	~~{{Main\|Diskless Mode}}~~

	~~== Committing changes~~ ==

	The <code>lbu</code> tool has several subcommands to manage the .apkovl:		The <code>lbu</code> tool has several subcommands to manage the .apkovl:
Line 42:		Line 25:
	* '''[ ]''' = '''optional''' ''(In 'lbu commit\|ci [-nv]' you can skip the '-n', '-v' or '-nv' part if you don't want it)''		* '''[ ]''' = '''optional''' ''(In 'lbu commit\|ci [-nv]' you can skip the '-n', '-v' or '-nv' part if you don't want it)''

			== Committing changes ==

			=== Basic commit ===

	~~=== Basic "commit" command ===~~
	When you "commit" or save changes you've made to your system, <code>lbu</code> will generate a file named something like {{Path\|<var>myboxname</var>.apkovl.tar.gz}} ''('myboxname' will be the same as the hostname)''.		When you "commit" or save changes you've made to your system, <code>lbu</code> will generate a file named something like {{Path\|<var>myboxname</var>.apkovl.tar.gz}} ''('myboxname' will be the same as the hostname)''.
	The file (which contains your modifications) is called your "apkovl".		The file (which contains your modifications) is called your "apkovl".
Line 98:		Line 83:
	ssh root@client "lbu package -" >client.apkovl.tar.gz		ssh root@client "lbu package -" >client.apkovl.tar.gz
	</pre>		</pre>

			=== Saving and loading ISO image customizations ===
			{{Main\|Diskless Mode}}
			The content present here has been moved to [[Diskless Mode]]. This heading is retained here as certain bug reports refer this heading.

	== Checking what will be added to your apkovl ==		== Checking what will be added to your apkovl ==
Line 203:		Line 192:

	NOTE: Nothing is changed on your running system when "reverting", it only affects which apkovl is considered active at the next boot.		NOTE: Nothing is changed on your running system when "reverting", it only affects which apkovl is considered active at the next boot.


	== See also ==		== See also ==

Prabuanand: replaced category: LBU by category: Diskless as diskless is more generic

2024-11-06T07:05:25Z

replaced category: LBU by category: Diskless as diskless is more generic

← Older revision		Revision as of 07:05, 6 November 2024
Line 212:		Line 212:
	[[Category:Booting]]		[[Category:Booting]]
	[[Category:Package Manager]]		[[Category:Package Manager]]
	[[category: ~~LBU~~]]		[[category: Diskless]]

Prabuanand: Moved the content from here to Diskless Mode page. Retaining the place holder as bugs in gitlab refer this heading

2024-11-03T11:39:53Z

Moved the content from here to Diskless Mode page. Retaining the place holder as bugs in gitlab refer this heading

@@ Line 22: / Line 22: @@
 == Saving and loading ISO image customizations ==
+{{Main|Diskless Mode}}
 == Committing changes ==