SUSE RPM issue

2014-06-10 Thread Mainframe Mainframe
Hello,
  We have requirement to install makedepend on /usr/X11R6/bin on
SL10SP2. But I am not able to find required RPM . but somewhere I
found XFree86-devel-4.3.99.902-43.48 is required but not sure on this. I
also checked SL10SP2 repository but I couldn't find
this XFree86-devel-4.3.99.902-43.48  in repository . Any anyone suggest,
what exact rpm do we need to install this makedepend

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: NFS migration

2014-06-10 Thread Offer Baruch
have a look at the "vserver export-policy rule create" command.
i think this sould work with the -superuser parameter set to sys and
the -clientmatch set to your nfs_client hostname.
here is a link to the command reference...
https://library.netapp.com/ecm/ecm_download_file/ECMP1196817
i don't have a cluster mode data-ontap so i can't test it but it sould look
somthing like this:

vserver export-policy rule create -vserver  -policyname
 root_access -ruleindex 1 -protocol nfs -clientmatch 
-superuser sys

you might also need the -rwrule and -rorule parameters... i am not sure...

hope this helps...

Offer Baruch


On Tue, Jun 10, 2014 at 5:57 PM, Jake anderson 
wrote:

> This command does not works in cluster mode.
> On 10 Jun 2014 00:43, "Offer Baruch"  wrote:
>
> > You need the root option...
> > root=clientid[:clientid...]
> > Specifies which NFS clients have root access to the file system path. If
> > you specify the root= option, you must specify at least one NFS client
> > identifier. To exclude NFS clients from the list, prepend the NFS client
> > identifiers with a minus sign (-).
> >
> > Offer Baruch
> > On Jun 9, 2014 9:25 PM, "Jake anderson" 
> wrote:
> >
> > > I have tried to export with anon=0 but still as a root fron linux I am
> > > unable to change the owner. Not sure where I am missing.
> > >
> > > Jake
> > > On 9 Jun 2014 22:49, "Offer Baruch"  wrote:
> > >
> > > > Dns should work just fine...
> > > > Just google for it...
> > > > I think root= is the correct syntax...
> > > > Server should be where you mount the nfs...
> > > >
> > > > Offer
> > > > On Jun 9, 2014 7:03 PM, "Jake anderson" 
> > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Yes this is a netapp exporting the nfs. Could you please provide me
> > > whole
> > > > > syntax ? we gave the DNS instead of serverip. Are there any
> > difference
> > > ?
> > > > >
> > > > >
> > > > > On Mon, Jun 9, 2014 at 9:27 PM, Offer Baruch <
> offerbar...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Is this a netapp exporting the nfs?
> > > > > > If so you need the root= export option?
> > > > > > If this is linux then you need the no_root_squash option...
> > > > > >
> > > > > > Offer Baruch
> > > > > > On Jun 9, 2014 6:27 PM, "Jake anderson" <
> justmainfra...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > We again exported the path as anon=0,unmounted and mounted, but
> > > still
> > > > > the
> > > > > > > root level of user is unable to change the Ownership.
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie <
> > > beatt...@uk.ibm.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Jake anderson writes:
> > > > > > > > > Recently we did a migration from one NFS storage server to
> > > > another
> > > > > > NFS
> > > > > > > > > storage server. During this Migration all the copied File
> had
> > > > > owners
> > > > > > as
> > > > > > > > > root. In the recent NFS storage server the FTP server
> option
> > is
> > > > no
> > > > > > more
> > > > > > > > > available so we have mounted the NFS storage to a linux
> > running
> > > > on
> > > > > > > VMware
> > > > > > > > > infra(as a ftp server). So when we try change the owner of
> > any
> > > > file
> > > > > > > > > mounted to Linux we get a permission denied(Even when we
> try
> > it
> > > > as
> > > > > > > root).
> > > > > > > > > The message we get is "permission denied"(This is the only
> > > > > message).
> > > > > > > The
> > > > > > > > ls
> > > > > > > > > -l clearly gives that all the file has the owner as root.
> > > > > > > > >
> > > > > > > > > Has any undergone this situation ? Why a root cannot change
> > the
> > > > > > > > owner(root)
> > > > > > > > > to someother ID ?
> > > > > > > > > Since the files have the User and Group copied from
> previous
> > > NFS
> > > > > > > storage.
> > > > > > > > > Aren't there anyways to change the Owner and Group from
> > Linux ?
> > > > > > > >
> > > > > > > > It's the NFS server that's forbidding it. It's very common in
> > all
> > > > > > > > but the snazziest of NFS environments for the NFS server to
> > > > "squash"
> > > > > > > > the root user of NFS clients and treat it as an unprivileged,
> > > > > > > > anonymous user. This avoids having a root user on any NFS
> > client
> > > > > > > > getting root-level access to all exported files on the
> server.
> > > > > > > >
> > > > > > > > For a Linux-based NFS server, the export options
> "root_squash"
> > > > > > > > (which is the default) and "all_squash" (probably not the
> case
> > > > here)
> > > > > > > > do this. You need an explicit export option "no_root_squash"
> to
> > > > allow
> > > > > > > > root on the chosen NFS clients to be allowed to chown and
> > access
> > > > > > > > exported files as though they were uid 0 on the server. Other
> > NFS
> > > > > > > > servers or appliances may present the option differently.
> > > > > > > >
> > > > > > > > --Malcolm
> > > > > > > >

