Age | Commit message (Collapse) | Author |
|
|
|
As we are no longer setting the ROOT_OFFSET based on disk size,
I have removed the ROOT_OFFSET variable and the set_root_fstype
function.
|
|
The current parted command does not align the root partition as desired
by the `--align optimal` option. This is evident from this parted message:
"Warning: The resulting partition is not properly aligned for best performance."
Instead of setting the ROOT_OFFSET=64S or ROOT_OFFSET=1024S (> 10GB) we should
set it to 0%. This will result in optimal alignment regardless of disk size.
Source: https://unix.stackexchange.com/a/49274
|
|
|
|
Bug 7732
Restore installation section that makes disk label.
|
|
|
|
Need to pass correct offset for start of root partition
|
|
On tiny disks, then it doesn't make sense to waste space by offsetting
root partition. On big disks, it doesn't hurt and it allows for running
on SSD.
|
|
Parted has magic value '0%' which causes it to choose optimum
alignment (2048 on most disks).
|
|
Redo Bug 7038
The previous change did nothing; the alignment option only reports
alignment, it does not change values. Need to manually reserve space
before root partition.
|
|
Bug 7038
Align the created disk partition for both install-system and initial
install-image.
Note: can't fix existing systems where disk is already partitioned.
They will just have to suffer with poor performance.
|
|
(cherry picked from commit 5de8a194db56c51c9e5541cca43423f11534ffb7)
|
|
|
|
The -z test in shell needs to be quoted to avoid issues
with shell expansion.
|
|
|
|
Bug 5443
When running on HyperV, install-system appeared to hang because
although hda existed, it had no information so parted was prompting
for retry. Use the -s flag (never prompt) at all the places
in install-system/install-image where we don't want to have
user interaction.
|
|
|
|
On image-based systems, the Vyatta configuration is mounted on /config and
can be found in the disk filesystem under
/boot/<image-name>/live-rw/config.
|
|
|
|
|
|
|
|
This could fix Bug 5151
There was a typo in script that saved old config
|
|
If previous disk-based install is found, use config info from it. Otherwise
look for image-based installs. If multiple image-based installs are found,
let the user select which one to save the config information from.
|
|
|
|
Bug 5151
Part of previous change caused regression in saving config information.
Also mounts old config read-only to avoid any problems.
|
|
Similar to previous change to install-system
|
|
|
|
|