01-25-2002
Well hell, if the current box is a 486, then yes - just about anything will do. The thing you'll have problems with is getting the program to run on the new box. If it's statically linked, you may be able to run it on a *BSD machine, depending on what it was compiled for.
If you have source and/or installation media, you have a much better chance.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi,
is there any tool that i can use to update my scripts (SH scripts)
form Unix to linux.
please mention any useful websites.
thanx in advance (2 Replies)
Discussion started by: omran
2 Replies
2. UNIX for Advanced & Expert Users
Hi all,
Would appreciate advise on my situation.
Currently server A is in production. Server A takes in data from Server X, does some processing and send to server Y. We are going to develop a different system in server B, something like an enhanced version of A. Server A will be retired once... (2 Replies)
Discussion started by: new2ss
2 Replies
3. Solaris
Hi,
I need docs related to migration of Solaris8.0 to solaris10.0.
steps to be taken care from developement side..
cheers
shell scripts developer (0 Replies)
Discussion started by: mohanpadamata
0 Replies
4. UNIX for Advanced & Expert Users
Hi ,
There is going to be a server migration from Solaris 8.0 to Solaris10.0.
Could anyone give me some tips and documents regarding the steps to be remembered,tips to be followed etc.
like
syntax differences
any new changes to the existing commands and tools we use
whatever the... (1 Reply)
Discussion started by: mohanpadamata
1 Replies
5. Shell Programming and Scripting
Hi,
I am working on migration project. thier are 50,000 scripts. As we are doing 70% of automization for changing the scripts. The remaining 30% doing manually.
After doing manual changes i have to find the wheather the change is dont or not and also clode review process.
Is there any... (2 Replies)
Discussion started by: unihp1
2 Replies
6. UNIX for Advanced & Expert Users
We are about to get a new server and I need to prepare for migration to the new one. This will be my first migration so I'm sure I will be learning alot.
My current server is running CentOS 4.x and I want to move to a sever running Centos 5.x , thought it would make things easier.
The old... (1 Reply)
Discussion started by: mcraul
1 Replies
7. AIX
Hi,
Existing several p5 server with lpar (aix5.3), also implemented with hacmp.
And now planning to buy new set of server (installing aix7.1)and SAN to replace the existing server.
My question is, how to perform data migration from old server/SAN to new server/SAN.
Suppose I install... (6 Replies)
Discussion started by: Oceanlo2013
6 Replies
8. AIX
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies
9. AIX
We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2
Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies
10. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
LEARN ABOUT MOJAVE
glutbuttonboxfunc
glutButtonBoxFunc(3GLUT) GLUT glutButtonBoxFunc(3GLUT)
NAME
glutButtonBoxFunc - sets the dial & button box button callback for the current window.
SYNTAX
#include <GLUT/glut.h>
void glutButtonBoxFunc(void (*func)(int button, int state));
ARGUMENTS
func The new button box callback function.
DESCRIPTION
glutButtonBoxFunc sets the dial & button box button callback for the current window. The dial & button box button callback for a window is
called when the window has dial & button box input focus (normally, when the mouse is in the window) and the user generates dial & button
box button presses. The button parameter will be the button number (starting at one). The number of available dial & button box buttons can
be determined with glutDeviceGet(GLUT_NUM_BUTTON_BOX_BUTTONS). The state is either GLUT_UP or GLUT_DOWN indicating whether the callback was
due to a release or press respectively.
Registering a dial & button box button callback when a dial & button box device is not available is ineffectual and not an error. In this
case, no dial & button box button callbacks will be generated.
Passing NULL to glutButtonBoxFunc disables the generation of dial & button box button callbacks. When a new window is created, no dial &
button box button callback is initially registered.
SEE ALSO
glutDialsFunc, glutDeviceGet, glutSpaceballButtonFunc, glutTabletButtonFunc
AUTHOR
Mark J. Kilgard (mjk@nvidia.com)
GLUT
3.7 glutButtonBoxFunc(3GLUT)