root@DELL:~ # freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 11.0-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
No updates needed to update system to 11.0-RELEASE-p8.
WARNING: FreeBSD 11.0-RELEASE-p8 is approaching its End-of-Life date.
It is strongly recommended that you upgrade to a newer
release within the next 2 months.
Ha-ha, so now that's why it just occurred to me today that it would not hurt to make a fresh install... from STABLE. Related to some strange problems I'm experiencing, but seems to fit in well with this other stuff here.
open as administrator
working, though I also reinstalled caja-extensions of which all other functions were working fine, exept for open as administrator
Yes, it definitely is Xorg seg fault, seems to be caused by /lib/libthr.so, this is clearly seem withMeantime I've built STABLE (as of yesterday) and installed it into a new root. Installed all my synth prebuilt packages into that system and -- previously built xorg-server segfaults. Or is it x11/nvidia-driver? Anyway, startx command I normally use to start my fvwm2 session resuits in system reboot.
Xorg -configure
command.Sorry, I am a newbie. But do you mean that when I doYes, it definitely is Xorg seg fault, seems to be caused by /lib/libthr.so, this is clearly seem withXorg -configure
command.
In addition to the above I can only add that I've rebuilt all the packages under STABLE, just for the purity sake. The same thing.
Xorg -configure
and I get the message Server is already active for display 0
that this is caused by the segmentation fault? If so, is there a solution to fix this?In my Mate environment Caja uninstalled itself just like that, and also a rollback of a recent snapshot did not reinstate Caja.
Xorg -configure
(or any other) you see on your screen something similar to this:1 segfault 0x000000010d0a99d0 _Z10catchCrashi + 16
2 libsystem_c.dylib 0x00007fff99b5dcfa _sigtramp + 26
3 ??? 0x00007fff00000000 0x0 + 140733193388032
4 segfault 0x000000010d0a9c67 _ZN7Crasher11doSomethingEv + 71
5 segfault 0x000000010d0a9880 _Z5crashPv + 32
6 segfault 0x000000010d0a9ac7 _Z7goCrashv + 199
7 segfault 0x000000010d0a9b33 main + 67
8 segfault 0x000000010d0a9854 start + 52
...
Xorg has stopped working due to segmentation fault.
freebsd-update fetch
, like every few days, today got this message: freebsd-update -r 11.0-RELEASE upgrade
(cannot upgrade to itself); more surprisingly, I can not do freebsd-update -r 11.0-RELEASE-p8 upgrade
either, although that version does seem to exist in the wild (judging by mentions on web searches). Signed: confused.You need to runOK, I'm still running 11.0-RELEASE-p1. Ran freebsd-update fetch, like every few days, today got this message
freebsd-update install
to install the fetched files.This thread is about 11.0-RELEASE (patch level 8), which was apparently approaching EoL, but isn't anymore after all.but is this new release
What's the "actual BSD"?the release of BSD... as in the actual BSD
I'm pretty new to this BSD community, only since, September 28th 2015.
I'm probably interpreting everything wrong here, but is this new release, the release of BSD... as in the actual BSD. Hopefully this will make some sense to everyone...
freebsd-update fetch
. I'm not usually always logged into my server, so it would be nice if there were a website or rss feed or announcement list or even a twitter account that I could follow for when this is updated.https://www.freebsd.org/security/advisories.htmlI'm not usually always logged into my server, so it would be nice if there were a website or rss feed or announcement list or even a twitter account that I could follow for when this is updated.
https://www.freebsd.org/security/advisories.html
https://www.freebsd.org/security/notices.html
You can also join the freebsd-announce mailing list.
To what? There's no newer release. It's still a long way off to 11.1 and until then 11.0 is a supported version.So, do I actually need to consider upgrading from 11.0-RELEASE now?
To what? There's no newer release. It's still a long way off to 11.1 and until then 11.0 is a supported version.