Re: How inode of /proc. /sys keep the same number on a given system

2017-11-08 Thread valdis . kletnieks
On Wed, 08 Nov 2017 21:22:47 +0300, Lev Olshvang said:
> Hello all,
>
> I observe that between reboot inode of files in /proc and /sys filesystem 
> keep the same number.
>
> I need to know whether I can rely on this in my program, and under what 
> conditions this assumption became incorrect?

If anything *at all* changes.  The machine reboots with a USB device plugged 
in. A race
condition during boot goes the other way for some reason. Daylight savings time 
has
changed.  Phase of the moon (and yes, I did once find an *actual* 'phase of the 
moon' bug :)

Relying on "My important file always has inode 93423" is a bad way to do things 
- why are
you doing that rather than using the pathname like 
/sys/whatever/my/important/file ?


pgpPChu7LGfPZ.pgp
Description: PGP signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


How inode of /proc. /sys keep the same number on a given system

2017-11-08 Thread Lev Olshvang
Hello all,

I observe that between reboot inode of files in /proc and /sys filesystem keep 
the same number.

I need to know whether I can rely on this in my program, and under what 
conditions this assumption became incorrect? 

Would inode number be the same on another system burned from the same image ?

I mean when I create 10 of embedded devices, will the inode  /proc of same 
files same between all devices?


Best regards,

Lev

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: Non-web based LXR

2017-11-08 Thread Mike Harless

François  wrote:

> On Tue, Oct 31, 2017 at 01:14:30PM +1100, Tobin C. Harding wrote:
> > So, thank you for your ideas. I'll consider this issue resolved by;
> > 
> > Use git grep
> > Use ctags/etags
> > Use free-electrons as a last resort
> 
> Also, there's a tool called cscope [1].
> There are also occurences of coccigrep [2] in the kernel.
> 
> [1] 
> https://courses.cs.washington.edu/courses/cse451/12sp/tutorials/tutorial_cscope.html
> [2] https://home.regit.org/software/coccigrep/

and another to add to the list is gscope, which is based off of cscope:

  * https://github.com/tefletch/gscope

--Mike

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: Non-web based LXR

2017-11-08 Thread Mike Harless

François  wrote:

> On Tue, Oct 31, 2017 at 01:14:30PM +1100, Tobin C. Harding wrote:
> > So, thank you for your ideas. I'll consider this issue resolved by;
> > 
> > Use git grep
> > Use ctags/etags
> > Use free-electrons as a last resort
> 
> Also, there's a tool called cscope [1].
> There are also occurences of coccigrep [2] in the kernel.
> 
> [1] 
> https://courses.cs.washington.edu/courses/cse451/12sp/tutorials/tutorial_cscope.html
> [2] https://home.regit.org/software/coccigrep/
> 

and another to add to the list is gscope, which is based off of cscope:

  * https://github.com/tefletch/gscope

--Mike

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies