headers
Matthew Herzog | 1 Jun 2007 01:41
Picon

mounting Solaris 10 NFS share

Hey all.

I'm trying to mount a Solaris 10 NFS share from my FreeBSD 6.2-STABLE
machine and I'm having some permissions problems.

Here's my /etc/dfs/dfstab file on Solaris 10.

share -F nfs  -o rw=spark -d "generic" /export/home/mush

and the line in /etc/fstab on FreeBSD:

192.168.0.26:/export/home/mush     /mnt/share     nfs    0     0

I am able to mount the share but unable to access it on the FreeBSD
machine. In fact I can't even cd into /mnt/share as root on FreeBSD.
Changinf the dir's permissions to 0777 on Solaris does "fix" the
problem but . . . it's not a solution.

Thanks for any help.

-- Matt
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Vinny Abello | 1 Jun 2007 02:12
Favicon

Re: Packet Loss w/bge & BCM5703 on Dell PE2650

Abdullah Ibn Hamad Al-Marri wrote:
>> I've installed an Intel Pro/100 adapter in the Dell PowerEdge 2650. This
>> is an Intel 82550 chipset. The packet loss problem is completely gone
>> when using this NIC in the server, so it is definitely related to the
>> bge driver and this chipset BCM5703 or something else in the server. I'm
>> going to try and isolate which major release this problem appeared.
>> Maybe this will help isolate the change that is causing this issue for
>> me.
> 
> I still suggest you csup to stable, there are changes made to the driver :)

OK, just did a cvsup to the latest RELENG_6 from today, recompiled and
still have the same problem with the newer bge code, so that didn't help. :(

Again, the fxp card works ok. It seems there is no easy fix for this at
the moment so I may end up just sticking fxp cards in these model
servers and disabling the integrated bge cards. :-/

--

-- 

Vinny Abello
Network Engineer
vinny <at> tellurian.com
(973)940-6100
PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325 FBCB 0100 977A

Tellurian Networks - The Ultimate Internet Connection
http://www.tellurian.com (888)TELLURIAN

"Courage is resistance to fear, mastery of fear - not absence of fear"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kris Kennaway | 1 Jun 2007 02:13

Re: mounting Solaris 10 NFS share

On Thu, May 31, 2007 at 11:41:00PM +0000, Matthew Herzog wrote:
> Hey all.
> 
> I'm trying to mount a Solaris 10 NFS share from my FreeBSD 6.2-STABLE
> machine and I'm having some permissions problems.
> 
> Here's my /etc/dfs/dfstab file on Solaris 10.
> 
> share -F nfs  -o rw=spark -d "generic" /export/home/mush
> 
> and the line in /etc/fstab on FreeBSD:
> 
> 192.168.0.26:/export/home/mush     /mnt/share     nfs    0     0
> 
> I am able to mount the share but unable to access it on the FreeBSD
> machine. In fact I can't even cd into /mnt/share as root on FreeBSD.
> Changinf the dir's permissions to 0777 on Solaris does "fix" the
> problem but . . . it's not a solution.

Isn't this usually because of a mismatch with credentials (uid/gid)
between server and client?  i.e. why do you think this is a FreeBSD
NFS client issue?

Kris
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel O'Connor | 1 Jun 2007 07:22
Picon
Favicon

Re: Unable to install FreeBSD from external USB cdrom

On Friday 01 June 2007 04:58, Vivek Khera wrote:
> On May 31, 2007, at 1:49 AM, Daniel O'Connor wrote:
> > Thanks so much, now I can have an automated install on a USB stick
> > :)
>
> please, please, please share the recipes to make this.  I would love
> to omit CD rom drives on my future systems as the only thing i ever
> use them for is install.
>
> also, can you run "fixit" mode from your USB stick, too?

I haven't actually done it yet, however I was thinking of making a basic 
FreeSBIE disk but split it into a UFS and a DOS partition. I'd put the 
dist files on the FAT partition as well as a tar ball I splat over the 
disk after install (that contains all the packages etc.. it is much 
faster than pkg_add which is what I used to use, it is also more easily 
tweaked).

The FAT partition would also have an install.cfg which sysinstall could 
read (I have sysinstall patches for this).

The reason for using FAT to store the dist files etc is that it would 
allow people to easily tweak the config and the like (useful in our 
situation probably less so for you)

One thing I'm not sure about is how to run sysinstall after boot. A 
normal install CD uses it as init but I don't think that will work very 
well here since FreeSBIE works differently.

The other approach would be to just splat an install CD onto a flash
(Continue reading)

Permalink | Reply | 1 comment |
headers
Claus Guttesen | 1 Jun 2007 09:47
Picon

Re: mounting Solaris 10 NFS share

