Disaster recovery ?
Hi I had a working FreeBSd 5.3 RELEASE server running postfix and zope until last night. When I checked it in the morning, it had a bunch of ad4 ... UNRECOVERABLE ERROR messages on it. Upon a reboot, it complains it cannot find /boot/loader (error 16). Last week, it had shut down without any apparent reason but came up upon reboot. Sounds like the hard disk is fried. Its a new server (just 5 months old or so). How do I recover what was on the partitions ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Effective user issue with zope
Hi
I am setting up zope-2.7.5-final on a server (FreeBSD 5.3-RELEASE).
Installed python-2.3.5 from sources (not ports). After configuring and
compiling it correctly, I got an initial error on running runzope.
Following the exhortation I found on the following webpage :
http://mail.zope.org/pipermail/zope/2004-May/149695.html
I created a new user (zopeuser), added it to group users, and tried to run
runzope as that user. I also changed the effective_user to zopeuser in
zope.conf. However, I now get the error :
Traceback (most recent call last):
File /usr/local/zope/lib/python/Zope/Startup/run.py, line 50, in ?
run()
File /usr/local/zope/lib/python/Zope/Startup/run.py, line 19, in run
start_zope(opts.configroot)
File /usr/local/zope/lib/python/Zope/Startup/__init__.py, line 52, in
start_zope
starter.startZope()
File /usr/local/zope/lib/python/Zope/Startup/__init__.py, line 231, in
startZope
Zope.startup()
File /usr/local/zope/lib/python/Zope/__init__.py, line 47, in startup
_startup()
File /usr/local/zope/lib/python/Zope/App/startup.py, line 57, in startup
DB = configuration.dbtab.getDatabase('/', is_root=1)
File /usr/local/zope/lib/python/DBTab/DBTab.py, line 96, in getDatabase
db = self._createDatabase(name, is_root)
File /usr/local/zope/lib/python/DBTab/DBTab.py, line 113, in
_createDatabase
db = factory.open()
File /usr/local/zope/lib/python/Zope/Startup/datatypes.py, line 172, in
open
DB = self.createDB()
File /usr/local/zope/lib/python/Zope/Startup/datatypes.py, line 169, in
createDB
return ZODBDatabase.open(self)
File /usr/local/zope/lib/python/ZODB/config.py, line 97, in open
return ZODB.DB(section.storage.open(),
File /usr/local/zope/lib/python/ZODB/config.py, line 128, in open
quota=self.config.quota)
File /usr/local/zope/lib/python/ZODB/FileStorage.py, line 227, in
__init__
self._lock_file = LockFile(file_name + '.lock')
File /usr/local/zope/lib/python/ZODB/lock_file.py, line 60, in __init__
self._fp = open(path, 'w+')
IOError: [Errno 13] Permission denied:
'/usr/local/zope/instance/var/Data.fs.lock'
I understand partially why this error is occuring - zopeuser does not have
write permissions in the instance directory. I wonder how is this issue
resolved - does one change the group ownership of the entire zope tree to a
new group (say zopeusers) and add zopeuser to that group, or what ?
Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for All-in-One device?
On Saturday 19 March 2005 08:29, Brian J. McGovern wrote: I'm currently in the market for an All-in-One device for the home network, mostly for the fax functionality (it'll be replacing an Canon scanner and Okidata 810e laser printer). Before anyone suggests their favorite FreeBSD Fax modem/app, I'll let it be known that I've been told that the expectation is that we'll have a normal looking/working fax machine for the house ;) I've searched the mailing lists for All-in-One, and tried searches on printers, scanners, copiers, and faxes individually with no real good hits. I'm somewhat curious about the HPs, but wanted to get people's experiences with different devices, and what works/doesn't work with FreeBSD. -B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I have an HP OfficeJet K80xi (fax + scan + print + copy). It looks partially like a normal fax machine. I think that HP does not produce it any longer. However, I have used it for almost 3 years without any problems. Look at www.linuxprinting.org to find out about supported printers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dovecot is broken in ports
On Tuesday 15 March 2005 11:08, Jim Trigg wrote: On Mon, March 14, 2005 11:43 pm, Madhusudan Singh said: Hi Just want to report that dovecot seems to be broken : === Returning to build of dovecot-0.99.14 === dovecot-0.99.14 depends on shared library: sasl2.2 - found === dovecot-0.99.14 depends on shared library: ldap-2.2.7 - found === dovecot-0.99.14 depends on shared library: iconv.3 - found [snip] install: /usr/ports/mail/dovecot/work/dovecot-0.99.14/src/imap/imap: No such file or directory *** Error code 71 It looks to me like the problem must be in the ldap integration; I just upgraded my copy last night with no problems, and do use sasl but not ldap. Jim Thanks for your response. However, any attempt to clean it, remove gnutls (pkg_delete) and install it again fails with : === dovecot-0.99.14 Currently incompatible with security/gnutls. I do not have gnutls installed now (just removed it). Why should I get this message (even after make clean and make distclean) ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dovecot is broken in ports
On Tuesday 15 March 2005 20:57, Jud wrote: Thanks for your response. However, any attempt to clean it, remove gnutls (pkg_delete) and install it again fails with : === dovecot-0.99.14 Currently incompatible with security/gnutls. I do not have gnutls installed now (just removed it). Why should I get this message (even after make clean and make distclean) ? # make config will allow you to redo your config choices and select SSL rather than GNUTLS, support for which is broken in Dovecot itself ATM, thus in the port also. Jud That did the trick. Thanks ! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dovecot is broken in ports
Hi Just want to report that dovecot seems to be broken : === Returning to build of dovecot-0.99.14 === dovecot-0.99.14 depends on shared library: sasl2.2 - found === dovecot-0.99.14 depends on shared library: ldap-2.2.7 - found === dovecot-0.99.14 depends on shared library: iconv.3 - found You need a group dovecot. Would you like me to create it [y]? Done. You need a user dovecot. Would you like me to create it [y]? Done. === Generating temporary packing list === Checking if mail/dovecot already installed install -s -o root -g wheel -m 555 /usr/ports/mail/dovecot/work/dovecot-0.99.14/src/imap/imap /usr/ports/mail/dovecot/work/dovecot-0.99.14/src/pop3/pop3 /usr/ports/mail/dovecot/work/dovecot-0.99.14/src/auth/dovecot-auth /usr/ports/mail/dovecot/work/dovecot-0.99.14/src/imap-login/imap-login /usr/ports/mail/dovecot/work/dovecot-0.99.14/src/pop3-login/pop3-login /usr/local/libexec/dovecot/ install: /usr/ports/mail/dovecot/work/dovecot-0.99.14/src/imap/imap: No such file or directory *** Error code 71 Stop in /usr/ports/mail/dovecot. *** Error code 1 Stop in /usr/ports/mail/dovecot. I am trying to set up a mailserver with postfix (having abandoned the idea of using qmail due to its complicated nature of setup) with dovecot as the imap server. I need an imap server that can work with postfix, and is easy to configure to run over imaps only. A link to a HOWTO would be very welcome. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Need help setting up qmail / binc imap on FreeBSD
Hi I am trying to implement a qmail based mailserver with binc imap on FreeBSD 5.3-RELEASE using the instructions found on : http://www.bsdguides.org/guides/freebsd/mailserver/qmail+vpopmail+qmailadmin.php I am using packet filter (pf) to setup the firewall. I have added the following rules to permit incoming traffic on ports 993 (imaps) and 465 (smtps) : pass in on $ext_if proto tcp from any to $ext_if \ port 993 flags S/SA keep state \ (max 15, source-track rule, max-src-nodes 100, max-src-states 3) pass in on $ext_if proto tcp from any to $ext_if \ port 465 flags S/SA keep state \ (max 15, source-track rule, max-src-nodes 100, max-src-states 3) However, when I try to connect to the server using openssl : /usr/local/ssl/bin/openssl s_client -connect servername:993 -crlf connect: Connection refused connect:errno=29 I have generated a .pem file for SSL over binc imap and made the suggested additions to /usr/local/etc/bincimap/bincimap.conf. Upon consulting /var/log/qmail/current, I see a slew of messages like : @40004233d471384eecb4 delivery 2: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/ @40004233d4713850679c status: local 0/10 remote 0/20 sockstat reveals that ports 143, 110 and 25 are being listened to (but are closed in the firewall). I wish to make qmail + binc to listen to 993 and 465 instead. Any hints on fixing the setup would be welcome. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Location of openssl certs in FreeBSD 5.3-RELEASE
Hi I am trying to set up bincimap with ssl support as a part of a wider qmail setup for a mailserver. I have openssl installed (man openssl opens up the right manpage). I want to know where are the certs installed. The reason is that the FAQ on bincimap's webpage states : SSL in Binc IMAP is quite simple to set up. First you need a PEM encoded private key and certificate file. In some distributions, you can generate this file by changing to /usr/share/ssl/certs and running make. A script will give you the option to build a PEM file. http://www.bincimap.org/bincimap-faq.html#q3 I tried locate cert. It throws up an openssl tree (looks like an installation tree) in /usr/src (might have been the result of an aborted cvsup operation a few days ago). Anyways, where are the certs installed in FreeBSD ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qmail / FreeBSD / vqadmin problem
On Thursday 10 March 2005 05:57, Peter Risdon wrote: On Thu, 2005-03-10 at 00:12 -0500, Madhusudan Singh wrote: Hi I am new to both FreeBSD and qmail. However, I am definitely not new to unix/linux (2 years of HP-UX and 7 years of Linux experience). I am using a pf firewall on a machine that will host a webserver as well as my mailserver. I am interested in setting up IMAP access to email for my users (do not care for POP3 access). However, I found installation instructions on qmailrocks.org and followed them to the letter (note to the author - /usr/home/vpopmail does not exist - I had to create it by hand - maybe the first shell script on step 2 needs some editing ?), until I installed vqadmin and setup the passwd and placed .htpasswd in /usr/local/www/cgi-bin, restarted apache (built from ports), and tried to login through the cgi interface from another machine. Ports www, 8080 and https are open in /etc/pf.conf. But I keep getting Waiting for FQDN and never can authenticate with the right password. A couple of possibilities. The default installation of vpopmail puts the vpopmail directory in /usr/local and if you want to use /usr/home you have to supply the correct argument to vpopmail when you build it. From /usr/ports/mail/vpopmail/Makefile: [...] # User-configurable variables # # Define these to change from the default behaviour # [...] # PREFIX- installation area for vpopmail (see comment below) [...] # Uncomment this, or set PREFIX to /home if you have an existing # vpopmail install with the vpopmail users' home directory set to # /home/vpopmail - package rules dictate we default to /usr/local/vpopmail # #PREFIX?= /home Note that this will, in my experience, create some odd directory trees in /usr/home (such as /usr/home/lib and /usr/home/libexec) which can safely be deleted subsequently. I don't use vqadmin, but this would need to know where to find the vpopmail binaries, and I can't see any make options that might define this, so that might be a major stumbling block. A possible cause of the behaviour you report would be that vqadmin is trying to run vpopmail binaries with inappropriate paths, or to read directory structures in the wrong place. One workaround, if your real vpopmail directory is in /usr/local and you do need it to be in /usr/home is to symlink /usr/local/vpopmail to /usr/home/vpopmail. Incidentally, the FreeBSD installation of qmail recommends using /var/service and much of the qmail documentation assumes the existence of /service. My own approach to this is to use /var/service but then symlink it to /service so that anything that assumes the existence of this directory will work. However, neither vpopmail not vqadmin would give you an imap server, and you don't say whether you have installed one separately. You do need to and a commonly used option in this case would be courier-imap because it's written by the same folk who brought us vpopmail, and integrates well with this and qmail. It isn't the only choice, of course, and you're generally best advised to use something you're familiar with. The question is : What am I possibly doing wrong ? A port that is not open, or is it some other problem that a FreeBSD / Qmail newbie might have missed ? It's generally best to use default installation locations with ports, especially when you're installing a few that will work with each other. Then, before testing a cgi interface like vqadmin, make sure everything works. Test qmail, (telnet) test imap, test vpopmail with a domain and a user or two on the command line. If these things aren't working properly, then vqadmin won't either. www.lifewithqmail.org is probably the most authoritative site to use as a reference, together with inter7's website and http://cr.yp.to for some perhaps slightly terse but very good initial docs. If you need more help, maybe say whether you have installed an imap server, and whether the underlying technologies - qmail, vpopmail, imap - are working. Peter. Thanks for your informative response. I apologize if I did not stress this point enough in my initial email. I was following instructions on freebsd.qmailrocks.org to the *letter* and building from source as is strongly recommended there. The install is currently in an interrupted state. Setting up IMAP *would have been* one of the next steps. I am right now at the following step : http://freebsd.qmailrocks.org/vqadmin.htm For an overview of the entire installation, please see : http://freebsd.qmailrocks.org/install.htm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qmail / FreeBSD / vqadmin problem
Hi Thanks once again for your message. I followed directions at the following website : http://www.bsdguides.org/guides/freebsd/mailserver/qmail+vpopmail+qmailadmin.php There was one strange comment on this page : Note: the binc-imap configuration is not complete enough to work. It will be complete tomorrow. I wonder what does it really mean. Anyways, the entire procedure of installing from ports went through. Now, I wish to configure things so that only SSL access to smtp and the binc-imap server is permitted. Do I need to do some qmail side configuration for this or is just a matter of opening only selected ports (which ports ? 995 and imaps ?) ? Thanks for the lifewithqmail link. I have printed out the pdf version and will shortly go through it. MS On Thursday 10 March 2005 05:57, Peter Risdon wrote: On Thu, 2005-03-10 at 00:12 -0500, Madhusudan Singh wrote: Hi I am new to both FreeBSD and qmail. However, I am definitely not new to unix/linux (2 years of HP-UX and 7 years of Linux experience). I am using a pf firewall on a machine that will host a webserver as well as my mailserver. I am interested in setting up IMAP access to email for my users (do not care for POP3 access). However, I found installation instructions on qmailrocks.org and followed them to the letter (note to the author - /usr/home/vpopmail does not exist - I had to create it by hand - maybe the first shell script on step 2 needs some editing ?), until I installed vqadmin and setup the passwd and placed .htpasswd in /usr/local/www/cgi-bin, restarted apache (built from ports), and tried to login through the cgi interface from another machine. Ports www, 8080 and https are open in /etc/pf.conf. But I keep getting Waiting for FQDN and never can authenticate with the right password. A couple of possibilities. The default installation of vpopmail puts the vpopmail directory in /usr/local and if you want to use /usr/home you have to supply the correct argument to vpopmail when you build it. From /usr/ports/mail/vpopmail/Makefile: [...] # User-configurable variables # # Define these to change from the default behaviour # [...] # PREFIX- installation area for vpopmail (see comment below) [...] # Uncomment this, or set PREFIX to /home if you have an existing # vpopmail install with the vpopmail users' home directory set to # /home/vpopmail - package rules dictate we default to /usr/local/vpopmail # #PREFIX?= /home Note that this will, in my experience, create some odd directory trees in /usr/home (such as /usr/home/lib and /usr/home/libexec) which can safely be deleted subsequently. I don't use vqadmin, but this would need to know where to find the vpopmail binaries, and I can't see any make options that might define this, so that might be a major stumbling block. A possible cause of the behaviour you report would be that vqadmin is trying to run vpopmail binaries with inappropriate paths, or to read directory structures in the wrong place. One workaround, if your real vpopmail directory is in /usr/local and you do need it to be in /usr/home is to symlink /usr/local/vpopmail to /usr/home/vpopmail. Incidentally, the FreeBSD installation of qmail recommends using /var/service and much of the qmail documentation assumes the existence of /service. My own approach to this is to use /var/service but then symlink it to /service so that anything that assumes the existence of this directory will work. However, neither vpopmail not vqadmin would give you an imap server, and you don't say whether you have installed one separately. You do need to and a commonly used option in this case would be courier-imap because it's written by the same folk who brought us vpopmail, and integrates well with this and qmail. It isn't the only choice, of course, and you're generally best advised to use something you're familiar with. The question is : What am I possibly doing wrong ? A port that is not open, or is it some other problem that a FreeBSD / Qmail newbie might have missed ? It's generally best to use default installation locations with ports, especially when you're installing a few that will work with each other. Then, before testing a cgi interface like vqadmin, make sure everything works. Test qmail, (telnet) test imap, test vpopmail with a domain and a user or two on the command line. If these things aren't working properly, then vqadmin won't either. www.lifewithqmail.org is probably the most authoritative site to use as a reference, together with inter7's website and http://cr.yp.to for some perhaps slightly terse but very good initial docs. If you need more help, maybe say whether you have installed an imap server, and whether the underlying technologies - qmail, vpopmail, imap - are working. Peter. ___ freebsd-questions@freebsd.org mailing list http
Qmail / FreeBSD / vqadmin problem
Hi I am new to both FreeBSD and qmail. However, I am definitely not new to unix/linux (2 years of HP-UX and 7 years of Linux experience). I am using a pf firewall on a machine that will host a webserver as well as my mailserver. I am interested in setting up IMAP access to email for my users (do not care for POP3 access). However, I found installation instructions on qmailrocks.org and followed them to the letter (note to the author - /usr/home/vpopmail does not exist - I had to create it by hand - maybe the first shell script on step 2 needs some editing ?), until I installed vqadmin and setup the passwd and placed .htpasswd in /usr/local/www/cgi-bin, restarted apache (built from ports), and tried to login through the cgi interface from another machine. Ports www, 8080 and https are open in /etc/pf.conf. But I keep getting Waiting for FQDN and never can authenticate with the right password. The question is : What am I possibly doing wrong ? A port that is not open, or is it some other problem that a FreeBSD / Qmail newbie might have missed ? Thanks (especially to the author who has created nearly idiot-proof installation instructions (so far) ). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sources vs. ports
Thanks for your response. On Thursday 03 March 2005 16:21, Jeff With wrote: On Thu, 3 Mar 2005 15:47:02 -0500, Madhusudan Singh [EMAIL PROTECTED]wrote: Hi Since some of the ports I need are broken, I am thinking of installing those parts from source. However, is there a way to let the local ports hierarchy know that a certain package has been installed, albeit by other means ? The handbook answer.. broken ports: fix-it, gripe or find our package from a local mirror... http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-broken.html .. or build your own package w/ pkg_create http://www.freebsd.org/cgi/man.cgi?query=pkg_createsektion=1apropos=0man path=FreeBSD+5.3-RELEASE+and+Ports Thanks for the link. I might want to do this. what ports you are trying to build? zope-cmfphoto for one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about cvsup
Thanks for a very helpful response. I have another query. As a matter of practice, is it a good idea to upgrade ports immediately after a kernel compile ? I do not expect that the ports depend directly on the kernel (for most changes in kernel), though I could well be wrong (for instance cdrecord on linux had major problems after the 2.6.9 kernel came out). On Thursday 03 March 2005 04:24, Ewald Jenisch wrote: On Tue, Mar 01, 2005 at 10:15:05PM -0500, Madhusudan Singh wrote: Hi I am new to FreeBSD and trying to use CVSup after someone suggested it to me on comp.unix.misc.bsd.freebsd. My supfile : *default tag=. *default host=cvsup.FreeBSD.org *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress ports-all release=cvs Hi, I usually do it this way: 1) copy /usr/share/examples/cvsup/ports-supfile to /root 2) Edit /root/ports-supfile so that it points to your preferred CVSup-site; the only thing you need to change is the *default host entry. 3) run cvsup: cvsup -g -L 2 /root/ports-supfile 4) pkgdb -F 5) portsdb -Uu At this point you've synced your ports tree and all databases. Now you can go and install your ports. Dru Lavigne has written an excellent article on this you can find at http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html It basically covers everything I described above including keeping your ports-tree up2date including all up/down dependencies. HTH, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sources vs. ports
Hi Since some of the ports I need are broken, I am thinking of installing those parts from source. However, is there a way to let the local ports hierarchy know that a certain package has been installed, albeit by other means ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
A possibly simple query about pf on FreeBSD 5.3-RELEASE
After nearly a week of fighting the dual problem of OpenBSD 3.6 release freezing on my hardware, and some rather odious personalities on the [EMAIL PROTECTED] mailing list, I decided to install FreeBSD 5.3-RELEASE on the web server I am deploying and stick to it. I went through the webpage on firewalling on FreeBSD (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-pf.html) and decided to pick pf as my firewall solution. The OpenBSD guide on this simply and elegantly written and is very easy to get the hang of. I have created a packet filtering ruleset in /etc/pf.conf, enabled the switches in /etc/rc.conf and am fiddling around with it. I tried to connect on port ssh (22, I think) and did a few tests with different IP addresses and it works as I expect. Since this beast is going to be a webserver, I wrote the following filter for port www : (previously blocking all and scrubbing all of course) pass in on $ext_if proto tcp from any to $ext_if \ port www flags S/SA keep state \ (max 200,source-track rule,max-src-nodes 100,max-src-states 3) Question : Is the above a reasonably good rule for my situation (if you have further questions, fire away) ? Second, whenever I load my rule set (pfctl -f /etc/pf.conf), I get a warning : No ALTQ support in kernel ALTQ related functions disabled Now, I would probably want to use queueing and bandwidth allotment if I am to run a webserver that allows a few IP addresses to connect via ssh. Question : How do I enable ALTQ support in the kernel ? And since I have the choice of either using a loadable module for pf (like I am doing) or compiling in PF support into the kernel, which is better from a security and performance pov ? Another issue, unrelated to pf : I am trying to install plone, zope (and a bunch of zope/plone related packages) and apache on the machine. However, the pkg_add process quit with some errors for some of the packages and refered me to some log (which log ?) during installation. Question : Are versions in the ports tree for these packages kosher, i.e., do they compile, install and work cleanly ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Question about cvsup
Hi I am new to FreeBSD and trying to use CVSup after someone suggested it to me on comp.unix.misc.bsd.freebsd. My supfile : *default tag=. *default host=cvsup.FreeBSD.org *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress ports-all release=cvs I ran cvsup and upgraded the ports that came with FreeBSD 5.3-RELEASE. Now when I try to install some zope products, I get broken dependencies, and in some case (more odd IMO) syntax errors (misplaced return statements) that get ignored and the product installs, seemingly without any problems. Was I wrong to use tag=. above ? If so, should I use RELENG_5_3 to ensure that things don't break like this ? The server in question is supposed to run a plone based website, and stability is important. Thanks. PS : Prior to settling on FreeBSD, I dallied for a while with OpenBSD where matching the ports version with the release version was paramount, a constraint that seems absent here. Or am I making a blunder here ? :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
