Sponsored Content
Operating Systems Solaris Can v240 disks be moved to v440 and have a chance of working? Post 302696847 by lyle on Wednesday 5th of September 2012 02:10:22 PM
Old 09-05-2012
Thanks for the reply, Jim.

The issue is really wanting to preserve applications, libraries, etc that are already installed, and avoid reinstalling (assuming I could even find them) on a fresh Solaris disk.

Licensing may be an issue on a different machine. But I too remember being able to move disks between different Sun machines in the same class.

Of course, if bus structure or controllers are different, it's not going to work. But I thought a v240 and v440 might be close enough.

Any more thoughts from the Community? Thanks....Lyle
 

6 More Discussions You Might Find Interesting

1. Solaris

migrate complete OS from v240 to v440

We are concluding development of a new application on a v240 and would like to migrate the entire Solaris10 OS on the v240 to a v440 that is currently live with Solaris 9. The steps outlined in my head are as follows: 1) Flash archive the v440 and v240 and store the flar file on a different... (6 Replies)
Discussion started by: dangral
6 Replies

2. Shell Programming and Scripting

no chance to input passwd when create new user in loop

Hi Dears, I have one script to create new users with information in one plain text file. This script will read all lines in the file and create one users for one line. Sample file: #action;login,full name title,expire date,project +;gmwen,Bruce Wen QA,04/01/2012,BT +;xxdeng,Shown Deng... (4 Replies)
Discussion started by: crest.boy
4 Replies

3. Solaris

How to get spare disks working

Dears how can i make this spare disks working online to replace a defective disks vxdisk list DEVICE TYPE DISK GROUP STATUS c0t10d0s2 sliced - - error c0t11d0s2 sliced disk08 rootdg online c1t16d0s2 sliced ... (3 Replies)
Discussion started by: thecobra151
3 Replies

4. Solaris

Hot swapping disks on V240 - blue light not lit after cfgadm -c unconfigure

Hot swapping a drive on V240. So, I do cfgadm -c unconfigure <disk>. Then cfgadm -al reports disk as unconfigured as expected. format then tells me there is no disk. BUT, blue light does not come on. Done the exact same command on my V440 and blue light does come on. V240 Server Admin... (0 Replies)
Discussion started by: psychocandy
0 Replies

5. Programming

How to make C++ give me a chance to inter a number while excuting?

Iam Trying to simulate a hardware "pci" by visual c++ program..... " i don't have the hardware right now so i want to test my program" the hardware is about to inter a number for example from switches compare it to other number also from switches.."which iam gonna take it from 1 textbox"... 1-... (0 Replies)
Discussion started by: fwrlfo
0 Replies

6. Solaris

Sun Fire 480 - devfsadm -C not working after replacing one of the boot disks

Our SunFire 480 - one of the boot disks failed. It is mirrored with VxVm. I followed the exact steps that is detailed in the veritas and sun guides (I can not post the URL since I don't have 5 posts yet.) After removing the failed disk, I ran devfsadm -C -c disk and it still shows the device... (7 Replies)
Discussion started by: jtamminen
7 Replies
advfsd(8)						      System Manager's Manual							 advfsd(8)

NAME
advfsd - Starts the AdvFS graphical user interface (GUI) daemon SYNOPSIS
/usr/sbin/advfsd DESCRIPTION
The AdvFS daemon, advfsd, is a process required by the AdvFS GUI (dtadvfs). The advfsd daemon issues commands and obtains system information on behalf of the AdvFS GUI. The /usr/var/advfs/daemon/socket/hosts.allow file contains a list of all hosts on which the advfsd daemon will allow the AdvFS GUI to run. This file can be edited to add or remove hosts. Each host name must be on a separate line. For example: host1 host3 host27 The /usr/var/advfs/daemon/socket/gui.passwd file, if it exists, is used by advfsd to force a dtadvfs user to enter a unique password when attempting to connect to the host. The first line of this file is the unique password required by the GUI. For example: guipassword For security reasons, do not use the password of the root user or any other user; make up a unique name and do not encrypt it. The advfsd daemon allows Simple Network Management Protocol (SNMP) clients such as NetView or Performance Manager (PM) to request AdvFS file system information. SNMP clients cannot issue system configuration commands to the advfsd daemon. The advfsd daemon is automatically started at boot time. Under normal conditions, this daemon does not need to be run manually. If you do not want to have the daemon started at boot time, move the /sbin/rc3.d/s53advfsd file from its default location to another directory and run it from that directory. Whenever you want to run the daemon at boot time, move the s53advfsd file back to the /sbin/rc3.d directory. The daemon (called an agent in the dtadvfs GUI interface) employs a file, /usr/var/advfs/daemon/disks.ignore, in which you can place the names of disks that the daemon will ignore when it gathers information about disks on the system. If you use the disks.ignore file, you can improve the performance of the dtadvfs GUI. Each line in the disks.ignore file contains the name of a disk (with no directory partition letter) to be ignored by the daemon. For example, to cause the disks /dev/disk/dsk3d and /dev/disk/dsk2g to be ignored, enter the following names on separate lines in the file: dsk2 dsk3 You cannot ignore an LSM volume by including the LSM volume name in the disks.ignore file; you must list the disks from which the LSM vol- ume is built. To ignore a complete disk group, you must list all the disks in it. Because all partitions on the listed disks will be ignored, unexpected results may occur if a disk has partitions belonging to more than one disk group. The disks.ignore file is processed each time the disks are checked. This means that if a disk fails or becomes unavailable, you can add the disk name to the disks.ignore file and the daemon will ignore it. Once the disk is available, remove the entry from the file. There is no need to stop the daemon. For more information, see the GUI interface reference page , dtadvfs(8). RESTRICTIONS
Only one advfsd daemon can be running on a system at a given time. If a second advfsd daemon attempts to start, it will fail. You must be the root user to use this utility and you must register the Advanced File System Utilities license. FILES
The script that starts the advfsd daemon at boot time. The advfsd message catalog. The SNMP data files. The sh scripts used by the dae- mon to execute commands. The advfsd daemon executable. The advfsd daemon message log file. Remove or copy this log to another location periodically to prevent the log from becoming too large. The security file that lists all hosts with permission to connect to the advfsd daemon with the AdvFS GUI (dtadvfs). The advfsd password file. The file that lists all disks for the advfsd daemon to ignore when col- lecting statistics about resources. SEE ALSO
advfs(4), dtadvfs(8) advfsd(8)
All times are GMT -4. The time now is 05:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy