Re: Upgrading packages - portupgrade confusion
Thanks Warren and Michael! :-)
On Sun, 12 Sep 2010, Kaya Saman wrote:
The thing I don't quite understand though is that if the ports tree
gets refreshed, do the packages get upgraded or will I need to rebuild
them??
The ports tree is just build instructions, so updating it doesn't update
any installed applications. It does let you use a program to see which
installed applications need to be updated, like pkg_version or
portversion.
Here's a document I've been working on lately about upgrading ports.
I'm not sure it's really there yet, but it covers the basics:
http://www.wonkity.com/~wblock/docs/html/portupgrade.html
Yep I kinda figured that before even posting and also I knew the
difference between packages built by pkg_add and compiling fresh from
ports since I've done a few BSD builds now but the really iffy thing was
a: communication - which let me down not explaining myself properly and
b: confusion of how to update
On 09/12/2010 05:36 PM, Michael Powell wrote:
[...]
Yes. A package is just a port that someone has compiled into a pre-built
binary package for use with pkg_add. These binary packages are placed on ftp
servers where pkg_add may download from and install.
A port is just you doing the compiling locally yourself using the ports
system. The installed result is the same, except for one thing. When a
package is built some build options may have been selected as defaults while
others were excluded. When you build the port locally you have complete
control over all options.
Ditto :-)
"portupgrade -a" or "portmanager -u" depending on what application you
are using. Switching between multiple port maintenance applications is
not the worse thing you could do; however, I would not recommend it as
an everyday occurrence.
Ok so "portupgrade -a" upgrades all ports according to the manual.
[snip]
Ok, so if I understand correctly now is that the csup command refreshes
the ports tree while portupgrade upgrades the actual port itself
Update the ports tree first! csup -L 2 ports<- this file "ports" is a
supfile. An example of a supfile was included in a previous mail. More
detailed info in the Handbook.
This clarifies, I can't believe what's wrong with me today as I seem to
not be thinking :-(
I picked this up the first time round on a really good production build
that I made and now I lost all that knowledge oh well working with
MS can do that to you I guess??
[...]
Another tip: Whenever there are situations which can get sticky most of the
time notes are placed into a file containing instructions on how to deal
with the problem. Get into the habit of always reading the UPDATING file
located in /usr/ports so you will know about these *before* updating.
[snip]
This is really great advise as I'm kinda in the process of developing
documentation myself similar to Warren:
http://wiki.optiplex-networks.com/xwiki/bin/view/FreeBSD/
Luckily I build all my systems in jails so is easily managed and doesn't
blow up the whole system, however I do share the ports tree throughout
all jails and the base install meaning that things get simplified
although it can have its own problems such as version inconsistencies etc...
{{PS. this is also due to the fact that I only one available production
system and can't afford to get more although soon I hope to one day}}
Thanks so much guys and sorry for being so noobish these last 2 days,
just sorry you all had to put up with it!! :-)
Anyway best regards to all and hopefully mail along side you guys
helping out others some sunny day in the future :-D
Kaya
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages - portupgrade confusion
Kaya Saman wrote: [snip] > The thing I don't quite understand though is that if the ports tree >> gets refreshed, do the packages get upgraded or will I need to >> rebuild them?? > > You have to rebuild them. > > Does this apply to ports too?? Yes. A package is just a port that someone has compiled into a pre-built binary package for use with pkg_add. These binary packages are placed on ftp servers where pkg_add may download from and install. A port is just you doing the compiling locally yourself using the ports system. The installed result is the same, except for one thing. When a package is built some build options may have been selected as defaults while others were excluded. When you build the port locally you have complete control over all options. > "portupgrade -a" or "portmanager -u" depending on what application you > are using. Switching between multiple port maintenance applications is > not the worse thing you could do; however, I would not recommend it as > an everyday occurrence. > > > Ok so "portupgrade -a" upgrades all ports according to the manual. > [snip] > Ok, so if I understand correctly now is that the csup command refreshes > the ports tree while portupgrade upgrades the actual port itself Update the ports tree first! csup -L 2 ports <- this file "ports" is a supfile. An example of a supfile was included in a previous mail. More detailed info in the Handbook. > eg: > > cd /usr/ports/*/nano > make install clean cd /usr/ports/editors/nano/ make install clean This installs nano when it was not installed before. The manual method to update would be: (with a freshly updated ports tree) cd /usr/ports/editors/nano/ make && make deinstall && make reinstall > although not the case but say if this was to build version 1.8 of the > Nano text editor, running: > > portupgrade nano > > would upgrade the installed version to 1.9?? Yes - provided you had installed portupgrade and are using an up to date ports tree. If your ports tree is as old as the old version of nano then as far as FreeBSD is concerned it does not know of any new version. Refreshing your ports tree is where that information comes from. The utility of automation with portupgrade really comes into play when you are trying to update more than one port. One port at a time can be done manually as in the above example, but that quickly becomes tiresome when there are many. Sometimes a port may provide a shared library which many other ports depend upon. Updating that library may cause dependent apps to break. In such a situation portupgrade can recurse and rebuild all apps depending on that library so they will be linked against the new. Another tip: Whenever there are situations which can get sticky most of the time notes are placed into a file containing instructions on how to deal with the problem. Get into the habit of always reading the UPDATING file located in /usr/ports so you will know about these *before* updating. [snip] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages - portupgrade confusion
On Sun, 12 Sep 2010, Kaya Saman wrote: The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? The ports tree is just build instructions, so updating it doesn't update any installed applications. It does let you use a program to see which installed applications need to be updated, like pkg_version or portversion. Here's a document I've been working on lately about upgrading ports. I'm not sure it's really there yet, but it covers the basics: http://www.wonkity.com/~wblock/docs/html/portupgrade.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages - portupgrade confusion
Hi Jerry and Michael, thanks for all the advise and information!! I think I was confusing terminologies a little I was trying to imply that I have been building from ports all this time and *not* using pkg_add to obtain pre-built packages. I think mainly it's just that I've been using package managers too much with Linux and OpenSolaris distros that it got burned into my brain. not to mention that yesterday was a 14 hour shift without break which didn't help. The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? You have to rebuild them. Does this apply to ports too?? "portupgrade -a" or "portmanager -u" depending on what application you are using. Switching between multiple port maintenance applications is not the worse thing you could do; however, I would not recommend it as an everyday occurrence. Ok so "portupgrade -a" upgrades all ports according to the manual. On 09/12/2010 03:52 PM, Michael Powell wrote: [...] To elaborate a little. csup -L 2 ports is what refreshes the ports tree. Portupgrade is a third party app you can install to assist in automating the updating process. Once you've installed portupgrade there are man pages for portsdb, pkgdb, and portversion to see what the switches described above do. The commands above are just strung together to prepare a system for updating. portupgrade -a is actually what does the actual updating. There are other tools as well, I'm just not as familiar with them. I think the other one is called portmaster. It may even be better, I don't know as I tend to stick with what I know as long as it keeps doing the job. [ Ok, so if I understand correctly now is that the csup command refreshes the ports tree while portupgrade upgrades the actual port itself eg: cd /usr/ports/*/nano make install clean although not the case but say if this was to build version 1.8 of the Nano text editor, running: csup -L 2 portupgrade nano would upgrade the installed version to 1.9?? Of course the current version of Nano is totally different I am just trying to understand here!! [...] I don't know if I can properly explain well enough, but I'll take a stab at it anyways. But I believe the first answer here would be no. Refreshing the ports tree does not install or update any installed software. I kind of keyed in on your mentioning of portupgrade. Portupgrade is a tool for automating the upgrading of installed software. While I believe it, and possibly portmaster can operate on pre-built packages I myself stopped using packages a long time ago. I compile everything. Ok I think this practically explains what I've just been trying to say above. [...] Hope this helps. I'm not the best at explaining things, but the Handbook is a most excellent resource to be studied extensively. It is written much better than anything I can manage. And while much of it may seem cryptic at first glance, most of what you need to know is in there. Yep I think this helps a lot!!! :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Many thanks and best regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages - portupgrade confusion
Kaya Saman wrote: > [...] >> csup -L 2 ports && portsdb -uF && pkgdb -u && portversion To elaborate a little. csup -L 2 ports is what refreshes the ports tree. Portupgrade is a third party app you can install to assist in automating the updating process. Once you've installed portupgrade there are man pages for portsdb, pkgdb, and portversion to see what the switches described above do. The commands above are just strung together to prepare a system for updating. portupgrade -a is actually what does the actual updating. There are other tools as well, I'm just not as familiar with them. I think the other one is called portmaster. It may even be better, I don't know as I tend to stick with what I know as long as it keeps doing the job. [snip] > > I didn't actually refresh the ports tree so I'm gona have to do that. > > The thing I don't quite understand though is that if the ports tree gets > refreshed, do the packages get upgraded or will I need to rebuild them?? I don't know if I can properly explain well enough, but I'll take a stab at it anyways. But I believe the first answer here would be no. Refreshing the ports tree does not install or update any installed software. I kind of keyed in on your mentioning of portupgrade. Portupgrade is a tool for automating the upgrading of installed software. While I believe it, and possibly portmaster can operate on pre-built packages I myself stopped using packages a long time ago. I compile everything. A pre-built package is built from the same ports system that you would use if you were compiling locally yourself. It's just someone else has done it for you. The thing to know is that in either situation, e.g. pre-built package or compile it yourself the ports tree is where the versioning and dependency tracking happens. There is more information in the Handbook, and probably presented better there than I can. It is spread out in several locations however. It may not be immediately apparent when reading the "How to install software" section that you also need to read the other sections further down that explain csup, portmaster, etc. The main thing we will keep reiterating though is the first step for updating installed apps is always refresh the ports tree first. > I slightly recall the csup commnad, however I've never actually > performed an inplace upgrade of a package in BSD. Only done this kind of > thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, > Belenix where they have package managers. > > What's the process for upgrading a package? make reinstall clean?? > Since I don't use packages my vantage point is centered around compiling locally myself. However, most of what I describe applies to both situations. Typically the first thing to do is update/refresh the ports tree. Should you determine something needs to be updated the manual approach would be to change to the directory of the app in ports system and do make, followed by make deinstall, and then make reinstall. The deinstall/reinstall leaves your configurations for installed apps in place. Portupgrade is a tool that automates this. After refreshing the ports tree the portupgrade -a command will pretty much do what was described in the previous paragraph automagically. It isn't perfect and sometimes it hiccups. I've noticed that doing this more often so that only a few out of date apps need upgrading at any one time is smoother. It's when you have a hundred things that are really old and out of date because updating has been infrequent is when you are most likely to experience trouble. Hope this helps. I'm not the best at explaining things, but the Handbook is a most excellent resource to be studied extensively. It is written much better than anything I can manage. And while much of it may seem cryptic at first glance, most of what you need to know is in there. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages - portupgrade confusion
On Sun, 12 Sep 2010 14:34:52 +0300 Kaya Saman articulated: > [...] > > Have you refreshed the ports tree(s) with csup using the same > > supfile to ensure the ports trees are up to date ( and therefore > > identical)? Since you are using portugrade, as I do, this is what I > > do to see what needs to be done: > > > > I cd to /usr/sup which is where I keep my supfiles and the > > housekeeping. Then using this command sequence will refresh the > > ports tree, the ports index database, and ensure the package > > database is clean and synced. Portversion then just tells you with > > a "<" symbol any that are old and in need of an update. > > > > csup -L 2 ports&& portsdb -uF&& pkgdb -u&& portversion > > > > where "ports" above is my supfile for ports refresh and looks like > > this: > > > > *default host=cvsup.nl.freebsd.org > > *default base=/usr > > *default prefix=/usr > > *default release=cvs tag=. > > *default delete use-rel-suffix compress > > ports-all > > > > Then a portupgrade -a as required. If all symbols in the right > > column are "=" everything is up to date and nothing is required. > > Adjust server location for mirror near you (or one that works best). > > > > -Mike > > Thanks alot Mike for the response!! > > I didn't actually refresh the ports tree so I'm gona have to do that. > > The thing I don't quite understand though is that if the ports tree > gets refreshed, do the packages get upgraded or will I need to > rebuild them?? You have to rebuild them. > I slightly recall the csup commnad, however I've never actually > performed an inplace upgrade of a package in BSD. Only done this kind > of thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, > Belenix where they have package managers. > > What's the process for upgrading a package? make reinstall clean?? If using a port maintenance application such as portupgrade or portmanager, you could simply do the following: "portupgrade -a" or "portmanager -u" depending on what application you are using. Switching between multiple port maintenance applications is not the worse thing you could do; however, I would not recommend it as an everyday occurrence. If doing it manually, you could just do: make && make deinstall && make reinstall && make distclean There are other variations of course. I would recommend that you run: "make config" in the port's home directory prior to building it for the first time. there might be some useful features that you want to turn on or off. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Minicomputer: A computer that can be afforded on the budget of a middle-level manager. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages - portupgrade confusion
[...] Have you refreshed the ports tree(s) with csup using the same supfile to ensure the ports trees are up to date ( and therefore identical)? Since you are using portugrade, as I do, this is what I do to see what needs to be done: I cd to /usr/sup which is where I keep my supfiles and the housekeeping. Then using this command sequence will refresh the ports tree, the ports index database, and ensure the package database is clean and synced. Portversion then just tells you with a "<" symbol any that are old and in need of an update. csup -L 2 ports&& portsdb -uF&& pkgdb -u&& portversion where "ports" above is my supfile for ports refresh and looks like this: *default host=cvsup.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix compress ports-all Then a portupgrade -a as required. If all symbols in the right column are "=" everything is up to date and nothing is required. Adjust server location for mirror near you (or one that works best). -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Thanks alot Mike for the response!! I didn't actually refresh the ports tree so I'm gona have to do that. The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? I slightly recall the csup commnad, however I've never actually performed an inplace upgrade of a package in BSD. Only done this kind of thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, Belenix where they have package managers. What's the process for upgrading a package? make reinstall clean?? Many Thanks Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages - portupgrade confusion
Kaya Saman wrote: > Hi, > > I have 2 servers one production and another test. > > The test machine's packages however, seem to be older then the > production machines one's even though I built the production system a > few months ago. > > I used the: portupgrade command in order to try to upgrade the ports nad > re-install the packages only the same versions seem to be compiling??? > > I ran: portupgrade -ai > > on the base system as the system where these packages are installed into > is a FreeBSD jail. > > The ports in question are these: > > tomcat-6.0.29 Open-source Java web server by Apache, 6.x branch > postgresql-client-8.2.17_1 PostgreSQL database (client) > postgresql-server-8.2.17_1 The most advanced open-source database > available anywhere > > Which on my newer test system show up as such: > > postgresql-client-8.2.13 PostgreSQL database (client) > postgresql-server-8.2.13 The most advanced open-source database > available anywhere > tomcat-6.0.20_1 Open-source Java web server by Apache, 6.x branch > > I don't understand this 100%??? > > I would like the versions to be the same as the production system since > I have a postgres-Tomcat connector which doesn't work on the test setup > as my Tomcat webapp isn't being displayed!! > > Can I do anything about this?? > > I don't even know why it is like this although I must admit that it has > been an exceptionally long day and am really suffering from fatigue now > which might be a contributor but I can't tell. > > Can anyone give me any advise?? > Have you refreshed the ports tree(s) with csup using the same supfile to ensure the ports trees are up to date ( and therefore identical)? Since you are using portugrade, as I do, this is what I do to see what needs to be done: I cd to /usr/sup which is where I keep my supfiles and the housekeeping. Then using this command sequence will refresh the ports tree, the ports index database, and ensure the package database is clean and synced. Portversion then just tells you with a "<" symbol any that are old and in need of an update. csup -L 2 ports && portsdb -uF && pkgdb -u && portversion where "ports" above is my supfile for ports refresh and looks like this: *default host=cvsup.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix compress ports-all Then a portupgrade -a as required. If all symbols in the right column are "=" everything is up to date and nothing is required. Adjust server location for mirror near you (or one that works best). -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Wed, 2 Sep 2009 05:12:25 -0500 Chris wrote: > I'll paraphrase what you said as I understand you; > Upgrading packages to a RELEASE system (by way of setting set > PACKAGESITE to reflect: > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/) > Would indeed keep them updated whereas the default PACKAGESITE setting > would do nothing more then install the packages that were created at the > time of RELEASE. > So in short, Yes, there is a way I can run RELEASE while still getting > updated packages using pkg_upgrade as long as I set PACKAGESITE. Correct. > Now - I just need that last question answered about mounting ext2 and > I'm off to install. Not me, sorry. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Wed, 02 Sep 2009 10:42:02 +0400 Boris Samorodov wrote: > On Wed, 2 Sep 2009 01:08:54 -0500 Chris wrote: > > On Wed, 02 Sep 2009 09:50:08 +0400 > > Boris Samorodov wrote: > > > On Wed, 2 Sep 2009 00:25:18 -0500 Chris wrote: > > > > > Thanks - although, this seems a moot point if one sticks with > > > > RELEASE (until a point release that is I suppose). > > > > > > Packges are build for STABLE as well: > > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ > > > I do realize this however, if one stays with RELEASE (and not deal > > with the possible (I did say possible) headaches of a changing base > > system) then (as I read it from the Handbook) updating packages is > > moot. They won't change until the next point release. > > The thing is that those packages (called FreeBSD-stable-packages) > can (and imo) should be used with RELEASE either. The ports tree > is always HEAD. And -stable- for packages means only that they > were build after -release- packages. > I'll paraphrase what you said as I understand you; Upgrading packages to a RELEASE system (by way of setting set PACKAGESITE to reflect: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/) Would indeed keep them updated whereas the default PACKAGESITE setting would do nothing more then install the packages that were created at the time of RELEASE. So in short, Yes, there is a way I can run RELEASE while still getting updated packages using pkg_upgrade as long as I set PACKAGESITE. Now - I just need that last question answered about mounting ext2 and I'm off to install. -- Best regards, Chris () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments "There's no place like 127.0.0.1" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Wed, 2 Sep 2009 01:08:54 -0500 Chris wrote: > On Wed, 02 Sep 2009 09:50:08 +0400 > Boris Samorodov wrote: > > On Wed, 2 Sep 2009 00:25:18 -0500 Chris wrote: > > > Thanks - although, this seems a moot point if one sticks with > > > RELEASE (until a point release that is I suppose). > > > > Packges are build for STABLE as well: > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ > I do realize this however, if one stays with RELEASE (and not deal with > the possible (I did say possible) headaches of a changing base system) > then (as I read it from the Handbook) updating packages is moot. They > won't change until the next point release. The thing is that those packages (called FreeBSD-stable-packages) can (and imo) should be used with RELEASE either. The ports tree is always HEAD. And -stable- for packages means only that they were build after -release- packages. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Wed, 02 Sep 2009 09:50:08 +0400 Boris Samorodov wrote: > On Wed, 2 Sep 2009 00:25:18 -0500 Chris wrote: > > On Wed, 02 Sep 2009 09:17:12 +0400 > > Boris Samorodov wrote: > > > On Tue, 1 Sep 2009 17:15:53 -0500 Chris wrote: > > > > > > > Probably a long time discussed question: > > > > Updating a system is (or can be) done with freebsd-update. > > > > What is the suggested way of upgrading packages (not ports)? > > > > > > The port sysutils/bsdadminscripts has a script pkg_upgrade > > > to upgrade packages. > > > Thanks - although, this seems a moot point if one sticks with > > RELEASE (until a point release that is I suppose). > > Packges are build for STABLE as well: > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ > I do realize this however, if one stays with RELEASE (and not deal with the possible (I did say possible) headaches of a changing base system) then (as I read it from the Handbook) updating packages is moot. They won't change until the next point release. I'm just trying to determine the way I want to move back to FreeBSD and not repeat the episodes of upgrades due to installing ports. This turned out to be a weekly event that took the majority of my Friday nights. I admit that I have gotten spoiled with Linux updates (all binary - no issues, no breakage, and no dependency-hell like there used to be with Ports). Of course, I'm sure that dealing with Ports has improved in the 2 years I was on my "sabbatical", but I did get used to actually using and enjoying my puter (again, my biased view point on when I used to use FreeBSD). And now for the last question - I know there were issues mounting ext2 (128 bit) but have since been corrected. This is important to me in the short term. What version (I know the upcoming 8 will have it) now has the patch I have about that supports ext2/128 bit? If it's 7.2, I assume that updating the src should or would take care of it? Once I have recommitted back to FBSD, I would convert the drives that are currently ext3. I'm not trolling nor trying to start an OS war, just some questions I need to get clarity on before I wipe and install. If all my ducks are in a row, my transition back should be rather pleasant or at worse, not happen at all. Thanks for your time. -- Best regards, Chris () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments "There's no place like 127.0.0.1" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Wed, 2 Sep 2009 00:25:18 -0500 Chris wrote: > On Wed, 02 Sep 2009 09:17:12 +0400 > Boris Samorodov wrote: > > On Tue, 1 Sep 2009 17:15:53 -0500 Chris wrote: > > > > > Probably a long time discussed question: > > > Updating a system is (or can be) done with freebsd-update. > > > What is the suggested way of upgrading packages (not ports)? > > > > The port sysutils/bsdadminscripts has a script pkg_upgrade > > to upgrade packages. > Thanks - although, this seems a moot point if one sticks with RELEASE > (until a point release that is I suppose). Packges are build for STABLE as well: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Wed, 02 Sep 2009 09:17:12 +0400 Boris Samorodov wrote: > On Tue, 1 Sep 2009 17:15:53 -0500 Chris wrote: > > > Probably a long time discussed question: > > Updating a system is (or can be) done with freebsd-update. > > What is the suggested way of upgrading packages (not ports)? > > The port sysutils/bsdadminscripts has a script pkg_upgrade > to upgrade packages. > Thanks - although, this seems a moot point if one sticks with RELEASE (until a point release that is I suppose). -- Best regards, Chris () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments "There's no place like 127.0.0.1" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Tue, 1 Sep 2009 17:15:53 -0500 Chris wrote: > Probably a long time discussed question: > Updating a system is (or can be) done with freebsd-update. > What is the suggested way of upgrading packages (not ports)? The port sysutils/bsdadminscripts has a script pkg_upgrade to upgrade packages. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Wed, 2 Sep 2009 01:32:47 +0200 Polytropon wrote: > On Tue, 1 Sep 2009 17:15:53 -0500, Chris wrote: > > Greetings, > > > > Probably a long time discussed question: > > Updating a system is (or can be) done with freebsd-update. > > What is the suggested way of upgrading packages (not ports)? > > There's at least portupgrade with the -P option that forces the > use of packages. You can as well use pkg_add to perform an > "upgrade-like" action, but you'll have to take care for more > things manually. > > > From sysutils/bsdadminscripts - pkg_upgrade looks like what I am after. From the pkg_upgrade man page... PKG_UPGRADE(1) BSD Reference Manual PKG_UPGRADE(1) NAME pkg_upgrade - upgrade an installed package in-place SYNOPSIS pkg_upgrade [-afqsv] pkgname.cgz DESCRIPTION The pkg_upgrade command is used to upgrade an installed package in-place. If no other version of the package is installed and -a is not given, pkg_upgrade simply calls pkg_add(1). Otherwise, the installed package is deleted and the new version is added, keeping dependencies intact. The following command line options are supported: -a Ignore packages for which no older version is installed (auto). -f Force upgrading the package: Also upgrade if the exact same ver- sion is already installed, useful if you rebuilt a package from source. If a conflicting package other than an older version of the same package is installed, remove it. -q Don't print less important messages (quiet). -s Enable special treatment for shared libraries, see below (shlibs). -v Pass the -v flag to subprocesses for more verbose operation. SHARED LIBRARY SUPPORT pkg_upgrade has a special mode for upgrading shared library packages. Consider the following situation: You have installed a package foo that contains libfoo.so.1.0. Package bar is also installed and contains a binary that depends on this version of libfoo. Now you upgrade the foo package, the new version contains libfoo.so.2.0 instead. The other binary will no longer run. For this reason, systems like Debian split their library packages in two: the library itself and a "developer" package containing headers and so on. Instead, pkg_upgrade creates a "stub package" from the installed package. Basically, the installed package is split in two. The old li- braries are kept as a package named stub-pkgname while the rest is delet- ed and replaced by the new version. In the general case, this should work but you may still run into situa- tions where you will need to rebuild dependent packages from source. In any case, you can delete unused stub packages after you have rebuilt dependent packages. SEE ALSO pkg_add(1), pkg_create(1), pkg_delete(1), ports(7) -- Best regards, Chris () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments "There's no place like 127.0.0.1" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading packages
On Tue, 1 Sep 2009 17:15:53 -0500, Chris wrote: > Greetings, > > Probably a long time discussed question: > Updating a system is (or can be) done with freebsd-update. > What is the suggested way of upgrading packages (not ports)? There's at least portupgrade with the -P option that forces the use of packages. You can as well use pkg_add to perform an "upgrade-like" action, but you'll have to take care for more things manually. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: UPGRADING PACKAGES
On 9/4/06, Phares Kariuki <[EMAIL PROTECTED]> wrote: Hello I installed Samba 2 on a FreeBSD box running 5.4 Stable... now the problem is this... I urgently need to upgrade this package but cannot seem to find a way to do so... I didnt install it off the port... In istalled it using pkg_add... it was in the CD that contains applications Deinstall it (pkg_delete -x samba) and install samba3 from ports (cd /usr/ports/net/samba3 && make install) or packages (pkg_add -r samba3) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
