Comment 5 for bug 1095484

I have to apologize for the whole issue! It is all my mistake. I changed
the Ubuntu name which messes everything up. Your program is very good, but
there is no solution for a mistake such as I made. Eventually, when time
permits will try to aid in a solution! Judging by what I have read in
issues, I will bet I am not the only one that has made this foolish mistake.

Once you enter the improper name, the modules get messed up which in turn
with the command update-intramfs then searches for all modules instead of
the module you are trying to update! As I have stated, I only have 8 months
using Linux. I am not expert! I have learned many things but never
everything and will remain that way no matter how far I go!

On Sat, Jan 5, 2013 at 2:23 AM, Francesco Muriana <
<email address hidden>> wrote:

> *** This bug is a duplicate of bug 1080110 ***
> https://bugs.launchpad.net/bugs/1080110
>
> ** This bug has been marked a duplicate of bug 1080110
> when assembling the image ,the md5sum is not registered in the image
> because of this there is an error in the VM
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1095484
>
> Title:
> Ubuntu Builder initramfs -u problem
>
> Status in Ubuntu Builder:
> Incomplete
>
> Bug description:
> While in chroot of Ubuntu Builder and you try to update initramfs -u
> instead of going to the file in boot of the system you are trying to
> create, it tries to update the hosts which fails. Unless you use
> automatic creation you won't get iso/casper/initrd.lz if you have
> installed many programs while in chroot of Ubuntu builder. Just looks
> as if once you go above 2 gigs for an ISO this program fails every
> time!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-builder/+bug/1095484/+subscriptions
>