This patch is broken because it doesn't fix the comment, which should
read
... 4398 / 2048 is very close to ideal.
The commited version is better :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
error before `bsfl'
/usr/include/machine/cpufunc.h:72: syntax error before `mask'
/usr/include/machine/cpufunc.h: In function `bsfl':
/usr/include/machine/cpufunc.h:74: syntax error before `result'
...
I looked, apparently it doesn't like u_int. I don't know why.
Poul-Henning Kamp wrote
In message [EMAIL PROTECTED], Kyle Butt writes:
At Wed, 27 Mar 2002 10:49:15 +0100,
Poul-Henning Kamp wrote:
Uhm, I just whacked the code into my editor, you may need
more #includes like sys/param.h or sys/types.h
Thanks. That did the trick. Now how do I go about finding that
port
Can you put the file a place where I can fetch it ? my antique mailer
cannot seem to extract it from your emails...
--
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
kue # Kawasaki LSI USB ethernet
device pcm
device midi
device seq
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
In message [EMAIL PROTECTED], David Malone writes:
On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote:
This is an interesting machine: A K6 wiht ACPI, havn't seen that
before.
I had one of these machines and concluded that the ACPI time counter
was busted. I dunno
#define N 10
uint32_t h[N];
main()
{
FILE *f;
f = fopen(/dev/io, r);
memset(h, 0, sizeof h);
insl(PORT, h, N);
write (1, h, sizeof h);
}
--
Poul-Henning Kamp | UNIX
:95: dereferencing pointer to incomplete type
../../../dev/bktr/bktr_i2c.c:101: dereferencing pointer to incomplete type
../../../dev/bktr/bktr_i2c.c:103: dereferencing pointer to incomplete type
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
% with you.
In principle because I think only -RELEASE should not have J, and
I think even -RELEASE should have A.
In practice I think this is completely l00ney, considering what
we have done in the kernel, worrying about AJ related false hits
is sooo totally down in the noise.
--
Poul-Henning Kamp
for you to accept AJ
in the developer release ? Better diagnostics ?
--
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 say that I'm not going to do any of this, so
this will be my last email on the topic: Do whatever you think is
the right thing to do.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
architecture
to another and get at the slices/partitions etc.
This also means that I belive GEOM will DTRT for -current users for
a long stretch of the road, and would therefore encourage more
people to please test it out.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
scare if you feel like, and say that since this is
about trying out and testing, we have set these options to help
people flush out bugs.
The steady trickle of emails I receive about things exposed by AJ
is a clear indication that we need it on as much as possible.
--
Poul-Henning Kamp
or indirectly, provide feedback to DARPA.
I hope this answers the FAQ on UFS2, GEOM and all that.
--
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
: `ip6_protox' undeclared (first u
se in this 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
);
}
if (error) {
--
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
]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
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
that the people who are so much against P4 tell
us what the alternative they want us to use is ?
--
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
,cbb9ad24,c0331f84,cbb9ab00,c0331d60) at vmspace_fork+0x4d
vm_forkproc(c0332080,cbb9ab00,cbb9ac00,20014) at vm_forkproc+0xc6
fork1(c0332080,20014,c0332130) at fork1+0xd58
create_init(0,432c00,432000,0,c012368c) at create_init+0x17
mi_startup() at mi_startup+0x90
begin() at begin+0x43
db
--
Poul-Henning
. No. Yes :-)
--
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
the
removal od CSRG libm and the repo copying of msun
to libm; otherwise we'll drag CSRG libm around
until 6.0.
Good idea.
--
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], Alfred Perlstein writes:
* Poul-Henning Kamp [EMAIL PROTECTED] [020313 22:43] wrote:
But if somebody wants to try to code this optimization, I'll be more
than happy to review the result. I just don't expect it to do much
in real-life as opposed to silly
? :-)
And everybody with VM clue I've asked says it would be trivial to
flip two page-table entries, so for all I care it can be
mexchangemapping(void *from, void *to, size_t length)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
.
--
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
that optimization.
But if somebody wants to try to code this optimization, I'll be more
than happy to review the result. I just don't expect it to do much
in real-life as opposed to silly benchmark situations.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since
In message [EMAIL PROTECTED], Rasmus Skaarup writes:
On Tue, 12 Mar 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Carl Makin writes:
On Mon, 2002-03-11 at 06:34, Poul-Henning Kamp wrote:
The GEOM code is now ready for early testing:
Would GEOM support accessing a device
you want.
--
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
and MBR modules, you can see how they simply
tack a letter or s%d onto the name from below. There is nothing
to prevent you from creating an entirely new name if you want to.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
-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
free bug
From: Poul-Henning Kamp [EMAIL PROTECTED]
Date: Mon, 11 Mar 2002 23:13:57 +0100
Message-ID: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
As author of our malloc(3) it is my opinion that we are not vulnerable to
this (kind of) bug.
Most mallocs keep their housekeeping data right next
In message [EMAIL PROTECTED], Carl Makin writes:
Hi,
On Mon, 2002-03-11 at 06:34, Poul-Henning Kamp wrote:
The GEOM code is now ready for early testing:
Would GEOM support accessing a device via multiple paths? (ie could we
write a method that would do that?)
Yes, that would be possible
point at such a gem as: add locking to NFS which I am
sure John and the rest of us would love to see you tackle...
Give us peace Matt...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
-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
In message [EMAIL PROTECTED], David Malone writes:
On Sun, Mar 03, 2002 at 09:26:11PM +0100, Poul-Henning Kamp wrote:
I presume you'd push the rules in using sysclt or did you have
something more filesystem like in mind?
Nope, just a sysctl.
I guess then you just need a sysctl which lets
, it has the permissions I want, and not
necessarily the defaults.
The overall plan is that it will be possible to push a ruleset into
the kernel which changes the defaults. ETA: this summer (If I have to
do it, if somebody wants to help code it it can probably be done faster).
--
Poul-Henning Kamp
In message [EMAIL PROTECTED], David Malone writes:
On Sun, Mar 03, 2002 at 05:36:04PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Crist J. Clark writes
:
I've checked the manpages, the files in /etc, and Googled, and I can't
find the answer. I am begining to worry
more filesystem like in mind?
Nope, just a sysctl.
--
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
:394: `printcol' undeclared (first use in this function)
ls-unmain.c: In function `mastercmp':
ls-unmain.c:750: `namecmp' used prior to declaration
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
1 error
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
and some other random people we can think
of.
Sounds weird, doesn't it ?
I don't know what axe you are grinding Julian, but if you are not
the one to do the work, I don't think you are in a position to
ask for commit it now and have it fixed in situ.
Poul-Henning
--
Poul-Henning Kamp
, considering that you were
one of the first people to not show up for the SMPng work whereas
John has been consistently chugging along on the job all the way.
At this point in time, until he is officially unseated John is our
designated SMPng architect and his word is pretty final.
--
Poul-Henning Kamp
.
:
:--
:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
Oooh... so you mean that since I was working full time and unable
to contribute, somehow this disqualifies me now?
No, but it does make you, like the rest of us, underlings to John
architectural direction.
--
Poul-Henning Kamp
that it is process
and not tools at the heart of this problem.
In addition to process it might be attitude.
Core@ was not elected to be ornamental.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
a bunch of:
Feb 25 18:05:34 ogoun kernel: ACPI-0954: *** Error: AcpiEvGpeDispatch: Unable to
queue handler for GPE[0], disabling event
The ACPI code was updated a few days ago, these problems are probably
caused by that.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
]:/usr/obj/usr/src/sys/GENERIC i386
Last make world: Feb 24 20:00
Cheers!
Regds,
Frode Nordahl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP
/acd0 doesn't.
So we have two unrelated problems here:
1.) getdiskbyname() panics the system if the device exists.
2.) getdiskbyname() doesn't work for acd0c.
Any clues how to fix?
No trivial fixes. New code (GEOM) will replace this entire mess
soon.
--
Poul-Henning Kamp | UNIX since Zilog
, resume, IOPL = 0
current process = 0 (swapper)
kernel: type 12 trap, code=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
:
On Tue, 26 Feb 2002, Poul-Henning Kamp wrote:
please send me /var/run/dmesg.boot from a boot -v on a current kernel
and output from sysctl kern.timecounter please ?
$ sysctl kern.timecounter
kern.timecounter.nmicrotime: 3838
kern.timecounter.nnanotime: 3
kern.timecounter.nmicrouptime: 1
:
} while (u1 u2 || u2 u3 || (u3 - u1) 15);
Hopefully this commit fixes the timecounter backwards problem
with broken ACPI timers, if not, let me know.
Enjoy,
Poul-Henning
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2002/02/25 01:51:18 PST
Modified files
, if the drivers are not fixed by may 1st
the HARP ATM stack will be put in the attic.
If anybody is interested in actively maintaining this code, I may be
able to find a donor for some ATM cards.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
of the message
--
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
Ok, found it:
This is the culprit:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/file.h.diff?r1=1.39r2=1.40
In message [EMAIL PROTECTED], Poul-Henning Kamp writes:
Yeah, I'm chasing that one right now.
I'm not yet quite sure which commit has broken this, nor what the right
fix
changes, etc,
only when the work is ready to commit.
Panic: recursion: commit only when ready to commit
Doesn't this one hinge on the stability/compilability goal of current
and only that ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since
of PIXX
made it go away so I am not entirely convinced this is really what
we are looking for in this case.
--
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
clock code.
If this patch cures the PIIX problem, something I'm not at all convinced
about, it should go in, if not only the comment should go in.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
{
tc = timecounter;
gen = tc-gen;
...
} while (gen != tc-gen);
--
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
;
+acpi_timer_timecounter.tc_get_timecount = acpi_timer_get_timecount_safe;
acpi_timer_timecounter.tc_frequency = acpi_timer_frequency;
tc_init(acpi_timer_timecounter);
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
:...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
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
it, that would be much better.
Holy shit. We are screwed. It's a free-running counter with NO
synchronization whatsoever. None. Zip. Zero.
Yes, there is an errata for just that on early chipsets.
Does the ..._slow patch I sent work for you ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus
source tree here.
Thanks to peter for fixing this, and sorry for the trouble!
--
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
that entire area of the code which will
help immensely :-)
--
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
source tree here.
Thanks to peter for fixing this, and sorry for the trouble!
--
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], Kenneth D. Merry writes:
Is there a way, under -current or -stable, to make a true RAMdisk that is
around 2GB in size?
Possibly. If you take the detour around a preloaded image for the md(4)
driver it should be possible.
--
Poul-Henning Kamp | UNIX since
of all minor devices on the disk when the first
one is opened.
Yeah, I admit I've been sitting on these patches for a bit too long,
I'll try to get through my pile and get to them.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
sys/dev/ccd/ccd.c:ccdinit() has a couple of very large items on
the stack.
Rewrite ccdinit() to allocate them with MALLOC(9) instead.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
belive the
rule-of-thumb is that nothing should remain allocated by the time
we return to userland.
--
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
In message [EMAIL PROTECTED], Maxim Konovalov wr
ites:
Ohh and I forgot: Thanks for the patch! Tested Committed :-)
--
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
be unaffected and still pass RB_HALT|RB_POWEROFF when invoked
as halt -p.
What do others think of this change:
Sounds reasonable.
--
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], Martin Blapp writes:
Hi all,
ftp://ftp.suse.com/pub/people/andrea/lil
Maybe we can port this and use it to see where the
latency actually happens ?
Doing something like that wouldn't be a bad idea.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
been signing their copyright over to FSF for a long
time...
--
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
My buildworld breaks:
[...]
/flat/src/gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c:52: machine/globaldata.h: No
such file or directory
Any workarounds/fixes ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
.
--
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
PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
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
not exist.
I'm sure there is a connection somewhere...
--
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], Poul-Henning Kamp writes:
=== usr.bin/tip
install -c -s -o root -g wheel -m 555 tip /flat/syv/usr/bin
/flat/syv/usr/bin/cu - /flat/syv/usr/bin/tip
ln: /flat/syv/usr/bin/cu: Operation not permitted
*** Error code 1
flat# ls -l /flat/syv/usr/bin/cu
-r-sr-sr-x 1
, that is the way to do it.
--
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
, but offered as a
HEADSUP for people to test the effect of the actual patch on
their systems.
The actual patch will remove the entire cdevsw_add() family.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
In message [EMAIL PROTECTED], Jos Backus writes:
Hi Poul-Henning,
On Wed, Oct 31, 2001 at 07:38:56PM +0100, Poul-Henning Kamp wrote:
Make sure you have rev 1.46 of sys/kern/subr_disk.c and 1.100 of
sys/kern/kern_conf.c
In other words: the latest.
I know, and I do.
OK, so far so
somebody
fixes its use of destroy_dev()
--
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
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED], Mike Silbersack
writes:
Oops, error on my part; /proc does need to exist. So, I guess the
question is this: Can devfs's error handling in the case of /dev
-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
In message [EMAIL PROTECTED], Mike Silbersack w
rites:
On Sat, 27 Oct 2001, Poul-Henning Kamp wrote:
Oops, error on my part; /proc does need to exist. So, I guess the
question is this: Can devfs's error handling in the case of /dev being
non-existant be improved?
Barely, because without
In message [EMAIL PROTECTED], Garrett Wollman w
rites:
On Sat, 27 Oct 2001 11:32:07 +0200, Poul-Henning Kamp [EMAIL PROTECTED] said:
Right, but the only way to get an error message is to let /sbin/init
die and have the kernel print the message. /sbin/init cannot
print the message when
In message [EMAIL PROTECTED], Chad David writes:
On Fri, Oct 19, 2001 at 05:00:16PM +0200, Poul-Henning Kamp wrote:
Sounds like the bug is the md driver cloning md10ec which it shouldn't
do. This bug must naturally be in md_clone(), but I don't have the
minutes right now to hunt it down
in the correct place. Any advice would be very welcome.
--
Chad David[EMAIL PROTECTED]
ACNS Inc. Calgary, Alberta Canada
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
with the above comment. Is this
a bug introduced in rev 1.67, or is it the intended new behavior and
the comment is out of date?
Actually, I think this is consistent, since console messages is now
also put in the buffer, but I am not 100% sure...
--
Poul-Henning Kamp | UNIX since Zilog Zeus
hardlinks
--
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
Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
in the kernel where VT_* macros are
[ab]used - it is Linuxlator, attached please find patches to fix it - please
review.
Sounds like a plan, and a quick eyeball of the patch shows no trouble.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP
In message [EMAIL PROTECTED], Peter Wemm writes:
Poul-Henning Kamp wrote:
You are not supposed to call __getcwd() directly.
Yes, but it would be an excellent junior-kernel-hacker task to make it work
in all cases, ie: manually searching parent directories. netbsd does this,
as does linux
that, but rather a descriptive string, i.e.
No actually not, I want something short and predictable like
VT_CODA.
--
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
() doesn't work right on devfs directrories (_PC_NAME_MAX and
_PC_PATH_MAX are unsupported, but must be supported for directories).
OK, that's a bug.
- acd devices still have insecure modes (world readable).
That is not a fault in DEVFS but in the driver.
--
Poul-Henning Kamp | UNIX since
to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
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], David O'Brien writes:
On Tue, Sep 04, 2001 at 01:33:30AM -0700, Poul-Henning Kamp wrote:
phk 2001/09/04 01:33:30 PDT
Modified files:
sys/dev/ccd ccd.c
sys/modules/ccd Makefile
sys/sys ccdvar.h
Log:
Kill
to make DEVFS entirely mandatory.
--
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
utterly unique, a decision of even more
questionable wisdom.
And just for the record: PERL is right out (of space) for this purpose...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
.
The v_tag has been abused a few places, easily recognizable by the fact
that the kernel should never inspect the value of v_tag.
These places should be easily changeable to use the new representation.
Please mark them with a big fat /*XXX: ABUSE OF v_tag */ comment.
--
Poul-Henning Kamp | UNIX
In message [EMAIL PROTECTED], Maxim Sobolev writes:
Attached please find regenerated diffs.
Committed, well done, thanks!
--
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], Maxim Sobolev writes:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Maxim Sobolev writes:
Attached please find regenerated diffs.
Committed, well done, thanks!
Nice to hear. It seems that you forgot to commit ccdconfig(8) part of the
patch. 8-)
Yeah
In message [EMAIL PROTECTED], Brent Verner writes:
On 04 Sep 2001 at 10:36 (+0200), Poul-Henning Kamp wrote:
|
| Assignment:
|
| The v_tag element in struct vnode is a debugging aid, but unfortunately
| it is implemented in a way which means that adding a filesystem means
| modifying
;
}
bzero((caddr_t)ldep, sizeof *ldep);
+ nvp-v_flag |= VLOCKABLE;
lockinit(nvp-v_lock, PINOD, denode, 0, 0);
nvp-v_vnlock = nvp-v_lock;
nvp-v_data = ldep;
--%--multipart-mixed-boundary-1.97537.999617732--%--
--
Poul-Henning Kamp | UNIX since Zilog
801 - 900 of 1643 matches
Mail list logo
