WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: bootsync.sh, bootlocal.sh, and shutdown.sh: always for user?  (Read 3191 times)

Offline genec

  • Full Member
  • ***
  • Posts: 240
bootsync.sh, bootlocal.sh, and shutdown.sh: always for user?
« on: September 04, 2011, 08:10:41 AM »
Are the files bootsync.sh, bootlocal.sh, and shutdown.sh in /opt/ to always remain for the user (as opposed to distro/extension authors; end user or remastering user) and will never be used by the Core to do anything useful?  The reason I ask is that users (especially on other distros) sometimes modify system configs/scripts and have to examine differences whenever upgrading to ensure that new critical options are not ignored.

If so, it would be useful to add to http://wiki.tinycorelinux.net/wiki:bootlocal.sh_and_shutdown.sh something to the effect that those 3 files shall always be templates.

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11576
Re: bootsync.sh, bootlocal.sh, and shutdown.sh: always for user?
« Reply #1 on: September 04, 2011, 09:07:30 AM »
Hi genec
Those files actually do something very useful. By providing an access point to the boot up and
shutdown process they greatly reduce the temptation to modify the system boot and shutdown
scripts.

Quote
always remain for the user (as opposed to distro/extension authors; end user or remastering user)
They are there to modify the behavior from the base system. Extension authors sometimes include
instructions to modify those files. You as an end user or in re-mastering are free to change them too.
I'm not sure what you mean by  "user as opposed to end user".


Offline genec

  • Full Member
  • ***
  • Posts: 240
Re: bootsync.sh, bootlocal.sh, and shutdown.sh: always for user?
« Reply #2 on: September 04, 2011, 09:23:57 AM »
I'm not sure what you mean by  "user as opposed to end user".

I'm sorry I was unclear.  User as in end user or remastering user; as opposed to the distro and extension authors.