WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Startup script vs. restore  (Read 2045 times)

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Startup script vs. restore
« on: November 21, 2009, 07:02:05 AM »
Startup scripts executed before backuped data restored. This means, that for example WICD auto connection script do not see saved settings and it has to be added to bootlocal.sh Changing the order to

1) load extensions
2) restore backup
3) run startup scripts

would solve the problem and would eliminate extra configuration step. There may be an impact on certain extensions theoretically, but I do not have a real case. Also making restored data available earlier would narrow the gap between different installation types.
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline mikshaw

  • Sr. Member
  • ****
  • Posts: 368
Re: Startup script vs. restore
« Reply #1 on: November 21, 2009, 09:32:00 AM »
I think it was done this way to prevent startup scripts from interfering with your personal dynamic files.  As I see it,  the backup is there to override the potential effects of all static content (base system and extensions).  If you have something static in your backup that needs to be in place before the scripts run, you can make an extension of it.