considerably less than a
millisecond wide.
Doing that from software practically rules out any high-level.
You might consider putting a PIC out there for the actual timing,
and having a control interface to it along the lines of "pulse this
line move ignition earlier, pulse that one and mov
ere is some kind of glitch somewhere when the TSC
>take over as timecounter?
Unlikely.
--
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
top all PHY drivers from calling MEDIAINIT, and
>call it once per miibus instance in miibus_attach() or miibus_probe()
>instead?
I just had reason to mess around with a PHY GigE related problem
as well, and I can only say that the MII code might have sounded
like a good idea at the time bu
Eventually vinum will either be absorbed into
GEOM as one class or (better) be implemented with a set of simple
classes in GEOM.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attrib
In message <[EMAIL PROTECTED]>, Miguel Mendez writes:
>Well, if you've used recent versions of the veritas volume manager
>fronted you'll notice that they give the cli command output in a window,
>that's what I intend to do.
They did that in 1994...
--
Poul-H
a program to list all the slices and partitions, because
>I couldn't find one already in existance. fdisk and disklabel only seem
>to work on one disk at a time, and I wanted to see everything.
Yes :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP s
involved that made the combination difficult. Perhaps
in the future).
--
Jaye Mathisen, COE Systems Manager(406) 994-4780
410 Roberts Hall,Dept. of Computer Science
Montana State University,Bozeman MT 59717 [EMAIL PROTECTED]
-
, D. M. Ritchie.
>
>They hacked the compiler to hack the passwd program when it was
>being compiled, and also to hack the compiler to include hacks
>to the compiler and the passwd program when the compiler itself
>was being compiled.
Sigh.
Wrong reference.
That was from Bri
In message <[EMAIL PROTECTED]>, David Schultz writes:
>Thus spake Poul-Henning Kamp <[EMAIL PROTECTED]>:
>> That was from Brians ACM Turning award thankyou-presentation.
>
>http://www.acm.org/classics/sep95/
Ahh, at least I got one more parameter right than Terry
of
>these features are extras, not the basics, correct? Other than SMP, of
>course.
It is the intent that GEOM will be standard (or basics if you like).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer |
In message <[EMAIL PROTECTED]>, j mckitrick writes:
>On Fri, Jun 07, 2002 at 02:44:27PM +0200, Poul-Henning Kamp wrote:
>| In message <[EMAIL PROTECTED]>, j mckitrick writes:
>| >| On the other hand, there are numerous new features (GEOM, TrustedBSD,
>| >| OpenPA
2f,0,0) at syscall+0x1db
>syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
>--- syscall (190, FreeBSD ELF, lstat), eip = 0x280b2f33, esp = 0xbfbff1ec, ebp -
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-hackers" in the body of t
I have a bunch of 8" floppies I need to try to recover contents
from, is there anybody out there who has a 8" drive they'd be willing
to part with for $$ ?
If it comes with the magic SA800-PC cable it would be just perfect.
Poul-Henning
--
Poul-Henning Kamp | UNIX since
In message <[EMAIL PROTECTED]>, Hellmuth Michaelis writes:
>Poul-Henning Kamp wrote:
>
>> I have a bunch of 8" floppies I need to try to recover contents
>> from, is there anybody out there who has a 8" drive they'd be willing
>> to part with for $$ ?
is an I belive it is actually the case on both
-current and -releng4 that disabling newreno improves TCP performance.
I belive running an X11 application or scp(1) over a wavelan is a very
good test-bed for this issue.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]
In message <[EMAIL PROTECTED]>, Michael Sierchio writes:
>Poul-Henning Kamp wrote:
>
>> Yes, I can attest to this an I belive it is actually the case on both
>> -current and -releng4 that disabling newreno improves TCP performance.
>>
>> I belive running
nsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-hackers" 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 attribut
",
>so after it finds the string it goes back to the first newline
>and returns the offset of the character after that. :(
Luigi, get in touch with W Gerald Hicks <[EMAIL PROTECTED]>,
he has patches which does this by objcopy'ing the binary file to
an elf-object and then lin
computers I run, and I need a
>reliable way to get passage of time (I don't need date/time, just
>the passage of it) for different internal operations in the program.
Use UTC time, it has no daylight savings problems.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTE
In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes:
>In message: <[EMAIL PROTECTED]>
> Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>: In message <005f01c22dd1$7be7d180$0300a8c0@fivehundred>, "Andrei Cojocaru" writ
>: es:
&
I think it is far too early
for an MFC. Suggest you provide a -stable friendly patchfile
until we have this issue settled in -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
they only available to the kernel. If so, how can I get a reasonable
>timer figure from user space?
There is no problem in making them available to userland, only the
question of which .h file to put them in and how to avoid breaking
some standard or other doing so.
--
Poul-Henning Kamp
k the forum would be interested as well.
I have yet to see a PC104 card which didn't support FreeBSD or (MSDOS 3.11
for that matter).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
I've started to type in my mental sticky notes, have at it:
http://people.freebsd.org/~phk/TODO/
--
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 wha
In message <[EMAIL PROTECTED]>, Maxim Sobolev writes:
>Poul-Henning Kamp wrote:
>>
>> I've started to type in my mental sticky notes, have at it:
>>
>> http://people.freebsd.org/~phk/TODO/
>
>Could you please modify reference to each of the t
D turned down because it was a pile of shit, and now you're
out to get revenge at the people who called you on your fraudlent
claims and made your the laughingstock of your equally loosing
#l33td00ds peers.
Here's a dime, get yourself a real OS.
You'd better tell your mom you've
t
correctly uses N/2^64 fractional the way binary computers prefer 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
d bintime, except that it
>:correctly uses N/2^64 fractional the way binary computers prefer it.
>:
>:--
>:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
>
>Hmm. That's certainly a reasonable point. I suppose a negative
>representation is still possible
bits in the kernel,
rather than have to s/time_t/time64_t throughout the kernel.
--
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
In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes:
>In message: <[EMAIL PROTECTED]>
>I think that this is a worthy problem to solve. But not for 5.0. [...]
Good thinking.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] |
t scan the CIS tuples for me and perform the appropriate allocations?
>If so, how do I get at the resource?
>If not, how would I go about doing this myself in the driver?
>And what would I want to put in my driver's xxx_probe() routine?
Suggest you look at the sys/dev/sio/sio_pccard
In message <[EMAIL PROTECTED]>, Bruce M Simpson writes:
>On Thu, Sep 05, 2002 at 09:22:11PM +0200, Poul-Henning Kamp wrote:
>> Suggest you look at the sys/dev/sio/sio_pccard.c file...
>
>I forgot to mention I'm working on -STABLE. =o)
"Don't", that'
In message <[EMAIL PROTECTED]>, Seva Tonkonoh writ
es:
>Hi,
>
>I have recently come across an old little discussion about InterMezzo.
>I 've got the impression that it wasn't really welcome to FreeBSD.
What is it ?
--
Poul-Henning Kamp | UNIX since Zilo
nt over the weekend.
>
>I'm very interested in comments and testing on -stable to help update the
>general architecture and stability.
IP-over-SCSI ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>
>
>On Sat, 7 Sep 2002, Poul-Henning Kamp wrote:
>>
>> IP-over-SCSI ?
>>
>
>Well I've just been reading about SCSI over IP so
That's different. IP-over-SCSI is a much wante
In message <[EMAIL PROTECTED]>, Nate Lawson wri
tes:
>On Sat, 7 Sep 2002, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Ju
>> lian Elischer writes:
>> >
>> >
>> >On Sat, 7 Sep 2002, Poul-Henning Kamp wrote:
>> >>
In message <[EMAIL PROTECTED]>, Bruce M Simpson writes:
>What I'd like to do is modify a Soekris net4501 for this.
There is a hardware watchdog in the Elan CPU used in the Soekris,
I plan to add support for it to the elan-mmcr driver when I get
a timeslot for it.
--
Pou
es or no? What is the desired behaviour?
No.
>The fact that this did work, was it a bug or did this come out due to some
>other change. The stacktrace from read(2) is below.
This hasn't worked for a long time in -current.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTE
In message <[EMAIL PROTECTED]>, Mark Santcroos writes:
>On Wed, Sep 25, 2002 at 07:41:44PM +0200, Poul-Henning Kamp wrote:
>> >The fact that this did work, was it a bug or did this come out due to some
>> >other change. The stacktrace from read(2) is below.
>>
crypt. The
>> logical choice is the device.
>
>Have you seen ports/security/vncrypt?
Or src/sys/geom/geom_aes ?
I have what I hope is industry-strenght encryption in my development
tree with only a few more issues to straigten out before it hits -current.
--
Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "Daniel O'Connor"
writes:
>On Thu, 2002-09-26 at 14:18, Poul-Henning Kamp wrote:
>> >Have you seen ports/security/vncrypt?
>>
>> Or src/sys/geom/geom_aes ?
>
>Whoo :)
>
>> I have what I hope is indust
le bit.
Geom will deal with all I/O requests as 64 bit byte offsets, so as such
GEOM will solve the problem, and provided the disk-driver authors
follow suit, this entire thing can be fixed before 5.0.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TC
;did't respond for unknown reason (busy?).
Hey easy now :-)
I'm discussing the issue with core@ right now, and if they agree
that this should go in the tree, I'll be your designated committer
for the first period of time.
Stay tuned, I'll get back to you when core@ gives me
n an
architecturally sane manner.
So they were removed, and good riddance.
If a buffered access-mode on block devices is desired, it should
be implemented either as an ioctl controllable feature, or as
a GEOM module. The latter is probably by far the easiest way.
--
Poul-Henning K
ired, and was sort of promised.
And we're close to the point where it can happen...
--
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 adequatel
27;t do it).
Man 4 geom is a good place to start.
There will also be a tutorial friday afternoon about GEOM
at BSDCONeuro2002 in amsterdam next month.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-t
In message <[EMAIL PROTECTED]>, Bakul Shah writes:
>Oh well.
>I am not going to argue about this over and over and over
>again.
Thankyou, a very wise decision sir!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
Fr
In message <[EMAIL PROTECTED]>, n0go013 writes
:
>On 04.10-18:27, Poul-Henning Kamp wrote:
>> In message n0go013 writes :
>> >On 04.10-15:40, fergus wrote:
>> > > On 04.10-14:20, Poul-Henning Kamp wrote:
>> > > [...]
>> > > > I
In message <[EMAIL PROTECTED]>, Lars Eggert writes:
>This is a cryptographically signed message in MIME format.
>
>--ms040706010906030302070807
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>
>Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>No, it is established principal tha the importer of new features has the
>responsibility to make older subsystems work.
I'm _so_ glad to hear _you_ say that:
When will you have made KSE work on sparc64 and ia64 ?
--
In message <[EMAIL PROTECTED]>, Daniel E
ischen writes:
>On Fri, 4 Oct 2002, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>, Ju
>> lian Elischer writes:
>>
>> >No, it is established principal tha the importer of new features has the
>
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Sat, 5 Oct 2002, Peter Wemm wrote:
>
>> Bruce Evans wrote:
>> > On Fri, 4 Oct 2002, Poul-Henning Kamp wrote:
>> >
>> > > Worst case you will have the option to use:
>> > >
>
will never notice
this and I'm just a old foghorn who doesn't know anything about
performance, but run a server where you actually have RAM pressure
and you might notice the difference.
Progress may be overrated, but it seldom goes too far...
Poul-Henning
--
Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, David Schultz writes:
>Thus spake Poul-Henning Kamp <[EMAIL PROTECTED]>:
>> In message <[EMAIL PROTECTED]>, David Schultz writes:
>>
>> >You can find a somewhat more thorough comparison of malloc
>> >implem
In message <[EMAIL PROTECTED]>, David Schultz writes:
>Thus spake Poul-Henning Kamp <[EMAIL PROTECTED]>:
>> >A harder problem to solve is fragmentation for long-running
>> >servers, where the RSS tends to creep upwards over time as virtual
>> >memory fills
you should add a flag
on the buf going down, saying "Never, ever retry".
--
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
somewhere.
I can't promise to fix all the issues which come up, but I will do my
very best...
--
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 a
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
.de writes:
>
>Is sysinstall still supposed to copy the contents of the mfsroot-
>image to /stand ? This at least results in two copies of sysinstall,
>one in /stand and the other one in /usr/sbin.
That is intentional
--
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
.de writes:
>On Tue, Oct 22, 2002 at 10:39:32PM +0200, Poul-Henning Kamp wrote:
>>
>> That is intentional
>>
>
>Is it ok then that the sysinstall in /stand of the 0917-JPSNAP
>immediately dumps core with s
o write to it before you find out that you can't.
--
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 Unsubscr
In message <[EMAIL PROTECTED]>, Hanspeter Roth writes:
> On Oct 29 at 18:34, Poul-Henning Kamp spoke:
>
>> That's a slightly more involved issue because you would have to
>> actually try to write to it before you find out that you can't.
>
>Isn'
In message <[EMAIL PROTECTED]>, David Schultz writes:
>IMO, the retry-forever bug is the
>real problem, but I'm a bit skeptical that it's easy to solve
>safely.
Just revert the commit which added it recently.
--
Poul-Henning Kamp | UNIX since Zilog Z
In message <[EMAIL PROTECTED]>, David Schultz writes:
>Thus spake Poul-Henning Kamp <[EMAIL PROTECTED]>:
>> In message <[EMAIL PROTECTED]>, David Schultz writes:
>>
>> >IMO, the retry-forever bug is the
>> >real problem, but I'm a bit s
quantam drives, the guy updated his
>firmware and it went away iirc. Does it do this only when you dump or
>under other circumstances? If other circumstances, which ones?
The fix is to not run dump(8) on a live filesystem. You should
either use a snapshot or umount the device.
--
Pou
d a problem. I was not aware of any snapshot feature
> available for 4.X-STABLE (only 5.0)?
It works most of the time, but not always. There is no way for dump(8)
to realize what has changed under its feet and therefore it sometimes
ends up with a bunch of negative blocknumbers.
--
P
In message , Rich Morin writes:
>My spouse had the problem of creating a bootable copy of A/UX on a
>single floppy. She decided to write a "doitall" program that had
>functionality from a number of small commands. This amortized the
>overhead a great deal.
man crunchgen.
on:
} else if (pti->pt_prison != td->td_ucred->cr_prison) {
return (EBUSY);
--
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
?
>:
>:There has always been code in kern/tty_pty.c which makes sure that the
>:master and slave have the same prison:
>:
>:} else if (pti->pt_prison != td->td_ucred->cr_prison) {
>:return (EBUSY);
>:
>:
>:--
>:Poul-Henning Kamp | U
KVM you need.
I don't really think running out of ptys is a problem compared to
other resource limitations (number of processes etc etc).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Nev
eral resource protection for jails: You can use up
any resource you can get your hand on: processes, disk, filedescriptors,
ptys, mbuf clusters, you name it.
If you want to add resource limitations to jails, then do it right from
the bottom, instead of as local hacks in random drivers or other hot
es, 10 hours in a car
and one hour by train, arrive totally wasted.
A big thanks from here to the organizers.
Next time seems to be 2003 in the US and then 2004 in Paris.
See you there !
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
Fre
;they did is entirely to them.
I'm pretty sure I heard them say that it was all your fault they
got started on this, but then again, I may be totally wrong.
>> Luigi@ had sent a part of his crew from Torino to talk about VPN
>> and other cool networking stuff in FreeBSD.
--
Poul-H
w doubt, that this works in the kernel case.
>
>So, is ${subject} usable on current or is it just a stale feature?
I havn't checked it lately, but it should be brought to work again
I think, it is a very valuable provider of insight into what code
is really executed.
--
Poul-Henning K
=476)
>at /usr/src/lib/libc/../libc/stdlib/malloc.c:1076
>#3 0x281885b5 in calloc (num=1, size=476)
>at /usr/src/lib/libc/../libc/stdlib/calloc.c:49
I think we can more or less conclude that something has trashed your
memory.
I'd suggest you try to run your program with Electri
But shouldn't you still be able to use the timer in the local apic ?
In message <[EMAIL PROTECTED]>, Ville-Pertti Keinonen writes:
>
>[EMAIL PROTECTED] (Poul-Henning Kamp) writes:
>
>> Somebody should study the abilities of the on-cpu APIC for this
>> for pentium
In message <[EMAIL PROTECTED]>, Scott Mitchell writes:
>Ugh. In that case, can someone back out Poul-Henning's changes to the
>if_xe.c in the -STABLE tree?
Uhm my change has not been applied to STABLE, but the 3.2-PAO import
references current rather than stable.
--
The point was who the heck sends the SIGHUP and why ?
Poul-Henning
In message <[EMAIL PROTECTED]>, Sheldon Hearn writes:
>
>[Hi-jacked from cvs-committers and cvs-all]
>
>On Wed, 21 Jul 1999 18:15:09 +0200, Poul-Henning Kamp wrote:
>
>> There is another one you may
cision and range could go hand in hand.
If we don't want to extend the size of the timestamps before 2038,
(and we should not only look at filesystems here), then the correct
fix will be to move the epoch and use the inode version to mark
this fact.
--
Poul-Henning Kamp FreeBSD cor
lso error routines, if
>> the exceptions were a problem it would would be trivial to fix.
>
>You would have to de-collapse several VOP lists that have been
>pre-collapsed.
You are talking gibberish here. Please show code where this is
a problem.
--
Poul-Henning Kamp Fre
s, or 292 (american) billion years. Current theories
>put the age of the universe at I think 12 to 16 billion years. So 64-bit
>signed times in seconds will cover from before the big bang to way past
>any time we'll be caring about. :-)
But we cannot do time in seconds resolution, we need
which used 32i.32f timestamps
and converted to timeval & timespec as needed and it actually made
a lot of code look a lot more sane. I may go back and do it some
day.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -curre
econd in the filesystems. Think about make(1) on
a blinding fast machine...
--
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 Unsubs
In message <[EMAIL PROTECTED]>, Julian
Elischer writes:
>On Wed, 18 Aug 1999, Poul-Henning Kamp wrote:
>
>> Matt doesn't represent the FreeBSD project, and even if he rewrites
>> the VFS subsystem so he can understand it, his rewrite would face
>> considerable
uff.
And what prevents you from taking over the default op ?
--
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-hackers" in the body of the message
cer
>
>How do I get a VOP, unknown to machine 2, from the vfs consumer
>on machine 1 that does know about it, to the vfs producer on
>machine 3 that also knows about it?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current
t this way.
>I'm a little surprised that there's any objection to the concept of
>mandatory locking.
Too many of us have had wedged systems because of it I guess...
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current o
f us have had wedged systems because of it I guess...
>
>Strange, I've probably used it more than anybody here, and I've never
>had a wedged system. Of course, you need to use it appropriately.
>'rm' can be a lethal tool :-)
Well, maybe you were more lucky, I've ha
econd in the filesystems. Think about make(1) on
a blinding fast machine...
--
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 Unsubs
In message <[EMAIL PROTECTED]>, Julian
Elischer writes:
>On Wed, 18 Aug 1999, Poul-Henning Kamp wrote:
>
>> Matt doesn't represent the FreeBSD project, and even if he rewrites
>> the VFS subsystem so he can understand it, his rewrite would face
>> considerable
which used 32i.32f timestamps
and converted to timeval & timespec as needed and it actually made
a lot of code look a lot more sane. I may go back and do it some
day.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -curre
uff.
And what prevents you from taking over the default op ?
--
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
is not significant, commit
>>that to. If it is significant, do more comprehensive testing on
>>what you have left over (i.e. that impacts existing builds) and
>>ask for another review after testing, before committing it.
>
>Erez.
>
>
>To Uns
In message <[EMAIL PROTECTED]>, Alfred P
erlstein writes:
>
>
>On Fri, 27 Aug 1999, Poul-Henning Kamp wrote:
>
>>
>> Uhm, have any of you actually ever looked at src/sys/kern/vnode_if.src ?
>
>I can't really tell if you are commenting on the diffs I p
be src/sys/crypto if we want to have
"kern-developer" still have a sensible meaning ? (and for
all the other reasons which made us move src/contrib/sys to
src/sys/contrib)
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -cu
s broken across multiple directories.
>
>Hmph. I guess common sense wins over ITAR in this case. :)
That's certainly an improvement in that particular battle :-)
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on
>But, unfortunately, putting the console on a serial port creates
>vulnerabilities when DDB is enabled. You are, essentially, creating
>an unintentional backdoor into the system. Hence the problem.
ports/*/conserver is your friend!
--
Poul-Henning Kamp
If you have access to a frequency counter it could be interesting to
measure the actual clockfrequency of the 14.318 MHz xtal in your
machine...
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
Fre
d that one. Will fix.
>Does anybody already encountered and solved problems described above
>or have an ideas ?
No, this is the first one I've heard about.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on the
In message <[EMAIL PROTECTED]>, Julian
Elischer writes:
>You have to examine ALL fd's in case one has a directory open that is
>outside the chroot..
>(see man fchdir(2))
We do. See source.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]
In message <[EMAIL PROTECTED]>, Julian
Elischer writes:
>I read it as her talking about chroot in general.
We do. See source. :-)
>
>On Mon, 27 Sep 1999, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>, Julian
>> Elischer writes:
>>
&g
501 - 600 of 654 matches
Mail list logo
