not work on SMP systems, including
multi-core laptops.
:-/
--
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], 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.
--
Poul-Henning Kamp
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 want to look at, I have not figured
psed.
You are talking gibberish here. Please show code where this is
a problem.
--
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 Un
ang to way past
any time we'll be caring about. :-)
But we cannot do time in seconds resolution, we need to resolve at least
the cpu clock frequency, which right now is approaching 1GHz (30bit!)
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "R
stacking layer (an NFS alternative), VOP's which
would normally be handled by vfs_default have to be handled on
the other end of the proxy, instead, in the same way that they
would be handled by the vfs_default stuff.
And what prevents you from taking over the default op ?
--
Poul-Henning Kamp
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 on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To U
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 on their laptop."
FreeBSD -- It will take a
' can be a lethal tool :-)
Well, maybe you were more lucky, I've had my share of troubles, and
I think the very concept stinks...
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will t
stacking layer (an NFS alternative), VOP's which
would normally be handled by vfs_default have to be handled on
the other end of the proxy, instead, in the same way that they
would be handled by the vfs_default stuff.
And what prevents you from taking over the default op ?
--
Poul-Henning Kamp
er testing, before committing it.
Erez.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-fs" in the body of the message
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
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 provided or
if you are commmenting on the comments I 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 -current on their laptop."
FreeBSD -- I
tories.
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 their laptop."
FreeBSD -- It will take
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.&quo
one I've heard about.
--
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 "unsub
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] "Real hacker
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:
You have to examine ALL fd's in case one has a directory
jail thing, but rather
make them inheritable like other credentials, so the structure
containing the stuff should hang of the proc structure, and hey
wait, we already have this "struct ucred" hanging there.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]
.
I agree, *IF* IPv6 ever becomes a reality, we will look at this.
(2)What is the goal of the restriction?
To isolate people in the jail from the "real" machine and from
other jails.
If physical level access protection is wanted,
it isn't.
--
Poul-Henning Kamp FreeBS
no futher than OSI ever did.
--
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 "unsu
for a long time as well, until the government
funded life-support was cut, then it evaporated overnight.
--
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
In message [EMAIL PROTECTED], Jamie Bowden
writes:
-security stripped
On Tue, 9 Nov 1999, Poul-Henning Kamp wrote:
:In message [EMAIL PROTECTED], Yoshinobu Inoue writes:
:(2)What is the goal of the restriction?
:To isolate people in the jail from the "real" machine and from
:o
functionality to jail(2), my point is
merely that until somebody who has sufficient time ability to
fiddle with it does it, it's not going to happen.
The usual rule applies:
"Great idea, why don't you send me patches which does this ?"
--
Poul-Henning Kamp FreeBSD coreteam mem
in a same jail
won't be necessariliy binded to a same address, but does it
matters?
Yes, that also matters, this is a administrative facility.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It
name internally and,
if A record is obtained, specify its address into "ip_number".
if record is obtained, also specify its address into "ip6_number".
Sure, this is trivial to do.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]
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
They die with the vnode
which maybe still die to fast.
Putting the inode with the data saves a little less than one diskaccess
on average per file, which for truly random access filesystems is a good
thing.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]
something they
can test, but let me know if any of you have lists of wanted features.
Poul-Henning
--
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!
In message [EMAIL PROTECTED], "Ray Hyatt Jr." writes:
Are you interested in external floppy drives with that type
of bus?
Not really. The intent of the driver is to interface to ascii
based test/lab equipment, not to apply for membership in the
antique hardware society :-)
--
Po
the AIX version was so hard to port that OSF eventually
had to give up trying. It was rather closely married to the VM
hardware on the Power CPU.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop.&quo
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-hacke
expensive. They only need
protection against the card itself, not against the entire system. It
just seems to be an overly large hammer.
I miss this too.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop.&quo
In message [EMAIL PROTECTED], Wes Peters writes:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Warner Losh writes:
I'd like to be able to do some simple spl locking in a driver that I'm
writing. While I could go the splhigh() route, I'm concerned that
spending lots of time
y add libz to the kernel.
We actually already have a unzip'er available in the kernel,
the one which was used for unzip'ing a.out executables.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD --
to be bothered by
routine driver maintenance.
While the card "works" you wont be able to set media-related features..so
you really do need the fix. I've successfully fixed our version and its
working nicely.I've forwarded the info to DG so hopefully it will be
patched soon.
DB
--
Po
In message [EMAIL PROTECTED], Dennis writes:
At 08:07 PM 3/27/00 +0200, Poul-Henning Kamp wrote:
Dennis,
You need to work with the maintainer of the driver on issues like
this, and as you have found out that is David Greenman.
Been there, done that...tired of waiting. What does one do when
you appear to have fixed the problems and updated the code,
would you like to submit it for review?
I would, except as we speak Poul-Henning Kamp is trying to have my posts
censored,so they dont seem to want my help.
I don't want them censored, I want the tagged ("Subject: [TROLL] bla bla
/banga/banga_html/banga.html
Is this relevant for FreeBSD ?
The problem: yes, the solution: maybe.
Other people have worked on an eventqueue based solution.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their l
In message [EMAIL PROTECTED], "David O'Brien" writes:
Access to ftp.internat.freebsd.org from the USA (and presumably
elsewhere) is an abomination. Isn't there *anyone* with an permanate FTP
server that could officially mirror the crypto bits from
ftp.internat.freebsd.org?
I may be able to
In message [EMAIL PROTECTED], "David E. Cross" writes:
I then used dump/restore to ensure that the
inode numbers would remain the same.
I don't think restore can preserve inode numbers.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP sin
mode is
pretty good for dial-up/demand lines.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send
d I belive the if_ar and if_sr
will as well.
If you are interested in a V.35 style sync card, I have one which
LMC (www.lanmedia.com) lent me, but for which I have not gotten
the driver converted to netgraph yet.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TC
gion, copy manually and release the old one?
Yes, we have no realloc(9).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by in
program to try and retrieve the values by calling
sysctlbyname (or sysctl if you know the OIDs).
... Or use
sysctl -b mumble.frotz | hexdump -C
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
st precise NTP stratum 1
servers in the world: +/- 20nsec.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To U
that military use is even better already, i.e. I just
imagine they are at 1m or less already.
Not quite, the military system is only better because it has two
frequencies, and that doesn't improve things *that* much.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
In message [EMAIL PROTECTED], Alexander Langer writ
es:
Thus spake Poul-Henning Kamp ([EMAIL PROTECTED]):
not supposed to know about how it works) which gives them an even more
interesting and powerful DOS on the GPS system. I doesn't quite work
by postal code, but it comes *very* close
coverage where you are.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
programs. There you will find both the environment and the
cmd line args.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be expla
more or les exactly
on the equator or one of the poles. Here where I live (56 north) about
30% of the sky is never covered by a satelite because of the inclination
of the satelites being non-zero.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
In message [EMAIL PROTECTED], Wes Peters writes:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Wes Peters writes:
: With 12-channel chipsets becoming common, new devices are getting quite
: good at this.
Yes. Most of the data I
that prefer the US?
Not really, but they don't bother going over the poles. Plot the orbits
based on the almanac and you can see the pattern.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
riend
on the other side of town" and the police then playing a GSM call and
showing the area where the phone could have been at the time of the call.
They need a court order of for both wire-tapping and getting hold of the
location information.
--
Poul-Henning Kamp | UNIX since Zilog
sense.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
serious problems, such as file descriptor
stealing (what happens when you roll the ref count to 0?). Any
objections?
Agreed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never
ss in the UNIX world is :-(
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Get the Fore PCA200 and use the "HARP" ATM code which is far more
functional than the "Chuck ATM" code.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribut
In message [EMAIL PROTECTED], Len Conrad wri
tes:
There was some talk about this back in March or so, leaving me rembering
someone said that it wouldn't be too hard or long to do it.
Has there been any progress?
I have still not received my hardware :-(
--
Poul-Henning Kamp | UNIX since
ng:
.
..
.ucbfoo
.attfoo
bar
and you were in universe "ucb" you would see:
.
foo
bar
where "foo" would take you to ".ucbfoo"
it was that simple.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[E
Can I use gettimeofday() inside kernel? if so why 3.3 is panicking? Ifnot
why 3.1 is not panicking?
It's called "microtime()" in the kernel.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since
and go away.
I understand it, and I think it sucks.
"Cogito ergo cogito ergo sum" as one of the fortunes claims with
little regard to latin grammer.
You forgot the bit about "shut up and go away" Dennis, despite
the fact that a fair number of people have asked you to.
You should make the exceeding of a quota a ipfw criteria rather
than an ipfw action, that way people can deny, drop, forward or DUMMYNET
packets exceeeding the quota.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member
all ip from any to any exquota guest
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
In message [EMAIL PROTECTED], Hans Huebner
writes:
On Wed, 7 Jun 2000, Poul-Henning Kamp wrote:
It should be possible to say say
ipfw deny all ip from any to any exquota any
as well as:
ipfw deny all ip from any to any exquota guest
Do you say that in principle
that can do fractional T1), they could part with for a good
cause, I would be most happy.
A V.35 CSU/DSU would be great but other devices can probably be
fit into my setup as well.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam
to be able to find certain
directories.
I had some fun with it when playing with a TOYFS of mine.
Take a peek in the libc sources, there are som assumptions which
may surprise you.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
are birds...
--
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 &q
times (e.g. programming language keywords).
And even then it's seldom worth it according to the people behind the LCC
compiler...
--
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], Josef Grosch writes:
Does anybody know of an EBCDIC to ASCII converter? I thought that at one
time FreeBSD had one of these.
man 1 dd
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
on your altitude and air pressure)
That is overlooking that the air rotates in mostly laminar fashion with
the platters, isn't 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
that qmail doesn't use fsync(2) as much as it should
:do. If that is true, then yes, softupdates would mean that a lot of things
:which qmail (mistakenly) think has been written are in fact not on the
:disk.
:
:--
:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
:[EMAIL PROTECTED] | TCP
, with any
:filesystem no matter how it is mounted (even sync mounted filesystems),
:is by calling fsync().
:
:So I would stick with softupdates.
:
:... provided that qmail calls fsync(2).
:
:--
:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
It doesn't matter whether qmail
I sat down and hacked a couple of shellscripts to give a basic
graphing of the interface trafic on a FreeBSD box without taking
the detour around SNMP.
The result is available here:
http://phk.freebsd.dk/IfTraf/
Enjoy,
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
? Is that file
obsolete, or do the warnings still apply?
I think that file is obsolete by now.
I also think we should make newfs turn softupdates on by default in
-current.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], Maxime Henrion writes:
What do you think of what NetBSD implemented ? softupdates is now enabled via
a mount option. This seems cleaner than the tunefs -n enable thing.
I have never understood why it was a tunefs thing...
--
Poul-Henning Kamp | UNIX since
In message [EMAIL PROTECTED], Peter Wemm writes:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Maxime Henrion writes:
What do you think of what NetBSD implemented ? softupdates is now enabled vi
a
a mount option. This seems cleaner than the tunefs -n enable thing.
I have
ug through which you can control the
probability in batch or realtime mode.
Either way, I'm not sure it belongs in phkmalloc()
--
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
this. There is no reliable way to associate
a call into the device driver with a particular file descriptor, and
in particular the driver cannot find out what happens in if dup(2)
is used.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
in
how many processes because neither dup(2) nor fork(2) result in
a (pseudo-)open call.
--
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
xplain why :-)
It is obfuscated 'C', but it is safe. The standard requires that
(void *) foo == (void *) foo-s and that if s were a complex
structure that it be laid out the same in all instances of s. So I
think that it is "safe" to do that.
Safe, but stupid, since type-safety is lost when doing
In message [EMAIL PROTECTED], "Jacques A. Vidrine" writes:
On Wed, Feb 21, 2001 at 05:13:35PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] "Jacques A. Vidrine" writes:
: Likewise if the first member were a mo
this warning means? What may be the effect of
this code when I shift it to kernel with due modifications?
It means that you do something like this:
...
p = malloc(n); /* N =2048 */
p += m;
free(p);
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
set some "silent-libc" or "libc messages go to logs" instead of
using stdout/stderr.
Since some time ago, there is an API to control how the messages
from malloc is output, look for "malloc_message" in malloc(3).
--
Poul-Henning Kamp | UNIX since Zi
incorporate that in your 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 [EMAI
errors, nfs servers going away, forced
unmounts).
--
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], Peter Seebach writes
:
In message 9402.983047348@critter, Poul-Henning Kamp writes:
Well, no, but the sole available definition of "portable" says that it is
"portable" to assume that all the memory malloc can return is really
available.
No, thi
In message [EMAIL PROTECTED], Peter Seebach writes
:
In message 9469.983047707@critter, Poul-Henning Kamp writes:
The guarantee is "If malloc returns NULL there is no memory you can use".
No, it's "if the memory is not available, malloc returns NULL".
No it is not and it ne
In message [EMAIL PROTECTED], Peter Seebach writes
:
In message 9631.983048712@critter, Poul-Henning Kamp writes:
No it is not and it never was.
The C committee believes it is.
The C committee doesn't deal with operating systems or the real world
for that matter. They only interest them selves
In message [EMAIL PROTECTED], Peter Seebach writes
:
In message 9820.983050024@critter, Poul-Henning Kamp writes:
I think there is a language thing you don't understand here.
No, I just disagree. It is useful for the OS to provide a hook for
memory which is *known to work
: 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 attribute to malice what can adequat
to help.
--
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 "unsubs
available? And (most important) one
which is supported by the necessary BSD drivers?
www.lanmedia.com, they have a T1/E1 card...
--
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
people who can fix it, but they cannot do anything if you
refuse to supply all the precise details in an easy to access form.
If you are unwilling to do that, then stop bothering us!
Indeed, I think Dennis could solve two problems by just dropping
FreeBSD right away.
--
Poul-Henning Kamp
that cyl 0-9 has
18 sectors while cyl10-81 has 21.
A small matter of hacking...
--
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
, unlike normal diffs.
Unified diffs are generally smaller than "plain" context diffs, and
some people find them more readable and some don't.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
with added emphasis:
Unified diffs are *also* context diffs.
Context diffs are named such because they contain undisturbed context
around the changed lines, unlike *normal* diffs.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
as closely as possible, including the fact that it may disappear
without notice or caution.
--
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
Shouldn't the FreeBSD project issue a press release welcoming
Apple's MacOS X ?
--
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], Robe
rt Watson writes:
On Sat, 24 Mar 2001, Kris Kennaway wrote:
On Sat, Mar 24, 2001 at 08:36:30AM +0100, Poul-Henning Kamp wrote:
Shouldn't the FreeBSD project issue a press release welcoming
Apple's MacOS X ?
Good idea, write one :-)
To be a really
1 - 100 of 606 matches
Mail list logo
