I have checked that when init runs chmod the sysfs entry is present. logwrapper says chmod finished with return value 0.
Further I created a oneshot service which does the chmod, but no luck Also I created a oneshot service which call a script and the script does the chmod, but no luck. If I run the same chmod command from console, It works fine. Any further inputs? -- Regards, Pratik Prajapati On Wed, Sep 21, 2011 at 6:56 AM, seba <sebastian.dr...@gmail.com> wrote: > Hi, > > it looks like the <sys fs file name> doesn't exist at a time > when init runs the chmod command. > > R, > Sebastian. > > On 20 Wrz, 18:06, Pratik Prajapati <pratik.prajap...@gmail.com> wrote: > > Hi, > > > > I'm doing below things in init.rc only. > > > > (1) > > on device-added-<device node path> > > chmod 777 <sys fs file name> > > > > (2) on boot > > chmod 777 <sys fs file name> > > > > But it does not work. > > > > -- > > Regards, > > Pratik Prajapati > > > > On Tue, Sep 20, 2011 at 8:58 AM, jagan <402ja...@gmail.com> wrote: > > > You can't give the permissions directly on android source. > > > We need to give the permissions on init.rc. > > > Better to read the file from system/core/init/readme.txt > > > > > Regards, > > > Jagan > > > > > On Tue, Sep 20, 2011 at 9:18 PM, Pratik Prajapati < > > > pratik.prajap...@gmail.com> wrote: > > > > >> Hi There, > > > > >> I'm setting permission to 777 (R+W+E for all) to a script file. But > after > > >> kernel built and flashed to the system, permission does not get > changed as > > >> expected. I understand I can give permission in make file while > creating > > >> filesystem to be flashed on system. But same thing is happening for > some > > >> sysfs entries. These sysfs entries are created by drivers at boot up > time. I > > >> have also tried > > > > >> on device-added-<device node path> > > >> chmod 777 <sys fs file name> > > > > >> But I can not set the mode by this method also. However on console > (adb > > >> shell) i can change the permission. I'm running on 2.1 > > > > >> Any idea, what could be wrong? > > > > >> Regards, > > >> Pratik > > > > >> -- > > >> unsubscribe: android-kernel+unsubscr...@googlegroups.com > > >> website:http://groups.google.com/group/android-kernel > > > > > -- > > > unsubscribe: android-kernel+unsubscr...@googlegroups.com > > > website:http://groups.google.com/group/android-kernel > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
