Re: cramfs problems, also file(1)

[skaya@enix.org]

>       I am a firm believer in the tenet that software should not
>  second guess humans.  The human asked for  initrd specifically, and I
>  am not going to ask you sure? really? really sure? say pretty
>  please. 
> 
>       Creating a kernel does require a certain modicum of care and
>  knowledge, after all.

of course. but in this specific case, the human is asking "build
me a kernel package --with initrd support", and this support requires
a specific patch. if this patch is not applied, the package will be
unusable. and this is not documented anywhere (well, since last week,
it must be in mailing list archives, but it's not in package docs).
testing whether or not the patch is applied would save a lot of time 
for people with funky kernels (i.e. not using debian sources for kernels).

I'm just wanting to avoid what seems to be a not-so-uncommon human error.

best regards,
Jerome Petazzoni <skaya@enix.org>
--------------------------------------------
Q:      How does a hacker fix a function which
        doesn't work for all of the elements in its domain?
A:      He changes the domain.