Re: Upgrade to 4.8 RELEASE
Jud wrote: On Sat, 18 Oct 2003 20:04:39 -0400, Robert H. Perry [EMAIL PROTECTED] wrote: [...] Unless there is a specific reason not to do so, cvsup and make world would seem to be an easier and altogether better way to go for an upgrade from one minor version number to the next. Many users do this quite routinely (e.g., I do it once every week or two). See URL: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html#CUTTING-EDGE-SYNOPSIS. While this section of the Handbook talks about the cutting edge development branches, -CURRENT and -STABLE, the same process can be used to upgrade to a -RELEASE. Do you find it impossible to install binary packages after such an update? Do you have to use ports after such an update? I could never get packages to install properly after cvsuping my source. I'm wondering if this is somehow by design, or if I did something wrong... ? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 4.8 RELEASE
On Thu, 23 Oct 2003 09:21:13 -0400, Jesse Guardiani [EMAIL PROTECTED] said: Jud wrote: On Sat, 18 Oct 2003 20:04:39 -0400, Robert H. Perry [EMAIL PROTECTED] wrote: [...] Unless there is a specific reason not to do so, cvsup and make world would seem to be an easier and altogether better way to go for an upgrade from one minor version number to the next. Many users do this quite routinely (e.g., I do it once every week or two). See URL: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html#CUTTING-EDGE-SYNOPSIS. While this section of the Handbook talks about the cutting edge development branches, -CURRENT and -STABLE, the same process can be used to upgrade to a -RELEASE. Do you find it impossible to install binary packages after such an update? Do you have to use ports after such an update? I could never get packages to install properly after cvsuping my source. I'm wondering if this is somehow by design, or if I did something wrong... ? Last question first: IIRC, you were a bit confused regarding ports vs. packages, so the reason for failure of packages (or perhaps it was ports?) to install properly may be as simple as typing commands meant for ports when you really wanted to install a package, or vice versa. Installing a package is as easy as typing 'pkg_add' followed by a URL, or a directory location if you've downloaded the package first. Installing a port is also quite easy - just cd to the port's directory and type 'make install clean.' If you cvsup the -CURRENT or 5.x base system sources and make world, then packages expecting a 4.x base system won't install properly. However (again, IIRC), Mr. Perry was contemplating an update from 4.7 to 4.8, so packages built for 4.x should install fine. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 4.8 RELEASE
Jud wrote: On Thu, 23 Oct 2003 09:21:13 -0400, Jesse Guardiani [EMAIL PROTECTED] said: Jud wrote: On Sat, 18 Oct 2003 20:04:39 -0400, Robert H. Perry [EMAIL PROTECTED] wrote: [...] Unless there is a specific reason not to do so, cvsup and make world would seem to be an easier and altogether better way to go for an upgrade from one minor version number to the next. Many users do this quite routinely (e.g., I do it once every week or two). See URL: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html#CUTTING-EDGE-SYNOPSIS. While this section of the Handbook talks about the cutting edge development branches, -CURRENT and -STABLE, the same process can be used to upgrade to a -RELEASE. Do you find it impossible to install binary packages after such an update? Do you have to use ports after such an update? I could never get packages to install properly after cvsuping my source. I'm wondering if this is somehow by design, or if I did something wrong... ? Last question first: IIRC, you were a bit confused regarding ports vs. packages, so the reason for failure of packages (or perhaps it was ports?) to install properly may be as simple as typing commands meant for ports when you really wanted to install a package, or vice versa. No. I wasn't confused about ports vs. packages. I was confused in that I thought the port cvsup had caused my problem. I've since discovered that it was the system source cvsup (to fix a security vulnerability) that caused my problems. I've updated ports on my laptop and I can still download and install package just fine. However, I'm sure that if I updated to -CURRENT I would no longer be able to install packages. [...] If you cvsup the -CURRENT or 5.x base system sources and make world, then packages expecting a 4.x base system won't install properly. However (again, IIRC), Mr. Perry was contemplating an update from 4.7 to 4.8, so packages built for 4.x should install fine. OK. That's what I thought. It's a shame that FreeBSD doesn't provide some sort of system to allow the use of packages with (at the very least) -STABLE. As an administrator, I find myself often torn between updating my system sources from -RELEASE to fix a security vulnerability (and thus give up my ability to install binary packages), and simply recompiling the effected program or library (and any linked programs that depend on it) by hand so I can still install binary packages. Is the ports/packages system actively maintained by anyone? If so, the above might be something to think about. For security updates, each effected package would have to be recompiled with the appropriate fix and somehow become the default choice (overriding the vulnerable package) for systems with a compatible bug fix level. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 4.8 RELEASE
On Sat, 18 Oct 2003 20:04:39 -0400 Robert H. Perry [EMAIL PROTECTED] probably wrote: Hello, I'm making plans to upgrade from 4.7 RELEASE to 4.8 RELEASE. My previous attempt was a binary upgrade from 4.5 to 4.7 which did not go very well. I eventually purchased the 4.7 CD. The FreeBSD Handbook stresses backing up the system and implies that /dump/ is a better backup program. Chapter 12.9.8.1 of the handbook recommends having a copy of the boot and fixit floppies available and making sure they have all your devices, otherwise you'll need to prepare two bootable custom floppies that contain /fdisk, disklabel, newfs, mount, /and your backup program. It goes on to say that these programs must be statically linked. I understand hard and soft links but I'm not familiar with static links. The handbook also provides a script for creatinng a bootable floppy. A static link is a firm link:) Seriously, static linking has nothing to do with filesystem links. A statically linked program just uses no shared libraries. AFAICT the programs in /stand (and /bin and /sbin) are statically linked (note that those in /stand are also a crunchbox, that is, a single monolithic program which runs differently depending on the name it was run as). You really have to mess with this only if you are going to write your own program to run from a boot floppy. You can use file(1) if you want to see if a program is staticlally linked: $ file /usr/bin/find /usr/bin/find: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 4.8, dynamically linked (uses shared libs), stripped $ file /stand/find /stand/find: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 4.8, statically linked, stripped Can someone help me understand static link? Secondly, can I assume that the script must be reviewed for likely modifications? I'm just learning shell programming and if significant modifications are necessary, I may end up purchasing a CD for 4.8. Any suggestions relative to the upgrade process is also appreciated. In fact, a source update isn't as dangerous as you expect. Thanks, Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- DoubleF When I was a boy I was told that anybody could become President. Now I'm beginning to believe it. -- Clarence Darrow pgp0.pgp Description: PGP signature
Re: Upgrade to 4.8 RELEASE
Hello, I'm making plans to upgrade from 4.7 RELEASE to 4.8 RELEASE. My previous attempt was a binary upgrade from 4.5 to 4.7 which did not go very well. I eventually purchased the 4.7 CD. The FreeBSD Handbook stresses backing up the system and implies that /dump/ is a better backup program. Chapter 12.9.8.1 of the handbook recommends having a copy of the boot and fixit floppies available and making sure they have all your devices, otherwise you'll need to prepare two bootable custom floppies that contain /fdisk, disklabel, newfs, mount, /and your backup program. It goes on to say that these programs must be statically linked. I understand hard and soft links but I'm not familiar with static links. The handbook also provides a script for creatinng a bootable floppy. A static link is a firm link:) Seriously, static linking has nothing to do with filesystem links. A statically linked program just uses no shared libraries. AFAICT the programs in /stand (and /bin and /sbin) are statically linked (note that those in /stand are also a crunchbox, that is, a single monolithic program which runs differently depending on the name it was run as). You really have to mess with this only if you are going to write your own program to run from a boot floppy. You can use file(1) if you want to see if a program is staticlally linked: $ file /usr/bin/find /usr/bin/find: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 4.8, dynamically linked (uses shared libs), stripped $ file /stand/find /stand/find: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 4.8, statically linked, stripped Thanks for the education Sergey. This makes a lot more sense now. I never prepared a boot floppy when I initially installed 4.7 so I thought the handbook was suggesting a necessary alternative (?). If it's not absolutely necessary, I'll skip it. Any suggestions relative to the upgrade process is also appreciated. In fact, a source update isn't as dangerous as you expect. That's what I've heard and I suspect you're right. However, AFAICT, past failures have usually come as a result of not following the handbook. Maybe this floppy is a bit of overkill though. Thanks again. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade to 4.8 RELEASE
Hello, I'm making plans to upgrade from 4.7 RELEASE to 4.8 RELEASE. My previous attempt was a binary upgrade from 4.5 to 4.7 which did not go very well. I eventually purchased the 4.7 CD. The FreeBSD Handbook stresses backing up the system and implies that /dump/ is a better backup program. Chapter 12.9.8.1 of the handbook recommends having a copy of the boot and fixit floppies available and making sure they have all your devices, otherwise you'll need to prepare two bootable custom floppies that contain /fdisk, disklabel, newfs, mount, /and your backup program. It goes on to say that these programs must be statically linked. I understand hard and soft links but I'm not familiar with static links. The handbook also provides a script for creatinng a bootable floppy. Can someone help me understand static link? Secondly, can I assume that the script must be reviewed for likely modifications? I'm just learning shell programming and if significant modifications are necessary, I may end up purchasing a CD for 4.8. Any suggestions relative to the upgrade process is also appreciated. Thanks, Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
