In message <[EMAIL PROTECTED]> "Kevin Oberman" writes:
: Does this only apply after a buildworld? I assumed that I could safely
: "config KERNEL; cd ../../compile/KERNEL; make depend; make; make
: install" any time I was simply modifying my kernel--as I always do
: when the xe driver gets re-insta
As I recall, Brandon D. Valentine wrote:
> You could probably even do it in Bourne shell if you were very clean
> about it, but I would prefer to parse the conf file in perl myself.
> This would be a much better idea than SYSV-afying our init.
As we seem to be going to hash this to death, allow m
In message <[EMAIL PROTECTED]> "Chad R. Larson" writes:
: As I recall, Warner Losh wrote:
: > How are you building the new kernel? If it isn't with make
: > buildkernel KERNEL=OPAL, it isn't supported :-)
:
: Is this buildkernel target for upgrades only, or is it now the
: standard practice?
It
On Fri, Jul 07, 2000 at 07:55:46AM -0700, Alfred Perlstein wrote:
> > Yes, I could do that - I have done that already for curses.h. But I
> > still think it sucks badly that there is a variable named 'class', and I
> > still think it should be changed.
>
> A really kludgy workaround would be to m
I have not run sendmail on my systems as I receive mail elsewhere and
felt that it was mostly a potential pain in the neck. As a result, I
had 'sendmail_enable="NO"' in my rc.conf.
For various reasons (including the fact that my system is now behind a
firewall) I decided to start running sendmail
Before I go look silly filing a PR (or, heaven forfend, search the open PRs
myself), anyone know of a good reason, off hand, why the manpages for
ad, afd, and ast are still using the old 'w' names?
--David Bushong
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable"
* Jacques A. Vidrine <[EMAIL PROTECTED]> [000707 09:26] wrote:
> On Fri, Jul 07, 2000 at 07:55:46AM -0700, Alfred Perlstein wrote:
> > > Yes, I could do that - I have done that already for curses.h. But I
> > > still think it sucks badly that there is a variable named 'class', and I
> > > still th
Gerhard Sittig <[EMAIL PROTECTED]> probably said:
> > Listening on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0
> > Sending on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0
> > Sending on Socket/fallback/fallback-net
>
> I would expect the daemon to listen on and to send to a "real"
this should be fixed now... as per:
>On Thu, Jul 06, 2000 at 01:17:47PM -0700, David O'Brien wrote:
>> I am about to import 5-CURRENT Binutils. Kernel builds will be broken
>> with the new Binutils, during the time it takes me to MFC the /sys/
>> changes that will be needed.
>
>
>I declare all m
On Fri, Jul 07, 2000 at 07:56:24AM -0700, Eric J. Schwertfeger wrote:
> On Fri, 7 Jul 2000, Bob Willcox wrote:
>
> > On Wed, Jul 05, 2000 at 05:01:16PM -0700, Eric J. Schwertfeger wrote:
> > > On Tue, 4 Jul 2000, Linh Pham wrote:
> > >
> > > > Does anyone know if the boxed AMD processors that th
* Graham Wheeler <[EMAIL PROTECTED]> [000707 07:46] wrote:
> Jim King wrote:
> >
> > In that case, although it's considerably more work I'd take a look at
> > writing some C wrappers around the offending stuff. You could write the
> > wrappers such that they'd compile with the offending include
On Fri, 7 Jul 2000, Bob Willcox wrote:
> On Wed, Jul 05, 2000 at 05:01:16PM -0700, Eric J. Schwertfeger wrote:
> > On Tue, 4 Jul 2000, Linh Pham wrote:
> >
> > > Does anyone know if the boxed AMD processors that they are including the
> > > new Thunderbird varieties?
> >
> > Almost definitely n
I cvsupped today and tried to buildworld. I received the following error:
===> doc
===> libiberty
===> libbfd
sed -e s/NN/32/g
/home/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf
xx-target.h > elf32-target.h
sed -f
/home/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/
> "JK" == Jim King <[EMAIL PROTECTED]> writes:
>> > > extern "C" {
>> > > #include
>> > > }
JK> You're right, my bad. Son of a gun, I've used 'extern "C"' for gobs of
JK> stuff but I guess I never ran into C header files that had C++ reserved
JK> words.
JK> In that case, although i
Hello,
You might do well to look at http://www.freebsd.org to understand
where to post questions like this. The mailing list [EMAIL PROTECTED] is
not the correct place to post such a question. Start at that website, and
have a look through http://www.freebsd.org/handbook/index.html w
Jim King wrote:
>
> In that case, although it's considerably more work I'd take a look at
> writing some C wrappers around the offending stuff. You could write the
> wrappers such that they'd compile with the offending include file, and be
> callable from C++. Sounds tedious and time consuming,
16 matches
Mail list logo
