Date: Tue, 12 Sep 2006 16:02:33 -0400 From: ograbme <ograbme@gmail.com> To: "Jeff Rollin" <jeff.rollin@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re[2]: The Ports collection / FreeBSD CDs Message-ID: <186816020.20060912160233@gmail.com> In-Reply-To: <8a0028260609120341v61920cf5p3aad4710ef3bd634@mail.gmail.com> References: <d85a51ff0609120304kf4bb0bdy8fba0ed4c7f174e6@mail.gmail.com> <8a0028260609120341v61920cf5p3aad4710ef3bd634@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Howdie Jeff (if I may) and others, Tuesday, September 12, 2006, 6:41:38 AM, you wrote: JR> On 12/09/06, Arindam <arindam.mukerjee@gmail.com> wrote: <snip> >> >> I chose not to install the ports collection because as of now, I do >> not have access to Internet in my home-network and it would take a >> little while before I can set it up for browsing. <snip> I too took this same approach as the box I installed FreeBSD 6.1 Release is not hooked up to the Internet. I bypassed installing the Ports collection. The installation went well and I have been refamiliarizing myself with Unix CLI commands and reading bits and pieces of documentation here and there. FreeBSD is pretty neat and has quite a few subtle differences from systems I worked on some years back, i.e., Solaris, HP-UX, etc. Anyway, now I would like to install the ports collection without having to reinstall the whole system again, if possible, thus my interest in this thread. For instance, I decided I wanted to install sudo ... <snip> JR> The FreeBSD installation program asks if you want "to install the ports JR> collection," but what it actually does is install a bunch of directories JR> (under /usr/ports) that you can use to browse what's available in the ports JR> collection. For example, to download a port, say, Firefox compiled for use JR> with the Linux compatibility layer, go into /usr/ports/linux/linux-firefox JR> and type: JR> $ make install clean Using the above info, I created /usr/ports directory (/usr was there, but not /ports of course as I hadn't installed the Ports collection). I created another directory under /usr/ports/ named /sudo, thus resulting in /usr/ports/sudo. I had mounted the ports CD I have and located sudo-1.6.8p12.tar.gz in the distfiles directory. I copied it over into the /usr/ports/sudo directory, gunzipped it, and then untarred it. I then made sure I was in the directory containing sudo.c and all its attendent other files and tried the above "make install clean". Unfortunately it was a no-go. Resultant message I received was: "make: Don't know how to make install. Stop" Obviously I've done something wrong here ... misstepped or tried to do the impossible, huh? LOL! Perhaps, sudo can only be installed via the pkg-add route per your mention below? I invoked sysinstall, but didn't see right away anything clearly indicating the "path to take" in resolving my dilemma. I'll keep reading and trying and may be stumble across the proper way to accomplish this, but all the while monitoring this email list for further enlightenment. Then again, may be I should just do a complete new install and select "Yes" to installing the Ports collection at that time, huh? Naaaaah, one has to mess up to learn! And trust me, I've learned quite a bit by reading yours and others comments and suggestions. Thank for all of you being so willing to share your knowledge. Thanks in advance. P.S. Please advise what the proper mode of responding is in terms of replying. I did a "reply all" (to both Jeff and the list) for my first submission. However, perhaps I should of only replied to the list to eliminate unnecessary traffic. <snip> JR> ($ stands for the prompt, as you probably know); make reads the Makefile, JR> and according to instructions in it, downloads the sources and compiles JR> them; make install and make clean (given here in shorthand) respectively JR> install the compiled port and clean up after make. JR> The alternative way to install software is from packages, which are JR> pre-compiled ports. You can use sysinstall to install them, or pkg_add from JR> the commandline. Disc2 mostly contains some of these packages (others are on JR> Disc1). <snip>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?186816020.20060912160233>