Huub | 1 Mar 2007 12:57
Picon

Re: gmplayer fails to build

Update: despite a fresh cvs -dAP, it keeps ending with the same error. 
Odd thing is that gmplayer built fine on 3.1/amd64. Anyone else with 
this error?

Jeremy C. Reed | 1 Mar 2007 18:32

gethostbyaddr(3) fails when DNS PTR record has a wildcard

I saw this DNS entry:

 10.7.18.64.in-addr.arpa. 22018  IN      PTR     *.s8a1.psmtp.com.

Which resolves with dig and host and nslookup, for example:

 $ host 64.18.7.10
 10.7.18.64.in-addr.arpa domain name pointer *.s8a1.psmtp.com.

But gethostbyaddr(3) fails for that and h_errno is "3" which is:

#define NO_RECOVERY     3 /* Non recoverable errors, FORMERR, REFUSED, NOTIMP */

Or:

 NO_RECOVERY     Some unexpected server failure was encountered. This is
                 a non-recoverable error.

And hstrerror(h_errno) has "Unknown server error".

ktrace shows:

 19145      1 gethost  CALL  recvfrom(3,0x805b000,0x10000,0,0xbfbfdd70,0xbfbfde3c)
 19145      1 gethost  GIO   fd 3 read 71 bytes
       "\M^[\M-Y\M^A\M^ <at> \0\^A\0\^A\0\0\0\0\^B10\^A7\^B18\^B64\ain-addr\^Darpa\
        \0\0\f\0\^A\M- <at> \f\0\f\0\^A\0\0 <at> \M-:\0\^R\^A*\^Ds8a1\^Epsmtp\^Ccom\0"

This is NetBSD 3.99.24.

I am trying to look through /usr/src/lib/libc/net/gethnamaddr.c to see why 
(Continue reading)

Christos Zoulas | 1 Mar 2007 19:23

Re: gethostbyaddr(3) fails when DNS PTR record has a wildcard

In article <Pine.NEB.4.64.0703011109490.25888 <at> glacier.reedmedia.net>,
Jeremy C. Reed <reed <at> reedmedia.net> wrote:
>I saw this DNS entry:
>
> 10.7.18.64.in-addr.arpa. 22018  IN      PTR     *.s8a1.psmtp.com.
>
>Which resolves with dig and host and nslookup, for example:
>
> $ host 64.18.7.10
> 10.7.18.64.in-addr.arpa domain name pointer *.s8a1.psmtp.com.
>
>
>But gethostbyaddr(3) fails for that and h_errno is "3" which is:
>
>#define NO_RECOVERY     3 /* Non recoverable errors, FORMERR, REFUSED, NOTIMP */
>
>Or:
>
> NO_RECOVERY     Some unexpected server failure was encountered. This is
>                 a non-recoverable error.
> 
>And hstrerror(h_errno) has "Unknown server error".
>
>ktrace shows:
>
> 19145      1 gethost  CALL 
>recvfrom(3,0x805b000,0x10000,0,0xbfbfdd70,0xbfbfde3c)
> 19145      1 gethost  GIO   fd 3 read 71 bytes
>       "\M^[\M-Y\M^A\M^ <at> \0\^A\0\^A\0\0\0\0\^B10\^A7\^B18\^B64\ain-addr\^Darpa\
>        \0\0\f\0\^A\M- <at> \f\0\f\0\^A\0\0 <at> \M-:\0\^R\^A*\^Ds8a1\^Epsmtp\^Ccom\0"
(Continue reading)

Greg A. Woods | 2 Mar 2007 03:12
X-Face
Favicon

aac(4) vs. Dell PERC 3/Di _and_ HP NetRAID-4M in same host

I've got a Dell PowerEdge 2650 here with that I've added an HP
NetRAID-4M card to for additional external storage.

Has anyone here successfully used a similar configuration with NetBSD
(or FreeBSD or OpenBSD, or even GNU/Linux)?  Any kind of system with
both Dell PERC and HP NetRAID in the same box?

This one boots up with netbsd-4 saying, in part, the following:

aac0 at pci2 dev 8 function 1: Dell PERC 3/Di
aac0: interrupting at ioapic1 pin 14 (irq 11)
aac0: i960RX at 100MHz, 128MB mem (118MB cache), optional battery present
ld0 at aac0 unit 0: RAID 5
ld0: 135 GB, 17700 cyl, 255 head, 63 sec, 512 bytes/sect x 284365824 sectors

aac1 at pci4 dev 6 function 0: HP NetRAID-4M
aac1: interrupting at ioapic1 pin 0 (irq 7)
aac1: StrongARM SA110 at 233MHz, 144MB mem (128MB cache), required battery present
ld1 at aac1 unit 0: RAID 5
ld1: 95450 MB, 12168 cyl, 255 head, 63 sec, 512 bytes/sect x 195482496 sectors

ld0 works just fine.  I was able to install onto it from sysinst, and
I've done a full source build on it right to the binary sets without
trouble, albiet a bit slower than it could be, apparently.

However ld1 behaves very bizarrely.  I can write to it at what seems to
be full blast.  I can read from it too, but slower than it should be, I
think (a lot slower than it writes!), and all I ever get back are zero
value bytes.  There are no errors, not a peep from anything, just lots
of blocks of zeros, no matter what's been "written" previously.
(Continue reading)

