Re: diff - FAQ5 missing info on updating current source tree

On Fri, May 06, 2016 at 12:58:33AM -0400, Gabriel Guzman wrote: > FAQ5 is missing a sentence: fixed, thanks.

diff - FAQ5 missing info on updating current source tree

FAQ5 is missing a sentence: Index: faq5.html === RCS file: /cvs/www/faq/faq5.html,v retrieving revision 1.267 diff -u -p -u -r1.267 faq5.html --- faq5.html 1 May 2016 16:59:24 - 1.267 +++ faq5.html 6 May 2016 04:54:43 -

Re: Source tree

Ted Unangst tedunangst.com> writes: [...] > Use cd-src.tar.gz for all paches. > > Thanks a lot, Ted. Olivier Debré

Re: Source tree

ke' step for errata > 001. I'll take care of that when I'll have a clear understanding of > what's hereunder). > > I read errata 006 : > 'The "src.tar.gz" file on the source tree was created on the wrong day, > and does not match the 5.8 release b

Re: Source tree

ata > 001. I'll take care of that when I'll have a clear understanding of > what's hereunder). > > I read errata 006 : > 'The "src.tar.gz" file on the source tree was created on the wrong day, > and does not match the 5.8 release builds. A replacemen

Source tree

27;ll have a clear understanding of what's hereunder). I read errata 006 : 'The "src.tar.gz" file on the source tree was created on the wrong day, and does not match the 5.8 release builds. A replacement file is available in the 5.8 release directory with the name cd-src.tar.gz'

Re: Building a single driver in the source tree

On Sep 14, 2012, at 9:33 PM, Nick Holland wrote: > On 09/14/12 20:16, jordon wrote: >> I am having trouble getting a Hifn7751 to work in an old Soekris box. I >> want to dig in and see if I can figure out what is going on but I am >> very new to this. From /usr/src/sys/dev/pci, I typed "make hi

Re: Building a single driver in the source tree

On 09/14/12 20:16, jordon wrote: > I am having trouble getting a Hifn7751 to work in an old Soekris box. I > want to dig in and see if I can figure out what is going on but I am > very new to this. From /usr/src/sys/dev/pci, I typed "make hifn7751", > but that leads to a lot of compiler errors.

Building a single driver in the source tree

I am having trouble getting a Hifn7751 to work in an old Soekris box. I want to dig in and see if I can figure out what is going on but I am very new to this. From /usr/src/sys/dev/pci, I typed "make hifn7751", but that leads to a lot of compiler errors. Is there some better way to do this or do

Re: Long delay updating xenocara source tree?

Hi, Jiri B wrote on Thu, Feb 09, 2012 at 07:52:44AM -0500: > Somebody suggested: >> find . -path '*CVS/Root' | xargs rm > Never ever! Well, certainly not when you are working in a mixed tree intentionally using different servers for different subdirectories. However, on a laptop i'm carrying a

Re: Long delay updating xenocara source tree?

Stuart Henderson wrote [2012-02-10 01:01+0100]: > On 2012-02-09, Steffen Daode Nurpmeso wrote: > > On the long run cvs(1) will die, and be replaced by Schily SCCS > > oh please don't, even as a joke. It's not that bad! It's from 1972, and only good things can come from 1972. > > And my daily do

Re: Long delay updating xenocara source tree?

