think(1) [linux man page]
THINK(1) General Commands Manual THINK(1) NAME
think - you don't have to think, the computer can think for you SYNOPSIS
think [ -detach ] DESCRIPTION
Think simulates a thinking brain. This can be useful if someone is not wanting to think at invocation time or if someone is needing some thinking about something. It can also be helpful if someone's brain is not working correctly at invocation time. When invoked, think will go ahead and look at all of the commands and keystrokes that a user has made during the current login session. Think will then look at what files the user has. From this and what level the user is listed at in the file /usr/lib/think, think will figure out what the user was trying to do when think was invoked. DEVICES
The process that think uses to help a user is greatly aided if the user is wearing a brain interface bus (bib) device. A bib device is normally worn on the head, and if being used, then think will try to see what was going through the users head at the time of invocation. After think does this, it will send electric signals to the users brain, causing the user to type in whatever keystrokes are necessary to accomplish the task that he/she doesn't want to think about. OPTIONS
-detach also known as "Must mother do all of your thinking for you?"-mode. This options causes think to run in the background as a daemon that watches for users who look like they may need assistance. When a user is found to be exercising cluelessness, think will lock up their keyboard and will proceed to execute what seems to be the most likely sequence of commands that the user had intended to execute. This flag may only be used by the super-user. FILES
/dev/brain bib device special file. /usr/lib/think file to indicate various user abilities. The format of this file is a username on each line followed by some whitspace and then a number. The higher the number for a given user, the more likely think is to assume that that user knows what he/she is doing. Unfortunately, what think considers a large number will vary with usage. BUGS
If a user is using a bib device and actually lacks a brain of their own, then there is a high risk that think will take over their (non- existent) minds. This has the upshot that someone other than the user will have to stop the program. (Perhaps this is a feature.) It may illegal in some areas to force users to wear bib devices. AUTHOR
This man page was written by John Guthrie <guthrie@math.upenn.edu> with suggestions from Kevin Whyte <kwhyte@math.upenn.edu> for the alt.sysadmin.recovery man page collection. think version 1.0 April 5, 1996 THINK(1)
Check Out this Related Man Page
allocate(1) allocate(1) NAME
allocate - device allocation SYNOPSIS
allocate [-s] [-U uname] device allocate [-s] [-U uname] -g dev-type allocate [-s] [-U uname] -F device The allocate utility manages the ownership of devices through its allocation mechanism. It ensures that each device is used by only one qualified user at a time. The device argument specifies the device to be manipulated. To preserve the integrity of the device's owner, the allocate operation is exe- cuted on all the device special files associated with that device. The argument dev-type is the device type to be operated on and can only be used with the -g option. The default allocate operation allocates the device special files associated with device to the uid of the current process. If the -F option is specified, the device cleaning program is executed when allocation is performed. This cleaning program is found in /etc/security/lib. The name of this program is found in the device_allocate(4) entry for the device in the dev-exec field. Only authorized users may allocate a device. The required authorizations are specified in device_allocate(4). The following options are supported: -g dev-type Allocates a non-allocated device with a device-type matching dev-type. -s Silent. Suppresses any diagnostic output. -F device Reallocates the device allocated to another user. This option is often used with -U to reallocate a specific device to a specific user. Only a user with the solaris.device.revoke authorization is permitted to use this option. -U uname Uses the user ID uname instead of the user ID of the current process when performing the allocate operation. Only a user with the solaris.device.revoke authorization is permitted to use this option. The following exit values are returned: non--zero An error occurred. /etc/security/device_allocate /etc/security/device_maps /etc/security/dev/* /etc/security/lib/* See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ deallocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5) The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. /etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment. 28 Mar 2005 allocate(1)