📜 ⬆️ ⬇️

What is NetBSD?

Perhaps this question will be banal for someone. However, I have repeatedly come across people who respond to the mention of NetBSD with a stereotyped “firebox” response.

I want to highlight the basic concepts of this OS and my experience with it.

Why do we need another operating system?


The idea behind the NetBSD project is to create a modern, maximally cross-platform operating system. By modern I mean the support of various new technologies, for example, xen host. Unlike Linux, NetBSD portability is not limited to the kernel. The same distribution kit works on all declared platforms. I think this is a major achievement.

Undoubtedly, there are downsides. A small team of developers + priority portability impose a restriction on compatibility. For example, in NetBSD, there is no support for basic file systems (JFS, XFS, NTFS, EXT3) and LVM. There are full-fledged analogs - LFS and ccd. This is another aspect of the ideology of NetBSD - not to chase after everything. Not as important as, the main thing that worked.
')
Like the OS itself, pkgsrc, the NetBSD package system, is primarily focused on portability. That is why at some point DragonFlyBSD switched to pkgsrc. Currently, pkgsrc supports 14 operating systems. This is another example of an integrated approach "to do so that it works everywhere."

My acquaintance with NetBSD


For a long time on my home network 24/7 server with ssh and donkey was an old OS / 2 laptop. Everything worked fine. Gradually, in the donkey files became less, and torrents are becoming more popular. In OS / 2, torrents are very bad. There is only a native client on python and ctorrent. It is impossible to seriously rock, and even more so it is impossible to distribute with their help. Therefore, it became necessary to replace the server OS, where it would be possible to run rtorrent.

Putting Linux in the first place was not interesting. I decided to try FreeBSD. Just at that moment, the release of 7.0 was released. I happily set to download something, and in the morning I found out that FreeBSD had dropped “Panic String: kmem_malloc (4096): kmem_map too small: 26476544 total allocated”. On the Internet, it was recommended to increase the buffers, I increased them, but the result was always the same. In the LJ FreeBSD community, I was recommended to try NetBSD.

On the first day of work, SSH again stopped responding. However, the system remained alive. I changed the number of NMBCLUSTERS in accordance with the recommendations and no more problems arose. In my opinion, stability is one of the most important qualities of a server system. As for performance, I can not complain. I will not give any benchmarks - everything depends too much on hardware, software settings, etc.

Source: https://habr.com/ru/post/49675/


All Articles