syscons is already capable of changing forground and background colors
via escape sequences. Is it not sufficient for your intended
application?
Kazu
Hi,
I'm thinking of messing with the syscons ioctl handler to allow setting
of color values - all EGA- and VGA-compatible video controllers
On Tue, Jan 09, 2001 at 05:32:29PM +0900, Kazutaka YOKOTA wrote:
syscons is already capable of changing forground and background colors
via escape sequences. Is it not sufficient for your intended
application?
Kazu
Since I received the same question in private mail more than once,
I
On Tue, Jan 09, 2001 at 05:32:29PM +0900, Kazutaka YOKOTA wrote:
syscons is already capable of changing forground and background colors
via escape sequences. Is it not sufficient for your intended
application?
Kazu
Since I received the same question in private mail more than once,
I
On Tue, Jan 09, 2001 at 06:24:30PM +0900, Kazutaka YOKOTA wrote:
On Tue, Jan 09, 2001 at 05:32:29PM +0900, Kazutaka YOKOTA wrote:
syscons is already capable of changing forground and background colors
via escape sequences. Is it not sufficient for your intended
application?
Kazu
Gerhard Sittig wrote:
[ citing from Doug's message in the "OT: silence ..." subthread
to keep the technical discussion in the "how to test" subthread ]
On Tue, Jan 05, 2001 at 14:45 -0800, Doug Barton wrote:
You stated in another post that you wished I had elaborated
more. I was in a
On Mon, 8 Jan 2001, Vijo Cherian wrote:
hi,
I have some questions... but most of them may be prerry lame because I am new
to FreeBSD.
I am running 5.0 and I have a driver for a card which was written for 4.1.
The driver uses bus_if.h, device_if.h and pci_if.h and these files are
On Tue, 9 Jan 2001, Doug Barton wrote:
But that's exactly what you're trying to do. I will not bother to
re-re-restate my points as to why what you're proposing is a bad idea.
Do all the testing you want, but make sure you understand that there
will be vigorous resistance to
On Tue 2001-01-09 (02:14), Doug Barton wrote:
Gerhard Sittig wrote:
[ citing from Doug's message in the "OT: silence ..." subthread
to keep the technical discussion in the "how to test" subthread ]
On Tue, Jan 05, 2001 at 14:45 -0800, Doug Barton wrote:
You stated in another
Today found any problem. What is it ?
freebsd:/usr/ports/security/sslwrap# make
=== Building for sslwrap-2.0.5
cc -o sslwrap s_server.c s_socket.c s_cb.c -O -pipe -DFLAT_INC
-DOPENSSL="\"openssl/\"" -L/usr/lib -lssl -lcrypto -I/usr/include
s_server.c: In function `sv_body':
This post would be better suited for the -ports mailing list, as it is
a list which deals specifically with the FreeBSD Ports Collection.
Also, one of the first people you could ask about a port problem
would be the port maintainer as specified in the Makefile. In this case,
it is [EMAIL
Hi all
I am attempting to port the cheops network mapping/diagnostic program
from Linux to FreeBSD (see www.marko.net/cheops). One of the first snags
I have hit comes in using SIOCGIFCONF to queries the network interface
names and addresses.
The cheops code assumes that the buffer returned will
Just a follow up on this: on Stevens vol 2 pg 117, code line 299, is the
implication that the returned buffer DOES hold an array of struct ifreq
elements. So this does seem to indicate that something may be broken on
FreeBSD. At the very least there is some ambiguity - is this an array of
struct
On Mon, 8 Jan 2001, John Baldwin wrote:
Unloading modules adds all sorts of new problems. Right now the WITNESS code
will do bad bad things if you kldunload a module that contains a mutex. Even
if the mutex is mtx_destroy'd because it still has a reference to its name in
the internal
On Mon, 8 Jan 2001, Greg Lehey wrote:
On Monday, 8 January 2001 at 10:04:44 +0200, Roman Shterenzon wrote:
* Roman Shterenzon [EMAIL PROTECTED] [010107 10:24] wrote:
Hi,
Could you please take a look at :
http://www.freebsd.org/cgi/query-pr.cgi?pr=24019
It's my friend's PR. Can you
On Tue, Jan 09, 2001 at 12:21:11PM +0200, Graham Wheeler wrote:
I am attempting to port the cheops network mapping/diagnostic program
from Linux to FreeBSD (see www.marko.net/cheops). One of the first snags
I have hit comes in using SIOCGIFCONF to queries the network interface
names and
On Tue, Jan 09, 2001 at 12:30:44PM +0200, Graham Wheeler wrote:
Just a follow up on this: on Stevens vol 2 pg 117, code line 299, is the
implication that the returned buffer DOES hold an array of struct ifreq
elements. So this does seem to indicate that something may be broken on
FreeBSD. At
David Malone wrote:
On Tue, Jan 09, 2001 at 12:21:11PM +0200, Graham Wheeler wrote:
I am attempting to port the cheops network mapping/diagnostic program
from Linux to FreeBSD (see www.marko.net/cheops). One of the first snags
I have hit comes in using SIOCGIFCONF to queries the
David Malone wrote:
If you read the paragraph below that code, it notes that the ifreq
structures are of variable length. The spacing depends on the size
of the returned info.
That's true. In which case the cheops code is wrong, as it iterates
through the list by incrementing a pointer to a
David Malone wrote:
If you read the paragraph below that code, it notes that the ifreq
structures are of variable length. The spacing depends on the size
of the returned info.
David.
Something that isn't clear to me - do you know (Mark for Linux, Dave or
someone else for FreeBSD)
Something that isn't clear to me - do you know (Mark for Linux, Dave or
someone else for FreeBSD) whether it is reasonable to assume the
ifr_name if the struct ifreq will be NUL terminated? I know that the
name in a struct sockaddr_dl is not necessarily so terminated, but for
the ifr_name
Marko - does Linux have getifaddrs()? I somehow doubt it...
Linux should have getifaddrs() if it has support for IPv6 in
userland libraries. There is an implimentation of it at:
http://www.linux-ipv6.org/cvsweb/libinet6/?cvsroot=usagi-libc
David.
To Unsubscribe: send mail to [EMAIL
On Tue, Jan 09, 2001 at 03:39:22PM +0200, Graham Wheeler wrote:
David Malone wrote:
If you read the paragraph below that code, it notes that the ifreq
structures are of variable length. The spacing depends on the size
of the returned info.
That's true. In which case the cheops code
On Mon, 8 Jan 2001, Mike Smith wrote:
Actually, I'm not sure that it does. They use the Symbios part with
the integrated ARM processor, and assume that SCSI passthrough works.
Maybe I was reading the docs for the passthrough interface incorrectly but
I was under the impression that the RAID
On 09-Jan-01 Julian Elischer wrote:
On Mon, 8 Jan 2001, John Baldwin wrote:
Unloading modules adds all sorts of new problems. Right now the WITNESS
code
will do bad bad things if you kldunload a module that contains a mutex.
Even
if the mutex is mtx_destroy'd because it still has a
Neil Blakey-Milner wrote:
On Tue 2001-01-09 (02:14), Doug Barton wrote:
Gerhard Sittig wrote:
You're blowing the significance of this part of your argument WAY out
of proportion. After long discussion we've picked times for the periodic
jobs that are the best overall choices,
At 10:51 AM 01/09/2001, David Malone wrote:
Marko - does Linux have getifaddrs()? I somehow doubt it...
Linux should have getifaddrs() if it has support for IPv6 in
userland libraries. There is an implimentation of it at:
http://www.linux-ipv6.org/cvsweb/libinet6/?cvsroot=usagi-libc
Hello again.
On Tue, 9 Jan 2001, Doug Barton wrote:
Neil Blakey-Milner wrote:
On Tue 2001-01-09 (02:14), Doug Barton wrote:
The point I'm trying (obviously in vain) to make is having cron do what
amounts to "slewing its internal clock" will not work for everyone, and
violates
Dear all,
I continued investigating the problem and at
http://www5.compaq.com/products/servers/linux/OptionsMatrix.html
I was surprised to find out that not even Linux supports tape drives
(cpqarray) driver with the Compaq Integrated Smart Array Controller.
I say "not even" as Compaq claims
Doug Barton wrote:
Neil Blakey-Milner wrote:
On Tue 2001-01-09 (02:14), Doug Barton wrote:
Gerhard Sittig wrote:
This way, we never repeat jobs, and never lose jobs. Which makes cron
reliable.
For your definition of "reliable." Personally, I find cron doing exactly
what it's
How can I convert the following gmake syntax into something that
FreeBSD's make can understand?
%.x: %.o libtinker.a
${F77} ${LINKFLAGS} -o $@ $^ ${LIBS}
Thanks.
--
Glenn Johnson
USDA, ARS, SRRC Phone: (504) 286-4252
New Orleans, LA 70124 e-mail: [EMAIL
Thanks to all of you for your very useful answers! Here is how I solved my
noise problem:
1- the hard drive was by far the biggest culprit: I swapped it with an old
laptop HD (2.5 inch) with the appropriate connector/converter that connects
to a regular IDE ribbon cable and AT power,
2- cut the
On 09-Jan-01 Glenn Johnson wrote:
How can I convert the following gmake syntax into something that
FreeBSD's make can understand?
%.x: %.o libtinker.a
${F77} ${LINKFLAGS} -o $@ $^ ${LIBS}
.o.x:
${F77} ${LINKFLAGS} -o $@ $ libtinker.a ${LIBS}
Try that. My mailer has
On Tue, Jan 09, 2001 at 04:11:18PM -0800, John Baldwin wrote:
On 09-Jan-01 Glenn Johnson wrote:
How can I convert the following gmake syntax into something that
FreeBSD's make can understand?
%.x: %.o libtinker.a
${F77} ${LINKFLAGS} -o $@ $^ ${LIBS}
.o.x:
On Wed 2001-01-10 (08:51), Greg Black wrote:
If any change to expected cron behaviour is to be introduced,
the traditional behaviour must be the default, with a knob
documented in the man pages that can be twisted to get the
oddball behaviour that is being proposed here.
The oddball
34 matches
Mail list logo
