Re[2]: The Ports collection / FreeBSD CDs

2006-09-13 Thread ograbme
Hello Frank,

Tuesday, September 12, 2006, 10:41:17 PM, you wrote:

snip

FS Go grab the compressed, reasonably up to date ports tree:

FS $ fetch -dpv ftp.freebsd.org/pub/FreeBSD/ports/ports/ports.tar.gz

FS (warning! 35MB compressed)

Will do when I have Internet connection via FreeBSD box.  Need to set
up ADSL connection - am currently reading about that process.  Also,
need to figure out how USB gets set up properly.  But these are two
separate issues that I will probably be asking about in the very near
future ... if I haven't managed to make any real progress in these
areas.

FS and:

FS # mv ports.tar.gz /usr/ports
FS # cd /usr/ports
FS # tar xvzf ports.tar.gz

FS to build sudo, first check that there's nothing funny with building
FS sudo:

FS $ cat /usr/ports/UPDATING | grep sudo

FS if there's nothing then:

FS # cd /usr/ports/security/sudo/
FS # make install clean

Thanks for the detailed steps.

FS Then read the handbook about keeping your ports tree up to date using
FS portsnap or cvsup.

Will do.

 
 P.S.  Please advise what the proper mode of responding is in terms of
 replying.  I did a reply all ...
 snip
 

FS That's OK. I usually post to the list and cc to the person who posted
FS in the first place as they may not be subscribed to the list.

Yes, this was my line of thinking, but don't want to upset anyone as
I am a newbie here. ;)

FS Welcome to FreeBSD!

Thanks.  Appreciate it, Frank.

--
Best regards,
ograbme


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-13 Thread Daniel Bye
On Tue, Sep 12, 2006 at 05:30:43PM -0700, Perry Hutchison wrote:
   ... at least in my recent experience, an up-to-date ports tree 
   does not always play nicely with a not-updated base install from
   CD.
 
  That's very interesting. However, the ports tree on the CD isn't
  complete, as in: not all the ports are there.
 
 Any idea why?  (I am referring to the ports tree itself, i.e. the
 collection of skeleton directories.  The set of distfiles provided
 on CDs 3 and 4 is necessarily incomplete, both due to limited space
 and because some distfiles have legal restrictions that prevent 
 their inclusion.)

Because since the release CD was cut, the porters have been tirelessly
porting new software and updating existing software - the ports tree is
pretty much in a constant state of growth and development.  As soon as 
the release is cut, the included ports tree is out of date.

-- 
Daniel Bye

PGP Key: http://www.slightlystrange.org/pgpkey-dan.asc
PGP Key fingerprint: D349 B109 0EB8 2554 4D75  B79A 8B17 F97C 1622 166A
 _
  ASCII ribbon campaign ( )
 - against HTML, vCards and  X
- proprietary attachments in e-mail / \


pgps591PQcSnj.pgp
Description: PGP signature


Re: The Ports collection / FreeBSD CDs

2006-09-13 Thread Frank Shute
On Wed, Sep 13, 2006 at 08:19:22AM -0400, ograbme wrote:

 Hello Frank,
 
 Tuesday, September 12, 2006, 10:41:17 PM, you wrote:
 
 snip
 
 FS Go grab the compressed, reasonably up to date ports tree:
 
 FS $ fetch -dpv ftp.freebsd.org/pub/FreeBSD/ports/ports/ports.tar.gz
 
 FS (warning! 35MB compressed)
 
 Will do when I have Internet connection via FreeBSD box.  Need to set
 up ADSL connection - am currently reading about that process.  Also,
 need to figure out how USB gets set up properly.  But these are two
 separate issues that I will probably be asking about in the very near
 future ... if I haven't managed to make any real progress in these
 areas.

I didn't realise you didn't have a network connection yet!

For usb, you need:

usbd_enable=YES

in /etc/rc.conf

