Mirko Vogt 439a869090 Do not overload mount-call - trying to reduce confusion ... The behaviour of calling 'mount' differed depending on whether it called the busybox-mount, the mount of util-linux, the mount defined in /lib/functions.sh and /lib/functions/boot.sh /etc/preinit even included /lib/functions.sh and /lib/functions/boot.sh, both re-defining 'mount'. SVN-Revision: 34792		2012-12-19 16:07:46 +00:00
..
05_firstboot_skip	base-files: fix typo in 05_firstboot_skip script (#11359)	2012-04-27 16:49:16 +00:00
10_determine_parts
10_no_fo_clear_overlay
10_reset_has_mini_fo	base-files: add initial support for mounting overlayfs	2011-03-17 19:09:39 +00:00
20_has_mini_fo	base-files: add initial support for mounting overlayfs	2011-03-17 19:09:39 +00:00
20_no_fo_mount_jffs	Do not overload mount-call - trying to reduce confusion	2012-12-19 16:07:46 +00:00
20_reset_clear_jffs
30_is_rootfs_mounted	Do not overload mount-call - trying to reduce confusion	2012-12-19 16:07:46 +00:00
30_no_fo_pivot	change from /jffs to /overlay, patch from Daniel Dickinson	2010-03-21 17:16:50 +00:00
30_reset_copy_rom
40_copy_ramoverlay	change from /jffs to /overlay, patch from Daniel Dickinson	2010-03-21 17:16:50 +00:00
40_no_fo_copy_ramoverlay
50_pivot	change from /jffs to /overlay, patch from Daniel Dickinson	2010-03-21 17:16:50 +00:00
99_10_no_fo_cleanup	change from /jffs to /overlay, patch from Daniel Dickinson	2010-03-21 17:16:50 +00:00
99_10_with_fo_cleanup	base-files: overlayfs whiteouts depend on a specific xattr entry, which does not get preserved by the tmpfs->overlay copy. work around this by cleaning all copied "(overlay-whiteout)" symlinks after the switch to jffs2	2011-03-17 19:09:43 +00:00