Bug#1000239: Rescue system won't find root partition, but insists on /usr
In commercial and industrial applications It is common to have discrete partitions for /, /boot, /home, /usr swap and /var. The rationale for doing so lies in three areas. /var can and does fill up with log files frequently. Having it separate has long been a means to prevent / from filling up, and to permit resizing /var without taking down the system.
Many times hardware failure will destroy a partition, and it's much less work to recover if 'everything' does not reside on a single partition. Judicious use of disk space dictatates splitting large disks into smaller partitions, which function more efficiently.
If there is a /usr partition, /usr/share will be part of it. So, separate /usr/share is exactly as common s/as separate /usr. For home use none of this matters, because it is trivial to reinstall the OS. Although, my personal lappy has five partitions on the disk.
/usr/share has architecture independent files which are architecture independent only because they are not binaries. No documentation is architecture dependent! The reader may be, but not the actual documentation, as is found in /usr/share/.
-------- Original Message --------
From: Pascal Hambourg <firstname.lastname@example.org>
Sent: December 8, 2021 11:41:11 AM UTC
To: Philip Hands <email@example.com>, firstname.lastname@example.org, TomK <email@example.com>
Subject: Re: Bug#1000239: Rescue system won't find root partition, but insists on /usr
Le 08/12/2021 à 10:49, Philip Hands a écrit :
> Is it a problem if /home or /usr/share are left unmounted during rescue?
/usr/share contains architecture-independent files for many programs
such as bash, grub, os-prober, debconf, dpkg, initramfs-tools...
How common is it to have a separate /usr/share and what is the rationale
for it ?