understand.

* Tong Sun <bts@bts.grml.org> [20081005 20:03]:

> In config, we have a var KERNEL to specify kernel version which should be
> installed. 

> I meant, if 

> KERNEL=2.6.26-grml

> then besides installing kernel 2.6.26-grml, we'll install
> aufs-modules-2.6.26-grml as well, since it is small and mostly needed.

NACK, because:

a) aufs is irrelevant on server systems and grml-debootstrap is
meant to be a generic tool

b) several kernel versions might not bring an aufs modules package

Additional stuff like aufs definitiely should be handled by the user
and his own package list(s).

regards,
-mika-

In config, we have a var KERNEL to specify kernel version which should be
installed. 

I meant, if 

KERNEL=2.6.26-grml

then besides installing kernel 2.6.26-grml, we'll install
aufs-modules-2.6.26-grml as well, since it is small and mostly needed.

Sorry, I've no idea what you are talking about

% pwd
/grml/git/grml-debootstrap
% grep -r aufs .
%

There's not a single reference regarding aufs in the grml-debootstrap package.
So what do you mean?

regards,
-mika-

Hi, 

what do you think to bundle aufs-modules with kernel in grml-debootstrap? 

with so many aufs-modules available,

aufs-modules-2.6.20-grml-small
aufs-modules-2.6.22-grml
aufs-modules-2.6.23-grml
aufs-modules-2.6.26-grml
aufs-modules-2.6-486
aufs-modules-2.6-686
aufs-modules-2.6-686-bigmem
...

It make sense not to hard code aufs-modules and the version/arch info in the
"packages" file. Further the package is only 120980b in size, so it won't hurt
to include it in even for people who don't need it. Otherwise, a separated
variable need to be defined. 

what do you think? 

tong