Re: installation sequence

2009-08-21 Thread Ruben de Groot
On Fri, Aug 21, 2009 at 01:29:26AM +, b. f. typed:
 Lane Holcombe wrote:
 
 Here's what you do:  Setup for yourself a local cvs repository like so:
 
 portinstall -Pp net/cvsup-mirror
 
 You have to make decisions about what to mirror, but in the end you will
 have a semi-authoritative mirror of all the source and ports for the
 whole dang FreeBSD development tree, that will maintain itself and be
 ready when you need it.
 
 It's good advice to make sure that you are using a base system and
 ports tree that are up-to-date, or at least contemporaneous and from a
 stable snapshot.  But it seems to me to be overkill to ask someone who
 is having trouble installing ports to mirror the FreeBSD repository.
 Snapshots downloaded per the instructions in the FreeBSD Handbook
 ought to be enough for most people.

Besides, an uptodate portstree is no guarantee at all that all ports will
compile and/or all dependencies will work. That's why there are periods of
ports freeze before every RELEASE.

On a desktop system, I tend to use binary packages only, coming with the
release. 

Ruben

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


Re: installation sequence

2009-08-21 Thread Michael Powell
PJ wrote:

 Does anybody have an idea of what the oder of files and dependencies is
 to install programs without all sorts of nonsensical errors?
 I usually have no problem installing FreeBsd whatever with apache22,
 cups, samba, php, mysql xorg etc. etc. I say usually because from time
 to time there do crop up some conflicts and they can usually be resolved
 by just looking at the error messages when the install is interrupted...
 usually one reinstalls the guilty port and voila! all things are in an
 ordered universe!
 But how do you avoid those error messages... I installed a pretty
 minimal 7.2 about a week ago and since then have been putzing about with
 a more serious installation of 7.2 on a larger disk to include xorg and
 a number of pretty cumbersome applications.
 I usually start with samba as that permits me to wander about on my lan
 and download and play around with other stuff while I am waiting for
 those substantial installs like jdk and xorg et al.
 So now, I have installed samba... works fine... thereafter I have been
 installing jdk16 and some other proggies like openldap and php5 and
 mysql ... actually, I was doing those because apache22 wouldn't
 compile... it grinds out a slew of errors that all seem to be related to
 ldap...util_ldap.c:2135 (or other numbers) and all have the notation
 undeclared (first use in this function) and finally the ghost gives up
 with Error code 1.
 
 Exactly the same installation with the same configuration on the smaller
 installation went without a hitch... (and on the same computer,
 different disk) The versions are the latest available and on 7.2...
 I have tried uninstalling php5, openldap, and removing the work
 directory for apache22, but the result is always the same... this is
 absurd. Can anybody make any sense of this... I don't like the idea of
 starting all over again... done that, been there, and still looking for
 some rationality to this world.
 Thanks for any ideas...
 ___

Not entirely sure this is totally relevant, but I wouldn't install any 
packages or third party apps when first installing a fresh system. The 
packages built at the time the release CD was created are already out of 
date and the ports tree has moved forward.

It's OK to go ahead and install the ports tree as part of the fresh install, 
however do not use it! The first thing I do after a fresh install is to csup 
the ports tree to '*default release=cvs tag=.'. (I know it's silly but don't 
confuse the tag=. with the end of sentence.) You have the best chance now 
for dependency tracking to be dead on, but the chance always remains that at 
any one given point in time there may be errors. The ports tree is fluid and 
changes constantly. Usually if there is a problem and the port(s) 
maintainers are made aware they get it fixed fairly quick and a quick csup 
after they repair will make it all good again.

Also realize that the previously mentioned tag if applied to src-all will 
pull down the sources for -CURRENT/HEAD. I have two separate sup files for 
each collection, one for source and one for ports. You can put them both in 
the same supfile if you want and there have been recent examples posted, you 
just have to make sure to get it right or you'll have a real mess. In other 
words, be aware of the different tags between tracking src-all and ports-
all. Should you use the wrong tag to track ports-all you may experience 
inconsistent problems.

