Sponsored Content
Operating Systems Solaris Porting to new hardware - best way? Post 302739693 by Joseph_TKLee on Tuesday 4th of December 2012 06:28:43 PM
Old 12-04-2012
I used to migrate to a new haredware.
You need to do it manually.
From top of my head, you need the following checklist.
1. /etc is important which has most of configuration files such as hosts,network info, dns,mail,applications startup scripts so you need to back up and copy each files to new hardware.
2. crontab files : /var/spool/cron
3. home directories : /export/home
4. root profile
5. kernal values
6. Package list

Cheers,
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Porting Scripts.

Hi all, Figured this would be a good a place (well more apropriate) to ask this ... What considerations are necesary to port a script from one system to another? The below link is a script that I'm currently working on at work. The work system is a SCO box and I'm slowly becoming familar... (1 Reply)
Discussion started by: Cameron
1 Replies

2. Programming

Porting to solaris

I have ported a c program to solaris. When I run , it gives me segmentation fault error at line :- memcpy ((char *)a_string ,(char *)0, MAX_READ ) ; originally this was in reliant unix as :- memcpy ( a_string , 0 , MAX_READ ) ; Can somebody help me about this ? (1 Reply)
Discussion started by: suds19
1 Replies

3. UNIX for Dummies Questions & Answers

HP-UX to linux porting

Hi all, i wanted to port some HP-UX code to linux. can anybody point to some documents or resources that would help me in doing the porting.. thanks in advance Arun Prakash (0 Replies)
Discussion started by: arunprakash
0 Replies

4. Programming

Porting tools

I m sorry if this is the wrong place to post this. I m going to do a project on porting tools in unix platform. Can any one give me further suggestions and resources for this topic "Porting tools". Thanks in advance (5 Replies)
Discussion started by: veeru554
5 Replies

5. UNIX for Advanced & Expert Users

porting

I want to know what are the design considerations to be taken into account. when porting a socket project from Unix platform to another ...... (10 Replies)
Discussion started by: areef4u
10 Replies

6. Linux

when porting from HP-UX to Linux

helo, i m porting HP-UX socket application to Linux SSL-socket application. I have use htonl() in HP-UX. so when i use it in Linux, data transf is not done and application become soem time crashed. now when i remove htonl() in linux, then i got data but it will not proper order or some data may... (1 Reply)
Discussion started by: amitpansuria
1 Replies

7. HP-UX

Makfile porting

I am trying to port to HP-UX 11i v3 system an application in C++ language written for a Tru64 Unix V5. I am trying to execute on HP-UX 11i v3 a Makefile written for Tru64 Unix V5 with this code: $(TARGET_MORE): $(DEPEND_FILE) $(SOURCE_MORE.cc) $(LIBS) @for i in $(TARGET_MORE); do \ ... (1 Reply)
Discussion started by: angeloberardi
1 Replies

8. AIX

Porting from HP-UX to AIX

I am orignally a VC++ programmer, this is the my post in UNIX form. I have an existing source code, that was developed in old HP-UX system, the objective is to make it work on new AIX system. It does'nt appear that AIX has the necessary libraries or even run the application if its... (0 Replies)
Discussion started by: maverick786us
0 Replies

9. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
CRONTAB(1)						    BSD General Commands Manual 						CRONTAB(1)

NAME
crontab -- maintain crontab files for individual users (ISC Cron V4.1) SYNOPSIS
crontab [-u user] crontab [-elr] DESCRIPTION
crontab is the program used to install, deinstall, or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their own crontab, and though these are files in /var/cron, they are not intended to be edited directly. If the /var/cron/allow file exists, then you must be listed therein in order to be allowed to use this command. If the /var/cron/allow file does not exist but the /var/cron/deny file does exist, then you must not be listed in the /var/cron/deny file in order to use this command. If neither of these files exists, depending on the compiled in settings, only the super user will be allowed to use this command, or everyone will be allowed to use this command. On NetBSD everyone is allowed to use this command. The default maximum size for a crontab is 256 kilobytes, but this may be changed for all users on the system by putting the desired maximum size (in bytes) in the /var/cron/maxtabsize file. If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you should always use the -u option for safety's sake. The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given. The -l option causes the current crontab to be displayed on standard output. The -r option causes the current crontab to be removed. The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. FILES
/var/cron/allow Optional list of users that are allowed to use crontab. /var/cron/deny Optional list of users that are disallowed to use crontab. /var/cron/maxtabsize Maximum size of crontab files. Defaults to 256 kilobytes. /var/cron/tabs/ Directory containing the individual user crontab files, named after the user. DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line. SEE ALSO
crontab(5), cron(8) STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic Version 3 AT&T UNIX syntax. AUTHORS
Paul Vixie <vixie@isc.org> BSD
May 6, 2010 BSD
All times are GMT -4. The time now is 04:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy