NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Marek Salwerowicz
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

lockup with vidcontrol VESA_800x600

2011-01-09 Thread Marc UBM Bocklet
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

lockup with vidcontrol VESA_800x600

2011-01-09 Thread Marc UBM Bocklet
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

Re: NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Marek Salwerowicz
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

Re: NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Rick Macklem
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 mount via

Loading uart module fails

2011-01-09 Thread Bruce Cran
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 ___

Re: NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Marek Salwerowicz
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

Re: lockup with vidcontrol VESA_800x600

2011-01-09 Thread Chris Brennan
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 ubm.free...@googlemail.com wrote: Hiho! :-) Yesterday I upgraded to FreeBSD hostname 9.0-CURRENT FreeBSD 9.0-CURRENT #28: Sat Jan 8 17:05:30 CET 2011

Lock-up with CPU busy at r217145; seems OK now at r217189

2011-01-09 Thread David Wolfskill
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

Re: Lock-up with CPU busy at r217145; seems OK now at r217189

2011-01-09 Thread Michael Butler
-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 from my

R: lockup with vidcontrol VESA_800x600

2011-01-09 Thread Barbara
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

Re: NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Rick Macklem
- 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 -e -u -t -n 8

Re: HEADS UP: Merge of binutils 2.17

2011-01-09 Thread Pav Lucistnik
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, can

Re: NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Rick Macklem
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.org

console freeze after ifconfig wlan0 scan with wi(4) pccard device

2011-01-09 Thread Anton Shterenlikht
On amd64 r217010 laptop (HP Compaq 6715s) I'm trying to use this wi(4) device: wi0: The Linksys Group, Inc. Instant Wireless Network PC Card at port 0x100-0x13f irq 20 function 0 config 1 on pccard0 I do # ifconfig wlan0 create wlandev wi0 # ifconfig -a bge0:

Re: lockup with vidcontrol VESA_800x600

2011-01-09 Thread Marc UBM Bocklet
On Sun, 9 Jan 2011 11:45:52 -0500 Chris Brennan xa...@xaerolimit.net 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

Re: lockup with vidcontrol VESA_800x600

2011-01-09 Thread Chris Brennan
On Sun, Jan 9, 2011 at 1:22 PM, Marc UBM Bocklet ubm.free...@googlemail.com wrote: On Sun, 9 Jan 2011 11:45:52 -0500 Chris Brennan xa...@xaerolimit.net wrote: Did you try http://www.freebsdwiki.net/index.php/High_Resolution_Console? Yeah, those are the kernel settings that I've been

Re: NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Marek Salwerowicz
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

Re: NFSv4 and pam_mount - mounting user home directories.

2011-01-09 Thread Marek Salwerowicz
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()