>Edward Welbon wrote:
>>
>> In 2.1.45, it seems that "chmod -R ..." causes a hard reset. in 2.1.42,
>> "chmod -R ..." is ok. I tried twice. It seems that something like
>> "find . -exec chmod ..." will also cause a reboot.
>
>I tried some chmod -R commands under 2.1.46-1 and didn't have any
>problems -- not sure whether it's fixed or I didn't try it on the right
>directory structure.
>
>Did the directory you tried it on have some sort of odd structure?
I am using [2.1.45].
I didn't tried to chown -R, but I am getting problems tring to install
debian packages that made a lot of symlinks (such us library packages).
The problem maybe caused when the dpkg try to chown a symlink or overwrite
a symlink or so on. I get a lot of *.dpkg-new files that should be
renamed without the ".dpkg-new" part of the filename.
This is a interesting part of a "strace -f -o out dpkg -i e2fsprogs[snip].deb"
launched using [2.1.42]. I didn' t tried a strace with
[2.1.45] but if anyone need more info I will try it.
[..]
1851 symlink("../../lib/libext2fs.so.2.3", "/usr/lib/libext2fs.so.dpkg-new") = 0
1851 chown("/usr/lib/libext2fs.so.dpkg-new", 0, 0) = 0
1851 readlink("/usr/lib/libext2fs.so", "../../lib/libext2fs.so.2.3", 480) = 26
1851 symlink("../../lib/libext2fs.so.2.3", "/usr/lib/libext2fs.so.dpkg-tmp") = 0
1851 chown("/usr/lib/libext2fs.so.dpkg-tmp", 0, 0) = 0
1851 rename("/usr/lib/libext2fs.so.dpkg-new", "/usr/lib/libext2fs.so") = 0
[..]
Doing these kernel syscall the script don' t work fine.
With [2.1.42] all works fine.
Andrea Arcangeli