I may have missed in the recent traffic on this list, but with the system svcup'ed on
11-Oct I am running into some problems with things network-related. In particular I
get:
WARNING: Driver mistake: repeat make_dev("net/xl0")
when I bring up a ppp link (with -nat and -auto parameters)
Then
> If you mean what I mean, that guy was Polish, and that stuff still sits in
> the tree:
Yeah, that was it, sorry - I'm always getting Germany and Poland mixed
up! No, not really, please don't hit! ;)
That's cool - I should look at this. A perfect excuse to pick up
forth again, I think.
- Jor
On Fri, 12 Oct 2001, Jordan Hubbard wrote:
> Cool! Committed to -current. Of course, this should really be rolled
> into the loader so that the sequence is more like this:
>
>
> Would you like to load any additional kernel modules (y/n)? y
> Please insert modules floppy and press return:
>
In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
: Cool! Committed to -current. Of course, this should really be rolled
: into the loader so that the sequence is more like this:
I actually like matsushita-san's patches too. Gives us more default
devices..
Warner
To Unsubscribe: send mai
Cool! Committed to -current. Of course, this should really be rolled
into the loader so that the sequence is more like this:
Would you like to load any additional kernel modules (y/n)? y
Please insert modules floppy and press return:
Please insert mfsroot floppy and press return:
That way
Hi,
just noticed a slight semantic change while using su:
Before pam, you can disable the wheel check if this group is empty.
Now this isn't possible any more.
I know I just could comment out pam_wheel from /etc/pam.conf but what
about the following solution:
Adding another flag for pam_wheel, w
On Fri, Oct 12, 2001 at 11:16:18AM -0700, David O'Brien wrote:
> On Fri, Oct 12, 2001 at 11:15:34AM -0500, Bob Willcox wrote:
> > I am interested in what is the best way to get a test system running
> > current? I have tried both upgrading from 4.4-stable (ran into kernel
> > build problems)
>
>
On Fri, Oct 12, 2001 at 11:15:34AM -0500, Bob Willcox wrote:
> I am interested in what is the best way to get a test system running
> current? I have tried both upgrading from 4.4-stable (ran into kernel
> build problems)
It would be nice to see the problems you experienced. One is supose to
be
The release notes for -CURRENT are a real mess. The current ordering
rule is something like "chronological ordering of items within a
section, but keep related items together". I've just begun converting
the release notes (one section at a time) to an alphabetical sorting (on
manpage references,
On Fri, Oct 12, 2001 at 09:20:35AM -0700, David Wolfskill wrote:
> Might help if you provided a pointer to the problems you had in the
> "upgrade from -STABLE" case. For that matter, a bit more detail on the
> "install failed to mount the filesystems" for the "install from -CURRENT
> snapshot" ca
Hi All,
I am interested in what is the best way to get a test system running
current? I have tried both upgrading from 4.4-stable (ran into kernel
build problems) and installing from the 5.0-20011011-CURRENT snapshot
(install failed to mount the filesystems). I decided that I would query
the net-
On Fri, 12 Oct 2001, Alfred Perlstein wrote:
> > The network is 100mbps, switched. To simulate load, I used a syn flooder
> > aimed at an unused port. icmp/rst response limiting was enabled.
>
> Actually, you might want to leave that on, it will generate more load.
I considered leaving it on,
Bruce Evans <[EMAIL PROTECTED]> writes:
> On 12 Oct 2001, Dag-Erling Smorgrav wrote:
> > Remove UCONSOLE from kernel config. This has been discussed to death
> > several times on the lists.
> That only prevents non-root from triggering the bug.
True. The only thing I know of that uses TIOCCONS
On 12 Oct 2001, Dag-Erling Smorgrav wrote:
> Doug Barton <[EMAIL PROTECTED]> writes:
> > Reported on 9/30:
> > panic: blockable sleep lock (sx) allproc @
> > /usr/local/src/sys/kern/kern_proc.c:212
> >
> > According to BDE, "This is a well-know bug in printf(9). The TIOCCONS
> > ioctl always gav
Robert,
the problem wan't with access(2) but with preceding setresuid(2)
calls. There was a false widening conversion taking place in
linux_uid16.c.
Various setXXid() calls allow the caller to set several ids at once,
or leave them unchanged by specifying the magic parameter -1.
Unfortunately u
On Thu, 11 Oct 2001, Jonathan Lemon wrote:
> >$FreeBSD: src/sys/pci/if_dc.c,v 1.56 2001/09/29 19:28:31 jlemon Exp $
>
> Can you back out this last change to if_dc, and see if that fixes the
> problem that you're having?
Yes, v1.55 of if_dc.c make my NIC back again.
To Unsubscribe: send ma
* Mike Silbersack <[EMAIL PROTECTED]> [011012 01:30] wrote:
>
> Well, I've been watching everyone argue about the value of interrupt
> coalescing in the net drivers, so I decided to port terry's patch to 4.4 &
> -current to see what the results are. The patch included applies cleanly
> to 4.4's
17 matches
Mail list logo
