Upgrading FreeBSD 8.3 amd64

Ralf Mardorf ralf.mardorf at rocketmail.com
Sun Dec 23 23:39:58 UTC 2012


I've done the upgrade yesterday. It was a clean 8.3 install, I only set
up PPPoE and then run the following commands.

# cd /usr/ports/misc/mc && make install clean
# uname -r
# freebsd-update -r 9.1-RELEASE upgrade
# freebsd-update install
# shutdown -r now

# freebsd-update install
# cd /usr/ports/ports-mgmt/portupgrade && make install clean
# /usr/local/sbin/portupgrade -f ruby
# rm /var/db/pkg/pkgdb.db
# /usr/local/sbin/portupgrade -f ruby18-bdb
# rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db
# /usr/local/sbin/portupgrade -af
# freebsd-update install
# shutdown -r now

# freebsd-update IDS >> outfile.ids

This is the content of outfile.ids:

Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
/boot/kernel/linker.hints has SHA256 hash ebf78144f48f13af88e5e3752735a709b084d7e6aaee10b05e57f2a117cbc366, but should have SHA256 hash 07b927068b34c4671a323e6a8aaa80ad22dc5fc4b3741b8a4060da1764510350.
/etc/group has SHA256 hash 108de8653d4a6d451cc3f018780277d2fe2d770df7a7d984f5160dc753e06678, but should have SHA256 hash d788718c25a04a14cc1818ac2afa8b76a3fd899583691972d0d5127947e3504f.
/etc/hosts has SHA256 hash 9684014402be7ecd32b9047181f595d124df6cf6a79dd323b0bd5685dccc2a81, but should have SHA256 hash f795387981b68599c3df984f2ce4ac4a32bf420d57faf1fb55f249b885414d64.
/etc/master.passwd has SHA256 hash cd9046284ac3e571eb9f0273f9bfc118e7094e0b9312fd1789f6385e43a26cd3, but should have SHA256 hash 6f1da238cc0a55ed360a215039bc6cb5ce5369d20b8fbceb8a1941c5124e6a4e.
/etc/motd has SHA256 hash fa311ce1a08aea0c818d57b904c979941dabb726d1fb2ddaa368102bd6f2fb95, but should have SHA256 hash 98f082efc89da5e887e72bc4dcfa3e5fc8bada9d19db4bdbba9a32692a7c82a7.
/etc/passwd has SHA256 hash e4bcb10c66a0440efb58591daadaeec894e75e5392da9e00f3881822d0647a11, but should have SHA256 hash 3135de169a0ff94c0c97aeb525a07ea10e5ed81c9b825e219f7eea8deb97c444.
/etc/ppp/ppp.conf has 0755 permissions, but should have 0600 permissions.
/etc/ppp/ppp.conf has SHA256 hash 623683de09ab97394221c64ccdec3569aa240854d907a4811f91c9ed92253dd4, but should have SHA256 hash f3dd3d0da252bd47681a261a1f0d46a8fc6ae84ff3cbd34b81b586bc87e49655.
/etc/pwd.db has SHA256 hash 62eb1eafbfa8fe718e68bf784e542d09ccdc09012ef43d254ae48e9846a1df4d, but should have SHA256 hash bf86739ee052821992412b61a6673811588c382fa63ab38cc47c1a59305376eb.
/etc/shells has SHA256 hash 4c25fb7c79fe5057217a70cfa1c27f41959bb7daa703a94774ec5ac9d29a9266, but should have SHA256 hash beab7e474ee12b051b98889f368bbd490340a908f6f2287f9238e818b830a1fd.
/etc/spwd.db has SHA256 hash b25126503c347feb67b76a5f27f44c318a675ddc82f4984b5ec0d2fc5a45fd30, but should have SHA256 hash 1cbfbea78d316e4e8d29f53f0770b8ff1f3a731e993c3ae717f36304715d7a5b.

When I run "ppp -ddial alice" now, I get warnings "Bad label
in /etc/ppp/ppp.conf (line x) - missing colon", but PPPoE still works.

Why are the checksums bad?

FWIW "snd_hdspe" now is available.


More information about the freebsd-questions mailing list