FreeBSD 6

Lowell Gilbert freebsd-questions-local at be-well.ilk.org
Tue Jul 26 20:46:41 GMT 2005


FreeBSD 6 (which hasn't been released yet, and will change a bit more
before it is) is still very cutting edge.  I would *strongly*
recommend that you follow the -CURRENT mailing list if you're going to
use it.

Nikolas Britton <nikolas.britton at gmail.com> writes:

> On 7/26/05, Nikolas Britton <nikolas.britton at gmail.com> wrote:
> > On 7/26/05, Nikolas Britton <nikolas.britton at gmail.com> wrote:
> > > Do I always need to run 'make cleandepend' when rebuilding a kernel,
> > > normally I build my kernels the old school way?
> > >
> > > Is it just me or is -O2 now the default for kernel builds? What about
> > > -Os, safe to use?

Yes, and not sure.

> > > The kernel build failed when it tired to compile the r128drm device.

With a default kernel?  Try updating your sources again.

> > > Is it safe to run the ULE scheduler instead of the 4BSD scheduler, ULE
> > > is commented out in the default kernel?

See the -CURRENT list archives.  It's gotten fairly stable for a lot
of people, and performs better in a number of cases, but it still
causes trouble in some others.

> > > Is the new ATA RAID stuff, metadata something, going to be backported
> > > to 5.x? I'm trying setup a RAID 1 mirror with Intel ICH5R / Adaptec
> > > HostRAID but it looks like it's not supported in 5.x

Search for messages about that.  SOS@ has discussed it quite a bit, if
I recall correctly.

> > One more thing... Will FreeBSD 5.4 kernel modules work under 6.x?

No.

> 
> Sorry! a few more things:
> 
> At boot up I get these errors / warnings:
> "kenv: unable to get dumpdev"

Try setting dumpdev?

> "no such user: _dhcp, falling back to "nobody""
> 
> I left groups and master.passwd files to deal with later in
> mergemaster and then I manually added the dhcp user to both of those
> files but the system still can't find him.

You rebuilt the password database, right?  You know you can't just
open up the password file and edit it?

> "Starting default moused: moused: unable to open /dev/ums0: Device busy"
> 
> I don't know whats up with that but my mouse does work.

And if you disable moused?

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
		http://be-well.ilk.org/~lowell/


More information about the freebsd-questions mailing list