The handbook is your best bet to get your network connection going.
Any problems, just post here.

 
 FS and:
 
 FS # mv ports.tar.gz /usr/ports
 FS # cd /usr/ports
 FS # tar xvzf ports.tar.gz
 
 FS to build sudo, first check that there's nothing funny with building
 FS sudo:
 
 FS $ cat /usr/ports/UPDATING | grep sudo
 
 FS if there's nothing then:
 
 FS # cd /usr/ports/security/sudo/
 FS # make install clean
 
 Thanks for the detailed steps.
 
 FS Then read the handbook about keeping your ports tree up to date using
 FS portsnap or cvsup.
 
 Will do.
 
  
  P.S.  Please advise what the proper mode of responding is in terms of
  replying.  I did a reply all ...
  snip
  
 
 FS That's OK. I usually post to the list and cc to the person who posted
 FS in the first place as they may not be subscribed to the list.
 
 Yes, this was my line of thinking, but don't want to upset anyone as
 I am a newbie here. ;)

Yeah, it always helps if you don't piss off everybody when you're
tring to get help ;)

 
 FS Welcome to FreeBSD!
 
 Thanks.  Appreciate it, Frank.
 

No worries.

BTW, you can get back to the installer with:

# /stand/sysinstall

and from there with your discs you can install a limited amount of
ports/packages.

Best of luck with it. It will take you some blood, sweat and tears to
familiarise yourself with FreeBSD but once you've gone through the
initial learning process and setting up the basics such as networking
and email, it's very easy to maintain your system and install software
- much easier than Linux IMHO. The ports system for application
software and buildkernel/buildworld for upgrading your base system are
very effective.

-- 

 Frank 


echo f r a n k @ e s p e r a n c e - l i n u x . c o . u k | sed 's/ //g'

  ---PGP keyID: 0x10BD6F4B---  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


The Ports collection / FreeBSD CDs

2006-09-12 Thread Arindam

I am a Linux user and have been recently trying to shift to FreeBSD. I
got hold of a couple of FreeBSD CD ISOs (version 6.1) - their names
being 6.1-RELEASE-i386-discX.iso, X being 1 and 2.

I did my installation with the Disc1 alone. I did not need Disc2. What
is the purpose of Disc2 and what can I do with it.

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. Does Disc2 contain
some of the ports collection?

Finally, what is the ports collection?

Cheers!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Jeff Rollin

On 12/09/06, Arindam [EMAIL PROTECTED] wrote:


I am a Linux user and have been recently trying to shift to FreeBSD. I
got hold of a couple of FreeBSD CD ISOs (version 6.1) - their names
being 6.1-RELEASE-i386-discX.iso, X being 1 and 2.

I did my installation with the Disc1 alone. I did not need Disc2. What
is the purpose of Disc2 and what can I do with it.

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. Does Disc2 contain
some of the ports collection?

Finally, what is the ports collection?



To take your last question first: The ports collection allows you to install
software from source that does not come as part of the base distribution -
that equates, more or less, to stuff that on FreeBSD installs itself to
directories in / and /usr. The base distribution includes stuff like the X
Window System, but not KDE, Firefox or MH, the mail handler. These latter
three are available as ports, which when compiled go into /usr/local by
default on FreeBSD.

The FreeBSD installation program asks if you want to install the ports
collection, but what it actually does is install a bunch of directories
(under /usr/ports) that you can use to browse what's available in the ports
collection. For example, to download a port, say, Firefox compiled for use
with the Linux compatibility layer, go into /usr/ports/linux/linux-firefox
and type:

$ make install clean

(note you need to have Linux compatibility already installed and turned on
to make this work).

($ stands for the prompt, as you probably know); make reads the Makefile,
and according to instructions in it, downloads the sources and compiles
them; make install and make clean (given here in shorthand) respectively
install the compiled port and clean up after make.

The alternative way to install software is from packages, which are
pre-compiled ports. You can use sysinstall to install them, or pkg_add from
the commandline. Disc2 mostly contains some of these packages (others are on
Disc1).

Cheers



You're welcome!

