Date: Sun, 14 Mar 1999 20:09:06 +0100 From: Roelof Osinga <roelof@eboa.com> To: John Polstra <jdp@polstra.com> Cc: questions@FreeBSD.ORG Subject: Re: CVSup: a newbie's tale. Message-ID: <36EC0952.2C2614CB@eboa.com> References: <XFMail.990313164337.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra wrote:
>
> No, the instructions you complained about are in the "Running CVSup"
> section of the tutorial -- not the "Configuration" section.
I've a holistic outlook on life, the universe and everything. Besides,
it's only 2 sentences into "Running CVSup", it barely left "Configuration".
> Not when the files are specified on the command line. I can't think
> of a single Unix utility that works that way.
A linker?
> With Samba, you don't name the "configuration" files on the command
> line.
But then Samba is usually run as daemon. Even so:
SYNOPSIS
smbd [ -D ] [ -a ] [ -d debuglevel ] [ -l log file ] [ -p
port number ] [ -O socket options ] [ -s configuration
file ]
First you compile in the 'default base dir' as well as the name of
the configuration file 'smbd.conf' next you can provide it as
param as well.
Whereas CVSup does talk about a default base dir as well as config
files, and although it does look like a daemon it is not and it
treats them differently. It's more like an awk script than a
configuration file. I think it's that dual function that befuddled
me. When talking about configuration files I expect some
etc/cvsup.conf that tells CVSup where it's defaults are. As something
separate from the scripts that tell it what to fetch. Currently
you need to include the setup part in each config file.
> I really can't help with this unless you can give me a recipe for
> duplicating the problem. If you can make it happen again on your
> system and will send me a transcript (man 1 script) of the entire
> build process, then I'd be happy to look at it.
When the opportunity arises I will so. First I'll need to get it up
and running enough to take over as Internet server. And I'm not
looking forward to porting all mailarchives from WU to Cyrus IMAP.
> You worry too much. :-) Heck, just run it! If you don't like what
> it's doing, then kill it. Unless you assume the program is outright
> hostile, it's not going to do much damage in the second or so it takes
> you to hit ^C.
I did and look where it got me. All the files ended up in /usr/sup :).
> You can get individual ports easily from the FreeBSD web pages. Go
> to www.freebsd.org, click on "Ported applications", and take it from
> there.
Now he tells me <g>. Besides, why do things the easy way whene there's
a perfectally good hard way to do it?
> Since '85 at the latest. ;-)
The story of my life. First I miss out on the sixties and now this!
Does it never stop? ;)
Roelof
--
Home is where the (@) http://eboa.com/ is.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36EC0952.2C2614CB>