ney for a set of features developed and supported over a long
> period of time. At least that's what Linux would make me think...
I would suggest that whoever does the work break up the nVidia needs
list into a small series of steps that could be accomplished (and
bought) more ea
(trimming the cc-list)
On Fri, Sep 28, 2007 at 07:33:35PM +0200, Markus Hitter wrote:
>
> Am 28.09.2007 um 16:23 schrieb Michael W. Lucas:
>
> >If you don't have the skills, but you believe that you have sufficient
> >motivation and interest, then you tneed to
a port, ran "make package," and let it bundle everything for me.
Then I distributed the package to my clients.
Understanding the package format annoyed me more than understanding
the ports format. You might find otherwise.
==ml
--
Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTE
ath0: scan_next: chan 4g -> 5g [active,
dwell min 20 max 200]
Feb 21 11:09:55 stretchlimo kernel: ath0: scan_next: chan 5g -> 8g [active,
dwell min 20 max 200]
Feb 21 11:09:55 stretchlimo kernel: ath0: scan_next: chan 8g -> 9g [active,
dwell min 20 max 200]
Feb 21 11:09:55 st
On Thu, Feb 21, 2008 at 02:15:47PM -0800, Sam Leffler wrote:
> Michael W. Lucas wrote:
> >Feb 21 09:45:57 stretchlimo kernel: ath0: mac 5.6 phy 4.1 radio 0.0
> >Feb 21 09:47:34 stretchlimo kernel: ath0: ath_chan_set: unable to reset
> >channel 40 (5200 Mhz, flags 0x140 hal
slogd -d didn't give anything interesting.
I'm now running syslogd -n, to see if that helps. I'm also restarting
syslogd every fifteen minutes, to ensure that the problem can last no
longer than 14 minutes. :-)
Anyone interested in why syslogd is not draining the queue?
Thank
*.*
>
> Are you using a serial console? I had similar problems in the past
> due to the serial port flow control.
Yes, I am.
So, if I disable syslogd writing to the console, it might clear this up?
Thanks,
==ml
--
Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTE
*.*
>
> Are you using a serial console? I had similar problems in the past
> due to the serial port flow control.
I've disabled syslog to the console, writing instead to
/var/log/console.log.
Moments after doing that, the problem reoccured. Thanks, Borja, but
no success.
On Mon, Mar 27, 2006 at 10:01:42PM +0400, Maxim Konovalov wrote:
> On Mon, 27 Mar 2006, 12:38-0500, Michael W. Lucas wrote:
>
> > On Mon, Mar 27, 2006 at 06:18:50PM +0200, Borja Marcos wrote:
> > > >I've got a machine running syslogd, DNS, DHCP, flow-capture, and oth
ll.log
+#*.* /var/log/all.log
# uncomment this to enable logging to a remote loghost named loghost
#*.* @loghost
# uncomment these if you're running inn
@@ -40,5 +30,3 @@
*.*/var/log/slip.log
!ppp
*.*
gt; Removed the named socket and restarted. We'll see what happens.
> [...]
>
> Can you check there is nothing from syslogd on the serial console?
I changed that this morning in response to an earlier suggestion.
To be sure, I just ran:
logger -p local0.err "test message"
encourage people to not hose things further.
Folks, don't let the fact that you're not a guru stop you from taking
a kiddie step and submitting a basic test!
==ml (who uses neither unionfs nor nullfs because of the scary man pages)
--
Michael W. Lucas[EMAIL PROTECTED], [EMAI
Woo hoo! We'll test this here the next time we upgrade.
Could you send-pr this, so it doesn't get lost?
Thanks!
==ml
On Tue, Jan 13, 2004 at 02:46:23AM -0500, Michael R. Wayne wrote:
>
> Although Doug Barton has written a wonderful tool, it has always
> seemed to have a major deficiency: it co
Hi,
This question really should go to [EMAIL PROTECTED] in the future,
not [EMAIL PROTECTED]
I wrote some articles on MRTG and SNMP. Take a look at:
http://www.onlamp.com/pub/a/bsd/2000/07/27/Big_Scary_Daemons.html
http://www.onlamp.com/pub/a/bsd/2000/08/10/Big_Scary_Daemons.html
http://www.onl
On Sat, May 29, 2004 at 07:55:21PM -0400, Robert Watson wrote:
> The FreeBSD Core Team took a look at the APSL a while back, and decided
> that similar to LGPL/GPL, it was an acceptable license for use in
> userspace for stand-alone tools, but that similar protections to LGPL/GPL
> would be require
On Sat, Jun 05, 2004 at 09:59:15PM +1000, Edwin Groothuis wrote:
> On Wed, Jun 02, 2004 at 09:57:57AM -0400, Michael W. Lucas wrote:
> > People may gripe about Apple not returning stuff to the open source
> > community. The truth is, they have. They aren't responsible for
Not to blow my own horn, but:
http://www.onlamp.com/pub/a/bsd/2002/05/09/Big_Scary_Daemons.html
On Mon, Jul 19, 2004 at 07:11:07AM -0500, Stephen Hocking wrote:
> All,
>
> I'm looking at creating multiple versions of FreeBSD on the one disk - sharing
> perhaps one or two filesystems, but with t
17 matches
Mail list logo
