> > I tried to build today's STABLE on 6.0-BETA2 FreeBSD 6.0-BETA2 #1: Wed Aug
> > 3
> > Kernel config differs from GENERIC just by atapicam device.
>
> Obviously, your userland and kernel sources are not synchronized. It is
> probably the cause of failed build.
>
> Update complete source tree
On 9.10.2005 00:41, Marcin Koziej wrote:
> > > I tried to build today's STABLE on 6.0-BETA2 FreeBSD 6.0-BETA2 #1:
> > > Wed Aug 3 Kernel config differs from GENERIC just by atapicam
> > > device.
> >
> > Obviously, your userland and kernel sources are not synchronized. It
> > is probably the cau
Am Samstag, 8. Oktober 2005 03:29 CEST schrieb Brandon Fosdick:
> I have a Soekris crypto card (hifn driver) in a box that I don't have
> immediate access to. Is there some way to disable the card w/o rebooting
> the machine? I know I could take the driver out of the kernel or force
> it not to loa
I Could be wrong, but i believe that you dont have to disklabel your
GEOM devices on sysinstall.. just make sure you load the geom_mirror
module on your /boot/loader.conf file
(add geom_mirror_load="YES")
and mount the mirrored device...
Upon loading, the geom_mirror module will read the metadata
I made the somewhat unexpected discovery that in FreeeBSD 5-STABLE,
if I use the "tmp*" variables in /etc/rc.conf to have an MFS /tmp
created, it is apparentyly not swap-backed -- as I expected from
the part of the mdmfs man page that reads:
By default, mdmfs creates a swap-based (MD_SWAP) di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a firewall with a small CF installation of FreeBSD 5.2.1
(post 20040814). It is missing the sysctl variable:
net.inet.ip.random_id. I am wondering if one of the libraries or
kernel objects I ripped out to minimize the install could be the
cu
In the last episode (Oct 09), Jeremy Baggs said:
> I have a firewall with a small CF installation of FreeBSD 5.2.1 (post
> 20040814). It is missing the sysctl variable: net.inet.ip.random_id.
> I am wondering if one of the libraries or kernel objects I ripped out
> to minimize the install could b
I had a bad ide cable which I have now replaced. on
bootup the filesystem produced a lot of errors and I
lost my first superblock. I since fsck'd and repaired
the superblock at sector 32. At no time does fsck
create, fix, or transfer the sector 32 superblock to
the front of the drive. mount won
