Re: Upgrading to 60 question.
On Tuesday 29 November 2005 07:16, the author RW contributed to the dialogue on- Re: Upgrading to 60 question.: On Tuesday 29 November 2005 14:01, Lowell Gilbert wrote: The ports will continue to work, but you should update them when you get a chance so that they link against the 6.0 libraries instead of the old ones. One exception is nvidia-driver, you must remove the driver from loader.conf and rebuild against 6.0 before re-enabling it. Umph just checked loader.conf and the file is blank Man nv(4) refers to the nvidia driver - I am not certain where/how the driver is being loaded -- X must be using it! any ideas? david -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 60 question.
On Tuesday 29 November 2005 18:53, Vizion wrote: On Tuesday 29 November 2005 07:16, the author RW contributed to the dialogue on- Re: Upgrading to 60 question.: On Tuesday 29 November 2005 14:01, Lowell Gilbert wrote: The ports will continue to work, but you should update them when you get a chance so that they link against the 6.0 libraries instead of the old ones. One exception is nvidia-driver, you must remove the driver from loader.conf and rebuild against 6.0 before re-enabling it. Umph just checked loader.conf and the file is blank Man nv(4) refers to the nvidia driver - I am not certain where/how the driver is being loaded -- X must be using it! any ideas? nv is the open-source driver. It's nvidia's own driver (in the x11/nvidia-driver port) that's causes a problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 60 question.
On Tuesday 29 November 2005 12:02, the author RW contributed to the dialogue on- Re: Upgrading to 60 question.: On Tuesday 29 November 2005 18:53, Vizion wrote: On Tuesday 29 November 2005 07:16, the author RW contributed to the dialogue on- Re: Upgrading to 60 question.: On Tuesday 29 November 2005 14:01, Lowell Gilbert wrote: The ports will continue to work, but you should update them when you get a chance so that they link against the 6.0 libraries instead of the old ones. One exception is nvidia-driver, you must remove the driver from loader.conf and rebuild against 6.0 before re-enabling it. Umph just checked loader.conf and the file is blank Man nv(4) refers to the nvidia driver - I am not certain where/how the driver is being loaded -- X must be using it! any ideas? nv is the open-source driver. It's nvidia's own driver (in the x11/nvidia-driver port) that's causes a problem. ___ nvidia-driver and nvidia-setting are in /dev but I do not know where they are loaded from! Umph Any ideas? david -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to pgsql 8.1 via ports
Pat Maddox writes: Should I use postgresql81-server now instead? Yes. What do I need to do in order to upgrade my system to use pgsql 8.1? I believe you need to go a pg_dumpall all to copy data. Also keep a copy of your postgresql.conf and pg_hba.conf If you don't have any dependencies on the postgresql ports you can pg_dumpall, delete porst, install new ones. If you have dependencies you need to use portupgrade or something like it. As another poster suggested if using portupgrade you will need to use the -o flag. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading glib
Paul Waring [EMAIL PROTECTED] writes: I've just done a cvsup on the following release: *default release=cvs tag=RELENG_5_4 Ports aren't branched, so I'll assume you used tag=. for the ports. and one of the packages due for an update is glib, which has gone from version 2.8.3 to 2.8.4. Given that I've built almost everything on my system from source using ports, do I need to rebuild things once I've upgraded glib? I've had problems before when updating Perl and having to rebuild all the p5-* modules, so I'm not sure with glib being a library of sorts whether or not I'll need to rebuild things. Perl is a special case, because the scripts embed the full path to the executable. In this case, you will probably be fine. To be sure, update everything that is outdated and dependent on glib. portupgrade and portmanager are both nice utilities to help you with this. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading application(s)
--On 11. november 2005 13:15 -0500 Charles Swiger [EMAIL PROTECTED] wrote: On Nov 11, 2005, at 12:57 PM, Sasa Stupar wrote: I am quite new to freebsd. I have several applications build from the ports collection. When some port change for a new version (I cvsup my ports collection) how do I do upgrade of that application? Is it the same as for the first time: just go to the port I want and then type make and make install or is there another way? Yes, there are other ways. The two main choices for rebuilding new ports are sysutils/ portupgrade and sysutils/portmanager. portupgrade is considered the default or standard tool, and it works quite well for most things, but has problems with KDE and GNOME in particular. portmanager uses a rather different approach to handling dependencies, which can require more compiler work, but it seems to handles updating KDE and GNOME better than portupgrade does. OK. I am trying to install portupgrade (I do not use X) from the ports but after I make install I get the following error: === db43-4.3.29 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of databases/db43 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/databases/db43. *** Error code 1 Stop in /usr/ports/databases/ruby-bdb. *** Error code 1 Stop in /usr/ports/sysutils/portupgrade. - Why is it complaining about db43? Yes, I have it allready installed before with installation of Cyrus-imapd. Shouldn't it just ignore if it is allready installed? Regards, Sasa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 6.0 - Would this backup strategy work?
Richard Collyer [EMAIL PROTECTED] writes: I'm thinking of upgrading my 5.4 box to 6.0 mainly becuase I've never done a buildworld I've always installed a fresh. The box is not production quality just something for me to learn BSD on. I have a 7006-2 3ware raid controller miroring on 2 drives. If I was to remove one of the drives and then do the upgrade if the upgrade was successful I could put the other drive in a build the array again. If it failedi could use the old drive to rebuild a working system quickly. Anyone see any issues with this? I think it should work. It seems to have a bunch of ways to accidentally shoot yourself in the foot, though. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading PHP port to 4.4.1 breaks Drupal site
On Friday 11 November 2005 08:30, Ron Wilhoite wrote: After a portupgrade of PHP to 4.4.1 my Drupal 4.6.3 site stopped working. I used portdowngrade to revert to 4.4.0 and the site worked again. After upgrading PHP to 4.4.1 you should rebuild ports that depend on it. -Mike I tried upgrading this morning to 4.4.1_1 and drupal-4.6.3_1, but got the same result. Using portdowngrade to revert to PHP 4.4.0 worked again. I posted to the drupal support list and PHP 4.4.1 does not seem to be causing problems for other Drupal users. The 'missing' files in the error logs below exist and have correct permissions. I also couldn't find anything relevant at php.net or with google searches. I will appreciate any suggestions. Ron Wilhoite Message posted to Drupal list: After upgrading PHP to 4.4.1, my site's homepage loads, but all other pages are blank and I can't login. I restarted apache and mysql, but got the same result. It's Drupal 4.6.3, Apache 2.0.55, Mysql 4.1.15, running on FreeBSD 5.4. I've copied the errors from the apache log below. If there is other information I can provide let me know. I downgraded my PHP ports to 4.4.0 and the site came back up. Thanks for any help or pointers. Apache error log: [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(sites/default/settings.php): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on line 642, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'sites/default/settings.php' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on line 642, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(includes/database.inc): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on line 643, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'includes/database.inc' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on line 643, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(includes/session.inc): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on lin e 644, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'includes/session.inc' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on line 644, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(includes/module.inc): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on line 645, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'includes/module.inc' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on l ine 645, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Fatal error: Call to undefined function: db_fetch_object() in /usr/local/www/data/includes/bootstrap.inc on line 199, referer: http://office.bals.org/ [Wed Nov 02 00:15:46 2005] [error] [client 192.168.0.35] PHP Fatal error: Cannot redeclare conf_init() (previously declared in /usr/local/www/data/includes/bootstrap.inc:45) in /usr/local/www/data/in cludes/bootstrap.inc on line 44, referer: http://office.bals.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to pgsql 8.1 via ports
Pat Maddox [EMAIL PROTECTED] writes: So PostgreSQL 8.1 was released a few days ago, and I was looking forward to upgrading to it. Figured it might take a day or two before the changes were made in ports, and was surprised to see that my postgresql packages are still up to date. The packages I have installed are postgresql-server and postgresql-client...which according to freshports.org don't exist! Right now I'm running 8.0, but I guess I have some outdated packages that may have been deleted? I don't know, to be honest. I suspect if you check /usr/ports/MOVED, you would find that they were moved into databases/postgresql81-*. So I've got a few questions. First, should I not be using postgresql-server and postgresql-client? They don't seem to be in /usr/ports/databases anymore, and I definitely installed them from ports. Should I use postgresql81-server now instead? What do I need to do in order to upgrade my system to use pgsql 8.1? If you use portupgrade, there's a nice -o option to do this. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading PHP port to 4.4.1 breaks Drupal site
Michael C. Shultz wrote: On Friday 11 November 2005 08:30, Ron Wilhoite wrote: After a portupgrade of PHP to 4.4.1 my Drupal 4.6.3 site stopped working. I used portdowngrade to revert to 4.4.0 and the site worked again. After upgrading PHP to 4.4.1 you should rebuild ports that depend on it. -Mike Thanks Mike. Is portupgrade -r php4 the best way to do that? Or should I force the other ports to rebuild with portupgrade -rf php4? Ron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading PHP port to 4.4.1 breaks Drupal site
This is a known bug with PHP4-4.4.1 and Apache2+mod_rewrite. Please see http://bugs.php.net/bug.php?id=35096. Ricky On Nov 11, 2005, at 11:30 AM, Ron Wilhoite wrote: After a portupgrade of PHP to 4.4.1 my Drupal 4.6.3 site stopped working. I used portdowngrade to revert to 4.4.0 and the site worked again. I tried upgrading this morning to 4.4.1_1 and drupal-4.6.3_1, but got the same result. Using portdowngrade to revert to PHP 4.4.0 worked again. I posted to the drupal support list and PHP 4.4.1 does not seem to be causing problems for other Drupal users. The 'missing' files in the error logs below exist and have correct permissions. I also couldn't find anything relevant at php.net or with google searches. I will appreciate any suggestions. Ron Wilhoite Message posted to Drupal list: After upgrading PHP to 4.4.1, my site's homepage loads, but all other pages are blank and I can't login. I restarted apache and mysql, but got the same result. It's Drupal 4.6.3, Apache 2.0.55, Mysql 4.1.15, running on FreeBSD 5.4. I've copied the errors from the apache log below. If there is other information I can provide let me know. I downgraded my PHP ports to 4.4.0 and the site came back up. Thanks for any help or pointers. Apache error log: [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(sites/default/settings.php): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on line 642, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'sites/default/settings.php' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on line 642, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(includes/database.inc): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on line 643, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'includes/database.inc' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on line 643, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(includes/session.inc): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on lin e 644, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'includes/session.inc' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on line 644, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(includes/module.inc): failed to open stream: No such file or directory in /usr/local/www/data/includes/bootstrap.inc on line 645, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Warning: main(): Failed opening 'includes/module.inc' for inclusion (include_path='.:') in /usr/local/www/data/includes/bootstrap.inc on l ine 645, referer: http://office.bals.org/ [Wed Nov 02 00:15:42 2005] [error] [client 192.168.0.35] PHP Fatal error: Call to undefined function: db_fetch_object() in /usr/local/www/data/includes/bootstrap.inc on line 199, referer: http://office.bals.org/ [Wed Nov 02 00:15:46 2005] [error] [client 192.168.0.35] PHP Fatal error: Cannot redeclare conf_init() (previously declared in /usr/local/www/data/includes/bootstrap.inc:45) in /usr/local/www/data/in cludes/bootstrap.inc on line 44, referer: http://office.bals.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading application(s)
On Nov 11, 2005, at 12:57 PM, Sasa Stupar wrote: I am quite new to freebsd. I have several applications build from the ports collection. When some port change for a new version (I cvsup my ports collection) how do I do upgrade of that application? Is it the same as for the first time: just go to the port I want and then type make and make install or is there another way? Yes, there are other ways. The two main choices for rebuilding new ports are sysutils/ portupgrade and sysutils/portmanager. portupgrade is considered the default or standard tool, and it works quite well for most things, but has problems with KDE and GNOME in particular. portmanager uses a rather different approach to handling dependencies, which can require more compiler work, but it seems to handles updating KDE and GNOME better than portupgrade does. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading application(s)
Sasa Stupar wrote: Hi! I am quite new to freebsd. I have several applications build from the ports collection. When some port change for a new version (I cvsup my ports collection) how do I do upgrade of that application? Is it the same as for the first time: just go to the port I want and then type make and make install or is there another way? Regards, Sasa As was already pointed out portmanager and portupgrade are the automated way of doing it, and both are quite good. To do it the manual way you need to go to the port you want to install and do a make deinstall before the make install otherwise it'll complain about the port already being installed. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 4.11-STABLE to 5.4-STABLE
On Wed, Nov 02, 2005 at 09:07:25PM +, Chris Howells wrote: Hi, I want to upgrade my 4.11-STABLE server to 5.4-STABLE. I'm very used to using cvsup to upgrade between minor releases (IIRC the box was 4.9 or 4.10 originally) but a jump between major versions is scaring me a bit :) Has anybody done this recently. Were there any major problems other than mentioned in UPDATING? Hi, I have upgraded few boxes remotly. I had only to copy pam.d directory to /etc otherwise I couldn't log via ssh it complained about pam. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading 4.11-STABLE to 5.4-STABLE
Oddly enough, and a little OT, (but semi-within the topic) I'm trying to update a 5.0 box to RELENG_5 right now with several different errors, too many to mention (generally they occur after rebooting after my installkernel. I can subsequently reboot off of kernel.old, as always). That's not surprising, if your kernel and userland are too far out of sync, lots of things won't work right like ps and ipfw and so forth. If the kernel boots OK into single-user mode, it should be OK to do the installworld. Hmmm, interesting point. I didn't even think of that. However, if I do that successfully, then reboot the system and it fails, there is no way to 'undo' the installworld...right? Either way, I'm going to try it, so I can use that experience for when I have to do a production box. Anyway, you really don't want to stay with 5.0, even if it takes a reinstall from a 5.4 CD to get there :-) Eventually, if all else fails, I will. Take full backups before you do anything. The thing is, there is nothing wrong with a 4.11 system, either, especially if it is a uni-processor machine. For SMP hardware, I'd be tempted to jump directly to 6.0 or wait for 6.1, rather than move to the middle/end of the 5.x releases. The Samba box is a SMP unit, but the 4.11 is a uni-proc box. I've been running it that way since 4.5, moving the system to new disks a few times, and periodically more powerful boxes. I have really no reason to upgrade this one to 5 or 6 at this point...and BTW, I always do backups. System is on a RAID-1, with a second RAID-1 setup that gets a mirrored copy of the primary RAID every day. Further that, I have it taped up too. Call me paranoid, but having the backup RAID ensures that I can just move it to new hardware and continue right on trucking. Keeping your ports up-to-date is a bigger concern, but things like portaudit and the people working on submitting both security warnings and patches to the ports help... Indeed. I just got familiar with portaudit a few weeks ago, and I find it quite handy. Tks for your input. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 4.11-STABLE to 5.4-STABLE
On Wed, Nov 02, 2005 at 09:07:25PM +, Chris Howells wrote: Hi, I want to upgrade my 4.11-STABLE server to 5.4-STABLE. I'm very used to using cvsup to upgrade between minor releases (IIRC the box was 4.9 or 4.10 originally) but a jump between major versions is scaring me a bit :) Has anybody done this recently. Were there any major problems other than mentioned in UPDATING? Worked smoothly for me. You do need console access to boot to single-user mode. Don't forget to rebuild all your installed ports afterwards too (portupgrade -fa or -faP). Kris pgp0lI2jJ85yF.pgp Description: PGP signature
Re: Upgrading 4.11-STABLE to 5.4-STABLE
On Wed, Nov 02, 2005 at 09:07:25PM +, Chris Howells wrote: Hi, I want to upgrade my 4.11-STABLE server to 5.4-STABLE. I'm very used to using cvsup to upgrade between minor releases (IIRC the box was 4.9 or 4.10 originally) but a jump between major versions is scaring me a bit :) Has anybody done this recently. Were there any major problems other than mentioned in UPDATING? In addition to UPDATING you should read http://www.freebsd.org/releases/5.3R/migration-guide.html which details how you should upgrade from 4.11 to 5.3. I don't think there has been any important changes between 5.3 and 5.4 in this regard. I don't particularly want to install from fresh if possible, due to the hassle of removing the server from the bottom of the pile (too poor to afford a rack ;(), opening the case up and fitting a CD-ROM etc. -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 4.11-STABLE to 5.4-STABLE
Chris Howells wrote: Hi, I want to upgrade my 4.11-STABLE server to 5.4-STABLE. I'm very used to using cvsup to upgrade between minor releases (IIRC the box was 4.9 or 4.10 originally) but a jump between major versions is scaring me a bit :) Has anybody done this recently. Were there any major problems other than mentioned in UPDATING? I don't particularly want to install from fresh if possible, due to the hassle of removing the server from the bottom of the pile (too poor to afford a rack ;(), opening the case up and fitting a CD-ROM etc. Hope this is not too obvious to mention but if your server has a floppy drive you could do a net install... Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading 4.11-STABLE to 5.4-STABLE
I want to upgrade my 4.11-STABLE server to 5.4-STABLE. I'm very used to using cvsup to upgrade between minor releases (IIRC the box was 4.9 or 4.10 originally) but a jump between major versions is scaring me a bit :) Oddly enough, and a little OT, (but semi-within the topic) I'm trying to update a 5.0 box to RELENG_5 right now with several different errors, too many to mention (generally they occur after rebooting after my installkernel. I can subsequently reboot off of kernel.old, as always). Since this is only a data box (running Samba), I'm not too worried, as I'll just reinstall...but I thought I'd throw it out there to see if there is a better approach to this particular upgrade (ie...incremental), as well as OP to get us both to STABLE. Note I also have a real production box at the following with the same issue, however, it's much more relied apon, so an upgrade as opposed to rebuild solution would be nice: FreeBSD pearl.ibctech.ca 4.11-STABLE FreeBSD 4.11-STABLE #4: Fri Jun 24 12:14:21 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PEARL i386 Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 4.11-STABLE to 5.4-STABLE
Steve Bertrand wrote: I want to upgrade my 4.11-STABLE server to 5.4-STABLE. I'm very used to using cvsup to upgrade between minor releases (IIRC the box was 4.9 or 4.10 originally) but a jump between major versions is scaring me a bit :) Oddly enough, and a little OT, (but semi-within the topic) I'm trying to update a 5.0 box to RELENG_5 right now with several different errors, too many to mention (generally they occur after rebooting after my installkernel. I can subsequently reboot off of kernel.old, as always). That's not surprising, if your kernel and userland are too far out of sync, lots of things won't work right like ps and ipfw and so forth. If the kernel boots OK into single-user mode, it should be OK to do the installworld. Anyway, you really don't want to stay with 5.0, even if it takes a reinstall from a 5.4 CD to get there :-) Since this is only a data box (running Samba), I'm not too worried, as I'll just reinstall...but I thought I'd throw it out there to see if there is a better approach to this particular upgrade (ie...incremental), as well as OP to get us both to STABLE. Note I also have a real production box at the following with the same issue, however, it's much more relied apon, so an upgrade as opposed to rebuild solution would be nice: FreeBSD pearl.ibctech.ca 4.11-STABLE FreeBSD 4.11-STABLE #4: Fri Jun 24 12:14:21 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PEARL i386 Take full backups before you do anything. The thing is, there is nothing wrong with a 4.11 system, either, especially if it is a uni-processor machine. For SMP hardware, I'd be tempted to jump directly to 6.0 or wait for 6.1, rather than move to the middle/end of the 5.x releases. Keeping your ports up-to-date is a bigger concern, but things like portaudit and the people working on submitting both security warnings and patches to the ports help... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from 5.3 to 6.0 (was: no subject)
On 10/27/05, George Katsanos [EMAIL PROTECTED] wrote: Hello , Since the actual 6.0 Release is taking too long , would you suggest me installing 6.0 RC-1 and then then 6.0 is out , can I just apply some patches , or I should Re-makeworld everything?... And another question , I'm on a PIII 550 with 256MB ram . I have 5.3 and some broken libs .Would you suggest me doing a fresh install , or a make world ? Consider I don't have the experience the second procedure takes , but I've heard both opinions. Should I do a portupgrade -a after the makeworld ?... Thank you George ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Yes, you can try 6.0RC1, it's pretty stable. Read the Handbook and stick to the advice: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html You shouldn't have any trouble. You should do portupgrade -fa (recompile all your ports) after the upgrade is finished, but it's not an urgent matter. You can as well wait a few weeks and recompile them all then - thanks to binary compatibility they will work until then. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to freebsd 5.4 STABLE from 5.3 kernel panic, what do i do to get data back?
El Osteguna 13 Urria 2005 14:49, Alex escribió: Hello list! I have been successfully been running 5.3 for a couple of weeks when i decided i should upgrade to 5.4 stable. Now the make world went fine except mergemaster complaining it couldn't find usr/src/etc or something similar. I made make buildkernel wich also went fine. But when I booted into my upgraded system I got kernel panic, so I made another restart and this time it went ok. Yestoday I removed SCSI card and DAT tape and NIC so I can have them in my main server. Now i cant get past this: freebsd 5.4-stable kernel trap 12 with interupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x9 fault code = supervisor write, page not present instruction pointer = 0x8 :0xc077c073 stack pointer = 0x10 :0xc0c20d00 frame pointer = 0x10 :0xc0c20d0c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault Uptime: 1s So my attack-plan is to reinstall system from scratch and never do make buildworld make buildkernel again, BUT, I have a whole lot of information remaining on both disks that are in right now. From what I could see in the installer, fbsd installer wont let me install in a different directory with filesystem still intact like windows doesor does it? Please help! :) You don't need to reinstall from scratch. Get into the boot loader prompt and type boot kernel.old, this way you'll boot the old 5.3 kernel. Once there, update your src tree and perform the upgrade following the instructions in the 20.4.1 chapter of the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading
On 9/29/05, eoghan [EMAIL PROTECTED] wrote: On 28 Sep 2005, at 21:46, Beecher Rintoul wrote: On Wednesday 28 September 2005 12:28 pm, eoghan wrote: Hello Im going to do a fresh install of 5.3 over the weekend, then id like to upgrade to 5.4. My reasons for upgrading are: ill have to do it some time or another and I cant always rely on having my trusty dvd with me. So, the question is: what is the best way to do an upgrade? I figure ill do the install, make sure its all ok, and before I go ahead and install anything ill upgrade. I did hear people say that using the sysinstall isnt the way to go - maybe or maybe not? So any opinions here on how it should be done would be appreciated. To save yourself some time, just boot from your disk change the tag in the options screen to 5.4-RELEASE and do a net install. No need to start from 5.3. Beech Thanks for your advice. and thank you Derrick. I will read into those articles. Mike, the main reason is just so I can learn how to do it. Im using freebsd on my other computer only to learn it. Thanks all Eoghan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] The Handbook has an excellent article on updating: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html For 5.3-5.4 or 5.3-6.0 or 5.4-6.0 transition you'll have to: 1. cvsup 2. make buildworld make buildkernel 3. make installkernel make installworld 4. mergemaster # be careful here 5. shutdown -r now Personally I tried each of these three transiotions and had absolutely no problem, though it did require some attention and reading. Have fun! Andrew P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading
On 9/28/05, eoghan [EMAIL PROTECTED] wrote: Hello Im going to do a fresh install of 5.3 over the weekend, then id like to upgrade to 5.4. My reasons for upgrading are: ill have to do it some time or another and I cant always rely on having my trusty dvd with me. Why would you want to do that? Why not just install 5.4? Or wait a bit and install 6? Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading
On Wednesday 28 September 2005 12:28 pm, eoghan wrote: Hello Im going to do a fresh install of 5.3 over the weekend, then id like to upgrade to 5.4. My reasons for upgrading are: ill have to do it some time or another and I cant always rely on having my trusty dvd with me. So, the question is: what is the best way to do an upgrade? I figure ill do the install, make sure its all ok, and before I go ahead and install anything ill upgrade. I did hear people say that using the sysinstall isnt the way to go - maybe or maybe not? So any opinions here on how it should be done would be appreciated. To save yourself some time, just boot from your disk change the tag in the options screen to 5.4-RELEASE and do a net install. No need to start from 5.3. Beech -- --- Beech Rintoul - System Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ --- pgphVynlsB1c9.pgp Description: PGP signature
Re: upgrading
On 28 Sep 2005, at 21:46, Beecher Rintoul wrote: On Wednesday 28 September 2005 12:28 pm, eoghan wrote: Hello Im going to do a fresh install of 5.3 over the weekend, then id like to upgrade to 5.4. My reasons for upgrading are: ill have to do it some time or another and I cant always rely on having my trusty dvd with me. So, the question is: what is the best way to do an upgrade? I figure ill do the install, make sure its all ok, and before I go ahead and install anything ill upgrade. I did hear people say that using the sysinstall isnt the way to go - maybe or maybe not? So any opinions here on how it should be done would be appreciated. To save yourself some time, just boot from your disk change the tag in the options screen to 5.4-RELEASE and do a net install. No need to start from 5.3. Beech Thanks for your advice. and thank you Derrick. I will read into those articles. Mike, the main reason is just so I can learn how to do it. Im using freebsd on my other computer only to learn it. Thanks all Eoghan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading mysql 4.0 to 4.1
Roger Merritt wrote: I want to upgrade mysql from ver. 4.0.26 to 4.1.x but am daunted by the existence of the separate ports. Can I just run portinstall -R mysql41-\* or should I do pkgdeinstall mysql40-\* first? mysql client 4.1 cannot connect to server 4.0 (and AFAIK, nor can client 4.0 connect to server 4.1) which justifies the existence of separate ports. They conflict so you will have to deinstall 4.0 first then install 4.1. Just to be on the safe side, take a complete dump of your database first. server 4.1 should be able to read the old database with out having to reaload everything. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading mysql 4.0 to 4.1
Hello, On Thu, Sep 22, 2005 at 09:40:32AM +0200 or thereabouts, Erik Norgaard wrote: mysql client 4.1 cannot connect to server 4.0 (and AFAIK, nor can client 4.0 connect to server 4.1) which justifies the existence of separate ports. Actually mysql 4.1 client is able to connect to mysql 4.0 server. I migrated our production servers to 4.1, with some databases still left in few 4.0, and applications are able to communicate with both versions via mysql 4.1 client. [amber] ~ mysql --version mysql Ver 14.7 Distrib 4.1.13, for portbld-freebsd5.4 (i386) using 4.3 [amber] ~ [amber] ~ [amber] ~ [amber] ~ mysql -u corwin -p -h 192.168.0.13 Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 44001 to server version: 4.0.25 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql -- martin hudec * 421 907 303 393 * [EMAIL PROTECTED] * http://www.aeternal.net Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws. Douglas Adams, The Hitchhiker's Guide to the Galaxy pgp4Fc1GOFViZ.pgp Description: PGP signature
Re: Upgrading mysql 4.0 to 4.1
On Thu, 22 Sep 2005 10:05:31 +0700, Roger Merritt [EMAIL PROTECTED] Subject: Upgrading mysql 4.0 to 4.1 Wrote these words of wisdom: I want to upgrade mysql from ver. 4.0.26 to 4.1.x but am daunted by the existence of the separate ports. Can I just run portinstall -R mysql41-\* or should I do pkgdeinstall mysql40-\* first? -- Roger * REPLY SEPARATOR * On 9/22/2005 4:53:54 AM, Gerard Seibert Replied: I went that root until I finally updated to MySQL 5. In any case, you could try the following. From root: 1) Update your ports 2) Install 'portmanager' 3} Run portmanager -u That will update all of your out of date ports and their dependencies as well as updating MySQL. Be fore warned, you will have to restart MySQL after portmanager has finished running. Actually, if there are a lot of running processes updated, I just reboot. -- Gerard Seibert [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
Zan wrote: uname -m = i386 which -a perl = /usr/local/bin/perl /usr/bin/perl Please show: uname -m which -a perl On Tuesday, August 30, 2005, at 01:30 P:M, Lowell Gilbert wrote: Zan [EMAIL PROTECTED] writes: in my /usr/local/bin I can clearly see that there is a newer version of perl (5.8.0) already there, but when I type 'perl -v' I see that I'm running off of 5.0. Is there anything else I can do besides trying the use.perl port command? Because that doesn't seem to work, and my jail did not come with a ports collection. I would appreciate any help you can give me. Thank you! Please show: uname -m which -a perl Just a little side-note. After performing such an upgrade of Perl it's likely that some applications will not work, since a lot of them expect your old version of Perl. Recompiling those applications does the trick. At least, that's what I noticed when upgrading from 5.8.6 to 5.8.7. And just so you know, there are ALOT of applications dependent of Perl. About your problem, you should really recompile Perl from the ports-tree if you want to upgrade your Perl version. And after you did that, I always rebooted the machine. I don't know how it will function without rebooting the machine, or if it's even possible to upgrade Perl properly without a reboot. Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
in message [EMAIL PROTECTED], wrote Jorn Argelo thusly... About your problem, you should really recompile Perl from the ports-tree if you want to upgrade your Perl version. And after you did that, I always rebooted the machine. I don't know how it will function without rebooting the machine, or if it's even possible to upgrade Perl properly without a reboot. There is no reason to reboot just to upgrade perl properly. Rebooting does nothing in regard to upgrading perl, rather you just cause inconvenience to yourself. - Parv -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
Parv wrote: in message [EMAIL PROTECTED], wrote Jorn Argelo thusly... About your problem, you should really recompile Perl from the ports-tree if you want to upgrade your Perl version. And after you did that, I always rebooted the machine. I don't know how it will function without rebooting the machine, or if it's even possible to upgrade Perl properly without a reboot. There is no reason to reboot just to upgrade perl properly. Rebooting does nothing in regard to upgrading perl, rather you just cause inconvenience to yourself. - Parv Yes, I stand corrected. Which is why I mentioned that I didn't know for sure ;-) Jorn. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
Please don't top-post. Zan [EMAIL PROTECTED] writes: On Tuesday, August 30, 2005, at 01:30 P:M, Lowell Gilbert wrote: Zan [EMAIL PROTECTED] writes: in my /usr/local/bin I can clearly see that there is a newer version of perl (5.8.0) already there, but when I type 'perl -v' I see that I'm running off of 5.0. Is there anything else I can do besides trying the use.perl port command? Because that doesn't seem to work, and my jail did not come with a ports collection. I would appreciate any help you can give me. Thank you! Please show: uname -m which -a perl uname -m = i386 Oops. I meant uname -a. You're running some 4.x, I guess? which -a perl = /usr/local/bin/perl /usr/bin/perl Okay, explicitly run each of those perl executables to find the version. Something doesn't make sense here, and you may be looking in the wrong direction... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
Zan wrote: Hello, Would you please help me? in my /usr/local/bin I can clearly see that there is a newer version of perl (5.8.0) already there, but when I type 'perl -v' I see that I'm running off of 5.0. 5.8 is from ports. 5.0.6. i think, is system based Is there anything else I can do besides trying the use.perl port command? Because that doesn't seem to work, you need to install the perl from ports before using use.perl port. and my jail did not come with a ports collection. virtual hoster? can you download the ports collection and use it? (check that you can compile first ;) ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
Zan [EMAIL PROTECTED] writes: in my /usr/local/bin I can clearly see that there is a newer version of perl (5.8.0) already there, but when I type 'perl -v' I see that I'm running off of 5.0. Is there anything else I can do besides trying the use.perl port command? Because that doesn't seem to work, and my jail did not come with a ports collection. I would appreciate any help you can give me. Thank you! Please show: uname -m which -a perl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
uname -m = i386 which -a perl = /usr/local/bin/perl /usr/bin/perl Please show: uname -m which -a perl On Tuesday, August 30, 2005, at 01:30 P:M, Lowell Gilbert wrote: Zan [EMAIL PROTECTED] writes: in my /usr/local/bin I can clearly see that there is a newer version of perl (5.8.0) already there, but when I type 'perl -v' I see that I'm running off of 5.0. Is there anything else I can do besides trying the use.perl port command? Because that doesn't seem to work, and my jail did not come with a ports collection. I would appreciate any help you can give me. Thank you! Please show: uname -m which -a perl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl -ports
Zan wrote: 5.8 is from ports. 5.0.6. i think, is system based In my 'usr/local/BIN' perl5.8.0 already exists. ok you need to install the perl from ports before using use.perl port. What I want to know is how to switch to 5.8.0 WITHOUT using use.perl port because I already tried that, and it does not work! what do you mean / how do you know 'it doesnt work'. It has always worked fine for me, both on a full system and jails. It will add some options to /etc/rc.conf. You will have to rebuild all perl-related ports so it starts using the perl from ports rather than from system virtual hoster? can you download the ports collection and use it? (check that you can compile first ;) ) Yes, I am on a virtual hosting account, and am very enthralled with freebsd. ;-) welcome aboard! B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading GNOME
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frank Jahnke wrote: | I am upgrading Gnome from 2.4 to 2.10 with a clean install (I have | backups) as part of an upgrade from FreeBSD 5.2.1 to the 6.0 Beta (which | is working well, btw). I would like to preserve various settings from | my old system, including bookmarks, passwords, old email, contacts, and | various folders. How do I do so? You should restore your home directory, then let the applications handle their settings migration. | | The upgrade is from Epiphany 1.4 to 2.2; Evolution is from 1.0.6 to | 1.6.0. A simple-minded copying of the old files into their original | locations showed that both Epiphany and Evolution did not recognize | them. If there is a page describing the upgrade I'd be happy to follow | it if a link is provided. You should never copy settings files. Instead, let the applications themselves handle migration. Evolution, for example, will migrate its own settings files. Copying files by hand will only break things. Note: an upgrade step this large has not been tested by the FreeBSD GNOME team. Joe | | Please copy me on any replies; I don't read both of these groups | regularly. | | Thank you in advance! | | Frank Jahnke | | ___ | [EMAIL PROTECTED] mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-gnome | To unsubscribe, send any mail to [EMAIL PROTECTED] | - -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC6AHjb2iPiv4Uz4cRAqPoAJ9G4baaP8Q7pNaAiDk3V1w/08wU7QCgkLxo GsJelazkcF7zcbUXoq87liY= =WSu/ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading GNOME
On Wed, 2005-07-27 at 14:51, Joe Marcus Clarke wrote: | | The upgrade is from Epiphany 1.4 to 2.2; Evolution is from 1.0.6 to | 1.6.0. A simple-minded copying of the old files into their original | locations showed that both Epiphany and Evolution did not recognize | them. If there is a page describing the upgrade I'd be happy to follow | it if a link is provided. You should never copy settings files. Instead, let the applications themselves handle migration. Evolution, for example, will migrate its own settings files. Copying files by hand will only break things. OK -- so what settings files do I delete to get this to work? Evolution's import facility, for example, did not recognize that any email files existed. I suspected that some of the index files need to be deleted, but before I do so I seek advice. Note: an upgrade step this large has not been tested by the FreeBSD GNOME team. I'll let you know how it works if you like. Joe Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading GNOME
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frank Jahnke wrote: | On Wed, 2005-07-27 at 14:51, Joe Marcus Clarke wrote: | | || || The upgrade is from Epiphany 1.4 to 2.2; Evolution is from 1.0.6 to || 1.6.0. A simple-minded copying of the old files into their original || locations showed that both Epiphany and Evolution did not recognize || them. If there is a page describing the upgrade I'd be happy to follow || it if a link is provided. | |You should never copy settings files. Instead, let the applications |themselves handle migration. Evolution, for example, will migrate its |own settings files. Copying files by hand will only break things. | | | OK -- so what settings files do I delete to get this to work? | Evolution's import facility, for example, did not recognize that any | email files existed. I suspected that some of the index files need to | be deleted, but before I do so I seek advice. No files should need to be deleted. Just restore your entire home directory as it was under GNOME 2.4, and run each application. If Evo is not recognizing the old files, you may be out of luck. Joe - -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC6AVtb2iPiv4Uz4cRAn7UAJ9FQoabpKKNI1zz0w0gz9aHVLlKlwCfbq7v 4Yddjm112P+d0dSOoklmyIQ= =6kdO -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading from 5.4-RELEASE-p4 to 5.4-RELEASE-p5
Louis LeBlanc wrote: There was a new security announcement a couple days ago regarding the devfs subsystem in FreeBSD. The announcement is here: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:17.devfs.asc My question is regarding the upgrade and patch description. I am running 5.4_RELEASE-p4. The alert suggests either patching and rebuilding the kernel or upgrading to 5.4-RELEASE-p5. Upgrading to 5-STABLE or RELENG_5_4 means synchronising your source with one of these CVS tagged branches and then rebuilding your system. In this particular case only the kernel really needs to be rebuilt and reinstalled. Some people however prefer to always rebuild the kernel and world to ensure synchronicity of the two. If I decide to upgrade my source, would it be sufficient (and safe) to just rebuild the kernel, or do I still need to rebuild world? In this case, you could do with only rebuilding and installing the kernel. The only files changed between my last build and this one are src/UPDATING src/sys/conf/newvers.sh src/sys/fs/devfs/devfs_vnops.c And for such a small change (I checked the patch, it's literally a 2 line change - sanity check of parameters for the defvs_mknod() call - plus commentary), would it really be necessary to go through the mergemaster process? (from my POV, this is the most tedious and error prone part of the whole process). No, here it is not necessary. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Monday 27 June 2005 17:37, Denny White wrote: On Mon, 27 Jun 2005, RW wrote: On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. ... This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. You can break-out of portupgrade -arRF anytime you like, it's only fetching distfiles not upgrading anything. Normally portupgrade -Fa will fetch all the file you needs, but portupgrade -FRa is a bit more thorough. Really though you don't need to run with the -F option at all, unless you can't build online or want to prefetch files. If it's taking 40 hours though, it probably means that your cache of files is badly out-of-date and you are getting slow downloads - a clean pass that doesn't fetch anything shouldn't take more than a hour. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 28 Jun 2005, RW wrote: On Monday 27 June 2005 17:37, Denny White wrote: On Mon, 27 Jun 2005, RW wrote: On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. ... This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. You can break-out of portupgrade -arRF anytime you like, it's only fetching distfiles not upgrading anything. Normally portupgrade -Fa will fetch all the file you needs, but portupgrade -FRa is a bit more thorough. Really though you don't need to run with the -F option at all, unless you can't build online or want to prefetch files. If it's taking 40 hours though, it probably means that your cache of files is badly out-of-date and you are getting slow downloads - a clean pass that doesn't fetch anything shouldn't take more than a hour. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I finally broke out of it. I waited until it had done its cleaning was starting to fetch more files. I did a ls -alt on /var/db/pkg it was definitely installing/ reinstalling ports. Won't do that again. :) I had wanted to force the upgrade or downgrade, whatever, of several held ports. Now I think maybe it had something to do with me not updating perl the right way. My bad. I went back reread UPDATING found what I had missed. I did a man perl-after-upgrade reread all of that too followed the instructions. Looks like everything's back to normal. Thanks for the help. Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwW4cy0Ty5RZE55oRAkAKAKCYmKfN8PabPGawUE5M6FQqZBIm+QCdFCsU MTCJr7cUxTcCipfZH/uDvjY= =h6sQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. Portmanager is a good way to bring your ports up-to-date, but it also rebuilds all ports that depend on out-of date ports. It's a very slow process if you have a slow machine and most of your ports were up-to-date already, but try it for yourself. Portupgrade does a pretty good job if you follow UPDATING, and use the gnome script for major Gnome upgrades. If you want to force the rebuilding of all your ports then see pkg_glob(1) and portupgrade (1) for instructions on how to rebuild ports built after a given timestamp, as this gives you a restartable method. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
Is there a way to do all of this with packages, I've used ports system exclusively? The reason I ask is... well I don't like waiting 2 to 3 days for everything to rebuild and I take the defaults for most programs anyways. if I could do that and then just rebuild the apps I want with custom flags that would be cool... pkg_version -v says I have 176 out of date ports. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Monday 27 June 2005 16:39, Nikolas Britton wrote: Is there a way to do all of this with packages, I've used ports system exclusively? The reason I ask is... well I don't like waiting 2 to 3 days for everything to rebuild and I take the defaults for most programs anyways. if I could do that and then just rebuild the apps I want with custom flags that would be cool... pkg_version -v says I have 176 out of date ports. You can do it to a limited extent using portupgrade with the -P and -PP options, or the settings in pkgtools.conf. The trouble is finding a suitable source of packages, I've upgraded KDE this way using the fruitsalad servers at freebsd.kde.org, but the ordinary FreeBSD servers don't keep packages up-to-date for releases. It might work for 5-stable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, RW wrote: On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. Portmanager is a good way to bring your ports up-to-date, but it also rebuilds all ports that depend on out-of date ports. It's a very slow process if you have a slow machine and most of your ports were up-to-date already, but try it for yourself. Portupgrade does a pretty good job if you follow UPDATING, and use the gnome script for major Gnome upgrades. If you want to force the rebuilding of all your ports then see pkg_glob(1) and portupgrade (1) for instructions on how to rebuild ports built after a given timestamp, as this gives you a restartable method. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. Any help/feedback on this will be GREATLY appreciated. :) Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwCs6y0Ty5RZE55oRAj6LAJ4wuENN2VAn5IlWUeRsPVps5nBgcQCgtsRr +YpDWuFkojneBoJkl3qk4Jk= =DrUN -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On 6/27/05, Denny White [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, Nikolas Britton wrote: This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. Any help/feedback on this will be GREATLY appreciated. :) Denny White You shouldn't have any problems if you do that but kill it at the beginning of the next build, not when it's cleaning. Thanks so much for the personal speedy reply. I've worked for a month getting this system to about where I want it, I hate to see it all go down the tubes. Sure glad you straightened me out on when to break out, too. I see you didn't put in a cc to freebsd-questions, so I guess I won't either. After breaking out of the loop, what's the best thing to do at that point? The only way I could come up with to try to start is: cvsup ports-supfile portsdb -Uu portversion -l portupgrade -arR (no F this time) Just restart portupgrade without the F flag, it will pick-up where it left off. If I can get things back right, I'll just learn to live with the held ports. I never remember telling it to hold anything, it's probably pretty apparent I don't understand as much as I should about portupgrade. I learned what I know from Dru Lavigne's blogs at Oreilly, until I fat-fingered the F without thinking, it was working okay, except for the held ports. Thanks again for your help. Denny White I'm not sure what you mean by held ports? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, Nikolas Britton wrote: On 6/27/05, Denny White [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, Nikolas Britton wrote: This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. Any help/feedback on this will be GREATLY appreciated. :) Denny White You shouldn't have any problems if you do that but kill it at the beginning of the next build, not when it's cleaning. Thanks so much for the personal speedy reply. I've worked for a month getting this system to about where I want it, I hate to see it all go down the tubes. Sure glad you straightened me out on when to break out, too. I see you didn't put in a cc to freebsd-questions, so I guess I won't either. After breaking out of the loop, what's the best thing to do at that point? The only way I could come up with to try to start is: cvsup ports-supfile portsdb -Uu portversion -l portupgrade -arR (no F this time) Just restart portupgrade without the F flag, it will pick-up where it left off. If I can get things back right, I'll just learn to live with the held ports. I never remember telling it to hold anything, it's probably pretty apparent I don't understand as much as I should about portupgrade. I learned what I know from Dru Lavigne's blogs at Oreilly, until I fat-fingered the F without thinking, it was working okay, except for the held ports. Thanks again for your help. Denny White I'm not sure what you mean by held ports? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Held ports are listed in an array in /usr/local/etc/pkgtools.conf. Why I have any there beats me. I don't know enough about it yet to be able to give an answer. There are times when portupgrade will ask me questions about extra features in some port, but that's the only interaction I remember having with the program while it was running, as far as supplying answers to it. I never remember telling it to hold anything. Wish someone could help me get this through my thick noggin. :) I've been doing a lot of reading on it, I see where a lot of folks think you're better off deinstalling ports starting from scratch. Others prefer portsmanager, I think it's called. The reason I started using ports in the 1st place was to learn how to add extra features to progs that aren't installed by default, as in packages. Since I definitely ain't that sharp, I may start using pkgs more ports less. I'd rather have a smooth working install than the power to wipe out my system have to reinstall, at least until I ever get up to speed on things. Thank you very much for the help. Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwFloy0Ty5RZE55oRAqiDAJ44tORnQYQY7QA1o5fMDxFSouurRQCg0aNc aZRTHj3B/y0nmcbP8bhb3FE= =bDDM -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
Kirk Strauser wrote: On Saturday 25 June 2005 06:36 am, Erik Nørgaard wrote: It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. On toy systems, maybe. I've got 654 ports installed on the machine I'm typing this on, and I assure you that it's much, much faster to selectively upgrade a few of them rather than starting over from scratch. I think you overlooked one important thing in the original post, and in my post as well: We are talking about upgrading the entire system, not just a few ports. Upgrading a few ports is faster using portupgrade, yes. Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sat, 25 Jun 2005, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? I hesitate and don't want to screw up my machine. # portupgrade -a works fine, if you do it regularily, i.e. there isn't too much to be updated and thus not too much that could be messed up. Before you start you should check /usr/ports/UPDATING if there are any ports that need special treatmentâand make sure # pkgdb -F doesn't show any inconsistencies. Good Luck, Uli. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] * * Peter Ulrich Kruppa - Wuppertal - Germany * *___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sunday 26 June 2005 06:28 am, you wrote: We are talking about upgrading the entire system, not just a few ports. It really depends on how often you upgrade. If more than once a year or so, I maintain that portupgrade -a is faster than the OpenBSD-style uninstall and reinstlal process. -- Kirk Strauser pgpWLLCRSLTgP.pgp Description: PGP signature
Re: upgrading all ports
Alex Zbyslaw wrote: Erik Nørgaard wrote: portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. What, in your opinion, makes it unsuitable? I've used portugrade exclusively and never had trouble. Unsuitable if - it is slower than the altertative to deinstall all ports and reinstall. - thinks break I don't claim it won't work, I don't claim that things will break, but they may depending on what is being upgraded which was not mentioned in OP. The problem is that the double (up and down) recursive resolution of interdependencies quickly becomes very complex with the result that some ports may be updated multiple times, or that portupgrade will choke trying to figure out where to start. It then quickly becomes much faster to simply deinstall all ports and reinstall. It also lets you clean up any junk that may have been left for whatever reasons. And, then there are the general warnings about upgrading Gnome (not minor minor upgrades) eg 2.8 to 2.10, upgrading perl and friends, module paths etc. These are things that can ofcourse be resolved, I just found it easier to clean up the whole thing and reinstall it, see /usr/ports/UPDATING - there are numerous warnings on portupgrade. For single/few apps upgrade portupgrade is fine, or if the system is mostly up to date so a full upgrade will only affect a few packages. I have had my system serverely down after using portupgrade because of problems with dependencies on X11. OP did not mention how old the system to be upgraded is. So in the particular case it is dificult to say. But I assume that if he wants to upgrade his _entire_ system then I can assume significant updates to be done. Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On 6/25/05, Erik Nørgaard [EMAIL PROTECTED] wrote: portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. I recommend writing down a list of apps you need to be happy, deinstall everything and then install those apps. Dependencies comes along fine, and then whatever remains can be installed as needed. Anyway, the worst that can happen is that you will screw up some user app's - ok this is bad - but your system won't require a reinstall :-) Cheers, Erik With Gnome, KDE, etc. I completely agree with you, portupgrade always manages fudge something up. What are some easy ways to do this... lets say for example I updated to gnome 2.12 what would be an easy (automated) way to remove all of Gnome 2.10 and all of my GTK apps without removing KDE and my QT apps? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sun, 26 Jun 2005, Nikolas Britton wrote: On 6/25/05, Erik Nørgaard [EMAIL PROTECTED] wrote: portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. I recommend writing down a list of apps you need to be happy, deinstall everything and then install those apps. Dependencies comes along fine, and then whatever remains can be installed as needed. Anyway, the worst that can happen is that you will screw up some user app's - ok this is bad - but your system won't require a reinstall :-) Cheers, Erik With Gnome, KDE, etc. I completely agree with you, portupgrade always manages fudge something up. What are some easy ways to do this... lets say for example I updated to gnome 2.12 what would be an easy (automated) way to remove all of Gnome 2.10 and all of my GTK apps without removing KDE and my QT apps? You should download download the gnome upgrade script from www.freebsd.org/gnome and use it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] * * Peter Ulrich Kruppa - Wuppertal - Germany * *___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sat, 25 Jun 2005 13:22:56 +0200 Dick Hoogendijk [EMAIL PROTECTED] wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? I hesitate and don't want to screw up my machine. do you want to upgrade all upgradable ports on your machine ? i use portmanager -u and/or portupgrade -arvy i've started using portmanager since i've read good things about it many times, and it does indeed handle dependencies better than portupgrade however, if portmanager ends up with errors i use e.g. portupgrade -rf postgrey* to correct those errors i like the combination of both ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? I hesitate and don't want to screw up my machine. portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. I recommend writing down a list of apps you need to be happy, deinstall everything and then install those apps. Dependencies comes along fine, and then whatever remains can be installed as needed. Anyway, the worst that can happen is that you will screw up some user app's - ok this is bad - but your system won't require a reinstall :-) Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Saturday 25 June 2005 06:36 am, Erik Nørgaard wrote: It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. On toy systems, maybe. I've got 654 ports installed on the machine I'm typing this on, and I assure you that it's much, much faster to selectively upgrade a few of them rather than starting over from scratch. -- Kirk Strauser pgpXBLDkTdhIz.pgp Description: PGP signature
Re: upgrading all ports
On 25 Jun Kirk Strauser wrote: On Saturday 25 June 2005 06:36 am, Erik Nørgaard wrote: It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. On toy systems, maybe. I've got 654 ports installed on the machine I'm typing this on, and I assure you that it's much, much faster to selectively upgrade a few of them rather than starting over from scratch. I agree. Normally I go over usr/ports/UPDATING and handle the 'problem' cases. After that I do parts, like portupgrade -rR 'XFree86*', etc.. Never a problem. Sometimes I forget to use the -m BATCH=yes option and that's no fun. Options I really want are in my pkgtools.conf zo I don't need the selection screens.. I see no harm in using this -m switch like someone else wrote in this list. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 5.3 to 5.4
On Mon, Jun 20, 2005 at 06:00:34PM -0600, Cartoon Factory wrote: I am a fairly novice user of FreeBSD. I just recently built two boxes with 5.3, and now that 5.4 is out, I was curious how easy it would be to upgrade. The Migration guide deals with 4.X = 5... do I essentially follow the Source upgrade instructions? Is there a better/easier (for a novice!) way to do this, especially since I am already at 5.3? These boxes are active servers- how long would I be down? Is it even advisable for me to try this? there should be no problems upgrading from 5.3 to 5.4. while building userland / kernel and installing the kernel no downtime is necessary. it's always advisable to try the update first on a test system, even when this is your first time updating a freebsd system. downtime depends on how fast your servers are and how careful your are answering to mergemaster. on my athlon64 3200 rebooting + installworld + mergemaster takes about 15 minutes. read the following sections in the fabulous handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html and finally http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html so to upgrade to 5.4 tag=RELENG_5_4 is your friend. to give a short summary: 0) su - root 1) cd /usr/src 2) cvsup -g -L2 your supfile here || make update (see make.conf) 2.1) READ UPDATING 3) rm -rf /usr/obj/* 4) make buildworld 5) make buildkernel 6) make installkernel 7) reboot to singlelooser mode 8) mount -a 9) mergemaster -p 10) cd /usr/src make installworld 11) mergemaster 12) exit || reboot (to be sure everything works). but please, read the documentation mentioned above BEFORE starting your update, i'll give no warranty :-)! hth, toni -- Wer es einmal so weit gebracht hat, dass er nicht | toni at stderror dot at mehr irrt, der hat auch zu arbeiten aufgehoert| Toni Schmidbauer -- Max Planck | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading MySQL Without Wrecking Bacula
On 6/10/2005 10:25 PM Kevin Kinsey wrote: Drew Tomlinson wrote: I am a total noob regarding MySQL. I have version 3.23 installed on my 4.10 system. The only thing it's been used for and by is Bacula. I have never used it directly. But now I have reason to learn MySQL and feel it would be appropriate to start with a newer version. I see there's 4.1 and 5.0. Even though it's beta, I'm inclined to just start with 5.0 since my data will not be super critical and quite small. Basically I want t make a product database and display it via web pages. There are less than 10,000 products. I also don't see more than 2 or 3 clients accessing it at one time. Maybe in an extreme case there might be 10 clients. Overall, pretty small. So what must I do to upgrade from 3.23 to something newer and keep Bacula happy. I've read the Bacula web site and it claims to work with 3.23 and higher. I've browsed the MySQL site and see instructions to upgrade from 3.23 to 4.0, 4.0 to 4.1, and upgrading to 5.0. However I'm sure I don't really need to upgrade in steps? Any guidance, advice, and/or links to tutorials would be greatly appreciated. Thanks, Drew I like mysqldump for easy to recreate backups: $ mysqldump sometable sometable.sql To restore, you need to add a statement to the top of the file, like use sometable. Then: $ mysqladmin create cometable and, finally: $mysql sometable.sql And everything should be good to go. Thanks for the tip. It gives me somewhere to start. Sorry I'm not much more help. I use portupgrade and/or portmanager to keep things somewhat up to date, but I don't know if there would be any gotchas with that and Bacula or not. I'd tend to think that as long as I had all my databases backed up, I could uninstall 323 and install something from the 4X or 5X line and not have too many issues. Me too. portupgrade is a great tool. I agree that if I have the databases backed up, I should be able to restore. This is just my home system so if the worst happened and I lost my complete bacula database, it still wouldn't be the end of the world (unless my hard drive crashed before I got bacula running again). You might want to learn a little about using the MySQL monitor itself, first, in 3.23; a little knowledge of MySQL syntax would add to your confidence in restoring the data, I would think . . . I've fiddled around with MySQL a little so far. Webmin provides an easy interface to administering MySQL users, databases, etc. and that has been very helpful. Now I just have to learn what real commands Webmin calls when performing these functions. I suspect it uses mysqladmin. Thanks for your reply, Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, More! http://www.alchemistswarehouse.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading MySQL Without Wrecking Bacula
Drew Tomlinson wrote: I am a total noob regarding MySQL. I have version 3.23 installed on my 4.10 system. The only thing it's been used for and by is Bacula. I have never used it directly. But now I have reason to learn MySQL and feel it would be appropriate to start with a newer version. I see there's 4.1 and 5.0. Even though it's beta, I'm inclined to just start with 5.0 since my data will not be super critical and quite small. Basically I want t make a product database and display it via web pages. There are less than 10,000 products. I also don't see more than 2 or 3 clients accessing it at one time. Maybe in an extreme case there might be 10 clients. Overall, pretty small. So what must I do to upgrade from 3.23 to something newer and keep Bacula happy. I've read the Bacula web site and it claims to work with 3.23 and higher. I've browsed the MySQL site and see instructions to upgrade from 3.23 to 4.0, 4.0 to 4.1, and upgrading to 5.0. However I'm sure I don't really need to upgrade in steps? Any guidance, advice, and/or links to tutorials would be greatly appreciated. Thanks, Drew I like mysqldump for easy to recreate backups: $ mysqldump sometable sometable.sql To restore, you need to add a statement to the top of the file, like use sometable. Then: $ mysqladmin create cometable and, finally: $mysql sometable.sql And everything should be good to go. Sorry I'm not much more help. I use portupgrade and/or portmanager to keep things somewhat up to date, but I don't know if there would be any gotchas with that and Bacula or not. I'd tend to think that as long as I had all my databases backed up, I could uninstall 323 and install something from the 4X or 5X line and not have too many issues. You might want to learn a little about using the MySQL monitor itself, first, in 3.23; a little knowledge of MySQL syntax would add to your confidence in restoring the data, I would think . . . HTH, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading from 5.3 to 5.4
Has anybody done this yet? Any gotcha's, or is it a fairly smooth upgrade? Hi! Yes, I've done that a week ago, and everything went well. You only have to be careful with your compile options (in /etc/make.conf) if you have increased the optimization level for compiling ports (don't use more than -O). Just follow the handbook instructions (new procedure) and you're on your way. In case something fails and if you're not familiar with the booting process, read the section about how to boot your old kernel if the new one doesn't work. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading from 5.3 to 5.4
I can confirm here as well, went very smoothly on all counts. Tony On Mon, 23 May 2005 [EMAIL PROTECTED] wrote: Has anybody done this yet? Any gotcha's, or is it a fairly smooth upgrade? Hi! Yes, I've done that a week ago, and everything went well. You only have to be careful with your compile options (in /etc/make.conf) if you have increased the optimization level for compiling ports (don't use more than -O). Just follow the handbook instructions (new procedure) and you're on your way. In case something fails and if you're not familiar with the booting process, read the section about how to boot your old kernel if the new one doesn't work. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading from 5.3 to 5.4
Duane Winner wrote: Has anybody done this yet? Any gotcha's, or is it a fairly smooth upgrade? It was a piece of cake to me. YMMV, as always :) bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading from 5.3 to 5.4
On Monday 23 May 2005 09:01, the author Andrea Venturoli contributed to the dialogue on Re: upgrading from 5.3 to 5.4: Duane Winner wrote: Has anybody done this yet? Any gotcha's, or is it a fairly smooth upgrade? It was a piece of cake to me. YMMV, as always :) I have held off from 5.3 5.4 because some people are reporting difficulties with java sdk's on 5.4 plus few other niggles. Until there is some certainty that those reports are no longer justified I would not make the jump myself. David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from Samba 2 to Samba 3
On Wed, 18 May 2005, Roger Merritt wrote: /usr/ports/UPDATING. Does anyone have any gotchas I should be aware of? You running 4.X or 5.X One FreeBSD gotach I recall was the need to have samba_enable=YES in /etc/rc.conf As for Samba... I think there was one (maybe two) options in smb.conf which were no longer valid and I just took them out and all was well. I only have samba on 2 very small networks, but other than the smb.conf options have not had any issues/problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from Samba 2 to Samba 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 18 May 2005, Roger Merritt wrote: I've just become aware that samba.org is no longer supporting Samba 2 (which has served me well for so long) and I should upgrade to Samba 3, which is now the stable version. I don't find any warnings about it in /usr/ports/UPDATING. Does anyone have any gotchas I should be aware of? Hi, you should definitely take a look into the official Samba-3 HOWTO. http://us3.samba.org/samba/docs/Samba-HOWTO-Collection.pdf there is a separate part about migration and updating. you should also read about the Account Information Databases in part-III/chapter 10, as this is importand to reuse your old smbpasswd or passdb.tdb file. good luck ;-) Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCitbiSPOsGF+KA+MRAhAqAJoCVyfh4ncLnS9S5ZK7/qgXSr8CYwCdF8Iw fr/opIoZLDrtZ6tjUWRKdtI= =67og -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading from Samba 2 to Samba 3
On Tue, 17 May 2005, Ted Mittelstaedt wrote: It's great if you like your server applications to be twice as complicated as before. Seriously, though, you can turn off all the fru-fru and set it up pretty much equivalent to a samba 2 server. The fru-fru is needed if you have a lot of XP stuff and you want to interoperate with a Microsoft AD. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roger Merritt Sent: Tuesday, May 17, 2005 7:40 PM To: freebsd-questions@freebsd.org Subject: Upgrading from Samba 2 to Samba 3 I've just become aware that samba.org is no longer supporting Samba 2 (which has served me well for so long) and I should upgrade to Samba 3, which is now the stable version. I don't find any warnings about it in /usr/ports/UPDATING. Does anyone have any gotchas I should be aware of? I recently heard a lecture about the evolution of Samba 4. Seems to me you can't understand it unless your are Microsoft certified systems engineer with lots of special active directory knowledge ... ;-) Best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading from Samba 2 to Samba 3
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joerg Pulz Sent: Tuesday, May 17, 2005 10:47 PM To: Roger Merritt Cc: freebsd-questions@freebsd.org Subject: Re: Upgrading from Samba 2 to Samba 3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 18 May 2005, Roger Merritt wrote: I've just become aware that samba.org is no longer supporting Samba 2 (which has served me well for so long) and I should upgrade to Samba 3, which is now the stable version. I don't find any warnings about it in /usr/ports/UPDATING. Does anyone have any gotchas I should be aware of? Hi, you should definitely take a look into the official Samba-3 HOWTO. http://us3.samba.org/samba/docs/Samba-HOWTO-Collection.pdf there is a separate part about migration and updating. you should also read about the Account Information Databases in part-III/chapter 10, as this is importand to reuse your old smbpasswd or passdb.tdb file. If you have one. On smaller networks I use the UNIX password file and just switch on unencrypted passwords on the Windows clients. When you have 12-15 people in the office, and the server is in an unlocked broom closet, your kidding yourself if you think that encrypting passwords on the wire will do anything whatsoever to increase your data security. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading from Samba 2 to Samba 3
It's great if you like your server applications to be twice as complicated as before. Seriously, though, you can turn off all the fru-fru and set it up pretty much equivalent to a samba 2 server. The fru-fru is needed if you have a lot of XP stuff and you want to interoperate with a Microsoft AD. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roger Merritt Sent: Tuesday, May 17, 2005 7:40 PM To: freebsd-questions@freebsd.org Subject: Upgrading from Samba 2 to Samba 3 I've just become aware that samba.org is no longer supporting Samba 2 (which has served me well for so long) and I should upgrade to Samba 3, which is now the stable version. I don't find any warnings about it in /usr/ports/UPDATING. Does anyone have any gotchas I should be aware of? -- Roger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading net-snmp-5.2.1 gives error
On Monday 28 March 2005 08:01, gustaaf wijnands wrote: Thomas Foster wrote: Does it compile WITH_PERL=NO ? It doesn't compile WITHOUT_PERL=yes what version of autoconf and libtool are you using? pkg_info |grep autoconf autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms pkg_info |grep libtool libtool-1.3.5_2 Generic shared library support script (version 1.3) libtool-1.5.10_1Generic shared library support script (version 1.5) and perl -v returns what version? perl -v This is perl, v5.8.6 built for i386-freebsd-64int perl -V Summary of my perl5 (revision 5 version 8 subversion 6) configuration: Platform: osname=freebsd, osvers=5.3-release-p5, archname=i386-freebsd-64int uname='freebsd laptop.intern 5.3-release-p5 freebsd 5.3-release-p5 #7: wed ja n 26 21:10:23 cet 2005 [EMAIL PROTECTED]:usrobjusrsrcsysmykernel i386 ' config_args='-sde -Dprefix=/usr/local -Darchlib=/usr/local/lib/perl5/5.8.6/mach -Dprivlib=/usr/local/lib/perl5/5.8.6 -Dman3dir=/usr/local/lib/perl5/5.8.6/perl /man/man3 -Dman1dir=/usr/local/man/man1 -Dsitearch=/usr/local/lib/perl5/site_perl /5.8.6/mach -Dsitelib=/usr/local/lib/perl5/site_perl/5.8.6 -Dscriptdir=/usr/local /bin -Dsiteman3dir=/usr/local/lib/perl5/5.8.6/man/man3 -Dsiteman1dir=/usr/local/m an/man1 -Ui_malloc -Ui_iconv -Uinstallusrbinperl -Dcc=cc -Doptimize=-O -pipe -Du seshrplib -Dccflags=-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.6/BSDPAN -Ud_dosuid -Ui_gdbm -Dusethreads=n -Dusemymalloc=y -Duse64bitint' hint=recommended, useposix=true, d_sigaction=define usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=define use64bitall=undef uselongdouble=undef usemymalloc=y, bincompat5005=undef Compiler: cc='cc', ccflags ='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.6/BSDPAN -DHAS_FP SETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include', optimize='-O -pipe ', cppflags='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.6/BSDPAN -DHAS_FPSETMASK - DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include' ccversion='', gccversion='3.4.2 [FreeBSD] 20040728', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseek size=8 alignbytes=4, prototype=define Linker and Libraries: ld='cc', ldflags =' -Wl,-E -L/usr/local/lib' libpth=/usr/lib /usr/local/lib libs=-lm -lcrypt -lutil perllibs=-lm -lcrypt -lutil libc=, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' -Wl,-R/usr/local/ lib/perl5/5.8.6/mach/CORE' cccdlflags='-DPIC -fPIC', lddlflags='-shared -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: USE_64_BIT_INT USE_LARGE_FILES Locally applied patches: SUIDPERLIO0 - fix PERLIO_DEBUG local root exploit (CAN-2005-0155) SUIDPERLIO1 - fix PERLIO_DEBUG buffer overflow (CAN-2005-0156) Built under freebsd Compiled at Feb 6 2005 20:47:58 @INC: /usr/local/lib/perl5/site_perl/5.8.6/mach /usr/local/lib/perl5/site_perl/5.8.6 /usr/local/lib/perl5/site_perl/5.8.5 /usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.6/BSDPAN /usr/local/lib/perl5/5.8.6/mach /usr/local/lib/perl5/5.8.6 . what happens after running ldconfig -R still the same error. Any idea? Thank for helping me Hi Gustaaf, I'm having exactly the same problem upgrading net-snmp as you. Have you managed to fix the problem yet? My system is pretty much identical to your's, except for autoconf: %pkg_info | grep autoconf autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.53_3 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms Here's the output when I try to build it without perl: daemon:/usr/ports/net-mgmt/net-snmp % sudo make -DWITHOUT_PERL=YES === Building for net-snmp-5.2.1_2 making all in /usr/ports/net-mgmt/net-snmp/work/net-snmp-5.2.1/snmplib making all in /usr/ports/net-mgmt/net-snmp/work/net-snmp-5.2.1/agent making all in
Re: Upgrading from 5.3-RELEASE-p5 to p6
On Monday 28 March 2005 16:46, you wrote: I just upgraded a test machine from 5.3-RELEASE-p5 to 5.3-RELEASE-p6. The make buildworld went fine. When I tried to make buildkernel it kept saying that: kernel build for GENERIC complete on xx.xx.xx time I tried using the old way of bulding a kernel and that went without issue. I'm bringing this up to see if it's a bug or if it's just something dorked up on my end. hrmm, I should clarify that I am doing: #make buildkernel KERNCONF=MYKERNEL -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from 5.3-RELEASE-p5 to p6
On Mon, Mar 28, 2005 at 04:46:31PM -0600, Josh Paetzel wrote: I just upgraded a test machine from 5.3-RELEASE-p5 to 5.3-RELEASE-p6. The make buildworld went fine. When I tried to make buildkernel it kept saying that: kernel build for GENERIC complete on xx.xx.xx time I tried using the old way of bulding a kernel and that went without issue. I'm bringing this up to see if it's a bug or if it's just something dorked up on my end. I don't see anything wrong, here. What did you do? What did you expect? What did you get? The basic way would be: cd /usr/src/ make buildworld make buildkernel KERNCONF=MYKERNEL make installkernel KERNCONF=MYKERNEL make installworld The exact procedure can be found in the handbook: www.freebsd.org/handbook/ -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading net-snmp-5.2.1 gives error
Does it compile WITH_PERL=NO ? what version of autoconf and libtool are you using? and perl -v returns what version? what happens after running ldconfig -R T - Original Message - From: gustaaf wijnands [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Sunday, March 27, 2005 1:35 PM Subject: upgrading net-snmp-5.2.1 gives error Hello all, portupgrading net-snmp-5.2.1 doesn't seem to work on my machine: /libexec/ld-elf.so.1: /usr/local/lib/perl5/site_perl/5.8.6/mach/auto/SNMP/SNMP.so: Undefined symbol perl_get_sv *** Error code 1 Stop in /usr/ports/net-mgmt/net-snmp/work/net-snmp-5.2.1. *** Error code 1 Stop in /usr/ports/net-mgmt/net-snmp. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade3553.1 make ** Fix the problem and try again. I am running FreeBSD 5.3-RELEASE-p5 #7. Anybody any idea what can be wrong and what can be done about it? Thanks, -- Gustaaf Wijnands ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading net-snmp-5.2.1 gives error
Thomas Foster wrote: Does it compile WITH_PERL=NO ? It doesn't compile WITHOUT_PERL=yes what version of autoconf and libtool are you using? pkg_info |grep autoconf autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms pkg_info |grep libtool libtool-1.3.5_2 Generic shared library support script (version 1.3) libtool-1.5.10_1Generic shared library support script (version 1.5) and perl -v returns what version? perl -v This is perl, v5.8.6 built for i386-freebsd-64int perl -V Summary of my perl5 (revision 5 version 8 subversion 6) configuration: Platform: osname=freebsd, osvers=5.3-release-p5, archname=i386-freebsd-64int uname='freebsd laptop.intern 5.3-release-p5 freebsd 5.3-release-p5 #7: wed ja n 26 21:10:23 cet 2005 [EMAIL PROTECTED]:usrobjusrsrcsysmykernel i386 ' config_args='-sde -Dprefix=/usr/local -Darchlib=/usr/local/lib/perl5/5.8.6/mach -Dprivlib=/usr/local/lib/perl5/5.8.6 -Dman3dir=/usr/local/lib/perl5/5.8.6/perl /man/man3 -Dman1dir=/usr/local/man/man1 -Dsitearch=/usr/local/lib/perl5/site_perl /5.8.6/mach -Dsitelib=/usr/local/lib/perl5/site_perl/5.8.6 -Dscriptdir=/usr/local /bin -Dsiteman3dir=/usr/local/lib/perl5/5.8.6/man/man3 -Dsiteman1dir=/usr/local/m an/man1 -Ui_malloc -Ui_iconv -Uinstallusrbinperl -Dcc=cc -Doptimize=-O -pipe -Du seshrplib -Dccflags=-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.6/BSDPAN -Ud_dosuid -Ui_gdbm -Dusethreads=n -Dusemymalloc=y -Duse64bitint' hint=recommended, useposix=true, d_sigaction=define usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=define use64bitall=undef uselongdouble=undef usemymalloc=y, bincompat5005=undef Compiler: cc='cc', ccflags ='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.6/BSDPAN -DHAS_FP SETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include', optimize='-O -pipe ', cppflags='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.6/BSDPAN -DHAS_FPSETMASK - DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include' ccversion='', gccversion='3.4.2 [FreeBSD] 20040728', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseek size=8 alignbytes=4, prototype=define Linker and Libraries: ld='cc', ldflags =' -Wl,-E -L/usr/local/lib' libpth=/usr/lib /usr/local/lib libs=-lm -lcrypt -lutil perllibs=-lm -lcrypt -lutil libc=, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' -Wl,-R/usr/local/ lib/perl5/5.8.6/mach/CORE' cccdlflags='-DPIC -fPIC', lddlflags='-shared -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: USE_64_BIT_INT USE_LARGE_FILES Locally applied patches: SUIDPERLIO0 - fix PERLIO_DEBUG local root exploit (CAN-2005-0155) SUIDPERLIO1 - fix PERLIO_DEBUG buffer overflow (CAN-2005-0156) Built under freebsd Compiled at Feb 6 2005 20:47:58 @INC: /usr/local/lib/perl5/site_perl/5.8.6/mach /usr/local/lib/perl5/site_perl/5.8.6 /usr/local/lib/perl5/site_perl/5.8.5 /usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.6/BSDPAN /usr/local/lib/perl5/5.8.6/mach /usr/local/lib/perl5/5.8.6 . what happens after running ldconfig -R still the same error. Any idea? Thank for helping me -- Gustaaf Wijnands ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 4.10-STABLE
[redirected to questions@ since this is not -net stuff] Hi, Julius, 2005-03-16 17:01 +0300Julius Kidubuka Hi all, I am trying to upgrade from 4.10-RELEASE to 4.10-STABLE and I have gone through the following steps; 1. make buildworld 2. make buildkernel KERNCONF=MYKERN 3. make installkernel KERNCONF=MYKERN 4. booted into single user mode and did, mount -u /, mount -a 5. make installworld 6. mergemaster 7. then finally rebooted My problem is after I have rebooted and issued the command uname -a, I still find that am running 4.10-RELEASE yet I have actually gone through all the steps above without any errors at all. Is there anything I could be doing wrong? Are you absolutely sure that you are sync'ing with 4-STABLE (now 4.11-STABLE), which is identified by RELENG_4? If you are sync'ing with RELENG_4_10, that's the 4.10-RELEASE security branch. Cheers, -- Xin LI delphij delphij net http://www.delphij.net/ signature.asc Description: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=BF=A1=E4=BB=B6=E7=9A=84=E6=95=B0?= =?UTF-8?Q?=E5=AD=97=E7=AD=BE=E5=90=8D=E9=83=A8?= =?UTF-8?Q?=E5=88=86?=
Re: Upgrading perl 5.8
On Mon, Feb 28, 2005 at 01:34:30PM +0100, Stefan Cars wrote: Hi! I'm upgrading perl 5.8 from the ports on a FreeBSD 5.3 machine, the problem is that alot of my installed modules doesn't work after the update (just a minor update from 5.8.2 to 5.8.6), probably becuase the @INC changed and did not include the mach directory of 5.8.2. Is this right ? Why can't it include the 5.8.2 mach dir ? There's nothing to stop you adding the 5.8.2 directories to @INC. But the cleanest way to solve this is to upgrade everything else on your system that depends on Perl. Portmanager is really good for this sort of task. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpTLd0dUgmHh.pgp Description: PGP signature
Re: Upgrading perl 5.8
Stefan Cars wrote: Hi! I'm upgrading perl 5.8 from the ports on a FreeBSD 5.3 machine, the problem is that alot of my installed modules doesn't work after the update (just a minor update from 5.8.2 to 5.8.6), probably becuase the @INC changed and did not include the mach directory of 5.8.2. Is this right ? Why can't it include the 5.8.2 mach dir ? Please read /usr/ports/UPDATING Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading hardware from P3 to AMD 64
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of RW Sent: Sunday, February 27, 2005 23:06 To: freebsd-questions@freebsd.org Subject: Upgrading hardware from P3 to AMD 64 I'm thinking about upgrading my hardware from an Intel P3 to an AMD 64, and replacing the graphics card, without buying a new hard disk. Has anyone done this kind of thing successfully? I've recompiled kernel+world for 686 and I've done a portupgrade -fR on cvsup and portupgrade. Most likely your system would stop booting up if you try to run a p3 kernel on a amd64. And AFAIK you *cant* build for 64 bit architecture on a 32 bit one. Typical motherboards now have a couple of sata connections in addition to the normal ide connections. Can I expect my current ide drives to still be ad0 and ad1? Yeh they would remain ad0 and ad1. The SATAs are generally at higher numbers. For me ad10 onwards are the SATA controllers. Regards, S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India smime.p7s Description: S/MIME cryptographic signature
Re: Upgrading hardware from P3 to AMD 64
On Sunday 27 February 2005 17:49, Subhro wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of RW Sent: Sunday, February 27, 2005 23:06 To: freebsd-questions@freebsd.org Subject: Upgrading hardware from P3 to AMD 64 I'm thinking about upgrading my hardware from an Intel P3 to an AMD 64, and replacing the graphics card, without buying a new hard disk. Has anyone done this kind of thing successfully? I've recompiled kernel+world for 686 and I've done a portupgrade -fR on cvsup and portupgrade. Most likely your system would stop booting up if you try to run a p3 kernel on a amd64. And AFAIK you *cant* build for 64 bit architecture on a 32 bit one. As I said, I'm recompiling for 686 (which I think is pentium pro), my undestanding is that the AMD 64 is back-compatible to 686. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading hardware from P3 to AMD 64
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of RW Sent: Sunday, February 27, 2005 23:29 To: freebsd-questions@freebsd.org Subject: Re: Upgrading hardware from P3 to AMD 64 On Sunday 27 February 2005 17:49, Subhro wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of RW Sent: Sunday, February 27, 2005 23:06 To: freebsd-questions@freebsd.org Subject: Upgrading hardware from P3 to AMD 64 I'm thinking about upgrading my hardware from an Intel P3 to an AMD 64, and replacing the graphics card, without buying a new hard disk. Has anyone done this kind of thing successfully? I've recompiled kernel+world for 686 and I've done a portupgrade -fR on cvsup and portupgrade. Most likely your system would stop booting up if you try to run a p3 kernel on a amd64. And AFAIK you *cant* build for 64 bit architecture on a 32 bit one. As I said, I'm recompiling for 686 (which I think is pentium pro), my undestanding is that the AMD 64 is back-compatible to 686. Negative. AFAIK there are incompatible in both the ways. Regards S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India smime.p7s Description: S/MIME cryptographic signature
Re: Upgrading hardware from P3 to AMD 64
On Sunday 27 February 2005 18:12, Subhro wrote: As I said, I'm recompiling for 686 (which I think is pentium pro), my undestanding is that the AMD 64 is back-compatible to 686. Negative. AFAIK there are incompatible in both the ways. I found this thread: http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2004-September/thread.html#2110 which shows that there are people using the i386 version on the AMD64. It makes sense, since there aren't dedicated amd64 versions of windows applications. I must admit, I'd forgoten it has it's own FreBSD installation ISOs, so I guess there is no smooth upgrade path from i386 to amd64. Maybe I'll do that with 5.4. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading hardware from P3 to AMD 64
On 02/27/05 12:36:04, RW wrote: I'm thinking about upgrading my hardware from an Intel P3 to an AMD 64, and replacing the graphics card, without buying a new hard disk. Has anyone done this kind of thing successfully? I've recompiled kernel+world for 686 and I've done a portupgrade -fR on cvsup and portupgrade. Typical motherboards now have a couple of sata connections in addition to the normal ide connections. Can I expect my current ide drives to still be ad0 and ad1? As long as the cpu you optimized for is a 686 only(no CPUTYPE= or - march or -mcpu), then yeah. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading to a specified version?
windlamf wrote: Thanks! If I specify the parameter of tag as RELENG_4, then does cvsup only fetch the latest source code of my current system version? Well, RELENG_4 a.k.a. FreeBSD 4-stable is FreeBSD 4.11 (the latest release) + security fixes + bug fixes or small backports from the -current branch, although this is not very likely for FreeBSD 4 anymore. RELENG_4_11 on the other and the security branch of FreeBSD 4.11 + security fixes. If you want to run FreeBSD 4 on your machine, I'd recommend any of the two above branches (since FreeBSD 5 is the new stable branch, RELENG_4 and RELENG_4_11 won't differ a lot). HTH, Simon pgpuGyuIps1fo.pgp Description: PGP signature
Re: upgrading to a specified version?
windlamf wrote: Hi all ! The version of my current system is 4.7, and I want to upgrade the system to 4.11.From the description of UPDATING in /usr/src, I know that I have alternatives among severval stable versions. But how can I specify the right version which I want the system upgraded to? If I want my fb upgraded to 4.10, what can I do? put this to your supfile: *default tag=RELENG_4_10 then run # cvsup supfile As far as I know, the handbook does not mention things like this. So I turn to you guys for help. Thanks Andy - Do You Yahoo!? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonaletel: +41-91-6108561 6928 Mannofax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading to a specified version?
windlamf wrote: Hi all ! The version of my current system is 4.7, and I want to upgrade the system to 4.11.From the description of UPDATING in /usr/src, I know that I have alternatives among severval stable versions. But how can I specify the right version which I want the system upgraded to? If I want my fb upgraded to 4.10, what can I do? As far as I know, the handbook does not mention things like this. So I turn to you guys for help. The handbook elaborates quite verbosely on this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html Simon pgpWCooalhLBS.pgp Description: PGP signature
RE: upgrading to a specified version?
Windlamf, Also see chapter 25... bob X Robert Kim, Wireless Internet Wifi Hotspot Advisor http://wireless-internet-broadband-service.com https://evdo.sslpowered.com/wifi-hotspot-router.htm 2611 S Pacific Coast Highway 101 Cardiff by the Sea CA 92007 : 206 984 0880 Wireless Internet Service Is ONLY Broadband with Broadband Customer Service(tm) OUR QUEST: To Kill the Cubicle! (SM) ---Shalo -;-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Barner Sent: Thursday, February 17, 2005 9:30 AM To: windlamf Cc: freebsd-questions@freebsd.org Subject: Re: upgrading to a specified version? windlamf wrote: Hi all ! The version of my current system is 4.7, and I want to upgrade the system to 4.11.From the description of UPDATING in /usr/src, I know that I have alternatives among severval stable versions. But how can I specify the right version which I want the system upgraded to? If I want my fb upgraded to 4.10, what can I do? As far as I know, the handbook does not mention things like this. So I turn to you guys for help. The handbook elaborates quite verbosely on this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.h tml Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading to a specified version?
Thanks! If I specify the parameter of tag as RELENG_4, then does cvsup only fetch the latest source code of my current system version? Andy Roberto Nunnari [EMAIL PROTECTED] wrote: windlamf wrote: Hi all ! The version of my current system is 4.7, and I want to upgrade the system to 4.11.From the description of UPDATING in /usr/src, I know that I have alternatives among severval stable versions. But how can I specify the right version which I want the system upgraded to? If I want my fb upgraded to 4.10, what can I do? put this to your supfile: *default tag=RELENG_4_10 then run # cvsup supfile As far as I know, the handbook does not mention things like this. So I turn to you guys for help. Thanks Andy - Do You Yahoo!? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonale tel: +41-91-6108561 6928 Manno fax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Do You Yahoo!? 150MP3 1G1000 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 5.3
On Thursday 17 February 2005 11:18 pm, Joachim Dagerot wrote: I just cvsuped to freebsd-stable and buildworld. No problems. Now I want to build the kernel with the same conf as I used for the last years (5.x), but I ran into problems. device pcm is unknown. Is this a 'common' problem, or am I in deep sh*t? //Joche [EMAIL PROTECTED]:/usr/src/ make buildkernel KERNCONF=JOCHE20050218 -- Kernel build for JOCHE20050218 started on Fri Feb 18 06:16:37 CET 2005 -- === JOCHE20050218 mkdir -p /usr/obj/usr/src/sys -- stage 1: configuring the kernel -- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/lega cy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i38 6/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/gam es:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/JOCHE20050218 /usr/src/sys/i386/conf/JOCHE20050218 config: Error: device pcm is unknown config: 1 errors *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Sound configuration has changed. See the UPDATING documentation. Andrew Gould ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 5.3
On 2005-02-18 Andrew L. Gould wrote: On Thursday 17 February 2005 11:18 pm, Joachim Dagerot wrote: I just cvsuped to freebsd-stable and buildworld. No problems. Now I want to build the kernel with the same conf as I used for the last years (5.x), but I ran into problems. device pcm is unknown. Is this a 'common' problem, or am I in deep sh*t? //Joche [EMAIL PROTECTED]:/usr/src/ make buildkernel KERNCONF=JOCHE20050218 -- Kernel build for JOCHE20050218 started on Fri Feb 18 06:16:37 CET 2005 -- === JOCHE20050218 mkdir -p /usr/obj/usr/src/sys -- stage 1: configuring the kernel -- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/lega cy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i38 6/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/gam es:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/JOCHE20050218 /usr/src/sys/i386/conf/JOCHE20050218 config: Error: device pcm is unknown config: 1 errors *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Sound configuration has changed. See the UPDATING documentation. I did, and searched for 'pcm' with no hit. Now I read it in more detail, and there's a change in the sound card device naming (or so). I'm just compiling the kernel without sound card support for now, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading FreeBSD
I was wondering if it is possible to upgrade from FreeBSD 3.2 to 5.3 without doing a fresh install, and if possible what issues might I have. It might be possible, but it may be less effort to just do the fresh install. You would have to do several stages of upgrades. I don't know anyone who is saying it can be done in one fell swoop as just an upgrade. jerry Thanks Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading FreeBSD
On Wed, Feb 02, 2005 at 10:13:11AM -0500, Greg Foster wrote: I was wondering if it is possible to upgrade from FreeBSD 3.2 to 5.3 without doing a fresh install, and if possible what issues might I have. Possible: Yes. Recommended: Absolutely not! You will almost certainly have to do it in several steps. The sequence 3.2 - 3.5.1 3.5.1 - 4.1 4.1 - 4.11 4.11 - 5.3 *should* work, but no guarantees. Remember to read /usr/src/UPDATING very carefully before each step - most problems that you *will* encounter are documented there. The sequence backup all data make a fresh install of 5.3 restore data from backup will almost certainly be quicker, simpler, and less prone to catastrophic failure. (Making a backup of all important data is a *very* good idea anyway.) -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading FreeBSD
On 02 Feb Erik Trulsson wrote: The sequence backup all data make a fresh install of 5.3 restore data from backup will almost certainly be quicker, simpler, and less prone to catastrophic failure. (Making a backup of all important data is a *very* good idea anyway.) You're so right ;-) Main problem (at least to me) is almost everytime *what* is important data and what is not? I don't mean my personal stuff (that's the easy part), but more, which control files and (fine) tunings on the running system do I not want to loose? /etc and /usr/local/etc are very important data dirs, but what others are too? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11 ++ FreeBSD 5.3 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading FreeBSD
Dick Hoogendijk wrote: [ ... ] You're so right ;-) Main problem (at least to me) is almost everytime *what* is important data and what is not? I don't mean my personal stuff (that's the easy part), but more, which control files and (fine) tunings on the running system do I not want to loose? /etc and /usr/local/etc are very important data dirs, but what others are too? You should backup all of your data, and stop worrying about missing something, rather than backup only some data and hope not to find out later that you didn't backup something you needed. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading FreeBSD
On Wed, Feb 02, 2005 at 04:49:23PM +0100, Dick Hoogendijk wrote: You're so right ;-) Main problem (at least to me) is almost everytime *what* is important data and what is not? I don't mean my personal stuff (that's the easy part), but more, which control files and (fine) tunings on the running system do I not want to loose? /etc and /usr/local/etc are very important data dirs, but what others are too? Save everything, just to be sure. The following strategy has helped me to keep track of run-control files: In my home-directory, I've created a directory named setup. If I want to change one of the run-control files, the first thing I do is make a copy of that file in ~/setup (or a relevant subdirectory), where I check the unmodified version in rcs(1) with ci(1). Next I check out the files (with co(1)), make the changes I want and check them in again. The last step is to copy the modified run-control file back where it belongs. This way you'll have a single point where all changed run-control files are stored, and thanks to RCS you can even easily see what the changes were between versions. Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpuTre11hA6v.pgp Description: PGP signature
Re: upgrading from 5.3 to current
This is rather a nubee question.. I am used to OBSD and how to update my sources...but seem to be missing something with FREEBSD. I installed 5.3 release and all I want to do now is update the source files on the disk to current. Very easy, all explained in the handbook. If on Intel, cvsup is your friend. Are you sure you'll want to install CURRENT, by the way? - In the FreeBSD context CURRENT is more like development alpha version, STABLE branch is more like beta, and RELENG branches are the bug and security fix branches of the original release. All explained in the handbook. Does someone have a web page that can show these steps? http://www.freebsd.org/handbook, See chapter 19 and appendix A. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading from 5.3 to current
At 08:06 AM 1/16/2005, Reko Turja wrote: This is rather a nubee question.. I am used to OBSD and how to update my sources...but seem to be missing something with FREEBSD. I installed 5.3 release and all I want to do now is update the source files on the disk to current. Very easy, all explained in the handbook. If on Intel, cvsup is your friend. Are you sure you'll want to install CURRENT, by the way? - In the FreeBSD context CURRENT is more like development alpha version, STABLE branch is more like beta, and RELENG branches are the bug and security fix branches of the original release. All explained in the handbook. Does someone have a web page that can show these steps? http://www.freebsd.org/handbook, See chapter 19 and appendix A. -Reko thanks. I am going to track STABLE...you are right. I am installing cvsup without GUI and then I will try to set this up... -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 AIM:lonebanditusa // MSN:[EMAIL PROTECTED] // Yahoo:lonebanditusa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl
Karl Agee wrote: Freebsd 4.11-pre. I am working on learning perl, and have perl 5.00x that is in the base system when I installed 4.10-Release. Since most of the learning materials out there are based on later verisions esp since 5.6.x some of the features arent in this older version. I am considering upgrading to 5.8.5 via ports, but, dont know if that will break anything. It won't break anything. You can have the base install, 5.6.x and 5.8.x installed from ports simultaneously. After installing perl from ports you run /usr/local/bin/use.perl port This will create links to the port install, eg. /usr/bin/perl - /usr/bin/perl5.8.5 And you can go back with /usr/local/bin/use.perl system Which will then replace the link with, eg. /usr/bin/perl - /usr/bin/perl5 These are the limitations: use.perl can only switch between one installed port-version and the system perl. So if you want to use another port-version (ie. for some reason you want both 5.6.x and 5.8.x) you will have to do the linking manually. When you install perl-packages they will be installed into the package path of the currently selected perl. So if you use 5.8.5 and install say p5-DBI then this won't be available for the system perl. However, perl looks backward, so 5.8.5 sees packages installed for the system perl. I haven't found big differences between 5.6 and 5.8, so I'd suggest you use 5.8. The main reason to stick with an older version is that you might develop scripts for platforms where the newer are not available. Note: If/when you upgrade to 5.x there is no system perl, this is partly to avoid the mess with multiple versions of perl. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading perl
--On Thursday, December 30, 2004 7:54 PM -0800 Karl Agee [EMAIL PROTECTED] wrote: Freebsd 4.11-pre. I am working on learning perl, and have perl 5.00x that is in the base system when I installed 4.10-Release. Since most of the learning materials out there are based on later verisions esp since 5.6.x some of the features arent in this older version. I am considering upgrading to 5.8.5 via ports, but, dont know if that will break anything. Just being cautious... It's good to be cautious. :-) If you want to switch to the ports version of perl, then after you run make install clean in the port, you will need to do the following: Type use.perl ports at the commandline. This will switch perl from the system version to the ports version. Until you do this, your system will still be using the system version. Furthermore, you can always revert back to the system version by typing use.perl system at the commandline. After you do that, you will need to run make reinstall in any port that you've installed that uses perl. You can also install all the CPAN modules using the base system, so there's no need to upgrade to the ports version unless you just want to. (I chose to do that on a server I maintain, but it worked fine using the system perl.) Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
