Doug White wrote:
>
> On Thu, 31 Aug 2000, Arjan Knepper wrote:
>
> > Anyone experience with this board?
> > Any comments? Recomandations?
>
> I have a ze card that we bought for use as a cheap term server, but found
> that the card is particular about the motherboard chipset. We had some
> te
Josef Karthauser wrote:
> You're not using the flags for colourized ls are you?
>
> If you do:
>
> % ls > /tmp/ls
> % cat /tmp/ls | more
>
> Does it still leave the screen inverted?
>
> Joe
>
Joe,
As in the first place, on the first screen it does not get the screen inverted but on
the second
On Fri, Sep 01, 2000 at 08:48:56AM +0100, Theo PAGTZIS wrote:
> Josef Karthauser wrote:
>
> > You're not using the flags for colourized ls are you?
> >
> > If you do:
> >
> > % ls > /tmp/ls
> > % cat /tmp/ls | more
> >
> > Does it still leave the screen inverted?
> >
> > Joe
> >
>
> Joe,
>
> As
Hi,
I wonder if it is possible to redirect stdout/stderr to syslog.
Background:
I'm writing a program which starts (fork=>execvp) and observes
another program. I would like to redirect all output of the "execvped"
program to syslog.
I know this is not really FBSD related but I hope you can help
man 1 logger
pipe your stdout/stderr to logger(1), and you're all set. You may even
specify a facility/level to log with.
G'luck,
Peter
--
What would this sentence be like if pi were 3?
On Fri, Sep 01, 2000 at 01:58:56PM +0200, Alexander Maret wrote:
> Hi,
>
> I wonder if it is possible to
Can lex/yacc (flex, bison, byacc, whatever) be used on an arbitrary
string, not an input stream? Like lines read from a config file,
or received through a network socket, or.. lots of uses; is there a way?
G'luck,
Peter
--
If the meanings of 'true' and 'false' were switched, then this sentence
> -Ursprungliche Nachricht-
> Von: Peter Pentchev [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 1. September 2000 14:00
>
> man 1 logger
>
> pipe your stdout/stderr to logger(1), and you're all set.
> You may even
> specify a facility/level to log with.
>
Thanks for your quick answ
>
> > -Ursprungliche Nachricht-
> > Von: Peter Pentchev [mailto:[EMAIL PROTECTED]]
> > Gesendet: Freitag, 1. September 2000 14:00
> >
> > man 1 logger
> >
> > pipe your stdout/stderr to logger(1), and you're all set.
> > You may even
> > specify a facility/level to log with.
> >
>
>
On Fri, Sep 01, 2000 at 02:13:19PM +0200, Alexander Maret wrote:
> > -Ursprungliche Nachricht-
> > Von: Peter Pentchev [mailto:[EMAIL PROTECTED]]
> > Gesendet: Freitag, 1. September 2000 14:00
> >
> > man 1 logger
> >
> > pipe your stdout/stderr to logger(1), and you're all set.
> > Yo
On Fri, 1 Sep 2000, Josef Karthauser wrote:
> It sounds like 'more' is the culprit, not 'ls'.
>
> Joe
FWIW, I've seen the inverted color problem a few times since less replaced
more, but haven't taken the effort to figure out when exactly it's
happening.
Ironically, it seems more likely to ha
>
>I've put the latest patches for tagged queueing on ATA disks up
>for ftp on:
>
> ftp://freebsd.dk/pub/ATA/ATA-tagged-queueing-diff-0831.gz
On my testmachine:
atapci0: port 0xffa0-0xffaf at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
ad0: 17206MB
Of course I should have done a "boot -v" (thanks neph!)
Doesn't work with tagged queueing:
ad0: ATA-4 disk at ata0-master
ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, UDMA66
ad0: piomode=4 dmamode=2 udmamode=4 cblid=1
Works with tag
On Thu, 31 Aug 2000, Peter Dufault wrote:
[..]
> I want to attach a gdb running on my FreeBSD system to something
> running on that wicked slow Sun. I've built a gdb with a target
> machine of "sparc-sun-solaris2.7", I've got an executable, but I
> haven't found a way to run something on the Su
> On Thu, 31 Aug 2000, Peter Dufault wrote:
>
> [..]
>
> > I want to attach a gdb running on my FreeBSD system to something
> > running on that wicked slow Sun. I've built a gdb with a target
> > machine of "sparc-sun-solaris2.7", I've got an executable, but I
> > haven't found a way to run som
/dev/cuaa1 turned out to be the culprit. I tested this
by `echo "hello" > /dev/cuaa1` on the debugger and
`cat /dev/cuaa1` on the debuggee. The hello makes it across.
Now I'm having some "packet error" problems with kgdb.
On the debuggee I ctrl-alt-esc into ddb and do:
db> gdb
db> step
>Fro
Hi, I discovered the source of my problem and solved it. For those
interested, here is an explanation:
The flags of the serial I/O device to be used for remote
debugging needs to be changed in the config file. I plugged
a null modem cable across the two ports labeled 1 (the other one
labeled 2)
Hi,
Like the subject says, I'm looking for documentation
on the SIOCSPGRP ioctl call:
rc = ioctl(port,SIOCSPGRP,&pid);
I've gone through the source tree and while I can find
references where it's used, and where the functionality
is defined, there appears to be no doc (or man page).
B
> Hi,
>
> I wonder if it is possible to redirect stdout/stderr to syslog.
>
> Background:
> I'm writing a program which starts (fork=>execvp) and observes
> another program. I would like to redirect all output of the "execvped"
> program to syslog.
>
> I know this is not really FBSD related but
On Sep 1, 3:24pm, Peter Pentchev wrote:
} Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC]
} On Fri, Sep 01, 2000 at 02:13:19PM +0200, Alexander Maret wrote:
} > > -Ursprungliche Nachricht-
} > > Von: Peter Pentchev [mailto:[EMAIL PROTECTED]]
} > > Gesendet: Freitag, 1. September
On Fri, Sep 01, 2000 at 04:10:40PM -0700, Don Lewis wrote:
> On Sep 1, 3:24pm, Peter Pentchev wrote:
> } No, I don't think you can do anything cheaper than a fork and
> } a pipe(2). popen(), as suggested in another message, is pretty
> } much the same. I don't think stdio has a hook to capture a
On Sep 1, 4:55pm, John DeBoskey wrote:
} Subject: SIOCSPGRP documentation?
} Hi,
}
}Like the subject says, I'm looking for documentation
} on the SIOCSPGRP ioctl call:
}
} rc = ioctl(port,SIOCSPGRP,&pid);
}
}I've gone through the source tree and while I can find
} references where it's
Hi all,
I hope this is the right place to ask; I've searched the mailing lists and
can't find any comments, so I hope it's not just me! I'm following the
current development branch and all has been (generally) okay until the
29th of aug, since when I've been unable to get the kernel to boot
succ
22 matches
Mail list logo
