Good to know if it will work with nfsv4 server started via rc.conf and
sysctl values in sysctl.conf..
build a kernel with "options NFSD" in its config file and then try it
with that kernel, and then you'll find out...
How about patching the /etc/rc.d/nfsd script like this:
[..]
nfsd_precmd(
Again, it works for me (using a pretty current FreeBSD client). The
only difference is that I never run mount_nfs directly and would use
the following command:
# mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4
Assuming the client is a FreeBSD8 box on the 192.168.183.0 subnet,
I don't kno
On Sun, Jan 9, 2011 at 1:22 PM, Marc UBM Bocklet wrote:
> On Sun, 9 Jan 2011 11:45:52 -0500
> Chris Brennan wrote:
>
> > Did you try
> > http://www.freebsdwiki.net/index.php/High_Resolution_Console?
>
> Yeah, those are the kernel settings that I've been using since approx.
> 2004 :-). But the wi
On Sun, 9 Jan 2011 11:45:52 -0500
Chris Brennan wrote:
> Did you try
> http://www.freebsdwiki.net/index.php/High_Resolution_Console?
Yeah, those are the kernel settings that I've been using since approx.
2004 :-). But the wiki page yielded a new data point - trying to set
MODE_280 (which corresp
On amd64 r217010 laptop (HP Compaq 6715s)
I'm trying to use this wi(4) device:
wi0:
at port 0x100-0x13f irq 20 function 0 config 1 on pccard0
I do
# ifconfig wlan0 create wlandev wi0
# ifconfig -a
bge0: flags=8843 metric 0 mtu 1500
options=8009b
ether 00:1a:4b:89:4b:4e
>
> Good to know if it will work with nfsv4 server started via rc.conf and
> sysctl values in sysctl.conf..
>
build a kernel with "options NFSD" in its config file and then try it
with that kernel, and then you'll find out...
___
freebsd-current@freebsd
Erik Cederstrand píše v ne 09. 01. 2011 v 00:10 +0100:
> I was pretty sure I couldn't improve anything with 5 minutes of
> thinking. I'm glad the most obvious things have already been done, and
> I'm sure you and others have put a lot of effort into this. My
> question was more what, if anything,
- Original Message -
> > It just worked for me. Try setting the sysctl before starting nfsd.
> > If
> > you are starting the daemons manually for a kernel that doesn't have
> > "options NFSD" do:
> >
> > # nfsuserd
> > # mountd -e -r
> > # sysctl vfs.newnfs.server_min_nfsvers=4
> > # nfsd
>Hiho! :-)
>
>Yesterday I upgraded to
>
>FreeBSD hostname 9.0-CURRENT FreeBSD 9.0-CURRENT #28: Sat Jan 8
>17:05:30 CET 2011
>
>and vidcontrol VESA_800x600 stopped working (again). I exchanged emails
>with jkim about a similar problem in February 2010 (vidcontrol
>VESA_800x600 would mangle the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/11 12:57, David Wolfskill wrote:
> As usual, I have been tracking, building, & booting head daily on my
> laptop for a while.
>
> Yesterday, having built head at r217090, I had updated to r217145,
> built, and booted it OK. (I then booted fr
As usual, I have been tracking, building, & booting head daily on my
laptop for a while.
Yesterday, having built head at r217090, I had updated to r217145,
built, and booted it OK. (I then booted from my stable/8 slice for the
rest of the day, as usual.)
This morning, I updated to r217189, but o
Did you try http://www.freebsdwiki.net/index.php/High_Resolution_Console?
-- Sent from my Droid
On Jan 9, 2011 6:58 AM, "Marc UBM Bocklet"
wrote:
>
> Hiho! :-)
>
> Yesterday I upgraded to
>
> FreeBSD hostname 9.0-CURRENT FreeBSD 9.0-CURRENT #28: Sat Jan 8
> 17:05:30 CET 2011
>
> and vidcontrol V
It just worked for me. Try setting the sysctl before starting nfsd. If
you are starting the daemons manually for a kernel that doesn't have
"options NFSD" do:
# nfsuserd
# mountd -e -r
# sysctl vfs.newnfs.server_min_nfsvers=4
# nfsd -e -u -t -n 8
- mountd -e loads the module, so you can do the
Hi,
I removed uart from my kernel configuration - when I tried to load it
later as a module I got the following error:
acpi_timer0: couldn't allocate resource (port 0x4008)
driver bug: Unable to set devclass (devname: (null))
--
Bruce Cran
___
freebsd
>
> After manually setting:
>
> salwe...@freebsd:/etc#sudo sysctl vfs.newnfs.server_max_nfsvers=4
> vfs.newnfs.server_max_nfsvers: 4 -> 4
> salwe...@freebsd:/etc#sudo sysctl vfs.newnfs.server_min_nfsvers=4
> vfs.newnfs.server_min_nfsvers: 4 -> 4
> salwe...@freebsd:/etc#
>
> We are still able to
What I am missing ?
/etc/sysctl.conf is applied before rc.d/nfs* ?
That would be my guess. The sysctl's aren't setable until the modules
are loaded. If you build a kernel with "options NFSD" in its kernel
config file, then it should be setable as above, I think? (I always
use sysctl manually a
Hiho! :-)
Yesterday I upgraded to
FreeBSD hostname 9.0-CURRENT FreeBSD 9.0-CURRENT #28: Sat Jan 8
17:05:30 CET 2011
and vidcontrol VESA_800x600 stopped working (again). I exchanged emails
with jkim about a similar problem in February 2010 (vidcontrol
VESA_800x600 would mangle the screen outpu
Hiho! :-)
Yesterday I upgraded to
FreeBSD hostname 9.0-CURRENT FreeBSD 9.0-CURRENT #28: Sat Jan 8
17:05:30 CET 2011
and vidcontrol VESA_800x600 stopped working (again). I exchanged emails
with jkim about a similar problem in February 2010 (vidcontrol
VESA_800x600 would mangle the screen outpu
Hi,
1. I have a NFSv4-enabled server with /etc/exports like:
V4: / -sec=sys
/home/stud -sec=sys
/etc/rc.conf:
nfs_server_enable=YES
nfsv4_server_enable=YES
nfsuserd_enable=YES
Is it possible to run ONLY NFSv4 server (without NFSv3 compatibility) ?
2. On a client station I installed pam_mount
19 matches
Mail list logo