Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-09:05.null

2009-10-07 Thread Bjoern A. Zeeb 

On Wed, 7 Oct 2009, Philip M. Gollucci wrote:




Corrected:  2009-10-02 18:09:56 UTC (RELENG_8, 8.0-RC2)
2009-10-02 18:09:56 UTC (RELENG_7, 7.2-STABLE)
2009-10-02 18:09:56 UTC (RELENG_7_2, 7.2-RELEASE-p4)
2009-10-02 18:09:56 UTC (RELENG_7_1, 7.1-RELEASE-p8)
2009-10-02 18:09:56 UTC (RELENG_6, 6.4-STABLE)
2009-10-02 18:09:56 UTC (RELENG_6_4, 6.4-RELEASE-p7)
2009-10-02 18:09:56 UTC (RELENG_6_3, 6.3-RELEASE-p13)



- -
RELENG_6
RELENG_6_4
RELENG_6_3
RELENG_7
RELENG_7_2
RELENG_7_1
RELENG_8
- -



Branch/path  Revision
- -
stable/6/ r197715
releng/6.4/   r197715
releng/6.3/   r197715
stable/7/ r197715
releng/7.2/   r197715
releng/7.1/   r197715
stable/8/ r197714
- -


Don't these usually mention HEAD/CURRENT ?


No.



and is the 197714 a typo ?


No. That was a separate MFC from HEAD in constrast to stable/7,8 which
were committed along with the 2 security advisories.


The correction date in the first line is a bit off though, as the 8.0-RC2
MFC had been a few minutes earlier.

/bz

--
Bjoern A. Zeeb It will not break if you know what you are doing.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Installing Cacti from Ports

2009-10-07 Thread mailinglist 
I hada VM running an older installation of FreeBSD 7.2.  I recently got back to 
it and tried to install Cacti from the ports collection.  I cvsup'd in an 
up-to-date ports collection, and did the usual "make, make install" for Cacti.  
During the "make install" process a dependency failed to build.  I believe it 
was xcb-utils that failed to build because XCB was at version 1.2 and needed to 
be at 1.4.  I couldn't get the issue resolved no matter what I tried.  I ended 
up giving up.later on I went through the "freebsd-update" process and 
upgraded to a newer version of 7.2.  After that Cacti and all dependencies 
built and installed successfully.  Was XCB upgraded when I did the 
freebsd-update process?  Or what?  I'm just trying to find out what 
happened.  Thanks! ___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

samba - SIGABRT

2009-10-07 Thread Oliver Lehmann 
Hi,

I wonder what may have caused this and how should I debug it to find the
source? I Installed samba 3.3.7 on a clean 8.0-RC1 and I upgraded then my
system to the latest RELENG_8.
Since I've not the time searching much longer for the error I'll just go
to upgrade to 3.3.8 (recompile it...) tomorrow but I'm curious what it
may have caused and how I would have been able to find the cause


r...@nudel samba33> /usr/local/sbin/smbd
Abort
Exit 134


r...@nudel samba33> gdb
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
(gdb) exec /usr/local/sbin/smbd
(gdb) run
Starting program: /usr/local/sbin/smbd 

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
You can't do that without a process to debug.
(gdb) q   
r...@nudel samba33> ktrace /usr/local/sbin/smbd
Abort
Exit 134
r...@nudel samba33> kdump
  2605 ktrace   RET   ktrace 0
  2605 ktrace   CALL  execve(0xbfbfed83,0xbfbfec50,0xbfbfec58)
  2605 ktrace   NAMI  "/usr/local/sbin/smbd"
