bump, and therefore -core hereby gives David O'Brien
permission to do so.
for -core,
Poul-Henning Kamp
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before pro
In message 02d801bf3132$71f6f8c0$[EMAIL PROTECTED], "David W. Chapman Jr.
" writes:
Any idea of when 4.0-RELEASE will be out, in terms of months or years?
Feature freeze in this year. Release in Q1/2000.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL
|
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time
the ex0 and ie0 drivers in userconfig
but that is no longer possible it seems.
Anyone know enough about how userconfig works these days to fix this ?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop.&quo
the ie0 driver in visual mode...
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
hard-hat in this
email or not, and I see some quite divergent australian positions,
so I will sit tight until I see a little bit more of a consensus.
Poul-Henning
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their l
(as opposed for the gadget/novelty thrill or
testing purposes) ?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe:
explain the logic you want implemented once people have
stopped haggeling about it, it is rather trivial.
I pressume we want the same policy for /proc/*/cmdline as for the
sysctl ps(1) uses ?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hacker
I still hear reports of sporadic calcru() warnings.
If any of you see these, could you try to see if they correlate
to the uptime of the machine in question ?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their l
Is this SMP ?
In message [EMAIL PROTECTED], N writes:
Poul-Henning Kamp wrote:
I still hear reports of sporadic calcru() warnings.
If any of you see these, could you try to see if they correlate
to the uptime of the machine in question ?
Should they start or stop when a machine has been
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
In message [EMAIL PROTECTED], Assar Westerlund writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
Don't use the generic kernel unchanged with the 3com card.
Disable the ex0 and ie0 drivers, one of those pummel the 3com
cards magic config registers.
Tack. Now it manages to find ep0
f_ex/if_ie and
I'll add that to my list of things to look at when I get a chance to fix a
few outstanding issues with if_ep.
Can we somehow mark the if_ep as "fickle hardware" so it gets probed
before the if_ex/it_ie ? We used to have such a facility.
--
Poul-Henning Kamp Fre
In message [EMAIL PROTECTED], "Matthew
N. Dodd" writes:
On Fri, 26 Nov 1999, Poul-Henning Kamp wrote:
Can we somehow mark the if_ep as "fickle hardware" so it gets probed
before the if_ex/it_ie ? We used to have such a facility.
I'm going to look closer at those
In message [EMAIL PROTECTED], Greg Lehey writes:
On Wednesday, 24 November 1999 at 10:39:44 +0100, Poul-Henning Kamp wrote:
So I would like to propose that we discontinue support for ST-506,
ESDI disks and BAD144 bad-sector remapping starting with the 4.0
release.
So, is anyone running
b
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Poul-Henning Kamp
() at begin+0x4b
Also, further back in the log there's a "setrootbyname failed".
Somehow, and there are a fair number of ways this could happen,
you ended up without a root device.
What is in your /etc/fstab for the root fs ?
Is your /boot up to date ?
--
Poul-Henning Kamp
Do you have /dev/sd* in your /etc/fstab ?
It should be changed to /dev/da*
In message [EMAIL PROTECTED], Manfred Antar writes:
At 09:29 PM 11/29/99 +0100, Poul-Henning Kamp wrote:
Manfred,
Could you send the 10 lines surrounding the address 0xc014a79a
from the output of "nm -n /this_k
explodes when it can't find /, rather than
giving up cleanly.
devsw(NODEV) bombs.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To U
although it is hard to figure out just
exactly what is needed to "run one's system".
Maybe a "remake" entry in MAKEDEV which remakes all current entries
if possible.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real h
)
cannot get out of single user mode. fsck core dumps. Any failed command
causes the single user shell to exit.
This doesn't sound like a /dev related problem to me.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their l
took out a testing-shim a little early which
allowed us to test with /dev/r* in /etc/fstab. Change your
/etc/fstab to read /dev/ad0a and you should be happy again.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their l
if=/dev/ad0 bs=1k count=64 | uuencode ache.ad0
--
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], Maksim Yevmenkin writes:
the question is: are options GEOM and NODEVS compatible?
No, they are 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
/share/man/man3
install -o root -g wheel -m 444 com_err.3.cat.gz
/R/stage/trees/base/usr/share/man/man/cat3/com_e
rr.3.gz
install: /R/stage/trees/base/usr/share/man/man/cat3/com_err.3.gz: No such file or
directory
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
.
--
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
/obj/usr/src/secure/usr.sbin/sshd/../../../kerbe
ros5/lib/libroken -lroken -lopie -lmd -lssh -lcrypt -lcrypto -lutil -lz -lwrap -
lpam
auth1.o: In function `do_authloop':
auth1.o(.text+0x220): undefined reference to `mm_auth_krb5'
*** Error code 1
1 error
*** Error code 2
--
Poul-Henning Kamp
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
auth1.o: In function `do_authloop':
auth1.o(.text+0x220): undefined reference to `mm_auth_krb5'
*** Error code 1
1 error
*** Error code 2
You must have cvsupped at a bad time - looks like
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
You must have cvsupped at a bad time - looks like you missed the three
Makefile deltas in src/secure.
I just started over, and cvsup
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
Inside the chroot.
'make release' checks out src in the sandbox, then chroots to it and
does a plain 'make world' right? There's no chance the sources in the
sandbox were stale
Makefile.inc1 par-cleandir
=== kerberos5
=== lib/libpam
=== lib/libssh
cd: can't cd to /usr/src/lib/libssh
=== secure/usr.bin/ssh
*** Error code 2
=== kerberos5/doc
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since
: initialization from incompatible point
er type
*** Error code 1
Stop in /usr/obj/usr/src/sys/GENERIC.
*** Error code 1
Stop in /usr/src.
*** 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
=
Hi Craig,
Can you please email me:
boot -v console output (use serial console if you can)
sysctl -n kern.geom.confxml
Thanks in advance!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], Craig Rodrigues writes:
--qDbXVdCdHGoSgWSk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Oct 31, 2002 at 04:56:49PM +0100, Poul-Henning Kamp wrote:
Can you please email me:
boot -v console output (use serial console if you
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2002/11/01 07:32:12 PST
Modified files:
sys/fs/specfsspec_vnops.c
Log:
Put a KASSERT in specfs::strategy() to check that the incoming buffer
has a valid b_iocmd. Valid is any one of BIO_{READ,WRITE,DELETE
.)
--
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
etc)
This will show you what the libdisk library thinks about your disks.
I'd like to see the output, along with the output from:
sysctl -n kern.geom.conftxt
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
In message [EMAIL PROTECTED], Frode Nordahl writ
es:
The nasty part:
- fdisk showed all partitions as type 165 (FreeBSD), I took a chance and
continued anyway. Now my two non-FreeBSD partitions are lost :)
Fixed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
machine and the same devices. So why do they probe
wrong?
I have no idea either, but the answer must be somewhere in the da driver...
--
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 a priority, propagate that priority down to the device
drivers and act accordingly in the disksort disk-scheduling code.
That would allow us to address not only the bgfsck but also things
like silly-seek-syndrome and other sub-optimal issues in our current
I/O system.
--
Poul-Henning Kamp | UNIX
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
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
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
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
. 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
/' 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
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
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
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
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
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
. 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
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
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
/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
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
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
-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
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
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
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
) {
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
, 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
-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
(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
)
+#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
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
-mail address as password.
Password:
530 Login incorrect.
ftp: Login failed.
That usually means that Jordan has left the country and isn't reachable
for at least a week...
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -cu
critizisms of it.
You are preaching to a very seasoned choir here...
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe:
and reported to peter who fixed it a few hours ago.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL
output. Lemme know what you
think.
BTW, I'm also in the middle of writing a prepdisk script that uses
fdisk and disklabel to properly and easily label a disk for use under
FreeBSD.
Please look at the script I wrote for the doc2k device, it is in
src/sys/contrib/dev/fla
--
Poul-Henning Kamp
:
30C + 60C - 25C = 65C
We just raised our CPU temperature about 15 C :-(
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress go
with ENOCANDO ?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
al/sbin
PERLLIB=/data/ricardo/perl:/home/iang/src/hayek/ricardo/blib/lib
PERL_BADLANG (unset)
SHELL=/usr/local/bin/bash
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Poul-Henning Kamp FreeBSD corete
);
#
# Damn, FreeBSD throws Floating Point Exception on NaN!
#
my $long = unpack("N", $data);
if ($long == 2143289344)
{
return "NaN";
}
That is not enough, NaN has multiple binary representations.
isnan(3) is your friend.
into a new
struct buf field called b_iocmd.
This patch is the first step towards the stackable BIO system as
sketched out on http://www.freebsd.org/~phk/Geom/
Please test review.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current
isable APM in your bios and remove apm from your config.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail
e to adopt to much worse things
before it becomes 5.0-RELEASE.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail
just as efficiently be done by comparing b_iodone to NULL.
Should you get a panic or drop into the debugger, complaining about
"b_iocmd", don't continue, it is likely to write where it should
have read.
Please test review.
--
Poul-Henning Kamp
.
I tried to newbusify if_mn.c, but after having added about 50 lines
of code to replace the current about 10, I gave up.
We need a highlevel wrapper for newbus before we should force people
to upgrade the old-style drivers.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL
Kirk and I have already mapped out a plan to drastically update
the buffer cache API which will encapsulate much of the state within
the buffer cache module.
Sounds good. Combined with my stackable BIO plans that sounds like
a really great win for FreeBSD.
--
Poul-Henning Kamp
for
much of their naming management. This is currently impossible.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe:
ge-aligned.
No protest from here. Encouraging people to think about their data
and the handling of them will always have my vote :-)
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will tak
n.
I seem to remember Bruce saying that clustering could even hurt ?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe:
101 - 200 of 1643 matches
Mail list logo
