pkg_upgrade -a -C
fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: File unavailable (e.g., file not found, no access)ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-current/BRANCH=9-current===>>> Checking package repository for latest available version
===>>> Package and/or archive not found at:
http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.0-release/audio/
Sure, like when he says,oliverh said:
There have been times when STABLE is, well, stable and there have been times when I really wished I had spent more time reading the stable/current lists before upgrading. To each his own. I just posted to share my experience in case it helps others. In '97 I needed to share a dsl connection with my roommates, so I tried IP masquerading with linux. A friend suggested NAT on FreeBSD might work better. We had a 286 running 2.something (I think) and it ran without problems for the entire year. I don't think I've installed a linux distribution since.
So, my only advice is to do your research and don't blindly upgrade if there isn't a good reason.
Welcome mate.bbzz said:
bbzz said:
Good point, if pkg_upgrade hasn't found anything, then why would portmaster?bbzz said:
purgatori said:
This will be solved by PKGNG project, take a look here: http://youtu.be/IRa6wFBLU28purgatori said:
I do not remember any 'mine' problems with binary FreeBSD update, but I 'walked' that road: 5.4 -> 6.0 -> 6.1 -> 6.2 -> 7.0 -> 7.1 without any problems by doing source upgrades (make buildworld ...)purgatori said:
Its probably the longest HOWTO I have ever written, but maybe because I wanted to explain all the steps and the 'why that way' behind them, seems pretty simple after several tries, try it under clean machine in VirtualBox first to catch some confidence.purgatori said:
Its definitely not my problem, but I would at least suggest keeping open eye on FreeBSD Security Advisories and patching when needed, along with portaudit from Ports.purgatori said:
Thats very easy to accomplish, make a list of Your installed packages, then remove all installed packages, then install them again from the list You have just made, like that:purgatori said:
# pkg_info -qoa > LIST
# pkg_delete -a
# rm -r -f /var/db/pkg /usr/local
# while read I; do pkg_add -r $( basename ${I} ); done < LIST# pkg_info -qoa > LIST
# pkg_delete -a
# rm -r -f /var/db/pkg /usr/local
# sh
# while read I; do pkg_add -r $( basename ${I} ); done < LISTIt may sound up like an advertising, but using methods described in this HOWTO solves that problem, packages are built every 2 weeks, and if newer version appears, its installed.purgatori said:
FreeBSD lacks a lot in serious clustering, like 3+ nodes sharing many resource groups with their services, a shared clustering filesystem, drivers for various Fibre Channel controllers etc, but that is a topic for long discussion on another threadpurgatori said:
vermaden said:
vermaden said:
apt-get update
apt-get upgradevermaden said:
vermaden said:
I suppose I'm evaluating things more from a desktop-users perspective. My activities on FreeBSD basically consist of: editing/proofreading documents in Emacs (which is as much my operating system as FreeBSD is ), writing LaTeX documents, running statistics & generating graphics in R, browsing the web/gopher, and watching videos/listening to music. For all of these activities, I find FreeBSD to perform admirably and with rock-solid stability -- and all on rather ancient hardware. But, as you rightly say, that's the topic of another discussion.purgatori said:Waaaaaay outta my depth, I'm afraid
Welcome.purgatori said:First off, thanks for your thorough reply vermaden
The good thing about FreeBSD, is when You learn something, that knowledge/experience very rarely outdates, with Linux You need to 'update Your knowledge' every release and as someone stated here, its often a lot different 'procedure' to achieve the same thing in, for example, RHEL 4.x, 5.x and 6.x, so You need to learn 3 different procedures, in FreeBSD, its just one.purgatori said:Despite its reputation, I don't think FreeBSD is terribly difficult to learn and use, even if you're not a computing boffin; that is, with the exception of package management. It would be nice if *that* was a little more idiot-proof, so to speak
purgatori said:
# ports-check
# ports-updatepurgatori said:Waaaaaay outta my depth, I'm afraid
vand777 said:
vermaden said:
I forgot about 'Ubuntu problems' as I havent used that distribution since quite long time, 2008 maybe, but Ubuntu changes seem to be much frequent then UpstreamVendor/CentOS ones, it must be a horror to keep up with all thos changespurgatori said:Tragically true. I remember moving between releases back when I was using Ubuntu, and how there was always some new back-end or protocol succeeding another. Not only would you have to learn how to use it, but it often provided no benefit, and more often than not just broke everything: PulseAudio being a great example. System configuration also seemed to be increasingly opaque with each release; there were less human readable configuration files, and more arcane, semi-functional GUI-mediated rituals
Besides the need to disable SELinux and that its still Linux and the need to always add all these various additional repositories that provide me the packages that I have at FreeBSD from the start, its not that bad, at least comparing to other Linux distributionspurgatori said:
Good to know that there are more people like me, I am a big fan of Fallout series, but definitely pre-Bethesda ones, I would even say pre-Tactics onespurgatori said:I notice we're also both fans of Fallout/Bethesda games, and have similar views on religion
vermaden said:
[root@BSD ~]# ports-check
bash: ports-check: command not found
[root@BSD ~]# ports-audit
bash: ports-audit: command not found