r...@nudel samba33> mount -t procfs /dev/null /proc
r...@nudel samba33> truss -fad /usr/local/sbin/smbd
truss: can not get etype: No such process
Exit 2
r...@nudel samba33> dmesg | tail -1
fxp0: Microcode loaded, int_delay: 1000 usec  bundle_max: 6
r...@nudel samba33> ldd /usr/local/sbin/smbd
/usr/local/sbin/smbd:
libcrypt.so.5 => /lib/libcrypt.so.5 (0x281aa000)
libpam.so.5 => /usr/lib/libpam.so.5 (0x281c3000)
libexecinfo.so.1 => /usr/local/lib/libexecinfo.so.1 (0x281cb000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x288d2000)
libpopt.so.0 => /usr/local/lib/libpopt.so.0 (0x281d6000)
libc.so.7 => /lib/libc.so.7 (0x28091000)
libm.so.5 => /lib/libm.so.5 (0x281df000)
libintl.so.8 => /usr/local/lib/libintl.so.8 (0x289d1000)
r...@nudel samba33> ls -l /lib/libcrypt.so.5 /usr/lib/libpam.so.5 
/usr/local/lib/libexecinfo.so.1 /usr/local/lib/libiconv.so.3 
/usr/local/lib/libpopt.so.0 /lib/libc.so.7 /lib/libm.so.5 
/usr/local/lib/libintl.so.8
-r--r--r--  1 root  wheel  1144500 Oct  5 16:40 /lib/libc.so.7
-r--r--r--  1 root  wheel32060 Oct  5 16:41 /lib/libcrypt.so.5
-r--r--r--  1 root  wheel   119372 Oct  5 16:41 /lib/libm.so.5
-r--r--r--  1 root  wheel28424 Oct  5 16:42 /usr/lib/libpam.so.5
-r--r--r--  1 root  wheel40636 Oct  4 19:59 /usr/local/lib/libexecinfo.so.1
-r--r--r--  1 root  wheel  1050349 Oct  4 19:41 /usr/local/lib/libiconv.so.3
-r--r--r--  1 root  wheel39876 Oct  4 19:52 /usr/local/lib/libintl.so.8
-rwxr-xr-x  1 root  wheel39623 Oct  4 20:00 /usr/local/lib/libpopt.so.0*
r...@nudel samba33> ls -l /usr/local/sbin/smbd
-rwxr-xr-x  1 root  wheel  6698391 Oct  4 20:30 /usr/local/sbin/smbd*
r...@nudel samba33> file /usr/local/sbin/smbd
/usr/local/sbin/smbd: ELF 32-bit LSB shared object, Intel 80386, version 1 
(FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.0 (800107), not 
stripped
r...@nudel samba33> 

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

RE: Installing Cacti from Ports

2009-10-07 Thread mailinglist 
As part of the "freebsd-update" process I did run a few portupgrade commands.  
But I thought portupgrade only did whatever it does to installed ports.  Or are 
you saying it upgraded the xcb port which allowed Cacti to build to completion?

Also, off topic I know, but what is the proper way to reply to this?  Reply?  
Reply to all?  Or reply just to the mailing list?

From: Adam Vande More [amvandem...@gmail.com]
Sent: Wednesday, October 07, 2009 2:03 PM
To: mailinglist
Cc: freebsd-stable@freebsd.org
Subject: Re: Installing Cacti from Ports

On Wed, Oct 7, 2009 at 12:31 PM, mailinglist 
mailto:mailingl...@ucwv.edu>> wrote:
I hada VM running an older installation of FreeBSD 7.2.  I recently got back to 
it and tried to install Cacti from the ports collection.  I cvsup'd in an 
up-to-date ports collection, and did the usual "make, make install" for Cacti.  
During the "make install" process a dependency failed to build.  I believe it 
was xcb-utils that failed to build because XCB was at version 1.2 and needed to 
be at 1.4.  I couldn't get the issue resolved no matter what I tried.  I ended 
up giving up.later on I went through the "freebsd-update" process and 
upgraded to a newer version of 7.2.  After that Cacti and all dependencies 
built and installed successfully.  Was XCB upgraded when I did the 
freebsd-update process?  Or what?  I'm just trying to find out what 
happened.  Thanks! ___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to 
"freebsd-stable-unsubscr...@freebsd.org"

You might want to try a tool like portmaster or portupgrade to manage these 
dependency and package backup process.

--
Adam Vande More
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Installing Cacti from Ports

2009-10-07 Thread Adam Vande More 
On Wed, Oct 7, 2009 at 12:31 PM, mailinglist  wrote:

> I hada VM running an older installation of FreeBSD 7.2.  I recently got
> back to it and tried to install Cacti from the ports collection.  I cvsup'd
> in an up-to-date ports collection, and did the usual "make, make install"
> for Cacti.  During the "make install" process a dependency failed to build.
>  I believe it was xcb-utils that failed to build because XCB was at version
> 1.2 and needed to be at 1.4.  I couldn't get the issue resolved no matter
> what I tried.  I ended up giving up.later on I went through the
> "freebsd-update" process and upgraded to a newer version of 7.2.  After that
> Cacti and all dependencies built and installed successfully.  Was XCB
> upgraded when I did the freebsd-update process?  Or what?  I'm just trying
> to find out what happened.  Thanks!
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>

You might want to try a tool like portmaster or portupgrade to manage these
dependency and package backup process.

-- 
Adam Vande More
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Installing Cacti from Ports

2009-10-07 Thread Adam Vande More 
On Wed, Oct 7, 2009 at 1:21 PM, mailinglist  wrote:

> As part of the "freebsd-update" process I did run a few portupgrade
> commands.  But I thought portupgrade only did whatever it does to installed
> ports.  Or are you saying it upgraded the xcb port which allowed Cacti to
> build to completion?
>
> Also, off topic I know, but what is the proper way to reply to this?
>  Reply?  Reply to all?  Or reply just to the mailing list?
> 
>
>
freebsd-update and portupgrade are different.  freebsd-update updates core
compoments, portupgrade deals with apps installed via the ports tree.  xcb
is part of ports.

I usually do reply to all although a few don't like it but it's generally
more convenient.  Also please do not top post.

http://catb.org/jargon/html/T/top-post.html
-- 
Adam Vande More
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: samba - SIGABRT

2009-10-07 Thread jhell 


On Wed, 7 Oct 2009 20:09 +0200, lehmann@ wrote:

Hi,

I wonder what may have caused this and how should I debug it to find the
source? I Installed samba 3.3.7 on a clean 8.0-RC1 and I upgraded then my
system to the latest RELENG_8.
Since I've not the time searching much longer for the error I'll just go
to upgrade to 3.3.8 (recompile it...) tomorrow but I'm curious what it
may have caused and how I would have been able to find the cause


r...@nudel samba33> /usr/local/sbin/smbd
Abort
Exit 134


r...@nudel samba33> gdb
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
(gdb) exec /usr/local/sbin/smbd
(gdb) run
Starting program: /usr/local/sbin/smbd

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
You can't do that without a process to debug.
(gdb) q
r...@nudel samba33> ktrace /usr/local/sbin/smbd
Abort
Exit 134
r...@nudel samba33> kdump
 2605 ktrace   RET   ktrace 0
 2605 ktrace   CALL  execve(0xbfbfed83,0xbfbfec50,0xbfbfec58)
 2605 ktrace   NAMI  "/usr/local/sbin/smbd"
r...@nudel samba33> mount -t procfs /dev/null /proc
r...@nudel samba33> truss -fad /usr/local/sbin/smbd
truss: can not get etype: No such process
Exit 2
r...@nudel samba33> dmesg | tail -1
fxp0: Microcode loaded, int_delay: 1000 usec  bundle_max: 6
r...@nudel samba33> ldd /usr/local/sbin/smbd
/usr/local/sbin/smbd:
   libcrypt.so.5 => /lib/libcrypt.so.5 (0x281aa000)
   libpam.so.5 => /usr/lib/libpam.so.5 (0x281c3000)
   libexecinfo.so.1 => /usr/local/lib/libexecinfo.so.1 (0x281cb000)
   libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x288d2000)
   libpopt.so.0 => /usr/local/lib/libpopt.so.0 (0x281d6000)
   libc.so.7 => /lib/libc.so.7 (0x28091000)
   libm.so.5 => /lib/libm.so.5 (0x281df000)
   libintl.so.8 => /usr/local/lib/libintl.so.8 (0x289d1000)
