Solved Re-installation of ports and packages after upgrading 10.0 to 10.1

Status
Not open for further replies.
O

obsigna

Profile disabled
I just finished upgrading one of my servers from 10.0-RELEASE to 10.1-RELEASE using freebsd-update -r 10.1 upgrade. Everything went smooth, except when merging the settings, vi(1) was entered, and since I never got used to using vi (and I never will), I needed to hard-reset the server, I got no idea how to leave vi otherwise. My fault, on this server I forgot to change in .cshrc:

Code: 
...
setenv  EDITOR  nano
...

I started over again freebsd-update -r 10.1 upgrade, and upgrading finished without any problems now. In the moment, a few number of ports are in the course of rebuilding as suggested by the Handbook.

My question is about the binary packages, do I need to reinstall these too? If yes, what would be the appropriate command?
 
Ports/packages only need to be rebuilt or reinstalled when the ABI changes, i.e. between major versions (e.g. 9 -> 10). There's nothing against doing it between minor versions, but it won't give you any advantages. For packages pkg upgrade -fy works fine.
 
obsigna said:
vi(1) was entered, and since I never got used to using vi (and I never will), I needed to hard-reset the server, I got no idea how to leave vi otherwise.
Click to expand...
At least learn one command, and remember it well. To exit vi(1) press escape a couple of times, then enter :q. That will quit vi without saving it. If you accidentally made changes use :q! to quit without saving.
 
Other than that, [Esc] followed by :help will give you access to more help.
 
DutchDaemon said:
Ports/packages only need to be rebuilt or reinstalled when the ABI changes, i.e. between major version (e.g. 9 -> 10). There's nothing against doing it between minor versions, but it won't give you any advantages. For packages pkg upgrade -fy works fine.
Click to expand...

OK, many thanks for the clarification. I felt that I overlooked something, namely the tiny detail that this upgrade was a minor and not a major one. Your answer will help me anyway, because I got another server to be upgraded from 9.3 to 10.1.
 
SirDice said:
At least learn one command, and remember it well. To exit vi(1) press escape a couple of times, then enter :q. That will quit vi without saving it. If you accidentally made changes use :q! to quit without saving.
Click to expand...
I am getting old. I remember only that the last time (more than 2 years ago) when I was forced into vi, I somehow managed to exit it the regular way, but today I forgot again how, and by getting older I finally lost also the patience for finding it out again and again. Sorry, vi is definitely not made for me -- I know, that's my fault.
 
No worries, it certainly isn't the most user friendly editor and it has a rather steep learning curve. Even after a couple of years of forcing myself to use it, I still only know the most basic editing commands. But it's enough for me to get by.
 
obsigna said:
I am getting old.
Click to expand...
It can also be the other way around. It might be completely off-topic, so I would not complain if this reply would be deleted by the moderators without notice.
Last weekend I have had to replace a dying disk with some non-FreeBSD installation. This is basically no problem, copy the stuff and edit the UUIDs in /etc/fstab. So launch blkid or so, append the output to /etc/fstab and edit the file. No problem, every rescue CD provides vi. At least this has been my experience in the past. Not this ****** disk. I thought ok, it might be the real hard one, it is ed, not comfortable to use, you see just one line of text and so on. But it is not impossible not to corrupt a file by using ed.

Finally nano was the only available editor. Maybe it has been more loud here than it should have been. I think vi is by far more user friendly than nano.

I think I am getting old as well.
 
chrbr said:
...
Finally nano was the only available editor. May be it has been more loud here than it should have been. I think vi is by far more user friendly than nano.
I think I am getting old as well.
Click to expand...

My problem with vi is that it doesn't supply any decent hint on what should be done once you were trapped-in.
nano shows a menu and ^X Exit is one of its prominent items. The FreeBSD base system comes with ee(1) -- easy editor, which also shows a menu. nano and ee might well not be as powerful as vi, however, the occasional user could easily survive and get the job done with ee or nano, while occasional users will be completely f****d-off by vi.

IMHO, it would be much more friendly for the non-power-users to change the default EDITOR in .cshrc from vi to ee.
 
Status
Not open for further replies.
Back
Top