Re: [osol-discuss] Where can I find a full Walk thru setting up nfs4 from scratch
Ian Collins i...@ianshome.com writes: On 11/14/11 02:38 PM, Harry Putnam wrote: Running openindiana b 151a as vm guest on host win7 Where can I find an up to date detailed description of setting up nfs4 from scratch on a home lan zfs server with linux nfs4 clients. There really isn't that much to it, just set snarenfs=true on the filesystem(s) you want to share. Egad... that's it? I must be mixing up with having set up the automounter for nfs .. I remember getting tangled up with some edit of files last time I did this, which by now must be a pretty while ago. The solaris box will be both server and client. Is there a good URL for whatever is involved getting the NFS client shares auto mounted? They would be on a Debian linux server. Both boxes will be both server and client. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle Solaris 11 install trouble, NVIDIA
On 11/10/11 18:09, Paul Gress wrote: Following previous messages, to get Solaris Express 11 updated I had to run: pkg uninstall 'pkg://opensolaris.org/*' \ 'pkg://contrib.opensolaris.org/*' \ 'pkg://jucr.opensolaris.org/*' \ 'pkg://Multimedia/*' \ 'pkg://kdeips-dev/*' \ 'pkg://ips.enst.fr/*' This basically cleaned out all the troublesome packages. I am a little disappointed have had to remove KDE. Yes, you'll have to remove it until they update the packages. I believe someone else already responded that you need to use the newest nVidia driver -- either the one included or the one on nVidia's website currently. -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Where can I find a full Walk thru setting up nfs4 from scratch
On 11/15/11 05:14 AM, Harry Putnam wrote: Ian Collinsi...@ianshome.com writes: On 11/14/11 02:38 PM, Harry Putnam wrote: Running openindiana b 151a as vm guest on host win7 Where can I find an up to date detailed description of setting up nfs4 from scratch on a home lan zfs server with linux nfs4 clients. There really isn't that much to it, just set snarenfs=true on the filesystem(s) you want to share. Egad... that's it? I must be mixing up with having set up the automounter for nfs .. I remember getting tangled up with some edit of files last time I did this, which by now must be a pretty while ago. The solaris box will be both server and client. Is there a good URL for whatever is involved getting the NFS client shares auto mounted? They would be on a Debian linux server. Both boxes will be both server and client. For Solaris, man automount. -- Ian. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] pfexec does not work any longer
Andrew: The functional replacement of the Primary Administrator RBAC profile is System Administrator. If you use this instead, you should find that your use is able to run programs with pfexec in much the same way as you used to do with Primary Administrator. Note that if you setup your login shell to a shell like pfsh, pfksh, pfcsh, pfbash, ..., then you do not have to run programs with pfexec when needed. With these shells, pfexec is automatically used when needed. If you want users to need to enter a role password in order to run programs, you can also configure the user to have access to a role which has the needed privileges (e.g. root). If RBAC is configured this way, then the panel will present the dialog to enter this role password before running such programs. But, it sounds like you more just want to use the System Administrator profile and avoid needing to enter passwords. Others have recommended sudo. The sudo program is useful for those people who find it the best way to configure a needed system. That said, using sudo to just avoid the use of RBAC is probably not the best use. Brian On 11/11/11 11:37 AM, Andrew Watkins wrote: I have lost the ability of making a user have access to root on Solaris 11 using the command pfexec. On the old Solaris 11 express box it works: === % grep andrew /etc/user_attr andrewprofiles=Primary Administrator;roles=root % id uid=102(andrew) gid=10(staff) % pfexec id uid=0(root) gid=0(root) Now on Solaris 11 it does not: == grep andrew /etc/user_attr andrewprofiles=Primary Administrator;roles=root % id uid=102(andrew) gid=10(staff) % pfexec id uid=102(andrew) gid=10(staff) What do I have to do to get pfexec working again? Cheers, Andrew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Where can I find a full Walk thru setting up nfs4 from scratch
Ian Collins i...@ianshome.com writes: Is there a good URL for whatever is involved getting the NFS client shares auto mounted? They would be on a Debian linux server. Both boxes will be both server and client. For Solaris, man automount. Yes, of course but if you don't really understand that page then is there a more detailed URL with more examples somewhere? As always the man page is intended for someone who has the basic idea and just needs reminders of syntax or the like... I need to start somewhere below that. For example: From man automount (/etc/auto_master) # Master map for automounter # +auto_master /net -hosts-nosuid /home auto_home It says that `+auto_master' is reference to NIS or NIS+ map if one exists. So if one does not exist do you leave `+auto_master' out? `/homeauto_home' Is auto_home a reference to another file somewhere? Or is it meant verbatim? Or am I supposed to know to put a map entry there... like host:/path/to ? In my case I want to mount a directory from a linux machine at /pub and another at /projects On the linux machine `pub' is found at /pub `projects' is found at /path/to/projects After studying that man page I still have no idea what my entries should look like. And further if auto_pub is a map... what does it look like? There appear to be `direct' and `indirect' ... and ... /pub linux.machine.onlan:/pub which, if any options ? /pub auto_pub ? (and if so, is auto_pub another file somewhere?) Then the whole question of possible options leads off into more man pages with more confusing information. That is, confusing unless you are at or above a fairly sophisticated level already. I need to see some simplified examples that take the whole matter up in one go and explain why, for someone who is not already at a fairly sophisticated level... Or in fact is in no way sophisticated at all. If it matters there are users with the same name and group. The numeric gid is also the same. Uid is different and unless I really need to, I'd as soon leave that alone since there are already numbers of files belonging to a specific (though different) number uid on both machines. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Where can I find a full Walk thru setting up nfs4 from scratch
On 11/14/11 15:24, Harry Putnam wrote: Ian Collinsi...@ianshome.com writes: Is there a good URL for whatever is involved getting the NFS client shares auto mounted? They would be on a Debian linux server. Both boxes will be both server and client. For Solaris, man automount. Yes, of course but if you don't really understand that page then is there a more detailed URL with more examples somewhere? As always the man page is intended for someone who has the basic idea and just needs reminders of syntax or the like... I need to start somewhere below that. For example: From man automount (/etc/auto_master) # Master map for automounter # +auto_master /net -hosts-nosuid /home auto_home It says that `+auto_master' is reference to NIS or NIS+ map if one exists. So if one does not exist do you leave `+auto_master' out? `/homeauto_home' Is auto_home a reference to another file somewhere? Or is it meant verbatim? Or am I supposed to know to put a map entry there... like host:/path/to ? In my case I want to mount a directory from a linux machine at /pub and another at /projects On the linux machine `pub' is found at /pub `projects' is found at /path/to/projects After studying that man page I still have no idea what my entries should look like. And further if auto_pub is a map... what does it look like? There appear to be `direct' and `indirect' ... and ... /pub linux.machine.onlan:/pubwhich, if any options ? /pub auto_pub ? (and if so, is auto_pub another file somewhere?) Then the whole question of possible options leads off into more man pages with more confusing information. That is, confusing unless you are at or above a fairly sophisticated level already. I need to see some simplified examples that take the whole matter up in one go and explain why, for someone who is not already at a fairly sophisticated level... Or in fact is in no way sophisticated at all. If it matters there are users with the same name and group. The numeric gid is also the same. Uid is different and unless I really need to, I'd as soon leave that alone since there are already numbers of files belonging to a specific (though different) number uid on both machines. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org few links that may help. I think the proper command is sharemgr if these two are not much help, I suggest do a web search using sharemgr and nfs. as keywords : http://prefetch.net/blog/index.php/2009/05/05/using-sharemgr-to-manage-nfs-file-systems-on-opensolaris-hosts/ http://blogs.oracle.com/dougm/entry/introduction_to_sharemgr ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Solaris11 zone networking on VirtualBox
Hello Folks, I installed Solaris 11 on VirtualBox and I created a zone named zdev1 by following the directions outlined here: http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-092-s11-zones-intro-524494.html Here is some information: root@solaris11:~# uname -a SunOS solaris11 5.11 11.0 i86pc i386 i86pc root@solaris11:~# cat /etc/release Oracle Solaris 11 11/11 X86 Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. Assembled 18 October 2011 root@solaris11:~# zoneadm list -civ ID NAME STATUS PATH BRANDIP 0 global running/ solaris shared 1 zdev1running/zones/zdev1 solaris excl But I can't get the zone networking to work for the life of me: root@solaris11:~# zlogin zdev1 [Connected to zone 'zdev1' pts/2] Oracle Corporation SunOS 5.11 11.0November 2011 root@zdev1:~# ifconfig -a lo0: flags=2001000849UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL mtu 8232 index 1 inet 127.0.0.1 netmask ff00 net0: flags=1000843UP,BROADCAST,RUNNING,MULTICAST,IPv4 mtu 1500 index 2 inet 192.168.1.13 netmask ff00 broadcast 192.168.1.255 ether 2:8:20:5:51:dc lo0: flags=2002000849UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL mtu 8252 index 1 inet6 ::1/128 net0: flags=20002004841UP,RUNNING,MULTICAST,DHCP,IPv6 mtu 1500 index 2 inet6 fe80::8:20ff:fe05:51dc/10 ether 2:8:20:5:51:dc Trying to ping the defaultrouter ( 192.168.1.254 ) root@zdev1:~# ping 192.168.1.254 no answer from 192.168.1.254 ofcourse trying out is not gonna work: root@zdev1:~# ping 173.194.64.103 no answer from 173.194.64.103 I can ping to my self: root@zdev1:~# ping localhost localhost is alive The zone info: root@solaris11:~# zonecfg -z zdev1 info zonename: zdev1 zonepath: /zones/zdev1 brand: solaris autoboot: true bootargs: -m verbose file-mac-profile: pool: limitpriv: scheduling-class: ip-type: exclusive hostid: fs-allowed: anet: linkname: net0 lower-link: auto allowed-address not specified configure-allowed-address: true defrouter not specified allowed-dhcp-cids not specified link-protection: mac-nospoof mac-address: random auto-mac-address: 2:8:20:5:51:dc mac-prefix not specified mac-slot not specified vlan-id not specified priority not specified rxrings not specified txrings not specified mtu not specified maxbw not specified rxfanout not specified I am not sure if this is VirtualBox related or if I am doing something wrong here. Any feedback is appreciated. Please let me know if you need more information. -Deniz. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris11 zone networking on VirtualBox
On Mon, Nov 14, 2011 at 10:46 PM, Deniz Rende deniz.re...@gmail.com wrote: root@solaris11:~# zonecfg -z zdev1 info zonename: zdev1 zonepath: /zones/zdev1 brand: solaris autoboot: true bootargs: -m verbose file-mac-profile: pool: limitpriv: scheduling-class: ip-type: exclusive hostid: fs-allowed: anet: linkname: net0 lower-link: auto It could be that this anet resource automatically picked the wrong lower link. From the global zone, what do dladm show-link and ipadm show-addr say? -- Mike Gerdts http://mgerdts.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris11 zone networking on VirtualBox
It could be that this anet resource automatically picked the wrong lower link. From the global zone, what do dladm show-link and ipadm show-addr say? I get the following information: root@solaris11:~# dladm show-link LINKCLASS MTUSTATEOVER net0phys 1500 up -- zdev1/net0 vnic 1500 up net0 root@solaris11:~# ipadm show-addr ADDROBJ TYPE STATEADDR lo0/v4static ok 127.0.0.1/8 net0/v4 static ok 192.168.1.20/24 lo0/v6static ok ::1/128 net0/v6 addrconf ok fe80::a00:27ff:fe22:cf2f/10 I don't know if it worths to mention but the version of Solaris 11 is the text installI also don't have any trouble GZ networking: root@solaris11:~# ping www.google.com www.google.com is alive -Deniz On Mon, Nov 14, 2011 at 11:08 PM, Mike Gerdts mger...@gmail.com wrote: On Mon, Nov 14, 2011 at 10:46 PM, Deniz Rende deniz.re...@gmail.com wrote: root@solaris11:~# zonecfg -z zdev1 info zonename: zdev1 zonepath: /zones/zdev1 brand: solaris autoboot: true bootargs: -m verbose file-mac-profile: pool: limitpriv: scheduling-class: ip-type: exclusive hostid: fs-allowed: anet: linkname: net0 lower-link: auto It could be that this anet resource automatically picked the wrong lower link. From the global zone, what do dladm show-link and ipadm show-addr say? -- Mike Gerdts http://mgerdts.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris11 zone networking on VirtualBox
On Mon, Nov 14, 2011 at 11:25 PM, Deniz Rende deniz.re...@gmail.com wrote: It could be that this anet resource automatically picked the wrong lower link. From the global zone, what do dladm show-link and ipadm show-addr say? I get the following information: root@solaris11:~# dladm show-link LINK CLASS MTU STATE OVER net0 phys 1500 up -- zdev1/net0 vnic 1500 up net0 root@solaris11:~# ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 net0/v4 static ok 192.168.1.20/24 lo0/v6 static ok ::1/128 net0/v6 addrconf ok fe80::a00:27ff:fe22:cf2f/10 I don't know if it worths to mention but the version of Solaris 11 is the text installI also don't have any trouble GZ networking: root@solaris11:~# ping www.google.com www.google.com is alive I suspect that what is happening is that the zdev1/net0 vnic thinks it is OK to allocate another MAC (Ethernet) address but virtualbox isn't happy with it and thinks something in the VM is trying to spoof packets There may be a way within virtualbox to disable this behavior, but I've not used virtualbox recently enough to remember. Assuming you can't disable the vbox feature that seems to be getting in the way, instead of using an anet resource which creates a vnic on top of the global zone's net0, try one of the following: Option 1: Use shared-stack zonecfg -z zdev1 remove anet linkname=net0 set ip-type=shared add net set name=net0 set addr=192.168.1.13/24 set defrouter=192.168.1.254 end exit zoneadm -z zdev1 reboot You will probably need to do some ipadm magic (ipadm delete-ip net0/something?) to make the configuration for net0 go away, else network/physical:default will probably be in maintenance. Option 2: Allocate another network In this option, you need to have virtualbox provide another NIC. That is, shut down the VM, within the VirtualBox GUI, configure a second network to look just like the first one, then boot the VM. Once you are back in Solaris: zonecfg -z zdev1 remove anet linkname=net0 add net set physical=net1 end exit zoneadm -z zdev1 reboot You will then need to transition your network configuration in the zone from net0 to net1. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris11 zone networking on VirtualBox
Hi Mike, Option 1: Use shared-stack But that means that I am not going to be able to use all the goodies that come with ip-excl. :( You will then need to transition your network configuration in the zone from net0 to net1. Do you mean, sysconfig configure here or some othe procedure. Right now it looks like this: LINKCLASS MTUSTATEOVER net0phys 1500 up -- net1phys 1500 unknown -- zdev1/net1 phys 1500 unknown -- -Deniz. On Mon, Nov 14, 2011 at 11:43 PM, Mike Gerdts mger...@gmail.com wrote: On Mon, Nov 14, 2011 at 11:25 PM, Deniz Rende deniz.re...@gmail.com wrote: It could be that this anet resource automatically picked the wrong lower link. From the global zone, what do dladm show-link and ipadm show-addr say? I get the following information: root@solaris11:~# dladm show-link LINKCLASS MTUSTATEOVER net0phys 1500 up -- zdev1/net0 vnic 1500 up net0 root@solaris11:~# ipadm show-addr ADDROBJ TYPE STATEADDR lo0/v4static ok 127.0.0.1/8 net0/v4 static ok 192.168.1.20/24 lo0/v6static ok ::1/128 net0/v6 addrconf ok fe80::a00:27ff:fe22:cf2f/10 I don't know if it worths to mention but the version of Solaris 11 is the text installI also don't have any trouble GZ networking: root@solaris11:~# ping www.google.com www.google.com is alive I suspect that what is happening is that the zdev1/net0 vnic thinks it is OK to allocate another MAC (Ethernet) address but virtualbox isn't happy with it and thinks something in the VM is trying to spoof packets There may be a way within virtualbox to disable this behavior, but I've not used virtualbox recently enough to remember. Assuming you can't disable the vbox feature that seems to be getting in the way, instead of using an anet resource which creates a vnic on top of the global zone's net0, try one of the following: Option 1: Use shared-stack zonecfg -z zdev1 remove anet linkname=net0 set ip-type=shared add net set name=net0 set addr=192.168.1.13/24 set defrouter=192.168.1.254 end exit zoneadm -z zdev1 reboot You will probably need to do some ipadm magic (ipadm delete-ip net0/something?) to make the configuration for net0 go away, else network/physical:default will probably be in maintenance. Option 2: Allocate another network In this option, you need to have virtualbox provide another NIC. That is, shut down the VM, within the VirtualBox GUI, configure a second network to look just like the first one, then boot the VM. Once you are back in Solaris: zonecfg -z zdev1 remove anet linkname=net0 add net set physical=net1 end exit zoneadm -z zdev1 reboot You will then need to transition your network configuration in the zone from net0 to net1. -- Mike Gerdts http://mgerdts.blogspot.com/ -- ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
