was able to load the
> >>drivers. I think you need to add "device sound" to get these modules to
> >>build automgically.
> >
> >No, the modules are built regardless of the kernel options you use.
>
> Hmm; how did ctodd know they weren't?
I have
Has anyone considered or accomplished allowing FreeBSD to write it's
current state (including window manager, windows, etc) to swap and
allowing a subsequent reload of the system to last state? This would be
sort of like the sleep mode of a laptop, but would allow the user to boot
into another OS
Trying to install 4.10/i386 on an amd64 system with Promise raid
controller. The saga
Can't use 4.x install disk because kernel doesn't support raid (at least
the promise controller).
Can boot off of 5.x install disk and switch media, but install fails
because it can't find the base distribu
On Wed, 29 Dec 2004, Lowell Gilbert wrote:
> [EMAIL PROTECTED] writes:
>
> > Has anyone gotten 4.x installed on this type of system? (ASUS A8V,
> > Athlon64 3500+, Promise PDC20378 (AKA Fastrak 378, TX2000), and Marvell
> > 88E8001 Gbe) If so, how did you align all the planets with the sun to
> >
On Sun, 2 Jan 2005, Bill Moran wrote:
> But it's a great way to boot Linux under Windows, or FreeBSD under
> either, or have multiple OSes running simultaneously under a single
> computer.
How good is device support from within vmware? Can I get to
serial/usb/audio/network ports seamlessly?
Chr
I just upgraded one of my Via systems (fresh install) to 5.3-R. I cvsup'd
the src (RELENG_5_3) and attempted a build world, but it consistently
fails when building libbfd. Given that it's a compiler error I thought it
may have something to do with the C3 processor. I know there's a conflict
with G
> I've just compiled RELENG_5 yesterday evening on a VIA C3 Samuel 2
> (EPIA 5000 Eden) without any problems. Perhaps you've cvsup(ed) at
> the wrong time?
Well I am pulling from a local mirror, but it updates nightly.
> What do you have in /etc/make.conf?
Just the CVS stuff. Keep in mind I'm p
> It seems like a safe assumption that 5.3-RELEASE was compiled for
> i386, because I was able to use it without any problems on the C3,
> including make buildworld/buildkernel/... If you did a buildworld/
> installworld with some special flags in the past, that userland may
> include CMOVs. That'
I'm looking for information on how to properly customize a FreeBSD
distribution when using the "make release" framework. I've made some
attempts to include a custom kernel in my own release, but this kernel
never makes it's way into the staging area (i.e. ftp distribution). The
documentation on th
