Date: Wed, 17 Jun 2020 21:04:32 +0300 From: "Yuri Pankov" <yuripv@yuripv.dev> To: freebsd-questions@freebsd.org Subject: Re: Why does FreeBSD not use the Linux kernel? Message-ID: <6fc1cf5e-040d-4a80-a0ec-22ee25edf4bd@www.fastmail.com> In-Reply-To: <CAHu1Y70aEvfupOGJysK_kqdeOBJ13JPLkKxKOVCHPfcWtGfVmQ@mail.gmail.com> References: <3a48ab1ab198c330400be3e942f921f2cd3c3e11.camel@tom.com> <20200617141857.b208232a.freebsd@edvax.de> <CAHu1Y70aEvfupOGJysK_kqdeOBJ13JPLkKxKOVCHPfcWtGfVmQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 17, 2020, at 8:55 PM, Michael Sierchio wrote: > On Wed, Jun 17, 2020 at 5:19 AM Polytropon <freebsd@edvax.de> wrote: > > > On Wed, 17 Jun 2020 11:33:25 +0800, kindu smith wrote: > > > Why does FreeBSD not use the Linux kernel? The structure of FreeBSD is > > > very good, such as the startup and directory structure, and the user > > > island program. The only shortcoming is poor hardware support. This is > > > mainly due to the lack of drivers provided by the kernel. > > > > While there are certain basic drivers in the kernel, the > > majority of drivers is provided by loadable kernel modules, > > either developed by the FreeBSD team itself, or available > > from the ports collection. They use interfaces provided by > > the kernel. > > > > > The chief difference from my perspective is that it is possible in FreeBSD > to create a monolithic kernel and prohibit the loading of kernel modules, > foiling one step in the chain of a rootkit. It's especially convenient for > embedded devices, security appliances, etc. > > Some features cannot work as loadable kernel modules, such as kernel NAT in > ipfw supplied by LIBALIAS. FWIW: $ ls /boot/kernel/ipfw_nat* /boot/kernel/ipfw_nat.ko /boot/kernel/ipfw_nat64.ko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6fc1cf5e-040d-4a80-a0ec-22ee25edf4bd>