r...@nudel samba33> ls -l /lib/libcrypt.so.5 /usr/lib/libpam.so.5 
/usr/local/lib/libexecinfo.so.1 /usr/local/lib/libiconv.so.3 
/usr/local/lib/libpopt.so.0 /lib/libc.so.7 /lib/libm.so.5 
/usr/local/lib/libintl.so.8
-r--r--r--  1 root  wheel  1144500 Oct  5 16:40 /lib/libc.so.7
-r--r--r--  1 root  wheel32060 Oct  5 16:41 /lib/libcrypt.so.5
-r--r--r--  1 root  wheel   119372 Oct  5 16:41 /lib/libm.so.5
-r--r--r--  1 root  wheel28424 Oct  5 16:42 /usr/lib/libpam.so.5
-r--r--r--  1 root  wheel40636 Oct  4 19:59 /usr/local/lib/libexecinfo.so.1
-r--r--r--  1 root  wheel  1050349 Oct  4 19:41 /usr/local/lib/libiconv.so.3
-r--r--r--  1 root  wheel39876 Oct  4 19:52 /usr/local/lib/libintl.so.8
-rwxr-xr-x  1 root  wheel39623 Oct  4 20:00 /usr/local/lib/libpopt.so.0*
r...@nudel samba33> ls -l /usr/local/sbin/smbd
-rwxr-xr-x  1 root  wheel  6698391 Oct  4 20:30 /usr/local/sbin/smbd*
r...@nudel samba33> file /usr/local/sbin/smbd
/usr/local/sbin/smbd: ELF 32-bit LSB shared object, Intel 80386, version 1 
(FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.0 (800107), not 
stripped
r...@nudel samba33>



You need to compile with the following:

CONFIGURE_ARGS+= --disable-pie

This was caused by your setting of the following:

security.bsd.map_at_zero=0

You can reset that value to 1 and you should be alright to operate like 
normal otherwise you will have to compile samba over again with the above 
mentioned configure options.


Best regards.

--

 ;; dataix.net!jhell 2048R/89D8547E 2009-09-30
 ;; BSD since FreeBSD 4.2Linux since Slackware 2.1
 ;; 85EF E26B 07BB 3777 76BE  B12A 9057 8789 89D8 547E

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: samba - SIGABRT

2009-10-07 Thread Bernhard Schmidt 
On Wednesday 07 October 2009 20:09:59 Oliver Lehmann wrote:
> Hi,
> 
> I wonder what may have caused this and how should I debug it to find the
> source? I Installed samba 3.3.7 on a clean 8.0-RC1 and I upgraded then my
> system to the latest RELENG_8.
> Since I've not the time searching much longer for the error I'll just go
> to upgrade to 3.3.8 (recompile it...) tomorrow but I'm curious what it
> may have caused and how I would have been able to find the cause


Is by any chance security.bsd.map_at_zero set to 0?  If it is 
http://lists.freebsd.org/pipermail/freebsd-stable/2009-October/052235.html has 
a solution.


> 
> 
> r...@nudel samba33> /usr/local/sbin/smbd
> Abort
> Exit 134
> 
> 
> r...@nudel samba33> gdb
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
>  are welcome to change it and/or distribute copies of it under certain
>  conditions. Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-marcel-freebsd".
> (gdb) exec /usr/local/sbin/smbd
> (gdb) run
> Starting program: /usr/local/sbin/smbd
> 
> Program terminated with signal SIGABRT, Aborted.
> The program no longer exists.
> You can't do that without a process to debug.
> (gdb) q
> r...@nudel samba33> ktrace /usr/local/sbin/smbd
> Abort
> Exit 134
> r...@nudel samba33> kdump
>   2605 ktrace   RET   ktrace 0
>   2605 ktrace   CALL  execve(0xbfbfed83,0xbfbfec50,0xbfbfec58)
>   2605 ktrace   NAMI  "/usr/local/sbin/smbd"
> r...@nudel samba33> mount -t procfs /dev/null /proc
> r...@nudel samba33> truss -fad /usr/local/sbin/smbd
> truss: can not get etype: No such process
> Exit 2
> r...@nudel samba33> dmesg | tail -1
> fxp0: Microcode loaded, int_delay: 1000 usec  bundle_max: 6
> r...@nudel samba33> ldd /usr/local/sbin/smbd
> /usr/local/sbin/smbd:
> libcrypt.so.5 => /lib/libcrypt.so.5 (0x281aa000)
> libpam.so.5 => /usr/lib/libpam.so.5 (0x281c3000)
> libexecinfo.so.1 => /usr/local/lib/libexecinfo.so.1 (0x281cb000)
> libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x288d2000)
> libpopt.so.0 => /usr/local/lib/libpopt.so.0 (0x281d6000)
> libc.so.7 => /lib/libc.so.7 (0x28091000)
> libm.so.5 => /lib/libm.so.5 (0x281df000)
> libintl.so.8 => /usr/local/lib/libintl.so.8 (0x289d1000)
> r...@nudel samba33> ls -l /lib/libcrypt.so.5 /usr/lib/libpam.so.5
>  /usr/local/lib/libexecinfo.so.1 /usr/local/lib/libiconv.so.3
>  /usr/local/lib/libpopt.so.0 /lib/libc.so.7 /lib/libm.so.5
>  /usr/local/lib/libintl.so.8 -r--r--r--  1 root  wheel  1144500 Oct  5
>  16:40 /lib/libc.so.7
> -r--r--r--  1 root  wheel32060 Oct  5 16:41 /lib/libcrypt.so.5
> -r--r--r--  1 root  wheel   119372 Oct  5 16:41 /lib/libm.so.5
> -r--r--r--  1 root  wheel28424 Oct  5 16:42 /usr/lib/libpam.so.5
> -r--r--r--  1 root  wheel40636 Oct  4 19:59
>  /usr/local/lib/libexecinfo.so.1 -r--r--r--  1 root  wheel  1050349 Oct  4
>  19:41 /usr/local/lib/libiconv.so.3 -r--r--r--  1 root  wheel39876 Oct 
>  4 19:52 /usr/local/lib/libintl.so.8 -rwxr-xr-x  1 root  wheel39623 Oct
>   4 20:00 /usr/local/lib/libpopt.so.0* r...@nudel samba33> ls -l
>  /usr/local/sbin/smbd
> -rwxr-xr-x  1 root  wheel  6698391 Oct  4 20:30 /usr/local/sbin/smbd*
> r...@nudel samba33> file /usr/local/sbin/smbd
> /usr/local/sbin/smbd: ELF 32-bit LSB shared object, Intel 80386, version 1
>  (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.0
>  (800107), not stripped r...@nudel samba33>
> 

-- 
Bernhard
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8.0-RC1: kernel page fault in NLM master thread (VIMAGE or ZFS related?)

2009-10-07 Thread Jamie Gritton 

Rick Macklem wrote:

On Sun, 27 Sep 2009, Robert Watson wrote:

On Fri, 25 Sep 2009, Jamie Gritton wrote:

It seems to be NFS related.  I think the null pointer in question is 
from the export's anonymous credential.  Try the patch below and see 
if it helps (which I guess means run it overnight and see if it 
crashes again).  I've also patched a similar missing cred prison in 
GSS_SVC, since I'm not versed enough in NFS/RPC stuff to know if it 
might be the problem.


This is one of the reasons I really dislike "magic" credentials and 
special handling of NULL credentials -- they always get into code the 
author doesn't expect, and either there are bad pointer dereferences, 
or incorrect security decisions.  It's almost always the case that a 
correct credential should have been cached or generated at some 
earlier point to represent the security context...



I don't really understand prisons/jails, but would creating these
credentials via:
crdup(td->td_ucred); // duplicating the daemon thread's cred
- and then replacing the 
make sense as an alternative to starting with crget()?
(ie. All the other stuff except  would be "inherited" from the
credential for the daemon thread.)


That sounds right to me for cases when the cred is based on passed
UID/GIDs. Perhaps you'd want to use the UID-changing helper functions on
kern_prot.c, or perhaps a new helper or helpers just for the circumstance.

- Jamie
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[SOLVED] Re: libthr and daemon()

2009-10-07 Thread Matthew Fleming 

> 2) why would fork resolve to the one in libc (presumably, I'm not sure
how
> to prove this) instead of the one in libthr?

