Re: Adding Packages and Ports
On Sun, Feb 01, 2004 at 11:21:13PM -0500, Krikket wrote: Please correct me if I'm wrong, but the various versions of freeBSD (3.x, 4.x, and 5.x) are still being worked. Needless to say, 5.x is the bleeding edge, but 4.x hasn't been left to go stale. (Or else how would security patches get done, when needed?) FreeBSD 3.x isn't actively supported or worked on any more, although very occasionally some critical security fixes have been committed to that branch. But otherwise, yes, you're right. Therefore, the thought was to get the latest and greatest from the net. No, it's not as bleeding edge as the 5.2 stuff, but if a patch was done since the 4.9 iso's were made, it would be a good idea to have that on hand. So I thought it would be a good thing to use -r as a default option. Or am I just using an incorrect line of thinking, due to the flux that I got used to (and wish to avoid) from when I was dealing with the Linux world? Ports are developed independantly of the base system. It's a continuous process of development as new ports get added, updates to current ports are made to accomodate upstream changes to port distfiles or to fix bug, and generally as new features appear in the ports make system. Testing on ports is done using the currently supported versions of the OS -- viz. 4.9 and 5.2 -- and while ports should work on older systems, that cannot be guarranteed. Each time a release is made, a full set of packages are built from the ports tree: there's a short period of code freeze before that on the ports tree when extra effort is put into bug fixing and making everything work as well as possible together, rather than introducing new code. Those packages are what goes onto the FTP sites, and a sample of the most popular ones go into the install CDs -- there's *far* too much stuff to fit all of it onto a 4 CD distribution set. Between releases, where a port is updated, an updated pkg tarball is eventually uploaded to the ftp servers into the 'Latest' directory, for each Tier-1 architecture and for both supported OS versions. pkg_add -r will download that 'Latest' version where available, or else the version from the release set. However, pkg building isn't instantaneous, and you can get hold of the newest stuff much quicker by building out of the ports tree yourself. So, given that I should have the ports installed from my initial install phase, all I have to do is the make install clean? Too cool. Thank you for the pointer! Absolutely. Lots of people instinctively head towards the installing precompiled packages route, but generally I find that installing through ports is just as easy, usually doesn't take that much more time (except for some really big compilations, like OpenOffice or jdk14), and lets you tweak various build options and so forth. Even so, it's perfectly fine to mix up stuff installed via packages and stuff installed via ports -- it all comes down to the same package database in the end. Using ports also makes it a lot easier to keep everything maintained and up to date, especially by using the portupgrade(1) tools. There are some ports which aren't available as packages, usually for licensing reasons. Note that the ports tree you installed is a snapshot of the state at the time your release was created. The ports tree has undergone a great deal of development since then. There's been a lot of updates to the 3rd party ported software as well, and some versions current at that time may not be available any more. You can track the current state of the ports tree using cvsup(1) -- exactly as you'ld track the current state of the system sources. Details of how to do that are available in the Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Nb. the cheats method of getting cvsup(1) working is very quick: Step 1: Install the cvsup-without-gui package using pkg_add. Type 'rehash' if you're using tcsh(1) as your shell, so that it becomes aware of the newly installed binaries. Step 2: Edit /etc/make.conf -- create the file if it doesn't exist. You need to add the following: SUP_UPDATE= yes SUP=/usr/local/bin/cvsup SUPFLAGS= -g -L 2 SUPHOST=cvsup.XX.FreeBSD.org [1] SUPFILE=/usr/share/examples/cvsup/standard-supfile [2] PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile where [1] should be a cvsup server local to you, and [2] as shown will get you the system sources for the same OS -RELEASE branch as you installed: eg. 4.9-RELEASE-pN or 5.2-RELEASE-pN. You can replace that by 'stable-supfile' to switch to the 4-STABLE branch, although once you've updated to 4-STABLE, the standard-supfile will be replaced by one pulling down the 4-STABLE sources. Step 3: Update the ports
Re: Adding Packages and Ports
I'm going to hold off on replying for a day, while I give this stuff a shot, but this part does raise a question for me... On Mon, 2 Feb 2004, Matthew Seaman wrote: Those packages are what goes onto the FTP sites, and a sample of the most popular ones go into the install CDs -- there's *far* too much stuff to fit all of it onto a 4 CD distribution set. I got my copy of FreeBSD by downloading the isos. CD 1 2 and mini. That's all that was available. CD #1 was the only CD that was ever asked for by the system. Where do the other CD's come into play? What's the difference between the isos and the 4 cd set? (Aside from the number of CDs...) I haven't seen anything that directly answers this. I'm more than willing to support the BSD project, assuming the OS meets my needs (and so far it looks like it probably will) I was just planning on starting with the BSD stuffie. 8^) And the BSD books... Krikket ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Packages and Ports
On Mon, Feb 02, 2004 at 03:34:33AM -0500, Krikket wrote: I'm going to hold off on replying for a day, while I give this stuff a shot, but this part does raise a question for me... On Mon, 2 Feb 2004, Matthew Seaman wrote: Those packages are what goes onto the FTP sites, and a sample of the most popular ones go into the install CDs -- there's *far* too much stuff to fit all of it onto a 4 CD distribution set. I got my copy of FreeBSD by downloading the isos. CD 1 2 and mini. That's all that was available. CD #1 was the only CD that was ever asked for by the system. Where do the other CD's come into play? What's the difference between the isos and the 4 cd set? (Aside from the number of CDs...) I haven't seen anything that directly answers this. I'm more than willing to support the BSD project, assuming the OS meets my needs (and so far it looks like it probably will) I was just planning on starting with the BSD stuffie. 8^) And the BSD books... The isos on the FreeBSD site are what's distributed as disks 1 and 2 of the 4 CD set. You only get the other two CDs (which contain various selected packages) if you buy a set from FreeBSDMall or Deamon News' bsdmall. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Adding Packages and Ports
On Mon, 2 Feb 2004 03:34:33 -0500 (EST), you wrote: I got my copy of FreeBSD by downloading the isos. CD 1 2 and mini. That's all that was available. Disc 1 is the install disc. Disc 2 is the repair/recovery disc Mini is disk 1 stripped down to more or less bare minimum. It's all you need to download if you have a decent 'net connection as the remainder of discs 1 and 2 are pre-compiled binary packages which you get from ports or pkg_add over the 'net connection as required. Now I come to think of it, the Mini CD has no X windows managers either (other than TWM), if it even has X on it at all. Not 100% sure on that. HTH dave -- Any speling misteaks are the reult of a bad insallation of mod_spelink. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Packages and Ports
Krikket wrote: On Sun, 1 Feb 2004, Roop Nanuwa wrote: Krikket wrote: I've done a brand-new install of FreeBSD (4.9), and am a fresh user to this flavor of *nix. Welcome, we hope you enjoy your stay :). Thank you! The install went more or less without a hitch. For some reason ldap (part of the default package selection) didn't want to install. Could you be a bit more specific? What happened during the install? Did it give you any error messages? A generic compile error message, nothing specific. And unfortunately, I didn't take notes. (No, I wasn't expecting help with troubleshooting that point, it was said more in the way of a commentary than anything else. I figured that when I got to the point of needing it, I could always install it at a later time, and if needed ask questions then.) To test things out, I tried installing mozilla. It failed due to a dependancy, so I checked out the website to see what was available, found a version that was there, adn installed it. How are you installing mozilla? There shouldn't be any dependency problems in either of the two main ways to install packages on FreeBSD. Whether you install via the ports tree or through the package system all the dependencies should be handled for you. I think the reason that you're having dependency issues is because you're attempting to install binaries that you've downloaded that aren't packaged for FreeBSD specifically. I attempted to do a pkg_add -r mozilla. After checking the on-line database of software at freebsd.org, I know I tried some versons of the command lile ... -r linux-mozilla and sometimes with version numbers. I forget the exact one that did work. But when I type mozilla to start the program, it's not found. (Nor was it added to the KDE Menu.) I was able to do a pkg_add -r cvsup on the first try. But I ended up with the same problem -- not being able to find the package once it was installed. Needless to say, I can't add any ports as a result. Which shell are you running? You might have to run 'rehash' to refresh your shell's cache of available programs. Logging in/out would do the same but running 'rehash' is simpler/quicker. bash. I'll give that a shot. I'm not at home at the moment, and for some reason ssh doesn't want to allow me to login. For bash, you'll want to do a 'hash -r' instead of rehash Scott (I get a login prompt, but it's not accepting the correct password for either myself or the root accounts. Even after I called home and had the roommate reboot the system, just in case something flakey got into memory. I'm thinking it may be time to pull out the rubber chicken.) Krikket ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Packages and Ports
Krikket wrote: I've done a brand-new install of FreeBSD (4.9), and am a fresh user to this flavor of *nix. Welcome, we hope you enjoy your stay :). The install went more or less without a hitch. For some reason ldap (part of the default package selection) didn't want to install. Could you be a bit more specific? What happened during the install? Did it give you any error messages? To test things out, I tried installing mozilla. It failed due to a dependancy, so I checked out the website to see what was available, found a version that was there, adn installed it. How are you installing mozilla? There shouldn't be any dependency problems in either of the two main ways to install packages on FreeBSD. Whether you install via the ports tree or through the package system all the dependencies should be handled for you. I think the reason that you're having dependency issues is because you're attempting to install binaries that you've downloaded that aren't packaged for FreeBSD specifically. But when I type mozilla to start the program, it's not found. (Nor was it added to the KDE Menu.) I was able to do a pkg_add -r cvsup on the first try. But I ended up with the same problem -- not being able to find the package once it was installed. Needless to say, I can't add any ports as a result. Which shell are you running? You might have to run 'rehash' to refresh your shell's cache of available programs. Logging in/out would do the same but running 'rehash' is simpler/quicker. --roop ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Packages and Ports
On Sunday 01 February 2004 09:29 pm, Krikket wrote: I've done a brand-new install of FreeBSD (4.9), and am a fresh user to this flavor of *nix. The install went more or less without a hitch. For some reason ldap (part of the default package selection) didn't want to install. While I can ssh to the box, it won't accept the password for users and/or root. (IE: It makes the connection, gives a login prompt, but the correct password is rejected. I'm sshing from a Fedora box.) But the big problem that I'm having, that's turning into a show-stopper has to deal with installing packages and/or ports, once the base OS is installed. To test things out, I tried installing mozilla. It failed due to a dependancy, so I checked out the website to see what was available, found a version that was there, adn installed it. Dependencies should be taken care of if you installed via ports or using pkg_add and the install cd, or pkg_add and the ftp server. Exactly how did you try to install mozilla? But when I type mozilla to start the program, it's not found. (Nor was it added to the KDE Menu.) Try executing 'rehash' after installing an application and before attempting to execute it. Also, if you installed mozilla-firebird, I think the command is 'mozilla-firebird'. Since certain app's help programs call mozilla, you might want to make a link called mozilla to your browser command. I was able to do a pkg_add -r cvsup on the first try. But I ended up with the same problem -- not being able to find the package once it was installed. Needless to say, I can't add any ports as a result. Why are you using the '-r' option? If you're using the install 4.9 CDROM, just cd to /cdrom/packages/All and: pkg_add cvsup-16.1h.tgz If you're using ports, cd to /usr/ports/net/cvsup and execute: make install clean I figure there's something basic that I'm missing, but I'll be damned if I can figure it out, despite the help of the handbook and FAQ... Can anyone give me a pointer in the right direction? Please? Thanks in advance, Krikket Best of luck, Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Packages and Ports
On Sun, 1 Feb 2004, Roop Nanuwa wrote: Krikket wrote: I've done a brand-new install of FreeBSD (4.9), and am a fresh user to this flavor of *nix. Welcome, we hope you enjoy your stay :). Thank you! The install went more or less without a hitch. For some reason ldap (part of the default package selection) didn't want to install. Could you be a bit more specific? What happened during the install? Did it give you any error messages? A generic compile error message, nothing specific. And unfortunately, I didn't take notes. (No, I wasn't expecting help with troubleshooting that point, it was said more in the way of a commentary than anything else. I figured that when I got to the point of needing it, I could always install it at a later time, and if needed ask questions then.) To test things out, I tried installing mozilla. It failed due to a dependancy, so I checked out the website to see what was available, found a version that was there, adn installed it. How are you installing mozilla? There shouldn't be any dependency problems in either of the two main ways to install packages on FreeBSD. Whether you install via the ports tree or through the package system all the dependencies should be handled for you. I think the reason that you're having dependency issues is because you're attempting to install binaries that you've downloaded that aren't packaged for FreeBSD specifically. I attempted to do a pkg_add -r mozilla. After checking the on-line database of software at freebsd.org, I know I tried some versons of the command lile ... -r linux-mozilla and sometimes with version numbers. I forget the exact one that did work. But when I type mozilla to start the program, it's not found. (Nor was it added to the KDE Menu.) I was able to do a pkg_add -r cvsup on the first try. But I ended up with the same problem -- not being able to find the package once it was installed. Needless to say, I can't add any ports as a result. Which shell are you running? You might have to run 'rehash' to refresh your shell's cache of available programs. Logging in/out would do the same but running 'rehash' is simpler/quicker. bash. I'll give that a shot. I'm not at home at the moment, and for some reason ssh doesn't want to allow me to login. (I get a login prompt, but it's not accepting the correct password for either myself or the root accounts. Even after I called home and had the roommate reboot the system, just in case something flakey got into memory. I'm thinking it may be time to pull out the rubber chicken.) Krikket ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Adding Packages and Ports
installing an package pkg_add -rv cvsup-without-gui rehash you have to do rehash command so your shell will search all /bin directories and build shell hash table. Then issue command for installed package. Or of course, reboot will fix it also. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Krikket Sent: Sunday, February 01, 2004 10:29 PM To: [EMAIL PROTECTED] Subject: Adding Packages and Ports I've done a brand-new install of FreeBSD (4.9), and am a fresh user to this flavor of *nix. The install went more or less without a hitch. For some reason ldap (part of the default package selection) didn't want to install. While I can ssh to the box, it won't accept the password for users and/or root. (IE: It makes the connection, gives a login prompt, but the correct password is rejected. I'm sshing from a Fedora box.) But the big problem that I'm having, that's turning into a show-stopper has to deal with installing packages and/or ports, once the base OS is installed. To test things out, I tried installing mozilla. It failed due to a dependancy, so I checked out the website to see what was available, found a version that was there, adn installed it. But when I type mozilla to start the program, it's not found. (Nor was it added to the KDE Menu.) I was able to do a pkg_add -r cvsup on the first try. But I ended up with the same problem -- not being able to find the package once it was installed. Needless to say, I can't add any ports as a result. I figure there's something basic that I'm missing, but I'll be damned if I can figure it out, despite the help of the handbook and FAQ... Can anyone give me a pointer in the right direction? Please? Thanks in advance, Krikket (I will say that compared to some flavors of Linux, this install was absolutely painfree. I did have to start over on some occasions, due to minor user errors, but assuming the perfect user during the install process, it went rather well. After dealing with the alsa hell of Linux, gettign sound working on FreeBSD was a very pleasent surprise!) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Packages and Ports
On Sun, 1 Feb 2004, Andrew L. Gould wrote: Krikket wrote: I was able to do a pkg_add -r cvsup on the first try. But I ended up with the same problem -- not being able to find the package once it was installed. Needless to say, I can't add any ports as a result. Why are you using the '-r' option? If you're using the install 4.9 CDROM, just cd to /cdrom/packages/All and: pkg_add cvsup-16.1h.tgz If you're using ports, cd to /usr/ports/net/cvsup and execute: make install clean Err... Excuse me while I'm a little bull-headed here, and attempting to adjust from the linux world. The reason I was thinking of using the -r option is because it pulls from the ftp site. Please correct me if I'm wrong, but the various versions of freeBSD (3.x, 4.x, and 5.x) are still being worked. Needless to say, 5.x is the bleeding edge, but 4.x hasn't been left to go stale. (Or else how would security patches get done, when needed?) Therefore, the thought was to get the latest and greatest from the net. No, it's not as bleeding edge as the 5.2 stuff, but if a patch was done since the 4.9 iso's were made, it would be a good idea to have that on hand. So I thought it would be a good thing to use -r as a default option. Or am I just using an incorrect line of thinking, due to the flux that I got used to (and wish to avoid) from when I was dealing with the Linux world? So, given that I should have the ports installed from my initial install phase, all I have to do is the make install clean? Too cool. Thank you for the pointer! Krikket ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Packages and Ports
Krikket wrote: Err... Excuse me while I'm a little bull-headed here, and attempting to adjust from the linux world. The reason I was thinking of using the -r option is because it pulls from the ftp site. It does. You should realize though that what you pull from the FTP site is no different/newer than what would be on the 4.9 release CD. It also isn't any different that the version you would install via the ports tree. Please correct me if I'm wrong, but the various versions of freeBSD (3.x, 4.x, and 5.x) are still being worked. Needless to say, 5.x is the bleeding edge, but 4.x hasn't been left to go stale. (Or else how would security patches get done, when needed?) 4.9-RELEASE is actually only a couple of weeks old, so hardly 'stale' by any stretch of the imagination. Therefore, the thought was to get the latest and greatest from the net. No, it's not as bleeding edge as the 5.2 stuff, but if a patch was done since the 4.9 iso's were made, it would be a good idea to have that on hand. So I thought it would be a good thing to use -r as a default option. Or am I just using an incorrect line of thinking, due to the flux that I got used to (and wish to avoid) from when I was dealing with the Linux world? I think you're confusing the differences between third party package versions, FreeBSD versions and what is bleeding edge or not. You can update your ports tree via cvsup (read the handbook for a guide) and after that your ports tree will contain all the latest available versions of different software. Whether you're running 4.9 or 5.2, when you update to the latest version of the ports tree it's the same either way. So, given that I should have the ports installed from my initial install phase, all I have to do is the make install clean? Too cool. Thank you for the pointer! Yep, that's right. Keep in mind, though, that most of the ports probably have newer versions out by now though. So you might want to look into the cvsup I mentioned above so that when you make install clean, it's not installing an 'old' version of that port. --roop ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
