all started when i decided to install a dualboot Tiny (at first only in virtualbox, to get accustomed with Tiny's unusual but awesome infrastructure). i accidentaly installed 2 bootloaders (don't ask me how i did it. even myself can't answer that
). after a little "hacking" to the main bootloader (to add the secondary Tiny boot options), i tried to get rid the files of the second bootloader. i opened the filemanager with sudo (i don't think that it would let me delete such files as a regular user). went in the second HD, found "boot", and delete. but it said, it couldn't delete the folder as it was read only (the "criminal" was a single file inside this folder
). ok, lets do it "the men's way"... terminal... su>root (i had asigned a password for root before this), and "rm -rf"... nothing happened.
after some search, i found out that this file was "immunized" (immutab flag is called i think) as read only, even for root, and wanted the chattr command run as root to remove "immunization". ok, download and install e2fsprogs (they contain this command). so again as root i removed the "immunization" of the file and finally got rid of the folder. and then it popped in my mind. "what if i could "immunize" the whole system?"
(i use persistent boot, tce, opt, home). and so did i. i immunized, boot, tce, and opt, with just one command
. i even tried the notorious "sudo rm -rf //". of course my (not so persistent) home folder was wiped away but the whole system didn't have a clue of what just happened (it froze of course but after reset it was like new. nothing was damaged)
now i have the immunization permanent on my Tiny and have nothing to fear (i have downloaded the apps i need and have made the setup i want, so i don't need to have the, boot, tce, opt, folders writable any more). the undead Tiny system boots fine, and IF i want to change something, i just run chattr to temporarily remove immunization, and restore it after having made my changes.