Precedence: list
MIME-Version: 1.0
Date: Sat, 7 Jan 2012 10:34:59 +0100
Message-ID: <CAFivhPnM_wFvKvYf5OLuRxSXdVwZzCoTzG=vPrUcoZ7SPBA1tg@mail.gmail.com>
Subject: [alpine-devel] Steps for adding / packaging a kernel module
From: Florian Heigl <florian.heigl@gmail.com>
To: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

i've been going through the wiki articles but so far this has been a
quite inconclusive thing.

I've prepared a VM and installed alpine-sdk,  and also somehow set up
abuild, but I'm not even sure that was a step into the right
direction.

Ah, and just now I noticed the rebuild-alpine.sh and stuff in aports.

I want to try to build packages for flashcache and openvswitch at some
point, right now I just want to install them "somehow" and test,
that's why I end up needing to compile some kernel modules.

Started a nice mass build of 1500 packages now and have no idea if
that will really help me in the end :)

Maybe this will just do it, but please take notice that one start-goal
documentation for this would not hurt.

Greetings,
Florian

-- 
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---