Search results for query: *

I've found LiveUpdate to be the easiest way to do this. Simply create a backup boot environment (man lucreate for details) and then install the patch. If you have trouble you can activate the backup environment and get back to your pre-patch state. Another option is to break the mirror and...

Mounting the filesystems is easy too. You'll need to do 'zfs list' to get a list of the filesystems on oldpool. After that you can pick which filesystem you want to mount and use 'zfs set mountpoint=/mnt oldpool/filesystem', where filesystem is the filesystem you want to mount, and then 'zfs...

If you can see the disk then you'll need to do 'zpool import' to get the numeric ID of the pool if you named the root pool 'rpool' on both the Ultra 2 and the T2000. After that, I think 'zpool import -f -N -F -m <insert numeric ID here> oldpool' will work. This will import the pool and name it...

Yep, the CPUs section is what you're looking for here. If you had a CPU model with multiple cores you'd see additional ones listed on each line separated by commas. _______ Linnorm

Either /usr/sbin/prtdiag or /usr/sbin/psrinfo will tell you how many cores as well as a variety of other information. _______ Linnorm

The devfsadm command should do the trick. _______ Linnorm

The couple of times I've done it I've just tar'ed up the user directories, grabbed /etc/shadow and /etc/passwd, and ftp'ed it all over to the new server. I appended the contents of /etc/passwd and /etc/shadow to the existing ones after editing out accounts (like root) that already existed on...

Issue this command at the command line and it should tell you what you're using "echo $0" _______ Linnorm

I've got it in /appbin/user_maint, but it's part of a larger script system contained there. You can put it wherever you want, just make sure that the path in .profile points to your chosen location. _______ Linnorm

Here it is. Note that it prevents resetting root, etc. You can add more userids if you have other ids that you want to prevent the script users from resetting; oracle for example. Also, it forces the user to change their password on their next login. The helpdesk user's .profile is also...

We use a custom shell script that gets called from .profile and sudo to do it here. When the user (helpdesk) logs in they are immediately dropped into a script for reseting passwords. The script uses sudo to do the work, and then the session exits. HTH

Ouch. In that case booting from cd really is you only option. You can get a terminal window to run the fsck after the installer starts. I don't remember off hand how far you need to get into the installer before you can get the terminal though. After the installer starts try right-clicking...

Just input the root password at the point where the boot process stops and it'll take you into maintenance mode. You can run the fsck from there.

I've got a new system I'm setting up with SAN storage on a CX3-80 and Symantec Storage Foundations and I'm having trouble getting SF to work. Per the Qlogic site I'm using the EMC approved drivers for the HBAs which appear to be SUNs Leadville drivers. The problem I'm running into is that SF...

Last week I installed Solaris 10 on our new server and told it to enable minimum network services. Now I'm trying to get an X-Windows connection to the box and can't figure out what I need to enable/configure to get it to work. I can use X at the graphical console with no trouble, I just can't...

There is a passwd option to set a warning that the password will expire in x days. I don't recall what it is off-hand, man passwd will have the answer though.

There's a pretty good overview here: http://www.tek-tips.com/faqs.cfm?fid=5892 and another here: http://www.adminschoice.com/docs/jumpstart_solaris.htm

I believe you are correct, It's been a couple of months since I played with LU. I found this site to be very helpful: http://hell.jedicoder.net/?p=39

Since you've got the install CDs it won't be too hard. First boot the system from the install CD. Then mount the root partition to /a. Finally, edit /a/etc/shadow and remove the password hash. Reboot and you should be able to login with no root password. Make sure to change the password once...

I'm with Annihilannic, it's more important to have your security patches up to date than have AV.