But supporting many different fs is one of linux greatest strengths. If linux were to support only one or two file systems like Windows NT, it would be much less difficult. That is the reason for all these kludges. The problem is that the inode number as defined in POSIX is only 32bit and therefore too small for the primary keys of many modern file systems. Many file systems such as ext2/ext3 have the inode number as a primary key. However, I'm not that familiar with the command line, so both of these solutions seem. > person (Linus?) that didn’t include a “primary key” system I wanted a command line command to search all shell scripts in the filesystem for a particular word, so I asked around at work and got the following solutions: grep word find / -name \.sh 2>/dev/null find / -name '.sh' 2>/dev/null xargs grep word. > I guess the cause of the problem is the stupidity of the I enhanced it instead of completely replacing it to increase the chance of getting it included, not because I like it. The original dnotify is very limited and also a quite strange as an API. You are right, and most people on the lkml agree. This is the default when there is more than one file to search. > than dnotify (except for polling, of course). H, -with-filename Print the file name for each match. I don’t think I could even imagine anything worse I don’t know if WaitForMultipleObjects first came about in NT, or started in some earlier system, but I wonder how hard it would be to implement in a unix kernal (linux, *bsd, darwin)? What are the main hurles to implmenting in unix when it’s considered bread and butter in NT? (Let’s ignore the window per process and other nastiness for now). When I learnt this it was the first time I though ‘wow NT does have significant advantages over unix’. By default, TYPE is binary, and grep normally outputs either a one-line message saying that a binary file matches, or no message if there is no match. The grep command is mainly used to search in a particular file but the recursive grep is used to recursively search in multiple files of a directory. Also waiting in a folder means it’s whole contents recursively (not sure about mount points, they can in Win2k). This makes it real easy to implement timeouts etc. The greate thing about WaitForMultpleObjects if that the array of objects can include files, folders, semaphors, mutexes, threads or timers. 9 Answers Sorted by: 127 You can specify -x more than once. 5.1 grep match pattern in input text ignore case search recursively for an exact string print filename and line number for each match invert match for. Back when I was new to NT4 programming (having had a unix background) I was very impressed by the Win32 api WaitForMultpleObjects.
0 Comments
Leave a Reply. |