Re: Creating /dev/dk* nodes so as to be persistent

2013-10-21 Thread Thomas Mueller
I now notice a page on www.netbsd.org, NetBSD Documentation: Other FAQs and HOWTOs with a section on rebuilding /dev The /dev directory contains the necessary device files for accessing hardware and pseudo devices. If it becomes damaged, much strangeness can ensue. To rebuild the /dev

Re: Creating /dev/dk* nodes so as to be persistent

2013-10-21 Thread Michael van Elst
mueller6...@bellsouth.net (Thomas Mueller) writes: I wonder if rebuilding/updating the NetBSD system from source would fix the /dev. A rebuild would do nothing and I doubt that an update helps (but it would be a good feature). A reinstall (using sysinst) does help. I notice the instructions

Re: Creating /dev/dk* nodes so as to be persistent

2013-10-21 Thread Thomas Mueller
mueller6...@bellsouth.net (Thomas Mueller) writes: I wonder if rebuilding/updating the NetBSD system from source would fix the /dev. A rebuild would do nothing and I doubt that an update helps (but it would be a good feature). A reinstall (using sysinst) does help. After building the

*Message about your email account

2013-10-21 Thread Linda Nef
*Message about your email account Dear Staff Your email account has exceeded the limit of 30 GB, which is was set by your email webmaster, you are currently at 30.9GB and it is generating a continuous error script (code:505) very soon you will not be able to create new e-mail to send or receive

Two issues during upgrade from 6.99.23 to 6.99.24

2013-10-21 Thread Paul Goyette
I upgraded my last machine this morning, from 6.99.23 (July time-frame) to 6.99.24 (October). I've encountered two separate issues on this machine, which did not occur on my other systems. 1. In-treee Xorg won't start. The /var/log/Xorg.0.log looks like it starts quite normal, but as soon

Re: Two issues during upgrade from 6.99.23 to 6.99.24

2013-10-21 Thread Paul Goyette
On Mon, 21 Oct 2013, Nick Hudson wrote: crash(8) will probably do a better job of getting a full backtrace. Yes, it does do a much better job. Here's the backtrace: crash bt _KERNEL_OPT_DDB_COMMANDONENTER() at 0 _KERNEL_OPT_DDB_COMMANDONENTER() at 0 vpanic() at vpanic+0x13f printf_nolog()

evbarm build failing

2013-10-21 Thread Dennis Ferguson
An evbarm build from a -current updated about two hours ago is failing like this: # compile BEAGLEBOARD_INSTALL/nand_bbt.o [...] /usr/src/sys/dev/nand/nand_bbt.c: In function 'nand_bbt_block_mark': /usr/src/sys/dev/nand/nand_bbt.c:207:2: error: 'chip' undeclared (first use in this function)

daily CVS update output

2013-10-21 Thread NetBSD source update
Updating src tree: P src/dist/smbfs/lib/smb/rap.c P src/dist/smbfs/lib/smb/subr.c P src/external/bsd/llvm/Makefile.inc P src/external/cddl/osnet/dist/uts/common/fs/zfs/zfs_znode.c P src/lib/libc/arch/arm/gen/_setjmp.S P src/libexec/ld.elf_so/tls.c P src/sbin/modstat/main.c P