Failing on e.g. "/dev/sda:512GB:scsi:512:512:gpt:ATA Samsung SSD 850:pmbr_boot;"
Fixed by only matching the device name when removing rpmb and boot devices
RE was added for MMC support in #9d1d032 and removes special MMC areas like
/dev/mmcblk0rmpb or /dev/mmcblk0boot1
I suspect the recursive calls were to work around the error caused by break
being called in a case statement which itself is within a while loop - the break
causes the while loop to terminate, bringing the installer to a grinding halt... whoops.
Now, menu_main() is called only from the main process loop, which we don't exit accidentally.
I've removed an entire case statement from do_install_quick() as this function either
performs an installation, or it doesn't - the case statement is pointless.
Due to the removal of whitespace, add ?w=1 in github.com when reviewing.
Remove the (at least on my system) broken repair/upgrade mode from
the installer. At the same time improve the formatting/wording of
some screens. Should be a bit simpler now.
This modifies the installer to use whiptail instead of dialog. Line drawing does not work without a proper locale. Create en_US.UTF-8 locale as part of the installer.
remove unused menu item, which breaks view log function
create empty log file, so view log function works prior to install
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
This reverts commit 2c7735709d.
it did not work. thanks to t-nelson for testing it..
1. Zotac ZBOX PI320 pico wants bootia32.efi not bootx32.efi
2. even with bootia32.efi (from syslinux) it doesnt boot. I suspect it requires pure 32bit kernel. no mixed mode ?
thank you zotac for creating such a mess.. damn it's almost y2k15
"Custom Install" is not install at all, it is there to be used for
upgrade / downgrade / repair. however, people are trying to use it
and get their disks not detected (which is expected)
so, make it clear what it does
add custom install where only KERNEL and SYSTEM files are copied to System partition, closes#1985
someone should go over the changes just to be sure that there is no errors
For some reason something made parted enter its interactive mode. Always
calling it with -s makes more sense anyway, and fixes that remaining issue
with never used blank 3TB drives I was still seeing.
