Re: Mount_nfs question

2011-05-30 Thread Thiago Damas
Maybe you can use "showmount -a SERVER-IP", foreach server you have... Thiago 2011/5/30 Mark Saad : > On Mon, May 30, 2011 at 8:13 PM, Rick Macklem wrote: >>> Hello All >>> So I am stumped on this one. I want to know what the IP of each >>> nfs server that is providing each nfs export. I am run

Re: Mount_nfs question

2011-05-30 Thread Mark Saad
On Mon, May 30, 2011 at 8:13 PM, Rick Macklem wrote: >> Hello All >> So I am stumped on this one. I want to know what the IP of each >> nfs server that is providing each nfs export. I am running 7.4-RELEASE >> When I run "mount -t nfs" I see something like this >> >> VIP-01:/export/source on /mnt/

Re: Mount_nfs question

2011-05-30 Thread Rick Macklem
> Hello All > So I am stumped on this one. I want to know what the IP of each > nfs server that is providing each nfs export. I am running 7.4-RELEASE > When I run "mount -t nfs" I see something like this > > VIP-01:/export/source on /mnt/src > VIP-02:/export/target on /mnt/target > VIP-01:/export

Mount_nfs question

2011-05-30 Thread Mark Saad
Hello All So I am stumped on this one. I want to know what the IP of each nfs server that is providing each nfs export. I am running 7.4-RELEASE When I run "mount -t nfs" I see something like this VIP-01:/export/source on /mnt/src VIP-02:/export/target on /mnt/target VIP-01:/export/lo

Re: Freebsd on the sun x4440

2011-05-30 Thread Mark Saad
On Sat, May 28, 2011 at 8:47 PM, Erich Dollansky wrote: > Hi, > > I would like to suggest to try 8.2. > > It is my experience that the different version behave very different on the > same hardware. It does not mean that the newer version is the better. As an > example, I have a machine here on

Re: compiler warnings (was: Re: [rfc] a few kern.mk and bsd.sys.mk related changes)

2011-05-30 Thread Dieter BSD
Chris writes: >> Ports need attention. The warnings I get there are frightening. > > I find it comforting that they're just that: warnings. > > How do they frighten you? High quality code does not have any warnings. The most frightening thing is the attitute that "They're just warnings, so I'll i

Re: compiler warnings (was: Re: [rfc] a few kern.mk and bsd.sys.mk related changes)

2011-05-30 Thread Alexander Best
On Mon May 30 11, Dieter BSD wrote: > > maybe we find some nice -Wwarning options which are reasonable > > to have > > -Wmissing-declarations > -Wimplicit > > FreeBSD's gcc doesn't seem to have  -Wcoercion  ??? > Bugzilla indicates that it was added years ago (2006?). -Wcoercion seems to have on

Re: compiler warnings (was: Re: [rfc] a few kern.mk and bsd.sys.mk related changes)

2011-05-30 Thread Chris Rees
On 30 May 2011 18:44, Dieter BSD wrote: >> maybe we find some nice -Wwarning options which are reasonable >> to have > > -Wmissing-declarations > -Wimplicit > > FreeBSD's gcc doesn't seem to have  -Wcoercion  ??? > Bugzilla indicates that it was added years ago (2006?). > > It would be really real

Re: compiler warnings (was: Re: [rfc] a few kern.mk and bsd.sys.mk related changes)

2011-05-30 Thread Dieter BSD
> maybe we find some nice -Wwarning options which are reasonable > to have -Wmissing-declarations -Wimplicit FreeBSD's gcc doesn't seem to have  -Wcoercion  ??? Bugzilla indicates that it was added years ago (2006?). It would be really really nice if -static worked on (nearly) everything. > and

Re: Active slice, only for a next boot

2011-05-30 Thread Dieter BSD
>> I have i.e; 3 slices, of which first is active. >> Now I wana set slice 2 active, but only for a one/next boot. >> Once slice 2 is booted and system is shutdown or rebooted, >> once again, first slice is active and booted, without user's intervention. I think that setting the active slice is th