Hi Pavel.
>>Building i386 bootdisk.img
>>cp: writing `/tmp/makebootdisk.tree.9911/vmlinuz': No space left on device
>>192000 pixels, 6717 bytes, (93.00% compression)
>>cp: writing `/tmp/makebootdisk.tree.9911/splash.lss': No space left on device
>>sed: Couldn't flush stdout: No space left on device
>>/files/work/backUP/Panama/buildinstall.tree.3241/mk-images: Failed to copy messages from /tmp/treedir.3260/instimage/usr/lib/anaconda-runtime/boot/ to
>>/tmp/makebootdisk.tree.9911.
Do you have a seperate /tmp ?
If so, it's probably full.
If you run the buildinstall script many times you'll notice that it
doesn't always clean up after itself so remove all the directories and
files it's created. If you look you'll notice which ones they are.
Or unmount /tmp and don't have it seperate.
anaconda always builds in /tmp.
>>I'm a bit confused becouse I have much of free space on my hd. So I
>>want to ask may be you have an expiriense of creating Fedora costume
>>distro based on your kernel packages?
Look above.
> No, I personally haven't created custom distributions or CDs based on
> Fedora, but Stefan Smietanowski <stesmi@stesmi.com> has done so. You
> can join atrpms-devel (Cced, you can subscribe at lists.atrpms.net).
That's me.
> About the error message: I believe it means the space on the
> bootdisk.img floppy image. I suggest to not add a bootsplash to the
> -BOOT kernel to avoid it growing too large, or you can hack anaconda
> to use different kernels for the CD boot vs the floppy boot.
I don't think that's the case. Look above.
It's when vmlinuz is copied, not when mk*fs is run.
// Stefan
>>Building i386 bootdisk.img
>>cp: writing `/tmp/makebootdisk.tree.9911/vmlinuz': No space left on device
>>192000 pixels, 6717 bytes, (93.00% compression)
>>cp: writing `/tmp/makebootdisk.tree.9911/splash.lss': No space left on device
>>sed: Couldn't flush stdout: No space left on device
>>/files/work/backUP/Panama/buildinstall.tree.3241/mk-images: Failed to copy messages from /tmp/treedir.3260/instimage/usr/lib/anaconda-runtime/boot/ to
>>/tmp/makebootdisk.tree.9911.
Do you have a seperate /tmp ?
If so, it's probably full.
If you run the buildinstall script many times you'll notice that it
doesn't always clean up after itself so remove all the directories and
files it's created. If you look you'll notice which ones they are.
Or unmount /tmp and don't have it seperate.
anaconda always builds in /tmp.
>>I'm a bit confused becouse I have much of free space on my hd. So I
>>want to ask may be you have an expiriense of creating Fedora costume
>>distro based on your kernel packages?
Look above.
> No, I personally haven't created custom distributions or CDs based on
> Fedora, but Stefan Smietanowski <stesmi@stesmi.com> has done so. You
> can join atrpms-devel (Cced, you can subscribe at lists.atrpms.net).
That's me.
> About the error message: I believe it means the space on the
> bootdisk.img floppy image. I suggest to not add a bootsplash to the
> -BOOT kernel to avoid it growing too large, or you can hack anaconda
> to use different kernels for the CD boot vs the floppy boot.
I don't think that's the case. Look above.
It's when vmlinuz is copied, not when mk*fs is run.
// Stefan