On another note, should you find yourself in a position where you have two 
perfectly identical machines sitting next to each other, e.g., you know 
positively for a fact that everything is the same such as ports tree freshly 
csup'ed, etc, and one machine is barfing during compiling you may have a 
marginally bad hardware memory problem. Compiling (especially make 
world/kernel) really hits the memory hard. I once had a machine whose memory 
would 'sing' with an audible tone only during compilation. Such a noise in 
chip circuitry is an oscillation which should not happen and if you continue 
to operate the chip under that set of conditions it will fry. 

About the only thing you could try in this scenario would be to add latency 
clocks to the RAM in the mainboard BIOS. Whether this actually helps would 
really only be test of the hypothesis and not a true fix. Most memory should 
just auto time itself by SPD and shouldn't need to be 'slowed down'. If I 
saw this I'd replace the memory with new, as if it can't operate correctly 
at the SPD timings it is of substandard quality. 

-Mike



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


Re: installation sequence

2009-08-21 Thread PJ
Neal Hogan wrote:
 On Thu, Aug 20, 2009 at 6:12 PM, PJaf.gour...@videotron.ca wrote:
   
 Does anybody have an idea of what the oder of files and dependencies is
 to install programs without all sorts of nonsensical errors?
 I usually have no problem installing FreeBsd whatever with apache22,
 cups, samba, php, mysql xorg etc. etc. I say usually because from time
 to time there do crop up some conflicts and they can usually be resolved
 by just looking at the error messages when the install is interrupted...
 usually one reinstalls the guilty port and voila! all things are in an
 ordered universe!
 But how do you avoid those error messages... I installed a pretty
 minimal 7.2 about a week ago and since then have been putzing about with
 a more serious installation of 7.2 on a larger disk to include xorg and
 a number of pretty cumbersome applications.
 I usually start with samba as that permits me to wander about on my lan
 and download and play around with other stuff while I am waiting for
 those substantial installs like jdk and xorg et al.
 So now, I have installed samba... works fine... thereafter I have been
 installing jdk16 and some other proggies like openldap and php5 and
 mysql ... actually, I was doing those because apache22 wouldn't
 compile... it grinds out a slew of errors that all seem to be related to
 ldap...util_ldap.c:2135 (or other numbers) and all have the notation
 undeclared (first use in this function) and finally the ghost gives up
 with Error code 1.

 Exactly the same installation with the same configuration on the smaller
 installation went without a hitch... (and on the same computer,
 different disk) The versions are the latest available and on 7.2...
 I have tried uninstalling php5, openldap, and removing the work
 directory for apache22, but the result is always the same... this is absurd.
 Can anybody make any sense of this... I don't like the idea of starting
 all over again... done that, been there, and still looking for some
 rationality to this world.
 Thanks for any ideas...
 

 Again, not to be rude (to you or fBSD) . . . but why stick with
 something that is giving you soo much trouble?
 There are a bunch of open source distros out there. I can appreciate
 that you do not want to f'around with another distro for another week
 . . . but . . .

 From other posts, it sounded like you have recovered the essential
 files. Rationality may dictate you moving on.

 The only thing I can suggest that may help those who know better, is
 to post the demsg's of the two machines (the one that works and the
 pain in the ass), given that they are different machines. What
 happened to the faulty hardware idea?

 I dunno . . . good luck!
   

First, the problem is not FreeBSD... it is the idiots who think they know how 
to deal with a lot of stuff and then post all sorts of stuff that just confuses 
the hell out of simpletons like me. I made the mistake of thinking some jerk 
had written a little script that would do an update of ports with csup... well, 
I did post looking for an explanation of why the damned thing didn't work... 
and the responses I got were rather cryptic and din't explain anything even 
though a good programmer would have understood it would not work...  :-) 
I'm certainly not a programmer in the professional sense at all...
so in thinking about the problem I saw that the ports were not being correctly 
updated... once I got that right, everything worked fine. I even fixed that 
little script and updates are a cinch.

As for faulty hardware... haven't found any up to now... I hae just 1 drive 
left to check and I'll know for sure...  ;-) 





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

 

   

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


Re: installation sequence

