Date: Wed, 4 Feb 1998 17:31:39 -0500 (EST) From: Uncle Flatline <flatline@pchb1f.gallaudet.edu> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 7 questions/problems from a former Linux, new FreeBSD user Message-ID: <Pine.BSF.3.96.980204171640.2255B-100000@pchb1f.gallaudet.edu> In-Reply-To: <Pine.BSF.3.96.980204132958.15689X-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, you're a saint. And now round two: On Wed, 4 Feb 1998, Doug White wrote: > > 3) When connecting via a multiplexer (DECserver/Vista) over a phone line > > the username is accepted, but the password seems to ignore the carriage > > return. The system waits forever for the password to be entered. (It > > seems that typing <LF> (^J) directly gets around this problem. But that's > > ugly!) > > This is a known bug and we've been trying to squash it for ages. Can you > set up your Vista to not expect DOS-style carriage returns? No access to the Vista, and an uncooperative Computer Services... > > 4) When telnetting to my Linux host, the system correctly translates > > IP name to IP numeric address, tells me it's connected, and then > > immediately says "Connection closed by foreign host". Telnetting > > from FreeBSD to other machines is fine, as is telnetting to the Linux > > machine from anything other than the FreeBSD machine. (Is this some > > authentication thing that I turned on during the install? Can I correct > > things without reinstalling?) > > Sounds like tcp wrappers are on on the Linux box and your FreeBSD machine > is blocked out. Also try disabling tcp_extensions in /etc/rc.conf. I dunno anything about tcp wrappers, but I just tried "rlogin" and that works... So, while trying to figure out what I should change, I do have a way to get into my other machine from here. > You can't have both. If you run pcvt, you loose some graphics > functionality on the console. If you don't plan on doing anything > spiffy-keen on the console then don't worry about it. You can teach Linux > about cons25, though, check the mail archives. So cons25's a bit better, then? Yes? (I imagine teaching Linux would consist of copying the termcap entry from one to the other. But just in case it's not that simple, I'll hunt thru the archives as you suggest.) > > 6) Recompilation of kernel lost the JAZ drive (and never got me the audio > > (SB) support.) How important is the order of the lines in the kernel > > config file? I tried to arrange mine in what I thought was a logical > > order: > > Order is somewhat significant. Particularly the network devices. What > type of Jaz is it? SCSI? SCSI. Didn't know there was another kind of JAZ. (ZIP I knew came in three flavors.) > > Recompiling with the order that LINT uses got the JAZ drive back, but > > I'm still stuck with no sound. P'n'P problem??? I don't want to turn it > > off if I can avoid it. > > If it's a new SB16 you need PnP support. Install 2.26 when it's releasd > and you'll be happy. I read about a patch. Where do I look for it? > > 7) STUPID IDEA: Why does chsh do so much more than it should and badly? > > It should just change the shell, not bring up an editor. I decided to > > change the sell of my root account. It not only displayed the shell, > > but a password line. I hadn't set my password yet at that point, so > > I attempted to set it from the chsh command. It proceeded to store > > the UNENCRYPTED password in master.passwd (and god knows where else). > > chsh was targeted at changing the user-modifiable parameters in the > password file. That seems fine, but shouldn't it know that one of those parameters is not plain-text (even if it only shows that parameter to root)? If it doesn't, can't it at least avoid that parameter alltogether? I mean, is there a GOOD reason for root to be able to edit the password parameter from chfn as it stands now? > We could use a shell-picker tool; let us know if you write anything neat. Unlikely, as I lack the skills necessary. But as I get more savvy, I'll try. > BTW chsh as root lets you modify everything (a la chpass or vipw). > > You figured out to NOT modify passwd firectly and use vipw, right? > Linux users usually miss that the first few times :) I've never needed to modify passwd directly, though in a pinch I've gone in and changed a uid or gid. Do I have to suffer with a vi-like editor? Thanks again. -- Kevin Cole <Flatline> | E-mail: flatline@pchb1f.gallaudet.edu Gallaudet Research Institute | WWW: http://pchb1f.gallaudet.edu/ Hall Memorial Bldg S-419 | Voice: (202) 651-5135 Washington, D.C. 20002-3695 | FAX: (202) 651-5746
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980204171640.2255B-100000>