of ram from malloc(9).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
In message [EMAIL PROTECTED], Alfred Perlstein writes:
* Poul-Henning Kamp [EMAIL PROTECTED] [030315 01:59] wrote:
In message [EMAIL PROTECTED], Alfred Perlstein writes:
Poul-Henning you promised me a patch two nights ago within a couple
of hours It's now going on the 36th hour since.
Ok
. I can see that powering down might
not do the disks any good.
Are you saying that you only tested vinums recovery with disks
which had been cleanly shut down ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
) doesn't exist and
setting dumpdev=ad0s1b in loader.conf doesn't help either.
Do you have any indication which device may be causing this ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
ticso tty 5, 1 Mar 14 14:50 1
crw--w 1 ticso tty 5, 1 Mar 14 14:50 2
d-w--- 1 root wheel 512 Feb 28 15:20 3
d- 1 root wheel 512 Mar 6 16:59 4
What is strange about it ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
In message [EMAIL PROTECTED], Bernd Walter writes:
On Fri, Mar 14, 2003 at 03:15:49PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Bernd Walter writes:
The /dev/fd content looks strange:
[160]cicely9# ls -al /dev/fd/
total 33
dr-xr-xr-x 2 root wheel 512 Mar 6 16:59
and a traceback ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
in jails.
Is there a jail devfs or is the way described in the
jail(8) man page still the right(tm) one?
See devfs(8)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
overlooked that devstat is not
locked when I moved the devstat to geom_disk.
Expect a patch tonight.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
/ken.patch
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
a gradient all the way from 0 to 70 C.
See:
http://www.corningfrequency.com/library/vig/Vig-tutorial_files/frame.htm
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
+0x5b
What does the output of ls -l /etc/malloc.conf look like?
This has nothing to do with userland, it's a kernel problem.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
, with the std{in,out,err} symlinks.
If we are required to do all filedescriptors, we should do so with
fdescfs by default.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
for additional fds accessible
from /dev/fd/* and build without that feature if not.
Well, as far as I know we don't need a patch, we just need to mount
fdescfs then.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
for reading:
fixes issues with apsfilter manual duplexing for me. could somebody
please commit this patch?
ping phk
I'm sort of expecting Bruce to commit his own patch ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
must have gotten lost then: Yes, it works for me.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
In message [EMAIL PROTECTED], walt writes:
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
Xint0x80_syscall() at 0xc02e2d2d = Xint0x80_syscall+0x1d
--- syscall (2), eip = 0x807ba9f, esp = 0xbfbff6bc, ebp = 0xbfbff6e8 ---
boot() called on cpu#0
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
/twe_freebsd.c
Index: dev/usb/umass.c
Index: dev/vinum/vinum.c
Index: geom/geom_disk.c
Index: ia64/ia64/autoconf.c
Index: ia64/ia64/sscdisk.c
Index: pc98/pc98/wd.c
Index: sys/ccdvar.h
Index: sys/disk.h
--
Poul-Henning Kamp | UNIX since
In message [EMAIL PROTECTED], Andy Farkas
writes:
I'll try and get some data for your clock/time tracking requests in a few
days. I assume you want wall-clock tracking info for both with and
without ntpd running?
yes.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
users
nor committers.
netns fails both criteria too.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
to the attic too ? Please ?
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
I've finished compiling my driver megacommit on i386, alpha and sparc64
and I will be committing the stuff shortly
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
In message [EMAIL PROTECTED], Poul-Henning Kamp writes:
I've finished compiling my driver megacommit on i386, alpha and sparc64
and I will be committing the stuff shortly
Done, you can take off your tinfoil hats now :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
In message [EMAIL PROTECTED], Bruce Evans writes:
On Sun, 2 Mar 2003, Bruce Evans wrote:
On Fri, 28 Feb 2003, Poul-Henning Kamp wrote:
My main concern would be if the chips have the necessary umphf
to actually do a real-world job once they're done running all the
overhead of 5.0-R
=CDEV_MAJOR,
+ .d_flags = D_MEM,
};
struct mem_range_softc mem_range_softc;
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
In message [EMAIL PROTECTED], Marcel Moolenaar writes
:
On Sun, Mar 02, 2003 at 09:14:13PM +0100, Poul-Henning Kamp wrote:
I plan to commit
http://phk.freebsd.dk/patch/cdevsw.patch
one of the first days of the week.
Basically, it changes cdevsw initializations to use C99 sparse
In message [EMAIL PROTECTED], Marcel Moolenaar writes
:
On Sun, Mar 02, 2003 at 09:26:31PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Marcel Moolenaar writes
:
On Sun, Mar 02, 2003 at 09:14:13PM +0100, Poul-Henning Kamp wrote:
I plan to commit
http://phk.freebsd.dk
,/* modevent */
ng_device_cons, /* constructor */
ng_device_rcvmsg, /* receive msg */
@@ -114,19 +114,14 @@
Damn, I thought I had caught that one.
Should be fixed now in the rev 2 of the patch I uploaded.
--
Poul-Henning Kamp | UNIX
suggested in a couple of weeks, then I think
those theoretical objections stand very weakly in the light of
proven reality :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
In message [EMAIL PROTECTED], M. Warner Losh writes:
In message: [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
: In message [EMAIL PROTECTED], John Baldwin writes:
:
: I personally think that we should not support the 80386 in 5.x.
: However when that has been brought
...
My main concern would be if the chips have the necessary umphf
to actually do a real-world job once they're done running all the
overhead of 5.0-R. The lack of cmpxchg8 makes the locking horribly
expensive.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
--- Forwarded Message
Return-Path: [EMAIL PROTECTED]
Date: Thu, 27 Feb 2003 05:19:48 -0500 (EST)
From: Geoffrey [EMAIL PROTECTED]
To: Poul-Henning Kamp [EMAIL PROTECTED]
Subject: Re: Volunteer with genuine i386 cpu lots of time wanted.
In-Reply-To: [EMAIL PROTECTED]
Message-ID: [EMAIL
/conf/majors for which there exists
no software, and convert drivers to use MAJOR_AUTO instead of using
static major numbers.
Thanks in advance!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
) During buildworld.
Please notice if
a) ntpd resorts to clock steps
b) ntpd exits
c) ntpd core dumps
Thanks in advance!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Xint0x80_syscall() at 0xc04084ad = Xint0x80_syscall+0x1d
--- syscall (6, FreeBSD ELF32, close), eip = 0x804afdb, esp = 0xbfbff81c, ebp =
0xbfbff828 ---
db
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since
0x1, eip = 0, esp = 0xd68b6d7c, ebp = 0 ---
db
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send
+0x257
Xint0x80_syscall() at 0xc026dabd = Xint0x80_syscall+0x1d
--- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x280c36bf, esp = 0xbfbffbec, ebp =
0xbfbffc08 ---
db
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
$?
1
syv#
That looks like a bug to me...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
mileage from the cn_arg field but I have not tried that.
Thanks in advance,
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
: No such file or directory
[...]
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
(desiredvnodes/2, M_MSDOSFSMNT, dehash);
mtx_init(dehash_mtx, msdosfs dehash, NULL, MTX_DEF);
return (0);
}
Somebody: please fix so this doesn't suck.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since
If somebody out there wonder how to make a contribution to FreeBSD
being a good curses programmer, I have the answer for you:
I could use some help with the user-interface side of some admin
tools for GEOM.
Apply in private email.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
I'm getting double-faults on my laptop, and I have managed to capture
them in DDB because I roughly know when to expect them.
But It seems that the panic and DDB offers absolutely no helpful
information about a double-fault ?
How does one debug problems like this ?
--
Poul-Henning Kamp
../../../dev/usb/usbdi.c 1034 Warning 548: else expected
../../../kern/kern_switch.c 448 Warning 548: else expected
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
#
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
() at Xint0x80_syscall+0x1d
--- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x805a8e7, esp = 0xbfbfe52c, e
bp = 0xbfbfe558 ---
db
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
I'm still not done with disklabel(8), and I have not run it through
all the tests I want (I'm waiting for my glacial 233MHz EV45 alpha
to compile a world) so be careful what you do with disklabel and in
particular the -B option.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
: passing arg 1 of `statclock_process'
from incompatible pointer type
*** Error code 1
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
, I will remove the NODEVFS and
NO_GEOM options from sys/conf on tuesday 28th january, and from
this date they will no longer be considered options in FreeBSD
-current.
After some $deltaT, probably two weeks, I will remove the code which
the removal of these options makes obsolete.
--
Poul-Henning
--- Forwarded Message
From: Poul-Henning Kamp [EMAIL PROTECTED]
Date: Sun, 19 Jan 2003 07:00:58 -0800 (PST)
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
phk 2003/01/19 07:00:58 PST
Modified files:
sys/sys ccdvar.h
sys/dev/ccd ccd.c
Log:
Finally
seconds sleeps if they are not
in sync as an incentive for people to upgrade.
Poul-Henning
--- Forwarded Message
From: Poul-Henning Kamp [EMAIL PROTECTED]
Date: Fri, 17 Jan 2003 06:53:53 -0800 (PST)
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: cvs commit: src/sys/dev/ccd ccd.c src/sbin
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
to profile multiple files, you just give them all the
same treatment as vfs_bio.
It's perfectly possible to profile the entire kernel if you want to.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
)
+#endif
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
(c01b0680,c14fbe80,d6985d48) at fork_exit+0xc4
fork_trampoline() at fork_trampoline+0x1a
--- trap 0x1, eip = 0, esp = 0xd6985d7c, ebp = 0 ---
db
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
-mcpu=pentiumpro -I/bang/src/usr.bin/kdump/../ktrace -I/bang/src/usr
.bin/kdump/../..-c ioctl.c
In file included from ioctl.c:93:
/usr/obj/bang/src/i386/usr/include/sys/diskpc98.h:47: redefinition of `struct do
s_partition'
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
, this is the first
comparison in this loop:
TAILQ_FOREACH(fp, ipq[sum], ipq_list)
if (ip-ip_id == fp-ipq_id
ip-ip_src.s_addr == fp-ipq_src.s_addr
ip-ip_dst.s_addr == fp-ipq_dst.s_addr
--
Poul-Henning
) {
stall(can't open %s: %m, name);
_exit(1);
}
(void) revoke(fd);
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what
Queueing Enable
d
da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
SMP: AP CPU #1 Launched!
Mounting root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
is a rather
obvious bug...
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
a very intrusive
probe function.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
== DT_LNK)
+ pname = de-de_dirent-d_name;
else
return (0);
KASSERT(pname != NULL, (devfs_rule_matchpath: NULL pname));
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
this hidden feature,
we should not do so by doubling the size of the table, but by
scanning it again looking for a match with the 0x10 bit flipped.
I will not even consider it until I get a patch implemented that way.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP
at this time. I have
copied Poul-Henning Kamp so that he can correct me if I am incorrect
on this point.
It is possible to boot UFS2 on i386, but the bootblocks are larger
than 8k and the foot-shooting potential is therefore over my threshold
for something I want to try to rush into 5.0.
The basic
, it is my intent to not install
BSD labels anymore, but switch to GPT instead, (possibly encapsulated
in an BSD MBR slice for legacy systems).
But lets burn that bridge once we have crossed it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
/share/mk/* could make it possible to simply write:
LOWWARNS= 3
To indicate that this program is WARNS clean _at least_ to level 3,
and always should be checked at 3 or above.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
! What in the hell could be causing
this? I'm tempted to point the finger at GEOM, but hate to say anything
like that.
I have absolutely no idea how this can happen, and would really
appreciate if people can try to find a way to reproduce it, I've
tried today and couldn't :-(
--
Poul-Henning Kamp
xor'ing with the hide-bit
and see if we then get a hit.
But as I said, this is rather marginal and I really don't feel
it should go in unless this xor-0x10 convention is more widespread.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
to this. I spent time getting rid of variant sized structs
in -current, and we should not reintroduce them.
If you wonder why this is important, think:
kld-load
and
forgetting the necessary opt_bla.h #includes.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
each and every non-static function in the kernel
and inserted an explicit assert on Giant, and then subsequently
removed them as we cleaned our way though the kernel.
Lets remember that next time :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
://2002.eurobsdcon.org/papers/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
about
signed/unsigned worries in the ufs related code.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
. contribute your scripts to do all this to the project :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
is incompatible
with the ``X'' option.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
This should fix a large part of the disklabel -e bogosity people
have been seeing.
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2002/11/20 12:12:52 PST
Modified files:
sys/geom geom_slice.c
Log:
Remember to update the providers idea of its size
defaults used.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
to fix if we move
devices from the vnode layer to the fdesc layer. A move which
increasingly is pressing its way up my TODO list.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
with the modification that the security-officer gang gets
to rule what exact m/o/g devices in the FreeBSD cvs tree should
have.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
In message [EMAIL PROTECTED], Anders Andersson wri
tes:
On Sat, Nov 16, 2002 at 04:52:57PM +0100, Poul-Henning Kamp wrote:
Boot with -v and look what geom tells you about your disk.
BIOS Geometries:
0:03fdef3f 0..1021=1022 cylinders, 0..239=240 heads, 1..63=63 sectors
0 accounted
In message [EMAIL PROTECTED], Anders Andersson wri
tes:
On Sat, Nov 16, 2002 at 05:06:50PM +0100, Poul-Henning Kamp wrote:
This is actually not from GEOM, look futher down...
There is nothing more related to GEOM, only ACPI and the stuff I already
pasted.
well: procfs registered
Timecounters
that the i8254 also runs twice as fast as it should ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send
, and i8254 does not seem to work.
And ACPI doesn't work either, right ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
/' a.c b.c
% gcc -O2 b.c
% ./a.out
12345678
56781234
Your code forgot to tell the compiler that you would be messing
with the variables storage directly.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3
. GEOM will become standard (ie: no disabling options).
2. Legacy code will be removed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
some pointers which have a correct value before and sudden=
ly
they got this odd 0xd0d0d0d0 value :/
When you have mistakes in your malloc(3)/free(3) handling.
See the malloc(3) manual page.
Try using electric-fence from the ports collection.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
In message [EMAIL PROTECTED], Takanori Watanabe writes:
In message [EMAIL PROTECTED], Poul-Henning Kamp wrote:
DEVFS:
3. major/minors will be dynamically assigned.
So we will need file to list node id list in printf(9) format,
instead of /sys/conf/majors.
I am not sure about this... [1
back to the previous
structure definition.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send
In message [EMAIL PROTECTED], Anti writes:
how are you supposed to get rid of devfs?
You're not.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
don't really have a chance to judge its correctness, so if you
think it is an improvement, you just commit it.
Thankyou very very much!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
In message [EMAIL PROTECTED], M. Warner Losh writes:
In message: [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
: In message [EMAIL PROTECTED], Takahashi Yoshihiro
: writes:
: The test program for libdisk is a failure in pc98 disks.
:
: I wonder at why pc98 disks don't
and no
hardware I can test on, so I am pretty unable to do anything sane.
Feel free to fix this and submit patches to me for review: I want
to make sure we don't adversely affect the platforms which work at
this late point i the release-process.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
utility of such archaic values
are to avoid breaking stupid firmware.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
In message [EMAIL PROTECTED], Nate Lawson writ
es:
It might be more useful for GEOM to query the BIOS for the physical values
and provide a way for upper levels (like CAM) to retrieve this.
This is a driver task. besides GEOM is above CAM, not below it.
--
Poul-Henning Kamp | UNIX since
In message [EMAIL PROTECTED], Nate Lawson writ
es:
On Mon, 4 Nov 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Lawson writ
es:
It might be more useful for GEOM to query the BIOS for the physical values
and provide a way for upper levels (like CAM) to retrieve
501 - 600 of 1643 matches
Mail list logo
