summaryrefslogtreecommitdiff
path: root/src/core
diff options
context:
space:
mode:
authorDieter Plaetinck <dieter@plaetinck.be>2008-12-15 20:24:32 +0100
committerDieter Plaetinck <dieter@plaetinck.be>2008-12-15 20:24:32 +0100
commitd54de104aa30ac02e45b41886da2d58285d993d5 (patch)
tree49cb9589b3408722d0771375f68289100469f1e5 /src/core
parentbe7f9233acf0a978334445a445c7216b2d9185f9 (diff)
todo updates
Diffstat (limited to 'src/core')
-rw-r--r--src/core/libs/lib-ui-interactive.sh4
-rw-r--r--src/core/libs/lib-ui.sh2
2 files changed, 3 insertions, 3 deletions
diff --git a/src/core/libs/lib-ui-interactive.sh b/src/core/libs/lib-ui-interactive.sh
index 0f4af3a..8241996 100644
--- a/src/core/libs/lib-ui-interactive.sh
+++ b/src/core/libs/lib-ui-interactive.sh
@@ -386,7 +386,7 @@ interactive_filesystem ()
# Cascading remove theoretical blockdevice(s), if relevant ( eg if we just changed from vg->ext3, dm_crypt -> fat, or if we changed the label of a FS, causing a name change in a dm_mapper device)
- if [[ $old_fs_type = lvm-* || $old_fs_type = dm_crypt ]] && [ "$NEW_FILESYSTEM" = no_fs -o "$old_fs_type" != "$fs_type" -o "$old_fs_label" != "$fs_label" ]
+ if [[ $old_fs_type = lvm-* || $old_fs_type = dm_crypt ]] && [ "$NEW_FILESYSTEM" = no_fs -o "$old_fs_type" != "$fs_type" -o "$old_fs_label" != "$fs_label" ] #TODO: deletion doesn't work when you delete an lvm LV, maybe otherwise too
then
target=
[ "$old_fs_type" = lvm-vg ] && target="/dev/mapper/$old_fs_label $old_fs_type $old_fs_label"
@@ -474,7 +474,7 @@ interactive_filesystems() {
fi
fi
else
- # an existing LV will be edited and it's settings updated
+ # an existing LV will be edited and it's settings updated #TODO: if we have 2 LV's, and we delete one, the result is twice the other lv
for lv in `sed 's/|/ /g' <<< $fs`
do
label=$(cut -d ';' -f 6 <<< $lv)
diff --git a/src/core/libs/lib-ui.sh b/src/core/libs/lib-ui.sh
index f7fd42c..09e6646 100644
--- a/src/core/libs/lib-ui.sh
+++ b/src/core/libs/lib-ui.sh
@@ -66,7 +66,7 @@ notify ()
# You can keep several "lists of successive things" by grouping them with <listname>
# this is somewhat similar to follow_progress. Note that this list isn't cleared unless you set $3 to 1. default 0. (optional).
# $3 0/1 this is the last one of the group of several things (eg clear buffer). default 0. (optional)
-infofy ()
+infofy () #TODO: when using successive things, the screen can become full and you only see the old stuff, not the new
{
successive=${2:-0}
succ_last=${3:-0}