It seems Paulo Fragoso wrote:
Hi,
I'm using one atapi-cdrw (CREATIVE CD-RW RW4224E/1.36) and works fine but
I don't know change speed to 4x, now I'm burning at double speed (I'm
spending 37min to burn one full cd). I've got other unit (YAMAHA-SCSI)
which spends 17min for a full cd but
On 22-Sep-99 Soren Schmidt wrote:
Are there any way to make wormcontrol burns cds at 4x speed?
Not directly, but your driver _should_ use the max speed as default.
You could ad a command to force the drive to max speed in the driver
though...
IMHO there should be a way to force it..
Warner Losh wrote:
In message [EMAIL PROTECTED] Wes Peters writes:
: Is there any possibility of creating a database of devfs perms that gets
: loaded into kernel-accessible data space by the loader before boot? Once
: the system is up, devfsd could take over, monitoring and updating the
It seems Daniel O'Connor wrote:
On 22-Sep-99 Soren Schmidt wrote:
Are there any way to make wormcontrol burns cds at 4x speed?
Not directly, but your driver _should_ use the max speed as default.
You could ad a command to force the drive to max speed in the driver
though...
In message [EMAIL PROTECTED] Wes Peters writes:
: Interrupt, DMA, I/O settings, promiscuous operation, baud rate and parity,
: etc. Any little thing a device driver might desire...
I had been specifically thinking of things more obscure like the
WNETID for wavelan cards, the frequency ranges
Anyhow, I have some changes to the worm stuff, it needs to be dealt with
to handle modern HW, and to deal with all the possible block formats
thats possible on a CD nowadays. It will probably mean the death of
the worm stuff as is now, but I'm the last user anyways so
NO! There is me as
It seems Luigi Rizzo wrote:
Anyhow, I have some changes to the worm stuff, it needs to be dealt with
to handle modern HW, and to deal with all the possible block formats
thats possible on a CD nowadays. It will probably mean the death of
the worm stuff as is now, but I'm the last user
On Tue, 21 Sep 1999 20:06:41 EST, "Pedro Fernando Giffuni" wrote:
Gawk has more features, but I saw a test somewhere that showed a
bug in the FreeBSD version. I can dig it up if someone is really
interested.
PR 13615
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Wed, 22 Sep 1999, Soren Schmidt wrote:
It seems Paulo Fragoso wrote:
Hi,
I'm using one atapi-cdrw (CREATIVE CD-RW RW4224E/1.36) and works fine but
I don't know change speed to 4x, now I'm burning at double speed (I'm
spending 37min to burn one full cd). I've got other unit
It seems Paulo Fragoso wrote:
I'm using one atapi-cdrw (CREATIVE CD-RW RW4224E/1.36) and works fine but
I don't know change speed to 4x, now I'm burning at double speed (I'm
spending 37min to burn one full cd). I've got other unit (YAMAHA-SCSI)
which spends 17min for a full cd but
Hello,
Could some one point me to or send to me a driver that use KLD.
What should I do
to make driver module? Should I manually run attach and probe in module?
Thanks.
Kurakin Roman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of
Graham Wheeler wrote:
The server creates a domain socket to listen for requests with the
path /cage/tmp/server. The client runs chrooted in the /cage directory,
and creates a domain socket /tmp/client.pid. It sends a request to
the server with a sendto() specifying the socket address
Greets .. are there existing daemons/proxies which convert UDP packets into TCP
packets to
act as some kind of relay?
client -udp- relay -tcp- server
kind regards
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Wed, Sep 22, 1999 at 04:19:28PM +0200, eT wrote:
Greets .. are there existing daemons/proxies which convert UDP packets into TCP
packets to
act as some kind of relay?
client -udp- relay -tcp- server
kind regards
ports/net/netcat is your friend.
Cheers,
--
Ruslan Ermilov
:where SIZE was 4 MB in this case. I ran it on the console (I've got 64 MB
:of RAM and 128 MB of swap) until the swap pager went out of space and
:my huge process was eventually killed as expected. Fine. But when I ran
:it under X Window, the system eventually killed the X server (SIZE ~20
Warner Losh wrote:
In message [EMAIL PROTECTED] Wes Peters writes:
: Interrupt, DMA, I/O settings, promiscuous operation, baud rate and parity,
: etc. Any little thing a device driver might desire...
I had been specifically thinking of things more obscure like the
WNETID for wavelan
First, let me warn you that this is a often recurring thread. It has
already showed up two or three times this year alone.
Ivan wrote:
I had a look at vm_pageout.c and noticed that situations may occur where
no process can be killed. I guess that in such situations memory
allocation
On Thu, 23 Sep 1999, Daniel C. Sobral wrote:
First, let me warn you that this is a often recurring thread. It has
already showed up two or three times this year alone.
Ivan wrote:
I had a look at vm_pageout.c and noticed that situations may occur where
no process can be killed. I
On Thu, 23 Sep 1999, Daniel C. Sobral wrote:
I had a look at vm_pageout.c and noticed that situations may occur where
no process can be killed. I guess that in such situations memory
allocation requests are simply rejected ( e.g. malloc returning NULL ) .
Err... no. Malloc() does not
On Wed, 22 Sep 1999, Alfred Perlstein wrote:
Terry Lambert brought up an interesting thought from AIX (I think),
instead of killing a process, it just sleeps the requesting process
until the situation alleviates itself. Of course this can wind up
wedging an entire system, it would probably
Ivan wrote:
Of course I didn't mean that malloc() calls the pageout daemon ... I
simply meant that if no more memory space can be regained (in particular
by killing a process) then at some point memory allocations will be
refused -- or else, when does malloc() ever returns NULL ?!
When
On Wed, 22 Sep 1999, Chuck Robey wrote:
On Wed, 22 Sep 1999, Alfred Perlstein wrote:
Terry Lambert brought up an interesting thought from AIX (I think),
instead of killing a process, it just sleeps the requesting process
until the situation alleviates itself. Of course this can wind
What kind of resources are there that both cause loss of swap AND are
freed up by sleeping a process?
four things i can think of:
1) Along with 'SIGDANGER' it allows the system to fix itself.
That's another issue. Don't mix sleeping processes with SIGDANGER, they
are independant of
How about this - add an 'importance' resource. The lower the number,
the more likely the process will be killed if the system runs out of
resources. We would also make fork automatically decrement the number
by one in the child.
The default would be 1000. The sysadmin
On Wed, 22 Sep 1999, Nate Williams wrote:
What kind of resources are there that both cause loss of swap AND are
freed up by sleeping a process?
four things i can think of:
1) Along with 'SIGDANGER' it allows the system to fix itself.
That's another issue. Don't mix sleeping
On Wed, 22 Sep 1999, Matthew Dillon wrote:
How about this - add an 'importance' resource. The lower the number,
the more likely the process will be killed if the system runs out of
resources. We would also make fork automatically decrement the number
by one in the child.
On Wed, 22 Sep 1999, Nate Williams wrote:
Maybe, and then again, maybe not. A program is requesting memory, so
putting other processes to sleep *keeps* them from freeing up memory.
The process that is trying to use memory is put to sleep. In the
machine runs out of swap cases I have seen
What kind of resources are there that both cause loss of swap AND are
freed up by sleeping a process?
four things i can think of:
1) Along with 'SIGDANGER' it allows the system to fix itself.
That's another issue. Don't mix sleeping processes with SIGDANGER, they
are
Maybe, and then again, maybe not. A program is requesting memory, so
putting other processes to sleep *keeps* them from freeing up memory.
The process that is trying to use memory is put to sleep.
Then this 'rogue' process is never allowed to free up any of it's
resources, hence the
: (Matt)
: How about this - add an 'importance' resource. The lower the number,
: the more likely the process will be killed if the system runs out of
: resources. We would also make fork automatically decrement the number
: by one in the child.
:
: The default would be
On Wed, 22 Sep 1999, Matthew Dillon wrote:
: (Matt)
: How about this - add an 'importance' resource. The lower the number,
: the more likely the process will be killed if the system runs out of
: resources. We would also make fork automatically decrement the number
: by
On Wed, 22 Sep 1999, Nate Williams wrote:
Not only that but perhaps reserving an amount of backing store for
root may be a good idea, artificially limit the resources to several
pages to enable root to actually do something in such a situation.
Stick to the topic at hand. That's
Not only that but perhaps reserving an amount of backing store for
root may be a good idea, artificially limit the resources to several
pages to enable root to actually do something in such a situation.
Stick to the topic at hand. That's another topic again, and the topic
is the
Chuck Robey wrote:
What kind of resources are there that both cause loss of swap AND are
freed up by sleeping a process?
Any of them being consumed by short-lived processes that will run to
completion and exit while everyone else is sleeping. This assumes such
processes exist, of course.
On Wed, 22 Sep 1999, Soren Schmidt wrote:
I've just commited a change to the ata driver wormcontrol, so now
you should be able to use the keywords: single double quad max
in the speed selection field. Its not very well tested yet though..
Try it and watch with systat how high the transfer
Matthew Dillon wrote:
How about this - add an 'importance' resource. The lower the number,
the more likely the process will be killed if the system runs out of
resources. We would also make fork automatically decrement the number
by one in the child.
As far as I'm
Nate Williams wrote:
Maybe, and then again, maybe not. A program is requesting memory, so
putting other processes to sleep *keeps* them from freeing up memory.
The process that is trying to use memory is put to sleep.
Then this 'rogue' process is never allowed to free up any of
On Mon, 20 Sep 1999, Julian Elischer wrote:
as I explained a few days ago,
MFS explodes because it synthesises a device vnode
The synthesized vnode is someohow confused as to whether it's a devfs
vnode or a UFS vnode.
I can't remember the exact problem but it may have something to do with
On Wed, 22 Sep 1999, Wes Peters wrote:
Chuck Robey wrote:
What kind of resources are there that both cause loss of swap AND are
freed up by sleeping a process?
Any of them being consumed by short-lived processes that will run to
completion and exit while everyone else is sleeping.
Kazutaka YOKOTA [EMAIL PROTECTED] wrote:
In the past, it has been pointed out that some of the termcap entries
needs updating.
Indeed. I just noticed that screen still has trouble in xterm, due
to a broken termcap entry. Would a committer please take care of
PR #12209?
--
Christian "naddy"
Soren Schmidt wrote:
It seems Luigi Rizzo wrote:
Anyhow, I have some changes to the worm stuff, it needs to be dealt with
to handle modern HW, and to deal with all the possible block formats
thats possible on a CD nowadays. It will probably mean the death of
the worm stuff as is
Hi,
I have got a surprising problem with StarOffice 5.1
for Linux on FreeBSD 4.0-current, the latest snapshot.
The CD-ROM installation went fine (after I configured the
Posix real-time thread support and linked the
additional libraries to the Linux compatibility
directory and slightly corrected
How can I tell how big fifo buffers are?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Wed, 22 Sep 1999, Wayne Cuddy wrote:
How can I tell how big fifo buffers are?
limits.h I would guess...?
#define_POSIX_PIPE_BUF 512
Andrew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Hi,
I have got a surprising problem with StarOffice 5.1
for Linux on FreeBSD 4.0-current, the latest snapshot.
The CD-ROM installation went fine (after I configured the
Posix real-time thread support and linked the
additional libraries to the Linux compatibility
directory and slightly
From [EMAIL PROTECTED] Thu Sep 23 00:36:13 1999
Return-Path: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 8151 invoked from network); 23 Sep 1999 00:36:12 -
Received: from user2.teleport.com ([EMAIL PROTECTED])
by smtp8.teleport.com with SMTP; 23 Sep 1999 00:36:12
Hi,
I'm doing TCP development on a custom operating system that I've
written and am using my FreeBSD box for testing my TCP stack. I'm in
the early stages right now and I have a lot of bugs. One of my bugs
is that I shut down a connection on my end but I'm doing something
wrong and the
On Wed, 22 Sep 1999, Alfred Perlstein wrote:
What kind of resources are there that both cause loss of swap AND are
freed up by sleeping a process?
four things i can think of:
1) Along with 'SIGDANGER' it allows the system to fix itself.
2) Allow the operator to determine which program
Perhaps this is already possible somehow, but...
In working with a graphical based embedded system (non-xwin), I'll typically
mmap the graphic files and bcopy them straight to our hardware blitter. This
works very nicely, since the kernel caches what it can off the disk, but
when more ram is
On Wed, 22 Sep 1999, Mark Newton wrote:
Has anyone had any problems running FreeBSD-SMP on Intel GX-chipset
motherboards?
We're having trouble with the Intel L440GX+ boards not rebooting, but
FreeBSD runs peachy on them. Haven't stress-tested SMP mode but it does
boot and operate. Our
Matthew Dillon wrote:
How about this - add an 'importance' resource. The lower the number,
the more likely the process will be killed if the system runs out of
resources. We would also make fork automatically decrement the number
by one in the child.
Well, that's one
On Thu, 23 Sep 1999, Daniel C. Sobral wrote:
Matthew Dillon wrote:
How about this - add an 'importance' resource. The lower the number,
the more likely the process will be killed if the system runs out of
resources. We would also make fork automatically decrement the
On a freshly supped -current I get:
location type 0 in non-PLT relocations
./make_keys
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/keys.list
init_keytry.h
/usr/libexec/ld-elf.so.1: /usr/obj/usr/src/tmp/usr/lib/libc.so.3:
Unsupported relocation type 0 in non-PLT relocations
***
53 matches
Mail list logo
