TC will not save some changes

[gerald_clark]

you also need wireless_tools in onboot.lst

[curaga]

That's a dep of wpa_supplicant, so it's loaded automatically.

[u4444]

you also need wireless_tools in onboot.lst

Done. However, I don't think it does anything if I have wpa_supplicant on there.

Also did:
chmod 664 /mnt/hda1/tce/optional/*
And permissions are right.

and I've edited wlan0.sh:
vi wlan0.sh

and inserted
iwconfig wlan0 essid any

When I check
iwconfig wlan0

It shows no ESSID. I don't know shell scripting or how the boot up works. I didn't put sudo behind it because I'm not stupid enough to risk doing that with something I don't know.

EDIT:

That's a dep of wpa_supplicant, so it's loaded automatically.

Yeah, I'll clean up my TCEs and everything (the tce/ folder is a mess cause I was trying every which way to get my wireless PCMCIA card to work.)

[gerald_clark]

/dev/hda1/tce/optional should be 775 not 664.

[u4444]

Ok, I've solved it in wlam0.sh:

sudo iwconfig wlan0 essid <SSID>

[maro]

@u4444: Well, it's good news that you've overcome your initial problem.

Following up on some of the things that have popped up meanwhile I'd like to add some minor comments:

• There should not be a need to make any (manual) changes to the ownership or permissions of files and directories under '.../tce', providing the user has not interfered with the (automatic) setup by the TC processes:
  
  • The directories for extension storage should be automatically created with ownership 'tc:staff' and permission of 775.
  • The respective files (i.e. downloaded extension files as well as 'onboot.lst') should all be with ownership 'tc:staff' and permission of 664.
• There is no need to use sudo when changing the 'onboot.lst' file (i.e. a simple vi .../tce/onboot.lst is enough).
• I believe the fact that extension names were missing from 'onboot.lst' comes down to "user error". Trust me that happens often enough to me even though I initially don't believe for it to be the case. I guess TC worked as designed, but it's easy enough to click accidentally on the wrong button, or miss to type a character when using CLI commands.

[gaixixon]

@gaixixon: I fully agree with the advice given by gerald_clark.

If you want to troubleshoot your problem have a closer look at reply #10. You can use a similar set of commands, just use:
    autoscan tinycore d
    fdisk -l /dev/sda
instead of the ones used above.

Obviously in your expected result you will have to substitute 'tce' with 'tinycore' and 'hda1' with 'sda6'.

Hurray, all of a sudden, my config below (same as before) suddenly works like a charm. I found out the reason why it does not save anything just because I shutdown / reboot my pc via sonsole (sudo reboot) not via shutdown button with the backup option checked.
BUT.. any data I save out of my home folder ~/tc  would be lost! Example, if I add something like:
sudo mkdir /this_is_at_root then it disappear at next reboot.
but sudo mkdir ~/tc/this_remain_after_reboot
what happen?
my boot config (again):

title Tiny Core
kernel /tinycore/bzImage tce=sda6/tinycore/
initrd /tinycore/tinycore.gz

[gerald_clark]

'filetool.sh backup' only backs up the files and directories listed in /opt/.filetool.lst.
Please spend some time reading the wiki.