Stephen Borrill | 6 Mar 2007 11:15
Picon
Favicon

Booting from NTFS?

Is there anyway to boot a kernel (with integral ramdisk, I'm not asking 
for root on ntfs!) from NTFS? i.e. drop a directory of files including a 
kernel into your drive C:\, edit boot.ini and then get the option of 
booting the kernel. Would this require basic ntfs support to be hammered 
into libsa?

--

-- 
Stephen

David Laight | 6 Mar 2007 19:27
Picon

Re: Booting from NTFS?

On Tue, Mar 06, 2007 at 10:15:33AM +0000, Stephen Borrill wrote:
> Is there anyway to boot a kernel (with integral ramdisk, I'm not asking 
> for root on ntfs!) from NTFS? i.e. drop a directory of files including a 
> kernel into your drive C:\, edit boot.ini and then get the option of 
> booting the kernel. Would this require basic ntfs support to be hammered 
> into libsa?

Almost certainly, and I'm not sure how easy it would be.

Maybe the windows boot manager is capable of copying very large files
to 0x7c00 - but I suspect the kernel is far too bit for that.

You can boot from FAT - including some USB sticks without having to
remake the FAT16 filesystem.

	David

--

-- 
David Laight: david <at> l8s.co.uk

Paul Newhouse | 7 Mar 2007 06:14

Help with core dump and gdb

I unzip'd some crash files and ran gdb:

   bigbox#  file *
   netbsd.6:      ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, not stripped
   netbsd.6.core: data
   bigbox# ls -l
   total 139040
   -rw-------  1 root  wheel    8459982 Mar  6 19:00 netbsd.6
   -rw-------  1 root  wheel  133825044 Mar  6 19:00 netbsd.6.core
   bigbox# ls -l /net*
   -rwxr-xr-x  1 root  wheel  8459982 Mar  6 09:41 /netbsd
   -rwxr-x---  1 root  wheel  8459982 Mar  6 09:37 /netbsd.030607.debug
   -rwxr-xr-x  1 root  wheel  8412345 Sep 10 01:35 /netbsd.first
   -rwxr-xr-x  1 root  wheel  8189387 Sep  7 22:54 /netbsd.installed.3.0.1
   -rwxr-x---  1 root  wheel  8531836 Mar  6 09:41 /netbsd.second
   bigbox# gdb -c netbsd.6.core netbsd.6
   GNU gdb 5.3nb1
   Copyright 2002 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--netbsdelf"...(no debugging symbols found)...
   "/var/crash/crash6/netbsd.6.core" is not a core dump: File format not recognized
   (gdb) bt
   No stack.
   (gdb) where
   No stack.
   (gdb) 

(Continue reading)

Lubomir Sedlacik | 7 Mar 2007 10:40

Re: Help with core dump and gdb

On Tue, Mar 06, 2007 at 09:14:53PM -0800, Paul Newhouse wrote:
> Where did I go wrong?

(gdb) help target
...
target kcore -- Use a kernel core dump file or live kernel as a target

regards,

--

-- 
-- Lubomir Sedlacik <salo <at> {NetBSD,Xtrmntr,silcnet}.org>   --
Nick Hudson | 7 Mar 2007 11:10

Re: Help with core dump and gdb

On Wednesday 07 March 2007 05:14, Paul Newhouse wrote:
> I unzip'd some crash files and ran gdb:
>
>    bigbox#  file *
>    netbsd.6:      ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> statically linked, not stripped netbsd.6.core: data
>    bigbox# ls -l
>    total 139040
>    -rw-------  1 root  wheel    8459982 Mar  6 19:00 netbsd.6
>    -rw-------  1 root  wheel  133825044 Mar  6 19:00 netbsd.6.core
>    bigbox# ls -l /net*
>    -rwxr-xr-x  1 root  wheel  8459982 Mar  6 09:41 /netbsd
>    -rwxr-x---  1 root  wheel  8459982 Mar  6 09:37 /netbsd.030607.debug
>    -rwxr-xr-x  1 root  wheel  8412345 Sep 10 01:35 /netbsd.first
>    -rwxr-xr-x  1 root  wheel  8189387 Sep  7 22:54 /netbsd.installed.3.0.1
>    -rwxr-x---  1 root  wheel  8531836 Mar  6 09:41 /netbsd.second
>    bigbox# gdb -c netbsd.6.core netbsd.6
>    GNU gdb 5.3nb1
>    Copyright 2002 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--netbsdelf"...(no debugging
> symbols found)... "/var/crash/crash6/netbsd.6.core" is not a core dump:
> File format not recognized (gdb) bt
>    No stack.
>    (gdb) where
>    No stack.
>    (gdb)
(Continue reading)

P S Senthil Kumar | 8 Mar 2007 12:17

OTG support in NetBSD source

Hi,

  I would like to know whether OTG support is enabled for the USB source
base in NetBSD.If so please give me the pointer to the same (as I
couldn't located any OTG specific Document/Code in the Netbsd code base)

Rgds
Senthil

Conexant E-mail Firewall (Conexant.Com) made the following
annotations---------------------------------------------------------------------**********************
Legal Disclaimer **************************** 

"This email may contain confidential and privileged material for the sole use of the intended recipient.
Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the
message in error, please advise the sender by reply email and delete the message. Thank you." 

********************************************************************** 

---------------------------------------------------------------------


Gmane