Re: cvsup: local
"fire jotawski" <[EMAIL PROTECTED]> writes: > On Thu, Nov 6, 2008 at 9:59 PM, Lowell Gilbert < > [EMAIL PROTECTED]> wrote: > >> "fire jotawski" <[EMAIL PROTECTED]> writes: >> >> > i have my small box, 10.3.1.25 ip, that cvsup-ed files from repository >> into >> > it. it use cvs-supfile in /usr/share/examples/cvsup/ to collect files. >> > now that i want my other machine to cvsup 6.2-release source files from >> the >> > one mentioned above. >> > >> > my trial was >> > >> > cvsupd -b /var/db -c sup >> > >> > for box, 10.3.1.25 ip, and for other machine >> > >> > cvsup -g -L 2 -h 10.3.1.25 sup-file >> > >> > what i got was 'Server message: Unknown collection "src-all" ' message. >> > and later on >> > >> > Running >> > Skipping collection src-all/cvs >> > Skipping collection doc-all/cvs >> > Shutting down connection to server >> > Finished successfully >> > >> > very strange indeed. >> > >> > any helps and hints in setting cvsup server would highly be appreciated. >> >> To run cvsupd, you need the whole cvs tree for the collections you're >> handling, not just the checked-out files. >> >> Assuming these machines are attached by a protected network, a better >> approach (easier, anyway) would probably be to cvsup the changes to >> just one machine, then NFS-mount that machine's ports tree from the >> other machine. >> >> -- >> Lowell Gilbert, embedded/networking software engineer, Boston area >> >> http://be-well.ilk.org/~lowell/<http://be-well.ilk.org/%7Elowell/> >> > > > thanks indeed and apologized me for postponing answer to all of postings. > what about cvs then. i did this > > cvs -d /home/ncvs checkout ports > > and i got some thing quite similar to ports tree indeed. What did you think that command was going to do? Do you have a full cvs ports tree under /home/ncvs? How did you get that? My understanding was that you wanted to put the ports tree on one machine (call it the "master"), then use it to install ports on other machines that are local to the master. The way to do that would be to use cvsup as normal on the master, and build all the ports there. Then you can use NFS to mount /usr/ports on the other machines, and install the ports on them as well. To speed things up, you can set WRKDIRPREFIX to point at local disk space on the client machines. You can even have the master machine build packages, avoiding the need to build the ports from source on the clients. Does that make sense to you? Do you need it described in more detail? Good luck. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup: local
On Thu, Nov 6, 2008 at 9:59 PM, Lowell Gilbert < [EMAIL PROTECTED]> wrote: > "fire jotawski" <[EMAIL PROTECTED]> writes: > > > i have my small box, 10.3.1.25 ip, that cvsup-ed files from repository > into > > it. it use cvs-supfile in /usr/share/examples/cvsup/ to collect files. > > now that i want my other machine to cvsup 6.2-release source files from > the > > one mentioned above. > > > > my trial was > > > > cvsupd -b /var/db -c sup > > > > for box, 10.3.1.25 ip, and for other machine > > > > cvsup -g -L 2 -h 10.3.1.25 sup-file > > > > what i got was 'Server message: Unknown collection "src-all" ' message. > > and later on > > > > Running > > Skipping collection src-all/cvs > > Skipping collection doc-all/cvs > > Shutting down connection to server > > Finished successfully > > > > very strange indeed. > > > > any helps and hints in setting cvsup server would highly be appreciated. > > To run cvsupd, you need the whole cvs tree for the collections you're > handling, not just the checked-out files. > > Assuming these machines are attached by a protected network, a better > approach (easier, anyway) would probably be to cvsup the changes to > just one machine, then NFS-mount that machine's ports tree from the > other machine. > > -- > Lowell Gilbert, embedded/networking software engineer, Boston area > > http://be-well.ilk.org/~lowell/<http://be-well.ilk.org/%7Elowell/> > thanks indeed and apologized me for postponing answer to all of postings. what about cvs then. i did this cvs -d /home/ncvs checkout ports and i got some thing quite similar to ports tree indeed. thanks in advance for any informations rgds, psr -- ?? ? ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup first time - connection refused
On Monday 17 November 2008 20:48:20 Roland Smith wrote: > On Mon, Nov 17, 2008 at 12:53:02PM -0500, Lowell Gilbert wrote: > > Roland Smith <[EMAIL PROTECTED]> writes: > > > On Mon, Nov 17, 2008 at 05:49:04PM +0200, Yony Yossef wrote: > > >> Hi, > > >> > > >> I'm running cvsup -g -L 2 cvs-supfile with all kinds of host names > > >> from this list: > > >> > > >> http://www.freebsd.org/doc/handbook/cvsup.html#HANDBOOK-MIRRORS-CHAPTE > > >>R-SGML-MIRRORS-IL-CVSUP > > >> > > >> I get a Connection refused error. > > >> > > >> Help.. > > > > > > First, you should run csup (which is now part of the base system) > > > instead of the cvsup port. > > > > That won't work at all with the standard cvs-supfile, which uses CVS > > mode. > > And what mode does csup use that is different? check-out only, for the moment. The csup author already has posted work on -hackers for repo-copy mode a few months back. The OP mentions cvs-supfile, which suggests /usr/share/examples/cvsup/cvs-supfile. This supfile repo copies the entire FreeBSD cvs repository. To get anything useful, it needs to be checked out again, using cvs. This is mainly used for mirroring and if you want to get different branches to a machine in one download, maintain local patches etc. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup first time - connection refused
On Mon, Nov 17, 2008 at 12:53:02PM -0500, Lowell Gilbert wrote: > Roland Smith <[EMAIL PROTECTED]> writes: > > > On Mon, Nov 17, 2008 at 05:49:04PM +0200, Yony Yossef wrote: > >> Hi, > >> > >> I'm running cvsup -g -L 2 cvs-supfile with all kinds of host names > >> from this list: > >> > >> http://www.freebsd.org/doc/handbook/cvsup.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-IL-CVSUP > >> > >> I get a Connection refused error. > >> > >> Help.. > > > > First, you should run csup (which is now part of the base system) > > instead of the cvsup port. > > That won't work at all with the standard cvs-supfile, which uses CVS > mode. And what mode does csup use that is different? The supfile that I successfully used with csup says "*default release=cvs tag=RELENG_7". The standard supfile shouldn't work unmodified anyway. The host CHANGE_THIS.FreeBSD.org doesn't resolve. Which is probably for the best :) Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpC4ckya9CJT.pgp Description: PGP signature
Re: cvsup first time - connection refused
Roland Smith <[EMAIL PROTECTED]> writes: > On Mon, Nov 17, 2008 at 05:49:04PM +0200, Yony Yossef wrote: >> Hi, >> >> I'm running cvsup -g -L 2 cvs-supfile with all kinds of host names >> from this list: >> >> http://www.freebsd.org/doc/handbook/cvsup.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-IL-CVSUP >> >> I get a Connection refused error. >> >> Help.. > > First, you should run csup (which is now part of the base system) > instead of the cvsup port. That won't work at all with the standard cvs-supfile, which uses CVS mode. > Then try one of the mirrors in say Greece or Italy or France. > > If that doesn't work, check that your firewall or router aren't blocking > things. That's almost certainly the problem. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup first time - connection refused
On Mon, Nov 17, 2008 at 05:49:04PM +0200, Yony Yossef wrote: > Hi, > > I'm running cvsup -g -L 2 cvs-supfile with all kinds of host names > from this list: > > http://www.freebsd.org/doc/handbook/cvsup.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-IL-CVSUP > > I get a Connection refused error. > > Help.. First, you should run csup (which is now part of the base system) instead of the cvsup port. Then try one of the mirrors in say Greece or Italy or France. If that doesn't work, check that your firewall or router aren't blocking things. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpFGovK5yez3.pgp Description: PGP signature
cvsup first time - connection refused
Hi, I'm running cvsup -g -L 2 cvs-supfile with all kinds of host names from this list: http://www.freebsd.org/doc/handbook/cvsup.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-IL-CVSUP I get a Connection refused error. Help.. Yony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update nagios-3.0.4_1
On Thursday 06 November 2008 16:20:13 Johan Hendriks wrote: > >> cd /usr/ports/ ; make update ; make fetchindex > >> > >> When the upgrade is finished, i run: > >> portversion -l '<' -v | grep nagios > >> > >> but nagios-3.0.4_1 is not present. [cut make.conf] > >cvsup18 has the latest. You're obviously having trouble with the > >index file, because that (or a database derived therefrom) is what > >portversion is looking at to determine what's out of date. > > > >Check the ports-mgmt/nagios/Makefile to be sure it is in fact showing > >the new version. > > I had the same thing, the makefile has the latest, butpkg_version did not > detect the new nagios. What I did was going to /usr/port/net-mgmt/nagios > And did a: > make FORCE_PKG_REGISTER=yes install clean > It installed nagios 3.0.4 Lowell is correct. You need to run `portsdb -uU' after any modification of the ports tree for the portupgrade tools to see new versions. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: CVSup update nagios-3.0.4_1
>> from web ports I have see ( >> http://www.freebsd.org/cgi/ports.cgi?query=nagios-3&stype=all&sektion=all) >> that is relased the version nagios-3.0.4_1 of nagios but I have on my system >> the version nagios-3.0.3. >> >> Now if i try to update nagios from cvsup I run the follow comands: >> >> cd /usr/ports/ ; make update ; make fetchindex >> >> When the upgrade is finished, i run: >> portversion -l '<' -v | grep nagios >> >> but nagios-3.0.4_1 is not present. >> >> This is my /etc/make.conf file: >> >> #make.conf# >> CPUTYPE=i686 >> CFLAGS= -O -pipe >> INSTALL=install -C >> SUP_UPDATE= yes >> SUP= /usr/local/bin/cvsup >> SUPFLAGS= -g -L 2 >> SUPHOST=cvsup18.FreeBSD.org >> SUPFILE= /usr/share/examples/cvsup/stable-supfile >> PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile >> DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile >> WRKDIRPREFIX= /var/tmp >> WITHOUT_GNOME= true >> WANT_OPENSSL_MANPAGES= true >> MAKE_IDEA= YES >> WITH_OPTIMIZED_CFLAGS= yes >> PERL_ARCH= mach >> NOPERL= yo >> NO_PERL=yo >> NO_PERL_WRAPPER=yo >> #make.conf# >> >> >> cvsup18.FreeBSD.org has not yet updated ? Have you an idea ? >cvsup18 has the latest. You're obviously having trouble with the >index file, because that (or a database derived therefrom) is what >portversion is looking at to determine what's out of date. >Check the ports-mgmt/nagios/Makefile to be sure it is in fact showing >the new version. I had the same thing, the makefile has the latest, butpkg_version did not detect the new nagios. What I did was going to /usr/port/net-mgmt/nagios And did a: make FORCE_PKG_REGISTER=yes install clean It installed nagios 3.0.4 Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.9.0/1771 - Release Date: 6-11-2008 7:58 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update nagios-3.0.4_1
"Gian Paolo Buono" <[EMAIL PROTECTED]> writes: > from web ports I have see ( > http://www.freebsd.org/cgi/ports.cgi?query=nagios-3&stype=all&sektion=all) > that is relased the version nagios-3.0.4_1 of nagios but I have on my system > the version nagios-3.0.3. > > Now if i try to update nagios from cvsup I run the follow comands: > > cd /usr/ports/ ; make update ; make fetchindex > > When the upgrade is finished, i run: > portversion -l '<' -v | grep nagios > > but nagios-3.0.4_1 is not present. > > This is my /etc/make.conf file: > > #make.conf# > CPUTYPE=i686 > CFLAGS= -O -pipe > INSTALL= install -C > SUP_UPDATE= yes > SUP=/usr/local/bin/cvsup > SUPFLAGS= -g -L 2 > SUPHOST=cvsup18.FreeBSD.org > SUPFILE=/usr/share/examples/cvsup/stable-supfile > PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile > DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile > WRKDIRPREFIX= /var/tmp > WITHOUT_GNOME= true > WANT_OPENSSL_MANPAGES= true > MAKE_IDEA= YES > WITH_OPTIMIZED_CFLAGS= yes > PERL_ARCH= mach > NOPERL= yo > NO_PERL=yo > NO_PERL_WRAPPER=yo > #make.conf# > > > cvsup18.FreeBSD.org has not yet updated ? Have you an idea ? cvsup18 has the latest. You're obviously having trouble with the index file, because that (or a database derived therefrom) is what portversion is looking at to determine what's out of date. Check the ports-mgmt/nagios/Makefile to be sure it is in fact showing the new version. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup: local
"fire jotawski" <[EMAIL PROTECTED]> writes: > i have my small box, 10.3.1.25 ip, that cvsup-ed files from repository into > it. it use cvs-supfile in /usr/share/examples/cvsup/ to collect files. > now that i want my other machine to cvsup 6.2-release source files from the > one mentioned above. > > my trial was > > cvsupd -b /var/db -c sup > > for box, 10.3.1.25 ip, and for other machine > > cvsup -g -L 2 -h 10.3.1.25 sup-file > > what i got was 'Server message: Unknown collection "src-all" ' message. > and later on > > Running > Skipping collection src-all/cvs > Skipping collection doc-all/cvs > Shutting down connection to server > Finished successfully > > very strange indeed. > > any helps and hints in setting cvsup server would highly be appreciated. To run cvsupd, you need the whole cvs tree for the collections you're handling, not just the checked-out files. Assuming these machines are attached by a protected network, a better approach (easier, anyway) would probably be to cvsup the changes to just one machine, then NFS-mount that machine's ports tree from the other machine. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup: local
hi sirs, i have my small box, 10.3.1.25 ip, that cvsup-ed files from repository into it. it use cvs-supfile in /usr/share/examples/cvsup/ to collect files. now that i want my other machine to cvsup 6.2-release source files from the one mentioned above. my trial was cvsupd -b /var/db -c sup for box, 10.3.1.25 ip, and for other machine cvsup -g -L 2 -h 10.3.1.25 sup-file what i got was 'Server message: Unknown collection "src-all" ' message. and later on Running Skipping collection src-all/cvs Skipping collection doc-all/cvs Shutting down connection to server Finished successfully very strange indeed. any helps and hints in setting cvsup server would highly be appreciated. with best regards, psr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Res: Question: Howto Cvsup mirror?
Yes, I know that this package exists... but I'm trying to setup a cvsup server on a CENTOS 5.2 machine. Does the cvsup client understands only this cvsup-mirror server or is there any other cross-platform(centos) server I can use ? for example a CVS server ? thanks Oliver vBK De: Yuri Pankov <[EMAIL PROTECTED]> Para: Oliver v.B.K. <[EMAIL PROTECTED]> Cc: freebsd-questions@freebsd.org Enviadas: Terça-feira, 4 de Novembro de 2008 14:30:47 Assunto: Re: Question: Howto Cvsup mirror? On Tue, Nov 04, 2008 at 08:01:17AM -0800, Oliver v.B.K. wrote: > Hi, > I've been trying to setup a freebsd7.0 mirror on my network for my needs. The > ftp mirror is working great(used a repository with cobbler) > but with the cvsup mirror I'm quite lost. > > I read in the freebsd handbook what cvsup does and how it works but I didn't > find anywhere > explaining how to create a mirror. > > Since the mirror server on the network runs centos5.2 I tried running csup > instead of compiling cvsup with modula3. > I tried it out with the supfiles I use on the freebsd7.0 machines and it > worked pretty well I guess... > > Now... what kind of server should I use ? is there a cvsupd I can use? or a > normal CVS server should be enough ? > > Thanks > > > Oliver vBK Check /usr/ports/net/cvsup-mirror HTH, Yuri Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com. http://br.new.mail.yahoo.com/addresses ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question: Howto Cvsup mirror?
On Tue, Nov 04, 2008 at 08:01:17AM -0800, Oliver v.B.K. wrote: > Hi, > I've been trying to setup a freebsd7.0 mirror on my network for my needs. The > ftp mirror is working great(used a repository with cobbler) > but with the cvsup mirror I'm quite lost. > > I read in the freebsd handbook what cvsup does and how it works but I didn't > find anywhere > explaining how to create a mirror. > > Since the mirror server on the network runs centos5.2 I tried running csup > instead of compiling cvsup with modula3. > I tried it out with the supfiles I use on the freebsd7.0 machines and it > worked pretty well I guess... > > Now... what kind of server should I use ? is there a cvsupd I can use? or a > normal CVS server should be enough ? > > Thanks > > > Oliver vBK Check /usr/ports/net/cvsup-mirror HTH, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Question: Howto Cvsup mirror?
Hi, I've been trying to setup a freebsd7.0 mirror on my network for my needs. The ftp mirror is working great(used a repository with cobbler) but with the cvsup mirror I'm quite lost. I read in the freebsd handbook what cvsup does and how it works but I didn't find anywhere explaining how to create a mirror. Since the mirror server on the network runs centos5.2 I tried running csup instead of compiling cvsup with modula3. I tried it out with the supfiles I use on the freebsd7.0 machines and it worked pretty well I guess... Now... what kind of server should I use ? is there a cvsupd I can use? or a normal CVS server should be enough ? Thanks Oliver vBK Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com. http://br.new.mail.yahoo.com/addresses ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CVSup update nagios-3.0.4_1
Hi, from web ports I have see ( http://www.freebsd.org/cgi/ports.cgi?query=nagios-3&stype=all&sektion=all) that is relased the version nagios-3.0.4_1 of nagios but I have on my system the version nagios-3.0.3. Now if i try to update nagios from cvsup I run the follow comands: cd /usr/ports/ ; make update ; make fetchindex When the upgrade is finished, i run: portversion -l '<' -v | grep nagios but nagios-3.0.4_1 is not present. This is my /etc/make.conf file: #make.conf# CPUTYPE=i686 CFLAGS= -O -pipe INSTALL=install -C SUP_UPDATE= yes SUP= /usr/local/bin/cvsup SUPFLAGS= -g -L 2 SUPHOST=cvsup18.FreeBSD.org SUPFILE= /usr/share/examples/cvsup/stable-supfile PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile WRKDIRPREFIX= /var/tmp WITHOUT_GNOME= true WANT_OPENSSL_MANPAGES= true MAKE_IDEA= YES WITH_OPTIMIZED_CFLAGS= yes PERL_ARCH= mach NOPERL= yo NO_PERL=yo NO_PERL_WRAPPER=yo #make.conf# cvsup18.FreeBSD.org has not yet updated ? Have you an idea ? Thanks GianPaolo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup to 7.0 from 5.5?
On Oct 22, 2008, at 1:06 AM, Aftab Jahan Subedar wrote: On 10/22/08, Chris Pratt <[EMAIL PROTECTED]> wrote: How risky is it to jump directly to 7.0 on a 5.5 system? Upgrade would be by cvsup. I expect mergemaster issues anyway but this system is relatively vanilla in it's configuration. It's duty is just rsyncing other servers. The kernel is GENERIC minus drivers plus ipfw and there are no kldloads. Can this jump be made? I was hoping to avoid having to make two major release jumps by doing only one. Thanks Not really a bed of roses. Its a thorny road. You will stumble with packages then gcc version then make.conf then cvsup itself. Cannot really remember exact thorny issues but I can tell that it is not straight path. Rather Install 7.0 directly then migrate the data. Thanks for the time to respond. That was enough for me. I'm half-way to a 6.3 installation, then will take it to 7.0. It's surprising that I could find no specifics of the issues, only references that it wasn't a good idea. -- Aftab Jahan Subedar CEO/Software Engineer Subedar Technologies Ltd Subedar Baag Bibir Bagicha #1 North Jatra Bari Dhaka 1204 Bangladesh 88027554546 8801552635208 8801191336608 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup to 7.0 from 5.5?
On 10/22/08, Chris Pratt <[EMAIL PROTECTED]> wrote: > > How risky is it to jump directly to 7.0 on a 5.5 system? > Upgrade would be by cvsup. I expect mergemaster > issues anyway but this system is relatively vanilla in > it's configuration. It's duty is just rsyncing other servers. > The kernel is GENERIC minus drivers plus ipfw and there are > no kldloads. Can this jump be made? I was hoping to avoid > having to make two major release jumps by doing only one. > > Thanks > Not really a bed of roses. Its a thorny road. You will stumble with packages then gcc version then make.conf then cvsup itself. Cannot really remember exact thorny issues but I can tell that it is not straight path. Rather Install 7.0 directly then migrate the data. -- Aftab Jahan Subedar CEO/Software Engineer Subedar Technologies Ltd Subedar Baag Bibir Bagicha #1 North Jatra Bari Dhaka 1204 Bangladesh 88027554546 8801552635208 8801191336608 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup to 7.0 from 5.5?
How risky is it to jump directly to 7.0 on a 5.5 system? Upgrade would be by cvsup. I expect mergemaster issues anyway but this system is relatively vanilla in it's configuration. It's duty is just rsyncing other servers. The kernel is GENERIC minus drivers plus ipfw and there are no kldloads. Can this jump be made? I was hoping to avoid having to make two major release jumps by doing only one. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
On 2008-Oct-11 08:24:51 -0700, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: >csup and cvsup function the same, and they both rely on the same source >versioning system. Note that csup only supports a subset of cvsup functionality. The most obvious missing feature is CVS mode. >If you really want Windows and FreeBSD to "play well" together, your >best option is to run Samba on the FreeBSD box and use UFS2 filesystems, >then make the Windows machine mount shares from the FreeBSD machine. I agree in general but this can also lead to similar gotchas on the Windows side if the Unix side has files differing only in case. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpT0HrqUp6lC.pgp Description: PGP signature
Re: cvsup 7.0 STABLE checkout failure
On Sun, Oct 12, 2008 at 02:41:34AM +0530, Shakul M Hameed wrote: > On Sat, Oct 11, 2008 at 08:24:51AM -0700, Jeremy Chadwick wrote: > > On Sun, Oct 12, 2008 at 02:20:52AM +0530, Shakul M Hameed wrote: > > > On Sat, Oct 11, 2008 at 07:47:11AM -0700, Jeremy Chadwick wrote: > > > > Are you sure? http://www.freebsd.org/doc/en/books/handbook/cvsup.html > > > > -- see > > > > the first "Note:" paragraph. > > > > > > As a newbie to FreeBSD, I would rather like to have a single Code > > > Versioning system. > > > Several methods put newbies in dilemma to decide upon the best suitable > > > procedure. > > > I feel there should be one unique source code management system. > > > > csup and cvsup function the same, and they both rely on the same source > > versioning system. However, cvsup requires Modula3/ezm3 (an external > > dependency), while csup was written entirely in C and comes with the > > FreeBSD base system. > > > > Does this explain the difference? > > > > Thus: pkg_delete cvsup and ezm3 (if installed) from your system, and > > start using csup. :-) > > > > > > I don't see how that would fix or change anything. In fact, I'm fairly > > > > certain it doesn't. > > > > > > > > The error you are receiving from cvsup is telling you "I tried to rename > > > > a file, but couldn't". This often implies a permissions or ownership > > > > thing. Since the directory you're storing stuff in is on an SMB/CIFS > > > > share, I cannot help but wonder if that's the cause of the problem > > > > (somehow). > > > > > > Jeremy, as pointed by "N.J. Mann" recently in a reply in this thread, > > > there is a semicolon in the filename > > > > You mean colon, but I understand what you meant. > > > > > where the rename faliure happened. Because the file > > > "checkouts.cvs:RELENG_7" had ":" in it, which was not created > > > subsequently due to SMB limitation for ":"-based filenames. > > > > > > Because this the cvsup checked-out halted at this point. Morever, as > > > indicated by "Sean <[EMAIL PROTECTED]>" the case-insensitiveness > > > would lead to missing files. > > > > > > I think, I should format my Network drive to NFS to make it really > > > UNIX friendly. > > > > NFS is a transport protocol, not a filesystem type. You don't "format a > > disk to be NFS-friendly". You can use NFS with any type of filesystem; > > UFS/FFS, ZFS, ext2fs, ext3fs, NTFS, MS-DOS, etc... > > > > The problem is that you're using an NTFS across smbmount(8). NTFS does > > not support some characters in filenames, and also is case-insensitive. > > You are being limited by NTFS, and also possibly by smbmount(8). > > > > What you need is to install another disk in your FreeBSD box, or > > allocate space somewhere on the existing filesystem(s) for your > > development stuff. > > > > If you really want Windows and FreeBSD to "play well" together, your > > best option is to run Samba on the FreeBSD box and use UFS2 filesystems, > > then make the Windows machine mount shares from the FreeBSD machine. > > The other way around (FreeBSD-->Windows) creates problems like the ones > > you've experienced. > > I am never going to do a Windows->FreeBSD mount as it is not required for me. > I rather go for extra space on my FreeBSD box. Is there any method to > increase > the size of my FreeBSD partition?? > > Thanks, > Moin Never mind. I have dropped the plan for new disk in my freeBSD box. Instead, My Western Digital Network Harddrive exports both SMB and NFS shares. So now I can mount it as NFS. Internally, this harddrive is ext2 formatted and the NFS and SMB exports are exported. > > > > Hope this helps. Cheers! > > > > -- > > | Jeremy Chadwickjdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > -- > - Moin -- - Moin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
On Sun, Oct 12, 2008 at 02:41:34AM +0530, Shakul M Hameed wrote: > I am never going to do a Windows->FreeBSD mount as it is not required for me. > I rather go for extra space on my FreeBSD box. Is there any method to > increase > the size of my FreeBSD partition?? Do you mean partition as in "I have separate partitions for Windows and FreeBSD", or do you mean partition as in "I want to grow /usr to be larger"? If the lesser: there are commercial utilities out there (such as Partition Magic) which let you "resize" partitions. However, I cannot stress this enough: *back up all of your data* before doing this. I have been bit by bugs in PQMAGIC *twice* in my lifetime (the program panic'ing at 99% and causing me to lose all of my data). If the latter: some people will tell you about growfs(8), but I'm not sure how reliable it is. You'll need to become familiar with bsdlabel(8) and fdisk(8) before you can use that. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
On Sat, Oct 11, 2008 at 08:24:51AM -0700, Jeremy Chadwick wrote: > On Sun, Oct 12, 2008 at 02:20:52AM +0530, Shakul M Hameed wrote: > > On Sat, Oct 11, 2008 at 07:47:11AM -0700, Jeremy Chadwick wrote: > > > Are you sure? http://www.freebsd.org/doc/en/books/handbook/cvsup.html -- > > > see > > > the first "Note:" paragraph. > > > > As a newbie to FreeBSD, I would rather like to have a single Code > > Versioning system. > > Several methods put newbies in dilemma to decide upon the best suitable > > procedure. > > I feel there should be one unique source code management system. > > csup and cvsup function the same, and they both rely on the same source > versioning system. However, cvsup requires Modula3/ezm3 (an external > dependency), while csup was written entirely in C and comes with the > FreeBSD base system. > > Does this explain the difference? > > Thus: pkg_delete cvsup and ezm3 (if installed) from your system, and > start using csup. :-) > > > > I don't see how that would fix or change anything. In fact, I'm fairly > > > certain it doesn't. > > > > > > The error you are receiving from cvsup is telling you "I tried to rename > > > a file, but couldn't". This often implies a permissions or ownership > > > thing. Since the directory you're storing stuff in is on an SMB/CIFS > > > share, I cannot help but wonder if that's the cause of the problem > > > (somehow). > > > > Jeremy, as pointed by "N.J. Mann" recently in a reply in this thread, > > there is a semicolon in the filename > > You mean colon, but I understand what you meant. > > > where the rename faliure happened. Because the file > > "checkouts.cvs:RELENG_7" had ":" in it, which was not created > > subsequently due to SMB limitation for ":"-based filenames. > > > > Because this the cvsup checked-out halted at this point. Morever, as > > indicated by "Sean <[EMAIL PROTECTED]>" the case-insensitiveness > > would lead to missing files. > > > > I think, I should format my Network drive to NFS to make it really > > UNIX friendly. > > NFS is a transport protocol, not a filesystem type. You don't "format a > disk to be NFS-friendly". You can use NFS with any type of filesystem; > UFS/FFS, ZFS, ext2fs, ext3fs, NTFS, MS-DOS, etc... > > The problem is that you're using an NTFS across smbmount(8). NTFS does > not support some characters in filenames, and also is case-insensitive. > You are being limited by NTFS, and also possibly by smbmount(8). > > What you need is to install another disk in your FreeBSD box, or > allocate space somewhere on the existing filesystem(s) for your > development stuff. > > If you really want Windows and FreeBSD to "play well" together, your > best option is to run Samba on the FreeBSD box and use UFS2 filesystems, > then make the Windows machine mount shares from the FreeBSD machine. > The other way around (FreeBSD-->Windows) creates problems like the ones > you've experienced. I am never going to do a Windows->FreeBSD mount as it is not required for me. I rather go for extra space on my FreeBSD box. Is there any method to increase the size of my FreeBSD partition?? Thanks, Moin > > Hope this helps. Cheers! > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | -- - Moin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
On Sun, Oct 12, 2008 at 02:20:52AM +0530, Shakul M Hameed wrote: > On Sat, Oct 11, 2008 at 07:47:11AM -0700, Jeremy Chadwick wrote: > > Are you sure? http://www.freebsd.org/doc/en/books/handbook/cvsup.html -- > > see > > the first "Note:" paragraph. > > As a newbie to FreeBSD, I would rather like to have a single Code Versioning > system. > Several methods put newbies in dilemma to decide upon the best suitable > procedure. > I feel there should be one unique source code management system. csup and cvsup function the same, and they both rely on the same source versioning system. However, cvsup requires Modula3/ezm3 (an external dependency), while csup was written entirely in C and comes with the FreeBSD base system. Does this explain the difference? Thus: pkg_delete cvsup and ezm3 (if installed) from your system, and start using csup. :-) > > I don't see how that would fix or change anything. In fact, I'm fairly > > certain it doesn't. > > > > The error you are receiving from cvsup is telling you "I tried to rename > > a file, but couldn't". This often implies a permissions or ownership > > thing. Since the directory you're storing stuff in is on an SMB/CIFS > > share, I cannot help but wonder if that's the cause of the problem > > (somehow). > > Jeremy, as pointed by "N.J. Mann" recently in a reply in this thread, there > is a semicolon in the filename You mean colon, but I understand what you meant. > where the rename faliure happened. Because the file > "checkouts.cvs:RELENG_7" had ":" in it, which was not created > subsequently due to SMB limitation for ":"-based filenames. > > Because this the cvsup checked-out halted at this point. Morever, as > indicated by "Sean <[EMAIL PROTECTED]>" the case-insensitiveness > would lead to missing files. > > I think, I should format my Network drive to NFS to make it really > UNIX friendly. NFS is a transport protocol, not a filesystem type. You don't "format a disk to be NFS-friendly". You can use NFS with any type of filesystem; UFS/FFS, ZFS, ext2fs, ext3fs, NTFS, MS-DOS, etc... The problem is that you're using an NTFS across smbmount(8). NTFS does not support some characters in filenames, and also is case-insensitive. You are being limited by NTFS, and also possibly by smbmount(8). What you need is to install another disk in your FreeBSD box, or allocate space somewhere on the existing filesystem(s) for your development stuff. If you really want Windows and FreeBSD to "play well" together, your best option is to run Samba on the FreeBSD box and use UFS2 filesystems, then make the Windows machine mount shares from the FreeBSD machine. The other way around (FreeBSD-->Windows) creates problems like the ones you've experienced. Hope this helps. Cheers! -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
On Sat, Oct 11, 2008 at 07:47:11AM -0700, Jeremy Chadwick wrote: > On Sun, Oct 12, 2008 at 01:21:31AM +0530, Shakul M Hameed wrote: > > > 1) Your setup looks very custom. I see SMB/CIFS in use, and you're > > > using a non-standard directory for the cvsup CVS data (the default is > > Yes, I am using mount_smbfs to mount a network harddrive to store all my > > devel code. > > I don't want to overcrowd the the root disk > > I'm left wondering if there are some permissions or ownership issues as > a result of this. > > > I am using X11 cvsup stable-supfile. This is the snapshot of my modified > > cvsup file > > > > # Defaults that apply to all the collections > > # > > # IMPORTANT: Change the next line to use one of the CVSup mirror sites > > # listed at http://www.freebsd.org/doc/handbook/mirrors.html. > > *default host=cvsup3.de.FreeBSD.org > > *default base=/usr/home/moin/smbmount/code/SUPDB/ > > *default prefix=/usr/home/moin/smbmount/code/src/ > > # The following line is for 7-stable. If you want 6-stable, 5-stable, > > # 4-stable, 3-stable, or 2.2-stable, change to "RELENG_6", "RELENG_5", > > # "RELENG_4", "RELENG_3", or "RELENG_2_2" respectively. > > *default release=cvs tag=RELENG_7 > > *default delete use-rel-suffix > > > > # If you seem to be limited by CPU rather than network or disk bandwidth, > > try > > # commenting out the following line. (Normally, today's CPUs are fast > > enough > > # that you want to run compression.) > > *default compress > > > > ## Main Source Tree. > > # > > # The easiest way to get the main source tree is to use the "src-all" > > # mega-collection. It includes all of the individual "src-*" collections. > > # Please note: If you want to track -STABLE, leave this uncommented. > > src-all > > ---- > > I have no idea what an "X11 cvsup stable-supfile" is, so I assume you > mean you've used /usr/share/examples/cvsup/stable-supfile as a template > supfile, but have your own somewhere else. > > The reason I was confused: you first stated you're using the ones in > /usr/share/examples/cvsup, and I assumed that mean you were using it > directly. You shouldn't modify any files in /usr/share/examples, as > they will be replaced/overwritten during installworld. > > Your pasted supfile looks fine, however. > > > > 2) Check permissions and ownership of all directories leading up to > > > /usr/home/moin/smbmount/code/SUPDB/sup/src-all. Yes, check every single > > > one. > > Please do this. > > > > 3) Ensure your umask is 022 before starting cvsup. This could be a side > > > result of item #2. > >umask is 0022 > > > > > > 4) I'm not sure why you're using cvsup on a 7.x box when csup comes with > > > the base system. > > > > I don't know why ? :-) . But I did as it was listed in the FreeBSD > > handbook. > > Are you sure? http://www.freebsd.org/doc/en/books/handbook/cvsup.html -- see > the first "Note:" paragraph. As a newbie to FreeBSD, I would rather like to have a single Code Versioning system. Several methods put newbies in dilemma to decide upon the best suitable procedure. I feel there should be one unique source code management system. > > > > I would also try doing this as a last resort: > > > > > > rm -fr /usr/home/moin/smbmount/code/SUPDB/sup/src-all > > > rm -fr /usr/src/* > > > csup -h -L 2 /usr/share/examples/cvsup/stable-supfile > > > > > As a lost resort, I did a "cvsup -g -L2 stable-supfile", with just > > changing the HOST part without changing other entries in > > stable-supfile, and I was successful to download the code. > > I don't see how that would fix or change anything. In fact, I'm fairly > certain it doesn't. > > The error you are receiving from cvsup is telling you "I tried to rename > a file, but couldn't". This often implies a permissions or ownership > thing. Since the directory you're storing stuff in is on an SMB/CIFS > share, I cannot help but wonder if that's the cause of the problem > (somehow). Jeremy, as pointed by "N.J. Mann" recently in a reply in this thread, there is a semicolon in the filename where the rename faliure happened. Because the file "checkouts.cvs:RELENG_7" had ":" in it, which was
Re: cvsup 7.0 STABLE checkout failure
On Sun, Oct 12, 2008 at 01:21:31AM +0530, Shakul M Hameed wrote: > > 1) Your setup looks very custom. I see SMB/CIFS in use, and you're > > using a non-standard directory for the cvsup CVS data (the default is > Yes, I am using mount_smbfs to mount a network harddrive to store all my > devel code. > I don't want to overcrowd the the root disk I'm left wondering if there are some permissions or ownership issues as a result of this. > I am using X11 cvsup stable-supfile. This is the snapshot of my modified > cvsup file > > # Defaults that apply to all the collections > # > # IMPORTANT: Change the next line to use one of the CVSup mirror sites > # listed at http://www.freebsd.org/doc/handbook/mirrors.html. > *default host=cvsup3.de.FreeBSD.org > *default base=/usr/home/moin/smbmount/code/SUPDB/ > *default prefix=/usr/home/moin/smbmount/code/src/ > # The following line is for 7-stable. If you want 6-stable, 5-stable, > # 4-stable, 3-stable, or 2.2-stable, change to "RELENG_6", "RELENG_5", > # "RELENG_4", "RELENG_3", or "RELENG_2_2" respectively. > *default release=cvs tag=RELENG_7 > *default delete use-rel-suffix > > # If you seem to be limited by CPU rather than network or disk bandwidth, try > # commenting out the following line. (Normally, today's CPUs are fast enough > # that you want to run compression.) > *default compress > > ## Main Source Tree. > # > # The easiest way to get the main source tree is to use the "src-all" > # mega-collection. It includes all of the individual "src-*" collections. > # Please note: If you want to track -STABLE, leave this uncommented. > src-all > I have no idea what an "X11 cvsup stable-supfile" is, so I assume you mean you've used /usr/share/examples/cvsup/stable-supfile as a template supfile, but have your own somewhere else. The reason I was confused: you first stated you're using the ones in /usr/share/examples/cvsup, and I assumed that mean you were using it directly. You shouldn't modify any files in /usr/share/examples, as they will be replaced/overwritten during installworld. Your pasted supfile looks fine, however. > > 2) Check permissions and ownership of all directories leading up to > > /usr/home/moin/smbmount/code/SUPDB/sup/src-all. Yes, check every single > > one. Please do this. > > 3) Ensure your umask is 022 before starting cvsup. This could be a side > > result of item #2. >umask is 0022 > > > > 4) I'm not sure why you're using cvsup on a 7.x box when csup comes with > > the base system. > > I don't know why ? :-) . But I did as it was listed in the FreeBSD handbook. Are you sure? http://www.freebsd.org/doc/en/books/handbook/cvsup.html -- see the first "Note:" paragraph. > > I would also try doing this as a last resort: > > > > rm -fr /usr/home/moin/smbmount/code/SUPDB/sup/src-all > > rm -fr /usr/src/* > > csup -h -L 2 /usr/share/examples/cvsup/stable-supfile > > As a lost resort, I did a "cvsup -g -L2 stable-supfile", with just > changing the HOST part without changing other entries in > stable-supfile, and I was successful to download the code. I don't see how that would fix or change anything. In fact, I'm fairly certain it doesn't. The error you are receiving from cvsup is telling you "I tried to rename a file, but couldn't". This often implies a permissions or ownership thing. Since the directory you're storing stuff in is on an SMB/CIFS share, I cannot help but wonder if that's the cause of the problem (somehow). > Currently, I am trying out to figure why the customised way is failing. I see nothing wrong with your supfile. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
On Sat, Oct 11, 2008 at 05:38:26AM -0700, Jeremy Chadwick wrote: > On Sat, Oct 11, 2008 at 11:33:08PM +0530, Shakul M Hameed wrote: > > Forwarding original msg to freebsd-questions mailing list. > > > > On Sat, Oct 11, 2008 at 11:06:13PM +0530, Shakul M Hameed wrote: > > > I am trying to download 7.0 stable release through cvsup, but it fails. I > > > tried changing the server, but still get those errors. > > > > > > - ERROR --- > > > > > > Checkout src/share/doc/psd/15.yacc/ss.. > > > Updater failed: Error in > > > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/checkouts.cvs:RELENG_7": > > > Cannot rename > > > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/#cvs.cvsup-7219.0" to > > > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/checkouts.cvs:RELENG_7": > > > No such filer or directory > > > > > > SUPFILE - > > > default stable-cvsup from /usr/share/examples/cvsup > > > -- > > > > > > pls, indicate what i am doing wrong here? > > 1) Your setup looks very custom. I see SMB/CIFS in use, and you're > using a non-standard directory for the cvsup CVS data (the default is Yes, I am using mount_smbfs to mount a network harddrive to store all my devel code. I don't want to overcrowd the the root disk > /usr/sup). You're either starting cvsup with some custom arguments or > your supfile *is* in fact modified. I am using X11 cvsup stable-supfile. This is the snapshot of my modified cvsup file # Defaults that apply to all the collections # # IMPORTANT: Change the next line to use one of the CVSup mirror sites # listed at http://www.freebsd.org/doc/handbook/mirrors.html. *default host=cvsup3.de.FreeBSD.org *default base=/usr/home/moin/smbmount/code/SUPDB/ *default prefix=/usr/home/moin/smbmount/code/src/ # The following line is for 7-stable. If you want 6-stable, 5-stable, # 4-stable, 3-stable, or 2.2-stable, change to "RELENG_6", "RELENG_5", # "RELENG_4", "RELENG_3", or "RELENG_2_2" respectively. *default release=cvs tag=RELENG_7 *default delete use-rel-suffix # If you seem to be limited by CPU rather than network or disk bandwidth, try # commenting out the following line. (Normally, today's CPUs are fast enough # that you want to run compression.) *default compress ## Main Source Tree. # # The easiest way to get the main source tree is to use the "src-all" # mega-collection. It includes all of the individual "src-*" collections. # Please note: If you want to track -STABLE, leave this uncommented. src-all ---- > > 2) Check permissions and ownership of all directories leading up to > /usr/home/moin/smbmount/code/SUPDB/sup/src-all. Yes, check every single > one. > > 3) Ensure your umask is 022 before starting cvsup. This could be a side > result of item #2. umask is 0022 > > 4) I'm not sure why you're using cvsup on a 7.x box when csup comes with > the base system. I don't know why ? :-) . But I did as it was listed in the FreeBSD handbook. > > I would also try doing this as a last resort: > > rm -fr /usr/home/moin/smbmount/code/SUPDB/sup/src-all > rm -fr /usr/src/* > csup -h -L 2 /usr/share/examples/cvsup/stable-supfile As a lost resort, I did a "cvsup -g -L2 stable-supfile", with just changing the HOST part without changing other entries in stable-supfile, and I was successful to download the code. Currently, I am trying out to figure why the customised way is failing. - Moin > > However, with regards to use of /usr/share/examples/cvsup/stable-supfile > see my above comment; yours may be modified. > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
On Sat, Oct 11, 2008 at 11:33:08PM +0530, Shakul M Hameed wrote: > Forwarding original msg to freebsd-questions mailing list. > > On Sat, Oct 11, 2008 at 11:06:13PM +0530, Shakul M Hameed wrote: > > I am trying to download 7.0 stable release through cvsup, but it fails. I > > tried changing the server, but still get those errors. > > > > - ERROR --- > > > > Checkout src/share/doc/psd/15.yacc/ss.. > > Updater failed: Error in > > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/checkouts.cvs:RELENG_7": > > Cannot rename > > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/#cvs.cvsup-7219.0" to > > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/checkouts.cvs:RELENG_7": No > > such filer or directory > > > > SUPFILE - > > default stable-cvsup from /usr/share/examples/cvsup > > -- > > > > pls, indicate what i am doing wrong here? 1) Your setup looks very custom. I see SMB/CIFS in use, and you're using a non-standard directory for the cvsup CVS data (the default is /usr/sup). You're either starting cvsup with some custom arguments or your supfile *is* in fact modified. 2) Check permissions and ownership of all directories leading up to /usr/home/moin/smbmount/code/SUPDB/sup/src-all. Yes, check every single one. 3) Ensure your umask is 022 before starting cvsup. This could be a side result of item #2. 4) I'm not sure why you're using cvsup on a 7.x box when csup comes with the base system. I would also try doing this as a last resort: rm -fr /usr/home/moin/smbmount/code/SUPDB/sup/src-all rm -fr /usr/src/* csup -h -L 2 /usr/share/examples/cvsup/stable-supfile However, with regards to use of /usr/share/examples/cvsup/stable-supfile see my above comment; yours may be modified. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 7.0 STABLE checkout failure
Forwarding original msg to freebsd-questions mailing list. On Sat, Oct 11, 2008 at 11:06:13PM +0530, Shakul M Hameed wrote: > I am trying to download 7.0 stable release through cvsup, but it fails. I > tried changing the server, but still get those errors. > > - ERROR --- > > Checkout src/share/doc/psd/15.yacc/ss.. > Updater failed: Error in > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/checkouts.cvs:RELENG_7": > Cannot rename > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/#cvs.cvsup-7219.0" to > "/usr/home/moin/smbmount/code/SUPDB/sup/src-all/checkouts.cvs:RELENG_7": No > such filer or directory > > SUPFILE - > default stable-cvsup from /usr/share/examples/cvsup > -- > > pls, indicate what i am doing wrong here? > > - Moin -- - Moin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: core Dumb during CVSUP
use csup, but at this stage, i'll wait untill portupgrade has finished to see if anything changes in that reguards. Well, you could ktrace(8) the binary and/or rebuild it with debugging symbols and bt the coredump ~BAS ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup mirrors
Or...contact the maintainer: http://www.dslreports.com/profile/191119 $ host cvsup1.ca.FreeBSD.org cvsup1.ca.FreeBSD.org is an alias for less.cogeco.net. less.cogeco.net has address 24.226.6.67 http://less.cogeco.net/ Many broken URLS. ~BAS On Fri, 12 Sep 2008, Michael P. Soulier wrote: I found this http://www.freebsd.org/doc/en/books/handbook/cvsup.html#CVSUP-MIRRORS and it lists one for me in Canada. cvsup1.ca.freebsd.org Unfortunately, it doesn't have RELENG_6 on it. cvsup says it's not there. Does the mirrors list need an update? Thanks, Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail?" ~Maynard James Keenan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup mirrors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On September 12, 2008 12:09:12 pm Michael P. Soulier wrote: > I found this > http://www.freebsd.org/doc/en/books/handbook/cvsup.html#CVSUP-MIRRORS > > and it lists one for me in Canada. > > cvsup1.ca.freebsd.org > > Unfortunately, it doesn't have RELENG_6 on it. cvsup says it's not there. > > Does the mirrors list need an update? > > Thanks, > Mike It could be the mirrors need updating, if you are looking for a Canadian cvsup server, try freebsd.articnetwork.ca. Thomas - -- Thomas Abthorpe | FreeBSD Committer [EMAIL PROTECTED] | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjLupcACgkQ5Gm/jNBp8qAidwCeLi3sRIr7/REoB4AoSxz6TOWr p14An0LmdkQ+eFyy7FXJeOihOPJ/o7Ce =oXVC -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup mirrors
I found this http://www.freebsd.org/doc/en/books/handbook/cvsup.html#CVSUP-MIRRORS and it lists one for me in Canada. cvsup1.ca.freebsd.org Unfortunately, it doesn't have RELENG_6 on it. cvsup says it's not there. Does the mirrors list need an update? Thanks, Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very Beginning CVSup Questions
Thanks to everyone for the help! - Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very Beginning CVSup Questions
On Tue, 22 Jul 2008 05:08:03 +0300 Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On Mon, 21 Jul 2008 20:08:37 -0400, "J.C." <[EMAIL PROTECTED]> > wrote: > > The "Using the Ports Collection" page in the handbook says to make > > sure /usr/ports is empty before running csup because otherwise "csup > > will not prune removed patch files." Isn't this what the "delete" in > > the supfile (as in the line *default release=cvs delete > > use-rel-suffix compress) is for? Do I have to clean /usr/ports > > every time I run csup or just the first time? > > Probably not. It's been a while that I haven't used CVSup for ports/, > so someone with more recent experience should answer this. The issue isn't specific to ports. The same thing can happen with the base system too when you adopt an existing tree that's older than the CVS version. Deletions made in CVS between the two points on the branch don't get made locally, because they rely on the relevant csup list file. To be safe you either start from an empty tree, or do an intermediate sync to the point on the branch that matches the local copy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very Beginning CVSup Questions
On Mon, 21 Jul 2008 20:08:37 -0400, "J.C." <[EMAIL PROTECTED]> wrote: > I'm a beginner with FreeBSD and somewhat intermediate with Unix-like > operating systems in general, so please bear the nature of my > questions. I have some questions about CVSup that seem unclear from > the handbook. Right now I'm sticking with RELENG_7_0; I intend to > track -STABLE once I get the hang of CVSup, make buildworld, etc. > > I understand that the supfile contains the list of *default settings > (*default tag=RELENG_7_0 etc.) followed by the list of "collections". > The "Using CVSup" page suggests simply using the src-all collection. I > understand that when tracking -STABLE I want to update the ports > collection before running make buildworld; Not necessarily. If you are tracking a -STABLE branch, the rule is that "ports compiled on earlier builds should work in later builds". There are very few exceptions that may require a rebuild of ports, but the FreeBSD team tries to avoid those if at all possible. > is the ports collection included in the "base source tree" (i.e. does > src-all imply ports-all) or should ports-all be included as a separate > line beneath src-all? It's probably a good idea to use a separate `supfile' for src/ and ports/. There are a few tiny but important differences between the "base system" (the src-all collection) and the ports. One of the differences is that the base system is "branched". This means that the branch name "RELENG_7" carries an important and well defined meaning for "src-all". There are no branches in ports, on the other hand. A consequence of this is that using the same supfile with the option "*default tag=RELENG_7_0" may do moderately surprising to your ports tree, like deleting it altogether. When CVSup fails to find a particular collection in the tag/branch you asked, and the supfile has enabled the "*default delete use-rel-suffix" option too, it _deletes_ the files that don't exist on the requested tag/branch. To avoid surprises like these, you can use two supfiles: one for the "src-all" collection, and one for the "ports-all" collection. > The "Using the Ports Collection" page in the handbook says to make > sure /usr/ports is empty before running csup because otherwise "csup > will not prune removed patch files." Isn't this what the "delete" in > the supfile (as in the line *default release=cvs delete use-rel-suffix > compress) is for? Do I have to clean /usr/ports every time I run csup > or just the first time? Probably not. It's been a while that I haven't used CVSup for ports/, so someone with more recent experience should answer this. > If I don't care about encrypted transmission or HTTP vs. CVS > protocols, are there any compelling reasons to use portsnap instead of > CVSup/csup? Speed. Portsnap doesn't have to worry about tags, branches, and CVS file revisions in the common case, so it can usually finish before CVSup has even finished uploading the current file versions. I just updated my /usr/ports tree with portsnap, and it took all of 50 seconds to fetch and apply 169 patches: | [EMAIL PROTECTED]:/root# \time portsnap fetch update | Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. | Fetching snapshot tag from portsnap1.FreeBSD.org... done. | Fetching snapshot metadata... done. | Updating from Sat Jul 19 18:10:14 EEST 2008 to Tue Jul 22 03:17:39 EEST 2008. | Fetching 3 metadata patches.. done. | Applying metadata patches... done. | Fetching 0 metadata files... done. | Fetching 169 patches.102030405060708090100110120130140150160 done. | Applying patches... done. | Fetching 22 new ports or files... done. | Removing old files and directories... done. | Extracting new files: | [lots of file paths snipped] | /usr/ports/x11/xloadimage/ | Building new INDEX files... done. |68.64 real12.99 user24.40 sys | [EMAIL PROTECTED]:/root# That's fast enough for me :-) Having said that, there are compelling reasons to use CVSup for ports if you are a developer who wants to make local patches for some of the ports, or if you are maintaining a large number of ports. In this case, having a local CVS mirror of the ports, and checking out from CVS may be useful, because you can see the history of the ports, browse through patches committed, look at port changelogs, or even maintain a locally patched /usr/ports tree in semi-offline mode. That mode of updating is useful too. It all depends on what you are planning to do with your /usr/ports tree. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very Beginning CVSup Questions
On Mon, 21 Jul 2008 20:08:37 -0400 J.C. <[EMAIL PROTECTED]> wrote: > I'm a beginner with FreeBSD and somewhat intermediate with Unix-like > operating systems in general, so please bear the nature of my > questions. I have some questions about CVSup that seem unclear from > the handbook. Right now I'm sticking with RELENG_7_0; I intend to > track -STABLE once I get the hang of CVSup, make buildworld, etc. You need to understand CVSup, make buildworld, to track RELENG_7_0 (and successors) too, are you sure you want to track a development branch? > I understand that the supfile contains the list of *default settings > (*default tag=RELENG_7_0 etc.) followed by the list of "collections". > The "Using CVSup" page suggests simply using the src-all collection. I > understand that when tracking -STABLE I want to update the ports > collection before running make buildworld; is the ports collection > included in the "base source tree" (i.e. does src-all imply ports-all) No > or should ports-all be included as a separate line beneath src-all? You can do that, but I think most people use separate files, so they can be updated independently. There are multiple sample files for this reason. > The "Using the Ports Collection" page in the handbook says to make > sure /usr/ports is empty before running csup because otherwise "csup > will not prune removed patch files." Isn't this what the "delete" in > the supfile (as in the line *default release=cvs delete use-rel-suffix > compress) is for? It's a bit subtle, csup has to establish a baseline in its metadata for it to be fully confident about which files it can delete, this can be done starting with an empty or fully syncronized tree. There's also a separate issue that it never deletes files which have never been under CVS. > Do I have to clean /usr/ports every time I run csup > or just the first time? Just the first. > If I don't care about encrypted transmission or HTTP vs. CVS > protocols, are there any compelling reasons to use portsnap instead of > CVSup/csup? portsnap is much faster. And since the fetch part doesn't affect the ports tree it can be done safely from a crontab, which speeds things up even more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Very Beginning CVSup Questions
I'm a beginner with FreeBSD and somewhat intermediate with Unix-like operating systems in general, so please bear the nature of my questions. I have some questions about CVSup that seem unclear from the handbook. Right now I'm sticking with RELENG_7_0; I intend to track -STABLE once I get the hang of CVSup, make buildworld, etc. I understand that the supfile contains the list of *default settings (*default tag=RELENG_7_0 etc.) followed by the list of "collections". The "Using CVSup" page suggests simply using the src-all collection. I understand that when tracking -STABLE I want to update the ports collection before running make buildworld; is the ports collection included in the "base source tree" (i.e. does src-all imply ports-all) or should ports-all be included as a separate line beneath src-all? The "Using the Ports Collection" page in the handbook says to make sure /usr/ports is empty before running csup because otherwise "csup will not prune removed patch files." Isn't this what the "delete" in the supfile (as in the line *default release=cvs delete use-rel-suffix compress) is for? Do I have to clean /usr/ports every time I run csup or just the first time? If I don't care about encrypted transmission or HTTP vs. CVS protocols, are there any compelling reasons to use portsnap instead of CVSup/csup? Thank you very much for your help. - Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: core Dumb during CVSUP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Warren Liddell wrote: | Subject: core Dumb during CVSUP http://www.prodigio.it/5/linguasegni.gif Sorry, couldn't resist :) - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhg44EACgkQwMJqmJVx9464pgCfbaHdN1EHy6Xmk4V4wpogZzpP WXwAn28hh7qNohqMHESlODtk8rzv96d9 =cpvU -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: core Dumb during CVSUP
On Tuesday 24 June 2008 21:51:09 Lowell Gilbert wrote: > Warren Liddell <[EMAIL PROTECTED]> writes: > > I have up untill recently been able to do cvsup np's at all, now all of a > > sudden it core dumps, any thoughts welcome.. > > > > Connecting to cvsup.au.freebsd.org > > Connected to cvsup.au.freebsd.org > > Server software version: SNAP_16_1h > > Negotiating file attribute support > > Exchanging collection information > > Establishing multiplexed-mode data connection > > Running > > Bus error (core dumped) > > What did you change since it worked? > Are you seeing core dumps on anything else? CORE dumps using cvsup still occur, so im presuming im always going ot have to use csup, but at this stage, i'll wait untill portupgrade has finished to see if anything changes in that reguards. But i was having a lot o fissues upgrading ports due to 1 pkg, but a completre rem of ports dir an a sup of the ports tree solved that issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: core Dumb during CVSUP
Warren Liddell <[EMAIL PROTECTED]> writes: > I have up untill recently been able to do cvsup np's at all, now all of a > sudden it core dumps, any thoughts welcome.. > > Connecting to cvsup.au.freebsd.org > Connected to cvsup.au.freebsd.org > Server software version: SNAP_16_1h > Negotiating file attribute support > Exchanging collection information > Establishing multiplexed-mode data connection > Running > Bus error (core dumped) What did you change since it worked? Are you seeing core dumps on anything else? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
core Dumb during CVSUP
I have up untill recently been able to do cvsup np's at all, now all of a sudden it core dumps, any thoughts welcome.. Connecting to cvsup.au.freebsd.org Connected to cvsup.au.freebsd.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Bus error (core dumped) -- No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.4.1/1513 - Release Date: 22/06/2008 7:52 AM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld fails on FreeBSD 7 - fresh cvsup - libreadline.so complaints
Rudy wrote: Workaround: If I go directly into /usr/src/gnu/usr.bin and type 'make' things are built... (still building, so I don't know if this will hose the system :) This came up about 5 more times (usr.sbin , bin, ...) so I finally gave up. Rudy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld fails on FreeBSD 7 - fresh cvsup - libreadline.so complaints
Problem: Fresh cvsup of FreeBSD-7 and make buildworld failed... Workaround: If I go directly into /usr/src/gnu/usr.bin and type 'make' things are built... (still building, so I don't know if this will hose the system :) Error: (note "gnu/usr.bin/bc" also failed with the similar errors [libreadline.so complaints]) ===> gnu/usr.bin/gdb/gdb (all) cc -O2 -fno-strict-aliasing -pipe -march=pentium4 -DHAVE_CONFIG_H -DRL_NO_COMPAT -DMI_OUT=1 -DTUI=1 -I. -I/usr/src/gnu/usr.bin/gdb/gdb/../arch/i386 -I/usr/src/gnu/usr.bin/gdb/gdb/../../binutils/libbfd -I/usr/src/gnu/usr.bin/gdb/gdb/../../binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/config -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/include -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/binutils/bfd -c /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/gdb.c cc -O2 -fno-strict-aliasing -pipe -march=pentium4 -DHAVE_CONFIG_H -DRL_NO_COMPAT -DMI_OUT=1 -DTUI=1 -I. -I/usr/src/gnu/usr.bin/gdb/gdb/../arch/i386 -I/usr/src/gnu/usr.bin/gdb/gdb/../../binutils/libbfd -I/usr/src/gnu/usr.bin/gdb/gdb/../../binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/config -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/include -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/binutils/bfd -Wl,-E -o gdb gdb.o /usr/obj/usr/src/gnu/usr.bin/gdb/gdb/../../gdb/libgdb/libgdb.a /usr/obj/usr/src/gnu/usr.bin/gdb/gdb/../../binutils/libbfd/libbfd.a /usr/obj/usr/src/gnu/usr.bin/gdb/gdb/../../binutils/libopcodes/libopcodes.a /usr/obj/usr/src/gnu/usr.bin/gdb/gdb/../../binutils/libiberty/libiberty.a -lm -lreadline -ltermcap -lgnuregex /usr/obj/usr/src/gnu/usr.bin/gdb/gdb/../../gdb/libgdb/libgdb.a(tui.o)(.text+0x6a9): In function `tui_rl_switch_mode': : undefined reference to `rl_newline' /usr/obj/usr/src/gnu/usr.bin/gdb/gdb/../../gdb/libgdb/libgdb.a(tui.o)(.text+0x8a2): In function `tui_rl_command_mode': : undefined reference to `rl_insert' /usr/obj/usr/src/gnu/usr.bin/gdb/gdb/../../gdb/libgdb/libgdb.a(top.o)(.text+0x174): In function `gdb_rl_operate_and_get_next': : undefined reference to `rl_newline' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_rubout_or_delete' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_clear_screen' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_delete' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_insert_comment' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_rubout' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_delete_horizontal_space' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_insert_text' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_refresh_line' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_quoted_insert' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_transpose_chars' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_backward_word' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_char_search' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_arrow_keys' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_backward_byte' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `_rl_char_search_internal' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_end_of_line' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_forward_byte' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_forward_word' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `_rl_set_mark_at_pos' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_set_mark' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_replace_line' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `_rl_rubout_char' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `_rl_overwrite_char' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_do_lowercase_version' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_upcase_word' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_tab_insert' /usr/obj/usr/src/tmp/usr/lib/libreadline.so: undefined reference to `rl_backward_char' /usr/obj
Re: cvsup RELENG_6_3 to RELENG_7 impaired gnome
Try downloading the binary packages for 7.0 that you need and install them. That would be fastest. FreeBSD doesn't claim to maintain binary (library?) compatibility across major releases. I personally have never had a problem, but I consider that dumb luck. Regards, Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup RELENG_6_3 to RELENG_7 impaired gnome
I am feeling nuked from the freeBSD community right now and I was trying to appropriately post to the gnome list but oh well. I don't have time for the continued bugs in my system, I have _GOT_ to get this running pronto. The subscription to the gnome list seems to be hanging or lagging and my paranoia meter says that some people are doing this because crimeny the gnome list should have sent me at least 50 emails by now. Anyway. To my stupid question that is probably too stupid for hackers, but I am not subscribed to questions either I just can't tolerate that in my time frames It is hard enough letting the other lists go by. Oh. I should have tried to subscribe to that but I am under the.. GGGH fine. If I don't get that subscription notice by the time I finish this then I'm sending it. I suspect the composition should take a reasonable amount of time for that to happen. I did cvsup with the standard-supfile but I guess I used the one from freeBSD 6.2 and I thought it would be kosher to change the bit that said "RELENG_6_2" to "RELENG_7" so that's what I did. I used the ftp4.freebsd.org mirror and I did a cvsup. Then I did cvsup with the ports-supfile but that one had cvsup4.freebsd.org in it, so after that I was OMG and I changed the ftp4.freebsd.org in the standard-supfile and redid that cvsup. Anyway. THen I started following instructions in /usr/src/Makefile. My current professor runs FreeBSD and he suggested that method. It looks pretty similar to stuff I have seen elsewhwere, plus it was part of what cvsup slurped up that was supposed to be specific to my version, right? Anyway, here are the steps: IMPROVISATION: I did mergemaster -p here oops. (see below) make buildworld / make buildkernel make kernel <-| substituted for-< make installkernel reboot -s .. okay. This is where I guess I am basic? I don't think I used the loader prompt, I didn't use reboot -s hmm.. that probably would have been a good thing to type after # I guess I am really stupid. I did shutdown -r now and when the devil came up I pressed "4" Then I typed "mount -a" and then.. mergemaster -p and that is a ball of wax depicted here: http://www.monkeyview.net/id/965/fsck/inst_world/index.vhtml The same thing happened the first time I did mergemaster -p tells my spidey sense "oh oh." Anyway. Then I did make installworld and had a bad thing something about "make doesn't get it" but I fixed that by googling it. Oh here it is: http://www.monkeyview.net/id/965/fsck/inst_world/p5240176.vhtml anyway, don't worry too much about that I fixed it by doing: /usr/src/usr.sbin/mergemaster/mergemaster.sh -p and had the same trials and tribulation of hitting 1000 space bars at the right time with intercelated 1000 return keys (actually maybe more like 300 space bars and 200 return keys) and then, saints be praised, make installworld did some presumably nice things so then I did: make delete-old like /usr/src/Makefile said and OMFG I had to hit "y" 200 times now. mergemaster -U 300 more space bars 200 more return keys make delete-old-libs and now I have provided some pictures of what happens when I try to start up. I get to the devil and then it looks like http://www.monkeyview.net/id/965/fsck/fb7/p5250001.vhtml http://www.monkeyview.net/id/965/fsck/fb7/p5250002.vhtml http://www.monkeyview.net/id/965/fsck/fb7/p5250004.vhtml http://www.monkeyview.net/id/965/fsck/fb7/p5250005.vhtml I broke my gnome and my nessus which is the thing I absolute need pronto! I am not trying to be demanding I am just informing everybody that I am under pressure here and I have no idea what to google at this point. *--* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *--* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup executed from crontab
I am using cvsup for backup, so I control both the client and the server. Works fine everytime stand-alone, but when I execute via crontab it appears to stall - then restart. Eventually there is so many copies of cvsup running at the same time it starts to bog down the client. I noticed in the man page there is the "-d 0" or "-1" option. Not sure if that will fix it - I just can't figure out why it works OK when executed manually as simply eg. "cvsup supfile" but stalls and starts anew when executed via crontab. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Perforce and cvsup access
On Tue, Apr 29, 2008 at 08:53:27PM +0200, David Naylor wrote: > Hi, > > I am trying to get a driver of perforce (//depot/projects/vap) to test out > however I do not know how to. I found out that perforce has been exported to > cvsup on cvsup10.freebsd.org and cvsup18.freebsd.org but I cannot find the > correct collection to use (and is there a list of the collections somewhere?) Only projects that specifically request a Perforce branch be exported to CVSup actually gets exported. This is because it's a royal pain to setup the export process. You might be better off asking the developers to provide a drop if you are looking for something specific. That would also make it less likely that you get the branch in an inconsistent state. Hope that helps! -gordon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipf fails after cvsup
Heya, Running a fresh install of 7.0-RELEASE. I've cvsup'd the sources, done the standard updating, e.g. make buildworld make buildkernel make installkernel (reboot) mergemaster -p make installworld mergemaster (reboot) But now ipf gives me ye olde Root Dude ? /sbin/ipf -Fa -f /etc/ipf.rules open device: No such file or directory User/kernel version check failed The ipf version is: Root Dude ? ipf -V ipf: IP Filter: v4.1.28 (512) open device: No such file or directory My supfile is pretty standard, with *default release=cvs tag=RELENG_7 src-all I've had this before when I've spaced out the make installworld. I've never gotten this *after* the sync/build. Have I missed a bit of documentation somewhere? -- Randy([EMAIL PROTECTED]) 765.983.1283 <*> Love with your heart, think with your head; not the other way around. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Perforce and cvsup access
Hi, I am trying to get a driver of perforce (//depot/projects/vap) to test out however I do not know how to. I found out that perforce has been exported to cvsup on cvsup10.freebsd.org and cvsup18.freebsd.org but I cannot find the correct collection to use (and is there a list of the collections somewhere?) Thanks in advance David signature.asc Description: This is a digitally signed message part.
CVSUP mirror failed on 7.0-RELEASE - Unknown collection src-all
Hi, I tried to setup a local mirror by installing cvsup-mirror on FreeBSD 7.0-RELEASE. The update.sh run to completion, but client failed to cvsup to the local mirror. In cvsupd.log, the error messsages follow :- Apr 29 21:41:34 havana cvsupd[2631]: CVSup server started Apr 29 21:41:34 havana cvsupd[2631]: Software version: SNAP_16_1h Apr 29 21:41:34 havana cvsupd[2631]: Protocol version: 17.0 Apr 29 21:41:34 havana cvsupd[2631]: Ready to service requests Apr 29 21:41:43 havana cvsupd[2633]: +0 [EMAIL PROTECTED] (havana.sml-citizen.com.hk) [SNAP_16_1h/17.0] Apr 29 21:41:43 havana cvsupd[2633]: =0 Unknown collection "src-all" Apr 29 21:41:44 havana cvsupd[2633]: -0 [0Kin+0Kout] Finished successfully I used the cvsup-mirror port on FreeBSD 6.x and it worked out of the box. I hope someone could point me what went wrong. Thanks a lot. John Mok ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install CVsup
yap..i tri using pkg_add but still the operation time out... what could possibly be wrong? Pleasethanks.. On Mon, Apr 21, 2008 at 3:39 PM, Glyn Millington <[EMAIL PROTECTED]> wrote: > "Ruel Luchavez" <[EMAIL PROTECTED]> writes: > > > Hi, > > > > my freebsd server is version 6.2, I want to install cvsup and this is > what i > > type in my box: > > > > cd /usr/ports/net/cvsup-without gui > > make install > > From the Handbook > > , > | The easiest way to install CVSup is to use the precompiled net/cvsup > | package from the FreeBSD packages collection. If you prefer to build > | CVSup from source, you can use the net/cvsup port instead. But be > | forewarned: the net/cvsup port depends on the Modula-3 system, which > | takes a substantial amount of time and disk space to download and build. > ` > > so why not try > > #pkg_add -r cvsup-without gui > > > ? > > atb > > > > > > > > Glyn > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install CVsup
But my question is why i allways has and error "Operation time out" or "time out"?? Is that a problem in my internet connection or not? thANKS... On Mon, Apr 21, 2008 at 3:57 PM, andrew clarke <[EMAIL PROTECTED]> wrote: > On Mon 2008-04-21 15:27:11 UTC+0800, Ruel Luchavez ([EMAIL PROTECTED]) > wrote: > > > my freebsd server is version 6.2, I want to install cvsup and this is > what i > > type in my box: > > > > cd /usr/ports/net/cvsup-without gui > > make install > > > > ..but during its process i allways has time-out connection then it ends > up.. > > 17:50 [EMAIL PROTECTED] [/usr/ports/net/cvsup-without-gui]make fetch > ===> Vulnerability check disabled, database not found > => cvsup-snap-16.1h.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > => Attempting to fetch from > ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/snapshots/. > cvsup-snap-16.1h.tar.gz<ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/snapshots/.cvsup-snap-16.1h.tar.gz> > 100% of 420 kB 113 kBps > > It seems to fetch the distfile fine here. But you should probably > look at using "csup" instead. It is functionally equivalent to > cvsup-without-gui but rewritten in C. It should be in the base system > on FreeBSD 6.2 (or newer) under /usr/bin. > > You may also want to look at Portsnap (which should be in the base > system at /usr/sbin/portsnap). I prefer it to csup. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install CVsup
On Mon 2008-04-21 15:27:11 UTC+0800, Ruel Luchavez ([EMAIL PROTECTED]) wrote: > my freebsd server is version 6.2, I want to install cvsup and this is what i > type in my box: > > cd /usr/ports/net/cvsup-without gui > make install > > ..but during its process i allways has time-out connection then it ends up.. 17:50 [EMAIL PROTECTED] [/usr/ports/net/cvsup-without-gui]make fetch ===> Vulnerability check disabled, database not found => cvsup-snap-16.1h.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/snapshots/. cvsup-snap-16.1h.tar.gz 100% of 420 kB 113 kBps It seems to fetch the distfile fine here. But you should probably look at using "csup" instead. It is functionally equivalent to cvsup-without-gui but rewritten in C. It should be in the base system on FreeBSD 6.2 (or newer) under /usr/bin. You may also want to look at Portsnap (which should be in the base system at /usr/sbin/portsnap). I prefer it to csup. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Install CVsup
>Hi, >my freebsd server is version 6.2, I want to install cvsup and this is what i >type in my box: >cd /usr/ports/net/cvsup-without gui >make install >..but during its process i allways has time-out connection then it ends up.. >I attached in this email the my console..PLease check it >Please tell me what i forgot..Thanks in advance.. Why do you want cvsup? There is csup that is in the base system. So if you use cvsup only to update the ports and base sources use csup! Regards, Johan Hendriks Double L Automatisering ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Install CVsup
Hi, my freebsd server is version 6.2, I want to install cvsup and this is what i type in my box: cd /usr/ports/net/cvsup-without gui make install ..but during its process i allways has time-out connection then it ends up.. I attached in this email the my console..PLease check it Please tell me what i forgot..Thanks in advance.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup will not speak to me :Connection refused
Lowell Gilbert wrote: I receive every time: Cannot connect to cvsup17.us.FreeSD.org: Connection refused I would appreciate anyone's suggestion on what to try. signed: perplexed. Try netcat or telnet to see what you get when a connections to cvsupd is initiated... I found a local firewall in place which was blocking this. I apologize for the bandwidth -- Jim Pazarena [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup will not speak to me :Connection refused
Jim Pazarena <[EMAIL PROTECTED]> writes: > I have a bank of 8 servers, all which do cvsup regularly for ports. > > I am recently going thru an upgrade to FreeBSD 7.0, and in a cvsup > with server #5, I get :Connection refused > > I cannot figure out why this machine would be refused, when the other > 4 upgrades to 7.0 work as expected. I use the same routine to do all my > cvsuping. > > I thought perhaps the IP # of this machine has been blackballed, so I changed > it, and I still get refused. > > I run: cvsup -g -L2 ports-supfile > > I use cvsup17.us.FreebBSD.org (altho I have tried many incantations > cvsup1, 2, etc). > > I receive every time: > Cannot connect to cvsup17.us.FreeSD.org: Connection refused > > I would appreciate anyone's suggestion on what to try. > signed: perplexed. Try netcat or telnet to see what you get when a connections to cvsupd is initiated... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup will not speak to me :Connection refused
I have a bank of 8 servers, all which do cvsup regularly for ports. I am recently going thru an upgrade to FreeBSD 7.0, and in a cvsup with server #5, I get :Connection refused I cannot figure out why this machine would be refused, when the other 4 upgrades to 7.0 work as expected. I use the same routine to do all my cvsuping. I thought perhaps the IP # of this machine has been blackballed, so I changed it, and I still get refused. I run: cvsup -g -L2 ports-supfile I use cvsup17.us.FreebBSD.org (altho I have tried many incantations cvsup1, 2, etc). I receive every time: Cannot connect to cvsup17.us.FreeSD.org: Connection refused I would appreciate anyone's suggestion on what to try. signed: perplexed. Jim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On Fri, 1 Feb 2008 14:12:43 +0100 Ruben de Groot <[EMAIL PROTECTED]> wrote: > On Thu, Jan 31, 2008 at 07:57:49PM -0600, Chris typed: > 23.2.2.1 What Is FreeBSD-STABLE? > FreeBSD-STABLE is our development branch from which major releases > are made. Changes go into this branch at a different pace, and with > the general assumption that they have first gone into FreeBSD-CURRENT > for testing. This is still a development branch, however, and this > means that at any given time, the sources for FreeBSD-STABLE may or > may not be suitable for any particular purpose. It is simply another > engineering development track, not a resource for end-users. > > RELENG_6 is STABLE > RELENG_6_3 is for security fixes > I stand corrected. -- Best regards, Chris Emperor Palpatine: Everything that has transpired has done so according to my design. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On Friday 01 February 2008 00:47:12 Allen wrote: > Now, this wouldn't work for some reason or another, but the system > seemed to be doing just fine. I did uname -a and sure enough I had > 6.3 Stable going. However, when typing kdm to load up that so I can > use a gui, it no longer loads, at all, it pops up for a split second to > just stop totally, and then gives me a message about the hostname. > > I thought it was odd, and XDM actually loads, but won't load X > itself as it too goes out with errors about hostname. So the hostname isn't set, the clue would be that machine presents itself as "amnesia". Check /etc/rc.conf so see if you set a hostname or if you use DHCP, check if the dhcp server gives you one. How this got lost in the upgrade, I don't know. mergemaster doesn't touch /etc/rc.conf, only /etc/defaults/rc.conf. > I've been looking on FreeBSD.org but I don't fnid anything about this, > but when did FreeBSD go from .tgz files to .tbz? I'm just wondering > what happened as I thought it was atypo at first and realized every > one of my books said .tbz and so did my screen heh. When libbz2 was brought into the base system, don't recall when exactly, somewhere around 5.0 I guess. tgz use gzip compression, tbz use bzip2 compression, which generally compresses better, but uses more CPU-time. FreeBSD can still read both though, it's just a change of default. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On Fri, Feb 01, 2008 at 09:45:30AM -0500, Gerard wrote:
> On Fri, 1 Feb 2008 15:14:59 +0100
> Erik Trulsson <[EMAIL PROTECTED]> wrote:
>
> {snip]
>
> > Going to single user mode is the less important part of rebooting.
> > The other part is that after the reboot you will be running the *new*
> > kernel which might possibly be needed for a successful installworld.
> > It is also a good test that the new kernel actually work. If the new
> > kernel should fail to work it is fairly easy to use the old kernel
> > instead. If you have already overwritten all userland programs with
> > ones which require the new (non-working) kernel it can be difficult
> > to recover from.
> >
> > Just going to single user mode without rebooting misses the point.
> > The important thing is not to go into single user mode, it is to
> > *reboot* into single user mode (or even into multi-user mode if you
> > want to, but there are fewer things that can go wrong when going to
> > single user mode.)
>
> From:
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
>From the same document:
23.4.9 Reboot into Single User Mode
You should reboot into single user mode to test the new kernel works. Do
this by following the instructions in Section 23.4.5
/usr/src/UPDATING (which contains the really official instructions for how
to upgrade) also tells you to reboot.
Just going into single user mode without rebooting is not very useful.
The section of the handbook you quote below should probably be rewritten
somewhat.
>
> 23.4.5 Drop to Single User Mode
>
> You may want to compile the system in single user mode. Apart from the
> obvious benefit of making things go slightly faster, reinstalling the
> system will touch a lot of important system files, all the standard
> system binaries, libraries, include files and so on. Changing these on
> a running system (particularly if you have active users on the system
> at the time) is asking for trouble.
>
> Another method is to compile the system in multi-user mode, and then
> drop into single user mode for the installation. If you would like to
> do it this way, simply hold off on the following steps until the build
> has completed. You can postpone dropping to single user mode until you
> have to installkernel or installworld.
>
> As the superuser, you can execute:
> # shutdown now
>
> from a running system, which will drop it to single user mode.
>
> --
>
> Gerard
> [EMAIL PROTECTED]
>
> The greatest productive force is human selfishness.
>
> Robert Heinlein
>
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On Fri, 1 Feb 2008 15:14:59 +0100
Erik Trulsson <[EMAIL PROTECTED]> wrote:
{snip]
> Going to single user mode is the less important part of rebooting.
> The other part is that after the reboot you will be running the *new*
> kernel which might possibly be needed for a successful installworld.
> It is also a good test that the new kernel actually work. If the new
> kernel should fail to work it is fairly easy to use the old kernel
> instead. If you have already overwritten all userland programs with
> ones which require the new (non-working) kernel it can be difficult
> to recover from.
>
> Just going to single user mode without rebooting misses the point.
> The important thing is not to go into single user mode, it is to
> *reboot* into single user mode (or even into multi-user mode if you
> want to, but there are fewer things that can go wrong when going to
> single user mode.)
From:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
23.4.5 Drop to Single User Mode
You may want to compile the system in single user mode. Apart from the
obvious benefit of making things go slightly faster, reinstalling the
system will touch a lot of important system files, all the standard
system binaries, libraries, include files and so on. Changing these on
a running system (particularly if you have active users on the system
at the time) is asking for trouble.
Another method is to compile the system in multi-user mode, and then
drop into single user mode for the installation. If you would like to
do it this way, simply hold off on the following steps until the build
has completed. You can postpone dropping to single user mode until you
have to installkernel or installworld.
As the superuser, you can execute:
# shutdown now
from a running system, which will drop it to single user mode.
--
Gerard
[EMAIL PROTECTED]
The greatest productive force is human selfishness.
Robert Heinlein
signature.asc
Description: PGP signature
Re: CVSup update or upgrade
On Fri, Feb 01, 2008 at 07:41:24AM -0500, Gerard wrote: > On Thu, 31 Jan 2008 19:57:49 -0600 > Chris <[EMAIL PROTECTED]> wrote: > > > Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you > > do not have customization in /etc - here's what I do... > > > > After a cvsup of the src tree (ensuring I want the STABLE branch > > (*default release=cvs tag=RELENG_6) > > > > # cd /usr/src > > # make buildworld > > # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) > > # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) > > # shutdown -r now (no need for Single-User Mode if YOU are the only > > user) > > You can just type: "shutdown now" to go into single user mode. It > avoids the reboot sequence. Going to single user mode is the less important part of rebooting. The other part is that after the reboot you will be running the *new* kernel which might possibly be needed for a successful installworld. It is also a good test that the new kernel actually work. If the new kernel should fail to work it is fairly easy to use the old kernel instead. If you have already overwritten all userland programs with ones which require the new (non-working) kernel it can be difficult to recover from. Just going to single user mode without rebooting misses the point. The important thing is not to go into single user mode, it is to *reboot* into single user mode (or even into multi-user mode if you want to, but there are fewer things that can go wrong when going to single user mode.) > > > # cd /usr/src > > # make installworld > > I prefer to use the following after "make installworld" > > mergemaster -i -v -U > > Read the man pages for mergemaster for further details. > > > # shutdown -r now > > After rebooting, you might want to cd to the /usr/src directory and > run: "make delete-old-libs" to clear out any garbage. It is not > actually required however. > > -- > > Gerard > [EMAIL PROTECTED] > > In the long run we are all dead. > > John Maynard Keynes > -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On Thu, Jan 31, 2008 at 07:57:49PM -0600, Chris typed: > NOTE: I don't use mergemaster unless I go from say 6.3 to 7.0 Not wise. New features and fixes are applied to configuration files and rc scripts regu;arly. You'll probably miss them. > STABLE is the security fix branch. Wrong. According to the handbook: 23.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. RELENG_6 is STABLE RELENG_6_3 is for security fixes regards, Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On Thu, 31 Jan 2008 19:57:49 -0600 Chris <[EMAIL PROTECTED]> wrote: > Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you > do not have customization in /etc - here's what I do... > > After a cvsup of the src tree (ensuring I want the STABLE branch > (*default release=cvs tag=RELENG_6) > > # cd /usr/src > # make buildworld > # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) > # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) > # shutdown -r now (no need for Single-User Mode if YOU are the only > user) You can just type: "shutdown now" to go into single user mode. It avoids the reboot sequence. > # cd /usr/src > # make installworld I prefer to use the following after "make installworld" mergemaster -i -v -U Read the man pages for mergemaster for further details. > # shutdown -r now After rebooting, you might want to cd to the /usr/src directory and run:"make delete-old-libs" to clear out any garbage. It is not actually required however. -- Gerard [EMAIL PROTECTED] In the long run we are all dead. John Maynard Keynes signature.asc Description: PGP signature
Re: CVSup update or upgrade
On Fri, 1 Feb 2008 02:21:42 + (UTC) Jona Joachim <[EMAIL PROTECTED]> wrote: > On 2008-02-01, Chris <[EMAIL PROTECTED]> wrote: > > On Thu, 31 Jan 2008 18:47:12 -0500 > > Allen <[EMAIL PROTECTED]> wrote: > > > >> Hello, > >> > >> I've been reading over my library of FreeBSD books, which I may > >> add is impressive due to me buying EVERY book available on > >> Freebsdmall and also buying the PowerPak to make sure my Library > >> is complete, and also I've been reading the freebsd.org docs > >> because I'm working on getting an upgrade to work properly. > >> > >> Here is what happened: > >> > >> I did as the website said and changed the cvsup example file which > >> is the one I'm using, to a FreeBSD cvsup server, left most of it > >> alone, because I wanted to use most packages, so I wanted > >> basically every app available, and when rebooting, after doing > >> this: > >> > >> # make buildworld > >> # make buildkernel > >> # make installkernel > >> # reboot > > > > Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming > > you do not have customization in /etc - here's what I do... > > > > After a cvsup of the src tree (ensuring I want the STABLE branch > > (*default release=cvs tag=RELENG_6) > > > > # cd /usr/src > > # make buildworld > > # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) > > # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) > > # shutdown -r now (no need for Single-User Mode if YOU are the only > > user) > > Sorry but you're giving wrong advice here. > *Always* drop to single user mode. > You are almost never the only user on your machine when you're in > multiuser mode. There will at least be root an your user account and > probably others. I'm not giving advice - I'm simply stating what *I* do. See my words below. > > Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming > > you do not have customization in /etc - here's what I do... Note the "here's what I do..." That does not sound like I'm advising any user to do what I do - only stating things based on my experiences. ... as to Single-User mode and mergemaster, here again, I can only comment on what I do and my experiences. I myself have never had a system failure due to not running mergemaster. Furthermore, I have never had issues not booting into Single-User mode to update my boxen. Of course, your mileage may vary. -- Best regards, Chris The lines are all busy (busied out, that is -- why let them in to begin with?). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On 2008-02-01, Chris <[EMAIL PROTECTED]> wrote: > On Thu, 31 Jan 2008 18:47:12 -0500 > Allen <[EMAIL PROTECTED]> wrote: > >> Hello, >> >> I've been reading over my library of FreeBSD books, which I may add is >> impressive due to me buying EVERY book available on Freebsdmall and >> also buying the PowerPak to make sure my Library is complete, and >> also I've been reading the freebsd.org docs because I'm working on >> getting an upgrade to work properly. >> >> Here is what happened: >> >> I did as the website said and changed the cvsup example file which is >> the one I'm using, to a FreeBSD cvsup server, left most of it alone, >> because I wanted to use most packages, so I wanted basically every app >> available, and when rebooting, after doing this: >> >> # make buildworld >> # make buildkernel >> # make installkernel >> # reboot > > Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you > do not have customization in /etc - here's what I do... > > After a cvsup of the src tree (ensuring I want the STABLE branch > (*default release=cvs tag=RELENG_6) > > # cd /usr/src > # make buildworld > # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) > # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) > # shutdown -r now (no need for Single-User Mode if YOU are the only > user) Sorry but you're giving wrong advice here. *Always* drop to single user mode. You are almost never the only user on your machine when you're in multiuser mode. There will at least be root an your user account and probably others. > # cd /usr/src > # make installworld > # shutdown -r now > > NOTE: I don't use mergemaster unless I go from say 6.3 to 7.0 *Always* use mergemaster. Default configuration is constantly changing slightly. It never happened to me that mergemaster had nothing to and I upgrade somewhat regularly. Not running mergemaster will sooner or later result in a broken system. It can be argued whether `mergemaster -p` has to be run everytime but just run it, it will never hurt you. I really recommend following the handbook step by step for this task unless you know exactly what you're doing. >> I booted in single user mode and tried this: >> >> # mergemaster -p >> # make installworld >> # mergemaster >> # reboot >> >> Now, this wouldn't work for some reason or another, but the system >> seemed to be doing just fine. I did uname -a and sure enough I had >> 6.3 Stable going. However, when typing kdm to load up that so I can >> use a gui, it no longer loads, at all, it pops up for a split second >> to just stop totally, and then gives me a message about the hostname. > > See above for your RELENG Tag > > >> I thought it was odd, and XDM actually loads, but won't load X >> itself as it too goes out with errors about hostname. > > You may need to update your ports tree and your installed packages > since you went to STABLE > >> I don't have the exact message which I know is bad form on my part, >> but I decided to just try updating again as I was kind of wondering >> what RELEASE is like instead of stable. > > STABLE is the security fix branch. > > *snip* > > Someone else may follow up the rest with you. > Best regards, Jona -- "I am chaos. I am the substance from which your artists and scientists build rhythms. I am the spirit with which your children and clowns laugh in happy anarchy. I am chaos. I am alive, and tell you that you are free." Eris, Goddess Of Chaos, Discord & Confusion" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup update or upgrade
On Thu, 31 Jan 2008 18:47:12 -0500 Allen <[EMAIL PROTECTED]> wrote: > Hello, > > I've been reading over my library of FreeBSD books, which I may add is > impressive due to me buying EVERY book available on Freebsdmall and > also buying the PowerPak to make sure my Library is complete, and > also I've been reading the freebsd.org docs because I'm working on > getting an upgrade to work properly. > > Here is what happened: > > I did as the website said and changed the cvsup example file which is > the one I'm using, to a FreeBSD cvsup server, left most of it alone, > because I wanted to use most packages, so I wanted basically every app > available, and when rebooting, after doing this: > > # make buildworld > # make buildkernel > # make installkernel > # reboot Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) # cd /usr/src # make installworld # shutdown -r now NOTE: I don't use mergemaster unless I go from say 6.3 to 7.0 > I booted in single user mode and tried this: > > # mergemaster -p > # make installworld > # mergemaster > # reboot > > Now, this wouldn't work for some reason or another, but the system > seemed to be doing just fine. I did uname -a and sure enough I had > 6.3 Stable going. However, when typing kdm to load up that so I can > use a gui, it no longer loads, at all, it pops up for a split second > to just stop totally, and then gives me a message about the hostname. See above for your RELENG Tag > I thought it was odd, and XDM actually loads, but won't load X > itself as it too goes out with errors about hostname. You may need to update your ports tree and your installed packages since you went to STABLE > I don't have the exact message which I know is bad form on my part, > but I decided to just try updating again as I was kind of wondering > what RELEASE is like instead of stable. STABLE is the security fix branch. *snip* Someone else may follow up the rest with you. -- Best regards, Chris Someone is standing on the ethernet cable, causeing a kink in the cable ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CVSup update or upgrade
Hello, I've been reading over my library of FreeBSD books, which I may add is impressive due to me buying EVERY book available on Freebsdmall and also buying the PowerPak to make sure my Library is complete, and also I've been reading the freebsd.org docs because I'm working on getting an upgrade to work properly. Here is what happened: I did as the website said and changed the cvsup example file which is the one I'm using, to a FreeBSD cvsup server, left most of it alone, because I wanted to use most packages, so I wanted basically every app available, and when rebooting, after doing this: # make buildworld # make buildkernel # make installkernel # reboot I booted in single user mode and tried this: # mergemaster -p # make installworld # mergemaster # reboot Now, this wouldn't work for some reason or another, but the system seemed to be doing just fine. I did uname -a and sure enough I had 6.3 Stable going. However, when typing kdm to load up that so I can use a gui, it no longer loads, at all, it pops up for a split second to just stop totally, and then gives me a message about the hostname. I thought it was odd, and XDM actually loads, but won't load X itself as it too goes out with errors about hostname. I don't have the exact message which I know is bad form on my part, but I decided to just try updating again as I was kind of wondering what RELEASE is like instead of stable. This is perfectly fine because the machine is NOT used as a server really, and is mainly for me to test out stuff and use FreeBSD more so I'm not worried about it breaking, or reinstalling the OS, it's no big deal, my reaqson for doing this the first time was mainly because pkg_add -r wouldn't work, I have 6.0 on the CDs I bought from the mall site, and I also have another 6.0 install disk as I bought a second copy, may seem odd but I like having more than one on CD (or in thie case 4 copies) but I like to help support the BSD people, so I do it. Anyway, does anyone have any idea? I'm using the web site for docs as my books seem to have different instructions all together which is odd but I also know that books coming up vs software coming out, you can't really keep books coming out at the same rate, so I decided to use the web docs for something like this to have more up to date info, so here it is since this message si looking rather sloppy: --I have install disks for FreeBSD 6.0 -- I don't mind reinstalling but would rather fix it and learn how -- I'm currently running an update again with cvsup as it says this is a better choice and option --I'm not a Unix wizard but I DO know enough to get around and dream of one day being a Unix hacker, that's a dream for now though, I came from using Windows and Linux, and still use both heh --IF I've borked up the system bad enough that a reinstall is the best option I really don't mind, I'd just like to know how to at least prevent this from happening again so I can stay up to date in FreeBSD I followed the instructions pretty much to the letter here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html The system has nothing really important on it yet as I set it up to learn more with so I can start using FreeBSD the way I do Linux, as a desktop to do my work and tests on. Thanks very much, and as I said, if I really screwed up or something, I can just reinstall. also, one more thing: Does anyone know how to make pkg_add -r package work again in a fresh install of FreeBSD 6.0? When I ran it after the install to grab something it said it didn't work and couldn't be found, and so I decided to investigate and found the reason to be the host it looks up is no longer there, so I just went to Freebsd.org and looked and found the server was renamed since 6.0 was released, and so I just updated everything for it to work better. Also, one last question: I've been looking on FreeBSD.org but I don't fnid anything about this, but when did FreeBSD go from .tgz files to .tbz? I'm just wondering what happened as I thought it was atypo at first and realized every one of my books said .tbz and so did my screen heh. Any info on that would be neat too :) Thanks VERY much! -Allen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Mon, Jan 07, 2008 at 03:58:41AM +, Frank Shute wrote: > On Sun, Jan 06, 2008 at 09:24:15PM +0100, Erik Trulsson wrote: > > > > On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote: > > > On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: > > > > > > > > Hi > > > > > > > > Upon reading chapters of the Handbook about the Ports collection > > > > and CVSup, I wanted to CVSup the ports collection for the > > > > RELEASE 6.2. Stupidly using the wrong tag (tag=.), I > > > > erroneously but successfully installed the CURRENT version. I > > > > could have used SYSINSTALL for the RELEASE 6.2 ports, but for > > > > the sake of learning and training myself I did not. > > > > > > You used the right tag. There is only a current tag as you only have a > > > current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The > > > ports might work with older releases too). > > > > Wrong. The ports tree is not branched, but it is tagged and it does have > > tags corresponding to each FreeBSD release. > > So if it's not branched but tagged, what's the difference between the > ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags > in my ports supfile? None whatsoever. Neither tag is a valid tag for the ports tree, so you will end up with an empty ports tree in either case. If you were instead to use the valid tags RELEASE_4_8_0 or RELEASE_7_0_0 you would get the ports tree that shipped with 4.8-RELEASE or the ports tree that will (barring last minute changes) ship with 7.0-RELEASE respectively. > > > > > > > > Problem: > > > > > > > > - I ran CVSup again with the correct tag but though everything > > > > in the process looked normal, the map usr/ports remains empty > > > > and nor with whereis nor with pkg_xxx any information about > > > > ports can be found. > > > > > > You ran cvsup again with the wrong tag. > > > > > > > > > > > Questions: > > > > > > > > - What did I do wrong in the process?. > > > > > > Used the wrong tag second time around. > > > > > > > > > > > - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea > > > > anyway (technically) ? > > > > > > No. Although there is no 6.2 ports collection, just CURRENT. > > > > Of course there is a 6.2 ports collection. What else would you call the > > ports tree shipped with FreeBSD 6.2? > > A snapshot of the ports tree when the release was made. > > > > > > > > > > > > > > > > > > > > > > > > Proces: > > > > > > > > - I use the recently installed cvsup-without-gui, installed from ports > > > > > > Use csup(1) it's identical to cvsup but no dependencies as it's in > > > base & written in C. > > > > Not quite identical. There are a couple of features that cvsup(1) has, but > > which csup(1) does not yet have. > > To just check out a copy of the ports tree either should work fine though. > > Features that a newbie wouldn't use. It's also difficult to build > cvsup when you don't necessarily have a ports tree. But you do not need a ports tree to install cvsup as a package. In either case csup(1) is not identical to cvsup(1) in functionality even if it can often be used as a drop-in replacement. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Mon, Jan 07, 2008 at 09:03:12AM +, Matthew Seaman wrote: > > > Frank Shute wrote: > > > So if it's not branched but tagged, what's the difference between the > > ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags > > in my ports supfile? > > Probably not a very great deal -- you'll get equally disappointing > results for both of those. RELENG_X and RELENG_X_Y tags / branches > apply to the src collection *only*. If you try and use them on the > ports you'll end up with a whole lot of nothing. None of the ports > tree is intentionally tagged with anything matching 'RELENG' This is where the original poster went wrong, he first off used tag=. which got him current ports, decided he wanted 6.2 ports and used RELENG_6_2 as a tag in his ports supfile and got nothing. > > In general, you always want the HEAD of the ports tree. There's > very little point in using anything else. I was trying to make the point you should use tag=. in ports supfile. > However it is possible > to use RELEASE_X_Y_0 to match the state of the ports tree used > to generate the packages distributed with X.Y RELEASE, or if you > still haven't upgraded all your 4.x machines yet, you can use > RELEASE_4_EOL to match the last state of the tree before the 4.x > compatability code was stripped out. This I didn't know. It used to be AFAIR that because of disk constraints only head was available. But I see from the CVS tags page that you can get the tree in it's old state with tags such as: RELENG_6_2_0_RELEASE http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html A.7.2 > > Note that cvsup'ing an old version of the ports tree is not > guaranteed to provide a workable ports collection: the dist files > the ports rely upon are not in the control of the FreeBSD project > and there is no assurance that old versions of software are still > available for download. Plus you will be struggling with unfixed > security bugs if you've installed portaudit -- or installing > vulnerable software if you haven't. I can't see the point in holding old versions of the ports tree except for nostalgic reasons and masochists. Although, I suppose portdowngrade works with it (never used it). Even the oldest machine you can usually upgrade to something new. E.g Tags for my webserver (300MHz Celeron 128MB) is tag=. for ports and RELEASE_6_3 for src. Works fine. Used to have problems building ruby due to the low memory so just built a package on my workstation and copied it over. > > Cheers, > > Matthew Thanks for explaining how things currently stand, Matthew. Regards, -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank Shute wrote: > So if it's not branched but tagged, what's the difference between the > ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags > in my ports supfile? Probably not a very great deal -- you'll get equally disappointing results for both of those. RELENG_X and RELENG_X_Y tags / branches apply to the src collection *only*. If you try and use them on the ports you'll end up with a whole lot of nothing. None of the ports tree is intentionally tagged with anything matching 'RELENG' In general, you always want the HEAD of the ports tree. There's very little point in using anything else. However it is possible to use RELEASE_X_Y_0 to match the state of the ports tree used to generate the packages distributed with X.Y RELEASE, or if you still haven't upgraded all your 4.x machines yet, you can use RELEASE_4_EOL to match the last state of the tree before the 4.x compatability code was stripped out. Note that cvsup'ing an old version of the ports tree is not guaranteed to provide a workable ports collection: the dist files the ports rely upon are not in the control of the FreeBSD project and there is no assurance that old versions of software are still available for download. Plus you will be struggling with unfixed security bugs if you've installed portaudit -- or installing vulnerable software if you haven't. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHgerP8Mjk52CukIwRCFAlAKCNmQAfP3JDHdBde/s4VWwcs3BGsACeNG/d kbfd4wXcBsG1U6tYvwIXmD0= =3Rc0 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Smith wrote:
> On Sun, 6 Jan 2008, Aryeh M. Friedman wrote:
>
>>>>> If you don't have cvsup installed, run this command: #
>>>>> pkg_add -r cvsup-without-gui
>>>>
>>>> It is better to use all ports or all packages so either do:
>>>
>>> Why do you say that? Do you know of unresolved issues
>>> regarding the interactions of port versus package
>>> installations? Any references?
>>
>> I am not currently aware of any conflicts but the fact that they
>> have historical been more frequent then inter-port or
>> inter-package conflicts leads to the conculsion... unlike either
>> of the above they are harder to troubleshoot
>
> The only problems I've ever seen with installing packages is that
> at times the package-building farm gets a bit behind, when you
> might need to build a desired newly updated port from source, and
> that in some cases a package built with default options may not be
> what you want. php5 is one example of the latter, as the default
> options do not include mod_php5 which (I gather?) is why most
> people install php at all.
The main issue is assuming that certain things are installed because
that is the way the developers recommend it then you install a package
and find out that the maintainer had different ideas. A very good
current example is boost vs. boost-python in regards to the
requirements for deluge and miro respectivally. An other example is
the entire Java tree.
>
> And yes there are some ports that don't have packages for licencing
> etc reasons, though I can't recall ever having to install one of
> those.
I am the author (but not the maintainer) of such a port
(devel/thistest) and there is often very legit reasons for not
allowing packages... for example my license requires explicit
agreement before you can download the source and/or binaries (because
it has specific provisions regarding execution vs. source usage [see
my blog for more details...
http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/index.php]).
>
> Not everyone has fast hardware and good bandwidth, so installing
> from packages for really big ports - such as X, KDE or Gnome,
> j{dk,re}, OO and such - is almost mandatory on smaller systems.
> Release CDs install at least the former three as packages of
> course, for obvious reasons, and at least around release times, up
> to date packages can be expected.
My experience has been every time I have attempted to make the two
play together well it blows up. It has been so long since I have used
a package vs. a port I can't site a specific example.
>
> I just think saying "it's better to use all ports or all packages"
> is poor and maybe misleading advice, particularly expressed without
> 'IMHO', as it implies problems that RE should know about -
> especially right now!
This is more of a long term issue that is being worked on by several
groups including the "ports 2.0" team that I am member of [see long
set threads in -ports@ regarding ports system re-engineering]... much
of the stuff I hint at in this thread is better spelled out there.
>
>>>> cd /usr/ports/net/cvsup-without-gui make install clean
>>>>
>>>> or after doing the above do a pkg_delete -a (assuming that
>>>> your working with a clean machine [no ports/packages
>>>> instaleld except cvsup]
>>>
>>> Why wouldn't pkg_delete -a remove your just-installed
>>> cvsup-without-gui?
>>
>> Sorry for not being clear I meant before the reinstall (besides
>> make install would fail if you hadn't done a pkg_delete -a)
>
> Hmm ok - thought you might be suggesting that port installs don't
> update the package database in /var/db/pkg just the same as pkg_add
> does.
>
>>>>> For more info on the supfile, look at this file on your
>>>>> FreeBSD machine: /usr/share/examples/cvsup/ports-supfile
>>>>>
>>>>> Preferring cvsup to portsnap is kinda like preferring vim
>>>>> over emacs... It's a holy war and the vi/cvsup side uses
>>>>> less disk space.
>>>>
>>>> Actually it is not like that at all.. cvsup/csup is the
>>>> officially preferred method and any other method is a short
>>>> cut of some kind...
>>>
>>> Please provide a reference URL to 'official' support of this
>>> claim?
>>
>> This is a case of actions by the developer community speaks
>> louder then words:
>>
>> 1. Csup is in the base system thus obvious preferred to either
>> cvsup or
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
On Sun, 6 Jan 2008, Aryeh M. Friedman wrote:
> > > > If you don't have cvsup installed, run this command: # pkg_add -r
> > > > cvsup-without-gui
> > >
> > > It is better to use all ports or all packages so either do:
> >
> > Why do you say that? Do you know of unresolved issues regarding the
> > interactions of port versus package installations? Any references?
>
> I am not currently aware of any conflicts but the fact that they have
> historical been more frequent then inter-port or inter-package
> conflicts leads to the conculsion... unlike either of the above they
> are harder to troubleshoot
The only problems I've ever seen with installing packages is that at
times the package-building farm gets a bit behind, when you might need
to build a desired newly updated port from source, and that in some
cases a package built with default options may not be what you want.
php5 is one example of the latter, as the default options do not include
mod_php5 which (I gather?) is why most people install php at all.
And yes there are some ports that don't have packages for licencing etc
reasons, though I can't recall ever having to install one of those.
Not everyone has fast hardware and good bandwidth, so installing from
packages for really big ports - such as X, KDE or Gnome, j{dk,re}, OO
and such - is almost mandatory on smaller systems. Release CDs install
at least the former three as packages of course, for obvious reasons,
and at least around release times, up to date packages can be expected.
I just think saying "it's better to use all ports or all packages" is
poor and maybe misleading advice, particularly expressed without 'IMHO',
as it implies problems that RE should know about - especially right now!
> > > cd /usr/ports/net/cvsup-without-gui
> > > make install clean
> > >
> > > or after doing the above do a pkg_delete -a (assuming that your
> > > working with a clean machine [no ports/packages instaleld except cvsup]
> >
> > Why wouldn't pkg_delete -a remove your just-installed cvsup-without-gui?
>
> Sorry for not being clear I meant before the reinstall (besides make
> install would fail if you hadn't done a pkg_delete -a)
Hmm ok - thought you might be suggesting that port installs don't update
the package database in /var/db/pkg just the same as pkg_add does.
> > > > For more info on the supfile, look at this file on your FreeBSD
> > > > machine: /usr/share/examples/cvsup/ports-supfile
> > > >
> > > > Preferring cvsup to portsnap is kinda like preferring vim over
> > > > emacs... It's a holy war and the vi/cvsup side uses less disk
> > > > space.
> > >
> > > Actually it is not like that at all.. cvsup/csup is the officially
> > > preferred method and any other method is a short cut of some kind...
> >
> > Please provide a reference URL to 'official' support of this claim?
>
> This is a case of actions by the developer community speaks louder
> then words:
>
> 1. Csup is in the base system thus obvious preferred to either cvsup
> or portsnap
% which portsnap
/usr/sbin/portsnap
> 2. C(v)sup is more universal
> 3. The only way to maintain an official local repo is via cvsup
You're talking about updating sources, ports and CVS too. We were just
talking about maintaining the ports tree. I sense nothing 'official'.
> > > many of them have very subtle issues that the typical end-user should
> > > not notice but should be aware of...
> >
> > Issues such as? And what other alternatives to c*sup and portsnap exist
> > for ports tree management?
>
> I can think of several off the top my head:
>
> 1. Ftp ports.tar.gz and unpack
Sure. Plus make fetchindex or such.
> 2. Maintain a local repo like I do
Clearly not a job for portsnap :)
> 3. Use portupgrade in conjunction with the above
>
> I was specifically refeering to the 3rd option when I said there where
> subtle issues. Speicfically the way "make install" (recursive) and
> "portupgrade -a" calculate the build order can lead to some issues
> (like compiling the default OPTIONS before asking the user to select
> OPTIONS)
It seems that here you're confusing port maintenance and upgrading
tools (portupgrade, portmaster etc and/or make install) with a choice
between c*sup and portsnap for maintaining the ports _tree_ and INDEX,
which is precisely all that portsnap is designed to do, and does well.
Sorry if I sound a bit harsh, but there seems to have been a flurry of
deprecation approaching folklore
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Mon, Jan 07, 2008 at 12:34:50AM +0100, Walter Jansen wrote: > > Thanks for your effort Fank, but unfortunately the Handbook shows that your > answer does not reflect the actual use of tags for fetching ports with > cvsup. Your answer triggers me to look for other places where information > can be found in order to reduce the confusion, and that is what I am > grateful for. Walter, show me in the handbook where my answer doesn't reflect the reality of using tags for fetching ports. Thanks. Read this (I know it's old): http://www.freebsddiary.org/ports.php // NOTE: Don't worry about releases/version when cvsup'ing your ports. There is only one version of the Ports collection. All versions of FreeBSD use the same ports collection. Therefore, when updating your ports use this tag: tag=. // You can use that tag for your src supfile too but you will get 8.0 which you don't want to do unless you are a developer. > > > Have a good day! > Walter > You too. -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 09:24:15PM +0100, Erik Trulsson wrote: > > On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote: > > On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: > > > > > > Hi > > > > > > Upon reading chapters of the Handbook about the Ports collection > > > and CVSup, I wanted to CVSup the ports collection for the > > > RELEASE 6.2. Stupidly using the wrong tag (tag=.), I > > > erroneously but successfully installed the CURRENT version. I > > > could have used SYSINSTALL for the RELEASE 6.2 ports, but for > > > the sake of learning and training myself I did not. > > > > You used the right tag. There is only a current tag as you only have a > > current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The > > ports might work with older releases too). > > Wrong. The ports tree is not branched, but it is tagged and it does have > tags corresponding to each FreeBSD release. So if it's not branched but tagged, what's the difference between the ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags in my ports supfile? > > > > > > > > > > > > > > > > > Problem: > > > > > > - I ran CVSup again with the correct tag but though everything > > > in the process looked normal, the map usr/ports remains empty > > > and nor with whereis nor with pkg_xxx any information about > > > ports can be found. > > > > You ran cvsup again with the wrong tag. > > > > > > > > Questions: > > > > > > - What did I do wrong in the process?. > > > > Used the wrong tag second time around. > > > > > > > > - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea > > > anyway (technically) ? > > > > No. Although there is no 6.2 ports collection, just CURRENT. > > Of course there is a 6.2 ports collection. What else would you call the > ports tree shipped with FreeBSD 6.2? A snapshot of the ports tree when the release was made. > > > > > > > > > > > > > > > > Proces: > > > > > > - I use the recently installed cvsup-without-gui, installed from ports > > > > Use csup(1) it's identical to cvsup but no dependencies as it's in > > base & written in C. > > Not quite identical. There are a couple of features that cvsup(1) has, but > which csup(1) does not yet have. > To just check out a copy of the ports tree either should work fine though. Features that a newbie wouldn't use. It's also difficult to build cvsup when you don't necessarily have a ports tree. Regards, -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
Gerard wrote: On Sun, 06 Jan 2008 15:41:35 -0500 "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: [snip] 1. Csup is in the base system thus obvious preferred to either cvsup or portsnap Correct me if I am wrong; however, I thought that 'portsnap' was part of the base system. Yes, portsnap is part of the base system, as is csup. csup and cvsup are equivalent unless you need to create a local repository (i.e. getting the RCS ,v files) which is not required for anyone simply wishing to use the ports tree for building apps. This feature is only available in cvsup. As for the OP, the tag to get the ports for FreeBSD 6.2-RELEASE would be: RELEASE_6_2_0 This is mentioned in the handbook, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html (the paragraph text in A.7.2) but may be it is not clear enough, since all the examples that follow refer to the src tree tags (which start with RELENG) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
On Sun, 06 Jan 2008 15:41:35 -0500 "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: [snip] > 1. Csup is in the base system thus obvious preferred to either cvsup > or portsnap Correct me if I am wrong; however, I thought that 'portsnap' was part of the base system. -- Gerard [EMAIL PROTECTED] I cannot conceive that anybody will require multiplications at the rate of 40,000 or even 4,000 per hour ... F. H. Wales (1936) signature.asc Description: PGP signature
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > > > > If you don't have cvsup installed, run this command: # pkg_add -r > > > cvsup-without-gui > > > > It is better to use all ports or all packages so either do: > > Why do you say that? Do you know of unresolved issues regarding the > interactions of port versus package installations? Any references? I am not currently aware of any conflicts but the fact that they have historical been more frequent then inter-port or inter-package conflicts leads to the conculsion... unlike either of the above they are harder to troubleshoot > > > cd /usr/ports/net/cvsup-without-gui > > make install clean > > > > or after doing the above do a pkg_delete -a (assuming that your > > working with a clean machine [no ports/packages instaleld except cvsup] > > Why wouldn't pkg_delete -a remove your just-installed cvsup-without-gui? Sorry for not being clear I meant before the reinstall (besides make install would fail if you hadn't done a pkg_delete -a) > > > > For more info on the supfile, look at this file on your FreeBSD > > > machine: /usr/share/examples/cvsup/ports-supfile > > > > > > Preferring cvsup to portsnap is kinda like preferring vim over > > > emacs... It's a holy war and the vi/cvsup side uses less disk > > > space. > > > > Actually it is not like that at all.. cvsup/csup is the officially > > preferred method and any other method is a short cut of some kind... > > Please provide a reference URL to 'official' support of this claim? This is a case of actions by the developer community speaks louder then words: 1. Csup is in the base system thus obvious preferred to either cvsup or portsnap 2. C(v)sup is more universal 3. The only way to maintain an official local repo is via cvsup > > > many of them have very subtle issues that the typical end-user should > > not notice but should be aware of... > > Issues such as? And what other alternatives to c*sup and portsnap exist > for ports tree management? I can think of several off the top my head: 1. Ftp ports.tar.gz and unpack 2. Maintain a local repo like I do 3. Use portupgrade in conjunction with the above I was specifically refeering to the 3rd option when I said there where subtle issues. Speicfically the way "make install" (recursive) and "portupgrade -a" calculate the build order can lead to some issues (like compiling the default OPTIONS before asking the user to select OPTIONS) > > ooroo, Ian > > - -- Aryeh M. Friedman FloSoft Systems, Java Developer Tools http://www.flosoft-systems.com Developer, not business, friendly. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHgTz+jRvRjGmHRgQRAgj8AKCbgfQfoquUWiceLSGxOBQmNDLGxQCeJLGY p2zteaiWHCoJ95O64urXoZs= =P5jK -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote: > On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: > > > > Hi > > > > Upon reading chapters of the Handbook about the Ports collection and CVSup, > > I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using > > the wrong tag (tag=.), I erroneously but successfully installed the CURRENT > > version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the > > sake of learning and training myself I did not. > > You used the right tag. There is only a current tag as you only have a > current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The > ports might work with older releases too). Wrong. The ports tree is not branched, but it is tagged and it does have tags corresponding to each FreeBSD release. > > > > > > > > > Problem: > > > > - I ran CVSup again with the correct tag but though everything in the > > process looked normal, the map usr/ports remains empty and nor with whereis > > nor with pkg_xxx any information about ports can be found. > > You ran cvsup again with the wrong tag. > > > > > Questions: > > > > - What did I do wrong in the process?. > > Used the wrong tag second time around. > > > > > - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea > > anyway (technically) ? > > No. Although there is no 6.2 ports collection, just CURRENT. Of course there is a 6.2 ports collection. What else would you call the ports tree shipped with FreeBSD 6.2? > > > > > > > > > Proces: > > > > - I use the recently installed cvsup-without-gui, installed from ports > > Use csup(1) it's identical to cvsup but no dependencies as it's in > base & written in C. Not quite identical. There are a couple of features that cvsup(1) has, but which csup(1) does not yet have. To just check out a copy of the ports tree either should work fine though. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: > > Hi > > Upon reading chapters of the Handbook about the Ports collection and CVSup, > I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using > the wrong tag (tag=.), I erroneously but successfully installed the CURRENT > version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the > sake of learning and training myself I did not. You used the right tag. There is only a current tag as you only have a current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The ports might work with older releases too). > > > > Problem: > > - I ran CVSup again with the correct tag but though everything in the > process looked normal, the map usr/ports remains empty and nor with whereis > nor with pkg_xxx any information about ports can be found. You ran cvsup again with the wrong tag. > > Questions: > > - What did I do wrong in the process?. Used the wrong tag second time around. > > - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea > anyway (technically) ? No. Although there is no 6.2 ports collection, just CURRENT. > > > > Proces: > > - I use the recently installed cvsup-without-gui, installed from ports Use csup(1) it's identical to cvsup but no dependencies as it's in base & written in C. > > - I deleted all entries and maps in/under /usr/ports (as recommended in the > Handbook) All you need is the empty dir /usr/ports and c(v)sup will fill it. > > > > - I modified the ports-supfile in usr/share/examples/cvsup and copied it to > portswj-supfile in the same map (not good practice I know now) > > The settings in the -supfile where: > > *default host=cvsup15.FreeBSD.org > > *default base=/var/db > > *default prefix=/usr > > *default release=cvs tag=RELENG_6_2_0_RELEASE (the handbook suggests > that this is a valid tag for ports) > > *default delete use-rel-suffix (I could not find a meaning for this in > the books, anyone can tell me please?) > > *default compress > > ports-all Try this as your ports-supfile: *default host=cvsup15.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all and run: csup -L 2 /usr/share/examples/cvsup/ports-supfile and it should download the current ports tree. For the src supfile you should use the tag: *default release=cvs tag=RELENG_6_3 as 6.3 is pretty close to release and you'll get 6.3RC2 probably. or if you want 7.0RC2(?) *default release=cvs tag=RELENG_7_0 For the src-supfile you only need to set that tag and the default host and it should work. Regards, -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
Erik Trulsson wrote:
On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote:
Hi
Upon reading chapters of the Handbook about the Ports collection and CVSup,
I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using
the wrong tag (tag=.), I erroneously but successfully installed the CURRENT
version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the
sake of learning and training myself I did not.
Problem:
- I ran CVSup again with the correct tag but though everything in the
process looked normal, the map usr/ports remains empty and nor with whereis
nor with pkg_xxx any information about ports can be found.
Questions:
- What did I do wrong in the process?.
You used the wrong tag.
If you want the exact version of the ports tree that shipped with 6.2 the
correct tag to use is "RELEASE_6_2_0". "RELENG_6_2_0_RELEASE" is the tag
used for the base system corresponding to 6.2-RELEASE.
- Is cvsup for installation of RELEASE 6.2 ports collection a bad idea
anyway (technically) ?
If you actually want the ports tree as it was when 6.2-RELEASE was made,
then it is not a bad idea. Most of the time one would like a more updated
version of the ports tree though.
Proces:
- I use the recently installed cvsup-without-gui, installed from ports
- I deleted all entries and maps in/under /usr/ports (as recommended in the
Handbook)
- I modified the ports-supfile in usr/share/examples/cvsup and copied it to
portswj-supfile in the same map (not good practice I know now)
The settings in the -supfile where:
*default host=cvsup15.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_6_2_0_RELEASE (the handbook suggests
that this is a valid tag for ports)
I doubt the handbook suggests that. If it does it is wrong.
*default delete use-rel-suffix (I could not find a meaning for this in
the books, anyone can tell me please?)
Read the cvsup(1) manpage.
*default compress
ports-all
- I ran: cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile
The conversation looked OK, no error messages but also no scrolling list of
files
There is a logfile in /var/db/sup ports-all, something like
.cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the
ports collection that looks normal and every record shows also
RELENG_6_2_0_RELEASE.
One idiotic question on the top of his troubles.
According to the disclaimer posted on the ports web-site. The ports tree
supports only Stable and Current version of the OS.
Since Release is sort of more stable than the Stable I wonder if there
is a frozen ports three with frozen packages for 6.2 release?
Personally, I was always following stable branch which is moving target
as you know. One needs to portsnap fetch and update ports three
before every build up and also portupgrade has to be done fairly regularly.
Personally, I could not care less for the newest versions of the
programs as long as the old one are stable so for me staying with
release would be perfectly OK.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
On Sat, 05 Jan 2008 22:31:29 "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: > Rudy wrote: > > Michael Lednev wrote: > >> Hello. > >> > >> Is there any way to compact /var/db/portsnap other than deleting > >> it and doing postsnap fetch? Not really. /var/db/portsnap/files contains one file for each port, gzipped. Mine's about 70MB with indices, containing a ports tree of some 450MB. I guess it depends whether that much space is more precious to you than the time and bandwidth to fetch and then extract the whole tree afresh? > > I don't like portsnap -- granted I've never typed the portsnap > > command in my 10 years of FreeBSD use. I use cvsup! I didn't like it much until I'd tried it, either :) c[v]sup works fine too of course, so trimming some discussion of that .. [..] > > If you don't have cvsup installed, run this command: # pkg_add -r > > cvsup-without-gui > > It is better to use all ports or all packages so either do: Why do you say that? Do you know of unresolved issues regarding the interactions of port versus package installations? Any references? > cd /usr/ports/net/cvsup-without-gui > make install clean > > or after doing the above do a pkg_delete -a (assuming that your > working with a clean machine [no ports/packages instaleld except cvsup] Why wouldn't pkg_delete -a remove your just-installed cvsup-without-gui? > > For more info on the supfile, look at this file on your FreeBSD > > machine: /usr/share/examples/cvsup/ports-supfile > > > > Preferring cvsup to portsnap is kinda like preferring vim over > > emacs... It's a holy war and the vi/cvsup side uses less disk > > space. > > Actually it is not like that at all.. cvsup/csup is the officially > preferred method and any other method is a short cut of some kind... Please provide a reference URL to 'official' support of this claim? > many of them have very subtle issues that the typical end-user should > not notice but should be aware of... Issues such as? And what other alternatives to c*sup and portsnap exist for ports tree management? ooroo, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: > Hi > > > > Upon reading chapters of the Handbook about the Ports collection and CVSup, > I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using > the wrong tag (tag=.), I erroneously but successfully installed the CURRENT > version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the > sake of learning and training myself I did not. > > > > Problem: > > - I ran CVSup again with the correct tag but though everything in the > process looked normal, the map usr/ports remains empty and nor with whereis > nor with pkg_xxx any information about ports can be found. > > Questions: > > - What did I do wrong in the process?. You used the wrong tag. If you want the exact version of the ports tree that shipped with 6.2 the correct tag to use is "RELEASE_6_2_0". "RELENG_6_2_0_RELEASE" is the tag used for the base system corresponding to 6.2-RELEASE. > > - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea > anyway (technically) ? If you actually want the ports tree as it was when 6.2-RELEASE was made, then it is not a bad idea. Most of the time one would like a more updated version of the ports tree though. > > > > Proces: > > - I use the recently installed cvsup-without-gui, installed from ports > > - I deleted all entries and maps in/under /usr/ports (as recommended in the > Handbook) > > > > - I modified the ports-supfile in usr/share/examples/cvsup and copied it to > portswj-supfile in the same map (not good practice I know now) > > The settings in the -supfile where: > > *default host=cvsup15.FreeBSD.org > > *default base=/var/db > > *default prefix=/usr > > *default release=cvs tag=RELENG_6_2_0_RELEASE (the handbook suggests > that this is a valid tag for ports) I doubt the handbook suggests that. If it does it is wrong. > > *default delete use-rel-suffix (I could not find a meaning for this in > the books, anyone can tell me please?) Read the cvsup(1) manpage. > > *default compress > > ports-all > > > > - I ran: cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile > > The conversation looked OK, no error messages but also no scrolling list of > files > > There is a logfile in /var/db/sup ports-all, something like > .cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the > ports collection that looks normal and every record shows also > RELENG_6_2_0_RELEASE. > > > -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
port collection RELEASE6.2 lost after reinstall with CVSUP
Hi Upon reading chapters of the Handbook about the Ports collection and CVSup, I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using the wrong tag (tag=.), I erroneously but successfully installed the CURRENT version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the sake of learning and training myself I did not. Problem: - I ran CVSup again with the correct tag but though everything in the process looked normal, the map usr/ports remains empty and nor with whereis nor with pkg_xxx any information about ports can be found. Questions: - What did I do wrong in the process?. - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea anyway (technically) ? Proces: - I use the recently installed cvsup-without-gui, installed from ports - I deleted all entries and maps in/under /usr/ports (as recommended in the Handbook) - I modified the ports-supfile in usr/share/examples/cvsup and copied it to portswj-supfile in the same map (not good practice I know now) The settings in the -supfile where: *default host=cvsup15.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6_2_0_RELEASE (the handbook suggests that this is a valid tag for ports) *default delete use-rel-suffix (I could not find a meaning for this in the books, anyone can tell me please?) *default compress ports-all - I ran: cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile The conversation looked OK, no error messages but also no scrolling list of files There is a logfile in /var/db/sup ports-all, something like .cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the ports collection that looks normal and every record shows also RELENG_6_2_0_RELEASE. Regards, Walter Jansen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
Hello, Rudy. On 6 января 2008 г., 5:43:54 you wrote: >> Is there any way to compact /var/db/portsnap other than deleting it >> and doing postsnap fetch? R> I don't like portsnap -- granted I've never typed the portsnap R> command in my 10 years of FreeBSD R> use. I use cvsup! Probably because portsnap is about 2 yo. The question is not "How to update my ports tree", its "How to compact /var/db/portsnap". Thanks for the answer anyway. PS try csup. This is cvsup clone written in C. Comes with the base system. -- Best regards, Michael mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rudy wrote: > Michael Lednev wrote: >> Hello. >> >> Is there any way to compact /var/db/portsnap other than deleting >> it and doing postsnap fetch? >> > > I don't like portsnap -- granted I've never typed the portsnap > command in my 10 years of FreeBSD use. I use cvsup! > > More info: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html > > > QUick HOW-TO Make a file called /usr/src/ports-supfile Your better off using /usr/share/examples/cvsup/ports-supfile because it is pre-debuggeg... also even though I don't use it because the nearest cvsup mirror is 5 miles away is install fastest_cvsup to find the fastest host. > - > #/usr/src/ports-supfile *default host=cvsup8.FreeBSD.org *default > base=/var/db *default prefix=/usr *default release=cvs tag=. > *default delete use-rel-suffix *default compress ports-all > - > > Then, run this command: cvsup /usr/src/ports-supfile Note if your not going to use the local cvs repository method I use then you should use csup not cvsup because it comes with the base system (the semantics are identical to those of cvsup) [the only difference is csup can't handle "raw" cvs commands thus the cvs-supfile doesn't work with it] Make an alias for this that way when you update your sources you won't lose the host settings if /usr/share/examples/cvsup gets overwritten... for example my alias is: (I keep a complete local copy of the cvs repo so I use cvs-supfile instead of ports or standard [note 1]): alias cvsup "cvsup -h cvsup9.us.freebsd.org /usr/share/examples/cvs-supfile" > > If you don't have cvsup installed, run this command: # pkg_add -r > cvsup-without-gui It is better to use all ports or all packages so either do: cd /usr/ports/net/cvsup-without-gui make install clean or after doing the above do a pkg_delete -a (assuming that your working with a clean machine [no ports/packages instaleld except cvsup] > > For more info on the supfile, look at this file on your FreeBSD > machine: /usr/share/examples/cvsup/ports-supfile > > Preferring cvsup to portsnap is kinda like preferring vim over > emacs... It's a holy war and the vi/cvsup side uses less disk > space. Actually it is not like that at all.. cvsup/csup is the officially preferred method and any other method is a short cut of some kind... many of them have very subtle issues that the typical end-user should not notice but should be aware of... > > - Rudy ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions To > unsubscribe, send any mail to > "[EMAIL PROTECTED]" > Notes: 1. I keep a local cvs repository because unlike cvsup/csup straight cvs will not over write locally modified files (it will do it's best to merge in newer changes while persevering your local ones) - -- Aryeh M. Friedman FloSoft Systems, Java Developer Tools http://www.flosoft-systems.com Developer, not business, friendly. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHgEuRjRvRjGmHRgQRAj/4AJ9rAd/rSZOPBDgtMfDjMzBEf8OCgQCgslO6 EPONuz7Tj7TMPQuvDhCHCdI= =lxH2 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[HOW-TO] cvsup for ports -- Re: compact portsnap db
Michael Lednev wrote: Hello. Is there any way to compact /var/db/portsnap other than deleting it and doing postsnap fetch? I don't like portsnap -- granted I've never typed the portsnap command in my 10 years of FreeBSD use. I use cvsup! More info: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html QUick HOW-TO Make a file called /usr/src/ports-supfile - #/usr/src/ports-supfile *default host=cvsup8.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all - Then, run this command: cvsup /usr/src/ports-supfile If you don't have cvsup installed, run this command: # pkg_add -r cvsup-without-gui For more info on the supfile, look at this file on your FreeBSD machine: /usr/share/examples/cvsup/ports-supfile Preferring cvsup to portsnap is kinda like preferring vim over emacs... It's a holy war and the vi/cvsup side uses less disk space. - Rudy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup not getting 'everything' with standard-supfile?
>>>>> "SF" == Steve Franks writes: SF> I see folks talking about building snd_hda on 6.2, but when I cvsup, SF> /usr/src/sys/modules/sound/driver/hda doesn't exist. I'm using an SF> unmodified (except for the url) standard-supfile, which has "src-all" SF> in big letters uncommented at the top, so I find the lack of anything SF> a bit surprising - any ideas? snd_hda don't present in RELENG_6_2 -- Max N. Boyarov pgpOKQD93J0n3.pgp Description: PGP signature
Re: cvsup not getting 'everything' with standard-supfile?
Steve Franks wrote: > I see folks talking about building snd_hda on 6.2, but when I cvsup, > /usr/src/sys/modules/sound/driver/hda doesn't exist. I'm using an > unmodified (except for the url) standard-supfile, which has "src-all" > in big letters uncommented at the top, so I find the lack of anything > a bit surprising - any ideas? > > Steve > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > The standard supfile will only get you to 6.2-RELEASE-p9 The snd_hda driver is only present in 6.2-STABLE (use stable-supfile) and, of course 6.3-RC and 7.0-BETA If you do not wish to move to 6.2-STABLE and make buildworld and all this, you may wish to get the ready module for 6.2-RELEASE and load it via /boot/loader.conf More instructions at this older post: http://lists.freebsd.org/pipermail/freebsd-questions/2007-August/155261.html Manolis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup not getting 'everything' with standard-supfile?
On Wed, Dec 19, 2007 at 03:43:21PM -0700, Steve Franks wrote: > I see folks talking about building snd_hda on 6.2, but when I cvsup, > /usr/src/sys/modules/sound/driver/hda doesn't exist. I'm using an > unmodified (except for the url) standard-supfile, which has "src-all" > in big letters uncommented at the top, so I find the lack of anything > a bit surprising - any ideas? > > Steve > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" That's odd, I usually get everything in one go (I usually just copy the example files from /usr/share/examples/cvsup - ports-supfile and stable-supfile), chnage the mirror where it gets the source from, and csup it. Is it possible the site you cvsup from doesn't have all the code (not synchronized properly) or that there's some screwup setting on your standard supfile? I'm just throwing ideas out into the wind, but those two possibilies stike me as a possible reason at the time of this writing. Russell Doucette ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup not getting 'everything' with standard-supfile?
I see folks talking about building snd_hda on 6.2, but when I cvsup, /usr/src/sys/modules/sound/driver/hda doesn't exist. I'm using an unmodified (except for the url) standard-supfile, which has "src-all" in big letters uncommented at the top, so I find the lack of anything a bit surprising - any ideas? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup-mirror: clients never get past 'running' (server 100% idle)
Hugo Silva wrote: Hello, I've set up a local cvsup mirror for a freebsd server farm but I'm having some trouble making it work. I went with all the defaults on the install, only skipping gnats www and mail. The initial update went well, took awhile but I have all files in place now. However, when connecting to get src or ports, it'll never get past /usr/src# make update -- >>> Running /usr/bin/csup -- Parsing supfile "/root/cvsup/standard-supfile" Connecting to 172.16.100.22 Connected to 172.16.100.22 Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running 73163 3002 1 440 7592K 3812K select 0 0:02 0.00% cvsupd It just stays idle forever... 3002 73163 0.0 0.2 7592 3812 ?? IJ7:07PM 0:01.58 /usr/local/sbin/cvsupd -e -C 10 -l @daemon -b /usr/local/etc/cvsup -s sup.client FreeBSD 7.0-BETA4/amd64, cvsupd is running inside a jail, on ZFS. What am I missing ? Regards, Hugo Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 16479 172.16.100.22.5999 172.16.100.92.61642 ESTABLISHED Send-Q is 16479 on the server as soon as the client gets to the "Running" phase (and stalls), the client sees: tcp4 0 0 172.16.100.92.61642172.16.100.22.5999 ESTABLISHED I'm baffled and don't have much free time to chase this down right now, does this ring a bell to anyone at all ? No firewalls are running on either host, and they're in the same subnet.. Best regards, Hugo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup-mirror: clients never get past 'running' (server 100% idle)
Hello, I've set up a local cvsup mirror for a freebsd server farm but I'm having some trouble making it work. I went with all the defaults on the install, only skipping gnats www and mail. The initial update went well, took awhile but I have all files in place now. However, when connecting to get src or ports, it'll never get past /usr/src# make update -- >>> Running /usr/bin/csup -- Parsing supfile "/root/cvsup/standard-supfile" Connecting to 172.16.100.22 Connected to 172.16.100.22 Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running 73163 3002 1 440 7592K 3812K select 0 0:02 0.00% cvsupd It just stays idle forever... 3002 73163 0.0 0.2 7592 3812 ?? IJ7:07PM 0:01.58 /usr/local/sbin/cvsupd -e -C 10 -l @daemon -b /usr/local/etc/cvsup -s sup.client FreeBSD 7.0-BETA4/amd64, cvsupd is running inside a jail, on ZFS. What am I missing ? Regards, Hugo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup question
On Tue, 11 Dec 2007 17:34:19 -0500 "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Simon Gao wrote: > > Hi, > > > > I wonder if just having port-all is enough in cvsupfile as follow. > > If I just want to keep ports tree up to date, do I really need to > > have '"src-all"? > > ... > Yes and oyu don't need tag=. also since that is the default value And that's yes to: "port-all is enough", not yes to "do I really need to have src-all?" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Gao wrote: > Hi, > > I wonder if just having port-all is enough in cvsupfile as follow. > If I just want to keep ports tree up to date, do I really need to > have '"src-all"? > > > *default host=cvsup9.freebsd.org *default base=/usr *default > prefix=/usr *default release=cvs tag=RELENG_4_11 *default delete > use-rel-suffix compress # src-all ports-all tag=. > Yes and oyu don't need tag=. also since that is the default value -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXxBrzIOMjAek4JIRAhLPAJ4wmwl7Vzqv7F29Q9QOY+F3+wPiPACfbyDf fJ7e1hG8+cHRNpdy8Esg5Wc= =D014 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CVSup question
Hi, I wonder if just having port-all is enough in cvsupfile as follow. If I just want to keep ports tree up to date, do I really need to have '"src-all"? *default host=cvsup9.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4_11 *default delete use-rel-suffix compress # src-all ports-all tag=. thanks, Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: urgent: undoing a cvsup update
Aryeh Friedman wrote: I just cvsuped the latest sources and they break many programs named and most X11-apps comes to mind immediately Well how do I backout of the this keep in miond I use cvs-supfile to populate a local repo and did a rm -rf /usr/obj /usr/src thinking that might clear stuff up but it didn't As far I can tell I can track the main issue to the new malloc stuff All programs that are borken just hang immediatlely after invocation Please, Aryeh. You've been using freebsd for 10 years and asking a flood of questions here. You should know by now to at least provide the basic info: uname -a error messages cvsup file the commands you entered to wind up in this unfortunate situation Since you of course have proper backups, just pop in a CD and do a rescue install. Asking questions like the above will get you nowhere. Erik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
urgent: undoing a cvsup update
I just cvsuped the latest sources and they break many programs named and most X11-apps comes to mind immediately Well how do I backout of the this keep in miond I use cvs-supfile to populate a local repo and did a rm -rf /usr/obj /usr/src thinking that might clear stuff up but it didn't As far I can tell I can track the main issue to the new malloc stuff All programs that are borken just hang immediatlely after invocation ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
