You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the partitioning sub-menu, select the 2nd option "Manually partition ..."
The output of the partitioning tool (cfdisk or cgdisk) ends up in the log file /tmp/pentoo-installer.log
The 'source' of the problem seems to be in sbin/pentoo-installer:
2> /tmp/pentoo-installer.log
if I remove that and remove redirection where cgdisk is called, then cgdisk starts working. But having no log file is no option!
My options:
replace that 2>log-file with tee
Some scary process substitution and file redirection and cgdisk shows, but output is slightly borken and keyboard input does not work.
Find out why vim/nano work in system config ... if they do, cgdisk should too.
Drop support for manual partitioning.
Seriously, anyone doing that should be able to do it outside installer. Plus cgdisk/cfdisk are the last tools I would use, only reason I kept them in the installer is cause i thought 'parted' was to complicated. But parted does not work for the same reason.
Let user edit some json config that I'm preparing to have installer run form config-file ... don't think we want that either.
The text was updated successfully, but these errors were encountered:
Without all the:
CONFIG_LIST="$(script)"
that lead to the partition_manual file (2), it works.
But that's the way installer was designed, write CONFIG_LIST to STDOUT, not to a file.
Reason: that list may contain sensitive info to remount partitions.
==> we could move that manual partitioning part to main-menu, then it does not need to return anything.
In the partitioning sub-menu, select the 2nd option "Manually partition ..."
The output of the partitioning tool (cfdisk or cgdisk) ends up in the log file /tmp/pentoo-installer.log
The 'source' of the problem seems to be in sbin/pentoo-installer:
if I remove that and remove redirection where cgdisk is called, then cgdisk starts working. But having no log file is no option!
My options:
replace that 2>log-file with tee
Some scary process substitution and file redirection and cgdisk shows, but output is slightly borken and keyboard input does not work.
Find out why vim/nano work in system config ... if they do, cgdisk should too.
Drop support for manual partitioning.
Seriously, anyone doing that should be able to do it outside installer. Plus cgdisk/cfdisk are the last tools I would use, only reason I kept them in the installer is cause i thought 'parted' was to complicated. But parted does not work for the same reason.
Let user edit some json config that I'm preparing to have installer run form config-file ... don't think we want that either.
The text was updated successfully, but these errors were encountered: