[systemd-devel] Loading Kernel Modules

[Pawel Pastuszak]

Hi Kay,

So in this case how would you support upgrading the kernel module?
The main reason to do the module unload is so you can upgrade the module to
an new version.

Pawel

On Mon, Mar 19, 2012 at 9:56 AM, Kay Sievers <kay at vrfy.org> wrote:

> On Mon, Mar 19, 2012 at 14:42, Pawel Pastuszak <pawelpastuszak at gmail.com>
> wrote:
> > I am new to to systemd, i trying to learn how to the configuration files
> > using system vs the old method of sysv with init.d script so i have
> couple
> > scripts that i uses currently for loading couple custom drivers and i
> like
> > to cover them into an systemd so that i can load them and unload them
> using
> > the systemctl stop/start commands sets.
> >
> > Can anybody show me a good example of how to do this?
>
> We never support module unloading. It's almost always wrong to do that.
>
> Module unloading is a 'development tool', or to *locally* work around
> broken drivers, we will not support that with any tools and advertise
> that, or make it easy to do so. It steals the focus from the kernel
> bugs, which is just bad. Module unloading is usually only fixing the
> symptoms, not the cause, which is an approach systemd refuses to
> support.
>
> If you need to unload modules, file bugs against the kernel please, so
> that this gets fixed. Modules need to be able to stay loaded all the
> time; just the same way they could be compiled-in in the first place.
>
> Systemd can force-load modules with 'man modules-load.d'.
>
> Thanks,
> Kay
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20120319/266f8664/attachment-0001.htm>