Jeff.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread RW
On Tuesday 12 September 2006 11:41, Jeff Rollin wrote:
 To take your last question first: The ports collection allows you to
 install software from source that does not come as part of the base
 distribution - that equates, more or less, to stuff that on FreeBSD
 installs itself to directories in / and /usr. The base distribution
 includes stuff like the X Window System, but not KDE, Firefox or MH, the
 mail handler. 

The base system doesn't include X Windows.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Jeff Rollin



The base system doesn't include X Windows.
_



Right, I was thinking of NetBSD. X Window System is a FreeBSD port (so it
must be installed as a package from sysinstall).

Jeff Rollin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Duane Hill
On Tuesday, September 12, 2006 at 11:29:31 AM, Jeff confabulated:



 The base system doesn't include X Windows.
 _


 Right, I was thinking of NetBSD. X Window System is a FreeBSD port (so it
 must be installed as a package from sysinstall).

Shouldn't you also be able to:

  cd /usr/ports/x11; make install clean

-- 
This message was sent using 100% recycled electrons.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Jeff Rollin

On 12/09/06, Duane Hill [EMAIL PROTECTED] wrote:


On Tuesday, September 12, 2006 at 11:29:31 AM, Jeff confabulated:



 The base system doesn't include X Windows.
 _


 Right, I was thinking of NetBSD. X Window System is a FreeBSD port (so
it
 must be installed as a package from sysinstall).

Shouldn't you also be able to:

  cd /usr/ports/x11; make install clean

--



That sentence was intended not to mean you have to install XWS as a package
from sysinstall but It must be the case that sysinstall installs it as a
package built from ports.

Jeff Rollin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread RW
On Tuesday 12 September 2006 12:29, Jeff Rollin wrote:
  The base system doesn't include X Windows.
  _

 Right, I was thinking of NetBSD. X Window System is a FreeBSD port (so it
 must be installed as a package from sysinstall).

That's actually my biggest problem with sysinstall, that it's standard 
installation mixes-up base system options and package options. I only use 
sysinstall once in a blue moon, and I find that  Choose Distributions menu, 
baffling - even though I know what I want installed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Duane Hill
On Tuesday, September 12, 2006 at 12:03:47 PM, Jeff confabulated:

 On 12/09/06, Duane Hill [EMAIL PROTECTED] wrote:

 On Tuesday, September 12, 2006 at 11:29:31 AM, Jeff confabulated:

 
 
  The base system doesn't include X Windows.
  _


  Right, I was thinking of NetBSD. X Window System is a FreeBSD port (so
 it
  must be installed as a package from sysinstall).

 Shouldn't you also be able to:

   cd /usr/ports/x11; make install clean

 --

 That sentence was intended not to mean you have to install XWS as a package
 from sysinstall but It must be the case that sysinstall installs it as a
 package built from ports.

I  wasn't  for  sure  as I don't install many things using sysinstall.
Thanks for clarifying.

-- 
This message was sent using 100% recycled electrons.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re[2]: The Ports collection / FreeBSD CDs

2006-09-12 Thread ograbme
Howdie Jeff (if I may) and others,

Tuesday, September 12, 2006, 6:41:38 AM, you wrote:

JR On 12/09/06, Arindam [EMAIL PROTECTED] 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?  Nah,
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


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread RW
On Tuesday 12 September 2006 21:02, ograbme wrote:

 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,

The ports collection is a set of recipes that enable the the ports system to 
automatically fetch the source, extract it, patch it, build and install the 
result. You can do all this manually, but it's often not straightforward. And 
the added advantage is that software that's installed through the ports 
system is also registered in the package database- making it easier to 
deinstall and upgrade.  

Before you can build from ports, you need to have ports tree in place, the 
standard way to do this is by running portsnap.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Perry Hutchison
 Before you can build from ports, you need to have ports tree
 in place, the standard way to do this is by running portsnap.
 
with the caveat that, at least in my recent experience, an
up-to-date ports tree does not always play nicely with a
not-updated base install from CD.  OP might be better off
loading the ports collection from the same CD set as the
rest of the system.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Donald J. O'Neill

