On Sat, Dec 08, 2001 at 05:09:11PM -0800, Peter Wemm wrote:
> Joerg Wunsch wrote:
> > Bernd Walter <[EMAIL PROTECTED]> wrote:
> >
> > > 32 times for each disk on booting with most of 30 disks.
> > > Possibly it's triggered by vinums drive scanning.
> >
> > Yep, same here (and it is triggered by
Joerg Wunsch wrote:
> Bernd Walter <[EMAIL PROTECTED]> wrote:
>
> > 32 times for each disk on booting with most of 30 disks.
> > Possibly it's triggered by vinums drive scanning.
>
> Yep, same here (and it is triggered by vinum).
>
> > What can I do about these messages?
>
> Remove it. It sho
;ACUERDO MOYANO-CAVALLO-DAHER
CONOCE UD. EL ACUERDO EXISTENTENTE ENTRE MOYANO, DAHER Y CAVALLO?
EL MISMO CONSISTE EN EL PARO PROGRAMADO PARA EL JUEVES.-
CON ESTE PARO, - QUE NO DEFIENDE PARA NADA LOS INTERESES DE LA CLASE TRABAJADORA
CAVALLO SE ASEGURA UN DIA "MUY NECESARIO" DE TRANQUILIDAD B
On Sun, Dec 09, 2001 at 01:38:03AM +0100, Dag-Erling Smorgrav wrote:
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> > des 2001/12/08 16:35:30 PST
> >
> > Modified files:
> > sys/fs/procfsprocfs.c procfs_ioctl.c
> > Log:
> > Fix various bugs in the debugging code an
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> des 2001/12/08 16:35:30 PST
>
> Modified files:
> sys/fs/procfsprocfs.c procfs_ioctl.c
> Log:
> Fix various bugs in the debugging code and reenable it.
>
> Revision ChangesPath
> 1.3 +0 -2 src/sys/
:boot block itself). The comments tell a bit more about it. But
:adding pointless messages that flush the boot log and possibly hide
:important boot messages can't be goo.
:
:--
:cheers, J"org .-.-. --... ...-- -.. . DL8DTL
Yes, Goo in the computer is wery, wery bad!
Bernd Walter <[EMAIL PROTECTED]> wrote:
> 32 times for each disk on booting with most of 30 disks.
> Possibly it's triggered by vinums drive scanning.
Yep, same here (and it is triggered by vinum).
> What can I do about these messages?
Remove it. It should not have been there in the first pla
* Alan Edmonds <[EMAIL PROTECTED]> [011208 17:42] wrote:
>
> Here's a data point for you Warner. I have an Intel PRO 2011
> 802.11b adapter (Symbol Spectrum24 OEM) card. Works just fine
> under -current and the wi driver. After a yesterday's rebuild
> I noticed the wi driver displaying this on
Here's a data point for you Warner. I have an Intel PRO 2011
802.11b adapter (Symbol Spectrum24 OEM) card. Works just fine
under -current and the wi driver. After a yesterday's rebuild
I noticed the wi driver displaying this on booting.
$ dmesg
FreeBSD 5.0-CURRENT #3: Sat Dec 8 19:32:20 GMT
As Ruslan Ermilov wrote:
> > You need to configure /some/ interface address for the remote end
> > anyway, and it must not clash with any other routing table entry,
> > since "ifconfig ... up" always adds an entry for the remote IP address
> > for p2p interfaces.
> Only if you have INET address
Mathieu Arnold wrote:
>
> Warner Losh wrote:
> >
> > 4.4-r -> current build is very broken right now. I'll investigate and
> > fix.
>
> last time I did it, I had a problem with install, adding LDFLAGS+=
> -static to src/usr.bin/xinstall/Makefile fixed the problem.
> the problem was using ins
On Sat, 8 Dec 2001 02:07:22 -0500, Jeremy Parker <[EMAIL PROTECTED]> wrote:
> I have also experienced this issue, caused me a lot of trouble. The only
> workaround I have figured out, is to bring up the interface with an IP
> address, then start dhclient and it seems to work.
>
> This is a ve
On Fri, Dec 07, 2001 at 09:01:12PM +0100, Joerg Wunsch wrote:
> As Ruslan Ermilov wrote:
>
> > > phk has chosen 0.0.0.1 since it obviously cannot be a meaningful
> > > statically configured address.
>
> > OK, but is it really necessary? It's much simpler to add routes
> > over P2P interfaces us
13 matches
Mail list logo
