On 22-Dec-2001 (22:23:24/GMT) aaron wrote:
[...removed CC: because I suppose all subscribed this list...]
any address found in the archives is automatically subscribed
Any address found N times (where N reasonably high number, like
10, because we can not really assume that the archives are
my 2 cents worth,
I don't think the effort is worth the reward. If the frequency increases, then
the issue should be revisited.
If we do decide this problem merits action...
A simple solution would be to restrict posts to subscribers of the lists
(-questions could be an exception). Another
Hi Jacques,
I've read that you've stopped working on our nsswitch
implememtation. But now that CURRENT has been delayed for
one year, it would be a really good time to finish
your work.
Not only because a working nss_ldap would be a great thing,
also for a working samba winbind. This feature
I meant anyone who is subscribed as a starting point,
and going forwards, anyone referenced in an email and not explicitly
NACK'd
On Sun, 23 Dec 2001, Riccardo Torrini wrote:
On 22-Dec-2001 (22:23:24/GMT) aaron wrote:
[...removed CC: because I suppose all subscribed this list...]
any
subscribe
__
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Hello all,
I have already sent a mail about this problem before.
I am a newbie of
FreeBSD. This time I attached the dmesg output and
kernel configuration for
you all.
I am using Asus A7V mb, Athlon 1.1 GHz CPU, 512 Mb
RAM. Whenever the kernel
boot up, the message device_probe_and_attach:
On Sun, Dec 23, 2001 at 04:43:55AM -0800, Raman Ng wrote:
I am using Asus A7V mb, Athlon 1.1 GHz CPU, 512 Mb
RAM. Whenever the kernel
boot up, the message device_probe_and_attach: ums0
attach returned 6.
Details can refer to the attached detail.. This
problem is similar to PR
Please note that I am taking no position regarding whether Matt's sio
changes should remain or be backed out.
That said, the following was the minimal change I found necessary to
get today's -CURRENT to build:
Index: sio.c
===
RCS
* mikem ([EMAIL PROTECTED]) wrote:
I don't think the effort is worth the reward. If the frequency
increases, then the issue should be revisited.
If we do decide this problem merits action...
How about filtering list messages through spamassassin? Anything that
matches can get bounced so
:Please note that I am taking no position regarding whether Matt's sio
:changes should remain or be backed out.
:
:That said, the following was the minimal change I found necessary to
:get today's -CURRENT to build:
Ha! My original commit was correct. My bruce-backout commit was
Dropping -stable crosspost.
For those of you with this mouse -- we really need the output of 'usbdevs
-v' with the mouse attached.
I'm betting that this isn't a standard USB mouse and requires a special,
proprietary driver. :(
Doug White| FreeBSD: The Power to Serve
[EMAIL
Not sure whether this better belongs to -current or -questions...
The situation is like this: I run a recent current (cvsup'ed on Fri Dec 21)
with drm (0.9.4). X 4.1.0_10 has been compiled locally with Matrox drivers
from Matrox site (1.4.3, to match X4.1.x). This has also been done around
On Sun, Dec 23, 2001 at 09:57 -0800, Matthew Dillon wrote:
[ the sio.c FIFO commit ]
Ha! My original commit was correct. My bruce-backout commit was
flawed. Wonderful. What do we do now?
Correct the patch to switch between 14 and 8 bytes trigger level
while leaving the default
Just ran make world this morning and 21 fd redirection stopped working
for /bin/sh.
$ ls /bad/file /dev/null 21
ls: /bad/file: No such file or directory
21 is used extensively in the /etc/rc* bootup scripts. Now, the bootup
screen is cluttered with unwanted messages.
Any idea?
kt
To
KT Sin [EMAIL PROTECTED] writes:
Just ran make world this morning and 21 fd redirection stopped working
for /bin/sh.
$ ls /bad/file /dev/null 21
ls: /bad/file: No such file or directory
21 is used extensively in the /etc/rc* bootup scripts. Now, the bootup
screen is cluttered with
: Warner, could you please add __stdoutp to the 20010919 entry, and
: a hint to put COMPAT4X=true to /etc/make.conf to the 20010924 entry?
Done.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Warner, could you please add __stdoutp to the 20010919 entry, and
a hint to put COMPAT4X=true to /etc/make.conf to the 20010924 entry?
Actually, you only need the first one. You don't need COMPAT4X=true
all the time, so I'm a little reluctant to include that. Lemme know
how I can improve
I'd like to drop bsd.man.mk support from bsd.kmod.mk,
because I was told by someone (peter?) that this is
the right direction. :-)
We use it slightly at Timing Solutions, but it is more of a pain than
a blessing. More of our module Makefiles have NOMAN than don't, by a
wide margin.
Warner
18 matches
Mail list logo
