FMVのPentium4でSCSIのみでハードディスクを付けてSolaris8を インストールしようとして、DISK1/2はインストールできるのにリブートすると 「operating system not found!」 って怒られて2/2のインストール画面にならないのですがどうしたらよいですか? 普通にIDEのディスクを付けるとインストールができるのですが… SUNに聞いてもよくわからん回答だし… SCSIをBIOSの設定で読み込めればできると思うのですが、それができないようでして
grep inetd /etc/rc?.d/* の結果は、 # grep inetd /etc/rc?.d/* /etc/rc0.d/K42inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc0.d/K42inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc0.d/K42inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc0.d/K42inetsvc:/usr/sbin/inetd -s & /etc/rc1.d/K42inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc1.d/K42inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc1.d/K42inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc1.d/K42inetsvc:/usr/sbin/inetd -s & /etc/rc2.d/S72inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc2.d/S72inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc2.d/S72inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc2.d/S72inetsvc:/usr/sbin/inetd -s & /etc/rc2.d/S72inetsvc~: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc2.d/S72inetsvc~:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc2.d/S72inetsvc~:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc2.d/S72inetsvc~:/usr/sbin/inetd -s & /etc/rc2.d/S73cachefs.daemon:inetconf=/etc/inet/inetd.conf /etc/rcS.d/K42inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rcS.d/K42inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rcS.d/K42inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rcS.d/K42inetsvc:/usr/sbin/inetd -s & となります。 本当にすみません。
ちなみに、nfsfindを見ると下記のように書いてあったり # Check shared NFS filesystems for .nfs* files that # are more than a week old. # # These files are created by NFS clients when an open file # is removed. To preserve some semblance of Unix semantics # the client renames the file to a unique name so that the # file appears to have been removed from the directory, but # is still usable by the process that has the file open.