Control: tag 702706 + moreinfo

On 03/10/2013 10:43 AM, J. Cassidy wrote:
Debirf 0.33


some more related stuff.

Debirf has built me a 3.2.x kernel... see below -

root@Carcassonne ~/debirf/xkiosk: ls -als
total 132168
     4 drwxr-xr-x  5 1000 1000      4096 Mar 11 17:43 .
     4 drwxr-xr-x  5 root root      4096 Mar 11 16:37 ..
    40 -rw-r--r--  1 root root     39468 Mar 11 17:39 .bootstrap.log 40
-rw-r--r--  1 root root     39468 Mar 11 16:45 bootstrap.log
     4 -rw-r--r--  1 1000 1000      1453 Mar 11 17:34 debirf.conf
128444 -rw-r--r--  1 root root 131521379 Mar 11 17:44
debirf-xkiosk_wheezy_3.2.0-4-amd64.cgz
   856 -rw-r--r--  1 root root    873303 Mar 11 17:44
.fakeroot-state.debirf-xkiosk
     4 drwxr-xr-x  2 1000 1000      4096 Dec  5  2011 modules
     4 drwxr-xr-x  4 root root      4096 Mar 11 17:43 nest
     4 drwxr-xr-x 22 root root      4096 Mar 11 17:43 root
  2764 -rw-r--r--  1 root root   2829472 Dec 19 15:16 vmlinuz-3.2.0-4-amd64






=> Hello Daniel,
=>
=> appreciate the time you have taken to look at my problem.
=>
=> Answers below:
=>
=> => Control: tag 702706 + moreinfo
=> =>
=> => On 03/10/2013 10:43 AM, J. Cassidy wrote:
=> =>> Package: Debirf 0.33
=> =>>
=> =>> Debirf 0.33 in Wheezy with 3.8.1 kernel. rc=134
=> =>
=>
=> Are you running your own build of the kernel, or the build from debian
=> experimental?  it looks to me like you're doing this on amd64 as well
-- => is that right? - My own build yes, 64 bit.
=>
=>
=> =>
=> =>> on running "debirf make xkiosk" using the abovementioned setup all
=> seems
=> =>> to proceed well (Retrieving, Validating etc.) until this -
=> =>
=> were you hoping to build a debirf image with the 3.8 kernel?  or with
=> the stock wheezy kernel?  That is, is 3.8 a property of the build
system => or the intended target?  if it is intended for the target, how
were you => instructing debirf to build against the 3.8 kernel?
=>
=> It was my naiive asssumption that the debirf process would use the =>
existing (my own build) kernel  variables / parameters
=> to do it's thing..
=>
=> 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 => GNU/Linux
=>
=>
=> =>
=> => 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
=> =>
=> =>> Debirf with the "r" switch produces a slightly different error
message => -
=> =>
=> We generally discourage running with -r, since it has the possibility
of => modifying the build system itself.
=>
=> I ran with the "r" switch to see if the ensuing output would enlighten
me => more perhaps.
=>
=>
=>
=>
=> Debirf conf (xkiosk)
=> ============
=>
=> # DEBIRF configuration file: this will be sourced by bash
=>
=> # Label for debirf system (for hostname and initrd).  "debirf" will be
=> # used if unspecified.
=> #
=> DEBIRF_LABEL="debirf-xkiosk"
=>
=> # Where shoud debirf build the image?  By default, debirf will build =>
# in the profile directory.
=> #
=> #DEBIRF_BUILDD=
=>
=> # What suite should be used?  The default is determined by
=> # lsb_release, and falls back to "sid".
=> #
=> #DEBIRF_SUITE=
=>
=> # The default distro (eg. "debian" or "ubuntu") is based on the distro
=> # of the suite specified.  If you want to use a suite from a
=> # non-Debian/Ubuntu distro, specify the distro explicitly here (all =>
# lowercase).
=> #
=> #DEBIRF_DISTRO=
=>
=> # What mirror should debirf pull the suite from?  By default, this is
=> # based on the DEBIRF_DISTRO
=> # (eg. "http://mirrors.kernel.org/${DEBIRF_DISTRO}";).
=> #
=> #DEBIRF_MIRROR=
=>
=> # What keyring should be used to verify the debootstrap for the => #
specified suite?  This is also based on the DEBIRF_DISTRO by
=> # default.  If you are trying to build a non-Debian/Ubuntu version of
=> # debirf, then you will need to specify the keyring explicitly here if
=> # you want to verify the debootstrap.  Otherwise, uncomment the => #
variable but leave the definition blank to have debirf skip the => #
debootstrap verification.
=> #
=> #DEBIRF_KEYRING=
=>
=> # Use a web proxy for downloading the packages (the "export" in front
=> # of the variable is necessary to have it recognized by all internal =>
# functions).
=> #
=> #export http_proxy=
=>
=>
=>
=> I have just ran --debirf make xkiosk-- again, beforehand I set the =>
variable "DEBIRF_KERNEL_FLAVOR=amd64 debirf make xkiosk" via export. =>
=> Debirf now runs/works... but with a lot of references to Squeeze in the
=> installation dialogue(s).
=>
=> Please see attached bootstrap log.
=>
=> If you need any more information, please let me know.
=>
=>
=> Regards,
=>
=>
=> John Cassidy
=>
=>
=>
=>
=> John Cassidy (Dipl.-Ing.)
=>
=> Kapellenstr. 21a
=>
=> D-65193 Wiesbaden
=>
=> EU
=>
=>
=>
=> Mobile:     +49 (0) 170 794 3616
=>
=>
=> http://www.JDCassidy.eu
=> http://en.federaleurope.org/
=>


John Cassidy (Dipl.-Ing.)

Kapellenstr. 21a

D-65193 Wiesbaden

EU



Mobile:     +49 (0) 170 794 3616


http://www.JDCassidy.eu
http://en.federaleurope.org/




John Cassidy (Dipl.-Ing.)

Kapellenstr. 21a

D-65193 Wiesbaden

EU



Mobile:     +49 (0) 170 794 3616


http://www.JDCassidy.eu
http://en.federaleurope.org/


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to