Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Oct 2002 15:07:23 -0700
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Brooks Davis <brooks@one-eyed-alien.net>
Cc:        Bakul Shah <bakul@bitblocks.com>, Dave Evans <devans@hclb.demon.co.uk>, freebsd-current@FreeBSD.ORG
Subject:   Re: pppd not working on latest current 2002-10-20
Message-ID:  <3DB9C09B.2190472E@mindspring.com>
References:  <20021025113137.A23521@Odin.AC.HMC.Edu> <200210251841.OAA09782@valiant.cnchost.com> <20021025123522.B23521@Odin.AC.HMC.Edu> <3DB9A281.6FE378F5@mindspring.com> <20021025130909.B7985@Odin.AC.HMC.Edu> <3DB9AD0D.E1C553D7@mindspring.com> <20021025145702.A19646@Odin.AC.HMC.Edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote:
> On Fri, Oct 25, 2002 at 01:43:57PM -0700, Terry Lambert wrote:
> > It's a moderately common case in -CURRENT, when kernel structure
> > sizes change, and you build a new kernel without new modules, and
> > a module refuses to load.  It's not technically correct.  The old
> > message might not be either, but at least it had you looking in
> > the right place.
> 
> Current users are supposed to have enough of a clue to figure this out.
> Other users are supposed to follow the instructions in UPDATING which
> preclude this problem.  The version of pppd built with my patch basicly
> keeps the only part of the old message was correct (telling you that you
> don't have kernel support).  The second sentence of the description is
> entierly unhelpful since README.bsd isn't anywhere in our source tree.

Heh.

You might as well just exit, and assume that whoever sees it not
running should have enough of a clue to know why it exited.  8-).

The only failure mode that gets to the end there is the module not
loading, and the error is not indicative of the load failure, was
all I was saying.

Like I said, it's an OK change (at least if it's OK for ifconfig
and mount to load modules, instead of the demand causing the kernel
to load them), it's just a bit light on the error message.

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB9C09B.2190472E>