Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Apr 2002 13:46:21 -0500
From:      "Shawn Kennedy" <shawnlkennedy@lucent.com>
To:        "mpd" <mpd6334@cs.rit.edu>
Cc:        "Kent Stewart" <kstewart@owt.com>, <alan.edmonds@t-motion.net>, <rehsack@liwing.de>, <freebsd-questions@FreeBSD.ORG>
Subject:   RE: kernel install problem
Message-ID:  <NEBBLNBDCLDILGOPJLGIKENLCHAA.shawnlkennedy@lucent.com>
In-Reply-To: <20020416141843.A5571@rochester.rr.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message-----
> From: mpd [mailto:mpd6334@cs.rit.edu]
> Sent: Tuesday, April 16, 2002 1:19 PM
> To: Shawn Kennedy
> Cc: Kent Stewart; alan.edmonds@t-motion.net; rehsack@liwing.de;
> freebsd-questions@FreeBSD.ORG
> Subject: Re: kernel install problem
> 
> 
> On Tue, Apr 16, 2002 at 01:02:45PM -0500, Shawn Kennedy wrote:
> <snipped>
> > 
> > So based upon Kent's info and Mike's info, should the cvsupfile
> > look like this instead?
> > 
> > *default  host=cvsup3.FreeBSD.org
> > *default  base=/usr
> > *default  prefix=/usr
> > *default  release=cvs
> > *default  tag=RELENG_4
> > *default  delete use-rel-suffix
> > 
> > src-all
> > *default tag=.
> > ports-all
> > doc-all
> 
> Looks good. Kent is right about the placement of the tag=. line.
> I've always just used separate supfiles for ports and doc, 
> because I update them at different times than I do the source
> tree.

I've updated the file accordingly and have started to recvsup.
Thank god work has a nice fat pipe for me ......

> > I do want to stay with -STABLE.  Is it possible to fix this
> > with a new cvsup with a corrected cvsupfile as Mike stated to?
> 
> If your cvsup file is correct, you should be all set. I don't
> see any problems with the one above. Even if you screw up
> and delete the entire source tree, it won't hose the running
> system, and you can fix the supfile and re-cvsup.

Cool.

> > Also, as to why the kernel build is installing in /boot/kernel/,
> > at the top of the kernel build, it lists a variable KMODDIR
> > that is set to /boot/kernel/. I have no idea where this is getting
> > set or by whom.
> 
> No idea. Something from -current, perhaps?

I just had a friend stop by telling me that is one of the things
he thinks changed with -current.

Thank a bunch.

Shawn

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?NEBBLNBDCLDILGOPJLGIKENLCHAA.shawnlkennedy>