Any comments / objections to these patches to savecore and friends?
After I get more than two or three md5 named files in var/crash I
start to go cross eyed.
--
Chad David[EMAIL PROTECTED]
www.FreeBSD.org [EMAIL PROTECTED]
ACNS Inc. Calgary, Alberta Canada
Fourthly, The
* Chad David [EMAIL PROTECTED] [020418 23:32] wrote:
Any comments / objections to these patches to savecore and friends?
After I get more than two or three md5 named files in var/crash I
start to go cross eyed.
I found the md5 names to be particularly disgusting as well. If this
reverts
On Fri, Apr 19, 2002 at 12:13:47AM +0100, Hiten Pandya wrote:
If anyone recalls, I sent a post before which was about changing the
kernel path changes in the (only) -current man pages. As these are
related to -current, I am sending them to this list for a complete
review.
Why are you
--- Mark Santcroos [EMAIL PROTECTED] wrote:
On Fri, Apr 19, 2002 at 12:13:47AM +0100, Hiten Pandya wrote:
If anyone recalls, I sent a post before which was about changing the
kernel path changes in the (only) -current man pages. As these are
related to -current, I am sending them to this
Hi,
I updated my -current system yesterday, and I see a few lock order reversals.
This one happens during booting:
Apr 18 16:35:40 0.2 terminus kernel: lock order reversal
Apr 18 16:35:40 0.2 terminus kernel: 1st 0xc5ecbbb8 xl0 (network driver)
@ /var/src/sys/pci/if_xl.c:1260
Apr 18 16:35:40
A Creative Soundblaster PCI64 (Ensoniq Audio PCI)...
$cat /dev/sndstat
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: AudioPCI ES1370 at io 0xd000 irq 10 (1p/1r/0v channels duplex
default)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
While I do not object to the addition of the new users for
sendmail, and I understand the theory of having them own directories for
its operation, I think that the current bootstrapping problems are
creating too greate a barrier for users who upgrade from source. There are
(at least) two
Even worse, I've had the same messages _and_ all
commands accessing one particular file (/sys/i386/conf/THINKPAD if anyone's
interested) hanged completely.
--
Marcin Cielak // [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in
So: I changed line 186 in sys/dev/ata/ata-disk.c from
adp-num_tags = atadev-param-queuelen;
to
adp-num_tags = 0x10;
which is roughly the half of the reported queuelenght (which is 0x1F).
And, Terry, I can't avoid to disappoint you... there's absolutely *no*
change in
Mark Santcroos [EMAIL PROTECTED] writes:
Why are you replacing /dev/kmem with the kernel path???
If you are referring to
-.Bl -tag -width /dev/kmem -compact
-.It Pa /kernel
+.Bl -tag -width /boot/kernel/kernel -compact
+.It Pa /boot/kernel/kernel
then he's doing it because /boot/kernel/kernel
DougB My proposal is simple. Change from using names to numeric [ug]id's
DougB in mtree, and elsewhere if needed. The plus is that it solves the
DougB bootstrapping problem. The negatives involve problems with systems
DougB that don't merge the password and group files, and therefore will
DougB
In message: [EMAIL PROTECTED]
Doug Barton [EMAIL PROTECTED] writes:
: 2. Users who don't read (or don't understand) UPDATING. This is basically,
: everybody.
Actually, UPDATING was changed last night to be more explicit about
what to do. Let's give that a chance. I don't like the
In message: [EMAIL PROTECTED]
Gregory Neil Shapiro [EMAIL PROTECTED] writes:
: .if !defined(NO_SENDMAIL)
: mtree -deU -f ${.CURDIR}/mtree/sendmail.root.dist -p ${DESTDIR}/
: .endif
Wow! I hadn't read this before making my suggestion. Honest :-)
I like his solution.
Warner
After yesterdays new build I found a problem
Xfree86-4 can't start as regular user (exept root)
this is the error message I get:
AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from
local host
AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from
local host
On 18 Apr 2002, Dag-Erling Smorgrav wrote:
Try the attached patch. You'll need to rebuild libutil and restart
sshd.
Works.
Thanks.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax |
|
On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote:
After yesterdays new build I found a problem
Xfree86-4 can't start as regular user (exept root)
Read the fine message you got at install-time and install the wrapper
port.
Kris
msg37428/pgp0.pgp
Description: PGP signature
Kris Kennaway wrote:
On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote:
After yesterdays new build I found a problem
Xfree86-4 can't start as regular user (exept root)
Read the fine message you got at install-time and install the wrapper
port.
Kris
Wrapper is installed
it
On 2002-04-19 00:31, Chad David wrote:
Any comments / objections to these patches to savecore and friends?
Since you asked ... :)
Index: savecore.8
===
+The
+.Nm savecore
You can safely remove savecore from the .Nm
Well, who damages LOGIN_CAP processing in sshd now? It not reads
~/.login_conf anymore and not sets LOGIN_CAP limits.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sat, Apr 20, 2002 at 05:21:42 +0400, Andrey A. Chernov wrote:
Well, who damages LOGIN_CAP processing in sshd now? It not reads
~/.login_conf anymore and not sets LOGIN_CAP limits.
I see parent environment seriously damaged in do_setusercontext() since
not saved. I mean MAIL,BLOCKSIZE
On Sat, Apr 20, 2002 at 03:28:18AM +0300, Giorgos Keramidas wrote:
On 2002-04-19 00:31, Chad David wrote:
Any comments / objections to these patches to savecore and friends?
Since you asked ... :)
Yes, I did.
Index: savecore.8
I've found that wrapper needs to be updated with XFree86-4.
James.
- Original Message -
From: John Angelmo [EMAIL PROTECTED]
To: current [EMAIL PROTECTED]
Sent: Friday, April 19, 2002 1:13 PM
Subject: Xfree86-4 problem
After yesterdays new build I found a problem
Xfree86-4 can't
On Sat, Apr 20, 2002 at 06:43:05 +0400, Andrey A. Chernov wrote:
On Sat, Apr 20, 2002 at 05:21:42 +0400, Andrey A. Chernov wrote:
Well, who damages LOGIN_CAP processing in sshd now? It not reads
~/.login_conf anymore and not sets LOGIN_CAP limits.
I see parent environment seriously
23 matches
Mail list logo
