From 662edb6e7ddc01ffee53ffb320acd45e1814c10a Mon Sep 17 00:00:00 2001 From: Artem Bityutskiy Date: Mon, 4 Jul 2011 09:48:37 +0300 Subject: 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 --- feature-removal-schedule.txt | 23 ----------------------- 1 file changed, 23 deletions(-) (limited to 'feature-removal-schedule.txt') 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. - ---------------------------- -- cgit v1.2.3