2009-08-21 Thread PJ
Lane Holcombe wrote:
 I'm all over this!

 Here's what you do: Setup for yourself a local cvs repository like so:

 portinstall -Pp net/cvsup-mirror

 You have to make decisions about what to mirror, but in the end you will
 have a semi-authoritative mirror of all the source and ports for the
 whole dang FreeBSD development tree, that will maintain itself and be
 ready when you need it.

 Next, when ever you do a fresh install of FreeBSD whatever, the first
 thing you do after the install is update your source and ports try by
 creating a cvsupfile, (I always keep one in /usr/local/etc/cvsupfile)
 like this:

 begin cvsupfile
 *default host=IP.OF.YOUR.LOCAL.CVS.MIRROR
 *default base=/usr
 *default prefix=/usr
 *default release=cvs delete use-rel-suffix tag=RELENG_7
 *default compress
 src-all
 src-contrib
 ports-all tag=.
 /end cvsupfile

 Note that the begin and /end tags are put in the email for clarity,
 but should NOT appear in your cvsup file. I think src-contrib is
 overkill, but I've not bothered to find out because I'm pretty lazy.

 Note, also that RELENG_7 is just what I'm using now. You should adjust
 to the FreeBSD whatever that you just installed.

 So after you put the cvsupfile in place, run this on your new install:

 csup -g -L2 /path/to/cvsupfile

 Note, again, that csup does *not* get installed with *base before like
 6.3 or something ... can't remember which. Did I mention lazy? If you
 are going back that far you have to install csup from ports or install
 cvsup from ports. (Which may likely put you back at square one where
 you have to work through the build failures - it ain't perfect, but it's
 nearly there!)

 Anyway, the point is you should always, always, always update your ports
 tree after a new install so you don't have build failures to stump you.

 And you still might get those :)

 So you should consider REBUILDING WORLD immediately after you do a new
 install. And THEN build/install whatever ports you need ...

Ok, I normally do something like that... problem here was that I made
the mistake of thinking that an interesting little script I found was
good for updating... but, I was sadly mistaken. The error was due to a
badly downloaded ports tree. That fixed, all works fine.
I really only have problems when some extraneous garbage comes along and
I'm suckere in to try it.
Here's the script (I modified it and it seems to work just fine) but I
sure would like to hear if that makes sense.
I called it update.ports and it runs from any directory. It can be
changed to update source and docs if so desired or all could be done
from same script.  Let me know, please, if it's ok?
==
#!/bin/sh
#
# Update source, docs and ports

LOCAL_DIR=$(pwd)

cd /usr/share/examples/cvsup
csup ports-supfile
cd /usr/ports
make fetchindex

/usr/local/sbin/portsdb -u
/usr//local/sbin/pkgdb -uvF

cd $LOCAL_DIR
===


 Good Luck!

 lane

 On Thu, 2009-08-20 at 19:12 -0400, PJ wrote:
 Does anybody have an idea of what the oder of files and dependencies is
 to install programs without all sorts of nonsensical errors?
 I usually have no problem installing FreeBsd whatever with apache22,
 cups, samba, php, mysql xorg etc. etc. I say usually because from time
 to time there do crop up some conflicts and they can usually be resolved
 by just looking at the error messages when the install is interrupted...
 usually one reinstalls the guilty port and voila! all things are in an
 ordered universe!
 But how do you avoid those error messages... I installed a pretty
 minimal 7.2 about a week ago and since then have been putzing about with
 a more serious installation of 7.2 on a larger disk to include xorg and
 a number of pretty cumbersome applications.
 I usually start with samba as that permits me to wander about on my lan
 and download and play around with other stuff while I am waiting for
 those substantial installs like jdk and xorg et al.
 So now, I have installed samba... works fine... thereafter I have been
 installing jdk16 and some other proggies like openldap and php5 and
 mysql ... actually, I was doing those because apache22 wouldn't
 compile... it grinds out a slew of errors that all seem to be related to
 ldap...util_ldap.c:2135 (or other numbers) and all have the notation
 undeclared (first use in this function) and finally the ghost gives up
 with Error code 1.

 Exactly the same installation with the same configuration on the smaller
 installation went without a hitch... (and on the same computer,
 different disk) The versions are the latest available and on 7.2...
 I have tried uninstalling php5, openldap, and removing the work
 directory for apache22, but the result is always the same... this is
 absurd.
 Can anybody make any sense of this... I don't like the idea of starting
 all over again... done that, been there, and still looking for some
 rationality to this world.
 Thanks for any ideas...
 ___
 freebsd-questions@freebsd.org mailing list

Re: installation sequence

