===> Vulnerability check disabled, database not found
===> Extracting for db42-4.2.52_4
=> MD5 Checksum mismatch for bdb/db-4.2.52.tar.gz.
=> SHA256 Checksum mismatch for bdb/db-4.2.52.tar.gz.
=> MD5 Checksum OK for bdb/patch.4.2.52.1.
=> SHA256 Checksum OK for bdb/patch.4.2.52.1.
=> MD5 Checksu
First, and before anything, you normally log in as root or are you just
trying to impress us?
Second, ram is a lot faster than using swap.
Third, the problem with the ssh trying to log in probably has to do with a
hostname resolving problem.
that is about it.
david
On Wed, 25 Dec 2002, Charli
I was wondering if anyone has had any more thoughts on this problem.
-- Forwarded message --
Date: Mon, 23 Dec 2002 13:10:40 -0800 (PST)
From: David Nicholas Kayal <[EMAIL PROTECTED]>
To: John Bleichert <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: mount pro
On Mon, 23 Dec 2002, John Bleichert wrote:
> Did you build this drive in another box and then swap it over to the box
> it's in now? Sounds like the bootloader doesn't know where your drive is
> (which is common if you swap in a root drive). Assuming you're using
> the standard FreeBSD bootloade
Is there an http://www.tuxedo.org/~esr/faqs/smart-replys.html?
Here is a copy of my fstab file:
> more fstab
# See the fstab(5) manual page for important information on automatic mounts
# of network filesystems before modifying this file.
#
# DeviceMountpoint FStype Options
For the past two freebsd installations I've done, I've run into a problem
where they system, upon booting, throws me into a manual root filesystem
specification prompt where I need to manually type the file system and the
device I wish to boot off of.
Yet when I check things such as /etc/fstab eve
