Tiny Core Base > Release Candidate Testing
Core v4.4rc3
AbNoRMiS:
thanks for clarifying, now it's clear :)
i always installed tc manually and never used tc-install
and therefore could not understand what is this
vinnie:
--- Quote ---It's only for loading extensions from an iso file, in the running session.
--- End quote ---
Uhm I misread!
--- Quote ---you could use memdisk (http://www.syslinux.org/wiki/index.php/MEMDISK) for that purpose ...
--- End quote ---
effectively I remember I had tried some time ago, trying to start [remaster] iso from tinycore.
now that you reminded me, what was exactly happening is that it started without the extensions.
So that means I can start other distros using tinycore as bootloader for derived and not derived?
gerald_clark:
Tiny core is not working as a bootloader.
Your bootloader is loading the tinycore kernel and initrd.
With the new iso=option, tinycore can now find the tce directory inb that iso.
mladen:
Thank You for 4.4rc3 Roberts !
With `fromISOfile` I get just what I needed when try to experiment with cde boot option - a possibility to boot a system to a customizable starting X/GUI configuration, without using .tcz or .scm extensions from standard /tce directory.
You were quite right with:
" On a usb install you should be using a normal live tce directory and not cde.
cde is intended for cdrom and isohybrid for delivery of read-only extensions due to the
factoring out of X/GUI from the initrd strting with version 4.2"
in 4.4rc2 conversation:
AbNoRMiS:
error permissions issued during the backup
--- Quote ---tc@box:~$ filetool.sh -b
sed: can't create temp file '/opt/.filetool.lstrjEe5X': Permission denied
Backing up files to /mnt/sda1/tce/mydata.tgz Done.
--- End quote ---
sed (string 158) haven't permissions to delete the empty lines
--- Code: ---sed -i /^$/d /opt/.filetool.lst
--- End code ---
sudo should be used
--- Code: ---sudo sed -i /^$/d /opt/.filetool.lst
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version