Mike Smith wrote:
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the
Hi everyone,
I've been following this discussion almost from the beginning, and I
have the feeling that we're not _really_ getting very far. There's good
arguments for and against overcommit, depending on your point of view
and your requirements.
What I do see is a not-so-openly voiced consent
Mike Smith scribbled this message on Jul 15:
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
It "works" for some definitions of "work". Firstly, there are three
different CDROM interfaces
At 01:05 15/07/99 -0700, John-Mark Gurney wrote:
Mike Smith scribbled this message on Jul 15:
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
It "works" for some definitions of "work". Firstly,
Thomas Gellekum [EMAIL PROTECTED] wrote:
Daniel Eischen [EMAIL PROTECTED] writes:
There are some bugs in libc_r in stable that have been fixed in
-current. I think the one that you've hit is an uninitialized
TAILQ_HEAD in a statically declared mutex (in localtime). It's
probably
Daniel Eischen [EMAIL PROTECTED] writes:
The libc_r version number was bumped in -current because of the
addition of poll(). Is this allowed in -stable, or something
that waits for a -RELEASE?
Jordan should have to say something about this. AFAIR, bumps are
allowed but only by one between
Hi everybody,
after wondering for two years why FreeBSD (2.2.x ... 3.2) might lock up
when an NFS server is down, I think I have found one reason for that (see
kern/12609 - I now know it doesn't belong to kern - sorry).
It is the implementation of getcwd (src/lib/libc/gen/getcwd.c). When
Kevin Schoedel wrote:
Imagine a reasonably big
program, like Netscape or Emacs, of which you usually just use a
subset of features. There can easily be many megabytes of code and
data in them you never actually use, or you don't _usually_ use
(like the people who use emacs like it was vi
[EMAIL PROTECTED] wrote:
All of the arguments I've seen so far assume that one process is
running off and grabbing all the available memory. That may be
the most likely scenario, but it's most certainly not the *only*
scenario. What if you have a whole bunch of "middle sized" processes
At 6:29 PM -0700 7/14/99, Matthew Dillon wrote:
If 1G isn't enough, spend another $30 and throw 2G of swap
online. Or perhaps dedicate an entire $150 disk and throw
6+ GB of swap online.
The equivalent setup using a non-overcommit model would require
considerably more swap
Been trying to get nb8390.com compiled under /usr/sys/i386/boot/netboot
and every time it does this:
(ns2)[6]:/usr/src/sys/i386/boot/netboot# make
Warning: Object directory not changed from original
/usr/src/sys/i386/boot/netboot
cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x9 -DPCI
Greetings Hackers,
We are in the process of releasing a FreeBSD v 3.2 Ethernet driver that detects link
failures and executes failovers, supports Cisco's FEC trunking, and system-to-system
trunking. To support these features, some configuration is required...the
configuration utility
Hi,
I am in the process of developing a device driver for the purpose of
stepper motor control. The timing of each pulse is determined by
external timing hardware on an I/O board, which will fire an interrupt
after the time requested. Using this method, I am able to generate
streams of pulses at
On Thu, 15 Jul 1999, Jordan K. Hubbard wrote:
:- Jordan should have to say something about this. AFAIR, bumps are
:- allowed but only by one between releases. We will have to provide
:- libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
:- anyway by the time 4.x is released).
I thought this amusing.
Take the following program, designed to suck stats out of /proc for the
network devices:
#include stdio.h
#include sys/types.h
#include unistd.h
main()
{
char stuff[4096];
int fd = open("/proc/net/dev", 0);
while(1)
{
int amount = read(fd, stuff,
: If I may re-phrase.. How do I determine if the send/recv spaces
:are large enough, and if not, how many times I bumped into the
:wall?
:
:Thanks!
:John
It depends entirely on the type of traffic your machine is
handling. A large web server usually uses relatively small
(16K or
Jordan should have to say something about this. AFAIR, bumps are
allowed but only by one between releases. We will have to provide
libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
anyway by the time 4.x is released).
I'd prefer not to bump it... John Birrell and
:Hi,
:
:I am in the process of developing a device driver for the purpose of
:stepper motor control. The timing of each pulse is determined by
:external timing hardware on an I/O board, which will fire an interrupt
:after the time requested. Using this method, I am able to generate
:streams of
On Thu, 15 Jul 1999, Daniel C. Sobral wrote:
Uh... like any modern unix, Solaris overcommits.
On Thu, 15 Jul 1999 08:46:36 -0700 (PDT),
"Eduardo E. Horvath" [EMAIL PROTECTED] said:
Where do you guys get this misinformation?
:
Note the `19464k reserved'; that space has
:Both Dillon and Sobral mistakenly claimed that "Solaris overcommits",
:this fact seems to be somewhat suggestive.
:
:And also, the followings are allocated memory and reserved memory
:in my environment. (This table also includes Eduardo's example)
:
: SunOS allocated reservedtotal
:"pstat -s" on SunOS4, and "swap -s" on SunOS5. From Solaris man page:
:
::-s Print summary information about total swap
:: space usage and availability:
::
:: allocated The total amount of swap space
::
::-s Print summary information about total swap
:: space usage and availability:
::
:: allocated The total amount of swap space
:: (in 1024-byte blocks)
::
Are there any design limits to mfs? I want to use cdrecord to write to a
dozen or so CD's at once, and fear making lots of coasters if I run them
all off a single on-disk file. However, a CD only holds 650 MB, so it
seems like I could have the image on mfs and sleep well sans coasters.
Would
:
:Are there any design limits to mfs? I want to use cdrecord to write to a
:dozen or so CD's at once, and fear making lots of coasters if I run them
:all off a single on-disk file. However, a CD only holds 650 MB, so it
:seems like I could have the image on mfs and sleep well sans coasters.
:
On Thu, Jul 15, 1999 at 10:44:57AM +0100, Alex Knowles wrote:
I hope this is the right place to post, sorry if it's not.
I'm really sorry to post what is probably a repeat question, but I've just
upgraded to freebsd 3.2-release and I'm having real problems getting the
kernel to see my printer
On Wed, 14 Jul 1999, John Nemeth wrote:
On Jul 15, 2:40am, "Daniel C. Sobral" wrote:
} Garance A Drosihn wrote:
} At 12:20 AM +0900 7/15/99, Daniel C. Sobral wrote:
} In which case the program that consumed all memory will be killed.
} The program killed is +NOT+ the one demanding
[Hijacked from freebsd-security]
On Thu, 15 Jul 1999 17:33:29 -0400, Garance A Drosihn wrote:
What I wanted to do was have "estr" routines, where the destination
is specified as the starting point and the ending point of the area
available for the string (as two parameters). The routines
According to Gregory A. Carter:
I'm assuming that might have something to do with it. The file scrt0.c
This is the old a.out crt code. The one in 3.0+ is crt1.c, look into
/usr/src/lib/csu/i386-elf/.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD
On Fri, Jul 16, 1999 at 12:15:31AM +0200, Sheldon Hearn wrote:
As I understand it, the goal here is to return to the caller the number
of bytes copied (however you represent it), so that the caller can
easily determine whether or not dst is safe for operations demanding a
null-terminated
:Before program start:
:total: 2k bytes allocated + 4792k reserved = 24792k used, 191048k available
:
:After malloc, before touch:
:total: 18756k bytes allocated + 37500k reserved = 56256k used, 159580k available
:
:After malloc + touch:
:total: 52804k bytes allocated + 4852k reserved =
If this is correct, then solaris is using a VMSPACE = SWAPSPACE
model. FreeBSD uses a VMSPACE = SWAPSPACE + REALMEM model.
AFAIK it has been stated quite explicitly by the Solaris folks that
Solaris 2.x uses VMSPACE = SWAPSPACE + REALMEM. This is *different*
from SunOS 4.1.x.
Steinar
On Fri, Jul 16, 1999 at 12:15:31AM +0200, Sheldon Hearn wrote:
As I understand it, the goal here is to return to the caller the number
of bytes copied (however you represent it), so that the caller can
easily determine whether or not dst is safe for operations demanding a
On Thu, 15 Jul 1999 18:34:42 -0400, Tim Vanderhoek wrote:
if (fooncat(string, append, sizeof(string)) != strlen(append))
...
which is rather evil, given that the second strlen(append) would be
completely gratuitous if it weren't for the interface you're
suggesting.
Tim, you're doing
On Thu, 15 Jul 1999, Mike Smith wrote:
What's really stupid is that most of the time you're trying to use
these functions to fix code that looks like:
strcpy(buf, str1);
strcat(buf, str2);
strcat(buf, str3);
without overflowing buf. This is dumb! Use asprintf
On Thu, 15 Jul 1999, Julian Elischer wrote:
There was a talk on these (strlcpy(3) and strlcat(3)) at USENIX.
The logic as to their design was presented and I agree totally with
the way that the logic was played out into the functions.
They are described in the FreeNIX proceedings on page
Here is what I get from one of BEST's mail www proxy machines.
~dillon/br adds the object size's together. 'swap' and 'default'
objects refers to unbacked VM objects - and none of the processes running
fork shared unbacked objects so we don't have to worry about that. The
Ugh. Take the first example in the paper; it rewrites as
len = asprintf(path, "%s/.foorc");
^ , homedir
Whoops.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph
On Thu, 15 Jul 1999, Mike Smith wrote:
Ugh. Take the first example in the paper; it rewrites as
len = asprintf(path, "%s/.foorc");
as opposed to
strlcat(path, homedir, sizeof(path));
strlcat(path, "/", sizeof(path));
strlcat(path, ".foord", sizeof(path));
On Fri, Jul 16, 1999 at 12:53:13AM +0200, Sheldon Hearn wrote:
If all you're saying is that you want an API that doesn't require a test
against the known length of src (append in your example), then you won't
like strl*. :-)
Well, if I read your message correctly, the difference between
At 12:15 AM +0200 7/16/99, Sheldon Hearn wrote:
[Hijacked from freebsd-security]
For those who missed the original article, here's the initial
topic (from Paul Hart, but truncated a bit):
I was just reviewing the proceedings from the USENIX 1999
Annual Technical Conference where Todd
In that scenario, the 512MB of swap I assigned to this machine would be
dangerously low.
With 13GB disks available for a couple of hundred bucks, my machines aren't
going to run out of swap space any time soon, even if I commit to disk.
All I want for Christmas is a knob to disable
On Thu, 15 Jul 1999 17:53:52 CST, [EMAIL PROTECTED] wrote:
All I want for Christmas is a knob to disable overcommit.
And what I'm pretty sure the majority of the readers on this list want
is for those of you who really think it's necessary to do it yourselves.
What? Nobody who wants to
but what about
While ( more data items)
{
copy data items onto end of buffer
if full{
write out buffer
clear buffer, copy in rest of last item.
}
}
I'd certainly not want to use xxprintf() for that
This is what stdio does, funnily enough. See fwrite() etc.
--
In message [EMAIL PROTECTED] Mike Smith writes:
: if (strlen(buf) = sizeof(buf))
: return(error);
This can never be true with the strl functions They don't run off
the end, so strlen(buf) is always going to be sizeof(buf) since it
doesn't include the traling null.
In message [EMAIL PROTECTED] Mike Smith writes:
: What's really stupid is that most of the time you're trying to use
: these functions to fix code that looks like:
: strcpy(buf, str1);
: strcat(buf, str2);
: strcat(buf, str3);
: without overflowing buf. This is dumb! Use
In message [EMAIL PROTECTED] Mike Smith writes:
: Ugh. Take the first example in the paper; it rewrites as
:
: len = asprintf(path, "%s/.foorc");
:
: as opposed to
:
: strlcat(path, homedir, sizeof(path));
: strlcat(path, "/", sizeof(path));
: strlcat(path, ".foord",
In message [EMAIL PROTECTED] Mike Smith writes:
: if (strlen(buf) = sizeof(buf))
: return(error);
This can never be true with the strl functions They don't run off
the end, so strlen(buf) is always going to be sizeof(buf) since it
doesn't include the traling null.
I
In message 19990715194203.A54146@mad Tim Vanderhoek writes:
: Looking at OpenBSD's actual definition of strlcat() which returns the
: number of chars that would have been in the final string is
: potentially non-useful, but not really too terrible.
No. It is useful. If you look at the
In message [EMAIL PROTECTED] Mike Smith writes:
: I still think this is the wrong way to deal with the problem. 8)
We mildly disagree here. The strl* functions are the end all, be all
of security. They are just designed to make the existing code that
uses static buffers easy to make more
In message [EMAIL PROTECTED] Warner Losh writes:
: We mildly disagree here. The strl* functions are the end all, be all
: of security.
NOTE: This should have read:
We mildly disagree here. The strl* functions are NOT the end all, be
all of security.
which changes its meaning quite a bit...
In message [EMAIL PROTECTED] Mike Smith writes:
: I still think this is the wrong way to deal with the problem. 8)
We mildly disagree here. The strl* functions are the end all, be all
of security. They are just designed to make the existing code that
uses static buffers easy to make more
In message [EMAIL PROTECTED] Sheldon Hearn writes:
: If you see my point, let me know and I'll send you an alternative
: strlcpy.3 .
I can see your point. I don't know if I'll like your man pages better
or not, but I'd be willing to give them a spin.
Warner
To Unsubscribe: send mail to
I found it when I went searching however I still can't get the netboot to
compile as it was designed for aout. Any ideas of why it wasn't moved to
elf along with the rest of the OS? Or if not how *I* can port it to elf
instead?
The intention is that loader(8) will provide the same
Andrew Reilly wrote:
On Thu, Jul 15, 1999 at 11:48:41PM +0900, Daniel C. Sobral wrote:
Actually, applications are written assuming that malloc() will not
fail, generally speaking.
Is this really the case? I'm pretty sure I've _never_ ignored the
possibility of a NULL return from
All I want for Christmas is a knob to disable overcommit.
And what I'm pretty sure the majority of the readers on this list want
is for those of you who really think it's necessary to do it yourselves.
What? Nobody who wants to disable the policy knows how to do it? Hmmm,
I've done some work on measuring things like interrupt response times
and the interval between two interesting events or steps in processing.
A cheap way to do this is to use the TSC register in the CPU, though you
then need to calibrate the frequency that the CPU really runs at.
If you're
Hello Niall and Josef,
Thanks for your great help.
Finally I get all data on the disk back after the struggle on the
weekend :) I run the program you sent me, but I got nothing from it.
I guess the reason as follows:
(1) The program fetches each chunks of 16 blocks from the disk and
check if
I've been running VM Ware under NT for a few days now, booting FreeBSD and
other OS's.
In some quick testing:
The host machine is NT 4.0, SP5, 384MB RAM, dual 450 PII's.
The guest OS is FreeBSD 3.2-RELEASE, configured with the VMWARE 512MB
disk, and 32MB RAM allocated
Compiling a
If there were a mechanism whereby one could opt out of the SIGKILL,
most if not all of the complaints would go away. SIGDANGER would
suffice, but even a rude hack would do in a pinch, such as the one
included below (untested). If you mmap real disk instead of sbrk'ing,
and use this procfs
: fail, generally speaking.
:
:Is this really the case? I'm pretty sure I've _never_ ignored the
:possibility of a NULL return from malloc, and I've been using it
:for nearly 20 years. I usually print a message and exit, but I
:never ignore it. I thought that was pretty standard practise.
:
: In that scenario, the 512MB of swap I assigned to this machine would be
: dangerously low.
:
:With 13GB disks available for a couple of hundred bucks, my machines aren't
:going to run out of swap space any time soon, even if I commit to disk.
:
:All I want for Christmas is a knob to
Any use of str{,n}cat makes me gag. In the past I have used
a composable function that may be of interest. Composable in
the sense that the result can be immediately used as an arg
to another call and it doesn't have the O(N^2) behavior of
strcat. Such a function can be totally safe.
On Thu, 15 Jul 1999, Matthew Dillon wrote:
The are dozens of libc routines which call malloc internally and return
allocated storage. strdup(), opendir(), fopen(), setvbuf(), asprintf(),
and so forth. Dozens. And while we might check some of these for NULL,
we don't
: The are dozens of libc routines which call malloc internally and return
: allocated storage. strdup(), opendir(), fopen(), setvbuf(), asprintf(),
: and so forth. Dozens. And while we might check some of these for NULL,
: we don't check them all, and the ones we do check we
:Technical follow-up:
:
:Contrary to what I previously said, a number of tests reveal that
:Solaris, indeed, does not overcommit. All non-read only segments,
:and all malloc()ed memory is reserved upon exec() or fork(), and the
:reserved memory is not allowed to exceed the total memory. It makes
Got no response from freebsd-questions.
can anyone here help ?
Please cc your reply to my email a/c.
thanks
--Vasudha
-- Forwarded message --
Date: Thu, 15 Jul 1999 14:42:34 +0800 (SGT)
From: Vasudha Ramnath [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: implementing
No, wait, I got that wrong I think.
Oh yah, I remember now. Hmm. How odd. I came across a case where
read() could return -1 and not set errno properly if errno
was already set, but a perusal of the kernel code seems to indicate
that this can't happen. Very
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the siobi
state. No way to
Daniel Eischen eisc...@vigrid.com writes:
There are some bugs in libc_r in stable that have been fixed in
-current. I think the one that you've hit is an uninitialized
TAILQ_HEAD in a statically declared mutex (in localtime). It's
probably about time for a MFC. If someone wants to give me
Mike Smith wrote:
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the
Hi everyone,
I've been following this discussion almost from the beginning, and I
have the feeling that we're not _really_ getting very far. There's good
arguments for and against overcommit, depending on your point of view
and your requirements.
What I do see is a not-so-openly voiced consent
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
It works for some definitions of work. Firstly, there are three
different CDROM interfaces that can be hung off an SB16; one is the
Matsushita
Mike Smith scribbled this message on Jul 15:
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
It works for some definitions of work. Firstly, there are three
different CDROM interfaces that can
On Thu, 15 Jul 1999, John-Mark Gurney wrote:
Mike Smith scribbled this message on Jul 15:
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
It works for some definitions of work. Firstly,
At 01:05 15/07/99 -0700, John-Mark Gurney wrote:
Mike Smith scribbled this message on Jul 15:
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
It works for some definitions of work. Firstly,
Hi,
Is-it any FreeBSD related events near or anybody who want to
drink a Beer and help me to visit the Town ?
S.
--
FranceNet Security Administrator sebastien.gio...@francenet.fr
French FreeBSD Documentation Projectgio...@freebsd.org
Tout FreeBSD en Francais
On Wed, Jul 14, 1999 at 10:56:05PM -0700, Mike Smith wrote:
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry.
I hope this is the right place to post, sorry if it's not.
I'm really sorry to post what is probably a repeat question, but I've just
upgraded to freebsd 3.2-release and I'm having real problems getting the
kernel to see my printer ports:
here is my kernel
device ppc0at isa? port?
And pidentd will still be supported. Eventually, I'd like to have those
huge majority who do not use DES tokens with pidentd move to the
inetd identd (when committed)...
How about a standalone identd with DES `tokens' and any other nice
to haves that it doesn't make sense to implement in a
Thomas Gellekum t...@ihf.rwth-aachen.de wrote:
Daniel Eischen eisc...@vigrid.com writes:
There are some bugs in libc_r in stable that have been fixed in
-current. I think the one that you've hit is an uninitialized
TAILQ_HEAD in a statically declared mutex (in localtime). It's
Daniel Eischen eisc...@vigrid.com writes:
The libc_r version number was bumped in -current because of the
addition of poll(). Is this allowed in -stable, or something
that waits for a -RELEASE?
Jordan should have to say something about this. AFAIR, bumps are
allowed but only by one between
Thomas Gellekum t...@ihf.rwth-aachen.de writes:
libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
/usr/src/lib/compat/compat3x
Sorry.
tg
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Hi everybody,
after wondering for two years why FreeBSD (2.2.x ... 3.2) might lock up
when an NFS server is down, I think I have found one reason for that (see
kern/12609 - I now know it doesn't belong to kern - sorry).
It is the implementation of getcwd (src/lib/libc/gen/getcwd.c). When
hi, there!
On Sun, 11 Jul 1999, Chris Costello wrote:
I've implemented a few new features. First off, strdup()
isn't abused anymore so the program should run much smoother and
smaller, as well as more quickly. Secondly, I have (thanks in
part to Alfred Perlstein) added both
Danny Thomas wrote:
Killing the biggest is simple to implement and usually right.
... but some people don't want that policy, at least on some of their
systems. Does FreeBSD offer alternatives? Is so, they've been conspicuously
absent from discussion, which might have taken things into a
lyn...@orthanc.ab.ca wrote:
All of the arguments I've seen so far assume that one process is
running off and grabbing all the available memory. That may be
the most likely scenario, but it's most certainly not the *only*
scenario. What if you have a whole bunch of middle sized processes
At 6:29 PM -0700 7/14/99, Matthew Dillon wrote:
If 1G isn't enough, spend another $30 and throw 2G of swap
online. Or perhaps dedicate an entire $150 disk and throw
6+ GB of swap online.
The equivalent setup using a non-overcommit model would require
considerably more swap to
Been trying to get nb8390.com compiled under /usr/sys/i386/boot/netboot
and every time it does this:
(ns2)[6]:/usr/src/sys/i386/boot/netboot# make
Warning: Object directory not changed from original
/usr/src/sys/i386/boot/netboot
cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x9 -DPCI
In message pine.bsf.4.10.9907151329040.9501-100...@merlin.th.physik.uni-bonn.d
e, Jan Conrad writes:
after wondering for two years why FreeBSD (2.2.x ... 3.2) might lock up
when an NFS server is down, I think I have found one reason for that (see
kern/12609 - I now know it doesn't belong to kern -
Hi,
Thanks for the reply(s)... If I understand you correctly, then:
%route -n get netapp01
route to: 192.168.21.52
destination: 192.168.21.52
interface: fxp1
flags: UP,HOST,DONE,LLINFO,WASCLONED
recvpipe sendpipe ssthresh rtt,msecrttvar hopcount mtu expire
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
It works for some definitions of work. Firstly, there are three
different CDROM interfaces that can be hung off an SB16; one is the
Greetings Hackers,
We are in the process of releasing a FreeBSD v 3.2 Ethernet driver that detects
link failures and executes failovers, supports Cisco's FEC trunking, and
system-to-system trunking. To support these features, some configuration is
required...the configuration utility requires
Jordan should have to say something about this. AFAIR, bumps are
allowed but only by one between releases. We will have to provide
libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
anyway by the time 4.x is released).
I'd prefer not to bump it... John Birrell and I are
On Thu, 15 Jul 1999, Jordan K. Hubbard wrote:
:- Jordan should have to say something about this. AFAIR, bumps are
:- allowed but only by one between releases. We will have to provide
:- libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
:- anyway by the time 4.x is released).
I thought this amusing.
Take the following program, designed to suck stats out of /proc for the
network devices:
#include stdio.h
#include sys/types.h
#include unistd.h
main()
{
char stuff[4096];
int fd = open(/proc/net/dev, 0);
while(1)
{
int amount = read(fd, stuff,
: If I may re-phrase.. How do I determine if the send/recv spaces
:are large enough, and if not, how many times I bumped into the
:wall?
:
:Thanks!
:John
It depends entirely on the type of traffic your machine is
handling. A large web server usually uses relatively small
(16K or
Jordan should have to say something about this. AFAIR, bumps are
allowed but only by one between releases. We will have to provide
libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
anyway by the time 4.x is released).
I'd prefer not to bump it... John Birrell and I
:Hi,
:
:I am in the process of developing a device driver for the purpose of
:stepper motor control. The timing of each pulse is determined by
:external timing hardware on an I/O board, which will fire an interrupt
:after the time requested. Using this method, I am able to generate
:streams of
On Thu, 15 Jul 1999, Daniel C. Sobral wrote:
Uh... like any modern unix, Solaris overcommits.
On Thu, 15 Jul 1999 08:46:36 -0700 (PDT),
Eduardo E. Horvath e...@one-o.com said:
Where do you guys get this misinformation?
:
Note the `19464k reserved'; that space has been
:Both Dillon and Sobral mistakenly claimed that Solaris overcommits,
:this fact seems to be somewhat suggestive.
:
:And also, the followings are allocated memory and reserved memory
:in my environment. (This table also includes Eduardo's example)
:
: SunOS allocated reservedtotal
1 - 100 of 166 matches
Mail list logo
