On Tue, Jun 15, 1999 at 08:59:59AM -0700, Arun Sharma wrote:
While we're on the init topic, is there any strong feeling here about
BSD /etc/rc* scripts Vs SysV ?
Yes, lots. The last round of discussion was covered in the freebsd-arch
mailing list, the archives should be enlightening.
N
--
san...@sanpei.org (MIHIRA Yoshiro) writes:
# Yes, We modify some ports to support start,stop.
And others to no longer support it. The Apache 1.2 port used to
support it, the Apache 1.3 port doesn't. Here's a replacement:
#!/bin/sh
if [ ! -x /usr/local/sbin/apachectl ] ; then
echo
David Scheidt dsche...@enteract.com writes:
# cd /; (cd /cdrom; tar cvf - usr/share/examples/drivers ) | tar xvf -
should work.
# cd /cdrom tar cvf - usr/share/examples/drivers | tar xvf - -C /
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to
It seems Tommy Hallgren wrote:
--- Mike Smith m...@smith.net.au wrote:
We'd previously encountered problems with the Infortrend controller not
at all liking the other disks we'd tried to talk to; a collection of
Cheetahs with IBM and Compaq firmware simply wouldn't work. This time
we
-Original Message-
From: Daniel Baker [SMTP:dba...@cuckoo.com]
Sent: Wednesday, June 16, 1999 5:12 AM
To: freebsd-hackers@freebsd.org
Subject: Typo: sys/pci/pcisupport.c
4.0-CURRENT: sys/pci/pcisupport.c:
955:/* VIA Technologies -- vendor 0x1106 /
956:
955:/* VIA Technologies -- vendor 0x1106 /
956:case 0x05861106: /* south bridge section */
957:return (VIA 82C586 PCI-ISA bridge);
This is cute. Moo.
[ML] Yes. A comment-within-a-comment compiler warning would
have been nice. AFAIK, gcc
On Tue, 15 Jun 1999, Daniel Baker wrote:
4.0-CURRENT: sys/pci/pcisupport.c:
955:/* VIA Technologies -- vendor 0x1106 /
956:case 0x05861106: /* south bridge section */
957:return (VIA 82C586 PCI-ISA bridge);
This is cute. Moo.
Fixed. Thanks.
- bill
-Original Message-
From: Nick Hibma [SMTP:nick.hi...@jrc.it]
Sent: Wednesday, June 16, 1999 2:27 PM
To: Ladavac Marino
Cc: FreeBSD hackers mailing list
Subject: RE: Typo: sys/pci/pcisupport.c
It does, just no one checking. Someone needs to go and fix warnings
again in
pointer-pointer-object.method;
where he wanted
pointer-pointer-object.method();
hpux CC did not say a word. Naturally, the method had desired
side effects :)
Port your application to see more compiler warnings. It sounds like
perl -e 'use strict; ...' :-)
There is a story behind it: our product was shipping for hpux
and was later ported to sinix. It had some instabilities during
development (it was first developed for hpux, then the enhancements were
ported to sinix, almost in parallel).
A colleague wrote (paraphrased)
We'd previously encountered problems with the Infortrend controller not
at all liking the other disks we'd tried to talk to; a collection of
Cheetahs with IBM and Compaq firmware simply wouldn't work. This time
we had better luck with real Seagate firmware, and the array
Yesterday I was able to mount my CD-ROM just fine. Today after
a lot of kernel hacking I am not. I am fairly new at this so
this may be a really easy answer.
I have an entry in the fstab file that references my cdrom
/dev/wcd0c /cdromro, noauto 0 0
but when I goto mount /cdrom I get an
Yesterday I was able to mount my CD-ROM just fine. Today after
a lot of kernel hacking I am not. I am fairly new at this so
this may be a really easy answer.
I have an entry in the fstab file that references my cdrom
/dev/wcd0c /cdromro, noauto 0 0
but when I goto mount /cdrom I get an
Once morpheus_...@depechemode.com aka (morpheus_...@depechemode.com) said:
Yesterday I was able to mount my CD-ROM just fine. Today after
a lot of kernel hacking I am not. I am fairly new at this so
this may be a really easy answer.
I have an entry in the fstab file that references my cdrom
Is this board supported? Anyone using them?
Dennis
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
In article 53425.929320...@zippy.cdrom.com you write:
And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin
And before people jump on me, let me just clarify in advance that I
was not meaning to imply that Apollo ever used the x86 architecture.
They didn't. It was just an example.
I don't seem to be able to get 3.2 to do a SL/IP
install (this is for a laptop which seems to be
having PAO problems...)
Turning on DEBUG in the install options, I can watch
it nicely execute:
ifconfig sl0 inet 10.0.0.98 10.0.0.99 netmask 255.255.255.0
but - not matter what - that always
On Thu, 20 May 1999, The Tech-Admin Dude wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I could add another one, top(1) frequently does that on this machine..
so whatever answers you get, be sure to forward them to me :).
Blast from the past, but since no one gave you an
I've ported PC-card boot.flp to -current.
Source patch can be found at
http://wing-yee.ntc.keio.ac.jp/hosokawa/pccard-flp/current-diff-19990616.tar.
gz
I was offline for a while - apologies for not getting back to you.
I have the new ones, and my box is busy building world with them
I don't seem to be able to get 3.2 to do a SL/IP
install (this is for a laptop which seems to be
having PAO problems...)
Turning on DEBUG in the install options, I can watch
it nicely execute:
ifconfig sl0 inet 10.0.0.98 10.0.0.99 netmask 255.255.255.0
but - not matter what -
Does anybody ever used this option?
options BOOTP_NFSROOT
I'd like to use it, to boot a computer from a boot disk, and start a
diskless station by mounting via NFS all the file system.
The problem is that I don't know how to use it.
and I don't know how to make the disk boot without using
At a chipset level (DEC 21143) yes...in the same way a Znyx card would
work.
It looks like the card also uses a DEC bridge chip too (not unussual on
multi-port Ethernet cards) and FreeBSD will also cope fine with that too.
HOWEVER...be aware that some BIOSes mess up the initialization of such
To add more to this - tracing through in.c in the kernel,
I see that when you configure an interface it eventually
works its way down to rtrequest - to add a route for
the new interface.
I believe rtrequest() is the one returning EEXIST which is
what causes ifconfig on sl0 to always complain
As Willem Jan Withagen wrote ...
In article 53425.929320...@zippy.cdrom.com you write:
And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin
And before people jump on me, let me just clarify in advance that I
was not meaning to imply that Apollo ever used the x86
On 16-Jun-99 Daniel O'Connor wrote:
On 16-Jun-99 John Baldwin wrote:
Whoops.. just ifconfig de0. Have you tried using the interface? We use
for a lab I help run, and 'arp -a' on the clients does not show an entry
for
the local de0 card they have installed, but they work fine
dro...@rpi.edu said:
:- While others seemed too busy with new technology to bother with
:- ugly-old-NFS problems, Matt dived in and pursued them with enough
:- enthusiasm to make a real difference.
In particular, lots of NFS bugs that had been there, and reported,
since early 2.2 days. Bugs
Well -
I've added some printf()s to determine that what I suspected
was correct. The route is being entered into the table
twice.
If looks like in_ifinit() is calling the sioctl() routine,
which calls if_up(), which then adds the route.
Then, in_ifinit() goes on to add another route and
At 05:06 PM 6/16/99 -0400, you wrote:
At a chipset level (DEC 21143) yes...in the same way a Znyx card would
work.
It looks like the card also uses a DEC bridge chip too (not unussual on
multi-port Ethernet cards) and FreeBSD will also cope fine with that too.
HOWEVER...be aware that some BIOSes
In article 199906161952.vaa05...@gratis.grondar.za
m...@grondar.za writes:
I was offline for a while - apologies for not getting back to you.
I have the new ones, and my box is busy building world with them right
now.
I'll commit if nobody else can/wants to...
Please note that this patch
In article 19990608084217.a5...@alaska.cert.siemens.de,
Udo Schweigert u...@cert.siemens.de wrote:
I'm using it (runsocks cvsup -P m) for a year now and it works
without any problems. (Since cvsup 16 the -P m is not needed, so
runsocks cvsup should so it).
Just to make sure I understand:
Thomas David Rivers wrote:
To add more to this - tracing through in.c in the kernel,
I see that when you configure an interface it eventually
works its way down to rtrequest - to add a route for
the new interface.
I believe rtrequest() is the one returning EEXIST which is
what causes
Thomas David Rivers wrote:
To add more to this - tracing through in.c in the kernel,
I see that when you configure an interface it eventually
works its way down to rtrequest - to add a route for
the new interface.
I believe rtrequest() is the one returning EEXIST which is
what
On Wed, 16 Jun 1999, Robert Withrow wrote:
dro...@rpi.edu said:
:- While others seemed too busy with new technology to bother with
:- ugly-old-NFS problems, Matt dived in and pursued them with enough
:- enthusiasm to make a real difference.
In particular, lots of NFS bugs that had been
Hi,
I've been doing some work which caused me to want to write a simple
userland bridging/filtering program (don't ask ;-). The easy way to do it
seemed to be to use BPF to read and write the packets one each side. I
wrote something up in a few hundred lines of code which worked (mostly) as
Load balancing will always be done at the driver level, and not in board
logic...you want those separate MACs etc. :-)
This is true of all the boards I'm familiar with.
I'm actually trying to implement EtherChannel under FreeBSD for Znyx
boards right now.
-marc
Hi,
I've been doing some work which caused me to want to write a simple
userland bridging/filtering program (don't ask ;-). The easy way to do it
ok, i won't ask, just remind you that freebsd (in 2.2.8, 3.2, 4.x)
has bridging integrated with the ipfw so you can do bridging and
filtering
36 matches
Mail list logo
