![\"\"](\"http:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/09\/mistake-pic1.png\")
<\/a><\/p>\nThis isn’t the first time that my fingers got the better of me, so I simply ran the ls command and asked that it display the inode number of each of the files. \u00a0Normally that would have been fine but my control character, perhaps ^H, was actually removing the previous character displayed.<\/p>\n
This means that my inode number was any one of ten possible values. \u00a0There are other ways to try and determine exactly what inode number a file is but before trying that I simply did a long listing using ls.<\/p>\n This actually did show that my inode number was 540. \u00a0I am actually a bit surprised that you cannot use this information directly to delete the file with the rm command (on Solaris, also on Linux?)<\/p>\n This information however can be used in conjunction with both the find and rm commands to delete this tiny mistake.<\/p>\n Instead of the familiar -name option for the find command there is a somewhat less used \u00a0 -inum option. \u00a0As this option name implies, it will look only for files that have this inode number.<\/p>\n Once it is possible to find the actual file it is a simple matter of using the -exec option of find to remove the file.<\/p>\n find . -inum 540 -exec rm {} \\;<\/p>\n There is another way to find an inode number using just variations of the find command.<\/p>\n find . -name “*”\u00a0 -ls<\/p>\n This will just do a directory listing of the files under the current working directory and run a similar directory listing at the same time. \u00a0Deleting the file is done using the same find and remove as described above.<\/p>\n","protected":false},"excerpt":{"rendered":" I knew that I had mistyped but it was too late. \u00a0I tried to exit out of vi in a hurry and accidentally exited but saved the file under a new name. \u00a0This wouldn’t have been so bad if the … Continue reading <\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nExtra credit method<\/h2>\n
<\/a><\/p>\n