Stephen Hocking wrote:
For those of us using NIS, it'd be nice if the check would be made against the
passwd and group maps if the local passwd and group don't have these users.
Actually, the correct fix is to use the id command. It will automagically
find it no matter what the passwd
Current -CURRENT won't let me run su; it dies with SIGSEGV. The
backtrace says:
#0 0x28078c57 in openpam_add_module (policy=0xbfbff700, chain=0, flag=1,
modpath=0xbfbff28f pam_nologin.so, optc=-1, optv=0xbfbfee78)
at
On Fri, May 03, 2002 at 12:30:15AM -0700, Peter S. Housel wrote:
Current -CURRENT won't let me run su; it dies with SIGSEGV. The
backtrace says:
#0 0x28078c57 in openpam_add_module (policy=0xbfbff700, chain=0, flag=1,
modpath=0xbfbff28f pam_nologin.so, optc=-1, optv=0xbfbfee78)
Thanks, I hope this is not a long-term workaround!
-Original Message-
From: Brooks Davis [mailto:[EMAIL PROTECTED]]
Sent: Friday, 3 May 2002 2:30 PM
To: Thyer, Matthew
Cc: '[EMAIL PROTECTED]'
Subject: Re: Can't install ports/emulators/linux_base on -CURRENT
On Fri, May 03, 2002 at
Also have the same problem with su on -CURRENT from yesterday.
Yuri
On Fri, 3 May 2002, Peter S. Housel wrote:
Current -CURRENT won't let me run su; it dies with SIGSEGV. The
backtrace says:
#0 0x28078c57 in openpam_add_module (policy=0xbfbff700, chain=0, flag=1,
[EMAIL PROTECTED] (Peter S. Housel) writes:
Current -CURRENT won't let me run su; it dies with SIGSEGV. The
backtrace says:
Yep, I see what the error is. All I can say is arrrgh! since I've
been running this code for a while now and it never segfaults on my
box :(
DES
--
Dag-Erling
Dear all,
I wanted to write to talk about the status of our USB stack in
-current because there has been some concern expressed over the
last week about where were are at with it, and more importantly
when the bugs are going to be ironed out. In particular there has
been a call to backout it all
In message [EMAIL PROTECTED], Josef Karthauser writes:
I'm prepared to back everything out if required, but my feeling is
that we're a stone's throw away from solving these problems; it's
just I'm throwing stones slower than a seasoned kernel hacker would.
Don't even think about it!
I am very
On 03-May-2002 (13:22:48/GMT) Josef Karthauser wrote:
If anyone has any others that they've not revealed I'd like to know
please.
I don't really know if is related, but gphoto2 doesn't work with my
camera because of different linux-freebsd usb channel usage (i think).
Also, if anyone
Joe,
Thank you for taking the time to document your work-in-progress. I,
for one, vastly appreciate what you're doing with the USB subsystem.
I think a lot of our community issues could be greatly improved by
more people doing exactly what you've done here.
OK, back to the peanut gallery.
On 3 May 2002, Dag-Erling Smorgrav wrote:
[EMAIL PROTECTED] (Peter S. Housel) writes:
Current -CURRENT won't let me run su; it dies with SIGSEGV. The
backtrace says:
Yep, I see what the error is. All I can say is arrrgh! since I've
been running this code for a while now and it never
Trish Lynch [EMAIL PROTECTED] writes:
DES: also seeing problems with ftpd:
Same bug, same fix. Cvsup and rebuild libpam.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
unsuscribe
freebsd-current
unsuscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On 18:24+0300, May 3, 2002, Radoslav Vasilev wrote:
unsuscribe freebsd-current
use [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Maxim Konovalov, MAcomnet, Internet
Riccardo Torrini wrote:
On 03-May-2002 (13:22:48/GMT) Josef Karthauser wrote:
If anyone has any others that they've not revealed I'd like to know
please.
I don't really know if is related, but gphoto2 doesn't work with my
camera because of different linux-freebsd usb channel usage (i
* Orion Hodson [EMAIL PROTECTED] [020501 18:10] wrote:
/-- Alfred Perlstein wrote:
| -current compiled today mp3s play too fast, any ideas on how to
| diagnose this?
|
| pcm0: Intel 82801BA (ICH2) port 0xef00-0xef3f,0xe800-0xe8ff irq 9 at device
| 31.5 on pci0
| pcm0: measured ac97 link
Oops. Josef. Sorry; my spelling is atrocious.
-- Terry
Terry Lambert wrote:
Riccardo Torrini wrote:
On 03-May-2002 (13:22:48/GMT) Josef Karthauser wrote:
If anyone has any others that they've not revealed I'd like to know
please.
I don't really know if is related, but gphoto2
Alfred Perlstein wrote:
This makes it sound almost perfect:
sysctl hw.snd.pcm0.ac97rate=55000
the default 44061 is bad.
I thought this was because it's the CD sample rate...
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
| -current compiled today mp3s play too fast, any ideas on how to
| diagnose this?
|
| pcm0: Intel 82801BA (ICH2) port 0xef00-0xef3f,0xe800-0xe8ff irq 9 at device
| 31.5 on pci0
| pcm0: measured ac97 link rate at 44061 Hz
This makes it sound almost perfect:
sysctl
* John Hay [EMAIL PROTECTED] [020503 12:09] wrote:
| -current compiled today mp3s play too fast, any ideas on how to
| diagnose this?
|
| pcm0: Intel 82801BA (ICH2) port 0xef00-0xef3f,0xe800-0xe8ff irq 9 at device
| 31.5 on pci0
| pcm0: measured ac97 link rate at 44061 Hz
In message [EMAIL PROTECTED], Will Andrews writes
:
On Thu, May 02, 2002 at 03:30:40PM -0700, Brooks Davis wrote:
I haven't tryed backing the commits out yet, but I'm seeing similar behavior
on my HP Omnibook 500. In my case, it's actually not quite hung. What
appears to be happening is that
On Fri, May 03, 2002 at 11:10:06PM +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Will Andrews writes
:
On Thu, May 02, 2002 at 03:30:40PM -0700, Brooks Davis wrote:
I haven't tryed backing the commits out yet, but I'm seeing similar behavior
on my HP Omnibook 500. In my
On Wed, Apr 17, 2002 at 06:49:29 -0700, Ruslan Ermilov wrote:
ru 2002/04/17 06:49:29 PDT
Modified files:
share/mk bsd.doc.mk bsd.docb.mk bsd.info.mk
bsd.lib.mk bsd.libnames.mk bsd.man.mk
bsd.nls.mk bsd.obj.mk
On Fri, May 03, 2002 at 22:00:05 -0600, Kenneth D. Merry wrote:
On Wed, Apr 17, 2002 at 06:49:29 -0700, Ruslan Ermilov wrote:
ru 2002/04/17 06:49:29 PDT
Modified files:
share/mk bsd.doc.mk bsd.docb.mk bsd.info.mk
bsd.lib.mk
ken Sorry, it was this commit that broke building -current kernels on -stable:
How do you build -current kernel on your -stable box?
cd /usr
cvs -d /your/CVSROOT checkout src
cd src
make buildworld
make buildkernel
should work as it should be (and it's
On Sat, May 04, 2002 at 13:41:51 +0900, Makoto Matsushita wrote:
ken Sorry, it was this commit that broke building -current kernels on -stable:
How do you build -current kernel on your -stable box?
cd /usr
cvs -d /your/CVSROOT checkout src
cd src
make
Heh, finally someone that's actually trying to fix this. 8)
The right thing is going to be to fix the MTRR code to preserve the
extra MTRR bits; I've tried a few times to get some documentation on what
these other bits mean without any luck.
You'll need to hide these bits from the layers
28 matches
Mail list logo
