"About" seems to be not available to me


#1

When I do an update I usually check the result in “about” but It doesn’t work anymore…why is this?


#2

A little more information would be helpful.
What were you on?
What were you updating to?
Did the update actually work?
Output of the commands:
beadm list
pkg info trident-core
ls -ltr /usr/local/bin | grep -i about


#3

I was on U6 modified enough to make it viable and updating to U7.

The following was the result from commands…

beadm list

BE Active Mountpoint Space Created
initial - - 1.8G 2019-03-03 17:10
2019-3-10-21-22-13 - - 44.6M 2019-03-10 21:07
legacy NR / 4.9G 2019-03-10 21:47
2019-3-14-8-18-16 - - 271.4M 2019-03-14 08:11
root@trident-5217:/usr/home/plumtreed # pkg info trident-core
pkg: no package matching trident-core
ls -ltr /usr/local/bin | grep -i about…no result


#4

Strange: you are now on ‘legacy’, not on the latest update. On reboot you would boot to legacy again.
You can try to activate the latest update (2019-3-14-8-18-16) and reboot.

My solution would be to roll-back to the latest known-good BE (2019-3-10-21-22-13 ??) and let it update again. Or do a fresh install to BE. I like fresh installs. :heart_eyes:


#5

Well legacy is just the name of the BE, so it could be anything, but good eye @martl.
The fact that pkg info trident-core says “no matching” is the root cause of no about command.
The question is “Why no trident-core”? Event if it there was no change between U6 and U7, you would have it on the system in the new BE.
Based on the timestamps in the beadm list command I think 2019-3-14-8-18-16 - - 271.4M 2019-03-14 08:11 is the one you want to be in.
You can do:
beadm activate 2019-3-14-8-18-16 and reboot to boot into it.

But before you do, if you are still in “legacy”, what’s the output of this command:
uname -a

That gives a bunch of information about the kernel version running and will give us a hint as to what “legacy” is.

One thing I’ve started doing with the updates and BE’s is renaming them.
There is a “beadm rename” command that will let you rename existing BEs.
sysup -update -bename whatever
will do the update and rename the new BE “whatever”

I’ve been using the string for “OS” in the about command so my BE’s are named like this:
18.12-RELEASE-U6

It makes more sense to me than just the timestamp.

So @plumtreed how about the output of “uname -a” and then use beadm activate 2019-3-14-8-18-16 and reboot to see if you wind up in U7.


#6

uname -a gives me

FreeBSD trident-5217 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC-NODEBUG amd64


#7

Hmm. I think that is the correct kernel version, so it looks like your update to U7 went bad.
Run out of disk space maybe?

I’d try the beadm activate and reboot and see where you are.


#8

type the following commands and post here

df -h

beadm list


#9

Command replies:
df -h

Filesystem Size Used Avail Capacity Mounted on
trident/ROOT/legacy 12G 3.0G 8.7G 26% /
devfs 1.0K 1.0K 0B 100% /dev
tmpfs 834M 460K 834M 0% /libexec/rc/init.d
trident/tmp 8.7G 416K 8.7G 0% /tmp
trident/usr/home 8.8G 97M 8.7G 1% /usr/home
trident/usr/jails 8.7G 88K 8.7G 0% /usr/jails
trident/usr/obj 8.7G 88K 8.7G 0% /usr/obj
trident/usr/ports 8.7G 88K 8.7G 0% /usr/ports
trident/usr/src 8.7G 88K 8.7G 0% /usr/src
trident/var/audit 8.7G 88K 8.7G 0% /var/audit
trident/var/log 8.7G 852K 8.7G 0% /var/log
trident/var/mail 8.7G 112K 8.7G 0% /var/mail
trident/var/tmp 8.7G 100K 8.7G 0% /var/tmp
map -hosts 0B 0B 0B 100% /net
map -automount 0B 0B 0B 100% /.autofs

beadm list

BE Active Mountpoint Space Created
initial - - 1.8G 2019-03-03 17:10
2019-3-10-21-22-13 - - 44.6M 2019-03-10 21:07
legacy NR / 4.9G 2019-03-10 21:47
2019-3-14-8-18-16 - - 271.4M 2019-03-14 08:11


#10

Ok, lets try activating what looks like the last BE created/installed.
It’s named “2019-3-14-8-18-16” and was created 2019-03-14 08:11
The command to do that should be:
beadm activate 2019-3-14-8-18-16

After doing that, do beadm list and you should see the “R” in the second column move from “legacy” to “2019-3-14-8-18-16”. “R” means “this is the BE that will be active on the next REBOOT” “N” means “This is the BE that is active NOW”

If that all matches, then reboot the system and see where you are.


#11

I’m back on the ‘legacy’ which seems to be the one that works…when I boot into BE I get (1 of 4) which is probably 2019-3-14-8-18-16 and doesn’t work(all hell breaks loose)…(2 of 4) which is the one that works and I am on now.

what does this progression refer to…and whereis the ‘about’ command?


#12

type -> uname -a <- post

beadm list < and post


#13

As requested…uname -a
FreeBSD trident-5217 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC-NODEBUG amd64

beadm list
BE Active Mountpoint Space Created
initial - - 1.8G 2019-03-03 17:10
2019-3-10-21-22-13 - - 44.6M 2019-03-10 21:07
legacy N / 56.0M 2019-03-10 21:47
2019-3-14-8-18-16 R - 5.2G 2019-03-14 08:11


#14

What is needed is a sysup - protocol. I don’t know if sysup writes one (question to the devs) but without it it would not be possible to find out what happend, my guess. Finally it will not be possible to repair it but by doing a new update/install.


#15

Since trident core seemed to be missing i added it from the app cafe and I can now use ‘about’ which also says I am on U6.

So while I’m on legacy & U6 I should work out why I am not on U7?

…perhaps I should mark this as ‘solved’, after all that was my original question:(


#16

I would doubt. Maybe something else is missing too. But OK, doubting is my fault.

So you are on U6 and it will ask soon to update to U7. I would do a ‘FULL’ update then.


#17

Well, I did a simple update from U6 to U7. All is well.
Just sayin’.


#18

Me too - but my starting point wasn’t a rotten OS.


#19
Because you removed trident-core when you removed drm-current to
install drm-legacy.
John
groenveld@acm.org

#20

Thanks John, I realise that now…when I found I could install it from the ‘App cafe’