From: Digestifier To: Linux-Admin@senator-bedfellow.mit.edu Reply-To: Linux-Admin@senator-bedfellow.mit.edu Date: Thu, 2 Sep 93 18:13:28 EDT Subject: Linux-Admin Digest #33 Linux-Admin Digest #33, Volume #1 Thu, 2 Sep 93 18:13:28 EDT Contents: Re: SLS 1.03 networking (Doug Beattie) Re: [Q]: eliminating hostname before 'login:' with MCC (Pat Mackinlay) Re: Let's collect KNOWN BUGS (Kai Voigt) Re: Let's collect KNOWN BUGS (Kai Voigt) REMINDER: LINUX HARDWARE POLL WILL END SATURDAY (Matthew Dillon) Re: [Q]: eliminating hostname before 'login:' with MCC (Jon Hamilton) Re: Another printing problem (Was Re: "lpd" won't run) (Zack Evans) Re: [Q]: eliminating hostname before 'login:' with MCC (Quowong P. Liu) ---------------------------------------------------------------------------- From: dbb@unislc.slc.unisys.com (Doug Beattie) Subject: Re: SLS 1.03 networking Reply-To: dbb@unislc.UUCP (Doug Beattie,D1V03,6814,CC 5230) Date: Thu, 2 Sep 1993 12:48:49 GMT In article wayne@rose.cs.odu.edu (C Wayne Huling) writes: > I have upgraded from SLS 1.01 to SLS 1.03 because it seemed to make >a lot of changes that I was making manually. Anyhow, the net-2 >software doesn't seem to communicate with the rest of the network at >any level? Does anyone have any suggestions as to why the network is >unreachable from the newly upgraded machine, but the other machines on >the network that are still SLS 1.01 can ping the upgraded machine? No >other network communication works (telnet, ftp, rsh, rlogin). > > > > Wayne Just for fun try adding an entry for one of the remote hosts into the hosts file on your upgraded system. Then attempt to telnet to it from the host that you added into its hosts file. The message you are probably getting now if you look into the log file is that you have a name/name mismatch between what the host sees sent to it and the looked up full domain name that a dns server may be supplying. This excersise should help to determine that. -- Doug Beattie - Computer Development Services Inc. dbb@unislc.slc.unisys.com c/o Unisys Corporation 322 No. 2200 West M.S. D1V03 Subcontractor 88K MP NFS Group - SLC, UT SLC, UT 84116 (801) 594-6814 Disclaimer - I represent myself and no one else ------------------------------ From: mackinla@cs.curtin.edu.au (Pat Mackinlay) Subject: Re: [Q]: eliminating hostname before 'login:' with MCC Date: 2 Sep 93 14:24:34 GMT roland@cac.washington.edu (Liem Bahneman) writes: >How do I eliminate the 'hostname login:' and restore to just 'login:' on >incoming telnet connections? MCC's getty doesn't have an /etc/gettydefs or >/etc/gettytab file, so I'm wondering where do I change this and how? After a brief look at the source to the MCC distribution's getty (agetty), I can say that you can't get rid of the hostname without recompiling the source. Fair enough? -- Pat -- "There's only one thing left to do Mama, I got to ding a ding dang my dang a long ling long" (Jesus Built My Hotrod -- Ministry) GCS d* -p+ c++ l++ m--- s+/- !g w- t- r ------------------------------ From: kai@depeche.toppoint.de (Kai Voigt) Subject: Re: Let's collect KNOWN BUGS Date: Wed, 1 Sep 1993 22:22:11 GMT drew@juliet.cs.colorado.edu (Drew Eckhardt) writes: >In article <1993Aug29.105820.750@depeche.toppoint.de> kai@depeche.toppoint.de (Kai Voigt) writes: >> >>on a networking congress here in Kiel some German Linuxers >>decided to create a Linux workshop. One of our ideas was >>to collect a list called "KNOWN BUGS". This list should be >>mainly an index to bugs in the SLS distribution, i.e its single >>packages. The SLS is great, no question, but there are some >>security lacks, some programs don't work etc. >1. It's my experience that many "bugs" aren't bugs and stem from > users not understanding the correct behavior and what they > need to do to get it (ie, boards jumpered right, etc). You > need to screen bugs for false reports. true. >2. SLS is not Linux. As a collection of the linux kernel and various > linux programs, it often lags begined the current state-of-the-art, > and many bugs will be fixed in newer versions of things that aren't > yet integrated with SLS. So, some of the bug reports here are going > to be useless. Well, what we actually want is to have an 'professional' Unix distrubution. SLS looks very messy in some places and lots of permissions aren't correct. If you want to use Linux in a company or something like this you will need to clean up the directory trees, e.g putting all README's into one seperate directory, putting detailed comments into config files. At the end of all this I'd like to see a Linux that you install easily and that you can put the system to the net without risking any security problems. >4. I often get "bug reports" from users who fail to specify their > configuration, what version they're using, and other important > details. In cases like this, it is impossible to track down the > bug. [..] This bug report form sounds good, it will really help a lot. We will work something out and present it on here then. >5. Finally, many Linux bugs aren't Linux bugs, but GCC bugs, Xfree bugs, > bugs in things that run under Linux but aren't necessarily Linux. Many > of these packages have their own bug alias that should be mailed, as is > the case with X, GCC, etc. Correct, and we don't want to deal too much with these problems, only with the structure of the SLS and the Linux specific things. >A clearing house for bug reports would be extremely useful for the developers >and users. It could weed out non-bugs, and insure that all bug reports had >enough information to reproduce the bugs. It could then mail the bugs out to >the appropriate people, and could maintain a public list as well. Developers >would have concise bug reports with a high-signal-to-noise ratio, making >problems easier to fix. Users would have a better chance of getting their >bugs fixed, and would know about what bugs to expect. I really hope that our German wide group will be able to support this and that it won't die like so many other pub ideas after some beers :-) We have founded a mailing list where we talk about what to improve in the sls. If there are people outside Germany interested in joining it, we might think about internationalizing it... Cheers, Kai -- Kai Voigt, Werftstrasse 2, 24148 Kiel, Germany, +49 431 7297514 no .signature is good .signature ------------------------------ From: kai@depeche.toppoint.de (Kai Voigt) Subject: Re: Let's collect KNOWN BUGS Date: Wed, 1 Sep 1993 22:24:31 GMT macy@telemax.com (Macy Hallock) writes: >In article <1993Aug29.233539.6106@colorado.edu> drew@juliet.cs.colorado.edu (Drew Eckhardt) writes: >>A clearing house for bug reports would be extremely useful for the developers >>and users. >A moderated newsgroup would be useful for this purpose. The only >drawback I can think of is: the knowledgable person who moderates >would have less time to track down and fix the bugs. On the other >hand, independant confirmation and documentation of a bug is a >very useful contribution... >Other ideas? I don't think that a newsgroup would be necessary. We collect the bugs and post them frequently in a single list to c.o.l.announce, who wants to contribute bugs or anything that might be improved in the SLS, should send a report about it to me. Kai -- Kai Voigt, Werftstrasse 2, 24148 Kiel, Germany, +49 431 7297514 no .signature is good .signature ------------------------------ From: dillon@moonshot.west.oic.com (Matthew Dillon) Crossposted-To: comp.os.linux.misc,comp.os.linux.development Subject: REMINDER: LINUX HARDWARE POLL WILL END SATURDAY Date: 2 Sep 1993 10:38:30 -0700 The linux hardware poll will end on Saturday Sep 4. I've been getting a wonderful response... 129 returns so far. For those of you who missed the poll, I am reposting it. This is the same poll I posted before, so if you have already answered it you don't need to do so again! -Matt Matthew Dillon dillon@moonshot.west.oic.com 1005 Apollo Way dillon@overload.berkeley.ca.us Incline Village, NV. 89451 ham: KC6LVW (no mail drop) USA Sandel-Avery Engineering (702)831-8000 [always include a portion of the original email in any response!] POLL ON LINUX HARDWARE CONFIGURATIONS, I/O BOARDS, AND PERCEPTIONS A. This is a poll on linux hardware configurations, I/O boards, and your perceptions as to the reliability of same. If you are a Linux user with knowledge of the hardware configuration of your machine then this poll is for you! B. If you have time, please answer the below questions and send the results to: poll@moonshot.west.oic.com POLL ENDS ON SATURDAY SEPTEMBER 4 1993 12:00 HOURS AT WHICH TIME I WILL POST THE RESULTS TO COMP.OS.LINUX.MISC. COMPLETE RESULTS WILL BE AVAILABLE VIA FTP. ALL RESPONSES WILL BE KEPT PRIVATE (EMAIL HEADERS WILL ALL BE REMOVED) If you do not have the answer to all the questions, please fill in those answers that you do have! This poll is being conducted by Matthew Dillon, dillon@moonshot.west.oic.com . Please email poll answers to poll@moonshot.west.com 0. How would you categorize yourself? Mark appropriate boxes. This will help me organize the answers and my comments to them. 0A. [ ] Joe end user with little technical knowledge and little application knowledge (i.e. only used a few commercial applications in your lifetime). Hint: if you check this box maybe you shouldn't be filling out this survey! 0B. [ ] Joe end user with some application knowledge but no technical (i.e. hardware knowledge) 0C. [ ] end user with a reasonable amount of ability installing boards and using applications but not much on programming languages (shell, interpreted, or compiled). 0D. [ ] power user who knows his way around PC boxes and maybe knows something about programming, but not so much about UNIX. 0E. [ ] power user who has no problem with hardware and can even write shell scripts and modify text files in /etc without too much havoc. 0F. [ ] expert UNIX user 0G. [ ] expert UNIX user, reasonable operating systems / machine management skills. 0H. [ ] power expert UNIX user - highly skilled in most things. 0I. [ ] UNIX guru - highly skilled in all things, experience modifying kernel code, writing device drivers... can pick up random source code you've never seen before and hack on it, etc... Can become an expert on a program after ten minutes of fiddling with it. 0J. [ ] UNIX god - 0I + over 1000 hours of kernel hacking, includes network protocol hacking but not system level hacking. Also must have posted at least one clandestine message to the internet (mail or news) in his/her lifetime and be able to become root on any machine he/she has an account on (in order to fix problems, of course!). Also must have crashed the kernel while hacking at least two dozen times (or you aren't on the leading edge :-)). 1. What type of machine do you have? 1A. Brand (e.g. Dell) -> 1B. Cpu (e.g. 486DX2/66) -> 1C. Math co-processor? (Y/N) -> 1D. Base memory (before any additions) -> 1E. Approximate price -> 1F. EISA or ISA computer? (if not an intel 486) -> 1G. Is this a localbus computer? -> 1H. Is this a portable computer? -> 1I. Please comment on any hardware problems you had installing and using Linux on this platform (i.e. dip switches you had to fool with, etc..) -> -> -> -> 1J. If available, please give an approximate price for this platform NOT including any additional boards you might have purchased for it. PLEASE INDICATE WHAT I/O BOARDS, IF ANY, CAME WITH THE PLATFORM. I am specifically interested in hard disk, video, and ethernet boards. -> -> -> -> 2. What brand of physical hard drive do you have? (the bare drive, not the controller. Do not answer this question if you have a hard-card): 2A. Brand (e.g. Quantum, Fujitsu..) -> 2B. Approximate price of bare drive -> 2C. Please comment on any hardware specific problems you might have had and the reliability of the drive itself. -> -> -> -> 3. What type and brand of hard drive controller do you have? Note that ISA cards can be stuck into EISA busses (reason for question #3B). THIS QUESTION APPLIES ONLY TO CARDS, NOT TO MOTHERBOARD-BASED CONTROLLERS. 3A. Type (e.g. SCSI, IDE, STANDARD) -> 3B. Approximate price -> 3C. Bus Interface (e.g. EISA, ISA) -> 3D. Brand -> 3E. Please comment on any hardware specific problems you might have had and the reliability of the card itself (if you can discern between drive reliability and card reliability :-)) -> -> -> -> 4. What are your perceptions as to the speed of your disk controller? The two categories will help separate out power user from joe user perceptions. You can answer this question even if you have a motherboard-based controller. 4A. If you are NOT using the disk heavily -> -> -> -> 4B. If you ARE using the disk heavily -> -> -> -> 5. Questions related to your video hardware. Answer only if you are running X-Windows (or other graphical environment). These are questions related to your video controller. 5A. on-Card or on-motherboard? -> 5B. Approx. price, include expansion-> 5C. What brand are you using? -> 5D. Bus interface(EISA,LOCAL,ISA..) -> 5E. Screen resolution you use -> 5F. Screen depth / colors -> 5G. How do you perceive the speed of this video controller. If you have made any comparisons with other controllers please indicate relative impressions of BOTH controllers, and list the second controller. -> -> -> -> 5H. Please comment on any installation problems you might have had installing the board. This includes dip switches, kernel patches you may have had to made, and Xconfig problems beyond the normal dumb stuff. Please differentiate between problems installing the board so the system would boot using it and problems installing the board to make it run under X-Windows (or other graphical environment). -> -> -> -> 6. Questions related to your physical screen, only if you have a multi-sync and run it in a high resolution graphics mode (i.e. under X-Windows or other graphical environment under Linux). 6A. What brand of monitor? -> 6B. Approximate price -> 6C. Size, in inches (or approx) -> 6D. Please comment on any problems you may have had interfacing the monitor to your video board, leave blank if you did not have any problems (most people will not have had any problems!) -> -> -> -> 6E. Please comment on special attributes of the monitor you like or dislike (e.g. has a nice stand, display exceptionally dull, etc...) -> -> -> -> 7. Questions related to your ethernet adapter, if you use one. 7A. What brand of adaptor? -> 7B. Approximate price -> 7C. Bus interface (EISA, ISA, ...) -> 7D. Please comment on any installation problems you might have had installing the board, including having to change default IRQ, Kernel reconfigurations, etc. If you had any difficulties getting packets to start running across it beyond the normal dumb stuff, please comment on them. Do not comment on difficulties getting ifconfig or routing setup unless they are hardware-related. -> -> -> -> 7E. Ethernet boards all run at about the same speed, but if you have done any comparisons and found any significant differences, please comment on them below! DMA *can* make a small difference though at 10 MBits/sec even ISA DMA doesn't have much of a problem. -> -> -> -> ------------------------------ From: jdh@iastate.edu (Jon Hamilton) Subject: Re: [Q]: eliminating hostname before 'login:' with MCC Date: Thu, 2 Sep 1993 19:31:26 GMT In article mackinla@cs.curtin.edu.au (Pat Mackinlay) writes: [...] >After a brief look at the source to the MCC distribution's getty (agetty), >I can say that you can't get rid of the hostname without recompiling the >source. Fair enough? This is not the case under SLS (I'm not disputing your claim, just offering a data point). In /etc/gettydefs, each line corresponds to a speed. In the field before you see login:, you'll find @S stuck in there. Remove the @S and you'll get login: instead of login:. I know this isn't terribly descriptive, but you know the story about me being here and it being there... > >-- >Pat -- "There's only one thing left to do Mama, I got to ding a ding dang > my dang a long ling long" (Jesus Built My Hotrod -- Ministry) >GCS d* -p+ c++ l++ m--- s+/- !g w- t- r -- ==================================================================== = Jon Hamilton | "Please saw off my legs. = = jdh@iastate.edu | -- George Carlin = ==================================================================== ------------------------------ From: zevans@nyx.cs.du.edu (Zack Evans) Subject: Re: Another printing problem (Was Re: "lpd" won't run) Date: Thu, 2 Sep 93 21:31:23 GMT In article , Erik Stenvall wrote: >to get my lpd working. When I recompiled the kernel without TCP I >found that lpd now worked quite OK. The sad thing is that a kernel >without TCP is not OK since X wont run. I'm no socket-guru so I >haven't looked deeper into it though. Before hundreds if not thousands of people panic at the prospect of having to recompile their kernels and make them 100k bigger just to install X, I think someone had better point out that this is wrong :) X runs fine using unix sockets instead of TCP - you do not need networking support to run X. Zack -- Zack Evans pyc081@cent1.lancs.ac.uk or zevans@nyx.cs.du.edu UNIX was not designed to stop its users from doing stupid things, as that would also stop them from doing clever things. ------------------------------ From: qpliu@ernie.Princeton.EDU (Quowong P. Liu) Subject: Re: [Q]: eliminating hostname before 'login:' with MCC Reply-To: qpliu@princeton.edu Date: Thu, 2 Sep 1993 20:10:36 GMT In article mackinla@cs.curtin.edu.au (Pat Mackinlay) writes: >roland@cac.washington.edu (Liem Bahneman) writes: >>How do I eliminate the 'hostname login:' and restore to just 'login:' on >>incoming telnet connections? >After a brief look at the source to the MCC distribution's getty (agetty), >I can say that you can't get rid of the hostname without recompiling the >source. Fair enough? Enough misinfomation on this triviality. telnetd doesn't touch getty. You need to recompile login, which has been printing the hostname since the 0.12 days. -- qpliu@princeton.edu Standard opinion: Opinions are delta-correlated. ------------------------------ ** FOR YOUR REFERENCE ** The service address, to which questions about the list itself and requests to be added to or deleted from it should be directed, is: Internet: Linux-Admin-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.admin) via: Internet: Linux-Admin@NEWS-DIGESTS.MIT.EDU Linux may be obtained via one of these FTP sites: nic.funet.fi pub/OS/Linux tsx-11.mit.edu pub/linux sunsite.unc.edu pub/Linux End of Linux-Admin Digest ******************************