At 09:48 PM 10/17/2005 -0400, Mike Silbersack wrote:
| > Hi,
| >
| > On a server I'm benchmark testing, via local host, I'm getting Limiting
| > closed
| > port RST response from to 200 packets/sec on the console when I'm
| > running a
| > lot of local connections very quickly all at once (a
On Tue, 18 Oct 2005 07:17:54 -0500, <[EMAIL PROTECTED]> wrote:
Hi all,
I failed this steps. FreeBSD cannot recognized my username.
I will try it again. Have anybody another solution ??
Did you read link that I have given?
Cheers,
Mezz
Thanks before.
regards.
Thanks for you all,
I will do
Hi all,
I failed this steps. FreeBSD cannot recognized my username.
I will try it again. Have anybody another solution ??
Thanks before.
regards.
> Thanks for you all,
> I will do this step.
>
> regards.
>
>> Hi,
>>
>> I would suggest you to try the below and make sure this
>> works
>>
>> 1 ) Inst
At 1:25 PM -0600 10/17/05, M. Warner Losh wrote:
In message: <[EMAIL PROTECTED]>
Gary Kline <[EMAIL PROTECTED]> writes:
: vi was the first screen/cursor-based editor in computer
: history.
Are you sure about this? I was using screen oriented editors over a
1200 baud dial
> Hi,
>
> On a server I'm benchmark testing, via local host, I'm getting Limiting
> closed
> port RST response from to 200 packets/sec on the console when I'm
> running a
> lot of local connections very quickly all at once (about 7500 per second).
> I've
> added the following:
>
> net.inet.
On Tue, 18 Oct 2005 02:22, [EMAIL PROTECTED] wrote:
> /usr/src/sys/i386/conf/TARTAR ../../conf/files: FreeBSD: must be count,
> optional, mandatory or
> standard
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
Looks like you broke sys/conf/files somehow.
Do a cvs
Hi,
On a server I'm benchmark testing, via local host, I'm getting Limiting closed
port RST response from to 200 packets/sec on the console when I'm running a
lot of local connections very quickly all at once (about 7500 per second). I've
added the following:
net.inet.tcp.log_in_vain: 0
n
Hi, (wondering off on a tangent), re:
> I was using screen oriented editors over a
> 1200 baud dialup line in 1977 on a PDP-11 running RSTS/E on a Behive...
Around this time I think full-screen editors from
DEC that took advantage of the VT-52 (and later
VT-100) included KED, EDT, and may
In message: <[EMAIL PROTECTED]>
Gary Kline <[EMAIL PROTECTED]> writes:
: vi was the first screen/cursor-based editor in computer
: history.
Are you sure about this? I was using screen oriented editors over a
1200 baud dialup line in 1977 on a PDP-11 running RSTS/E on a Be
2005/10/17, Marc Fonvieille <[EMAIL PROTECTED]>:
> On Mon, Oct 17, 2005 at 02:46:56AM +0400, Oleg Petrov wrote:
> > Hello, FreeBSD people.
> >
> > First thing to mention is that I'm very experienced Emacs user. I was using
> > it
> > for 4-5 years or so. But sometime ago i began to feel myself so
2005/10/17, kamal kc <[EMAIL PROTECTED]>:
> > > sys/malloc.h has function prototypes for malloc()
> > > kern/kern_malloc.c defines the malloc()
> > >
> > > the malloc() definition is
> > >
> > > void *
> > > malloc(size, type, flags)
> > > unsigned long size;
> > > struct malloc_type *type;
Hello list,
I am trying to add a new directory (NIC) to my base system (FreeBSD5.4)
to support an experimental card. But I have this error trying to build
the kernel.
--
>>> Kernel build for TARTAR started on Mon Oct 17 09:48:55 PDT 2005
On Mon, Oct 17, 2005 at 04:49:20PM +0200, Marc Fonvieille wrote:
>
> I'd say "s/nvi/vim" (see http://www.vim.org/) if you want to really do
> everything with your Vi.
>
Err, sorry for the cross-post :(
Marc
___
freebsd-hackers@freebsd.org mailing list
On Mon, Oct 17, 2005 at 02:46:56AM +0400, Oleg Petrov wrote:
> Hello, FreeBSD people.
>
> First thing to mention is that I'm very experienced Emacs user. I was using it
> for 4-5 years or so. But sometime ago i began to feel myself so uncomfortable
> with it for some reasons: first, i use many dif
Hi.
I need to write some user interface to perform some tasks with USB
storage devices. One of the tasks is to show a list of all USB
storage connected and all slices/partitions and filesystems in them.
With tools like usbdevs and sysctl, I can find out what USB devices
are connected, and also w
On Mon, 17 Oct 2005 21:56, kamal kc wrote:
> the man pages use M_FOOBUF(where did it come from ??)
> in the field type.
'foo' is a generic term for a random variable name.
> Now how should i code it.
>
> struct malloc_type mytype;
> mytype=MALLOC_DEFINE(.,"mybuffers","mybuffers");
>
> what s
Hi, Kamal
On 17.10.2005 04:49:01, kamal kc wrote:
> this may be a trivial question for many of you
> but i am confused in doing memory allocation in the
> kernel.
>
> sys/malloc.h has function prototypes for malloc()
> kern/kern_malloc.c defines the malloc()
>
> the malloc() definition is
>
>
On Mon, Oct 17, 2005 at 02:46:56AM +0400, Oleg Petrov wrote:
> Hello, FreeBSD people.
>
> First thing to mention is that I'm very experienced Emacs user. I was using it
> for 4-5 years or so. But sometime ago i began to feel myself so uncomfortable
> with it for some reasons: first, i use many dif
Hello, FreeBSD people.
First thing to mention is that I'm very experienced Emacs user. I was using it
for 4-5 years or so. But sometime ago i began to feel myself so uncomfortable
with it for some reasons: first, i use many different systems and emacs isn't
default application for FreeBSD or any o
On Mon, 17 Oct 2005 21:19, kamal kc wrote:
> void *
> malloc(size, type, flags)
> unsigned long size;
> struct malloc_type *type;
> int flags;
>
> i understand the size and flags but what shall i
> do with the malloc_type.
man 9 malloc
It is used to do basic sanity checking and f
> > sys/malloc.h has function prototypes for malloc()
> > kern/kern_malloc.c defines the malloc()
> >
> > the malloc() definition is
> >
> > void *
> > malloc(size, type, flags)
> > unsigned long size;
> > struct malloc_type *type;
> > int flags;
> >
> > i understand the size and fla
this may be a trivial question for many of you
but i am confused in doing memory allocation in the
kernel.
sys/malloc.h has function prototypes for malloc()
kern/kern_malloc.c defines the malloc()
the malloc() definition is
void *
malloc(size, type, flags)
unsigned long size;
st
22 matches
Mail list logo
