On Mon, Sep 26, 2011 at 11:32 AM, Lennart Poettering
wrote:
> My question to you: why are these modules built at boot time at all? Why
> not at install time? Seems like the more appropriate time to me, given
> that the set of kernel packages does not change during boot, but only at
> install time.
On Mon, Sep 26, 2011 at 12:34 PM, Doug Ledford wrote:
> - Original Message -
>> Well, you can move your service into the early boot part if
>> necessary. However, there's a fundamental problem here: iiuc you
>> compile
>> driver modules at boot and want them recognized by the system during
Am 26.09.2011 21:54, schrieb Kevin Kofler:
> Reindl Harald wrote:
>> normally the kmod-packages are updated the same time
>> as the kernel in stable repos, but you can not guarantee
>> this for external repos everytime, especially that the
>> mirror you catched is recent enough
>
> But akmods ar
On Mon, 2011-09-26 at 21:54 +0200, Kevin Kofler wrote:
> The right solution is for the user to just uncheck the kernel from the
> list
> of packages to update in the PackageKit GUI of choice (be it gnome-
> packagekit, KPackageKit or Apper) if the kmod doesn't show up along
> with it.
> It's not
On Mon, Sep 26, 2011 at 3:07 PM, Pierre-Yves Chibon wrote:
> On Mon, 2011-09-26 at 15:00 -0500, Richard Shaw wrote:
>> > The right solution is for the user to just uncheck the kernel from
>> the list
>> > of packages to update in the PackageKit GUI of choice (be it gnome-
>> > packagekit, KPackage
On Mon, 2011-09-26 at 15:00 -0500, Richard Shaw wrote:
> > The right solution is for the user to just uncheck the kernel from
> the list
> > of packages to update in the PackageKit GUI of choice (be it gnome-
> > packagekit, KPackageKit or Apper) if the kmod doesn't show up along
> with it.
> > It'
On Mon, Sep 26, 2011 at 2:54 PM, Kevin Kofler wrote:
> But akmods are a very hackish solution to that problem. Building modules on
> the end user system sucks on a binary distribution. It drags in the whole
> GCC toolchain, kernel-devel and the source code for the modules and the
> whole system is
Reindl Harald wrote:
> because akmods is used to build kernel-modules after the kernel
> was updated and the komd-package not - this was before vmxnet3
> as example hardly needed for vmware because without network
> yum makes no fun
>
> another example are the nvidia-drivers - for normal users
> i
Am 26.09.2011 18:32, schrieb Lennart Poettering:
> My question to you: why are these modules built at boot time at all? Why
> not at install time? Seems like the more appropriate time to me, given
> that the set of kernel packages does not change during boot, but only at
> install time.
because
- Original Message -
> Well, you can move your service into the early boot part if
> necessary. However, there's a fundamental problem here: iiuc you
> compile
> driver modules at boot and want them recognized by the system during
> the
> same boot run. That's hardly possible though. To com
On Sat, 24.09.11 08:48, Richard Shaw (hobbes1...@gmail.com) wrote:
> I just took over the akmods package at RPM Fusion and one of the many
> BZ requests is to convert it to systemd.
>
> The current suggestion is:
> [Unit]
> Description=Builds and install new kmods from akmod packages
> After=sysl
Richard Shaw wrote:
> On Sun, Sep 25, 2011 at 7:01 AM, Michal Schmidt
> wrote:
>
>> Or, instead of building all the modules from akmods.service, you
>> can build them using 'akmods --akmod ...' from their own akmod-*.service
>> where the ordering will be defined as needed.
>
> Here they provide
On Sun, Sep 25, 2011 at 7:01 AM, Michal Schmidt wrote:
> You can have every akmod-* package ship
> a /lib/systemd/system/akmod-*.target file to specify the ordering, e.g.
> akmod-foo-video-driver.target:
>
> [Unit]
> Description=akmod for foo
> After=akmods.service
> Before=prefdm.service
>
>
On Sat, 24 Sep 2011 08:48:16 -0500 Richard Shaw wrote:
> I just took over the akmods package at RPM Fusion and one of the many
> BZ requests is to convert it to systemd.
>
> The current suggestion is:
> [Unit]
> Description=Builds and install new kmods from akmod packages
> After=syslog.target
> B
I just took over the akmods package at RPM Fusion and one of the many
BZ requests is to convert it to systemd.
The current suggestion is:
[Unit]
Description=Builds and install new kmods from akmod packages
After=syslog.target
Before=prefdm.service
[Service]
Type=oneshot
ExecStart=-/usr/sbin/akmod
15 matches
Mail list logo