General TC > Programming & Scripting - Unofficial
ezremaster: Wizard that walks you step by step to remaster ISO of tinycore
ixbrian:
I apologise for the confusion. I have created a new extension with the previous version of ezremaster named ezremaster-legacy.tcz.
For Tiny Core 4.0 or 4.1, use ezremaster-legacy.tcz
For Tiny Core 4.2rc1 (when released) and later use ezremaster.tcz
Thanks,
Brian
gavs:
Brian
Thank you for your efforts. The legacy version is working for me.
gavs
gavs:
I am using Tinycore 4.1 with ezremaster-legacy.tcz and my first step is to create a remaster with alsa functioning on boot (I will later add mpd and gmpc to complete my music appliance). The target system has enough ram so I am extracting in to initrd (I assume this is the best option for a functioning music appliance with the fastest power-up). I have tried both options for the startup scripts (run in chroot or add to bootlocal). Ezremaster creates the iso successfully, but alsa is not functioning on boot (I notice that /proc/asound has not been created).
An earlier posting by littlebat suggested that 2 lines should be added at the head of the function package() in order to update modules.dep and ld.so.cache (I notice that these lines have been added to ezremaster 2.0.3). Is this the reason why an alsa remaster does not boot with alsa functioning? If so, can I easily modify /usr/local/bin/remaster.sh to include these lines (initial attempts with editor result in the error message that the filesystem is read only, even when I use run sudo editor)?
gavs
Rich:
Hi gavs
Besides including the ALSA extension, did you provide a means to either run a setup script OR to
restore working ALSA configuration settings?
ixbrian:
--- Quote from: gavs on December 10, 2011, 01:47:11 PM ---I am using Tinycore 4.1 with ezremaster-legacy.tcz and my first step is to create a remaster with alsa functioning on boot (I will later add mpd and gmpc to complete my music appliance). The target system has enough ram so I am extracting in to initrd (I assume this is the best option for a functioning music appliance with the fastest power-up). I have tried both options for the startup scripts (run in chroot or add to bootlocal). Ezremaster creates the iso successfully, but alsa is not functioning on boot (I notice that /proc/asound has not been created).
An earlier posting by littlebat suggested that 2 lines should be added at the head of the function package() in order to update modules.dep and ld.so.cache (I notice that these lines have been added to ezremaster 2.0.3). Is this the reason why an alsa remaster does not boot with alsa functioning? If so, can I easily modify /usr/local/bin/remaster.sh to include these lines (initial attempts with editor result in the error message that the filesystem is read only, even when I use run sudo editor)?
gavs
--- End quote ---
Hi gavs,
It is showing read only when you try to edit remaster.sh because it is a symlink to a readonly squashfs extension. Try this:
--- Code: ---sudo cp /tmp/tcloop/ezremaster-legacy/usr/local/bin/remaster.sh /usr/local/bin
sudo vi /usr/local/bin/remaster.sh
--- End code ---
Note that any changes you make to remaster.sh like this will be lost when you reboot the system.
Ezremaster 2.0.3 includes the 2 line fix suggested by littlebat, so rather than editing remaster.sh you could use 2.0.3 along with Tiny Core 4.2rc1.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version