Date: Sun, 8 Jan 2012 16:59:52 +0000 From: Frank Shute <frank@shute.org.uk> To: Polytropon <freebsd@edvax.de> Cc: leeoliveshackelford@surewest.net, freebsd-questions@freebsd.org Subject: Re: Installing FreeBSD ver. 8.2 Message-ID: <20120108165952.GC1715@orange.esperance-linux.co.uk> In-Reply-To: <20120108003225.dc64798a.freebsd@edvax.de> References: <20120107150555.BYL92929@ms5.mc.surewest.net> <20120108003225.dc64798a.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--jousvV0MzM2p6OtC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 08, 2012 at 12:32:25AM +0100, Polytropon wrote: > > On Sat, 7 Jan 2012 15:05:55 -0800 (PST), leeoliveshackelford@surewest.ne= t wrote: > > (1) Does anyone know how to get FreeBSD to read the > > motherboard name? This name, on an xw4400, starts with > > "HP" followed by a eleven digits, and is given in Windows > > XP as "Full Computer Name" on the "Computer Name" tab > > of the "System Properties" window. Among other purposes, > > this name is used by Novell network operating system to > > distinguish hosts on a subnet. >=20 > The OS provides the output of dmesg and maybe the > output of pciconf -lv, as well as the sysctl value > dev.acpi.0.%desc which may contain the required > information. However, I'm sure there is a program > in the ports collection that can be used to obtain > that kind of information. >=20 > Try: >=20 > dmesg | grep "HP" > sysctl -a | grep "HP" > pciconf -lv | less >=20 > and see if there's such a number mentioned. Maybe > you can also use acpidump to retrieve that information > from the ACPI datasets. >=20 >=20 >=20 > > (2) I cannot get the "find" command to locate files > > that I believe were installed at the time of sysinstall.=20 > > If I understand the Handbook correctly, when one runs > > "find" from the "/" directory, it is supposed to inspect > > all directories and subdirectories of all partitions, > > which it is not doing. What concept am I missing here? >=20 > It would be easier to answer if you could provide > the find command line you've been running. :-) >=20 > See "man find" for more information. Basically, > "find / -name <namespec> -type f" should be sufficient > to access all partitions currently mounted to search > for <namespec> specified regular files. >=20 >=20 >=20 > > (3) I thought that I would obtain a better understanding > > of the file system by running "man heir." This command > > runs fine under "sh." When I switch to my preferred shell, > > which is "bash," I type, and receive echo on the screen, > > "man hei." As soon as I depress "r," the entire previously > > entered command echos to the screen, starting where the > > "r" should have appeared. In checking the bash manual, it > > says that this response is correct for "control-r." I > > could not find "non-shift-r" to be called out as a command.=20 > > Am I doing something wrong? Is this a hardware bug? Is > > this a software bug? Is there something that needs to be > > defined or undefined in a configuration file? =20 >=20 > No, bash's configuration files provided after install > should be fine. >=20 > However, I think you have a typo. The command you're > intending to run is "man hier" ("hierarchy"). I've > tested both csh and bash here, both allow the command > to be entered without any interruption. When I type > "man hei" followed by Ctrl+R, I get the following > output: "(reverse-i-search)`': man hei". >=20 >=20 >=20 > > (4) Not having very good luck with the "find" command, > > I thought I would try to use the "locate" command.=20 > > To use this command, one must create a database.=20 > > On www.us-webmasters.com, I read that this database > > could be constructed by running the command > > "#usr/libexec/locate.updatedb."=20 >=20 > The required task is usually executed by the system's > "night job" at 3:00 once a week. The script that will > be run is /etc/periodic/weekly/310.locate which you > could run manually. It will deal with the correct > call of /usr/libexec/locate.updatedb (instead of > running it as root!). The thing to run is periodic(8): # periodic weekly That will also update other useful stuff. Regards, --=20 Frank Contact info: http://www.shute.org.uk/misc/contact.html --jousvV0MzM2p6OtC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk8Jy4cACgkQHduKvUAgeK6F/QCffTG/3/IoDwox5cQ6+M8znDJJ KdAAoJ/HrroM4YJxi+UUQ5DpP1REnY/S =yAAD -----END PGP SIGNATURE----- --jousvV0MzM2p6OtC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120108165952.GC1715>