2009-08-21 Thread Adam Vande More
On Fri, Aug 21, 2009 at 12:01 PM, PJ af.gour...@videotron.ca wrote:

 Lane Holcombe wrote:
  I'm all over this!
 
  Here's what you do: Setup for yourself a local cvs repository like so:
 
  portinstall -Pp net/cvsup-mirror
 
  You have to make decisions about what to mirror, but in the end you will
  have a semi-authoritative mirror of all the source and ports for the
  whole dang FreeBSD development tree, that will maintain itself and be
  ready when you need it.
 
  Next, when ever you do a fresh install of FreeBSD whatever, the first
  thing you do after the install is update your source and ports try by
  creating a cvsupfile, (I always keep one in /usr/local/etc/cvsupfile)
  like this:
 
  begin cvsupfile
  *default host=IP.OF.YOUR.LOCAL.CVS.MIRROR
  *default base=/usr
  *default prefix=/usr
  *default release=cvs delete use-rel-suffix tag=RELENG_7
  *default compress
  src-all
  src-contrib
  ports-all tag=.
  /end cvsupfile
 
  Note that the begin and /end tags are put in the email for clarity,
  but should NOT appear in your cvsup file. I think src-contrib is
  overkill, but I've not bothered to find out because I'm pretty lazy.
 
  Note, also that RELENG_7 is just what I'm using now. You should adjust
  to the FreeBSD whatever that you just installed.
 
  So after you put the cvsupfile in place, run this on your new install:
 
  csup -g -L2 /path/to/cvsupfile
 
  Note, again, that csup does *not* get installed with *base before like
  6.3 or something ... can't remember which. Did I mention lazy? If you
  are going back that far you have to install csup from ports or install
  cvsup from ports. (Which may likely put you back at square one where
  you have to work through the build failures - it ain't perfect, but it's
  nearly there!)
 
  Anyway, the point is you should always, always, always update your ports
  tree after a new install so you don't have build failures to stump you.
 
  And you still might get those :)
 
  So you should consider REBUILDING WORLD immediately after you do a new
  install. And THEN build/install whatever ports you need ...

 Ok, I normally do something like that... problem here was that I made
 the mistake of thinking that an interesting little script I found was
 good for updating... but, I was sadly mistaken. The error was due to a
 badly downloaded ports tree. That fixed, all works fine.
 I really only have problems when some extraneous garbage comes along and
 I'm suckere in to try it.
 Here's the script (I modified it and it seems to work just fine) but I
 sure would like to hear if that makes sense.
 I called it update.ports and it runs from any directory. It can be
 changed to update source and docs if so desired or all could be done
 from same script.  Let me know, please, if it's ok?
 ==
 #!/bin/sh
 #
 # Update source, docs and ports

 LOCAL_DIR=$(pwd)

 cd /usr/share/examples/cvsup
 csup ports-supfile
 cd /usr/ports
 make fetchindex

 /usr/local/sbin/portsdb -u
 /usr//local/sbin/pkgdb -uvF

 cd $LOCAL_DIR
 ===

 
  Good Luck!
 
  lane
 
  On Thu, 2009-08-20 at 19:12 -0400, PJ wrote:
  Does anybody have an idea of what the oder of files and dependencies is
  to install programs without all sorts of nonsensical errors?
  I usually have no problem installing FreeBsd whatever with apache22,
  cups, samba, php, mysql xorg etc. etc. I say usually because from time
  to time there do crop up some conflicts and they can usually be resolved
  by just looking at the error messages when the install is interrupted...
  usually one reinstalls the guilty port and voila! all things are in an
  ordered universe!
  But how do you avoid those error messages... I installed a pretty
  minimal 7.2 about a week ago and since then have been putzing about with
  a more serious installation of 7.2 on a larger disk to include xorg and
  a number of pretty cumbersome applications.
  I usually start with samba as that permits me to wander about on my lan
  and download and play around with other stuff while I am waiting for
  those substantial installs like jdk and xorg et al.
  So now, I have installed samba... works fine... thereafter I have been
  installing jdk16 and some other proggies like openldap and php5 and
  mysql ... actually, I was doing those because apache22 wouldn't
  compile... it grinds out a slew of errors that all seem to be related to
  ldap...util_ldap.c:2135 (or other numbers) and all have the notation
  undeclared (first use in this function) and finally the ghost gives up
  with Error code 1.
 
  Exactly the same installation with the same configuration on the smaller
  installation went without a hitch... (and on the same computer,
  different disk) The versions are the latest available and on 7.2...
  I have tried uninstalling php5, openldap, and removing the work
  directory for apache22, but the result is always the same... this is
  absurd.
  Can anybody make any sense of this... I don't like the idea of starting
  all over again... done that, 

