[Bug 1762920] Re: casper-helpers:try_mount doesn't honor the mount point
Tomo
1762920 at bugs.launchpad.net
Fri Apr 13 01:21:43 UTC 2018
** Description changed:
I apologize for direct mentioning to the source codes.
Problem:
- try_mount() in casper-helpers script doesn't honor the mount-point parameter when mount-option != "ro".
- This is obvious on code, but it wouldn't what it meant to be.
- I guess,
- if the device is already mounted on A, and
- if the indicated mount point of which is the same as previous mounted (i.e. A; where_is_mounted() says),
- do mount -o remount ...
- else
- do mount -o bind ...
- whatever the indicated mount options are.
+ try_mount() in casper-helpers script doesn't honor the mount-point parameter when mount-option != "ro".
+ This is obvious on code, but it wouldn't what it meant to be.
+ I guess,
+ if the device is already mounted on A, and
+ if the indicated mount point of which is the same as previous mounted (i.e. A; where_is_mounted() says),
+ do mount -o remount ...
+ else
+ do mount -o bind ...
+ whatever the indicated mount options are.
- This spec suffers in the case,
- setting persistence YES, boot media, especially USB, is multi-partitioned, and persistence data are on separated part from the base boot image.
- In that case, find_cow_device() falsely unmount /cdrom (because where_is_mounted() says '/cdrom' was
- previous mount point in the device searching iteration) and gone busybox prompt.
- There might be a fix find_cow_device() itself but, I thought that try_mount() is fundamental.
+ This spec suffers in the case,
+ setting persistence YES, boot media, especially USB, is multi-partitioned, and persistence data are on separated part from the base boot image.
+ In that case, find_cow_device() falsely unmount /cdrom (because where_is_mounted() says '/cdrom' was
+ previous mount point in the device searching iteration) and gone busybox prompt.
+ There might be a fix find_cow_device() itself but, I thought that try_mount() is fundamental.
A patch attached is a sample to solve this.
+
+ Notice:
+ An attached patch was from my own fixed version, and contains find_cow_device() modification. Be careful when applying.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1762920
Title:
casper-helpers:try_mount doesn't honor the mount point
Status in casper package in Ubuntu:
New
Bug description:
I apologize for direct mentioning to the source codes.
Problem:
try_mount() in casper-helpers script doesn't honor the mount-point parameter when mount-option != "ro".
This is obvious on code, but it wouldn't what it meant to be.
I guess,
if the device is already mounted on A, and
if the indicated mount point of which is the same as previous mounted (i.e. A; where_is_mounted() says),
do mount -o remount ...
else
do mount -o bind ...
whatever the indicated mount options are.
This spec suffers in the case,
setting persistence YES, boot media, especially USB, is multi-partitioned, and persistence data are on separated part from the base boot image.
In that case, find_cow_device() falsely unmount /cdrom (because where_is_mounted() says '/cdrom' was
previous mount point in the device searching iteration) and gone busybox prompt.
There might be a fix find_cow_device() itself but, I thought that try_mount() is fundamental.
A patch attached is a sample to solve this.
Notice:
An attached patch was from my own fixed version, and contains find_cow_device() modification. Be careful when applying.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1762920/+subscriptions
More information about the foundations-bugs
mailing list