rpaulo
e824aed9d8
Mention removal of net.inet.tcp.newreno.
2006-10-09 18:57:30 +00:00
bjh21
7e7ad31f07
Mention acorn32 console changes, since they'll break builds with custom
...
kernel configs.
2006-08-15 20:48:01 +00:00
christos
f830640ca4
Mention ACPI PCI interrupt changes (original code from FreeBSD)
2006-07-04 00:40:43 +00:00
dogcow
4ed1c11714
document where and why the socket syscall changed.
2006-06-27 21:14:11 +00:00
christos
4ad5c93d32
more details.
2006-06-02 19:08:00 +00:00
pavel
2aa1e28cea
document that a recent linker is needed to link the i386 and xen kernels
...
after the changes to the ldscript.
2006-06-02 19:01:00 +00:00
martin
7161703c02
Note new sparc64 bootloader requirement.
2006-01-31 22:54:22 +00:00
yamt
a692b5dc5a
note about conf/std.
...
(forgot to commit with conf/std.)
2005-10-03 04:45:52 +00:00
lukem
36476eed8b
Don't mark /etc/namedb/named.conf as "obsolete" since that will cause
...
a file that has end-user configuration to be unconditionally removed.
Instead, remove the entry from the set list, and add a note to UPDATING
reminding users of MKUPDATE=yes to manually rectify the problem in
their DESTDIR.
The "named" fix in postinstall(8) will migrate /etc/namedb/named.conf
to /etc/named.conf if the latter doesn't exist.
(The need for these style of migrations was why I implemented postinstall(8)
in the first place.)
2005-09-14 00:32:26 +00:00
drochner
8d7141beec
mention recent kernel config change,
...
being here, usr.sbin/config -> usr.bin/config where appropriate,
and remove references to egcs
2005-08-25 16:01:14 +00:00
augustss
bf5d559079
It's genassym(1) not genassym(8), and it's in /usr/bin not /usr/sbin.
2005-07-01 09:55:37 +00:00
yamt
2b157dcd40
note about kernfs fix and xentools.
2005-06-03 11:02:59 +00:00
christos
fef1b9e902
Add an entry for genassym.
2005-05-31 18:42:44 +00:00
lukem
8232ca0162
Tweaks for the move of postinstall from /etc to /usr/sbin
2005-04-17 23:12:40 +00:00
cube
7f25e48562
Add a note into 20050325 entry that the speaker might not even play any
...
sound if you don't add an attimer(4) device, as pointed out by Steven M.
Bellovin.
2005-04-11 15:36:46 +00:00
cube
32d34f2595
Add a note about pcppi -> pcppi+attimer.
2005-03-26 14:25:25 +00:00
jmc
28e9ff91f2
Note that configure in some places (binutils is what got me) will abort if
...
the new environment is different than the original configured one (i.e. for
UPDATE=1)
2005-02-11 17:50:13 +00:00
christos
f1e0ce31b6
Mention /etc/pam.d requirement.
2005-01-09 07:31:31 +00:00
christos
6df43d1ef4
mention make lossage
2005-01-06 23:28:56 +00:00
jmmv
f5aed78f0a
Drop duplicate word.
2005-01-04 19:14:00 +00:00
wiz
41b2e9e897
Only delete /dev/bpf[0-9]*, not /dev/bpf too :).
2004-12-02 00:00:11 +00:00
christos
ee20faea65
Mention /dev/bpfX -> /dev/bpf
2004-12-01 23:55:19 +00:00
jmc
2597e77e92
Note the breakage w. 1.35 of var.c in /bin/sh and the need to update /bin/sh
...
before attempting a build
2004-10-12 04:03:20 +00:00
he
1ccc26b661
Complete the list of victims of the IPF relocation by adding ftp-proxy.
2004-10-02 16:24:32 +00:00
christos
dc8336fa20
say what breaks now that we've moved ipf out of netinet.
2004-10-01 15:29:23 +00:00
lukem
7a69732f67
postinstall currently does not migrate /usr/X11R6/lib/X11/* -> /etc/X11/*
2004-08-15 16:02:59 +00:00
atatat
5276b9840f
Note the sendmail auto-start change, add a note about the ath
...
reworking, and fix a little spacing and unnecessary abbreviation.
2004-07-22 03:55:33 +00:00
jmc
af447bac3f
Include notes about purging most of tools/* before building to get correctly
...
generated yacc/lex output files from new bsd.hostprog.mk
2004-06-22 01:29:51 +00:00
jmc
cde4553cd9
Add suggested wording from PR#24654 to reference BUILDING and build.sh as
...
the first place one should go when building.
2004-06-13 08:08:43 +00:00
itojun
d28d146fa1
sysctl update: describe failure case.
2004-05-31 00:18:58 +00:00
lukem
c1f9391e92
src/x11 stuff after the /etc/X11 change
2004-05-16 11:33:44 +00:00
atatat
f217667991
You also need a new libc for the new sysctl binary to work.
2004-05-03 04:12:21 +00:00
atatat
b0004c2157
Note the change to the sysctl machinery, and how to rebootstrap
...
yourself if both your boots appear to have fallen off.
2004-05-03 03:57:15 +00:00
dbj
0dab748521
mention the fixsb script and updated information on botched superblock
...
upgrade issues
2004-04-25 21:16:57 +00:00
jmc
d01e0e4fa1
Typo police
2004-04-23 19:44:47 +00:00
christos
9be64e49b4
be more specific about what to cleanup.
2004-04-23 15:07:31 +00:00
christos
68b4d0866c
Mention statvfs pitfalls.
2004-04-22 14:35:55 +00:00
jmc
34fda5691a
Note need for latest bsd.files.mk now wrt athhal-elf.o
2004-03-26 17:48:13 +00:00
dan
e98f1f3c17
Note cgd blowfish changes, see comments in sys/dev/cgd.c 1.15 for more
...
details.
2004-03-18 11:03:57 +00:00
keihan
ca3871791b
s/netbsd.org/NetBSD.org/
2004-03-16 14:33:03 +00:00
simonb
de37ce0135
Use tabs consistently at the start of lines.
2004-03-14 21:08:10 +00:00
dbj
6f51d6ea03
update information about the botched superblock messages
2004-03-14 14:56:47 +00:00
dbj
16def41342
update information about the botched superblock messages
2004-03-14 14:56:00 +00:00
bjh21
402ecd3c7b
Mention required kernel config change caused by death of busmouse(4)
...
on acorn32.
2004-03-13 20:03:52 +00:00
reinoud
1d654e444e
It wasn't stated that with the superblock problems that were fixed before
...
it is also needed to update fsck_ffs or it will keep on bugging.
2004-02-23 22:51:51 +00:00
bjh21
a64b6f36a8
Mention removal of "beep" alongside "sysbeep".
2004-01-25 14:13:08 +00:00
bjh21
ef6393dd75
Mention acorn32 sysbeep removal, since it needs a kernel config file change.
2004-01-18 12:52:47 +00:00
dbj
51134cc5dd
change the updating note to say you may need fsck_ffs -b 32 -c 4'
2004-01-12 16:19:19 +00:00
dbj
a0d8cc6467
change fsck to fsck_ffs in 20040109 updating note
2004-01-12 05:01:22 +00:00
dbj
b4c4fbb551
add fsck compatibility notes
...
20040109:
Compatibility for old ffs superblock layouts has been
added, and the restrictive fsck checks have been reenabled
when using those layouts. If you have been using -current
since 20030402, you may find that fsck again signals fatal
superblock mismatches. To work around, you can use
fsck -b 32 to restore an alternate superblock.
2004-01-09 19:36:28 +00:00