| gabriel rosenkoetter on Fri, 25 Jan 2002 03:16:47 -0500 |
|
On Fri, Jan 25, 2002 at 12:47:15AM -0500, Samantha Samuel wrote: > As for NetBSD probs I have many. Main ones include the fact that bash is > not the default shell, See vipw(8) and chsh(1) as well as the contents of /etc/shells. The only shells installed by default are sh, csh, and ksh. You might be most content with ksh. bash, tcsh, zsh (my own favorite), scsh, and a variety of others are available as packages. > the fact that I have to work with vi, Emacs, as you noted, is readily available as a package and setting the shell variable EDITOR to emacs will make programs like vipw (as well as crontab -e, many MUAs, so forth) use it instead of the default vi. (Note that, unless you specifically set your user to another shell, you'll need to do this in C shell syntax, "setenv EDITOR emacs".) (Be glad you didn't have to edit any text files while booted off the floppy; the only editor available there is ed(1). :^>) NetBSD contains the same basic things in the distribution that 4.4BSD (and previous versions) did. *This* is Unix. Anything else is an add-on. (Granted, vi, for instance, has been replaced with nvi, as the original vi source is under an unacceptable license, but the system still mirrors the basic functionality of a Berkeley Unix distribution.) > and even though I configured networking in the installation, after > rebooting, networking worked no more. I'd need to know more about the details of the system to know what's wrong, but it sounds like you got bit by the vagaries of the Tulip chipset. I'm presuming of course that you did tell sysinst to preserve your network setup after installation. First off, do an ls -l /etc/ifconfig.* and show me the results. An ifconfig -a would be helpful as well. Then, do egrep -A5 '^de|^tlp' /var/run/dmesg.boot and post the results of that too. (The -A is so that we catch the phy match lines too, since I've no clue what kind of phy your Tulip card may be using.) (Actually, it wouldn't hurt for me to be able to see your full dmesg output--stored, after boot, at /var/run/dmesg.boot--but it might be better to send that to me privately than to send it to the list, and might be easier to get off the machine once the network problem is sorted out.) Based on this, you're probably going to want to build a new kernel with one of the options TLP_MATCH_21x4y lines uncommented. (The tlp driver is slowly replacing the de driver for DEC/Tulip chips. tlp already supports a wider variety of cards, but there are some mutually exclusive quirks in a variety of Tulip-based cards for which a graceful workaround hasn't been written into the driver yet, so these matches force the driver to behave in a specific way. Yes, I'm aware this is an ugly hack, but it's not an easy problem to solve right.) If that's the case, I can explain some more details, but you might take a look at http://www.netbsd.org/Documentation/kernel/. (Make sure that you use the same branch of the source tree for the kernel source as the system you have booted. If that's a -current snapshot, then just do a cvs checkout--you'll need to get cvs as a pkg too, btw--if it's some version of 1.5.N where N is 2 or 3 with some stuff trailing after it, you want to do cvs checkout -r netbsd-1-5 syssrc.) > When I tried to get packages up through: > pkg_add -v /cdrom/packages/All/emacs-20.7.tgz I had a host of > "no permission" errors scrolling up. To what did you have no permission? When referencing errors like this, it's far easier to diagnose what's wrong if you reproduce the exact error message. At a guess, I'd say you were not allowed to write to /usr/pkg and /var/db/pkg. You must be able to in order to install packages, which implies being root on a default install. (So, try su'ing first.) -- gabriel rosenkoetter gr@eclipsed.net Attachment:
pgpsXJ0UtfbIw.pgp
|
|