Re: NFS migration

2014-06-10 Thread Jake anderson
This command does not works in cluster mode.
On 10 Jun 2014 00:43, "Offer Baruch"  wrote:

> You need the root option...
> root=clientid[:clientid...]
> Specifies which NFS clients have root access to the file system path. If
> you specify the root= option, you must specify at least one NFS client
> identifier. To exclude NFS clients from the list, prepend the NFS client
> identifiers with a minus sign (-).
>
> Offer Baruch
> On Jun 9, 2014 9:25 PM, "Jake anderson"  wrote:
>
> > I have tried to export with anon=0 but still as a root fron linux I am
> > unable to change the owner. Not sure where I am missing.
> >
> > Jake
> > On 9 Jun 2014 22:49, "Offer Baruch"  wrote:
> >
> > > Dns should work just fine...
> > > Just google for it...
> > > I think root= is the correct syntax...
> > > Server should be where you mount the nfs...
> > >
> > > Offer
> > > On Jun 9, 2014 7:03 PM, "Jake anderson" 
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > Yes this is a netapp exporting the nfs. Could you please provide me
> > whole
> > > > syntax ? we gave the DNS instead of serverip. Are there any
> difference
> > ?
> > > >
> > > >
> > > > On Mon, Jun 9, 2014 at 9:27 PM, Offer Baruch 
> > > > wrote:
> > > >
> > > > > Is this a netapp exporting the nfs?
> > > > > If so you need the root= export option?
> > > > > If this is linux then you need the no_root_squash option...
> > > > >
> > > > > Offer Baruch
> > > > > On Jun 9, 2014 6:27 PM, "Jake anderson" 
> > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > We again exported the path as anon=0,unmounted and mounted, but
> > still
> > > > the
> > > > > > root level of user is unable to change the Ownership.
> > > > > >
> > > > > >
> > > > > > On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie <
> > beatt...@uk.ibm.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Jake anderson writes:
> > > > > > > > Recently we did a migration from one NFS storage server to
> > > another
> > > > > NFS
> > > > > > > > storage server. During this Migration all the copied File had
> > > > owners
> > > > > as
> > > > > > > > root. In the recent NFS storage server the FTP server option
> is
> > > no
> > > > > more
> > > > > > > > available so we have mounted the NFS storage to a linux
> running
> > > on
> > > > > > VMware
> > > > > > > > infra(as a ftp server). So when we try change the owner of
> any
> > > file
> > > > > > > > mounted to Linux we get a permission denied(Even when we try
> it
> > > as
> > > > > > root).
> > > > > > > > The message we get is "permission denied"(This is the only
> > > > message).
> > > > > > The
> > > > > > > ls
> > > > > > > > -l clearly gives that all the file has the owner as root.
> > > > > > > >
> > > > > > > > Has any undergone this situation ? Why a root cannot change
> the
> > > > > > > owner(root)
> > > > > > > > to someother ID ?
> > > > > > > > Since the files have the User and Group copied from previous
> > NFS
> > > > > > storage.
> > > > > > > > Aren't there anyways to change the Owner and Group from
> Linux ?
> > > > > > >
> > > > > > > It's the NFS server that's forbidding it. It's very common in
> all
> > > > > > > but the snazziest of NFS environments for the NFS server to
> > > "squash"
> > > > > > > the root user of NFS clients and treat it as an unprivileged,
> > > > > > > anonymous user. This avoids having a root user on any NFS
> client
> > > > > > > getting root-level access to all exported files on the server.
> > > > > > >
> > > > > > > For a Linux-based NFS server, the export options "root_squash"
> > > > > > > (which is the default) and "all_squash" (probably not the case
> > > here)
> > > > > > > do this. You need an explicit export option "no_root_squash" to
> > > allow
> > > > > > > root on the chosen NFS clients to be allowed to chown and
> access
> > > > > > > exported files as though they were uid 0 on the server. Other
> NFS
> > > > > > > servers or appliances may present the option differently.
> > > > > > >
> > > > > > > --Malcolm
> > > > > > >
> > > > > > > --
> > > > > > > Malcolm Beattie
> > > > > > > Linux and System z Technical Consultant
> > > > > > > IBM UK Systems and Technology Group
> > > > > > >
> > > > > > >
> > > >
> --
> > > > > > > For LINUX-390 subscribe / signoff / archive access
> instructions,
> > > > > > > send email to lists...@vm.marist.edu with the message: INFO
> > > > LINUX-390
> > > > > or
> > > > > > > visit
> > > > > > > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > > > > > >
> > > >
> --
> > > > > > > For more information on Linux on System z, visit
> > > > > > > http://wiki.linuxvm.org/
> > > > > > >
> > > > > >
> > > > > >
> > > --
> > > > > > For LINUX-390 subscribe / signoff / archive access instructions,
> > > > > > send email to lists...@vm.marist.edu with the message: INFO
> >