On 02/09/12 12:54, Otto Moerbeek wrote: > On Thu, Feb 09, 2012 at 06:15:50PM +0100, Jan Stary wrote: > >> Replying to myself, > > [snip] > >> Things might change if (1) the cvsroot is remote (2) it is not >> the same for all files. I will try that next. >> >> Jan > > That last case (remo

Re: Long delay updating xenocara source tree?

On 2012-02-09, Steffen Daode Nurpmeso wrote: > On the long run cvs(1) will die, and be replaced by Schily SCCS oh please don't, even as a joke. anyway they are still releasing new versions of CVS. (they have to, they add new features with security holes...) > I like my patch. > And my daily dos

Re: Long delay updating xenocara source tree?

On Thu, Feb 09, 2012 at 08:16:25PM +0100, Jan Stary wrote: > On Feb 09 20:10:11, Jan Stary wrote: > > On Feb 09 18:54:45, Otto Moerbeek wrote: > > > BTW, AFAIK, cvs -d up does not write Root files. > > > > It does: > > > > cd /usr/src > > ftp -o - ftp://MIRROR/pub/OpenBSD/5.0/sys.tar.gz | tar xz

Re: Long delay updating xenocara source tree?

On Feb 09 20:10:11, Jan Stary wrote: > On Feb 09 18:54:45, Otto Moerbeek wrote: > > BTW, AFAIK, cvs -d up does not write Root files. > > It does: > > cd /usr/src > ftp -o - ftp://MIRROR/pub/OpenBSD/5.0/sys.tar.gz | tar xzpf > cd sys > find . -name Root > cvs -q -d MIRROR up > find . -name Root A

Re: Long delay updating xenocara source tree?

On Feb 09 18:54:45, Otto Moerbeek wrote: > BTW, AFAIK, cvs -d up does not write Root files. It does: cd /usr/src ftp -o - ftp://MIRROR/pub/OpenBSD/5.0/sys.tar.gz | tar xzpf cd sys find . -name Root cvs -q -d MIRROR up find . -name Root Jan

Re: Long delay updating xenocara source tree?

On Thu, Feb 09, 2012 at 06:15:50PM +0100, Jan Stary wrote: > Replying to myself, [snip] > Things might change if (1) the cvsroot is remote (2) it is not > the same for all files. I will try that next. > > Jan That last case (remote repo's and different Roots) is the actual case I have o

Re: Long delay updating xenocara source tree?

Replying to myself, On Feb 09 13:16:10, Jan Stary wrote: > Also, specifying 'cvs -d mirror' explicitly should get rid of this > problem then (right?), and speed things up, which it doesn't. it does; see below. > Or is the slowdown possibly due to the sheer *number* of CVS/Root > files that are c

Re: Long delay updating xenocara source tree?

> there aren't all that many repositories the size of ours out > there. My upload-traffic problem never occurred with binutils, which is also an *incredible* large repository, especially if you up -d. 10% there and my monthly traffic would exhaust, and no begging would help. > I have no idea, I j

Re: Long delay updating xenocara source tree?

1. On the long run cvs(1) will die, and be replaced by Schily SCCS (oh god, why does v6 not have any branch name info, too??), which will rule the world. Without having the need to use GNU autoconf at all, so that software will compile with make(1) not gmake(1). Make bootstrapping easy. Freedom! P

Re: Long delay updating xenocara source tree?

On Thu, Feb 09, 2012 at 07:52:44AM -0500, Jiri B wrote: > On Thu, Feb 09, 2012 at 01:16:10PM +0100, Jan Stary wrote: > > > +it maybe wise to issue a command sequence like the following: > > > + > > > + # cd /usr/src > > > + # find . -path '*CVS/Root' | xargs rm > > > + # cvs -d anon...@anoncvs.ca.

Re: Long delay updating xenocara source tree?

On Thu, Feb 09, 2012 at 01:16:10PM +0100, Jan Stary wrote: > > Otto Moerbeek wrote [2012-02-03 12:47+0100]: > > > I like to say that long delays I have seen when using cvs had to do > > > with multiple different values of CVS/Root files in my local tree. > > Otto, could you please elaborate? > Ho

Re: Long delay updating xenocara source tree?

On Thu, Feb 09, 2012 at 01:16:10PM +0100, Jan Stary wrote: > > +it maybe wise to issue a command sequence like the following: > > + > > + # cd /usr/src > > + # find . -path '*CVS/Root' | xargs rm > > + # cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd > > + > > Never ever! For example

Re: Long delay updating xenocara source tree?

> Otto Moerbeek wrote [2012-02-03 12:47+0100]: > > I like to say that long delays I have seen when using cvs had to do > > with multiple different values of CVS/Root files in my local tree. Otto, could you please elaborate? How does this slow down a cvs update? Is it really due to the fact that t

Re: Long delay updating xenocara source tree?

On Fri, Feb 03, 2012 at 12:47:02PM +0100, Otto Moerbeek wrote: > On Thu, Feb 02, 2012 at 03:15:29PM +0100, Steffen Daode Nurpmeso wrote: > > > Henning Brauer wrote: > > > there aren't all that many repositories the size of ours out there. > > > > That's true. > > But no Henning, i don't believe i

Re: Long delay updating xenocara source tree?

On Fri, 3 Feb 2012, Otto Moerbeek wrote: >On Thu, Feb 02, 2012 at 03:15:29PM +0100, Steffen Daode Nurpmeso wrote: > >> Henning Brauer wrote: >> > there aren't all that many repositories the size of ours out there. >> >> That's true. >> But no Henning, i don't believe it's that; >> you know, it's j

Re: Long delay updating xenocara source tree?

Otto Moerbeek wrote [2012-02-03 12:47+0100]: > I like to say that long delays I have seen when using cvs had to do > with multiple different values of CVS/Root files in my local tree. > > Those different entries can be created when doing a cvs up -d that > creates a new dir. If a cvs -d option is

Re: Long delay updating xenocara source tree?

On Thu, Feb 02, 2012 at 03:15:29PM +0100, Steffen Daode Nurpmeso wrote: > Henning Brauer wrote: > > there aren't all that many repositories the size of ours out there. > > That's true. > But no Henning, i don't believe it's that; > you know, it's just that i don't have anything to say, because >

Re: Long delay updating xenocara source tree?

Henning Brauer wrote: > there aren't all that many repositories the size of ours out there. That's true. But no Henning, i don't believe it's that; you know, it's just that i don't have anything to say, because i have no knowledge about the internals of cvs(1). I always thought of this as some ki

Re: Long delay updating xenocara source tree?

> > > > And even more speedy when I added a "scanfile /root/cvsync-scanfile" > > > > line in the "collection" part of the config file. > > > > > > You're running it as root? > > > > > > It makes a lot more sense to use a separate user. > > > > > > > I have been updating as root (the few times

Re: Long delay updating xenocara source tree?

On 2012/02/02 23:00, Brett wrote: > On Thu, 2 Feb 2012 11:40:22 + (UTC) > Stuart Henderson wrote: > > > On 2012-02-02, Brett wrote: > > > Yes, I also finally got around to trying cvsync because of this thread > > > and its a lot quicker. > > > > > > And even more speedy when I added a "sca

Re: Long delay updating xenocara source tree?

On Thu, 2 Feb 2012 11:40:22 + (UTC) Stuart Henderson wrote: > On 2012-02-02, Brett wrote: > > Yes, I also finally got around to trying cvsync because of this thread and > > its a lot quicker. > > > > And even more speedy when I added a "scanfile /root/cvsync-scanfile" line > > in the "col

Re: Long delay updating xenocara source tree?

On 2012-02-02, Brett wrote: > Yes, I also finally got around to trying cvsync because of this thread and > its a lot quicker. > > And even more speedy when I added a "scanfile /root/cvsync-scanfile" line in > the "collection" part of the config file. You're running it as root? It makes a lot

Re: Long delay updating xenocara source tree?

> > Dave Anderson wrote [2012-01-28 15:13+0100]: > > [.] > >> I haven't yet had a chance to look into how cvs works beyond > >> reading the man page, faq, etc. > > > > > > If you're doing your updates in such a regular manner, i think > > your best bet is cvsync(1), even if that means additional l

Re: Long delay updating xenocara source tree?

Hi Amit, Amit Kulkarni wrote [2012-02-01 00:57+0100]: > this motivated me to use cvsync from anoncvs and use a > CVSROOT=/home/amit/MYLOCALREPO to update from cvs. Much much faster > and while initial checkout from cvsync takes 5-10 hrs Yes, that's a real pity. I think it would be great if tarbal

Re: Long delay updating xenocara source tree?

On Sat, Jan 28, 2012 at 8:43 AM, Steffen Daode Nurpmeso wrote: > Hey, > > Dave Anderson wrote [2012-01-28 15:13+0100]: > [.] >> I haven't yet had a chance to look into how cvs works beyond >> reading the man page, faq, etc. > > Also true for me. > >> >> I've run into this problem perhaps a dozen t

Re: Long delay updating xenocara source tree?

2012/1/31 Dave Anderson : > > I do have a slowish ADSL link (384Kbps/1536Kbps) which would limit me to > very roughly 1MB/min outbound, so I took advice to use '-z 9' to > compress data and that reduced the total time for a xenocara source tree > update from about 11

Re: Long delay updating xenocara source tree?

esults >will vary, but not to nine hours, unless you are using dialup. :) I do have a slowish ADSL link (384Kbps/1536Kbps) which would limit me to very roughly 1MB/min outbound, so I took advice to use '-z 9' to compress data and that reduced the total time for a xenocara source tree

Re: Long delay updating xenocara source tree?

* Steffen Daode Nurpmeso [2012-01-28 15:44]: > I've noted a lot of upload network traffic when doing 'cvs up' > on OpenBSD repos; i.e., before anything else happened about > ~70 MB (www) and ~150 MB (src) *upstream* traffic were produced, > and it took more than an hour before the download of data

Re: Long delay updating xenocara source tree?

On 01/28/12 09:12, Dave Anderson wrote: > Thanks for the info. I've been using -Pd because > says to use them; I haven't yet > had a chance to look into how cvs works beyond reading the man page, > faq, etc. and please continue to use them. -Pd is the RIGHT w

Re: Long delay updating xenocara source tree?

21 EST: when trying to update the xenocara source tree there is a >> very long (perhaps infinite) delay between issuing the 'cvs ...' command >> and the start of any visible activity. In this most recent case the >> delay was about 9 hours. Updating the src and ports

Re: Long delay updating xenocara source tree?

Hey, Dave Anderson wrote [2012-01-28 15:13+0100]: [.] > I haven't yet had a chance to look into how cvs works beyond > reading the man page, faq, etc. Also true for me. > >> I've run into this problem perhaps a dozen times over the past several > >> months [.] I've noted a lot of upload network

Re: Long delay updating xenocara source tree?

ng a system built from source updated at about 14:30 >> 2012/1/21 EST: when trying to update the xenocara source tree there is a >> very long (perhaps infinite) delay between issuing the 'cvs ...' command >> and the start of any visible activity. In this most recent c

Re: Long delay updating xenocara source tree?

EST: when trying to update the xenocara source tree there is a > very long (perhaps infinite) delay between issuing the 'cvs ...' command > and the start of any visible activity. In this most recent case the > delay was about 9 hours. Updating the src and ports source trees at

Re: Long delay updating xenocara source tree?

EST: when trying to update the xenocara source tree there is a > very long (perhaps infinite) delay between issuing the 'cvs ...' command > and the start of any visible activity. B In this most recent case the > delay was about 9 hours. B Updating the src and ports source trees at

Long delay updating xenocara source tree?

I've run into this problem perhaps a dozen times over the past several months while running amd64-current, most recently at 15:53 2012/1/26 EST while running a system built from source updated at about 14:30 2012/1/21 EST: when trying to update the xenocara source tree there is a very

Re: compile 4.3 source tree on a 4.2 system

On Mon, Aug 11, 2008 at 8:48 PM, Jesus Sanchez <[EMAIL PROTECTED]> wrote: > can I compile a 4.3 source tree with also xenocara on a > 4.2 installation?? If you had read the FAQ, you might think this is the sort of question that would be answered there. You would be corre

Re: compile 4.3 source tree on a 4.2 system

On Tue, Aug 12, 2008 at 04:48:04AM +0200, Jesus Sanchez wrote: > can I compile a 4.3 source tree with also xenocara on a > 4.2 installation?? No. Why would you want to? Do a binary upgrade and then either patch or compile the stable tree.

compile 4.3 source tree on a 4.2 system

can I compile a 4.3 source tree with also xenocara on a 4.2 installation??

Re: More questions on building a release with a read only source tree

; NAS, and have each build machine build the release it needs. > > In my experience, this doesn't work at all if the build processes > writes into the src tree itself, and historically I have had to keep a All the openbsd releases are built using the same source tree shared via nf

Re: More questions on building a release with a read only source tree

On Sun, Feb 24, 2008 at 11:27:31PM -0800, Don Jackson wrote: > I would like "make release" to use [ a ] "read only source tree" I use lndir(1) to accomplish this. Check your source tree out somewhere else, and use lndir to make a 'copy' in /usr/src. Build from there, no other magic required.

Re: More questions on building a release with a read only source tree

On Mon, Feb 25, 2008 at 7:31 AM, Marco Peereboom <[EMAIL PROTECTED]> wrote: > You want to read lndir(1). This is extremely helpful advice, thank you! I used lndir to create an architecture specific copy of my source tree, and successfully built a release within it. So, this is one way t

Re: More questions on building a release with a read only source tree

needs. > > In my experience, this doesn't work at all if the build processes > writes into the src tree itself, and historically I have had to keep a > "virgin" source tree, and copy to each build machine, which takes a > long time, and it is really kind of a pai

Re: More questions on building a release with a read only source tree

../compile/GENERIC > # make clean && make depend && make > > or > Variation on above process: Read-only source tree > Sometimes, you may wish to ensure your /usr/src/sys directory > remains untouched. This can be done by using the following process: >

Re: More questions on building a release with a read only source tree

and historically I have had to keep a "virgin" source tree, and copy to each build machine, which takes a long time, and it is really kind of a pain to maintain the consistency of 3 copies. While choosing to avoid the use of the (inflammatory) word "inane", I find it curious

Re: More questions on building a release with a read only source tree

# make clean && make depend && make > > or > Variation on above process: Read-only source tree > Sometimes, you may wish to ensure your /usr/src/sys directory > remains untouched. This can be done by using the following process: >$ cd

More questions on building a release with a read only source tree

The FAQ describes two ways to build the kernel ( http://www.openbsd.org/faq/faq5.html#BldKernel ), # cd /usr/src/sys/arch/i386/conf # config GENERIC # cd ../compile/GENERIC # make clean && make depend && make or Variation on above process: Read-

After upgrading the source tree the kernel building process fails!

Hi all, I upgraded my OpenBSD 3.7 system's source code running this command: cvs -q up -rOPENBSD_3_7 -Pd Ok, everything worked fine, the source files were updated. Following the instructions contained in http://www.openbsd.org/anoncvs.html, there says that before compiling a new kernel I should