The reason that /etc/init.d/boot.local and /etc/rc.d/boot.local are the same file is because /etc/rc.d is a link to /etc/init.d on my SuSE 7.2 PRO system.
linuxpc> ls -ald /etc/rc.d lrwxrwxrwx 1 root root 6 Mar 24 2001 /etc/rc.d -> init.d
Been there, done that :-) Actually, I tried root@233p5:/ > ls -al /etc/init.d/boot.local -rwxr--r-- 1 root root 447 Jan 30 16:37 /etc/init.d/boot.local root@233p5:/ > ls -al /etc/rc.d/boot.local -rwxr--r-- 1 root root 447 Jan 30 16:37 /etc/rc.d/boot.local | |____________________ | and found that both had the number 1 where I expected 2. I then went back to an old UNIX manual and did some more reading :-) and tried root@233p5:/ > ls -il /etc/init.d/boot.local 274722 -rwxr--r-- 1 root root 447 Jan 30 16:37 /etc/init.d/boot.local root@233p5:/ > ls -il /etc/rc.d/boot.local 274722 -rwxr--r-- 1 root root 447 Jan 30 16:37 /etc/rc.d/boot.local and, miracles still happen, got the same inodes for both files. So it looks like we have a hard link. However, we still have 1 and not 2 :-) I notice you have the same "disease" I then wondered whether SuSE was doing something odd. I therefore went to /tmp and, as root, created two subdirectories z1 and z2. I then cat'd /etc/fstab to z1/test1 to create a file. I finally created a hard link from z2/test1 to z1/test1. When I now did a ls -il on those two test1 files, there were 2's where they should be! At this point, Chuck suggested I do a forced fsck. I had some trouble at first (until he showed me I had to remount / ro; I had tried the SuSE rescue system but it complained about bad superblocks and/or odd "magic numbers". This happened on three boxes so I was unconvinced there was a screwed up file system on all three machines). I have just now finished that fsck -f /dev/hda7 on my notebook and all it reports is 0.2% non-contiguous --- as I suspected from the problem on three boxes (or 4, if we include yours) no screwed up file system. So the mystery now is why do we both get 1 for those linked files. doug filesystem.