code:

TYPE="FreeBSD"
REVISION="5.3"
BRANCH="BETA5"
RELEASE=5.3-BETA5
VERSION="${TYPE} ${RELEASE}"


Hmmm. I'm not understanding what I am doing wrong. But it looks like you two must be correct in your assesment. From portsupfile:

code:

# 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=cvsup10.us.freebsd.org
*default base=/var/db
*default prefix=/usr
*default release=cvs
*default tag=RELENG_5_3
*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

## Ports Collection.
#
# The easiest way to get the ports tree is to use the "ports-all"
# mega-collection. It includes all of the individual "ports-*"
# collections,
ports-all



I am just running command:

sudo cvsup -g -L 2 portsupfile

I'm not root when I do it (obviously thus the sudo). It runs for a while and seems to finish fine. I have ran cvsup like 6 times now. I do notice though again, you must be on to something because /usr/ports is looking mighty thin. There is hardly anything in there. Perhaps I should just toast the portsupfile and start again.

Ah... change the ports-all to a src-all

You are updating your ports tree to RELENG_5_3 -- which doesn't exist and likely wiped everything out or did nothing at all... whichever is more anoying... probably the delete.

Then run the same command again... with the "src-all" instead of the "ports-all"

Notice anything stange?

edit:
guru frob23 to the rescue!

I always seperate my cvsup.os and cvsup.ports files. Here's my cvsup.ports file that I use with a refuse file.

*default host=cvsup17.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=.
*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
## Ports Collection.
#
# The easiest way to get the ports tree is to use the "ports-all"
# mega-collection. It includes all of the individual "ports-*"
# collections,
ports-all

Thanks again -X-. And just for grins, as you have suggested, I have copied your os sup file verbatim. Not sure what you meant by change the tag, unless you were pointing out what was mentioned prior...
code
default realease=cvs
tag=RELENG_5_3

If for some reason, this go around doesn't work, I'll try that next. I guess any improvements I thought I saw must be purely wishful thinking at this stage.

"Whichever is most annoying." Got a good chuckle out of that. Yes. I see what you mean. And right now, I do see a difference already just examining the output. It seems to be taking much longer. So perhaps this will do the trick this time.

Glad you mentioned that. That makes perfect sense. After I get done with this little exercise, I can see I need to upgrade my ports again (for real this time).

I use the same cvsup file and change the tag when I upgrade to a different version, that's all. Also, I have different cvsup files for os, ports, docs that let me update what and when I want to and avoid this type of problems.

See my edit on a previous post. Thought I'd get it in there before you posted again, otherwise I would have made a new post.

See, told you some guru would come along and find what the problem is!

Glad you're off on the right track!

Glad we are on the right track too. Interesting mysterious problem...or so I thought. Grateful to you both. I think I have learned more in these posts/exercise than I have in quite a while. Yes frob23 does appear to have the guru gleam to him doesn't he?

lol... not so sure I want to snatch the label guru just yet. Maybe a little experienced because I have made similar mistakes in the past (once confused my supfiles and wiped out my ports tree... while upgrading to current... which was something I wasn't expecting).

I keep them seperate as well.
/root/srcup -- my scr supfile
root/portsup -- my ports supfile.

Once you create them it is a cake-walk to upgrade the source. And upgrading a version is just an edit away... like -X- said.

Been a pretty good exercise for me to. Posted more today that the last few weeks combined. yeah, frob23 is good to have around.

You have to remember... FreeBSD has been my only operating system for over five years. If I didn't have some idea of how it worked I would be in trouble.

I think this will be a good valuable thread for people. I know I'll use it again. Having said that, just for the curious, even though I was on the wrong track I do have a couple of questions:

1. I wonder why I went from FreeBSD .xyz.net 5.3-BETA5 FreeBSD 5.3-BETA5 #2 to FreeBSD .xyz.net 5.3-BETA5 FreeBSD 5.3-BETA5 #0. From two to zero. Just curious there.

2. Is there a reason why I would not want to stick with my own custom kernel config? Again, I have been away from FreeBSD for a while, but back when I was using it quite a bit, you had to recompile the kernel to get sound to work and cd burning.

Running buildworld now.

The only thing I can think of is that you used the old method to install the #2 (and #1 and original #0) kernels but the new method when you installed this one. The old method creates a folder /usr/src/sys/i386/compile/KERNNAME

Somewhere in this folder... something allows the build process to bump the build number. Sorry for being non-specific. I'll need to hunt it up in a couple minutes. But the new method builds in /usr/obj (which is why it needs to be populated) and thus the old versions weren't seen to be bumped.

The custom kernel thing is weird right now. It is nice to remove stuff you don't need but not needed if you want to add stuff as all the drivers are built as modules (if they aren't in the kernel) and can be selected and loaded at boot time or any time after boot.

So, to enable sound you just tell the kernel to load a module at boot and you won't need to recompile it.

I think your on to something frob23. I did in fact, when I compiled the MYKERNEL kernel, do it old style. Wow. Amazing you knew that.

lol... maybe.. just maybe... I might earn that guru title someday.

Tooling around in the kernel is something I get a kick out of. I am trying to figure out how exactly the version gets put there each time (I know it is retained... but I need to find where) it is going to take a few minutes because these recursive makefiles can be a bear to wade through. But you've got me interested.