/usr/src/UPDATING contains the line:
"WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty"
This should be:
WITHOUT_MODULE_DRM and WITHOUT_MODULE_DRM2=t to /etc/src.conf to avoid nasty"
(I also added the reference to /etc/src.conf which I think is missing)
06 22:00
To: freebsd-stable@freebsd.org
Subject: -stable make world: ERROR: Required audit group is missing,see
/usr/src/UPDATING
Subject says it all.. nothing in UPDATING regarding audit group.
Appears to have been in the process of linking sshd
This src is RELENG_6 cvsup'd ~1930 UTC this
On Sat, 2006-Mar-11 17:13:58 -0500, Scott Robbins wrote:
>In fairness, many folks often skip mergemaster -p without ill effect
>till something like this happens.
Note that "mergemaster -p" also checks the options in your /etc/make.conf
and whilst changes to supported options are also rare, missin
Thanks muchly to Scott, Torfinn and Patrick for the quick replies.
This machine was running:
6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sun Feb 12 11:37:04 EST 2006
Since it was this new, it was updated with a make world and the error did not
appear in the process where I first thought it did -at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Mar 11, 2006 at 04:50:05PM -0500, Kim Culhan wrote:
> Subject says it all.. nothing in UPDATING regarding audit group.
>
> Appears to have been in the process of linking sshd
>
> This src is RELENG_6 cvsup'd ~1930 UTC this date
>
> Any help
On Sat, 11 Mar 2006 16:50:05 -0500
Kim Culhan <[EMAIL PROTECTED]> wrote:
> Subject says it all.. nothing in UPDATING regarding audit group.
>
> Appears to have been in the process of linking sshd
>
> This src is RELENG_6 cvsup'd ~1930 UTC this date
>
> Any help is greatly appreciated
To you an
Kim Culhan wrote:
Subject says it all.. nothing in UPDATING regarding audit group.
Appears to have been in the process of linking sshd
This src is RELENG_6 cvsup'd ~1930 UTC this date
Any help is greatly appreciated
-kim
--
[EMAIL PROTECTED]
___
f
Subject says it all.. nothing in UPDATING regarding audit group.
Appears to have been in the process of linking sshd
This src is RELENG_6 cvsup'd ~1930 UTC this date
Any help is greatly appreciated
-kim
--
[EMAIL PROTECTED]
___
freebsd-stable@freebsd
Marc G. Fournier <[EMAIL PROTECTED]> schrieb:
> Can someone add a pointer to this as to how to actually do this? For
> instance, I know from 5.x about the 'ln -s aj /etc/malloc.conf' for malloc
> ... but what about the rest?
Check your kernel config for INVARIANTS and WITNESS and disable these
NOTE TO PEOPLE WHO THINK THAT FreeBSD 6.x IS SLOW:
FreeBSD 6.x has many debugging features turned on, in
both the kernel and userland. These features attempt to detect
incorrect use of system primitives, and encourage loud failure
through extra sanity checking and
Claus Guttesen wrote:
I would like to know if I am the only one whos
UPDATING file in the
sourcetree hasn't changed since 4.9-RELEASE. If not
What does your supfile say?
*default release=cvs tag=RELENG_4
Yep, correct.
maby?
regards
Claus
greets,
Kay
___
On Thu, May 06, 2004 at 09:01:17AM +0200, Kay Lehmann wrote:
> I would like to know if I am the only one whos UPDATING file in the
> sourcetree hasn't changed since 4.9-RELEASE. If not I am wondering why
> it isn't changed concerning security issues etc. any more (but I think I
> am the only!!)
I'm in the same boat,
but when I recompile kernel and world, FreeBSD-4.10-RC2 when I do a uname.
Toan
> Hello evrybody,
>
> I would like to know if I am the only one whos UPDATING file in the
sourcetree hasn't changed since 4.9-RELEASE. If not I am wondering why
it isn't changed concerning secur
> I would like to know if I am the only one whos
> UPDATING file in the
> sourcetree hasn't changed since 4.9-RELEASE. If not
What does your supfile say?
*default release=cvs tag=RELENG_4
maby?
regards
Claus
Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og
v
Hello evrybody,
I would like to know if I am the only one whos UPDATING file in the
sourcetree hasn't changed since 4.9-RELEASE. If not I am wondering why
it isn't changed concerning security issues etc. any more (but I think I
am the only!!).
Thanks for the replies.
Greets,
Kay
Btw. I am runni
: * Bill Fenner's code to make ipfw/dummynet/bridge KLD'able
:
: BOTH THESE THINGS REQUIRES REBUILDING OF ipfw.ko and /sbin/ipfw
:
:I am not sure if that should be added to UPDATING. After all, it was not
:added to -CURRENT's /usr/src/UPDATING neither ;-)
:
:
e
BOTH THESE THINGS REQUIRES REBUILDING OF ipfw.ko and /sbin/ipfw
I am not sure if that should be added to UPDATING. After all, it was not
added to -CURRENT's /usr/src/UPDATING neither ;-)
Regards,
JMA
--
** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] **
Hi,
I had a similar query about just this very thing when 4.4 just went into
release mode and Warner Losh had replied to the post saying that UPDATING
in different tags (namely RELENG_4 and RELENG_4_4) are maintained
independantly of each other, so one UPDATING could differ to the other.
Makes sen
Mark Ovens wrote:
>
> On Wed, Aug 02, 2000 at 10:49:12AM -0700, John Reynolds~ wrote:
> >
> > [ On Wednesday, August 2, Warner Losh wrote: ]
> > > : I am not in favour of putting *that* in UPDATING. Either suggest an
> > > : appropriate entry in /boot/loader.conf:
> > >
> > > Actually, make ins
On Wed, Aug 02, 2000 at 10:49:12AM -0700, John Reynolds~ wrote:
>
> [ On Wednesday, August 2, Warner Losh wrote: ]
> > : I am not in favour of putting *that* in UPDATING. Either suggest an
> > : appropriate entry in /boot/loader.conf:
> >
> > Actually, make installkernel was fixed so that you do
> In message <[EMAIL PROTECTED]> Nate Williams writes:
> : > : That's wrong. 'shutdown now' takes you to single user mode. 'shutdow
> n -r now'
> : > : will make it reboot.
> : >
> : > That's changed since the last time I did shutdown then :-). Of
> : > course, that was 5 years ago or so...
>
Neil Blakey-Milner wrote:
>
> Marcel's changes mean that you the tools you use to install the world
> are ones that you can run with the old kernel. However, once they're
> installed, you may not be able to run the new binaries with the old
> kernel. In all, you "should" boot the kernel, and yo
In message <[EMAIL PROTECTED]> Nate Williams writes:
: > : That's wrong. 'shutdown now' takes you to single user mode. 'shutdown -r now'
: > : will make it reboot.
: >
: > That's changed since the last time I did shutdown then :-). Of
: > course, that was 5 years ago or so...
:
: It's been th
In message <[EMAIL PROTECTED]> Nate Williams writes:
: Warner, I think you are confused. 'shutdown now' takes you to single
: user mode. 'halt' will take you to the above prompt.
I was confused between shutdown now and shutdown -h now.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
> : That's wrong. 'shutdown now' takes you to single user mode. 'shutdown -r now'
> : will make it reboot.
>
> That's changed since the last time I did shutdown then :-). Of
> course, that was 5 years ago or so...
It's been that way since 4.3BSD, at least. Not sure which OS you were
using at
> : > : [1]
> : > : --> reboot <--
> : > :
> : [...]
> : > : This line should be "shutdown now", isn't it? Any further suggestions to
> : > : make life of Warner easier?
> : >
> : > No. It should be "reboot" since that's the simplest thing. "shutdown
> : > now" do
Johan Karlsson <[EMAIL PROTECTED]> writes:
> This has been taken care of in current but in a slightly different way.
> When using the build/installkernel targets the built / installed kernel
> is named 'kernel'
> Hence, when these changes are MFC:ed this part is not needed at all in
> UPDATING.
At 02 Aug 2000 09:58:04 +0200, Roland Jesse wrote:
> Siegbert Baude <[EMAIL PROTECTED]> writes:
>
> > ---Begin Suggestion---
>
> Not bad, but:
>
> > # Verify that the new kernel works, it will be installed as
> > # /YOUR_KERNEL_HERE
> > chflags noschg /kernel
> >
28 matches
Mail list logo
