On 03/11/2013 12:05 PM, J. Cassidy wrote: > My own build yes, 64 bit.
fwiw, debian has multiple 64-bit architectures. If you mean amd64 (aka
x86_64), using the specific term avoids possible ambiguity :)
> It was my naiive asssumption that the debirf process would use the
> existing (my own build) kernel variables / parameters to do it's thing..
By default, debirf selects and installs a kernel from the distribution
you're building.
> in particular, can you supply the output of uname -r ?
>
> root@Carcassonne ~: uname -ars
> Linux Carcassonne 3.8.1 #2 SMP PREEMPT Sat Mar 2 11:04:32 CET 2013 x86_64
right, in this case you'd need to use DEBIRF_KERNEL_FLAVOR to select a
kernel flavor, or explicitly supply a kernel .deb via the --kernel-deb
argument:
debirf make --kernel-deb=/path/to/linux-image-whatever.deb xkiosk
> the install-kernel module assumes that the kernel flavor (e.g. "amd64")
> can be derived from $(uname -r | cut -d- -f3-). If your kernel doesn't
> supply that, you can force the matter with an environment variable, by
> running like:
>
> DEBIRF_KERNEL_FLAVOR=amd64 debirf make xkiosk
I didn't see any report of you trying this. does it work for you?
> I ran with the "r" switch to see if the ensuing output would enlighten me
> more perhaps.
sure, testing is fine and reasonable -- just be aware that it may cause
changes on your host system that you don't expect. we hope it won't,
and we'd consider it a bug if it does, but the way to ensure that it
doesn't damage the host system is to build as a non-privileged user. So
certainly, don't run with -r in a production environment.
Regards,
--dkg
signature.asc
Description: OpenPGP digital signature