Re: Installation sequence

2009-08-21 Thread b. f.
from same script.  Let me know, please, if it's ok?

Well, not quite.


==
#!/bin/sh
#
# Update source, docs and ports

LOCAL_DIR=$(pwd)

You don't need to change directories if you change some of the
commands slightly, so the above line and the last line are
unnecessary.


cd /usr/share/examples/cvsup
csup ports-supfile

The example scripts shouldn't be run as-is: you need to edit them
first, or issue more flags on the command-line.  For instance, for the
ports-supfile you need at least to either change the

*default host ...

line to use the server of your choice, or issue a -h flag with the
right server in your script. (The choice of the right server can make
a substantial difference in how long this process takes -- you can
experiment with different servers, and/or use the
sysutils/fastest_cvsup port to find one that works well for you.  Not
every server is updated at the same interval.)  Also, you can avoid
changing directories by just using a full path to the cvsup script
file.  So, for example, you should replace the above two lines in the
script with something like:

csup -L 2 -h cvsup1.ca.FreeBSD.org /usr/share/examples/cvsup/ports-supfile

I prefer to increase the verbosity with the -L switch, so that I have
a better idea of what's happening if something goes wrong.  All of
this is covered in the FreeBSD Handbook.  Also, you need not use
csup(1) at all if you prefer to use portsnap(8) instead.


cd /usr/ports
make fetchindex

/usr/local/sbin/portsdb -u

You don't need all of the three previous lines: you can just run
'portsdb -F' or 'portsdb -Fu' instead.  Also, these lines and the line
below require one of the portupgrade ports to be installed, but I
guess you know that.  If you're not planning on using portupgrade,
then don't use the portsdb or pkgdb commands, but just run: 'make -C
/usr/ports fetchindex' instead.

/usr//local/sbin/pkgdb -uvF

cd $LOCAL_DIR


As I mentioned, you don't need this last line.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: installation sequence

2009-08-21 Thread Michael Powell
PJ wrote:

[snip]
 
 Ok, I normally do something like that... problem here was that I made
 the mistake of thinking that an interesting little script I found was
 good for updating... but, I was sadly mistaken. The error was due to a
 badly downloaded ports tree. That fixed, all works fine.
 I really only have problems when some extraneous garbage comes along and
 I'm suckere in to try it.
 Here's the script (I modified it and it seems to work just fine) but I
 sure would like to hear if that makes sense.
 I called it update.ports and it runs from any directory. It can be
 changed to update source and docs if so desired or all could be done
 from same script.  Let me know, please, if it's ok?
 ==
 #!/bin/sh
 #
 # Update source, docs and ports
 
 LOCAL_DIR=$(pwd)
 
 cd /usr/share/examples/cvsup
 csup ports-supfile
 cd /usr/ports
 make fetchindex
 
 /usr/local/sbin/portsdb -u
 /usr//local/sbin/pkgdb -uvF
 
 cd $LOCAL_DIR
 ===
 

I essentially do something very similar. About once a week I do this:

csup -L 2 ports  portsdb -uF  pkgdb -u  portversion

This pretty much does the same thing as the script.

I keep intending to make it a cron job and email me the output, but until I 
get 'round to it I just take a quick gander at the output and if needed 
issue a portupgrade -a. 9.8 times out of 10 this is all I ever need. Every 
once in a while I have to manually fix something, but that isn't all that 
often, maybe once or twice a year. Another thing is to read UPDATING 
religiously as this can help sidestep boo boos before they happen.

[snip]

-Mike


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


Re: installation sequence

