Sorry, I've just noticed that I got confused somehow about which problem
I needed to respond to when I sent the below quoted response to this
discussion.

@upiter, I just sent you a response regarding your "mv: target
`binary/live/vmlinuz' is not a directory" issue.
@charles, below is a quoted copy of my response to your "mount: special
device config does not exist" issue, if you didn;t notice it before,
with it having been incorrectly sent addressed to upiter.

I have no idea why both of you are ending up with both the 3.16 and 3.2
kernels, you should just have the 3.16 kernel, as I did in the test I
just ran today to try to get tot he bottom of the problems you're
experiencing. Clearly you both must be doing something wrong. Try to
follow the instructions I gave in the other message I just sent (I
response to upiter's issue).


On 22/01/2015 13:27, jnqnfe wrote:
> The following line in your output/log tells us that it's made it into
> the chrook_hooks script:
>
> [2015-01-13 22:54:34] lb chroot_hooks
>
> clearly it is getting as far as outputting "Begin executing hooks..."
> since that appears in your output/log.
>
> The important line in your ouput/log is this one:
>
> mount: special device config does not exist
>
> This tells us that the mount program cannot find something called
> 'config'. If you look in the chroot_hooks script, the very first thing
> it does, after the usual script initialisation stuff is execute the
> following block of code (copied from LB v4.0.4-1):
>
> # Make build config available to chroot hooks. First, make the bind
> # mount and then make it read-only. This can't happen in one mount
> # command, then the resulting mount will be rw (see mount(8)). Making it
> # ro prevents modifications and prevents accidentally removing the
> # contents of the config directory when removing the chroot.
> mkdir -p chroot/live-build/config
> mount -o bind config chroot/live-build/config
> mount -o remount,ro,bind config chroot/live-build/config
>
> So, it is trying to mount the chroot/live-build/config directory it
> just created, to your config directory. According to the error, your
> config directory does not exist at this point...
>
> Do you have a config directory prior to or at the start of your build
> process? (Running lb config prior to lb build will create it, though
> lb build will run lb config automatically if you don't do it
> manually). There should be no reason for not having a config
> directory. Check it exists, and if so, check the permissions (or just
> delete and allow it to be recreated). Try ensuring that a clean build
> is done by executing lb clean before anything else.
>
> Which version of live-build are you using? 3.x or 4.x? I am not
> familiar with 3.x. If that is what you are using, perhaps it has a
> bug, but if 4.x, I'd lean towards user error...
>
>
> On 22/01/2015 12:35, [email protected] wrote:
>>
>> hi
>>
>> Has anyone an idea for this BUG, why the binary.img won't be created?
>>
>>  
>>
>>  
>>
>> On 2015-01-14 09:50, [email protected] wrote:
>>
>>> Hi
>>>
>>> Today I have tried to craete hdd image with backports kernel, but 
>>> binary.img was not created:
>>>
>>> .......................................................................................
>>>
>>> [2015-01-14 10:40:09] lb binary_grub
>>> [2015-01-14 10:40:09] lb binary_grub2
>>> [2015-01-14 10:40:09] lb binary_syslinux
>>> P: Begin installing syslinux...
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Suggested packages:
>>>  os-prober
>>> Recommended packages:
>>>  mtools libcrypt-passwdmd5-perl
>>> The following NEW packages will be installed:
>>>  syslinux syslinux-common
>>> 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
>>> Need to get 1031 kB of archives.
>>> After this operation, 3393 kB of additional disk space will be used.
>>> Get:1 http://ftp.de.debian.org/debian/ wheezy/main syslinux-common all 
>>> 2:4.05+dfsg-6+deb7u1 [934 kB]
>>> Get:2 http://ftp.de.debian.org/debian/ wheezy/main syslinux i386 
>>> 2:4.05+dfsg-6+deb7u1 [96.1 kB]
>>> Fetched 1031 kB in 0s (2805 kB/s)
>>> Selecting previously unselected package syslinux-common.
>>> (Reading database ... 67291 files and directories currently installed.)
>>> Unpacking syslinux-common (from 
>>> .../syslinux-common_2%3a4.05+dfsg-6+deb7u1_all.deb) ...
>>> Selecting previously unselected package syslinux.
>>> Unpacking syslinux (from .../syslinux_2%3a4.05+dfsg-6+deb7u1_i386.deb) ...
>>> Processing triggers for man-db ...
>>> Setting up syslinux-common (2:4.05+dfsg-6+deb7u1) ...
>>> Setting up syslinux (2:4.05+dfsg-6+deb7u1) ...
>>> mv: target `binary/live/vmlinuz' is not a directory
>>> P: Begin unmounting filesystems...
>>> P: Saving caches...
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>>
>>> # ls
>>> auto binary.list cache chroot.packages.install config
>>> binary binary.packages chroot chroot.packages.live local
>>>
>>>
>>> Knows anyone a solution?
>>>
>>>
>>> greetings
>>> Piotr
>>>
>>>
>>> On 2015-01-14 07:08, Charles Samuels wrote:
>>>> On Tuesday, January 13, 2015 10:08:19 PM Charles Samuels wrote:
>>>>> Solved: I add this to config/package-lists/my.list.chroot:
>>>> Setting up user-setup (1.48) ... Processing triggers for
>>>> initramfs-tools ... update-initramfs: Generating
>>>> /boot/initrd.img-3.2.0-4-amd64 df: Warning: cannot read table of
>>>> mounted file systems: No such file or directory live-boot: core
>>>> filesystems devices utils udev wget blockdev. [2015-01-13 22:54:34]
>>>> lb chroot_includes P: Begin copying chroot includes... [2015-01-13
>>>> 22:54:34] lb chroot_hooks P: Begin executing hooks... mount:
>>>> special device config does not exist P: Begin unmounting
>>>> filesystems... P: Saving caches... Reading package lists... Done
>>>> Building dependency tree Reading state information... Done and then
>>>> live-build exits without creating an image. How is it getting
>>>> 3.2.0-4 and why does live-build appear to want to install
>>>> linux-image-amd64 and the one I specify in
>>>> LB_LINUX_PACKAGES="linux-image-3.16.0-0.bpo.4"? Charles
>

Reply via email to