Tiny Core Linux
General TC => General TC Talk => Topic started by: deodion on August 20, 2017, 07:15:45 AM
-
I have Core 8.0 x64 installed in frugal,
I did everything based in wiki to make persistent,
for example putting bootlocal.sh in
/mnt/sda1/opt
/mnt/sda1/tce/opt
/mnt/sda1/tce/optional
the file contains:
sudo ln -s /lib /lib64
for /mnt/sda1/boot/extlinux/extlinux.conf
tried:
tinycore norestore tce=sda1 opt=sda1
or
norestore tce=sda1 opt=sda1
or
opt=sda1
it just doesnt work, its so amazing, I follow the wiki. Am I missing something again?
-
Judging by your comment, I believe you have your bootlocal.sh modified and want to keep it.
Did you perform a backup before you reboot?
In GUI, use filetool or exittc.
In prompt, use filetool.sh -bv.
-
Hi deodion
bootlocal.sh belongs in your /opt directory and will automatically be include when you run a backup.
Using the norestore boot code tells the system not to restore the files you backed up.
-
Perhaps post output of
showbootcodes
-
Hi deodion
One other thing, if you make /opt persistent, you need to remove any references to opt from your /opt/filetool.lst file.
-
How can I change anything like /opt/bootlocal.sh but when I reboot it, it will reload the fresh one (nothing inside)?
Are you guys saying all the persistent feature must be supervise by filetool.lst backup?
because there is no way to persist bootlocal.sh and bootsynnc.sh??
From what I see, /mnt/sda1/boot/extlinux/extlinux.conf alone is not working as explained in Wiki,
need to have at least the help of filetool.lst be backed up, from what I get there is no way to persist /opt/bootlocal.sh and bootsync.sh
I successfully reload backed bootlocal.sh
which contain: ln -s /lib /lib64
-
Hi deodion
One other thing, if you make /opt persistent, you need to remove any references to opt from your /opt/filetool.lst file.
Ohh mann this explain why,
-
Hi deodion
One other thing, if you make /opt persistent, you need to remove any references to opt from your /opt/filetool.lst file.
Are you saying to make this work, then I have to backup (mydata.tgz) with empty filetool.lst ?
This is the only logic I can see now,
Edit:
Hello Rich,
Please explain it how, thanks
I'm not comfortable asking too much basic question but wiki isnt helping me much,
-
Are you guys saying all the persistent feature must be supervise by filetool.lst backup?
The persistent feature is supervise by /opt/.filetool.lst and /opt/.xfiletool.lst
because there is no way to persist bootlocal.sh and bootsynnc.sh??
Both bootlocal.sh and bootsync.sh should persist by default.
From what I see, /mnt/sda1/boot/extlinux/extlinux.conf alone is not working as explained in Wiki,
need to have at least the help of filetool.lst be backed up, from what I get there is no way to persist /opt/bootlocal.sh and bootsync.sh
extlinux.conf is a config file for EXTLINUX, which specifies which kernel to use, which initrd to load and what bootcodes to be passed.
The only bootcodes that matter are base and norestore.
I successfully reload backed bootlocal.sh
which contain: ln -s /lib /lib64
Is that a success in backing up the files for you ? ???
-
If both bootlocal.sh and bootsync.sh is persist by default, how come I can't change its config inside?
After reboot it just new blank ones,
The only bootcodes that matter are base and norestore.
what is the use/meaning of opt=sda1 then?
I thought its like I have to have storage medium, then it will automatically load/read/write that /mnt/sda1/opt instead? which is logically simple?
But thats not what I'm getting,
I get the mydata.tgz reloaded after reboot,
it just contains: ln -s /lib /lib64 for testing,
I am really sorry guys, but it seems it doesnt have enough comprehension in wiki, how things working,
-
what is the use/meaning of opt=sda1 then?
The bootcode specify the path to a local opt directory on your disk.
In that case, you should remove "opt" from your /opt/.filetool.lst
Adjust /mnt/sda1/opt/bootlocal.sh
Backup (filetool.sh -bv)
Reboot
-
The bootcode specify the path to a local opt directory on your disk.
In that case, you should remove "opt" from your /opt/.filetool.lst
Adjust /mnt/sda1/opt/bootlocal.sh
Backup (filetool.sh -bv)
Reboot
Is this in other words means: filetool.sh -bv knows which one to back up? which is backup: /mnt/sda1/opt/bootlocal.sh? NOT /opt/.... ?
and thats because of I removed "opt" from /opt/.filetool.lst or/and because of opt=sda1??
Because from what I understand is: by design TCL is always loaded new from (whatever it is: the corepure64.gz/vmlinuz) but has by default automatic restore if mydata.tgz is not zero?
-
Since you have opt specified via bootcode opt=sda1.
The opt in mydata.tgz may overwrite your local opt directory on your disk (/mnt/sda1/opt)
When TC boots with bootcode home=disk, opt=disk
The directories are created (on the disk) and linked to the system.
i.e.
ln -s /mnt/disk/home /home
ln -s /mnt/disk/opt /opt
Therefore, you should remove "opt" from your (/mnt/sda1)/opt/.filetool.lst in order to drop the opt directory from your mydata.tgz to prevent overwrite.
And modify your (/mnt/sda1)/opt/bootlocal.sh
-
@deodion
Persistence can be confusing, but I'm sure you will find it easier to understand if you read Chapter 7.x from the core book available in PDF format here http://tinycorelinux.net/book.html (http://tinycorelinux.net/book.html).
You'll know by now that there is more than one way to create persistent storage and each method will likely cause a conflict.
Given the default install for splunk is in /opt you'll probably want to use the opt=sda1 bootcode and disable opt from the backup, or disable backup altogether..?
-
@deodion
Persistence can be confusing, but I'm sure you will find it easier to understand if you read Chapter 7.x from the core book available in PDF format here http://tinycorelinux.net/book.html (http://tinycorelinux.net/book.html).
You'll know by now that there is more than one way to create persistent storage and each method will likely cause a conflict.
Given the default install for splunk is in /opt you'll probably want to use the opt=sda1 bootcode and disable opt from the backup, or disable backup altogether..?
Yes thank very much coreplayer2,
-
All of my confusion is answered by looking at the book,
in chapter 7, it explains bootcodes needs to use APPEND command, or it will not work