Mailinglist Archive: opensuse-kernel (131 mails)

< Previous Next >
[opensuse-kernel] procedure to extract & build btrfs-unstable module & progs against opensuse Kernel:HEAD kernel sources?
  • From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
  • Date: Sun, 7 Feb 2010 10:06:03 -0800
  • Message-id: <c67eed301002071006x6a421e5du7a94eedb001f2a56@xxxxxxxxxxxxxx>
I'm running

uname -a
Linux TEST 2.6.33-rc6-12-xen #1 SMP 2010-02-05 18:11:23 +0100
x86_64 x86_64 x86_64 GNU/Linux

and have,

ls -al /usr/src | grep rc6
lrwxrwxrwx 1 root root 19 2010-02-07 09:53 linux -> linux-2.6.33-rc6-12
drwxr-xr-x 24 root root 4096 2010-02-06 07:04 linux-2.6.33-rc6-12/
drwxr-xr-x 3 root root 4096 2010-02-06 01:09 linux-2.6.33-rc6-12-obj/

I'd like to experiment with *this* kernel and latest/unstable btrfs.

Although the btrfs wiki
refers to a 'standalone' btrfs source tree, it's apparently ~ 1 year
out of date, and no longer maintained. Afaict, the latest btrfs
sources are only available in

git clone
git clone

that pull a complete kernel tree ...

Reading Git docs/howtos, I note: "With Git it is not possible to pull
only a single directory, because of the hash code nature of Git, you
must take all or nothing.", so I guess I'm stuck with pulling the
whole non-opensuse kernel tree, and either patching it with opensuse's
patches etc, or extracting all (?) the btrfs-unstable bits, and
swapping them into the opensuse kernel sources.

What would be the "right procedure" for extracting the btrfs &
btrfs-progs sources from the trees, and building the
module/progs against my in-place, fully-patched, opensuse kernel's
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups