Chris Coleman wrote:
>
> On one of our servers, deleted space is not being freed and causing is to
> run out of disk space. To test this, I copied a 200 meg file to the /usr
> partition and then deleted it. I checked df before copying, after copying,
> and after deleting it. After deleting it,
Following Brian's suggestion, I've modified gif to create a /dev/if_gif
device with is controlled by the IOCIFMANAGE ioctl which allows creation
and deletion of specific devices and creation of wildcard devices. I've
hacked ifconfig to support this in a general manner. If you know which
one you
I don;t know why people always forget it, but also look
at the sample driver in -current.
/usr/share/examples/drivers/make_device_driver.sh
(the 4.x version is way out of date)
On Fri, 8 Jun 2001, Sergey Babkin wrote:
> j mckitrick wrote:
> >
> > Okay, there is something i'm not understandin
> Looking at the description of the sysKonnect dual adapter, its not clear if
> this is a real 2 port nic or that the second port is only a failover port. I
> have 2 questions for anyone who has one:
>
> 1) Can this be used as a 2 port gigabit NIC?
Yes. You will have two interfaces, sk0 and sk
In article <[EMAIL PROTECTED]>,
milunovic <[EMAIL PROTECTED]> wrote:
>
> I'm little confused.I'm reading ELF specification and I found that
> p_offset and p_vaddr should be congrunet to module PAGE_SIZE.
> So is this correct ? If it isn't can anybody tell me what is correct.
It is correct. It
j mckitrick wrote:
>
> Okay, there is something i'm not understanding here. In the ed driver,
> there are many possible cards, which each have different i/o ports, correct?
> The driver has a lot of probe routines, and it looks like they are just
> using different macros with hard-coded (#define
Oh my, and just posting these I found a couple of bugs!
:char *
:safe_replace(char **pptr, const char *s)
:{
:/*
: * Same data (also occurs if s == *ptr), nothing to do
: */
:if (*pptr) {
: if (s && strcmp(s, *pptr) == 0)
: return(*pptr);
: free(*pptr);
Here is the whole set of supporting routines.
-Matt
/*
* STRDUP.C
*
* $Backplane: backplane/src/libsupport/strdup.c,v 1.13 2001/04/03 00:03:18 dillon Exp
$
*/
#include "defs.h"
Export char *safe_strdup(const char *s);
Export char *safe_strdup_s
:OK, here's a scenario:
:
:struct validation_fun {
: const char *name;
: valfun *fun;
: int dyn;
:};
:
:This is a structure for a set of validation functions, referenced by
:name from another type of object. There are some predefined functions,
:present
On Fri, Jun 08, 2001 at 06:47:01PM +0300, Giorgos Keramidas wrote:
> On Fri, 8 Jun 2001, Deepak Jain wrote:
>
> > Is this a hardware issue or an application problem? The kernel is 4.1
> > RELEASE. The RAM is ECC.
>
> I would start by removing a few RAM chips and seeing if this happens
> when a p
On Fri, Jun 08, 2001 at 12:17:41PM -0500, Kevin Day wrote:
> I looked at this.. I see how I can dlopen my own executable, and dlsym()
> will let me get addresses from symbol names, but how do I do the reverse? I
> have an address and need to get the symbol name from it, not vice versa.
dladdr(3)
>
> > Since some strings are non-constant (the are allocated) - I believe
> > the `const' qualifier in the structure declaration is incorrect.
>
> 'const' just means "I will not be modifying this"; it's a way for a
> function prototype to constrain the function's implementation.
>
Yes - it
On Fri, Jun 08, 2001 at 03:55:55PM -0400, [EMAIL PROTECTED] wrote:
> In a message dated 06/08/2001 1:28:22 PM Eastern Daylight Time,
> [EMAIL PROTECTED] writes:
>
> > > 1) Can this be used as a 2 port gigabit NIC?
> > > 2) Does this NIC have hardware failover (that is, when power is cut the
>
In a message dated 06/08/2001 1:28:22 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> > 1) Can this be used as a 2 port gigabit NIC?
> > 2) Does this NIC have hardware failover (that is, when power is cut the
2
> > ports will be physically tied together. I dont know of any PC plug in
On Fri, Jun 08, 2001 at 09:39:15PM +0200, Bernd Walter wrote:
> On Thu, Jun 07, 2001 at 03:20:58PM -0700, Matt Dillon wrote:
> >
> > :
> > :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote:
> > :>
> > :> :
> > :> :Thanks, I will try setting errno, but I don't think it is signals.
> >
On Thu, Jun 07, 2001 at 03:20:58PM -0700, Matt Dillon wrote:
>
> :
> :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote:
> :>
> :> :
> :> :Thanks, I will try setting errno, but I don't think it is signals.
> :> :I have been running truss on the process. The relevant part is
> :> :
> :>
On Fri, 8 Jun 2001, Deepak Jain wrote:
> I've never seen this error. Its been occuring randomly on this
> machine, sometimes as often as every few minutes, sometimes days
> apart.
>
> Others have seen this error (based on a Google search) but nothing recent
> and nothing that conclusive. This is
Yes, its only happening on this one chassis so far. We'll try replacing the
memory and see what happens.
Thanks!
Deepak Jain
AiNET
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Assar Westerlund
Sent: Friday, June 08, 2001 9:07 AM
To: [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
I'm little confused.I'm reading ELF specification and I found that
p_offset and p_vaddr should be congrunet to module PAGE_SIZE.
So is this correct ? If it isn't can anybody tell me what is correct.
#define PAGE_SIZE 4096
p_offset % PAGE_SIZE == p_vaddr % PAGE_
> Since some strings are non-constant (the are allocated) - I believe
> the `const' qualifier in the structure declaration is incorrect.
'const' just means "I will not be modifying this"; it's a way for a
function prototype to constrain the function's implementation.
--
... every activity me
On Fri, Jun 08, 2001 at 07:51:08PM +0200, Stefan Hoffmeister wrote:
>
> What are the status of / plans for support of select wide character
> routines, such as the ones declared in wchar.h?
>
> Particularly, I am looking for wcsoll, towupper, and towlower - IOW, the
> whole barrage of wide chara
What are the status of / plans for support of select wide character
routines, such as the ones declared in wchar.h?
Particularly, I am looking for wcsoll, towupper, and towlower - IOW, the
whole barrage of wide character transformation and collation :-)
I haven't found anything conclusive in th
On Fri, Jun 08, 2001 at 01:18:44PM -0400, [EMAIL PROTECTED] wrote:
> Looking at the description of the sysKonnect dual adapter, its not clear if
> this is a real 2 port nic or that the second port is only a failover port. I
> have 2 questions for anyone who has one:
>
> 1) Can this be used as a
i can only answer question 1) - yes, it can be used as a dual port
gigabit nic
i can hardly imagine the syskonnect offers failover...
hth
cu
rené
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 8. Juni 2001 18:19
An: [EMAIL PROTECTED]
Betre
* Kevin Day <[EMAIL PROTECTED]> [010608 13:21] wrote:
> >
> > In the last episode (Jun 08), Kevin Day said:
> > > Is there a simple way that I can lookup a symbol name(by address)
> > > during runtime?
> > >
> > > I know I can exec nm, look up for the address I need, and get local
> > > symbols,
>
> In the last episode (Jun 08), Kevin Day said:
> > Is there a simple way that I can lookup a symbol name(by address)
> > during runtime?
> >
> > I know I can exec nm, look up for the address I need, and get local
> > symbols, but it would be really nice if I could get addresses of
> > functio
Looking at the description of the sysKonnect dual adapter, its not clear if
this is a real 2 port nic or that the second port is only a failover port. I
have 2 questions for anyone who has one:
1) Can this be used as a 2 port gigabit NIC?
2) Does this NIC have hardware failover (that is, when p
>
> Kevin Day wrote:
> >
> > Is there a simple way that I can lookup a symbol name(by address) during
> > runtime?
>
> man dlopen.
>
I looked at this.. I see how I can dlopen my own executable, and dlsym()
will let me get addresses from symbol names, but how do I do the reverse? I
have an add
In the last episode (Jun 08), Kevin Day said:
> Is there a simple way that I can lookup a symbol name(by address)
> during runtime?
>
> I know I can exec nm, look up for the address I need, and get local
> symbols, but it would be really nice if I could get addresses of
> functions in dynamic lib
Kevin Day wrote:
>
> Is there a simple way that I can lookup a symbol name(by address) during
> runtime?
man dlopen.
--
farooq <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Fri, Jun 08, 2001 at 12:09:39PM -0500, Kevin Day wrote:
>
>
> Is there a simple way that I can lookup a symbol name(by address) during
> runtime?
>
> I know I can exec nm, look up for the address I need, and get local
> symbols, but it would be really nice if I could get addresses of functi
Is there a simple way that I can lookup a symbol name(by address) during
runtime?
I know I can exec nm, look up for the address I need, and get local
symbols, but it would be really nice if I could get addresses of functions
in dynamic libraries as well. I know I could use ldd to get offsets o
In article [EMAIL PROTECTED]> you write:
>This thread is baffling. The bottom line is that you cant trust data coming
>into your machine, and you have to checksum it. The link level check only
>verifies that what was sent by the last forwarding point is the same as what
>you got, but in NO WAY
This thread is baffling. The bottom line is that you cant trust data coming
into your machine, and you have to checksum it. The link level check only
verifies that what was sent by the last forwarding point is the same as what
you got, but in NO WAY implies that all of the data is valid. A li
On Fri, 8 Jun 2001, Peter Pentchev wrote:
>On Fri, Jun 08, 2001 at 01:49:12PM +0100, Rasputin wrote:
>You can only use kernel-space functions in kernel code, that is, writing
>a kernel module, or writing a piece of code that is to be compiled along
>with the rest in src/sys.
By the way, are ther
Assar Westerlund wrote:
>
> Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> > On Fri, Jun 08, 2001 at 02:24:23PM +0200, Assar Westerlund wrote:
> > > Terry Lambert <[EMAIL PROTECTED]> writes:
> > > > This all came from IP headers being 14 bytes long, instead
> > > > of 16.
> > >
> > > Hu? An IPv4 h
> E.. this was the whole point of this thread. I *can't* cast
> a (const char *) to a (char *) when using the -Wcast-qual gcc flag -
Not all -W options are equally useful and some are actively harmful.
This is one of them. There are several situations where it is
necessary to remove a quali
On Fri, Jun 08, 2001 at 03:09:53PM +0200, Assar Westerlund wrote:
> Peter Pentchev <[EMAIL PROTECTED]> writes:
> > My explanation was a reply to a suggestion to remove the 'const' in
> > the structure definition.
>
> My fault. The code that I should have shown was without the 'const'.
> With gcc
Peter Pentchev <[EMAIL PROTECTED]> writes:
> My explanation was a reply to a suggestion to remove the 'const' in
> the structure definition.
My fault. The code that I should have shown was without the 'const'.
With gcc 2.95.3 and 'gcc -O -g -Werror -Wall -W -Wcast-qual -c foo.c'
I don't get any
"Deepak Jain" <[EMAIL PROTECTED]> writes:
> Others have seen this error (based on a Google search) but nothing recent
> and nothing that conclusive. This is a very standard config that has been
> stable for quite a while. The panic: malloc: lost data implies to me that
> something is misbehaving w
On Fri, Jun 08, 2001 at 03:02:56PM +0200, Assar Westerlund wrote:
> Peter Pentchev <[EMAIL PROTECTED]> writes:
> > GCC complains when I try to initialize the structure with something like:
> >
> > struct validation_fun val_init[] = {
> > {"init",valfun_init,0}
> > };
> >
>
Peter Pentchev <[EMAIL PROTECTED]> writes:
> GCC complains when I try to initialize the structure with something like:
>
> struct validation_fun val_init[] = {
> {"init",valfun_init,0}
> };
>
> This can be avoided by:
>
> struct validation_fun val_init[] = {
> {(char *)
>
> On Fri, Jun 08, 2001 at 08:51:54AM -0400, Thomas David Rivers wrote:
> > >
> > > GCC complains when I try to initialize the structure with something like:
> > >
> > > struct validation_fun val_init[] = {
> > > {"init",valfun_init,0}
> > > };
> > >
> > > This can be avoide
On Fri, Jun 08, 2001 at 08:51:54AM -0400, Thomas David Rivers wrote:
> >
> > GCC complains when I try to initialize the structure with something like:
> >
> > struct validation_fun val_init[] = {
> > {"init",valfun_init,0}
> > };
> >
> > This can be avoided by:
> >
> > st
On Fri, Jun 08, 2001 at 01:49:12PM +0100, Rasputin wrote:
> * Peter Pentchev <[EMAIL PROTECTED]> [010608 13:35]:
> > On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin wrote:
> > > I'm playing with resettodr(9), to set the BIOS clock from the system time..
>
> > As others pointed out, resettodr(9
>
> GCC complains when I try to initialize the structure with something like:
>
> struct validation_fun val_init[] = {
> {"init",valfun_init,0}
> };
>
> This can be avoided by:
>
> struct validation_fun val_init[] = {
> {(char *) (uintptr_t) "init", valfun_init,0}
* Peter Pentchev <[EMAIL PROTECTED]> [010608 13:35]:
> On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin wrote:
> > I'm playing with resettodr(9), to set the BIOS clock from the system time..
> As others pointed out, resettodr(9) is a kernel-space function.
> Section 9 of the manual is for those
On Fri, Jun 08, 2001 at 06:55:50AM -0400, Thomas David Rivers wrote:
> Peter Pentchev <[EMAIL PROTECTED]> wrote:
> >
> > On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote:
> > >
> > > On 07-Jun-01 Peter Pentchev wrote:
> > > > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev w
Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> On Fri, Jun 08, 2001 at 02:24:23PM +0200, Assar Westerlund wrote:
> > Terry Lambert <[EMAIL PROTECTED]> writes:
> > > This all came from IP headers being 14 bytes long, instead
> > > of 16.
> >
> > Hu? An IPv4 header (not including options) is 20 byte
On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin said:
> I'm playing with resettodr(9), to set the BIOS clock from the system time..
>
> I get warning about syntax errors in systm.h:
>
> [rasputin@dogma rasputin]$ gcc b0rken.c
> In file included from b0rken.c:3:
> /usr/include/sys/systm.h:333
On Fri, Jun 08, 2001 at 02:24:23PM +0200, Assar Westerlund wrote:
> Terry Lambert <[EMAIL PROTECTED]> writes:
> > This all came from IP headers being 14 bytes long, instead
> > of 16.
>
> Hu? An IPv4 header (not including options) is 20 bytes long.
>
Terry meant the length of an IPv4 header up
On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin wrote:
> I'm playing with resettodr(9), to set the BIOS clock from the system time..
>
> When I try to compile the following snippet,
>
> [rasputin@dogma rasputin]$ cat b0rken.c
> #include
> #include
> #include
>
> int main(void){
> resetto
Terry Lambert <[EMAIL PROTECTED]> writes:
> This all came from IP headers being 14 bytes long, instead
> of 16.
Hu? An IPv4 header (not including options) is 20 bytes long.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Garance A Drosihn <[EMAIL PROTECTED]> writes:
> So, we could fix this by:
> 1) changing /bin/sh
This you have already done and I think it's ok.
> 2) changing make not to call /bin/sh with -e
> 3) changing 'automake' to include a "true;" statement
> in that 'for' loop (or s
I didn't think resettodr(9) was a system call exposed to user program,
but instead a function available to be called from kernel code. Thus,
the section 9 manual page.
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I'm playing with resettodr(9), to set the BIOS clock from the system time..
When I try to compile the following snippet,
[rasputin@dogma rasputin]$ cat b0rken.c
#include
#include
#include
int main(void){
resettodr();
return(0);
}
I get warning about syntax errors in systm.h:
[rasputin@dog
Peter Pentchev <[EMAIL PROTECTED]> wrote:
>
> On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote:
> >
> > On 07-Jun-01 Peter Pentchev wrote:
> > > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote:
> > >> Hi,
> > >>
> > >> Is free((void *) (size_t) ptr) the only way to fr
In message <[EMAIL PROTECTED]>, Terry Lambert writes:
>
>Use a chain allocator. I would suggest using the zone
>allocator, but it has some fundamental problems that I
>don't think are really resolvable without a rewrite.
Heh, maybe, but I'm not sure I want to write a new allocator for
this :-) B
Dave Hayes wrote:
>
> David O'Brien -Hackers <[EMAIL PROTECTED]> writes:
> > You mentioned though that your CDROM is /. How about posting the real
> > /etc/fstab from your root partition for us to have a look at?
>
> There is none. No default fstab exists.
There is no Dana, only Zuul...
I thi
Ian Dowse wrote:
>
> In message <[EMAIL PROTECTED]>, Graham Barr writes:
>
> >Also why does this happen only every few hours ? There is a lot of
> >data going through these connections maybe the timer for SO_RCVTIMEO
> >is not being reset.
> >
> >But then we have another server, with a similar n
Cejka Rudolf wrote:
>
> There is following paragraph in SUSv2:
>
> If a process sets the action for the SIGCHLD signal to SIG_IGN,
> the behaviour is unspecified, except as specified below. If the
> action for the SIGCHLD signal is set to SIG_IGN, child processes
> of the calling process
On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote:
>
> On 07-Jun-01 Peter Pentchev wrote:
> > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote:
> >> Hi,
> >>
> >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr
> >> with WARNS=2? (or more speci
Bill Fenner wrote:
>
> >The TCP checksum protects more than just the contents of the packet
> >on the wire; it's also a (somewhat) weak check on the contents
> >of your packet sitting in memory, and as it's going over the bus
> >in your computer between memory and peripherals and for other
> >end
I've never seen this error. Its been occuring randomly on this machine,
sometimes as often as every few minutes, sometimes days apart.
Others have seen this error (based on a Google search) but nothing recent
and nothing that conclusive. This is a very standard config that has been
stable for qu
Ian Dowse wrote:
> Nice idea, but I'm not sure I see the benefit of partially reclaiming
> second-level arrays. Because it is a hash array, there isn't really
> the concept of a working set; a directory that is `in use' will
> rarely see many create/rename/delete operations on a small fixed
> set
Ian Dowse wrote:
> >The only potential problem I see here is that you could
> >end up seriously fragmenting the malloc pool you are
> >using to allocate the slot arrays. And, of course, the
> >two issues you brought up in regards to regularing memory
> >use.
>
> Thanks for th
66 matches
Mail list logo
