on startup
- create share/examples/wpa_supplicant/wpa_supplicant.conf and make it
known in the relevant places. Improvements welcome, my point was
ctrl_interface and "you seriously want this"
it to trigger in 1/4 of the builds with -j 40 on a 24 processor box. Typical
error is:
ln: machine/include: File exists
*** Failed target: .BEGIN
*** Failed command: rm -f machine && ln -s /p/netbsd/cvsroot/src/sys/arch/vax/include machine
*** Error code 1
Stop.
Another approach to fixing this is to create a lockfile or adding other flags
to ln to change its behavior.
bsd.sys.mk and bsd.own.mk
- Add protection requiring that:
1. bsd.sys.mk is not include from other Makefiles directly
2. bsd.own.mk must be included before bsd.sys.mk since it
sets variables that bsd.sys.mk uses as conditionals.
This is step 1 of removing all variable settings from bsd.sys.mk and
leaving behind only rules. This way, the structure of a standard Makefile
is:
variable overrides
optionally include bsd.own.mk
optionally include bsd.endian.mk
variable settings that use variables defined in bsd.own.mk
include a one or more rule .mk files (such as bsd.prog.mk etc)
This file is only intended to be included from the other rules files like
bsd.lib.mk or bsd.prog.mk. If you need things to be defined early, use
bsd.own.mk.
relative to uname output when running in emulations: the magic links
are *not* affected even though uname output changes.
(This means @machine magic links can be used for e.g. amd64 vs. i386
device nodes. There's also an @emul magic link for emulation.)
Noted by apb.
since there is no definition of CRYPTO_ALGORITHM_ALL!
XXX The description of the arguments for crypto_register() needs further
updates, too, but that will be left for another day.
Major changes from tzdata2013d to tzdata2013e:
Fiji (Pacific/Fiji) DST in 2013 starts on October 27, not October 20.
Several zones have been turned into links, either to correct errors,
or where the differences were in older data (before 1943) that was
thought to be unreliable.
Some time zone abbreviations have been changed.
Major changes from tzdata2013e to tzdata2013f:
Tocantins, Brazil (America/Araguaina) DST will not start in September
2013.
Jordan (Asia/Amman) moves to permanent UTC+3 (instead of UTC+2 with
permanent DST since 2012).
Palestine (Asia/Hebron and Asia/Gaza) will end DST at 00:00, not
01:00, as from September 2013.
Major changes from tzdata2013f to tzdata2013g:
Morocco (Africa/Casablanca) now observes DST from the last Sunday
in March to the last Sunday in October, not April to September.
respectively.
Major changes from tzdata2013g to tzdata2013h:
Libya (Africa/Tripoli) has switched its time zone back to UTC+2
without DST, instead of UTC+1 with DST.
Western Sahara (Africa/El_Aaiun) uses Morocco's DST rules.
Acre, Brazil (America/Rio_Branco) and (we guess) western Amazonas,
Brazil (America/Eirunepe), will switch from UTC-4 to UTC-5 on
2013-11-10.
Add entries for DST transitions in Morocco in the year 2038. This
avoids some year-2038 glitches introduced in 2013g.
Major changes from tzdata2013h to tzdata2013i:
Jordan (Asia/Amman) switches back to UTC+2 standard time at 00:00 on
December 20, 2013. The 2006-2011 DST transition schedule is planned
to resume in 2014. The switch to permanent UTC+3 is cancelled.
In 2004, Cuba (America/Havana) began DST on March 28, not April 4.
The files solar87, solar88, and solar89 are no longer distributed.
The zones built from those files (Asia/Riyadh{87,88,89}) and
Mideast/Riyadh{87,88,89}) are no longer installed. They were a
negative experiment -- that is, a demonstration that tz data can
represent solar time only with some difficulty and error. Their
presence in the distribution caused confusion, as Riyadh civil time
was generally not solar time in those years.
