Re: Cronjob Cvsup -> What?
Hello Matthew, Thanks for an outstanding piece of documentation. It resolves a number of concerns I had and convinced me to move from portsnap where I discovered an apparent bug that gave me security concerns. More specifically I manually edited /usr/ports/UPDATING and portsnap did not recognise the change and download a proper copy. The only downside with svn seems to be the 728 MB footprint. Cheers ... Mark On Sun, 27 Jan 2013 05:46:23 Matthew Seaman wrote: > On 27/01/2013 08:35, Zyumbilev, Peter wrote: > > Last 10 years I am using cvsup. Any good guide for the transition to > > subversion ? > > Most of the guides around freebsd.org are aimed at developers who will > be using SVN read-write. For simple read-only use (ie. not checking > anything into the repository) the following should suffice: > > 0) Install svn > > It isn't part of the base system, and it has too many external > dependencies with different licensing terms for it to be bought > in easily. There's been some discussion about this, but it hasn't > happened yet. If it did, the imported version would be fairly > minimal, and anyone wanting to use it for serious development > would probably just grab the ports version anyhow. > > If all you want to do is pull down a copy of the sources then you > can turn off most of the options to reduce the fairly large > dependency tree to something more manageable: > > BDB=off: Berkeley Database > BOOK=off: Install the Subversion Book > ENHANCED_KEYWORD=on: Enhanced svn:keyword support > FREEBSD_TEMPLATE=on: FreeBSD Project log template > GNOME_KEYRING=off: Build with GNOME Keyring auth support > KDE_KWALLET=off: Build with KDE KWallet auth support > MAINTAINER_DEBUG=off: Build debug version > MOD_DAV_SVN=off: mod_dav_svn module for Apache 2.X > MOD_DONTDOTHAT=off: mod_dontdothat for Apache 2.X > NEON=off: WebDAV/Delta-V repo access module (neon) > P4_STYLE_MARKERS=off: Perforce-style conflict markers > SASL=off: SASL support > SERF=on: WebDAV/Delta-V repo access module (serf) > STATIC=off: Build static version (no shared libs) > SVNAUTHZ_VALIDATE=off: install svnauthz-validate > SVNMUCC=off: Install Multiple URL Command Client > SVNSERVE_WRAPPER=off: Enable svnserve wrapper > TEST=off: Run subversion test suite > > There is the new devel/subversion-static port which does all that, > and compiles subversion with static linkage so it has *no* runtime > dependencies on anything else. The disadvantage here is that if > there is, say, a security hole discovered in the one of the > libraries subversion links against, you won't secure the > statically linked copy of subversion simply by updating to a fixed > version of the shlib. subversion-static is really only intended > for providing a one-off binary package that people can download > and install in order to bootstrap a more standard FreeBSD > environment. > > 1) Choose a SVN mirror close to you. Currently there are two choices: > > svn0.us-west.FreeBSD.org -- Western USA > svn0.us-east.FreeBSD.org -- Eastern USA > > Use whichever one gives you best performance. Certainly from > Europe at the moment us-east seems to be the best choice. > > The number of SVN mirrors and their global coverage should increase > over time, but it will never need as many servers as the old cvsup > network. > > The canonical list of SVN mirrors is here: > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn-mirrors.html > > 2) Choose a protocol for access the SVN servers. Your choices in > order of preference are > > svn:// > https:// > http:// > > Use svn:// for best performance. If you're concerned about MITM > attacks injecting trojans into the FreeBSD sources, then use > https and be sure to verify the certificate hashes on first > connection. Otherwise, if you're stuck behind a restrictive > firewall, use http:// > > 3) Choose which branch you want to mirror. It's relatively easy to > switch between branches and doesn't involve downloading the entire > contents of /usr/src all over again if you change your mind. > However right now, the viable choices are > > head --- Current, the bleeding edge, really only suitable > for development purposes > > stable/9 --- 9-STABLE Still a rapidly changing development > branch, but not quite so close to the edge, and > with less bleeding involved. > > stable/8 --- 8-STABLE Ditto. > > releng/9.1 --- 9.1-RELEASE This tracks any security patches to > version 9.1. However, in this case you would be > better advised to use freebsd-update(
Re: BSD Magazine PDFs
Hello, I've been downloading BSD Mag since it first came out and your list is identical to mine. Cheers .. Marek On Thursday 17 February 2011 21:40:37 Xn Nooby wrote: > Is there a place where I can download all the BSD Magazine PDF back > issues? I have got a lot of them from the BSD Magazine site, and a > few other sites, but I think I am missing some. For example, I only > have 2 from 2008, and 4 from 2009. I was able to get most of them > from http://bsdmag.org > > I renamed them to sort properly, the ones I have are: > > BSD_2008_01.pdf > BSD_2008_02.pdf > > BSD_2009_01.pdf > BSD_2009_02.pdf > BSD_2009_03.pdf > BSD_2009_04.pdf > > BSD_2010_01.pdf > BSD_2010_02.pdf > BSD_2010_03.pdf > BSD_2010_04.pdf > BSD_2010_05.pdf > BSD_2010_06.pdf > BSD_2010_07.pdf > BSD_2010_08.pdf > BSD_2010_09.pdf > BSD_2010_10.pdf > BSD_2010_11.pdf > > BSD_2011_01.pdf > BSD_2011_02.pdf > > I would like to get the others, if there are any, and it is legal. Or > perhaps I have all the ones available. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Not able to compile GENERIC kernel
On Sunday, 20 September 2009 12:55:44 Giorgos Keramidas wrote: > On Sun, 20 Sep 2009 11:15:15 -0400, mfv wrote: > > Hello, > > > > After rebuilding FreeBSD for many years I am not able to build a > > GENERIC kernel for the last few days. It always stops when > > compiling acpi. > > > > The source code is up to date for 7 -STABLE for i386 on a amd64 > > cpu. I have always been able to recompile a GENERIC kernel since > > release 5.1 and do not know what I am doing wrong. > > > > Any help would be greatly appreciated. > > > > With thanks. > > > > Marek > > > > The following is the tail end of "make buildkernel": > > > > cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 - > > nostdinc -I > > /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica > > -DHAVE_KERNEL_OPTION_ HEADERS -include > > /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/a ltq > > -finline-limit=8000 --param inline-unit-growth=100 --param large- > > function-growth=1000 -fno-common -g -I/usr/obj/usr/src/sys/GENERIC > > -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx > > -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 - ffreestanding -Wall > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmi > > ssing-prototypes -Wpointer- arith -Winline -Wcast-qual -Wundef > > -Wno-pointer-sign -fformat-extensions -c > > /usr/src/sys/modules/acpi/acpi/../../../i386/acpica/acpi _machdep.c > > @ ->/usr/src/sys > > ln: @/sys: Operation not permitted > > *** Error code 1 > > Can you wipe our /usr/obj and start with a clean object tree? You > may also have stale build artifacts in /usr/src so something like > this might be a good idea: > > # rm -fr /usr/obj/usr > # cd /usr/src > # make cleandir ; make cleandir > Thanks to all for your comments and insights. I was finally able to compile a GENERIC kernel by performing radical surgery: 1. cd /usr/src/sys 2. rm -r * 3. Update source tree using csup 4. cd /usr/src 5. make cleanworld 6. make buildkernel I did this over three days. On the third day it finally worked. My suspicion is that for some reason my source code was scrambled. Thanks again for your comments. Using them as a starting point I discovered cleanworld and have a better understanding of the compile process. Cheers... Marek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Not able to compile GENERIC kernel
Hello, After rebuilding FreeBSD for many years I am not able to build a GENERIC kernel for the last few days. It always stops when compiling acpi. The source code is up to date for 7 -STABLE for i386 on a amd64 cpu. I have always been able to recompile a GENERIC kernel since release 5.1 and do not know what I am doing wrong. Any help would be greatly appreciated. With thanks. Marek The following is the tail end of "make buildkernel": cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 - nostdinc -I /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica -DHAVE_KERNEL_OPTION_ HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/a ltq -finline-limit=8000 --param inline-unit-growth=100 --param large- function-growth=1000 -fno-common -g -I/usr/obj/usr/src/sys/GENERIC -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 - ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmi ssing-prototypes -Wpointer- arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/acpi/acpi/../../../i386/acpica/acpi _machdep.c @ ->/usr/src/sys ln: @/sys: Operation not permitted *** Error code 1 Stop in /usr/src/sys/modules/acpi/acpi. *** Error code 1 Stop in /usr/src/sys/modules/acpi. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [root] /usr/src # ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Questions on portmaster
On Wednesday, 1 July 2009 02:02:47 Manish Jain wrote: > Hi, > > I am using portmaster on FreeBSD-7.2 to keep my ports up to date. When > there are multiple ports to be updated, portmaster will fork off child > processes. Does each child start 'make fetch' in the background ? I ask > this because the parent process attached to the console reports very low > data transfer rates (in the range of 0.7 to 4.0 kBps, while normally I > get 30 to 35 kBps). > > Further, how can portmaster be tuned to automatically ignore ports which > are actually marked as IGNORE in the port directory ? This is not > covered in the manpage. > > While doing portmaster -a, I have only managed to stop portmaster from > building exactly one port specified with the -x option. Can I get to > stop multiple ports from being built ? Is there regular expression > support for the -x option ? > > Thanks for any help. Hello Manish, Regarding your last point about excluding particular ports I always thought that it would be convenient to have a section in /usr/local/etc/portmaster.rc and/or $HOME/.portmasterrc to identify these particular ports. I prefer to have all this information in one place rather than scattered over many subdirectories. I had the same problem with trying to have multiple instances of "-x" but gave up and used +IGNOREME instead. Some time ago I succeeded with a regular expression but it became overly complicated if more than two ports were to be excluded. Nevertheless, I use portmaster daily and am very pleased with it. With thanks to Doug Barton. Cheers... Marek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portaudit strange behavior.
On Wednesday, 1 July 2009 02:02:47 Arek Czereszewski wrote:
> Hi,
>
> On all my servers I have portaudit version 0.5.13
> If I try update audit database (by hand or from periodic script)
> I have:
>
> # portaudit -Fd
> auditfile.tbz 100% of 53 kB 39 kBps
> portaudit: Database too old.
> Old database restored.
> portaudit: Download failed.
> #
>
> When I change
>
> ${portaudit_sites="http://portaudit.FreeBSD.org/"}
> to
> ${portaudit_sites="http://www.FreeBSD.org/ports/"}
> Like was in 0.5.12
> # portaudit -Fd
> auditfile.tbz 100% of 56 kB 34 kBps
> New database installed.
> Database created: Wed Jul 1 07:40:02 CEST 2009
> Update work fine.
>
> Anyone have behavior like I have?
>
> regards
> Arek
Hello Arek,
I've had the same problem for the last few days. Thanks for a temporary
solution.
Marek
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrading installed ports: time to do it ?
On Monday, 22 June 2009 16:48:02 RW wrote:
> On Mon, 22 Jun 2009 20:58:41 +0100
>
> Chris Whitehouse wrote:
> > I'll probably get flamed for this but since I've been using
> > ports-mgmt/portmanager I've almost forgotten
> > about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it
> > was. I've upgraded ports just by doing 'portmanager -u' over one or
> > two quite major changes and not had any problems that haven't been
> > down to an individual ports.
>
> You still need to read UPDATING, portmanager handles some of the
> issues automatically, but not all.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscr...@freebsd.org"
Hello,
Here is a perl hack I use to automatically read and parse UPDATING as part of
my daily upgrade routine. It is part of a larger set of five scripts which
use:
1. "csup" to update ports
2. "make index" to update the /usr/ports/INDEX
3. "pkg_version" to identify the ports that need upgrading
4. "portfetch" to download the tarballs
5. a script to display the relevant contents, if any, of UPDATING using the
hack shown below and the contents identified in step 3 above.
These five scripts are combined in a master script (csup-all) which I invoke
the first thing in the morning. After doing some other morning chores I then
run "portconfig -a -v" to set up any configuration settings prior to running
"portmaster -a -u". Everything is automatic except for the configuration.
Here is the perl hack. It can be improved by comparing the ports that need to
be updated (step 3) with the ports specified within UPDATING (step 5). The
embedded ansi codes will work with the default FreeBSD console settings,
otherwise they can be removed.
#!/usr/bin/perl
#
# file:csup-update.pl
#
# created: 2006-07-16
#
# purpose: To review update notes in /usr/ports/UPDATING
# This program will only display those notes issued
# since last csup
#
# algorithm: Each line of the file /usr/ports/UPDATING is scanned and if
# it finds a date in the form ^mmdd$ the date is assigned
# to the variable $date. Otherwise all non-date lines are printed
# to STDOUT. As soon as this program finds a date older than the
# last update this program quits and prints an appropriate closing
# message.
#
unless ( open ( MYFILE, "/usr/ports/UPDATING" ) ) {
die ("Cannot open input file /usr/ports/UPDATING.\n") ;
}
unless ( open ( LASTUPDATE, "/root/bin/csup-lastupdate.txt" ) ) {
die ("Cannot open file csup-lastupdate.txt.\n") ;
}
$eof = '' ;
$date = $lastupdate = ;
$line = ;
$count = 0 ;
while ( $line ne $eof ) {
if ( $line =~ /^2\d{7}/ ) {
$date = $line ;
$date =~ tr/://d ;
$count++ ;
}
if ( ( $date - $lastupdate ) >= 0 ) {
if ( $line =~ /^2\d{7}/ ) {
print ("^[[32m$line^[[0m") ;
} else {
print ("^[[0m$line") ;
}
$line = ;
$date = $lastupdate ;
} else {
$count-- ;
if ( $count == 0 ) {
print ( "^[[36mThere are no updates to review. ") ;
} elsif ( $count == 1 ) {
print ( "^[[36mThere is only one update to review. ") ;
} else {
print ( "^[[36mThere are $count updates to review. ") ;
}
chop ( $lastupdate ) ;
print ( "The last run of csup was on $lastupdate.^[[0m\n\n" ) ;
exit ;
}
}
# EoF
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Reading warnings when installing multiple ports
On Tuesday 12 May 2009 13:53:35 Mel Flynn wrote: > On Monday 11 May 2009 15:21:24 Jerry McAllister wrote: > > But, I very often wish there was a convenient way to see some of those > > messages and especially messages about things one has to do during > > the install, such as manually installing something or getting some > > license thing handled, before I start the port install. > > > > Sometimes I get a question in the middle of an install that I do not > > know how to answer and it is an awfully inconvenient time to have > > to start scrounging for information.Having a commannd that > > would display all those things and maybe some related information > > or pointers to information for making an intelligent response - before > > starting the make - would be very helpful. > > Do you have specific examples? Cause I can't think of anything that falls > under your description. Hello All, I had a recent experience with editors/openoffice.org-2. Based on past experience I know that the compile would take a few hours. I started make and left to do some chores. When I returned I discovered that the program had aborted as I did not have java installed and had to download a patch from the Sun website. I agree with Jerry about lining up all the necessary ducks so that an upgrade does not need constant attention. Using "portfetch -a -v" and "portconfig -a -v" followed by "portmaster -a -u -t -v" does most of the work but some configure screens still pop up. Cheers... Marek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
