On Mon, 17 Nov 2003 13:52:41 +0100 (MET)
"Svetoslav Slavtchev" <[EMAIL PROTECTED]> wrote:

> and you dropped some cramfs changes:
> ----------------------- cut here
> ---------------------------------------------------
> --- kernel-source-2.6.0-test9-2.6.0-test9.orig/fs/cramfs/inode.c
> +++ kernel-source-2.6.0-test9-2.6.0-test9/fs/cramfs/inode.c
> @@ -43,7 +43,7 @@
>  static struct inode *get_cramfs_inode(struct super_block *sb, struct
> cramfs_inode * cramfs_inode)
>  {
>         struct inode * inode = new_inode(sb);
> -       static struct timespec zerotime;
> +       const struct timespec zerotime = { 0, 0 };
> 
>         if (inode) {
>                 inode->i_mode = cramfs_inode->mode;
> ---------------------- cut here
> ----------------------------------------------

sorry, I didn't included it in my previous mail :/
But I used it for my tests.

> have you tried adding "--nocompress"
> cramfs is already compressed and adding --nocompress increases the
> size with~2k

Yes, I tried, with --compress, the initrd is really a cramfs one (not a
gzipped cramfs), so it needs the cramfs initrd patch.

Same results, the cramfs image is recognized, but cannot be mounted.

It won't make any difference to compress or not the cramfs initrd if the
cramfs initrd patch is applied.
I repeat one more time: it is only needed for non-compressed cramfs
initrd :-)

> i've tried your initrd changes and all seemd fine until it actually
> tried to mount it
> :-) i've forgotten to compile in cramfs :-)
> so let see what happens when the recompile is ready

Good luck :)

> > Strangly enough, I can mount the initrd correctly once the kernel is
> > booted up (in this case, I use a ext2 initrd, ext2 and cramfs are
> > builtin).
> > 
> > Should I ask about it on lkml ?
> 
> PS
> 
> the old modular ide is broken even if everything is compiled in
> ( see "buffer layer errot....."  on lkml )
> fix & new patch uploaded, but i still get a oopses at cdrom
> initialization kobject_register returned -17

I'll have a look later.

Cheers.

-- 
Olivier Blin

Reply via email to