* 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
rever
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 consta
On Fri, 19 Apr 2002, kai ouyang wrote:
> options UFS_EXTATTR
> options UFS_EXTATTR_AUTOSTART
> options UFS_ACL
Now you have to create backing storage for extended attributes, ALC in
your case. This can be achieved by the following commands:
# cd /
# mkdir .attribute .a
Hi everyone, I has seen the manual and /sys/ufs/ufs/README.* . I add the following to the kernel conf: options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART options UFS_ACL The
On Thu, 18 Apr 2002, Thomas Wuerfl wrote:
> Am Donnerstag, 18. April 2002 05:00 schrieb Craig Boston:
> > My only trouble so far has been mount_smbfs panicking the machine when
> > connecting to certain servers (but not others, weird). I'm compiling a
> > debug kernel now and will attempt to get
Matthias Schuendehuette wrote:
> Am Donnerstag, 18. April 2002 17:54 schrieb Terry Lambert:
> > I wish someone who is having the problem would try the three
> > hacks I suggested, and report back. I personally can't reproduce
> > the problem here, either.
>
> So: I changed line 186 in sys/dev/at
On Thu, 18 Apr 2002, Hiten Pandya wrote:
> --- Robert Watson <[EMAIL PROTECTED]> wrote:
> > I've had four seperate and distinct panics on my -current box from
> > yesterday in the last twenty minutes. -CURRENT appears to be somewhat
> > unstable. Yes, this is -CURRENT; please wear a hard hat a
On Thu, 18 Apr 2002 14:46:25 EST, Peter Schultz wrote:
> I just pulled php4 from cvs and found that libtool version 1.4 is
> required for the build. I know the popular response is to say "shut up
> and code," but I'm not afraid to admit that libtool is way over my head.
> I just hope some
Hi all,
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. I had given this to Giorgos (keramida@), but he has been
busy and ill latel
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> Yep, the problem seems to be that sshd calls pam_open_session(3) too
> early. I'm looking into it right now.
Try the attached patch. You'll need to rebuild libutil and restart
sshd.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
--- //depot
> Hi,
>
> i cant record from /dev/dsp with the record device 'mic'. Is
> there support
> for the microphone input?
>
What sound card are you using?
Scott
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
i cant record from /dev/dsp with the record device 'mic'. Is there support
for the microphone input?
Jan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 18 Apr 2002, Eric Brunner-Williams in Portland Maine wrote:
> # uname -a
> FreeBSD nic-naa.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Wed Apr 17 10:35:32 EDT 2002
> [EMAIL PROTECTED]:/usr/src/sys/compile/ABENAKI i386
>
[snip ...]
> install -c -s -o root -g wheel -m 555 chflags /bi
I just pulled php4 from cvs and found that libtool version 1.4 is
required for the build. I know the popular response is to say "shut up
and code," but I'm not afraid to admit that libtool is way over my head.
I just hope some sympathetic genius sees this and decides they're not
above tackl
On Thu, 18 Apr 2002, Brandon D. Valentine wrote:
>http://www.specbench.org/gpc/opc.static/vp50.htm
This is probably a more useful URL:
http://www.specbench.org/gpc/opc.static/overview.htm
(thought I hit back before copying-and-pasting the URL, but I guess not)
- Brandon D. Valentine
To Unsu
Am Donnerstag, 18. April 2002 17:54 schrieb Terry Lambert:
> I wish someone who is having the problem would try the three
> hacks I suggested, and report back. I personally can't reproduce
> the problem here, either.
So: I changed line 186 in sys/dev/ata/ata-disk.c from
adp->num_tags = atadev->
On Thu, 18 Apr 2002, Oswald Buddenhagen wrote:
> hi,
>
> heck, was it hard for me (a person who never used freebsd) to find the
> right address ... nah, whatever. :)
>
> src/lib/libc_r/uthread/uthread_init.c
> some time ago you commited a workaround for processes with pid 1 (and no
> stdio). un
>
> Could people test this in-kernel DRM and tell me how it works
> for them?
Works fine for me on a Matrox G400 with the standard Mesa apps, Linux Unreal
Tournament, and a custom build of Quake2 for FreeBSD. Good work!
Scott
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> "Matthew N. Dodd" <[EMAIL PROTECTED]> writes:
> > If not pam_unix, what module is responsible for updating utmp?
> pam_lastlog(8) (though there seems to be a problem with sshd)
Yep, the problem seems to be that sshd calls pam_open_session(3) too
e
On 18 Apr 2002, Dag-Erling Smorgrav wrote:
>Eric Anholt <[EMAIL PROTECTED]> writes:
>> Could people test this in-kernel DRM and tell me how it works for them?
>
>Seems to work fine here (trusty ol' Matrox G200 w/8 MB). Is there a
>particular DRI application I can use to somehow stress-test or
>b
"Matthew N. Dodd" <[EMAIL PROTECTED]> writes:
> If not pam_unix, what module is responsible for updating utmp?
pam_lastlog(8) (though there seems to be a problem with sshd)
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-c
Am Donnerstag, 18. April 2002 17:54 schrieb Terry Lambert:
>
> I wish someone who is having the problem would try the three
> hacks I suggested, and report back. I personally can't reproduce
> the problem here, either.
Ok, ok... ;-) I start *now*. I just compiled a new -current world
(...puhh)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Coolio, thanks for letting me in the know.
Cheers,
Eugene
On Thu, Apr 18, 2002 at 04:26:20PM +0300, Ruslan Ermilov wrote:
> Already fixed this earlier this morning (local time).
> And just removed the gratuitous LIBCOMPATDIR assignments.
>
> Cheers,
> --
> Ruslan ErmilovSysadmi
On 18 Apr 2002, Dag-Erling Smorgrav wrote:
> Actually, the bug is in the PAM configuration files that list pam_unix
> as a "session" module while pam_unix doesn't provide session
> management services. PAM is correct in whining about that. The
> solution is to remove lines like this from /etc/pa
Eric Anholt <[EMAIL PROTECTED]> writes:
> Could people test this in-kernel DRM and tell me how it works for them?
Seems to work fine here (trusty ol' Matrox G200 w/8 MB). Is there a
particular DRI application I can use to somehow stress-test or
benchmark the module? I've gotten kind of tired of
I was getting the same "Signal 12" error about a week ago.. What I had
to end up doing was after a 'buildworld', then rebuilding the kernel
installing it and then rebooting. Then after this doing an
'installworld, then things seemed to be alright from then on :-)
Glenn G.
On Thu, 18 Apr 2002
--- Robert Watson <[EMAIL PROTECTED]> wrote:
> I've had four seperate and distinct panics on my -current box from
> yesterday in the last twenty minutes. -CURRENT appears to be somewhat
> unstable. Yes, this is -CURRENT; please wear a hard hat and avoid
> manipulating critical data using you -CU
It seems Alexander Leidinger wrote:
> On 18 Apr, Søren Schmidt wrote:
>
> >> What's your theory on it?
> >
> > None so far, I've instrumented the code here, and I simply cannot
> > see what should go wrong (yet).
>
> Does it make sense to give this instrumentation to someone who can
> reproduce
On 18 Apr, Søren Schmidt wrote:
>> What's your theory on it?
>
> None so far, I've instrumented the code here, and I simply cannot
> see what should go wrong (yet).
Does it make sense to give this instrumentation to someone who can
reproduce it?
Bye,
Alexander.
--
It's not
# uname -a
FreeBSD nic-naa.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Wed Apr 17 10:35:32 EDT 2002
[EMAIL PROTECTED]:/usr/src/sys/compile/ABENAKI i386
# mount | grep src
agaskwa:/freebsd/FreeBSD/branches/-current/src on /usr/src (nfs)
(/usr/obj is local)
cvsup'd Apr 18 09:10 EDT
...
install -
I have a dell poweredge 500sc currently running 4.5-STABLE with the
following:
atapci0: port
0x8c0-0x8c3,0x8b0-0x8bf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at
device 15.1 on pci0
ad0: 19073MB [38752/16/63] at ata0-master UDMA100
and it eventually stops at a mount root prompt after se
It seems Terry Lambert wrote:
> > Hmm, since I havn't been able to get my hands on the problem
> > (I've been running 3 systems here with tags all over since the
> > first report, not a single hickup yet :( ) I can't tell whats
> > going on, it might be that the drive somehow gets really confused
"Søren Schmidt" wrote:
> > > Oh yes you can, the ATA driver does just that in case of the drive
> > > loosing its marbels.
> >
> > If it worked, people wouldn't be having this problem.
>
> Hmm, since I havn't been able to get my hands on the problem
> (I've been running 3 systems here with tags a
It seems Terry Lambert wrote:
> "Søren Schmidt" wrote:
> > > I didn't mean for the reset itself, I meant for the process. You
> > > can't "take back" writes that are in progress and not acknowledged,
> > > in order to retry them after the reset, so as to not lose data.
> >
> > Oh yes you can, th
Matthias Schuendehuette wrote:
> ...ahh, I mean, the driver *does* take an action (it/he(?) switches
> back to PIO4), but why is any UDMA-Mode no longer usable afterwards?
This is the $64 question.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in th
It seems [EMAIL PROTECTED] wrote:
> This won't help people using similair drives (in one of my machines)
> that I am using, I have the same problem in current that I have in
> RELENG_4,
> It times out and drops to PIO4 mode after a few min. I dropped
> "atacontrol mode 0 pio4 none" (I only have t
"Søren Schmidt" wrote:
> > I didn't mean for the reset itself, I meant for the process. You
> > can't "take back" writes that are in progress and not acknowledged,
> > in order to retry them after the reset, so as to not lose data.
>
> Oh yes you can, the ATA driver does just that in case of the
It seems Matthias Schuendehuette wrote:
> > > I didn't mean for the reset itself, I meant for the process. You
> > > can't "take back" writes that are in progress and not acknowledged,
> > > in order to retry them after the reset, so as to not lose data.
> >
> > Oh yes you can, the ATA driver doe
Bill Fenner <[EMAIL PROTECTED]> writes:
> Part of the commit log for rev 1.32 of pam_unix.c says:
>
> - remove dummy functions since OpenPAM handles missing service
> functions
>
> However, OpenPAM is noisy about handling missing service functions:
>
> Apr 17 11:21:31 stash login: in open
This won't help people using similair drives (in one of my machines)
that I am using, I have the same problem in current that I have in
RELENG_4,
It times out and drops to PIO4 mode after a few min. I dropped
"atacontrol mode 0 pio4 none" (I only have the 1 drive on the chain)
before the fsck che
I got this as well, setting the ENV variable however seems to resolve it
temporarily
export INFODIR="/usr/share/info"
setenv INFODIR /usr/share/info
Whichever shell you use, chose the appropriate one, atleast it seemed to
work for me, and I have not noticed any problems.
Jason
-Original
Am Donnerstag, 18. April 2002 16:44 schrieb Søren Schmidt:
> It seems Terry Lambert wrote:
> > "Søren Schmidt" wrote:
> > > It seems Terry Lambert wrote:
> > > > My other hunch is that there will need to be a channel reserved
> > > > for "reset" commands to be queued to the disk, so that you can
>
It seems Terry Lambert wrote:
> "Søren Schmidt" wrote:
> > It seems Terry Lambert wrote:
> > > My other hunch is that there will need to be a channel reserved
> > > for "reset" commands to be queued to the disk, so that you can
> > > queue more commands to it later (e.g. can't connect to send the
On Wed, 17 Apr 2002, Julian Elischer wrote:
> I got this fault on a production machine..
> The given fault PC was 0xc01499f0 which is the first byte of fxpintr()
> (??)
> even though coredumps were enabled, for some reason none was made.
>
> > > >
> > > > wss0c left this message in /var/log/messa
On Thu, Apr 18, 2002 at 12:04:35AM -0700, Manfred Antar wrote:
> The recent changes to the /usr/src/share/mk files
> have made installing ports broken , also doing a make install world stops at
> /usr/src/share/info:
> (info)518}make install
> Warning: the directory /usr/share/info does not exist!
On Thu, Apr 18, 2002 at 06:34:38AM +0900, Eugene M. Kim wrote:
> Don't know what prevented this from being caught, but:
>
>
>http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/compat/Makefile.inc?only_with_tag=MAIN#rev1.5
>
>http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/compat/compat1x/Makefile?only
"Søren Schmidt" wrote:
> It seems Terry Lambert wrote:
> > My other hunch is that there will need to be a channel reserved
> > for "reset" commands to be queued to the disk, so that you can
> > queue more commands to it later (e.g. can't connect to send the
> > reset because of the already disconn
Am Donnerstag, 18. April 2002 05:00 schrieb Craig Boston:
> My only trouble so far has been mount_smbfs panicking the machine when
> connecting to certain servers (but not others, weird). I'm compiling a
> debug kernel now and will attempt to get a good backtrace to post.
I have the same problem
It seems Alexander Leidinger wrote:
> On 18 Apr, Doug Barton wrote:
> > Given the impending 4.6-release, might it make sense to back off ata in
> > -stable to the last known-good state?
>
> We have some time until the code freeze, so give him some days to track
> it down. If he is able to fix it:
hi, there!
On Thu, Apr 18, 2002 at 01:51:19AM -0700, Doug Barton wrote:
> > It seems Doug Barton wrote:
> > > Given the impending 4.6-release, might it make sense to back off ata in
> >
> > The busdma/sparc64 code is *not* in stable...
>
> Hmmm... I thought I saw some complaints on -stabl
On 18 Apr, Doug Barton wrote:
> Given the impending 4.6-release, might it make sense to back off ata in
> -stable to the last known-good state?
We have some time until the code freeze, so give him some days to track
it down. If he is able to fix it: fine, else he can still back it out.
Bye,
Alex
On Thu, 18 Apr 2002, Søren Schmidt wrote:
> It seems Doug Barton wrote:
> > Given the impending 4.6-release, might it make sense to back off ata in
>
> The busdma/sparc64 code is *not* in stable...
Hmmm... I thought I saw some complaints on -stable, but I might
have been mistaken.
--
It seems Doug Barton wrote:
> Given the impending 4.6-release, might it make sense to back off ata in
The busdma/sparc64 code is *not* in stable...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
54 matches
Mail list logo
