Takahiro Kambe <taca@back-street.net>  wrote:
 > It might be a special case, but there is a situation:
 > 
 > - Not always stick a console (except some hardware trouble).
 > - Can't prepare a terminal for serial console.
 > 
 > User shutdown a machine from some Web based management system from
 > another room, but there is no space to put another peripheral.
 > (And this user isn't a specialist for administration.)

then user shouldn't be allowed to shutdown the machine.

Frankly, if you don't have console's on your servers, then they can't
be all that important and then it just doesn't matter when you turn
them off.

Sysadmins build machinerooms with consoles, console cables, and 
console servers.  I have a machineroom with close to 200 machines
in it, and I have one monitor.  I can get to any console on those
machines from anywhere, even across the planet.

If you want to build a hacked up network, then that's up to you. But
then you can hack up your kernel with whatever code you want too. But
don't make everyone else have to have that code there just because
you like to run a sloppy network.

 > So, beep should be controlled by sysctl and default should be off.

The code shouldn't even be there.