Perry Hutchison wrote:
Before you can build from ports, you need to have ports tree
in place, the standard way to do this is by running portsnap.
 
with the caveat that, at least in my recent experience, an

up-to-date ports tree does not always play nicely with a
not-updated base install from CD.  OP might be better off
loading the ports collection from the same CD set as the
rest of the system.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]



That's very interesting. However, the ports tree on the CD isn't 
complete, as in: not all the ports are there. I stopped installing the 
ports tree from the install CD a long time ago for that reason.


Don
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Re[4]: The Ports collection / FreeBSD CDs

2006-09-12 Thread Jeff Rollin

On 12/09/06, ograbme [EMAIL PROTECTED] wrote:


Hello Jeff,

First of all ... thanks for your help and suggestions ... please see
comments interwoven below.

Tuesday, September 12, 2006, 4:20:51 PM, you wrote:

snip

JR You need to go back into sysinstall and install the ports
JR collection. That will give you the framework for downloading
JR ports, but you will not be able to install them without network
JR access.

Understand.

JR If you want to install a package, the easiest way without
JR network access is to go back into sysinstall and choose it from
JR the Packages item. But, if the package you want is not available
JR on the FreeBSD install discs (if you need to eject one and insert
JR the other, it will tell you to), and you don't have a network
JR connection, I'm afraid you're out of luck.

This is the approach I took.  All looked like it was going well until
the point of needing to switch cdroms.  Couldn't do it.  My cdrom
would not eject so I could switch CDROMs.  Not sure what the problem
was/is, but got to thinking because it was mounted, i.e., mount /cdrom
manually initially by me before starting the sysinstall command.
Anyone I just ignored trying to install those packages that I had
selected and eventually finished up, but when finished, I could not
find the /usr/ports directory ... even though sysinstall reported
individually the selected packages were installed properly during the
process.  Oh well, something went awry.  I'll try again with hopefully
only selecting items from one cdrom to try to control the process in
that regard and see if I experience the same result.

JR If there's nothing else wrong with your system, you don't
JR need to reinstall; just type sysinstall as the root user and
JR you're in.

I cannot with certainly vouch there is nothing wrong with my system.
It hasn't locked up; it hasn't conked out on me; I've been able to do
a number of things (albeit they are cursory type things ... nothing
big ... executing various Unix commands, creating a few small C
programs and compiling them with gcc tool, etc) thus far, without
incident.

JR BTW, I would delete your manually-created /usr/ports
JR directory and everything in it, just in case.

I did this prior to the above steps.  The release I have installed is
FreeBSD 6.1 Release #0 May 07 ... perhaps this is part of the problems
I'm experiencing.  I bought the FreeBSD Mall 4 CDROM, May 2006
set.  May be I need to try to get a newer version.  I think I saw
where there is some release #2 mentioned by various list members.  I
suppose I could download it from the web site and burn it.  I'd only
need the first cdrom, right?

Thanks in advance.  While I may not be making leaps and bounds, I do
feel I'm making some headway!

Take care.



This sounds like a bug to me; before you do anything else I would:

1. Make sure there is no /usr/ports directory;

2. Insert the FBSD CDROM, *without mounting it*

3. Run sysinstall and attempt to install the ports tree again.

If this doesn't work, I would download the FBSD 6.1 CD from a mirror (it was
6.1 you were using, wasn't it?), burn it, and reinstall. If you are sure you
don't need any packages from CD2, you can forgo downloading and burning that
one. In fact if you have the net connection (and the patience), you can
download a bootonly iso that, when used to boot the system, downloads
everything else needed from the net.

