On Sat, Sep 15, 2001 at 03:57:26AM +1000, Bruce Evans wrote:
> On Wed, 5 Sep 2001, Ruslan Ermilov wrote:
>
> > On Wed, Sep 05, 2001 at 09:44:05PM +1000, Bruce Evans wrote:
> > [...]
> > > > Index: Makefile
> > > > ===
> > > > RCS fil
On Sun, Sep 16, 2001 at 12:37:53PM +0200, Oliver Fromme wrote:
>
> Have you verified that the duplex setting of your network
> interface is correct? It should be set to half-duplex if
> the machine is connected to a hub. Don't trust autoselect.
> Check the collision LEDs at the card (if present
>Hi, I've just noticed strange behavior of psm probing (w/ and w/o acpi).
[...]
>This is not a ThinkPad, but FIVA 206VL (PS/2 mouse PnP ID = 0x130fd041;
>normal one), the psm is no longer recognized if USB is not compiled (or
>USB module is not loaded at loader).
I have never heard of this type
Matthew Jacob <[EMAIL PROTECTED]> writes:
> ROFL. That's hilarious.
By timing issue, I mean where the Makefiles think the files are
out-of-date and try to regenerate them, not a kernel race. :)
> This is a pretty much brand new kernel- same tree, buildkernel/installkernel.
> Okay, it's from last
ROFL. That's hilarious.
This is a pretty much brand new kernel- same tree, buildkernel/installkernel.
Okay, it's from last night's cvsup. But still.
I've been seeing this for some weeks- if you're saying it was fixed today,
I'll try again later, but the usual make -k did mostly what I needed- i
Matthew Jacob <[EMAIL PROTECTED]> writes:
> Seems like this has been broken for some time? I might just go off and 'fix'
> unless somebody fixes it first.
>
> install -c -o root -g wheel -m 555 rcs-to-cvs
> /usr/share/examples/cvs/contrib/rcs-to-cvs
> cp /usr/src/gnu/usr.bin/cvs/contrib/../../
Seems like this has been broken for some time? I might just go off and 'fix'
unless somebody fixes it first.
install -c -o root -g wheel -m 555 rcs-to-cvs
/usr/share/examples/cvs/contrib/rcs-to-cvs
cp /usr/src/gnu/usr.bin/cvs/contrib/../../../../contrib/cvs/contrib/rcs2log.sh
rcs2log
cp:No su
On 13-Sep-2001 Joe Greco wrote:
|> Ted: I've been watching this one because I've HAD to allow uploads to
|> incoming because of a need for such a place article submissions from
|> our
|> Tech mag website from 175+ countries.
|>
|> Your tips for monitoring (like the script for a daily listing of
This patch implements syscall wrappers for Giant around various
subsystems. It is intended to allow more developers to work on -current,
in the main tree, by allowing the various Giant pushdown works in
progress to be comitted to the main tree.
This patch implements sysctl va
Hello -
I added a login class to my /etc/login.conf and then ran cap_mkdb /etc/login.conf
test:\
:passwd_format=blf:
I then proceeded to add a user. When it came to login class, i put in test. After
the adduser script was done, i looked in /etc/master.passwd, and the password was
enc
> > The sound driver interface provides the application writer the choice to
set
> > the buffering they require. This patch has obvious implications for the
> > ordering of ioctl's that we may not want to introduce.
>
> Yes, OSS interface allows for that, but currently FreeBSD doesn't fully
> pro
On Sun, 16 Sep 2001 11:59:53 -0700, Orion Hodson wrote:
>
> Maxim
>
> The sound driver interface provides the application writer the choice to set
> the buffering they require. This patch has obvious implications for the
> ordering of ioctl's that we may not want to introduce.
Yes, OSS inter
Maxim
The sound driver interface provides the application writer the choice to set
the buffering they require. This patch has obvious implications for the
ordering of ioctl's that we may not want to introduce.
I suspect (not insist :-) the two specific fixes you report are caused by:
On Sun, Sep 16, 2001 at 11:24:54AM -0700, Julian Elischer wrote:
>
> peter has been working on this...
>
> It's because the process structure and u-area have changed entirely.
Hmmm... I can't explain the behaviour I see with this info. Can you
explain why gdb(1) gets the SIGTRAP?
--
Marcel M
Marcel Moolenaar wrote:
>
> Gang,
>
> I don't know exactly what the gdb(1) problems on Alpha are, but we
> do have a problem that's probably not specific to an architecture.
>
> The problem is basicly this: one cannot debug any programs because
> gdb(1) gets a SIGTRAP delivered when it invokes
Jonathan Belson wrote:
>
> Jim Bryant wrote:
> >
> > I am getting intermittant communications initialization errors involving
>DCOPSERVER upon starting KDE. The thing is that it seems
> > to be random. So far it will happen 2 out of every 3 times you attempt to login
>via KDM... So far, the
Gang,
I don't know exactly what the gdb(1) problems on Alpha are, but we
do have a problem that's probably not specific to an architecture.
The problem is basicly this: one cannot debug any programs because
gdb(1) gets a SIGTRAP delivered when it invokes ptrace(2) and never
gets a change to wait
Hi, I've just noticed strange behavior of psm probing (w/ and w/o acpi).
> > It now appears that some IBM ThinkPad models assign a distinct PnP ID
> > to the PS/2 mouse port.
> >
> > If you have ThinkPad and its pointing device is not recognized when
> > ACPI is loaded in the latest -current sys
Jim Bryant wrote:
>
> I am getting intermittant communications initialization errors involving DCOPSERVER
>upon starting KDE. The thing is that it seems
> to be random. So far it will happen 2 out of every 3 times you attempt to login via
>KDM... So far, the only cure is to keep
> logging in
Geoff Rehmet <[EMAIL PROTECTED]> wrote:
> No, I can't say for certain when this started. In fact, reverting to a
> kernel from June 27 still shows the same problem.
>
> However, I have done the following exercise, with three machines,
> two of which sit on our internal LAN together, on the
20 matches
Mail list logo
