Date: Sun, 28 Jan 2007 21:58:28 +0300 From: "Andrew Pantyukhin" <infofarmer@FreeBSD.org> To: "Alexander Leidinger" <Alexander@leidinger.net> Cc: FreeBSD Ports <ports@freebsd.org> Subject: Re: Non-daemon programs requiring kernel modules Message-ID: <cb5206420701281058r4232ad35xfddfc4f29c6ff8ca@mail.gmail.com> In-Reply-To: <20070128193804.5b2e09ba@Magellan.Leidinger.net> References: <cb5206420701280735o6c916639ufbbc941f0927f4c8@mail.gmail.com> <20070128193804.5b2e09ba@Magellan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/28/07, Alexander Leidinger <Alexander@leidinger.net> wrote: > Quoting "Andrew Pantyukhin" <infofarmer@FreeBSD.org> (Sun, 28 Jan 2007 18:35:30 +0300): > > > I'm porting a simple util requiring aio(4). My plan is > > to install a wrapper script which includes rc.subr(8) > > and uses its required_modules mechanism. > > > > If anyone has a better idea, please tell me. > > Just tell at port/package install time the requirement. Every linux > program needs the linux module or the corresponding kernel option. If > the code is not available at runtime, the user will get an error. Unix > is not for dumb people, so I don't think we need this low-level > hand-holding. That's one opinion. But Unix is also not about dumb developers. As a ports developer, my job is to make it easier for users to run third-party software and that's just what I'm trying to do to the extent of my skills and motivation...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420701281058r4232ad35xfddfc4f29c6ff8ca>