2009-08-20 Thread Neal Hogan
On Thu, Aug 20, 2009 at 6:12 PM, PJaf.gour...@videotron.ca wrote:
 Does anybody have an idea of what the oder of files and dependencies is
 to install programs without all sorts of nonsensical errors?
 I usually have no problem installing FreeBsd whatever with apache22,
 cups, samba, php, mysql xorg etc. etc. I say usually because from time
 to time there do crop up some conflicts and they can usually be resolved
 by just looking at the error messages when the install is interrupted...
 usually one reinstalls the guilty port and voila! all things are in an
 ordered universe!
 But how do you avoid those error messages... I installed a pretty
 minimal 7.2 about a week ago and since then have been putzing about with
 a more serious installation of 7.2 on a larger disk to include xorg and
 a number of pretty cumbersome applications.
 I usually start with samba as that permits me to wander about on my lan
 and download and play around with other stuff while I am waiting for
 those substantial installs like jdk and xorg et al.
 So now, I have installed samba... works fine... thereafter I have been
 installing jdk16 and some other proggies like openldap and php5 and
 mysql ... actually, I was doing those because apache22 wouldn't
 compile... it grinds out a slew of errors that all seem to be related to
 ldap...util_ldap.c:2135 (or other numbers) and all have the notation
 undeclared (first use in this function) and finally the ghost gives up
 with Error code 1.

 Exactly the same installation with the same configuration on the smaller
 installation went without a hitch... (and on the same computer,
 different disk) The versions are the latest available and on 7.2...
 I have tried uninstalling php5, openldap, and removing the work
 directory for apache22, but the result is always the same... this is absurd.
 Can anybody make any sense of this... I don't like the idea of starting
 all over again... done that, been there, and still looking for some
 rationality to this world.
 Thanks for any ideas...

Again, not to be rude (to you or fBSD) . . . but why stick with
something that is giving you soo much trouble?
There are a bunch of open source distros out there. I can appreciate
that you do not want to f'around with another distro for another week
. . . but . . .

From other posts, it sounded like you have recovered the essential
files. Rationality may dictate you moving on.

The only thing I can suggest that may help those who know better, is
to post the demsg's of the two machines (the one that works and the
pain in the ass), given that they are different machines. What
happened to the faulty hardware idea?

I dunno . . . good luck!

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

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


Re: installation sequence

2009-08-20 Thread Lane Holcombe
I'm all over this!

Here's what you do:  Setup for yourself a local cvs repository like so:

portinstall -Pp net/cvsup-mirror

You have to make decisions about what to mirror, but in the end you will
have a semi-authoritative mirror of all the source and ports for the
whole dang FreeBSD development tree, that will maintain itself and be
ready when you need it.

Next, when ever you do a fresh install of FreeBSD whatever, the first
thing you do after the install is update your source and ports try by
creating a cvsupfile, (I always keep one in /usr/local/etc/cvsupfile)
like this:

begin cvsupfile
*default host=IP.OF.YOUR.LOCAL.CVS.MIRROR
*default base=/usr
*default prefix=/usr
*default release=cvs delete use-rel-suffix tag=RELENG_7
*default compress
src-all
src-contrib 
ports-all tag=.
/end cvsupfile

Note that the begin and /end tags are put in the email for clarity,
but should NOT appear in your cvsup file.  I think src-contrib is
overkill, but I've not bothered to find out because I'm pretty lazy.

Note, also that RELENG_7 is just what I'm using now.  You should adjust
to the FreeBSD whatever that you just installed.

So after you put the cvsupfile in place, run this on your new install:

csup -g -L2 /path/to/cvsupfile

Note, again, that csup does *not* get installed with *base before like
6.3 or something ... can't remember which.   Did I mention lazy?  If you
are going back that far you have to install csup from ports or install
cvsup from ports.  (Which may likely put you back at square one where
you have to work through the build failures - it ain't perfect, but it's
nearly there!)

Anyway, the point is you should always, always, always update your ports
tree after a new install so you don't have build failures to stump you.

And  you still might get those :)

So you should consider REBUILDING WORLD immediately after you do a new
install.  And THEN build/install whatever ports you need ...

Good Luck!

lane

