View Single Post
Old 01-05-07, 03:35 PM   #9
Laurent Blume
Registered User
Join Date: Jan 2007
Posts: 1
Default Re: Solarsi 10 (6/06) crash

Originally Posted by netllama
touch /reconfigure

is far more destructive than just doing a "reboot -- -r". It basically wipes out all system specific configurations and forces you to reconfigure them, which is normally not what you'd want for a system which is already working fine.

I'd be curious why a user of Solaris told you that doing a "reboot -- -r" is dangerous, as that command is the method that Sun recommends.
It's me who said that reboot is evil on Solaris.
I wonder who at Sun recommends using reboot? It is clearly stated in the man why it is dangerous:
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.

Me, I like *clean* shutdowns, which reboot does not do on Solaris (same for halt and poweroff). They are emergency commands, to use when regular shutdown and init do not work (like when there's NFS I/O pending that won't succeed).

And I also wonder where you got the idea that touch /reconfigure is destructive? There are quite a few patches that do it already, and it's a completely painless process, with no user intervention required beside the reboot, and no change done to existing configuration. It only checks for *new* peripheral, it does not modify any existing ones:
The /reconfigure file causes the Solaris software to check for the presence of any newly installed devices the next time you turn on or boot your system.

You're probably mistaking it with the sys-unconfigure command, which is something quite different.

I hope this will clarify the situation, and help correct that NVidia README that is making far too many new users believe reboot is safe. It's not.
Laurent Blume is offline   Reply With Quote