As I recall, Jordan Hubbard wrote:
> Guys,
>
> We need to figure out whether this is going to go in pre-4.3 or not.
Gotta have a working dump.
Lotsa folks install off the release CDs, and never upgrade between
releases.
-crl
--
Chad R. Larson (CRL15) 602-953-1392 Brother, can you p
Michael VanLoon wrote:
>
> The example I found was not correct for the format of configuration used in
> 4.1, and when I try to fudge it, I get no smb probe on startup.
>
> What's a correct configuration for smbus0 and/or smb0?
>
> Thanks...
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> wit
On Thu, 19 Apr 2001, Domas Mituzas wrote:
> We've got Intel ISP2150 chasis with two quantum atlass 36g drives,
> connected via SCA to mylex acceleraid 170 (firmware 6.x).
>
> Mylex logical volume was inicialized using automatic setup, cause it fully
> satisfied our needs (fault-tolerant mirror)
In message <[EMAIL PROTECTED]>, Thomas
Quinot wri
tes:
> Le 2001-04-17, Cy Schubert - ITSD Open Systems Group écrivait :
>
> > I don't see how a fix like this would risk the integrity of the
> > upcoming 4.3-RELEASE.
>
> Other scripts could parse the output of netstat and depend on
> the typo.
Hello!
> I have recently upgraded Apache/modssl via the ports collection to
> 1.3.19-2.8.2. This seems to have broken persistent connections to my
> PostgreSQL database.
>
> It seems that while persistent connections open fine, they are not being
> returned to the pool for reuse, the end result
Hello,
I just cvsup'ed and upgraded my desktop box from 4.2 stable (12202000) to
what is now 4.3RC (04192001) including all ports I wanted to use. I used
pkg_version to find out which ports needed recompiling/installation. Almost
everything works, even KDE2.1, building the parts one by one. Ho
Hello,
one more kernel panic.
We've got Intel ISP2150 chasis with two quantum atlass 36g drives,
connected via SCA to mylex acceleraid 170 (firmware 6.x).
Mylex logical volume was inicialized using automatic setup, cause it fully
satisfied our needs (fault-tolerant mirror).
It always (during s
I have recently upgraded Apache/modssl via the ports collection to
1.3.19-2.8.2. This seems to have broken persistent connections to my
PostgreSQL database.
It seems that while persistent connections open fine, they are not being
returned to the pool for reuse, the end result being that PostgreSQ
Hello!
I've been preparing some FreeBSD boxes for the new project going on, and
when I already created all needed images, and cloned my second box, I
encountered this problem:
$ man whatever
it yields
/usr/libexec/ld-elf.so.1: Cannot open "/usr/lib/libz.so.2"
Which is very strange :-(
When I
:: Yes, this is a test system. Will be changing modem capable of
:: 56K upstream,
:: if project works.
There is no such thing, AFAIK. Not even the V.92 modems will do 56Kbps
upstream.
-- Juha
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the me
oppps... sorry i forgot to mention that there is a pap-secret file with the
entries:
#client server password ipaddr
* * "" *
At 04:32 PM 4/19/01 +0900, you wrote:
>its not ppp-login it should be pap-secrets
>
>
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EM
Yes, this is a test system. Will be changing modem capable of 56K upstream,
if project works.
At 12:17 AM 4/19/01 -0700, you wrote:
> You do know that if two 56K modems call each other, the maximum
> speed is
>33.6K.
>
> DS
>
> > -Original Message-
> > From: [EMAIL PROT
12 matches
Mail list logo
