Date: Fri, 17 Mar 2000 19:34:29 EST From: "John Daniels" <jmd526@hotmail.com> To: dcs@newsguy.com Cc: freebsd-questions@freebsd.org, freebsd-qa@freebsd.org Subject: Need More Info Re: 4.0-RELEASE Install Message-ID: <20000318003429.28434.qmail@hotmail.com>
next in thread | raw e-mail | index | archive | help
Hi:
Thanks for the reply, but still have a problem to resolve, and some
potential problems if I don't get RSAREF.
When I startx, I get a message ("could not lookup internet address for
<domain name of my machine>..."). I believe that the message come from
Gnome. I checked my system and I found that my NIC seems to be configured
and available (as shown by ifconfig). I have a 3Com905B, which shows up as
x10 in ifconfig. My NIC is connected to a Netopia router and I use
concentric for DSL service. I installed via ftp so I'm pretty certain that
on a system level, I should be able to 'ping' or use the NIC.
The question is do I need to change gnome configurations, start pppd or
named (I have inetd running) or some other service, or do I need to change
Gnome configuration settings (and isn't it a bug if they weren't set by
ports or sysinstall?)
I haven't seen anyone else complaining, so I figure that I need to start
named (or pppd.) I tried to do this with /stand/sysinstall's postinstall
option but it didn't appear to work. Is that a bug?
How can I start named from the system? Do I just edit the configuration
file and type 'named' (from root)? If so, can someone give me some pointers
on how to edit the named config file since it is a bit confusing.
Is there something else that I need to do that I am missing?
FYI: 'localization' needs better documentation. I don't recall seeing any
explaination during the install. Others have recently had trouble with
localization and I saw a fix for this where a set of 3 'set env..' (for
US-english key mappings, etc.) commands need to be added to the csh.cshrc
file. If 'localization' in the install really does refers to site-specific
details, then this should be made clear. If not, then it would appear that
sysinstall 'localization' is indeed responsible for installing localized
keymappings, etc, and the fact that it was missing is a bug. (I complained
about this after RC3)
Also: In my install I was not able to get RSAREF. I have seen that several
people have had problems with the new rsa/crypto/security in 4.0, and I
would like to avoid that now, rather than stumble over it later.
I looked for the local and RSAREF distributions within /stand/sysinstall but
I didn't see them. (As above, I also tried to enable named from
/stand/sysinstall but apparently I couldn't.) How can I do get RSAREF (I
already know the fix for localization) from within the system itself?
Lastly, I'd like to clarify the issue of Current v. Stable. With RELENG_4
release tag, I have seen 4.0 described as the "4.0-stable branch." I have
also heard that 4.0 is very stable, much more so than 3.0 was, etc. and I am
not using the box in a production environment. Even so, since 4.0 is fairly
new, I figure that it may experience a time when CVSup-ing results in
problems. I'd rather keep that to a minimum (if I was at a level where I
could deal with such problems and had the patience and time, I would be
tracking 5.0-CURRENT). I know that I am accepting *some* risk by tracking
RELENG_4 but I would like to reduce that as much as possible. Do I simply
CVSup, then examin the mailing lists for problems for a few days, and if no
major problems are reported, then make and install a new kernel from that (2
or 3 day old) CVSup?
John
>John Daniels wrote:
> >
> > Hi:
> >
> > I installed 4.0-RELEASE on March 15th from ftp.freebsd.org and found
>these
> > problems:
> >
> > 1. "Unable to extract local distribution"
> >
> > I had the same problem with 4.0-RC3. What is the local distribution?
>Is it
> > important? Has this been fixed? Can I now get it using
>/stand/sysinstall?
>
>Jordan never clarified this, but I have always thought this refers to an
>arbitrary set of files, so that you can create distributions of your own
>to be automatically installed on your network. Ie, "local" distribution.
>:-)
>
> > 2. "Package RSAREF was not found in the Index"
> >
> > Again, can I now get this using /stand/sysinstall?
>
>Well, that I can't even test.
>
> > 3. After the system rebooted, I logged in a user account but I got the
> > message "could not lookup internet address for ..." when I started x.
>(I
> > hit a "continue" button or something and X did start - but Netscape did
>not
> > connect to any web pages) Perhaps my NIC was not being made available
>as a
> > device to the user account?
>
>That doesn't happen.
>
> > I don't recall getting the message under root, but I haven't yet tested
> > Netscape under root either. Is there some privilege that I have to set,
>or
> > some group that a user must belong to that will allow access to the NIC?
>
>No. Can you do a simple ping to local network addresses by IP? And
>addresses outside your LAN? If so, does nslookup works? Your problem
>might be either one of misconfiguration of the network (wrong network
>IP/mask or misconfiguration of default router), or one of
>misconfiguration of DNS.
>
> > 4. I wasn't asked if I wanted to sync my clock with an outside source.
>Is
> > this because I didn't activate named? How can I activeate named now?
> > (stand/sysinstall?)
>
>This has nothing to do with named. We simply do not do that by default.
>If you want to sync your clock with an outside source, read the ntp man
>page.
>
> > 5. By CVSup-ing, I can keep my sources up-to-date, but how do I know
>thta is
> > safe to make and install a new kernel? (I have been wondering this
>about
> > those who track -CURRENT)
>
>WRT stable, you may _assume_ it is safe. Sometimes, it isn't, and that's
>our fault. Mostly, it is.
>
>If you plan to follow -current, you need to read -current and cvs-all
>mailing lists, and also pay attention to /usr/src/UPDATING. And, then,
>you simply don't know it's safe, because it hasn't been tested except in
>limited enviroments. It's -current users that make the larger testing
>environment.
>
> > I know that it is always a good idea to keep a previously workign kernel
> > around, but how do you tell the system, on boot, to use the old one?
>
>When the system starts the 10 seconds count down before booting,
>interrupt it and then enter the following commands:
>
>unload
>boot <KERNEL>.old
>
>where <KERNEL> is the name of your kernel, of course.
>
>--
>Daniel C. Sobral (8-DCS)
>dcs@newsguy.com
>dcs@freebsd.org
>
> One Unix to rule them all, One Resolver to find them,
> One IP to bring them all and in the zone bind them.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000318003429.28434.qmail>