> I'm trying to mount a Solaris 10 NFS share from my FreeBSD 6.2-STABLE
> machine and I'm having some permissions problems.
>
> Here's my /etc/dfs/dfstab file on Solaris 10.
>
> share -F nfs  -o rw=spark -d "generic" /export/home/mush
>
> and the line in /etc/fstab on FreeBSD:
>
> 192.168.0.26:/export/home/mush     /mnt/share     nfs    0     0
>
> I am able to mount the share but unable to access it on the FreeBSD
> machine. In fact I can't even cd into /mnt/share as root on FreeBSD.
> Changinf the dir's permissions to 0777 on Solaris does "fix" the
> problem but . . . it's not a solution.

As mentioned earlier it is probably a mismatch between uid/gid. And by
default root is *not* allowed access to nfs-shares unless you specify
map-root=root (freebsd-syntax) on your nfs-server, albeit this is
*not* recommended as well to grant root access to nfs.

--

-- 
regards
Claus

When lenity and cruelty play for a kingdom,
the gentlest gamester is the soonest winner.

Shakespeare
_______________________________________________
(Continue reading)

Permalink | Reply | 1 comment |
headers
Juraj Lutter | 1 Jun 2007 11:52
Picon

Re: mounting Solaris 10 NFS share

On 6/1/07, Claus Guttesen <kometen <at> gmail.com> wrote:
> As mentioned earlier it is probably a mismatch between uid/gid. And by
> default root is *not* allowed access to nfs-shares unless you specify
> map-root=root (freebsd-syntax) on your nfs-server, albeit this is
> *not* recommended as well to grant root access to nfs.

Try to use NFSv3 on Solaris side.

otis

--

-- 
Sincerely yours,
Juraj Lutter
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Daniel O'Connor | 1 Jun 2007 16:04
Picon
Favicon

Re: Unrecognized archive format with RELENG_6_2 and RELENG_6

On Friday 01 June 2007 19:10, Robin Gruyters wrote:
> This happends when the following command is used:
>
> # tar -tf /dev/sa0
>
> It will show you the first 10 files and then exits.
> After searching the MARC list, I found the following post:

What happens if you try
tar -b 128 -tf /dev/sa0

What did you upgrade from? Some gnutar using system I guess? (5.x or 
4.x?)

--

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Permalink | Reply | 15 comments |
headers
Robin Gruyters | 1 Jun 2007 16:09
Picon

Re: Unrecognized archive format with RELENG_6_2 and RELENG_6

> What happens if you try
> tar -b 128 -tf /dev/sa0
>
Same problem.

> What did you upgrade from? Some gnutar using system I guess? (5.x or
> 4.x?)
>
I'd upgraded from FreeBSD 6.1-RELEASE-p10

Kind regards,

Robin Gruyters
Network and Security Engineer
Yirdis B.V.
I: http://yirdis.com
P: +31 (0)36 5300394
F: +31 (0)36 5489119

Quoting Daniel O'Connor <doconnor <at> gsoft.com.au>:

> On Friday 01 June 2007 19:10, Robin Gruyters wrote:
>> This happends when the following command is used:
>>
>> # tar -tf /dev/sa0
>>
>> It will show you the first 10 files and then exits.
>> After searching the MARC list, I found the following post:
>
> What happens if you try
(Continue reading)

Permalink | Reply | 14 comments |
headers
Daniel O'Connor | 2 Jun 2007 01:22
Picon
Favicon

Re: Unrecognized archive format with RELENG_6_2 and RELENG_6

On Friday 01 June 2007 23:39, Robin Gruyters wrote:
> > What happens if you try
> > tar -b 128 -tf /dev/sa0
>
> Same problem.
>
> > What did you upgrade from? Some gnutar using system I guess? (5.x
> > or 4.x?)
>
> I'd upgraded from FreeBSD 6.1-RELEASE-p10

OK.
Can you read the archive as a normal file from the tape? eg dd 
if=/dev/sa0 of=/tmp/foo

If so does it work? Are you getting errors reading from the drive, or 
just the tar file is broken?

I don't really have any other suggestions though sorry.

--

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Permalink | Reply | 13 comments |
headers
Chris | 2 Jun 2007 09:45
Picon

Re: release cycle

On 29/05/07, Mark Linimon <linimon <at> lonesome.com> wrote:
> On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote:
> > Agreed.  6.3-RELEASE would nominally be due around July but the lack
> > of any schedule on http://www.freebsd.org/releng/ suggests that it will
> > be later than that.  The plans to start the 7.0-RELEASE cycle will also
> > impact this.
>
> At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and
> released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping
> so as to reuse the same ports freeze).
>
> The ports tree is not even close to stable enough to release right now.
>
> mcl
> _______________________________________________
> freebsd-stable <at> freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
>

Given that Kris repeatedly tells me and others that the ports system
is only supported on the latest freebsd release (meaning one has to be
upgrading freebsd on their servers every few months to get this
support) if 7.0 and 6.3 are released around the same time will the
ports tree be supported on both?

Due to the fact the ports tree is only supported on the latest freebsd
release I propose longer release cycles for example not releasing 6.3
until 6.2 is almost EOL rather then having 2 releases overlap each
other because the current situation is there is a release that is
(Continue reading)

Permalink | Reply | 12 comments |

Gmane