diff options
author | Artem Bityutskiy <dedekind1@gmail.com> | 2011-07-04 09:48:37 +0300 |
---|---|---|
committer | Artem Bityutskiy <dedekind1@gmail.com> | 2011-07-04 09:48:37 +0300 |
commit | 662edb6e7ddc01ffee53ffb320acd45e1814c10a (patch) | |
tree | e7fad5729f9df47bff5c463eb8354f1f1f28569a /feature-removal-schedule.txt | |
parent | df1d8c90f634a200564ae21a76e9e6b84804d7fa (diff) |
mkfs.ubifs: remove root inode squash feature
Remove the -squash-rino-perm mkfs.ubifs option as this was planned. Remove
the corresponding record from the feature-removal-schedule.txt file.
Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
Diffstat (limited to 'feature-removal-schedule.txt')
-rw-r--r-- | feature-removal-schedule.txt | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/feature-removal-schedule.txt b/feature-removal-schedule.txt index 69a8155..ca8bb6c 100644 --- a/feature-removal-schedule.txt +++ b/feature-removal-schedule.txt @@ -3,26 +3,3 @@ removed in the mtd-utils source tree. Every entry should contain what exactly is going away, why it is happening, and who is going to be doing the work. When the feature is removed from the utils, it should also be removed from this file. - ---------------------------- -1. Kill --squash-rino-perm and --nosquash-rino-perm parameters of mkfs.ubifs. - -Originally, mkfs.ubifs did not have these parameters, and it always set -permissions for the UBIFS root inode to be {uid=gid=root, u+rwx,go+rx}. This was -a bug which was found too late, when mkfs.ubifs had already been used in -production. To fix this bug, 2 new options were introduced: ---squash-rino-perm which preserves the old behavior and --nosquash-rino-perm -which makes mkfs.ubifs use the right permissions for the root -inode. - -For a while (releases 1.4.0-1.4.3) --squash-rino-perm was the default, and if -neither --squash-rino-perm nor --nosquash-rino-perm were used, -mkfs.ubifs printed a warning. This was introduced in mtd-utils-1.4.0 (13 Sep 2010). - -Now we have removed a warning and made --nosquash-rino-perm to be the -default. Also, both options are declared deprecated, so users should try -to stop using them. - -The further step is to remove both of them. - ---------------------------- |