[IPv6-only address above; strip the obvious for IPv4-only mail]
> > ...That is, your kernel can mount the NetBSD partitions with their 16
> > partitions within, even if `disklabel' doesn't work yet...
> Heh, I just mounted the NBSD partition using an un-patched FBSD kernel
> with GEOM, even thou
[IPv6-only address above; strip the obvious for IPv4-only mail]
> > We never had to ability to do this before. GEOM can probably do it for
> > you, with something like this patch:
>
> Oops. Now I get the same error with both kinds of partitions:
>
> disklabel: ioctl DIOCGDINFO: Operation not
Sorry to answer myself, but after a bit of free time to reflect on
this, I may as well talk back at myself. I wrote:
> Am I the only one getting duplicated #include lines in the generated
> ioctl.c file, created as part of building usr.bin/kdump?
YES!
> 27 #include
> 28 #include
[don't mail me, I'm going on holiday Real Soon Now again]
Am I the only one getting duplicated #include lines in the generated
ioctl.c file, created as part of building usr.bin/kdump?
Probably yes, because when I build things in other locations (I'm
using a MAKEOBJDIRPREFIX), I don't see the lin
> >> # diff -u2 /usr/src/Makefile.inc1.orig /usr/src/Makefile.inc1
> >> --- /usr/src/Makefile.inc1.origMon Apr 29 20:42:50 2002
> >> +++ /usr/src/Makefile.inc1 Tue Jun 25 20:05:28 2002
> >> @@ -402,9 +402,10 @@
> >> KRNLCONFDIR= ${KRNLSRCDIR}/${TARGET}/conf
> >> KRNLOBJDIR=${O
[This is an IPv6-only e-mail address, if you have any need to
respond to this and send me a copy but do not have IPv6-
capability, strip out the obvious part of the address, but I
follow the list archives so no need to mail me]
> > /usr/src/lib/libc/net/gethostbydns.c: In function `gethostan
to=ESMTP, daemon=MTA, relay=newman2.bestweb.net [209.94.102.67]
Note that the messages sent to the list have a different msgid than the
originals and are all [EMAIL PROTECTED]> .
I read this list via usenet, so here's relevant headers from a post
that ``I'' just made:
Original-Date:
I just wrote
> In case anyone else hasn't figured out why you're seeing a few old
> I read this list via usenet, so here's relevant headers from a post
Murphy's law. The news swerver I read from has stopped getting any
new articles after about three bestweb regurgitations, which I didn't
reali
Serwoas!
%s wrote on %.3s, %lld Sep 1993
> > Could it be due to the DDB, INVARIANTS & WITNESS options in the
> > kernel? If it is that's fine with me, I'm just wondering where
> > that magnitude of a slowdown would be coming from.
> WITNESS can really hurt. Quite possibly I should turn it off
If this might be of interest:
kernel built 07.feb
at boot time...
| Doing initial network setup: hostname.
* swi_net: unregistered isr number: 18.
| xl0: flags=8843 mtu 1500
| options=3
[...]
This is (probably) the dhclient being run at this time, maybe.
Should I be bothered by the foll
> > MODULES_WITH_WORLD=true # do not build modules when building kernel
> ^^^
> ...you need to read the option you enabled?
Never mind, I figured out what happened, and will happen again in
the future, since this doesn't quite `o
Is it just me, or...
I've changed my /etc/make.conf from the default, to be
MODULES_WITH_WORLD=true # do not build modules when building kernel
since I find myself often building new kernels (plus identical
modules) without updating the rest of the source, taking extra time.
I just finished the
Are the following lock order reversals something that I should mention
when I encounter them, in general?
On the other hand, this is from an older -current, built 25.Jan, before
which I don't see these messages, while after installworld/reboot, I
see them, except I haven't normally booted into -c
If this might be of interest:
kernel built 07.feb
at boot time...
| Doing initial network setup: hostname.
* swi_net: unregistered isr number: 18.
| xl0: flags=8843 mtu 1500
| options=3
[...]
This is (probably) the dhclient being run at this time, maybe.
Should I be bothered by the foll
> > MODULES_WITH_WORLD=true # do not build modules when building kernel
> ^^^
> ...you need to read the option you enabled?
Never mind, I figured out what happened, and will happen again in
the future, since this doesn't quite `o
Is it just me, or...
I've changed my /etc/make.conf from the default, to be
MODULES_WITH_WORLD=true # do not build modules when building kernel
since I find myself often building new kernels (plus identical
modules) without updating the rest of the source, taking extra time.
I just finished the
Are the following lock order reversals something that I should mention
when I encounter them, in general?
On the other hand, this is from an older -current, built 25.Jan, before
which I don't see these messages, while after installworld/reboot, I
see them, except I haven't normally booted into -c
Serwoas!
%s wrote on %.3s, %lld Sep 1993
> > Could it be due to the DDB, INVARIANTS & WITNESS options in the
> > kernel? If it is that's fine with me, I'm just wondering where
> > that magnitude of a slowdown would be coming from.
> WITNESS can really hurt. Quite possibly I should turn it off
[replies sent directly to me may timeout and bounce, since I'm not
online as often as I should be, but I'll check the list archives]
Aiee, aiee. One hardware-related failure resulted in the root
filesystem getting hosed, with trashed inodes for a couple
links, a couple empty directories, a cou
[replies sent directly to me may timeout and bounce, since I'm not
online as often as I should be, but I'll check the list archives]
I wrote a while back to freebsd-hackers:
> Is it safe (relatively speaking) to use the null and the union
> filesystems?
Well, so far I have had no serious probl
20 matches
Mail list logo
