Mason Loring Bliss wrote:
> 
> Hi again, all.
> 
> It seems that #including "ioconf.h" in grf.c was the only thing needed to
> successfully build the 1.3B kernel. Everything seems to be running smoothly
> so far.

Hmmm...perhaps it's an actual bug.  You might want to ask Scott or Steve
Allen since they're likely to have built a -current kernel.
 
> I have a couple silly questions.
> 
> 1) In /etc/myname I have "acheron.middleboro.ma.us", sans quotes. I noticed
> in /etc/rc/conf that there are spots to include both a hostname and a domain
> name. Would I be correct in assuming that I'd include nothing but "acheron"
> as the hostname, and nothing but "middleboro.ma.us" as the domain name?

That will work, although if your /etc/resolv.conf is setup correctly, I
don't think the domainname is necessary.  Feel free to stick with the
"older" method, although you might want to move the domain part of your
hostname out of /etc/myname and into /etc/defaultdomain.

> I
> don't have a sufficient clue, and I didn't see anything in the rc.conf man
> page that would point in either direction. My sendmail and everything else
> work well enough with my current setup, but I'd like to do things in the
> canonical fashion.

Well, you never know what you might wind up breaking, so keep a backup
copy :-)

> 2) Why is -current -currently at 1.3B, and not 1.3A? I remember something
> from the netbsd-current list from Perry saying that he was going to explain
> this, but evidently I missed the explanation. Just curious.

I believe that Jason checked in some big changes the day before sup
switched back over to -current, thus the bump in version number (it had
been 1.3A since sometime back in late November, I believe).  If you check
the CHANGES file a little over a week ago, you'll probably see what it
was.

> 3) I'm finally running X on my SE/30. (I found an old 500-meg drive that
> seems to work. It died after a while a year or so ago when I was running
> it on my Mac, and I expect that it will die eventually in its current
> situation, but until then, I have space for X... :) I noticed that there
> seems to be a nice little screen blanker that kicks in after a while.
> The settings don't seem to be in Xsetup_0... I'd like to change the amount
> of idle time until sleep, but I can't find where to do it. Where is this
> particular setting... set?

Actually, the settings probably are there, you just have to look harder
:-)

The command you want to read about is the xset(1) utility, which controls
things like the screensaver, console bell, mouse acceleration, etc.  I
usually turn the screensaver off and run xautolock with xlockmore (well,
actually, I think xautolock turns off the screensaver itself).

I hope this helps some...and now I'm going to go get some sleep before I
make any more typos.

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.