Other Help Topics :: Struggling to Remaster

Quote (casio @ Nov. 21 2005,16:45)

I think the problem here is that for some reason the mkwriteable routine is not been run. When I look at this script there are several directories that should be copied to the ramdisk. Once I boot the remastered disk, these directories are not in the /ramdisk area.

mkwriteable needs to be run as root. If not then the commands it calls won't run becuase of the permissions they require, even if mkwriteable itself would allow you to run it.

Where are you trying to run mkwriteable from? From the bootlocal.sh script? That's probably the best place to put it for a remaster. You would need to run it as sudo /etc/init.d/mkwriteable. You could also just add the lines you want to run to bootlocal.sh if you preface them with sudo to run them as root.

Personally I thought that anything in /etc/init.d ran on boot up. However from what you have said, this is not the case as you are suggesting I place it within bootlocal.sh.

I am used to other flavours of Linux where the init.d or rc2.d areas are looked at on boot up. Is this not the case with DSL?

When I ran mkwriteable I was logged in as root by doing sudo su. I then ran mkwriteable by entering ./mkwriteable at the /etc/init.d prompt.

Currently I am also experimenting with DSL embedded in windows as well. This has been fun

Adding it to the bootlocal.sh has made this work thanks Clacker. The only thing is, is that the other directories in mkwriteable make their attempt to create their symbolic links but fail as these have already been created.

Any reason why mkwriteable doesnt start by itself from /etc/init.d?

original here.