HTH (especially as if it does not, I'm out of ideas! :-/)

BTW, if you DO end up reinstalling, make sure you reformat your partitions,
as I have sometimes run out of space when attempting to reinstall on
partitions with data still on them.


Jeff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Perry Hutchison
  ... at least in my recent experience, an up-to-date ports tree 
  does not always play nicely with a not-updated base install from
  CD.

 That's very interesting. However, the ports tree on the CD isn't
 complete, as in: not all the ports are there.

Any idea why?  (I am referring to the ports tree itself, i.e. the
collection of skeleton directories.  The set of distfiles provided
on CDs 3 and 4 is necessarily incomplete, both due to limited space
and because some distfiles have legal restrictions that prevent 
their inclusion.)

 I stopped installing the ports tree from the install CD a long
 time ago for that reason.

Perhaps sysinstall's rather strong recommendation to install the
ports ought to be toned down a bit, e.g. to suggest installing
the ports from CD only if one does not have a high-speed Internet
connection.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Donald J. O'Neill

Perry Hutchison wrote:
... at least in my recent experience, an up-to-date ports tree 
does not always play nicely with a not-updated base install from
CD.

That's very interesting. However, the ports tree on the CD isn't
complete, as in: not all the ports are there.


Any idea why?  (I am referring to the ports tree itself, i.e. the
collection of skeleton directories.  The set of distfiles provided
on CDs 3 and 4 is necessarily incomplete, both due to limited space
and because some distfiles have legal restrictions that prevent 
their inclusion.)



I stopped installing the ports tree from the install CD a long
time ago for that reason.


Perhaps sysinstall's rather strong recommendation to install the
ports ought to be toned down a bit, e.g. to suggest installing
the ports from CD only if one does not have a high-speed Internet
connection.



You've asked a question, given some clarification as to what you are 
referring to, and I can tell you I don't have anything other than 
possibilities - which may be far from the truth - as to why this is. 
You're referring to a 4 CD set, that can't be downloaded from 
FreeBSD.org, that has to come from somewhere else, such as the
FreeBSD Mall or somewhere else. I would use that if I couldn't connect 
to the Internet at all.


Maybe, I should say: I can't tell you why it is that way. I've never 
been very concerned about it, just understood that it was that way and 
lived with it. I've never had a problem with an up-to-date ports tree 
not playing nicely with a RELEASE or a STABLE install. I suspect the 
reason is that I just never happened to up-date the ports tree at a time 
when there were problems. It does happen at times, but then... You've 
probably heard the advice somethings wrong with your ports tree, blow 
it off and re-install it. It's not a big problem to deal with, the 
problem comes when you need to do it and don't.


Sysinstall only asks if you want to install the ports tree. If I was 
going to update it with cvsup, I would install it from there. I use 
portsnap, so I don't install it from the CD.



Yes, I have a hi-speed connection. It makes things easier. I wouldn't be 
without it.


Don
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: The Ports collection / FreeBSD CDs

2006-09-12 Thread Frank Shute
On Tue, Sep 12, 2006 at 04:02:33PM -0400, ograbme wrote:

 Howdie Jeff (if I may) and others,
 
 Tuesday, September 12, 2006, 6:41:38 AM, you wrote:
 
 JR On 12/09/06, Arindam [EMAIL PROTECTED] 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?  Nah,
 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.

Go grab the compressed, reasonably up to date ports tree:

$ fetch -dpv ftp.freebsd.org/pub/FreeBSD/ports/ports/ports.tar.gz

(warning! 35MB compressed)

and:

# mv ports.tar.gz /usr/ports
# cd /usr/ports
# tar xvzf ports.tar.gz

to build sudo, first check that there's nothing funny with building
sudo:

$ cat /usr/ports/UPDATING | grep sudo

if there's nothing then:

# cd /usr/ports/security/sudo/
# make install clean

Then read the handbook about keeping your ports tree up to date using
portsnap or cvsup.

 
 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
 

That's OK. I usually post to the list and cc to the person who posted
in the first place as they may not be subscribed to the list.

Welcome to FreeBSD!

-- 

 Frank 


echo f r a n k @ e s p e r a n c e - l i n u x . c o . u k | sed 's/ //g'

  ---PGP keyID: 0x10BD6F4B---  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]