Well, I'm not sure how the application plus libraries linked, but there
was no explicit -lthr or -lpthread in the Makefile.  So the resulting
binary used the fork() in libc.  When I added -lthr the app grew by
about 15 bytes, and correctly used the fork() weak-referenced to the
explicit _fork() in libthr.

Weird.

Thanks,
matthew
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

NDIS broken?

2009-10-07 Thread Jeff Dowsley 

Folks

Just upgraded from 7.2 to 8.0RC1

Under 7.2, I was using an ndis wrapper to provide a Windows network  
driver for an old Linksys PCMIA card (non-ath). Worked beautifully as  
per the Handbook under 7.2.


Sadly, under 8.0RC1, the process to generate the wrapper appears to  
work OK, but when I attempt to set any of the card's parameters,  
ifconfig returns I/O errors.


For example:

ifconfig ndis0 up   (back to prompt without errors, but then...

ifconfig ndis0 inet 192.168.1.105 netmask 255.255.255.0

ifconfig: ioctl (SIOCAIFADDR): Invalid argument

or

ifconfig ndis0 ssid chcs

ifconfig: SIOCS80211: Invalid argument



dmesg reports that ndis0 is available as a Wireless-G Notebook  
Adapter after the ndis drivers are loaded.



Any advice?

JeffD


_
M 0427565791

jeff.dows...@mac.com



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: NDIS broken?

2009-10-07 Thread Glen Barber 
Hi

On Wed, Oct 7, 2009 at 7:51 PM, Jeff Dowsley  wrote:
> Folks
>
> Just upgraded from 7.2 to 8.0RC1
>
> Under 7.2, I was using an ndis wrapper to provide a Windows network driver
> for an old Linksys PCMIA card (non-ath). Worked beautifully as per the
> Handbook under 7.2.
>
> Sadly, under 8.0RC1, the process to generate the wrapper appears to work OK,
> but when I attempt to set any of the card's parameters, ifconfig returns I/O
> errors.
>
> For example:
>
> ifconfig ndis0 up               (back to prompt without errors, but then...
>
> ifconfig ndis0 inet 192.168.1.105 netmask 255.255.255.0
>
> ifconfig: ioctl (SIOCAIFADDR): Invalid argument
>
> or
>
> ifconfig ndis0 ssid chcs
>
> ifconfig: SIOCS80211: Invalid argument
>
>

Have a look at the 20080420 entry in /usr/src/UPDATING for 8.X.  You
have to change ndis to wlan with an additional change in rc.conf.

HTH.

-- 
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

r197748 - base/stable/7/bin/sh/ 7.2-STABLE i386

2009-10-07 Thread jhell 


 
r197748 | jilles | 2009-10-04 13:16:11 -0400 (Sun, 04 Oct 2009) | 7 lines


MFC r197371: Mention that NUL characters are not allowed in sh(1) input.

I do not consider this a bug because POSIX permits it and argument strings 
and environment variables cannot contain '\0' anyway.


PR: bin/25542



Recently I have been noticing strange happenings of what I believe to be 
coming from the latest revision of /bin/sh. Prior to this revision it had 
not happened to the following examples. I am taking this as it could just 
be a following behavior in sudo due to fixing the first behavior in sh(1) 
but I am not sure and looking for feedback.


How to repeat: ( Let me know if this is only me. )
# sudo rm -rf /usr/ports/*/*/work

After issuing the above command the process waits for the list of (work) 
directories to be collected and ends by bombing out with pam timeout 
error. This could probably be easier seen with higher IO load but it has 
struck me kind of odd since I have not seen it at all till now. Also once 
it gets started you can not ^C the process until it has run the full 
directory tree.


Behavior before, you could issue the command and it would ask you for your 
password before it would issue any IO to the disk. Is the new behavior 
called for adjusting your command to sh -c "rm -rf /usr/blah/bloo/bla*" ?


Thanks

--

 ;; dataix.net!jhell 2048R/89D8547E 2009-09-30
 ;; BSD since FreeBSD 4.2Linux since Slackware 2.1
 ;; 85EF E26B 07BB 3777 76BE  B12A 9057 8789 89D8 547E

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: r197748 - base/stable/7/bin/sh/ 7.2-STABLE i386

2009-10-07 Thread Barney Wolff 
I believe you are wrong about prior behavior.  sudo is from a port and
is in /usr/local/bin.  Any shell is going to expand the list of args
*before* giving control to the executable.  So the system will churn
for a while before sudo gets to ask for the password.

On Thu, Oct 08, 2009 at 12:59:36AM -0400, jhell wrote:
> 
>  
> r197748 | jilles | 2009-10-04 13:16:11 -0400 (Sun, 04 Oct 2009) | 7 lines
> 
> MFC r197371: Mention that NUL characters are not allowed in sh(1) input.
> 
> I do not consider this a bug because POSIX permits it and argument strings 
> and environment variables cannot contain '\0' anyway.
> 
> PR: bin/25542
> 
> 
> 
> Recently I have been noticing strange happenings of what I believe to be 
> coming from the latest revision of /bin/sh. Prior to this revision it had 
> not happened to the following examples. I am taking this as it could just 
> be a following behavior in sudo due to fixing the first behavior in sh(1) 
> but I am not sure and looking for feedback.
> 
> How to repeat: ( Let me know if this is only me. )
> # sudo rm -rf /usr/ports/*/*/work
> 
> After issuing the above command the process waits for the list of (work) 
> directories to be collected and ends by bombing out with pam timeout 
> error. This could probably be easier seen with higher IO load but it has 
> struck me kind of odd since I have not seen it at all till now. Also once 
> it gets started you can not ^C the process until it has run the full 
> directory tree.
> 
> Behavior before, you could issue the command and it would ask you for your 
> password before it would issue any IO to the disk. Is the new behavior 
> called for adjusting your command to sh -c "rm -rf /usr/blah/bloo/bla*" ?

-- 
Barney Wolff I never met a computer I didn't like.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: samba - SIGABRT

2009-10-07 Thread Oliver Lehmann 
jhell writes: 

Hi, 



This was caused by your setting of the following: 

security.bsd.map_at_zero=0 

You can reset that value to 1 and you should be alright to operate like 
normal otherwise you will have to compile samba over again with the above 
mentioned configure options.


Yeah this caused the problem. I wonder how I could have
find this by myself (google is not counting ;)) I mean,
the Abort message is not very verbose what the problem
is here.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"