Sponsored Content
Full Discussion: Branded zone Solaris 9
Operating Systems Solaris Branded zone Solaris 9 Post 302942086 by hicksd8 on Friday 24th of April 2015 05:59:35 AM
Old 04-24-2015
It is an access rights issue. p2v cannot create the required directory tree before populating it with the migrating data.

Check out the access rights on the mount point. Open the rights up, at least whilst executing p2v.

What user account are you running under???? (root or sudo would be best to circumvent access rights issues)
 

9 More Discussions You Might Find Interesting

1. Solaris

Postprocess issue installing Solaris 9 Branded Zone

Hello, I am attempting to install a newly configured Solaris 9 zone using the flash archive image provided on the sun website. Each time I run the install I get a failure during the Postprocess: Creating mount points. Following is the log: Log File: /var/tmp/s9-zone.install.25457.log... (0 Replies)
Discussion started by: brialt1
0 Replies

2. Solaris

Three questions - migrating to branded zone

1. i read that VxFS (3.x) installed on a solaris 8 will not work on a branded zone. fair enough, but what is the impact of having the packages installed when the flarcreate is done? will the container fail to boot with those packages installed? 2. NTP client and server doesnt work on branded... (11 Replies)
Discussion started by: frustin
11 Replies

3. Solaris

Prerequisites for Solaris10 Branded Zone within Solaris 11 Express

Dear all, we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message: ***The image patch level is downrev for running in a solaris10 branded zone*** The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed. Does the... (0 Replies)
Discussion started by: xunil321
0 Replies

4. Solaris

Solaris 9 branded zone on a Solaris 10 server

I have a T5220 running Solaris 10. I have a application that can only run on Solaris 9. I want to build a branded Solaris 9 zone for this application on the Solaris 10 Server. What steps would I need to accomplish this? (2 Replies)
Discussion started by: soupbone38
2 Replies

5. Solaris

Branded Solaris 10 zone no network

I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate. #zonecfg -z <device> >create -b >set brand=solaris10 >set zonepath=/zonez/<device> >set ip-type=exclusive >add net... (1 Reply)
Discussion started by: aeroforce
1 Replies

6. Solaris

NFS server on Solaris 10 branded zone

I am trying to get a NFS share on a Solaris 10 branded zone. I have read that this is not possible...but I was hoping someone here could tell me different. share -F nfs -o ro,anon=0 /dir This would really surprise me that you cannot do this. Thanks (2 Replies)
Discussion started by: aeroforce
2 Replies

7. Solaris

Solaris 10 branded zone with IPMP

All. I am trying to create a 10 branded zone on a Sol 11.1 T5. The Global is using IPMP...so aggregating is out of the question. Has anyone successfully created a branded zone with IPMP? If they have can you please show me the steps you took to get this to run. Thanks (4 Replies)
Discussion started by: aeroforce
4 Replies

8. Solaris

Solaris 11 Global zone patching having Solaris 10 branded zone

I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies

9. Solaris

Help setting up a bhyve branded zone

So I started with following the example on the omnios page for bhyve (sorry, I can't provide the link because I'm a post shy of the 5 to give a URL): And found that in the end I was able to create a running bhyve zone, but accessing it via zlogin results in a blank console. I've tried Debian 9... (14 Replies)
Discussion started by: stratacast1
14 Replies
mnthome(1)						    BSD General Commands Manual 						mnthome(1)

NAME
mnthome -- mount an AFP (AppleShare) home directory with the correct privileges SYNOPSIS
mnthome [-v] [-d] [-m mntpath] [-n] [-b] [-p password] [-i] [-x mount point] [-u] [-s] DESCRIPTION
The mnthome command unmounts the AFP (AppleShare) home directory that was automounted as guest, and remounts it with the correct privileges by logging into the AFP server using the current username and password. This command also allows you to have guest access turned off on your AFP server too and still have AFP home directories work with "su". When you ssh into another computer using an account that has an AFP home directory or you "su <netuser>" where <netuser> is an AFP home directory user, then the resulting home directory will not have the correct access privileges. This is because automount is assuming NFS behavior which assumes that all computers share the same user/group privileges and mounts volumes using "no security" and lets the client enforce privileges based on the current user. AFP is different since the privileges are based on the user that logged into the server. Since automount does not put up an authentication dialog asking for an user name and password, automount mounts the fileserver using guest login. Thus you end up with getting the world access privileges and the privileges are shown via "mapping". You also would have to allow guest access to the server to that sharepoint. Mapping makes all the files/folders appear like they are owned by the current user. Even those items not really owned by the current user show up as being owned by the current user. The server provides user access rights (UARights) which is a summary of what the access rights are regardless of the category (owner, group, world) from which they were obtained. When doing "mapping", the AppleShare client will take these UARights and show them as the owner rights. So, everything looks like it is owned by the current user and the owner rights are set to the UARights. Thus if you had access to that file/folder before, then you still do. The options are: -v Display version number. -d Print debugging information. -m Alternative mount point is specified with the -m option followed by a path to an existing directory. Normally, the volume is mounted in /Network/Servers/ or /var/automount/Network/Servers/. -n Do not force the unmount of the previous mount point. -b Exec the user's shell after mount of home. -p A password may be specified with the -p option followed by a password. If this option is not used, then the user will be prompted to enter in a password. -i Display information about the AFP home mount point. -u Attempt to unmount the current home directory mount. -x This option must be followed by a path to an existing AFP mount point. Display information about the mount point. -s Skip preflight check to see if the currently mounted home directory is already correctly mounted for the user. EXAMPLES
The following example illustrates how to mount an AFP home directory: mnthome This example shows how to print the debugging information and provide a password: mnthome -d -p foobar SEE ALSO
mount(2), unmount(2), mount(8) mount_afp(8) BUGS
I get the mounting url from the "home_loc" attribute and the mountpath from the "home" attribute (with the path from home_loc subtracted out). If your AFP home directory automounts in a different location, then you need to use the -m option to specify an alternative mount point. I cant figure out how to cd out of the current home dir so I can do the unmount and then restore the user back into the new home dir. If you are in the AFP home directory when you use mnthome, you automatically get put back into that same directory when mnthome leaves. If mnthome works, then your current directory is a dead directory and you need to "cd ~" to get to your new home directory. If the server with the home directory was already mounted by another user, you will not be able to replace it with a mount made by your user id. The original mount must be first unmounted by the mounting user or root. HISTORY
The mnthome command first appeared Mac OS X version 10.3. RETURN VALUES
0 mnthome successfully remounted the AFP home directory. [EINVAL] Invalid arguements were passed in. [EPERM] The current AFP home directory could not be unmounted by mnthome because the current user does not have the correct access. The current AFP home directory was probably mounted by another user first. [EAUTH] Incorrect password. Mac OS X August 4, 2004 Mac OS X
All times are GMT -4. The time now is 07:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy