livecd-creator unmounting temp image, running daemons.

Jerry Vonau jvonau at shaw.ca
Sun Jul 27 16:52:34 UTC 2008


Martin:
Your cc to the livecd list are not appearing there, are you subscribed?

Martin Langhoff wrote:
> On Sun, Jul 27, 2008 at 8:45 PM, Martin Langhoff
> <martin.langhoff at gmail.com> wrote:
>> Sounds complex. I will try going in the opposite direction: downgrade
>> the package on F9 or pass flags to disable the new fanciness.
> 
> Right - with the following patch to fs.py the F7 kernel won't panic
> anymore, and a basic F8 will boot. The mkfs tweak is probably
> unneeded, the main difference seems to come from -no-sparse:
>

Think the issue is going to be how the kernel modules differ from
version 3.2 and 3.3 of squashfs-tools.  

So lets get this clear, F7 is using the 2.6.23.?? and does not boot,
F8 is now booting correctly? with which kernel?
 
> --- a/imgcreate/fs.py
> +++ b/imgcreate/fs.py
> @@ -38,7 +38,7 @@ def makedirs(dirname):
>              raise
> 
>  def mksquashfs(in_img, out_img):
> -    args = ["/sbin/mksquashfs", in_img, out_img]
> +    args = ["/sbin/mksquashfs", in_img, out_img, '-no-sparse', '-b',
'131072']
> 
>      if not sys.stdout.isatty():
>          args.append("-no-progress")
> @@ -200,7 +200,7 @@ class SparseExtLoopbackMount(SparseLoopbackMount):
> 
>      def __format_filesystem(self):
>          rc = subprocess.call(["/sbin/mkfs." + self.fstype,
> -                              "-F", "-L", self.fslabel,
> +                              '-I', '128', "-F", "-L", self.fslabel,
>                                "-m", "1", "-b", str(self.blocksize),
>                                self.lofile,
>                                str(self.size / self.blocksize)])
> 
> 
> On F7 - my actual target ATM - the problem is not gone through. Init
> is dropping me to a panic shell, and I cannot figure out how to get
> something I can mount there. When I get dropped in the shell, lsmod
> makes it seem like no interesting modules have been loaded.
> modprobe-ing libata, cdrom and other modules works. I don't know the
> major/minor numbers enough to mknod my way around here.
> 

see above

> So I suspect of the initrd, but I am unsure of what to do next. The
> mayflower initrd seems to work though it does  throw some (IMO)
> meaningless errors - complaining about old module names that are not
> relevant to the 2.6.23 kernel I have:
> 
> Building an initramfs at /boot/initrd-2.6.23.1-21.fc7.img for kernel
> 2.6.23.1-21.fc7
> FATAL: Module ide_cd not found.
> FATAL: Module =ata not found.
> FATAL: Module usbhid not found.
> FATAL: Module ieee1394 not found.
> Done; initramfs is 4.2M.
> 
> any more hints on this track?
> 

Think the only way you'll get this to fly is to get the source for
squashfs-tools3.3  http://www.squashfs-lzma.org/dl/squashfs3.3.tar.gz
and patch your 2.6.23 kernel and recompile the module and replace the
module in the initrd. There is a good post on the livecd list about
patching squashfs for lsma support and covers all the steps, perhaps you
could adapt the steps(leave out the lzma patches). 
https://www.redhat.com/archives/fedora-livecd-list/2008-July/msg00007.html
https://www.redhat.com/archives/fedora-livecd-list/2008-July/msg00005.html
Repacking is initrd and iso are not that hard, but I have some notes
around if you need them.

Jerry





More information about the fedora-devel-list mailing list