My procedure to upgrade to 14.0-RC3

Alain De Vos

Alain De Vos

What i did, i downloaded the kernel.tgz & base.tgz.
And i simply untarred them , tar xfvz in /
Everything works fine.
But is this a good procedure ?
 
Alain De Vos said:
What i did, i downloaded the kernel.tgz & base.tgz.
And i simply untarred them , tar xfvz in /
Everything works fine.
But is this a good procedure ?
Click to expand...
it should be fine as long as you did install a boot loader, make sure that you create the users and do post install carefully
 
wouldn't untarring base to root overwrite any changes you made to base files in /etc (passwd, group, etc)? wouldn't work for me but maybe it does for you?
 
Alain De Vos said:
What i did, i downloaded the kernel.tgz & base.tgz.
And i simply untarred them , tar xfvz in /
Everything works fine.
But is this a good procedure ?
Click to expand...

No. If you didn't use the v (verbose) option you'd more clearly see this:

Code: 
./var/empty/: Can't restore time: Operation not permitted
./sbin/init: Can't unlink already-existing object: Operation not permitted
./lib/libc.so.7: Can't unlink already-existing object: Operation not permitted
./lib/librt.so.1: Can't unlink already-existing object: Operation not permitted
./lib/libthr.so.3: Can't unlink already-existing object: Operation not permitted
./lib/libcrypt.so.5: Can't unlink already-existing object: Operation not permitted
./libexec/ld-elf.so.1: Can't unlink already-existing object: Operation not permitted
./libexec/ld-elf32.so.1: Can't unlink already-existing object: Operation not permitted
./usr/bin/su: Can't unlink already-existing object: Operation not permitted
./usr/bin/login: Can't unlink already-existing object: Operation not permitted
./usr/bin/chpass: Can't unlink already-existing object: Operation not permitted
./usr/bin/passwd: Can't unlink already-existing object: Operation not permitted
./usr/bin/crontab: Can't unlink already-existing object: Operation not permitted
tar: Error exit delayed from previous errors.
Meaning these files didn't get updated.

cracauer@ said:
I exclude /etc from the untar.
Click to expand...

This can also bite you, if some files in /etc are updated.
 
What I end up doing some time is quite clunky but doesn't leave a zillion update files in /var/db/freebsd-update/ directory! Something like:

Code: 
mdconfig -a -t vnode -f FreeBSD-14.0-RC4-amd64-mini-memstick.img
mount -r /dev/md0s2a /mnt
cd /mnt
find . -flags schg > /tmp/schg-files
(cd / ; xargs < /tmp/schg-files chflags noschg)
<do a careful update using rsync>
<fix up etc files>
(cd / ; xargs < /tmp/schg-files chflags schg)
cd
umount /mnt
mdconfig -d -u 0

Usually I just build kernel+world locally and install that but I like to keep around one VM that is tracking the latest official release and release candidates.
 
bakul said:
No. If you didn't use the v (verbose) option you'd more clearly see this:

./var/empty/: Can't restore time: Operation not permitted
./sbin/init: Can't unlink already-existing object: Operation not permitted
./lib/libc.so.7: Can't unlink already-existing object: Operation not permitted
./lib/librt.so.1: Can't unlink already-existing object: Operation not permitted
./lib/libthr.so.3: Can't unlink already-existing object: Operation not permitted
./lib/libcrypt.so.5: Can't unlink already-existing object: Operation not permitted
./libexec/ld-elf.so.1: Can't unlink already-existing object: Operation not permitted
./libexec/ld-elf32.so.1: Can't unlink already-existing object: Operation not permitted
./usr/bin/su: Can't unlink already-existing object: Operation not permitted
./usr/bin/login: Can't unlink already-existing object: Operation not permitted
./usr/bin/chpass: Can't unlink already-existing object: Operation not permitted
./usr/bin/passwd: Can't unlink already-existing object: Operation not permitted
./usr/bin/crontab: Can't unlink already-existing object: Operation not permitted
tar: Error exit delayed from previous errors.

Meaning these files didn't get updated.



This can also bite you, if some files in /etc are updated.
Click to expand...
I do a "chflags -R noschg / ", to avoid this. This is just because of "old and stupid flags", which give a bad feeling of "security".
 
You must log in or register to reply here.
Back
Top