On 09-Sep-99 Jason Young wrote:
After some thought, I think the mount option idea is best. I hadn't
thought of that before. One might want to apply different procfs
security policies to different mounts of procfs, especially in a
jail() situation. Good call.
Yeah, you'd have to make
Nate Williams [EMAIL PROTECTED] writes:
Nate: it's a while since I looked at VM on XEmacs. I found its
layout cluttered and it's key sequences awkward. How configurable
is it, really? Do you use it as it comes out of the box?
Really configurable, and no, I don't use it in an
On Wed, 08 Sep 1999 20:19:32 -0400, Zhihui Zhang wrote:
I have to use attach and dettach to do so. Does that mean I have to
display the pid of the new process in order to follow it. And I have to
modify the child process so that it can wait until I can attach to it.
That will not be as
Marcel Moolenaar wrote:
I suggest to try to avoid the version bump. NetBSD-like way to do it:
Give new implementations another names in object files, so that they
don't conflict with old implementations, and preserve old
implementations in the library too. To make the compiler generate
From: Darren Reed [EMAIL PROTECTED]
The problem with this is the BSD TCP/IP implementation ACK's (or at least
attempts to ACK) data as soon as it is received and it is a big no-no to
discard queued data that has already been ACK'd.
Probably it is not self-evident why we HAVE to drop this
On Thu, 9 Sep 1999, Julian Elischer wrote:
I think he wants something like an "inverted chroot"
(you can see out but others can't see in?
(into all facets, e.g. process stats, etc.)
Then maybe he should begin by looking at the work Poul-Henning has done
on jail(8) code? Is that what you're
Hi Nate,
Somewhere , theres got to be a nice little email place where Unix people can talk
about
usability and ease of software.
Just to toss in my 0.02 cents, I've been using exmh for a while and
am on one hand very satisfied with it, on the other hand it's handling
of mime and html
On Thu, Sep 09, 1999 at 12:08:01PM +1000, Andrew Reilly wrote:
Lots of folk use procmail, but since I'm using qmail as an MTA,
I thought I'd see if I could use it's native methods, and it's
really easy, with a shell script that's just a case $SENDER
block.
It's even "easier" :-)
I subscribe
On Wed, Sep 08, 1999, Gustavo V G C Rios wrote:
Dear gentleman,
One clear example:
No user(but only that ones previous allowed to) should be able to see
other users process. This facility have to be done at kernel level,
(that's what i think).
Define "see". Access the memory?
In some mail from Stas Kisel, sie said:
From: Darren Reed [EMAIL PROTECTED]
The problem with this is the BSD TCP/IP implementation ACK's (or at least
attempts to ACK) data as soon as it is received and it is a big no-no to
discard queued data that has already been ACK'd.
Probably
Darren Reed wrote:
It is evil connection. Good applications do read data from their sockets,
and evil ones do not. And ever if it is good, but silly or busy
application, good clients do not send so much data that application
can not process it. Am I wrong, there are any examples?
So
In some mail from Karl Pielorz, sie said:
Darren Reed wrote:
It is evil connection. Good applications do read data from their sockets,
and evil ones do not. And ever if it is good, but silly or busy
application, good clients do not send so much data that application
can not
On Thu, Sep 09, 1999 at 01:45:39PM +0400, Stas Kisel wrote:
From: Darren Reed [EMAIL PROTECTED]
The problem with this is the BSD TCP/IP implementation ACK's (or at least
attempts to ACK) data as soon as it is received and it is a big no-no to
discard queued data that has already been
Dmitrij Tejblum wrote:
Marcel Moolenaar wrote:
I suggest to try to avoid the version bump. NetBSD-like way to do it:
Give new implementations another names in object files, so that they
don't conflict with old implementations, and preserve old
implementations in the library
From [EMAIL PROTECTED] Thu Sep 9 16:17:27 1999
Probably it is not self-evident why we HAVE to drop this connection.
So what if someone manages to crash a program due to a DOS attack ?
An easy one that comes to mind is syslogd. It's often stuck in disk-wait
and can easily be targetted
Just to toss in my 0.02 cents, I've been using exmh for a while and
am on one hand very satisfied with it, on the other hand it's handling
of mime and html is not good, so I'd be very interested in discussing
this topic too.
VM doesn't do HTML/MIME very well, although I understand in later
If memory serves me right, Marc van Kempen wrote:
Hi Nate,
Somewhere , theres got to be a nice little email place where Unix people ca
n talk about
usability and ease of software.
Just to toss in my 0.02 cents, I've been using exmh for a while and
am on one hand very satisfied
I strongly disagree. Spitting "unresolved references" is *not* a way to
tell the user that he doesn't have the right libraries.
I strongly disagree. This is much better than version bump. After all,
we can add suggestion to upgrade libraries to the "unresolved references"
message.
I would get out of mbufs, increase maxusers. Either my code
is less agressive than originally, or something has changed in
some of the freebsd releases since then, even slightly to prevent this
from currently happening. I'm not sure which. NetBSD also suffers
from this problem, and
Dmitrij Tejblum wrote:
Other OSes started to avoid version bumps. Linux promises to not bump
the libc version since glibc2.
Yes, we now have a multitude of patches floating around for all those
glibc2 binaries that just won't work on glibc2.1. Instead of a simple and
intuitive message like
At 6:44 PM -0700 9/8/99, Justin C. Walker wrote:
From the FWIW department, we have, in the Darwin source, an
implementation of a "select replacement" that is designed to get
around some of the (perceived or real) issues with select(), e.g.,
looking at a long (FD_SETSIZE or larger) array of bits
hi,
any idea on how to force ATX power supplies to restart after a power
outage without having someone press the 'power' button on the front
panel ? All the motherboards i can find now have their bios with two
options:
Disabled
no automatic restart on power failure
any idea on how to force ATX power supplies to restart after a power
outage without having someone press the 'power' button on the front
panel ? All the motherboards i can find now have their bios with two
options:
Disabled
no automatic restart on power failure
You
On Thu, 9 Sep 1999, Luigi Rizzo wrote:
hi,
any idea on how to force ATX power supplies to restart after a power
outage without having someone press the 'power' button on the front
panel ? All the motherboards i can find now have their bios with two
options:
Disabled
From: Garance A Drosihn [EMAIL PROTECTED]
Date: 1999-09-09 10:33:59 -0700
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: message queues for I/O (usenix paper)
In-reply-to: [EMAIL PROTECTED]
X-Sender: [EMAIL PROTECTED]
At 6:44 PM -0700 9/8/99, Justin C. Walker wrote:
From the FWIW
There is a short but sweet[1] article on ZDNet today regarding FreeBSD:
http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html
Not too in-depth, but it gives a good quick overview, calling FreeBSD a
true Unix, emphasizing it's history compared to Linux.
-
Chris D.
[redirected to -advocacy where this belonged first off]
On Thu, 9 Sep 1999, Chris D. Faulhaber wrote:
There is a short but sweet[1] article on ZDNet today regarding FreeBSD:
http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html
Not too in-depth, but it gives a
Mike Smith wrote:
any idea on how to force ATX power supplies to restart after a power
outage without having someone press the 'power' button on the front
panel ? All the motherboards i can find now have their bios with two
options:
Disabled
no automatic restart
Dmitrij Tejblum wrote:
Other OSes started to avoid version bumps. Linux promises to not bump
the libc version since glibc2.
Yes, we now have a multitude of patches floating around for all those
glibc2 binaries that just won't work on glibc2.1. Instead of a simple and
intuitive
Sheldon Hearn wrote:
On Thu, 09 Sep 1999 10:56:05 CST, Nate Williams wrote:
Yes, we shouldn't version bump every time someone has a whim, ending
up with 10 version bumps/week, but neither should we avoid them
altogether and cause the Linux syndrome of programs refusing to work
Yes, we shouldn't version bump every time someone has a whim, ending
up with 10 version bumps/week, but neither should we avoid them
altogether and cause the Linux syndrome of programs refusing to work
because they have the *wrong* version of glibc2.3 (or whatever)
This is
On Thu, Sep 09, 1999, Mike Pritchard wrote:
I used to work somewhere where we didn't wany any of the users
to know anything about any other groups of users processes.
We did this by restricting ps to only show other procs that
had the same primary group as the person executing ps.
Root and
* Daniel O'Connor ([EMAIL PROTECTED]) [990909 07:15]:
On 09-Sep-99 Gustavo V G C Rios wrote:
I would not be able to see any other proccess which i am not the
owner, top would indicated, only 8 proccess, for this current scenario.
Linux already have such a facility!
Hack ps and turn off
On Thu, 9 Sep 1999, Julian Elischer wrote:
I think he wants something like an "inverted chroot"
(you can see out but others can't see in?
(into all facets, e.g. process stats, etc.)
It sounds like a "FreeBSD VM", VM taken to mean virtual machine. Anybody
in such a 'jar' would not notice
On Thu, Sep 09, 1999, Narvi wrote:
It sounds like a "FreeBSD VM", VM taken to mean virtual machine. Anybody
in such a 'jar' would not notice (be able to notice) the existence of
others at all.
With somedata hiding and given file systems mounted only in such a 'jar'
the ones in it would
For what it's worth, I agree with Marcel. Version bumps should be
discouraged, but not totally avoided.
What is the reason to not avoid the version bump?
Carrying around old libraries
with older version numbers is *hardly* a burden for the users, and those
folks who are running old
On Wed, Sep 08, 1999 at 05:43:17PM -0700, Amancio Hasty wrote:
3. Needlessly cross-posted (watch your cc lines, loser! :).
On a different topic, does anyone know of a good X mailer
(currently I am using exmh) :
1. user friendly
2. filtering capability
3. thread topic support
Kind of like
For what it's worth, I agree with Marcel. Version bumps should be
discouraged, but not totally avoided.
What is the reason to not avoid the version bump?
Because if you don't have the latest/greatest library (old machines),
newer programs that are compiled against the latest/greatest
This appears to be an oversight on the developers of gdb's part, but
direct from the info page:
GDB has no special support for debugging programs which create
additional processes using the `fork' function. When a program forks,
GDB will continue to debug the parent process and the child
Dmitrij Tejblum wrote:
Dmitrij Tejblum wrote:
Other OSes started to avoid version bumps. Linux promises to not bump
the libc version since glibc2.
Yes, we now have a multitude of patches floating around for all those
glibc2 binaries that just won't work on glibc2.1. Instead of
On Thu, Sep 09, 1999 at 01:21:09PM +0200, Markus Stumpf wrote:
On Thu, Sep 09, 1999 at 12:08:01PM +1000, Andrew Reilly wrote:
really easy, with a shell script that's just a case $SENDER
It's even "easier" :-)
I subscribe new mailing lists (and resubscribed old ones) as
[EMAIL
In the last episode (Sep 10), Andrew Reilly said:
On Thu, Sep 09, 1999 at 01:21:09PM +0200, Markus Stumpf wrote:
On Thu, Sep 09, 1999 at 12:08:01PM +1000, Andrew Reilly wrote:
really easy, with a shell script that's just a case $SENDER
It's even "easier" :-)
I subscribe new mailing
On Thu, Sep 09, 1999 at 10:35:52AM -0700, Mike Smith wrote:
Disabled
no automatic restart on power failure
You _should_ be able to change this.
none of them is satisfactory especially for picoBSD things such as
routers or firewalls where an UPS is overkill...
You
hi my names donna kean and i'm a 3rd year is
student at the australian defence force academy. i'm enrolled in a systems
administration course and i have to write an assignment about freebsd gui tools
that help sysadmins do their work such as create users, monitor the system etc.
i was
Marcel Moolenaar wrote:
Dmitrij Tejblum wrote:
Dmitrij Tejblum wrote:
Other OSes started to avoid version bumps. Linux promises to not bump
the libc version since glibc2.
Yes, we now have a multitude of patches floating around for all those
glibc2 binaries that just
Can someone who understands make(1)
check out bin/13039
specifically the fix would be nice in 3.3 if we can get it
(the fix is in the PR)
julian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On my dual processor I am running old boot blocks and an AOUT kernel. I need the AOUT
because I have a lkm device the talks out the parallel port to "Background Debug
Module" for a Motorola 68332. I haven't been able to convert it over yet.
My code is up to date with cvs-cur.5648.gz (Sept. 9
On Fri, 10 Sep 1999, Andrew Reilly wrote:
How is it that BIOS settings can affect this? Do they fiddle
with some battery-backed switch on the motherboard?
The ATX power supply has a lead or two that are always powered. This allows
the machine do softpower on. It also means that the bios
On 09-Sep-99 Luigi Rizzo wrote:
any idea on how to force ATX power supplies to restart after a power
outage without having someone press the 'power' button on the front
panel ? All the motherboards i can find now have their bios with two
options:
There are no jumpers on the mobo to help
Please word-wrap your messages, as reading them unwrapped is a major
nuisance.
On my dual processor I am running old boot blocks and an AOUT kernel.
I need the AOUT because I have a lkm device the talks out the parallel
port to "Background Debug Module" for a Motorola 68332. I haven't been
Zhihui Zhang [EMAIL PROTECTED] writes:
Your response suggests that I can not achieve the same result simply by
using (I am using gdb 4.18):
(gdb)set follow-fork-mode child
As far as I can tell, `set follow-fork-mode' only works on HP-UX.
/assar
To Unsubscribe: send mail to [EMAIL
VM doesn't do HTML/MIME very well, although I understand in later
versions of XEmacs they've incorporated some packages that handle things
better. (I'm still using XEmacs 19.16, from the dark ages...)
Does it do IMAP?
It doesn't even do POP, I use fetchmail/procmailrc to get my
On 10-Sep-99 Nate Williams wrote:
Does it do IMAP?
It doesn't even do POP, I use fetchmail/procmailrc to get my email,
which works *MUCH* better than anything else I've found.
Woe is me.
Oh well.. back to xfmail :)
---
Daniel O'Connor software and network engineer
for Genesis Software -
On Thu, 09 Sep 1999, Nate Williams wrote:
I'm more tempted to revert to the major/minor versioning.
ELF has no minor revision number (IMO a mistake, but it's not my call).
I agree that it is a mistake.
However, if you think of "major" changes as different libraries, it does make
sense. We
On 09-Sep-99 Nate Williams wrote:
VM doesn't do HTML/MIME very well, although I understand in later
versions of XEmacs they've incorporated some packages that handle things
better. (I'm still using XEmacs 19.16, from the dark ages...)
Does it do IMAP? I have only seen *1* emailer which
Mike Smith wrote:
Please word-wrap your messages, as reading them unwrapped is a major
nuisance.
Sorry, I had turned it off for a specific message and forgot.
You should do this soon.
I know. But I was barely able to create it the first time.
Because nobody is testing using a.out
On Fri, 10 Sep 1999, Donna Kean wrote:
hi my names donna kean and i'm a 3rd year is student at the australian
defence force academy. i'm enrolled in a systems administration
course and i have to write an assignment about freebsd gui tools that
help sysadmins do their work such as create
I use freebsd about +- 12 months ago. I have never did any thing serious
at kernel level, nor i know anything about kernel desgin.
Suppose, i would like to spend time and patience learnig Fbsd internals.
If, later, i were able to code something to freebsd, and suppose i do,
what (or better, how)
On Fri, 10 Sep 1999, Daniel O'Connor wrote:
Does it do IMAP? I have only seen *1* emailer which does IMAP properly (xfmail)
all the others either don't support it at all, or treat IMAP like POP (ie just
fetch mail from INBOX).
Netscape does, actually. I set up a friend's computer to do
On 10-Sep-99 David Scheidt wrote:
fetch mail from INBOX).
Netscape does, actually. I set up a friend's computer to do this, over an
ssh-forwarded local port, even. It all more less "Just worked". On a win98
box, even. shudder.
Yeah, I forgot to mention Netscape.. OK no mailer with a
On Thu, Sep 09, 1999, Gustavo V G C Rios wrote:
I use freebsd about +- 12 months ago. I have never did any thing serious
at kernel level, nor i know anything about kernel desgin.
Suppose, i would like to spend time and patience learnig Fbsd internals.
If, later, i were able to code
Andrew Reilly wrote:
I have an ATX system that must be looking for a keyboard-located
power switch of some sort. It won't power up unless I unplug the
(PS-2) keyboard, and then plug it back in again. That seems as
though there's something fairly complicated in the system that _is_
being
Nate Williams writes:
VM doesn't do HTML/MIME very well, although I understand in later
versions of XEmacs they've incorporated some packages that handle things
better. (I'm still using XEmacs 19.16, from the dark ages...)
Does it do IMAP?
It doesn't even do POP, I use
On 10-Sep-99 Florent Parent wrote:
I've been trying different MUAs that would allow me to read my mail
under FreeBSD and NT (dual boot laptop) while sharing the same mail
folders (shared DOS partition). So far, only VM/Xemacs allowed me to
do that. Even Netscape FreeBSD/NT use different
I have about 5 years experance with FreeBSD. I am running it at home
connected to a cable modem. My server is fairly secure from the
outside. I periodically read and act upon the builins from CERT, etc.
The box is just going to be running NATD and IPFW, maybe DHCLIENT.
Some suggestions:
Hello:
One suggestion I have is webmin. Look at www.webmin.com.
and i have to write an assignment about freebsd gui tools that help sysadmins
do their work
Darren Wiebe
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the
On Fri, 10 Sep 1999, Daniel O'Connor wrote:
On 10-Sep-99 Florent Parent wrote:
I've been trying different MUAs that would allow me to read my mail
under FreeBSD and NT (dual boot laptop) while sharing the same mail
folders (shared DOS partition). So far, only VM/Xemacs allowed me to
I just did that upgrade (been with freebsd since 1.1!) and everything
seems pretty smooth. I did a 2.2-3.1 upgrade on another machine so
I'm probably glossing over some aout issues (mainly that you have to
find them and move them into a separate directory).
One thing that confused me for
The box is just going to be running NATD and IPFW, maybe DHCLIENT.
Mr. NT is been told he can try and break-in, crash what ever this box
from the internet side.
I am asking for links, pointer to make sure this is configured as
secure/solid as possible. I will be installing 3.3-STABLE
From [EMAIL PROTECTED] Thu Sep 9 18:10:06 1999
I am creating about 100 icmp sockets, and as they are
created, allocate a very large SO_RCVBUF:
(void)setsockopt(localstruct-icmp_s, SOL_SOCKET,
SO_RCVBUF, (char *)hold, sizeof(hold));
This can be a part of the
--On Freitag, 10. September 1999, 10:56 +0930 Daniel O'Connor
[EMAIL PROTECTED] wrote:
On 09-Sep-99 Nate Williams wrote:
VM doesn't do HTML/MIME very well, although I understand in later
versions of XEmacs they've incorporated some packages that handle things
better. (I'm still using
Hi all,
Sort of off topic, though thought it might bring about some positive
response and ideas here...
I've successfully avoided a Cisco solution (though not the ADC kentrox
one =( ) recently with the Sangoma Wanpipe using FreeBSD 3.2-STABLE
(cvsupped last week).
Time permitting,
-Original Message-
From: owner-freebsd-hack...@freebsd.org
[mailto:owner-freebsd-hack...@freebsd.org]on Behalf Of
Daniel O'Connor
Sent: Wednesday, September 08, 1999 9:05 PM
To: Gustavo V G C Rios
Cc: freebsd-hackers@FreeBSD.ORG; ch...@calldei.com
Subject: Re: CS Project
On
On 09-Sep-99 Jason Young wrote:
Hack ps and turn off procfs :)
I would think it more appropriate to adjust procfs' permissions in the
kernel such that a user couldn't look at processes they don't own,
i.e., can't cd or look into /proc/$PIDTHEYDONTOWN. Adding group-read
for wheel or
I think the idea (of a procfs ps) was shot down on the
lists some time
ago because ps needs to retain the ability to look at
the process list
in a kernel coredump. IMHO that's a lot of messy kvm
groveling and
associated kernel-to-userland sync dependencies, just to
cater to the
Hi!
On 09-Sep-99 Andrew Reilly wrote:
XFMail isn't acceptable, because I've got 130M of mbox mail
boxes in a deep directory hierarchy, and I'd like to keep them
that way. The last time I looked at XFMail it insisted on an
un-nested mh-directory style of mailbox. Is it still the case?
Nope
Some further thoughts before I doze off:
allowed to. This should be controlled by sysctls like
(placement based
on nfs and ffs sysctl placement precedent):
Or even a mount option to procfs :)
After some thought, I think the mount option idea is best. I hadn't
thought of that before.
On 09-Sep-99 Jason Young wrote:
After some thought, I think the mount option idea is best. I hadn't
thought of that before. One might want to apply different procfs
security policies to different mounts of procfs, especially in a
jail() situation. Good call.
Yeah, you'd have to make sure
I think he wants something like an inverted chroot
(you can see out but others can't see in?
(into all facets, e.g. process stats, etc.)
julian
On Wed, 8 Sep 1999, Chuck Robey wrote:
On Wed, 8 Sep 1999, Gustavo V G C Rios wrote:
Dear gentleman,
i am a computer science student, and
Nate Williams n...@mt.sri.com writes:
Nate: it's a while since I looked at VM on XEmacs. I found its
layout cluttered and it's key sequences awkward. How configurable
is it, really? Do you use it as it comes out of the box?
Really configurable, and no, I don't use it in an
I just mailed drusc...@cs.rice.edu to ask about extra information, work,
or references that he may have on the event queues paper that he was
a coauthor of.
Just saying this so other people dont just have about a dozen messages about
the same thing.
Please notice that this message is going to
From: bmile...@dsuper.net (Bosko Milekic)
Having MGET store that null (e.g. fail as opposed to panic) on a
M_WAIT seems fairly easy to fix, and would probably require some patching
that would ensure that the packet loss is handeled relatively 'cleanly'
(probably some debugging), but I
On Wed, 08 Sep 1999 20:19:32 -0400, Zhihui Zhang wrote:
I have to use attach and dettach to do so. Does that mean I have to
display the pid of the new process in order to follow it. And I have to
modify the child process so that it can wait until I can attach to it.
That will not be as
Marcel Moolenaar wrote:
I suggest to try to avoid the version bump. NetBSD-like way to do it:
Give new implementations another names in object files, so that they
don't conflict with old implementations, and preserve old
implementations in the library too. To make the compiler generate
From: Darren Reed ava...@coombs.anu.edu.au
In some mail from Stas Kisel, sie said:
[...]
IMHO it is a good idea to develop tcp_drain() from /sys/netinet/tcp_subr.c
It should be quite intellectual to select a target - a process or a uid,
which does not read properly from it's sockets, and
From: Darren Reed ava...@coombs.anu.edu.au
The problem with this is the BSD TCP/IP implementation ACK's (or at least
attempts to ACK) data as soon as it is received and it is a big no-no to
discard queued data that has already been ACK'd.
Probably it is not self-evident why we HAVE to drop
On Thu, 9 Sep 1999, Julian Elischer wrote:
I think he wants something like an inverted chroot
(you can see out but others can't see in?
(into all facets, e.g. process stats, etc.)
Then maybe he should begin by looking at the work Poul-Henning has done
on jail(8) code? Is that what you're
Hi Nate,
Somewhere , theres got to be a nice little email place where Unix people can
talk about
usability and ease of software.
Just to toss in my 0.02 cents, I've been using exmh for a while and
am on one hand very satisfied with it, on the other hand it's handling
of mime and html
On Thu, Sep 09, 1999 at 12:08:01PM +1000, Andrew Reilly wrote:
Lots of folk use procmail, but since I'm using qmail as an MTA,
I thought I'd see if I could use it's native methods, and it's
really easy, with a shell script that's just a case $SENDER
block.
It's even easier :-)
I subscribe new
On Wed, Sep 08, 1999, Gustavo V G C Rios wrote:
Dear gentleman,
One clear example:
No user(but only that ones previous allowed to) should be able to see
other users process. This facility have to be done at kernel level,
(that's what i think).
Define see. Access the memory?
On Thu, Sep 09, 1999 at 01:21:09PM +0200, Markus Stumpf wrote:
On Thu, Sep 09, 1999 at 12:08:01PM +1000, Andrew Reilly wrote:
Lots of folk use procmail, but since I'm using qmail as an MTA,
I thought I'd see if I could use it's native methods, and it's
really easy, with a shell script
I am evaluating both the S508 and S508/FT1 at the present time and
have both models running on FreeBSD 3.2-STABLE. Had to add a fourth
parameter to one of the function calls in ptpipe.c to get it to compile.
They appear easy to turn up and reliable. The PPIPEMON Windows utility
is useful
Dmitrij Tejblum wrote:
Marcel Moolenaar wrote:
I suggest to try to avoid the version bump. NetBSD-like way to do it:
Give new implementations another names in object files, so that they
don't conflict with old implementations, and preserve old
implementations in the library too. To
In some mail from Stas Kisel, sie said:
From: Darren Reed ava...@coombs.anu.edu.au
The problem with this is the BSD TCP/IP implementation ACK's (or at least
attempts to ACK) data as soon as it is received and it is a big no-no to
discard queued data that has already been ACK'd.
Darren Reed wrote:
It is evil connection. Good applications do read data from their sockets,
and evil ones do not. And ever if it is good, but silly or busy
application, good clients do not send so much data that application
can not process it. Am I wrong, there are any examples?
So
In some mail from Karl Pielorz, sie said:
Darren Reed wrote:
It is evil connection. Good applications do read data from their sockets,
and evil ones do not. And ever if it is good, but silly or busy
application, good clients do not send so much data that application
can not
unsubscribe bran...@ferginc.com
unsubscribe branson.mathe...@ferginc.com
- branson
---
Branson Matheson If you are falling off of a mountain,
Unix Systems Manager You may as well try to
Dmitrij Tejblum wrote:
Marcel Moolenaar wrote:
I suggest to try to avoid the version bump. NetBSD-like way to do it:
Give new implementations another names in object files, so that they
don't conflict with old implementations, and preserve old
implementations in the library
On Thu, Sep 09, 1999 at 01:45:39PM +0400, Stas Kisel wrote:
From: Darren Reed ava...@coombs.anu.edu.au
The problem with this is the BSD TCP/IP implementation ACK's (or at least
attempts to ACK) data as soon as it is received and it is a big no-no to
discard queued data that has already
From ava...@cheops.anu.edu.au Thu Sep 9 16:17:27 1999
Probably it is not self-evident why we HAVE to drop this connection.
So what if someone manages to crash a program due to a DOS attack ?
An easy one that comes to mind is syslogd. It's often stuck in disk-wait
and can easily be
1 - 100 of 159 matches
Mail list logo
