NetBSD

Bloated echo command

做~自己de王妃 提交于 2019-12-18 11:57:25
问题 Look at the following implementations of the "echo" command: http://bxr.su/o/bin/echo/echo.c (OpenBSD) http://bxr.su/d/bin/echo/echo.c (DragonFly) http://bxr.su/n/bin/echo/echo.c (NetBSD) http://bxr.su/f/bin/echo/echo.c (FreeBSD) http://git.savannah.gnu.org/cgit/coreutils.git/tree/src/echo.c (GNU) As you go down the list, I'm sure you'll notice the increasing bloat in each implementation. What is the point of a 272 line echo program? 回答1: In their article 'Program Design in the UNIX

Error while setting up netbsd crosscompiler

大憨熊 提交于 2019-12-11 14:44:49
问题 I am in the process of setting up a cross compiler for netbsd to sbmips with a mips64el processor. so I got the source and used ./build.sh -a mips64el -m sbmips and I got my toolchain with no errors. I continued to configure the kernel with: cd /usr/src/sys/arch/sbmips/conf /usr/src/tooldir.NetBSD-5.2.2-amd64/bin/nbconfig GENERIC this works, after this I go: cd ../compile/GENERIC /usr/src/tooldir.NetBSD-5.2.2-amd64/bin/nbmake-sbmips which fails with error code 1, Here is a link with 2 screens

Which processor would execute hardware interrupt in a muticore system

帅比萌擦擦* 提交于 2019-12-08 19:38:31
In general hardware interrupts need to be processed immediately, at least so as to acknowledge it and do some first level of processing. As I understand this is not scheduled activity. Please correct me. So the question is how to choose a processor that would actually execute this hardware interrupt handler? One can answer this for Linux and/or BSD systems In general, this depends on the functionality offered by multi-core processor and OS. While using multi-core processors, you might need to configure the affinity of the interrupt as per your requirement. In the case of linux , the /proc file

Unix screen utility error: Cannot find termcap entry for 'xterm-256color'

不打扰是莪最后的温柔 提交于 2019-12-03 11:44:52
问题 I work on a NetBSD system through an ssh connection from my Mac and I want to use the screen utility so that I can start processes and come back to them after my terminal connection has been interrupted. When I type screen I get the error message: Cannot find termcap entry for 'xterm-256color' After looking through forum posts, I thought it had something to do with termcap on the remote machine, but that appears not to be the case; I can initiate screen with no errors from an ssh session from

Unix screen utility error: Cannot find termcap entry for 'xterm-256color'

泄露秘密 提交于 2019-12-03 02:05:41
I work on a NetBSD system through an ssh connection from my Mac and I want to use the screen utility so that I can start processes and come back to them after my terminal connection has been interrupted. When I type screen I get the error message: Cannot find termcap entry for 'xterm-256color' After looking through forum posts, I thought it had something to do with termcap on the remote machine, but that appears not to be the case; I can initiate screen with no errors from an ssh session from another computer, one to which I don't generally have access. This suggests that I need to configure

httpd 443端口为什么只监听在tcp6上

一曲冷凌霜 提交于 2019-11-28 18:45:18
系统redhat7 ,httpd已经启动 [root@rhcsa conf.d]# netstat -tnpl | grep 443 tcp6 0 0 :::443 :::* LISTEN 1229/httpd 为什么如上命令只显示tcp6,而没有tcp ? --------------------------------------------------- 监听了tcp6后,tcp也可以用的。 虽然这个只显示了IPv6的端口监听,但并不代表只接受IPv6的连接,实际上,apache会以mapped address (::FFFF:a.b.c.d) 方式来接受IPv4的连接。除了少部分平台上,例如FreeBSD,NetBSD,OpenBSD之外, Apache在编译时,默认启用了 --enable-v4-mapped 选项。所以,Apache会同时接受IPv6和IPv4的连接请求。 除非是 IPV6_V6ONLY 模式开启,才需要两个不同的socket来分别监听IPv6和IPv4.IPV6_V6ONLY模式可以通过 sysctl net.ipv6.bindv6only 来控制,默认是关闭的。如果你实在愿意在netstat中只看到IPv4端口的监听,那么,你可以修apachezhttp.conf 中,将 Listen 80 修改为 Listen 0.0.0.0:80 具体信息