On Thu, 2009-08-20 at 19:12 -0400, PJ wrote:
 Does anybody have an idea of what the oder of files and dependencies is
 to install programs without all sorts of nonsensical errors?
 I usually have no problem installing FreeBsd whatever with apache22,
 cups, samba, php, mysql xorg etc. etc. I say usually because from time
 to time there do crop up some conflicts and they can usually be resolved
 by just looking at the error messages when the install is interrupted...
 usually one reinstalls the guilty port and voila! all things are in an
 ordered universe!
 But how do you avoid those error messages... I installed a pretty
 minimal 7.2 about a week ago and since then have been putzing about with
 a more serious installation of 7.2 on a larger disk to include xorg and
 a number of pretty cumbersome applications.
 I usually start with samba as that permits me to wander about on my lan
 and download and play around with other stuff while I am waiting for
 those substantial installs like jdk and xorg et al.
 So now, I have installed samba... works fine... thereafter I have been
 installing jdk16 and some other proggies like openldap and php5 and
 mysql ... actually, I was doing those because apache22 wouldn't
 compile... it grinds out a slew of errors that all seem to be related to
 ldap...util_ldap.c:2135 (or other numbers) and all have the notation
 undeclared (first use in this function) and finally the ghost gives up
 with Error code 1.
 
 Exactly the same installation with the same configuration on the smaller
 installation went without a hitch... (and on the same computer,
 different disk) The versions are the latest available and on 7.2...
 I have tried uninstalling php5, openldap, and removing the work
 directory for apache22, but the result is always the same... this is absurd.
 Can anybody make any sense of this... I don't like the idea of starting
 all over again... done that, been there, and still looking for some
 rationality to this world.
 Thanks for any ideas...
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
 

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


Re: installation sequence

2009-08-20 Thread b. f.
Lane Holcombe wrote:

Here's what you do:  Setup for yourself a local cvs repository like so:

portinstall -Pp net/cvsup-mirror

You have to make decisions about what to mirror, but in the end you will
have a semi-authoritative mirror of all the source and ports for the
whole dang FreeBSD development tree, that will maintain itself and be
ready when you need it.

It's good advice to make sure that you are using a base system and
ports tree that are up-to-date, or at least contemporaneous and from a
stable snapshot.  But it seems to me to be overkill to ask someone who
is having trouble installing ports to mirror the FreeBSD repository.
Snapshots downloaded per the instructions in the FreeBSD Handbook
ought to be enough for most people.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: installation sequence

2009-08-20 Thread b. f.
Does anybody have an idea of what the oder of files and dependencies is
to install programs without all sorts of nonsensical errors?

This is supposed to be automated, but of course things can sometimes
go wrong, either through hardware problems, user-error, or an error in
Ports.

I usually have no problem installing FreeBsd whatever with apache22,
cups, samba, php, mysql xorg etc. etc. I say usually because from time
to time there do crop up some conflicts and they can usually be resolved
by just looking at the error messages when the install is interrupted...
usually one reinstalls the guilty port and voila! all things are in an
ordered universe!
But how do you avoid those error messages... I installed a pretty
minimal 7.2 about a week ago and since then have been putzing about with
a more serious installation of 7.2 on a larger disk to include xorg and
a number of pretty cumbersome applications.
I usually start with samba as that permits me to wander about on my lan
and download and play around with other stuff while I am waiting for
those substantial installs like jdk and xorg et al.
So now, I have installed samba... works fine... thereafter I have been
installing jdk16 and some other proggies like openldap and php5 and
mysql ... actually, I was doing those because apache22 wouldn't
compile... it grinds out a slew of errors that all seem to be related to
ldap...util_ldap.c:2135 (or other numbers) and all have the notation
undeclared (first use in this function) and finally the ghost gives up
with Error code 1.

It sounds like a missing header, but you need to tell us more before
we can attempt to figure out why.  Don't spend a lot of time and
energy paraphrasing what happened, but rather include the end of a
build transcript with your message, beginning a few lines above where
the first error appeared.  You can cut-and-paste, or use script1) to
capture the output, or whatever -- but we need to see the _exact_
output.  Also include a list of the ports that you have installed now,
and  the OPTIONS settings, if any, of the port and the ports that it
depends upon. Also check to see when you are installing a new port
that:

1) you are using a up-to-date ports tree and INDEX file (or at least a
snapshot that has no known errors), and an up-to-date portsdb and
pkgdb if you are using portupgrade;
2) all of your currently installed ports are up-to-date (or at least
consistent with your ports tree);
3) you are starting with clean work directories for the port that you
want to  build and install, and all ports that will also need to be
build and installed as missing dependencies;
4) your installed ports and base system have not been corrupted;
5) you have no known hardware problems, like bad memory or a
malfunctioning hard drive.

And you know, you don't have to build from source -- you could just
download and install prebuilt binary packages, either from FreeBSD
Ports or some other packaging system...


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org