Date: Sat, 11 Dec 2004 15:16:41 -0800 From: "Loren M. Lang" <lorenl@alzatex.com> To: Jeff Lawlor <jeff.lawlor@med.va.gov> Cc: FreeBSD Mailing list <freebsd-questions@freebsd.org> Subject: Re: Linux kernel on FreeBSD Message-ID: <20041211231641.GE16539@alzatex.com> In-Reply-To: <1102690190.565.35.camel@ist-lawloj-fbsd53-r.vhaist.med.va.gov> References: <20041210082138.GF32126@alzatex.com> <d9175cad0412100548643cbbea@mail.gmail.com> <1102690190.565.35.camel@ist-lawloj-fbsd53-r.vhaist.med.va.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 10, 2004 at 08:49:50AM -0600, Jeff Lawlor wrote: > For programs that require linux kernel source code what about copying > the linux kernel source files from a linux box on to the FreeBSD > machine? Has anyone tried this? This make make it compile, but it does not mean it will work. For example, if the program requires the kernel headers to define the ioctls used for V4L2, it may now compile under freebsd, but the device file won't know what to do with that ioctl and fail, assuming the device file even exists. > > > On Fri, 2004-12-10 at 07:48, Eric Kjeldergaard wrote: > > > Also, I've found the > > > Netfilter firewall in Linux to be, IMHO, a little better designed than > > > ipfilter or ipfw in freebsd, and it definetely has more features than > > > those two freebsd firewalls. > > > > Which features? Is there something I'm missing with the firewalls > > available in FreeBSD? -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041211231641.GE16539>