summaryrefslogtreecommitdiffstats
path: root/fs_mgr
Commit message (Collapse)AuthorAgeFilesLines
* am 7fd51b36: am b20fa762: Merge "Fix fs_mgr to properly invoke e2fsck on ↵Ken Sumrall2012-11-121-2/+2
|\ | | | | | | | | | | | | encrypted devices" into jb-mr1.1-dev * commit '7fd51b36dabedee4de159213237e71ba20865812': Fix fs_mgr to properly invoke e2fsck on encrypted devices
| * Fix fs_mgr to properly invoke e2fsck on encrypted devicesKen Sumrall2012-11-061-2/+2
| | | | | | | | Change-Id: Ie220f5cb7b614a48ec8afe66f4721ede3a368166
* | am cfd7c2a0: am 1c0c5250: Merge "Rename getline to fs_getline for fs_mgr"Elliott Hughes2012-09-261-3/+3
|\ \ | |/ |/| | | | | * commit 'cfd7c2a05166a3ff27b2145b007834408d95a2e0': Rename getline to fs_getline for fs_mgr
| * am 1c0c5250: Merge "Rename getline to fs_getline for fs_mgr"Elliott Hughes2012-09-261-3/+3
| |\ | | | | | | | | | | | | * commit '1c0c52503dcedff1a75775bf8bfffe7ec77b722b': Rename getline to fs_getline for fs_mgr
| | * Rename getline to fs_getline for fs_mgrIrina Tirdea2012-09-121-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fs_mgr defines its own version of getline and uses it internally. This leads to a build error if getline is also defined in bionic, since fs_mgr will see readline as defined internally. Rename getline in fs_mgr to a local name (fs_getline) so that there will no longer be any conflicts. This is needed it we want to add getline in bionic. Change-Id: I3a32be71a645e122629802d98ff8f9ab9c419e86 Signed-off-by: Irina Tirdea <irina.tirdea@intel.com>
* | | Support shared-subtree and bind mount flags.Jeff Sharkey2012-08-141-0/+6
|/ / | | | | | | | | Bug: 6925012 Change-Id: Id8d887d17c6b1b2f90cfd1a1de991ccaba730b7d
* | Mount/unmount filesystems before running e2fsckKen Sumrall2012-07-241-3/+24
|/ | | | | | | This works around a performance problem in the firmware of some emmc chips. Change-Id: Ia414b4604d11e47ce9cb3f86ac82602e081bb09e
* A filesystem manager library to mount filesystems for init.Ken Sumrall2012-05-015-0/+860
Instead of specifying in init what to mount, and having various hacks in init itself to deal with encryption, use a filesystem manager library to do the work, that can also be invoked by vold when mounting an encrypted volume. Keep all the magic filesystem info an a device specific fstab file. Change-Id: Ib988f1e4fb0638ba1d5fd98407fa6d8cf862aaca