threebsdFreeBSD by default sets the TERM variable as cons25, and you have colors. In NetBSD and OpenBSD, the TERM settings are vt100 and vt220, respectively. Just ‘export TERM=wsvt25′ and make it permanent by adding a line to your .profile .
MY setup first: my good ole trusty Thinkpad T22, a 4.9-release install CD and the need for -current. I booted from the CD, chose HTTP as the install source and changed the location on the server from something like OpenBSD/4.9/i386 to OpenBSD/snapshots/i386. The installer will initially find only the kernel and the ramdisk: install them, ignore the errors, be patient and reboot from the HDD when the installer is done. From the boot prompt, type “boot bsd.rd”, choose Install and install from HTTP, again using OpenBSD/snapshots/i386. Note that this location may differ on certain mirrors. That’s it!
If you can’t use your mouse in (modular) Xorg on NetBSD-current, do, as root
/etc/rc.d/wsmoused onestop vi /etc/rc.conf #comment the wsmoused line if you have one
and start X again.
…and best wishes. Take care of each other.
If you get this error with a recently updated NetBSD current, just create a symlink from /usr/lib/libcrypto.so.7 to /usr/lib/libcrypto.so.4 . Possibly other packages are affected by this as well.
It seemed to me that the NetBSD’s documentation in the guide, although good, lacks the clarity of Open or FreeBSD’s documentation on the matter. So I wanted to share with you how I compile my system (-current, but this is mostly irrelevant). I will presume that you have already checked the sources, so now you can start.
# mkdir /usr/obj /* after the first time, remember to do a 'rm -rf /usr/obj/*' */ # cd /usr/src # ./build.sh tools (add -U if this is an upgrade and -x if you want X as well; this applies to every command involving build.sh - skip the -x in kernel-related issues) # ./build.sh kernel=MYCONFIG (after this, if you need modules built as well, see [1]) # mv /netbsd /netbsd.old # cp sys/arch/YOUR_ARCH/compile/obj/MYCONFIG/netbsd / # reboot # cd /usr/src # ./build.sh distribution # ./build.sh install=/ # etcupdate # cd /usr/tests # atf-run | atf-report [1] Build modules: # ./build.sh modules Install'em: # cd sys/modules # make install USETOOLS=no DESTDIR=/
That’s it, and it works for me. Hope it helps.
By default bwi and bwn drivers are commented in GENERIC. If uncommented, the resulting kernel panics and thus doesn’t boot.
If, like me, you made the mistake of purchasing a laptop with a Broadcom 431x wi-fi card, can you confirm this?
PS: F*** Broadcom.
I got this error while trying to compile mplayer on OpenBSD current. The solution is to use
make PKG_CREATE_NO_CHECKS=Yes install clean-depends
I installed NetBSD 5.1, upgraded to STABLE and started installing necessary software. Among this, the Alpine mail client. Everything works good, as one can expect from NetBSD, but Alpine segfaults when trying to open the huge mailbox (~156000 e-mails). I asked on netbsd-users@ for help, and as expected, help came shortly. It was a system limit, just as I suspected. Since NetBSD is focused on portability, its stack size is set to 2048, which was a little small for Alpine. Doing
$ ulimit -s 4096
solved my issue. Hope it helps you.
[EDIT] On OpenBSD-current the default stack size is 4096, but Alpine dies with an “out of memory”
exception. Increasing the stack size to 8192 as it is on my Debian system, on which alpine works
just fine, didn’t solve my problem. Will keep you posted.
[LATER EDIT] It’s only PEBKAC, folks. Don’t be lazy like me and create a configuration
from scratch and all will be fine without you having to raise the stack size more than 4096.
I was inspired from here: https://www.cs.virginia.edu/~csadmin/wiki/index.php/Setting_up_Pine_%28Alpine%29_for_IMAP_Gmail .
