Catchup from my holiday lull:
o libcrypt not a symlink. o hw.sndunit -> hw.snd.unit o burncd / kernel changes o I386_CPU now mutually exclusive with all other CPU types.
This commit is contained in:
parent
a07736d0f6
commit
aac7dfeae8
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=71171
17
UPDATING
17
UPDATING
@ -5,6 +5,18 @@ directly to him. See end of file for further details. For commonly
|
|||||||
done items, please see the end of the file. Search for 'COMMON
|
done items, please see the end of the file. Search for 'COMMON
|
||||||
ITEMS:'
|
ITEMS:'
|
||||||
|
|
||||||
|
20010116:
|
||||||
|
The kerrnel option I386_CPU is now mutually exclusive with the
|
||||||
|
other cpu types. If you have an i386 system, be sure that it
|
||||||
|
only had this line. Remove it for all other configurations.
|
||||||
|
|
||||||
|
20010110:
|
||||||
|
Changes to the kernel require it and burncd be in sync.
|
||||||
|
|
||||||
|
20010102:
|
||||||
|
Everyone who has hw.sndunit set to something in
|
||||||
|
/etc/sysctl.conf, it is now hw.snd.unit.
|
||||||
|
|
||||||
20010101:
|
20010101:
|
||||||
ex and vi were broken by some changes to sys/queue.h. If you
|
ex and vi were broken by some changes to sys/queue.h. If you
|
||||||
have a bad vi, you will see make buildworld fail with a core
|
have a bad vi, you will see make buildworld fail with a core
|
||||||
@ -18,6 +30,11 @@ ITEMS:'
|
|||||||
vi/ex is dynamically linked, but I've not received any reports
|
vi/ex is dynamically linked, but I've not received any reports
|
||||||
of this working.
|
of this working.
|
||||||
|
|
||||||
|
20001228:
|
||||||
|
There have been some changes to libcrypt in -current. The
|
||||||
|
libscrypt/libdescrypt symlink sillyness is gone and the installed
|
||||||
|
libcrypt is fully functional. Be aware of this.
|
||||||
|
|
||||||
20001218:
|
20001218:
|
||||||
Linksys Fast Ethernet PCCARD cards supported by the ed driver
|
Linksys Fast Ethernet PCCARD cards supported by the ed driver
|
||||||
now require the addition of flag 0x80000 to their config line
|
now require the addition of flag 0x80000 to their config line
|
||||||
|
Loading…
Reference in New Issue
Block a user