RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs

Fri, 03 Feb 2006 22:05:06 -0800

Bernard,

 

I just though of something that my have caused the read only problem.  I may have gotten the initrd.img by extracting it from a mounted autoinstall iso image file which is an iso9660 ro file system rather than using the original initrd.img.  I should perhaps retry this by starting with the initrd.img file under the standard boot i386 directory.

 

Sorry for the premature post, hope this will fix the problem.

 

Thanks,

Bela

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi
Sent: Saturday, February 04, 2006 12:35 AM
To: [email protected]
Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs

 

Bernard,

 

Thanks, but to clarify:

 

I basically did that, it was unzipped, mounted as a loop device, modified the function script and then I recreated initrd.img with mkcramfs then gzipped it.

 

Are you saying that I should not create a cramfs file from the initrd directory?  Otherwise the steps in your response are the same as performed.

 

Thanks,

Bela

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li
Sent: Friday, February 03, 2006 11:35 PM
To: [email protected]; [email protected]
Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs

 

Hi Bela:

 

It appears that you can mount the initrd.img and write to it:

 

mv initrd.img initrd.img.gz

gunzip initrd.img.gz

mount -o loop initrd.img /mnt

 

Modify the file, then gzip it.  Hopefully it'll work.

 

Cheers,

 

Bernard

 

From: [EMAIL PROTECTED] on behalf of B. Erdelyi
Sent: Fri 03/02/2006 20:22
To: [email protected]
Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs

Bernard,

 

My thinking is that for whatever reason this has to do with BusyBox and the environment that it is running on our machine.  The options are not being passed on.  To test this theory I wanted to hardwire the mount tmpfs command in the script to see what happens.  I found the command in the “functions” script and replaced it with:

 

mount tmpfs /new_root –t tmpfs –o size=2g,nr_inodes=2000,mode=777 || shellout

 

Then I recreate the initrd.img with mkcramfs, gziped it and placed it in the standard flavor directory.  Unfortunately, when I load from the new autoinstall cd I get an error indicating that the file system is read only and the rcS script cannot write a text file to it (line 41 of the rcS script).

 

What am I doing wrong?  I thought that the mode command with 777 would create the file system with full access.  Is there other options being passed on via the $tmpfs_opt variable?  Or should I be setting rw access somewhere else when I recreate the cramfs initrd.img?

 

I would really like to test this out to see if by bypassing the parameter passing solves the issue.  It may give you a better hint at what is going on.  Any suggestions will be appreciated.

 

Thanks,

Bela

Reply via email to