I am going to mount /mnt/runtime without a loopback so the parameter will
actually be NULL.
---
loader/method.c | 23 +++++++++++++----------
1 files changed, 13 insertions(+), 10 deletions(-)
diff --git a/loader/method.c b/loader/method.c
index d6f83e6..969a47e 100644
--- a/loader/method.c
+++ b/loader/method.c
@@ -62,16 +62,20 @@ extern uint64_t flags;
int umountLoopback(char * mntpoint, char * device) {
int loopfd;
-
/* copies a second stage from fd to dest and mounts on mntpoint */
int copyFileAndLoopbackMount(int fd, char * dest, char * device, char * mntpoint,
progressCB pbcb, struct progressCBdata *data,
--
1.6.6
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
04-09-2010, 11:17 AM
Martin Sivak
umountLoopback() now accepts NULL as device.
Well, but why to put this in umountLoopback at all? Don't we have separate umount call? And if this is here because we call this to umount stage2 and we need to decide how we mounted it, then the decision logic should be in the caller function and not here.