The -n option in the wr_date tool is used for a dry run. It execute the
code without applying changes in the system and the hardware.
However calling "wr_date -n set host" was not setting the date but
applying the TAI offset. To make things more consistant, a new option
has been added. Calling "wr_date set host tai" now sets only the TAI
offset.
The wr_date script has been changed to take into account this
modification of the behavior.

1/ wr_date script:
- Started before PPSi
- Set number of NTP retries to 10 if GM otherwise 1. GM info is
extracted from dot-config
- Clock source is controlled directly with wr_date tool
- Can be started any time without any risk to set a wrong date (see
point 2)
2/ wr_date
- 'set host' parameters take into account the time mode ( FR: set
sec+ns, BC: time cannot be set, GM: set seconds only+wait to be in a
middle of a second)
- function substrat_substrat() moved to time_lib.h. Also used by wr_mon
3/ wr_mon
- Print TAI-UTC
- Update Timing Mode & PLL locking state displayed values

- Check if we are in GM mode, if yes :
    - wait GM to be locked
    - Disable WR as kernel clock source
    - Increase retries for NTP
- Retries x time NTP until setting host time:
    - Set date from host to WR
    - Enable (back) WR as kernel clock source

Fix TAI offset into kernel was done withing get function but this has
been removed in commit #91f4c8d. As it is still needed by slave, we
force its use using -n option. This will only fix tai offset into kernel
without applying ToD to WR/FPGA time.

Conflicts:
	userspace/tools/wr_date.c

Keep created wr_date.conf in /etc not in /wr/etc.
There is no need to keep it in the flash instead of ramdisk.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Move:
/etc/init.d/[SK]??<name> to /etc/init.d/<name>
Then create symlinks in
/etc/init.d/rcS/[SK]??* to all files that previously were /etc/init.d/[SK]??*
With exception of monit since monit will start soon from init.

Rename all occurences of changed files.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Date was never restored due to wrong filename in /etc/init.d/S70wr_date
Use saved_date instead of update_date
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

--add running all /etc/init.d/K* scripts before restart
--add /etc/init.d/K90time_save.sh script to save current date
--set saved date in case date cannot be received from ntp
--update developer manual
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Also, run "wr_date get" at boot once, so it parses leap-seconds.list
and configures the kernel for the proper tai_offset.

With the previous commit it worked with "wr_date get tohost",
becase after the host is correctly in 2014 or so, all leap seconds are
in the past.  But if we are not synced, the host is in 1970 and
no leap second has already happened.

If this code is unchanged in 2018, we'd better be off by 2 seconds
than 37, so if linux reports a date earlier than 2014, use 2014 and
fix tai_offset at 35.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>