From: Digestifier To: Linux-Admin@senator-bedfellow.mit.edu Reply-To: Linux-Admin@senator-bedfellow.mit.edu Date: Sat, 2 Oct 93 19:13:27 EDT Subject: Linux-Admin Digest #88 Linux-Admin Digest #88, Volume #1 Sat, 2 Oct 93 19:13:27 EDT Contents: NIS or workaround (proposal) (Jan Wielemaker) Re: net-2 rlogin failed (Dieter Armbruster) [Q] lpd, Ghostview and umount (LMRusu) Welcome to the comp.os.linux.* hierarchy! (Matt Welsh) Re: NIS or workaround (proposal) (Michael Griffith) Re: crontab entry for sendmail? (Bill Heiser) [solved] mitsumi with kernel 0.99.13 (Maurizio Codogno) ---------------------------------------------------------------------------- From: jan@swi.psy.uva.nl (Jan Wielemaker) Subject: NIS or workaround (proposal) Date: Sat, 2 Oct 1993 14:04:52 GMT Hi, Trying to get Linux systems set up for our students, one needs NIS to share at least the passwd stuff (most of the other info is bearable). I (think I) know NIS is not around and probably wont be on the very short term (actually I wonder why nobody came around in implementing such a useful tool). I was thinking of the following work-around: * Export a directory (say /export/nis) from the main network holding a copy of passwd and group (and maybe other info). This directory is exported read-only from the (SunOs) server. * Create a directory /nis on the linux machine and put passwd and group files with entries needed for maintenance (e.g. root and friends). * mount server:/export/nis read-only over /nis on the linux box. This will allow anyone to login. No shadow passwd unfortunately. We could arrange that too if someone could explain how to generate passwd and shadow from a traditional passwd file. (What do the numbers mean??) This will allow us to share the passwd info. Cron on the server will update the central copy for the linux network every 1/2 hour or so. Now the tricky bit is to change the passwd. For the majority of users we whould not want to provide rlogin permission to the main network, so one would need yppasswd. Are ther public sources of yppasswd that compile (with minor fixes) on Linux? Other hints are welcome too. Thanks for any comments. Experience of people in this area are welcome! --- Jan ------------------------------ From: armbr@azu.informatik.uni-stuttgart.de (Dieter Armbruster) Subject: Re: net-2 rlogin failed Date: Sat, 2 Oct 1993 16:38:39 GMT In article <285hlm$r8t@news.csie.nctu.edu.tw> ghhwang@pllab1 () writes: >Dear friends, > I have installed SLS 1.03. There is net-2 binary code. However, when i use >the command "rlogin" the following message appeared: > > > rlogin sun370 > rcmd: socket: Permission denied > > Anyon can help me? > >ghhwang@cs.nthu.edu.tw > Hi, The solution seems to be quite simple: rlogin (and all the other r*-commands) need to be set-uid to root, i.e., chown root rlogin; chmod 4755 rlogin. Hope that helps. D.Armbruster Phone: ++49 712142346 ------------------------------ From: rusu@eniac.seas.upenn.edu (LMRusu) Subject: [Q] lpd, Ghostview and umount Date: 2 Oct 93 16:20:02 GMT Hi Netters, I checked the FAQs, Digests and HOWTOs throroughly and I couldn't find a solution to these problems I'm having. 1. I can't get the lpd to stay in the memory. I've put /etc/lpd in the rc file. When I want to print a file with lpr "filename" it gives me back a message saying that the file is being queued but that no daemon is running. The file gets in the queue but it doesn't print out until I call lpd. After that the story starts again: lpr "filename" just puts the filename in the queue and I have to type lpd to get it printed. I checked all the help on this in the Printing-HOWTO and the archives for this newsgroups and tried all the things suggested (like creating a dir /usr/spool/lpd and files .seq, lock, status, changing the mode and ownerships of lpr,lpq,lpd, etc) but nothing works. A related problem (I think) is that Ghostview doesn't want to print any postscript files (when I choose to print a file and then I do a ps x to see if Ghostview called gs I see: gs -sDEVICE=x11 -dNOPAUSE -dSAFE but I don't see a file name like I do when I gsprint). I'm using gsprint "filename" right now to print psfiles. Any advice on these 2 things because I've tried everything I could think or saw on the net? 2. When I use the shutdown command by second drive doesn't want to umount (It says sda2 cannot umount). My second drive is running off a Adaptec 1522 and I mounted it under the /home directory. I'd really like to umount it before I shut down because I don't want to end up with the hole thing in the lost+found. Any advice? I would really appreciate any advice on these problems and I will post a summary on the net if I get any responses. After reading the archives of these newsgroup it seems to me that quite a few other people had these problems. BTW, Linux/XWindows are the greatest. I'm a newbie at this (3 1/2 weeks) and I only used MSWindows a couple of times since then. How can you use MSWindows after using Linux/XWindows? :) Regards, Larry -- ------------------------------ From: mdw@sunsite.unc.edu (Matt Welsh) Crossposted-To: comp.os.linux.announce,comp.os.linux.help,comp.os.linux.development,comp.os.linux.misc,comp.os.linux,news.answers,comp.answers Subject: Welcome to the comp.os.linux.* hierarchy! Date: 2 Oct 1993 17:02:44 GMT Archive-name: linux/announce/intro Last-modified: 8 August 93 Welcome to the comp.os.linux.* hierarchy! Background ========================================================================= This posting is an introduction to the comp.os.linux.* hierarchy of USENET newsgroups. Linux is a free implementation of UNIX for 80386/80486 machines covered by the GNU GPL. Most of the development of the Linux kernel has been done by Linus Torvalds, an internationally reknowned UNIX wizard from Helsinki, Finland. For the past two years or so, the newsgroup comp.os.linux has grown be one of the most popular groups on USENET. Late in 1992, a CFV for splitting comp.os.linux was posted; the only group which passed was comp.os.linux.announce, a moderated newsgroup for Linux announcements and patches. Six months later, during the summer of 1993, another CFV for splitting comp.os.linux was posted. The voting period for the comp.os.linux reorganization results ended at 23:59:59 UTC on 4 August 1993 (4:59PM US Pacific Time, 7:59PM US Eastern Time.) The results are as follows: comp.os.linux reorganization results - 1842 votes Yes No : 2/3? >100? : Pass? : Group ---- ---- : ---- ----- : ----- : ------------------------------- 1692 135 : Yes Yes : Yes : comp.os.linux.admin 1741 90 : Yes Yes : Yes : comp.os.linux.development 1647 177 : Yes Yes : Yes : comp.os.linux.help 1660 155 : Yes Yes : Yes : comp.os.linux.misc Because of this split, the newsgroup comp.os.linux will be deleted on 11 November 1993. The new newsgroups will be created on 11 August 1993. This posting describes these newsgroups, including comp.os.linux.announce, which will remain entact. General Policy ========================================================================= The general policy for the Linux newsgroups is simple. Who sets the policy? We all do. All of us on USENET are interested in communicating openly about a number of topics. That's why we have USENET. If you want the Linux newsgroups to work for you, a few suggestions: * Read the Linux FAQ and follow the newsgroups for some time before posting questions. This is very important. comp.os.linux suffered from HUGE amounts of noise and traffic because much of the growing readership never bothered to READ the newsgroup; they only posted questions. The same thing will happen with the new newsgroups unless you read the FAQ (found on sunsite.unc.edu in the file pub/Linux/docs/FAQ) and read the newsgroup for some time before posting questions. Chances are, your question has already been recently answered, and a simple browsing of the newsgroup will answer it. We suggest using a threaded newsreader such as "trn" which will allow you to browse and mark articles by subject, so you don't have to read each and every article in each newsgroup. * Crossposting between the Linux newsgroups is STRONGLY discouraged. If you do crosspost questions between Linux newsgroups, expect to be flamed to oblivion. The reason we have a newsgroup split is to categorize discussions into separate newsgroups. Crossposting negates this effect. If your posting cannot fit into ONE of the newsgroups c.o.l.admin, c.o.l.help, or c.o.l.development, then you should post it to c.o.l.misc. The one exception is for announcements. Occasionally, an important announcement (such as this one) will be crossposted between c.o.l.announce and one or more of the other c.o.l.* groups. These announcements must be approved by the .announce moderator; see below. * Reply to questions via e-mail if at all possible. While discussion in the newsgroups is encouraged, if someone is asking a simple question to which the answer is well-known, there is no reason to post the reply. Don't assume that the person posting the question actually reads the newsgroup or will even note your followup if they do. Reply via e-mail unless the reply is of general interest. * Don't flame newbies. Over the course of the past few months, the Linux community has developed an oversensitive ego and a reputation for being unfriendly towards newcomers, mostly because of unwarranted flaming by a handful of righteous individuals. If someone posts, saying, "Hi! I'm new to this group! What is Linux?" (which will inevitably happen as the new newsgroups are propagated), DO NOT FLAME THEM. When someone sees a new newsgroup pop up within "rn", they are justifiably curious about the new group and probably don't know that well over 80,000 people who know EVERYTHING about Linux read the group. Right? Instead of being rude, you can send a polite note to the poster, saying, "Hello, Linux is a free implementation of UNIX for the 386 and 486. You can get the FAQ from sunsite.unc.edu in /pub/Linux/docs. Let me know if I can be of help!". That's all. Not difficult, eh? You can even save your stock reply in a file and simply send form-letters to newbies if you wish. But there is very little point in flaming or ever being rude. It goes against everything that Linux can and should be. Just remember that nobody knows everything---not even Linus--- and that you were a newbie once, too. :) comp.os.linux.announce ========================================================================= Comp.os.linux.announce is a moderated newsgroup for Linux announcements and source patches. The purpose of this group was to get all of the ``important'' Linux information out of the regular newsgroup and into a place where all Linux users could see the important announcements without having to wade through a jungle of other postings. So far, this group has been very successful. The moderators for this group are myself (Matt Welsh, mdw@sunsite.unc.edu) and Lars Wirzenius (wirzeniu@cc.helsinki.fi). We will be sharing the moderator duty, and backing each other up to make sure that postings to this group will be approved as soon as possible after they're submitted. Submissions to this group should be mailed to the address: linux-announce@tc.cornell.edu If you have any problems or questions about c.o.l.announce, please send mail to the moderators at linux-announce-request@tc.cornell.edu Or simply mail us directly. This is not a request address for mailing list subscription; see below. A separate posting details the guidelines for submitting to this group. I plan to approve just about anything that's posted to this group, except for questions or discussions about Linux. So, please, post away. :) There are also archives of comp.os.linux.announce available at a number of Linux FTP sites: check sunsite.unc.edu:/pub/Linux/docs/linux-announce.archive There is a mailing list mirror of the comp.os.linux.announce newsgroup; to join, send mail to linux-activists-request@niksula.hut.fi With the line X-Mn-Admin: join ANNOUNCE at the top of the body (not in the subject). Approved postings to c.o.l.announce will automatically be mailed to this mailing list channel. comp.os.linux.admin ========================================================================= This newsgroup was created simply to thwart the unique newsgroup acronym "c.o.l.a", previously used by c.o.l.announce. However, this newsgroup is also used for discussions and questions about running Linux systems, either in a single-user or multi-user environment. Clearly, there is no large distinction between c.o.l.admin and c.o.l.help. However, .admin should be mostly used for discussions about RUNNING Linux, not USING or PROGRAMMING it. Unfortunately, especially with Linux, the line between system administrator and system user is very fuzzy. In short, we anticipate c.o.l.admin to be mostly about questions with installing, setting up, and configuring Linux systems, as well as other discussions relating to system administration. comp.os.linux.development ========================================================================= c.o.l.development, or "c.o.l.d" for short, is a newsgroup for questions and discussions about Linux kernel and systems-level development. Please note that this is a newsgroup about development OF Linux, not development FOR Linux. In other words, c.o.l.d isn't for questions about programming or porting software to Linux. Instead, this is a newsgroup for discussions about developing the Linux kernel itself, including writing device drivers, adding new features, and so on. In addition, discussions about development of shared libraries, and other essential systems-level projects, are welcome here. Hopefully, this newsgroup will embody some of the content and scope of the linux-activists mailing list channels such as GCC, KERNEL, SCSI, and NET. comp.os.linux.help ========================================================================= Comp.os.linux.help is perhaps the most general of Linux newsgroups. It is for any general user, programming, or setup questions and discussion about Linux. If your question is about Linux development, post to c.o.l.development. If it is about system administration, post to c.o.l.admin. However, if your question is of a more general nature, such as "How do I set up Linux for use with an NE2000 card?", c.o.l.help is your place. Remember that you should not crosspost between .help and other Linux newsgroups. This means that if you are asking for help in .development, that's fine, but .help is for those questions which don't fit into .admin and .development. comp.os.linux.misc ========================================================================= This group is the canonical ``catch-all'' for discussions and questions which don't fit into the other Linux newsgroups. While c.o.l.help is generally for questions, c.o.l.misc is for discussions of a general nature about Linux, such as setting up a file hierarchy standard, questions about Linus' personal life and virtual beer, and the inevitable flame war. Again, it should be noted that crossposting between c.o.l.misc and other Linux newsgroups is strongly discouraged. If your posting or question does not fit into ONLY ONE of the other Linux newsgroups, post it to .misc. Comments ========================================================================= If you have questions or comments about this document, please direct them to mdw@sunsite.unc.edu. Flames to /dev/null; cheques and money orders to Linus Torvalds. Thanks. -- Send submissions for comp.os.linux.announce to: linux-announce@tc.cornell.edu ------------------------------ From: grif@ucrengr.ucr.edu (Michael Griffith) Subject: Re: NIS or workaround (proposal) Date: 2 Oct 1993 18:06:51 GMT In article , Jan Wielemaker wrote: >Hi, > >Trying to get Linux systems set up for our students, one needs NIS >to share at least the passwd stuff (most of the other info is >bearable). I (think I) know NIS is not around and probably wont >be on the very short term (actually I wonder why nobody came >around in implementing such a useful tool). I was thinking of >the following work-around: [plan deleted] Wouldn't be easier just to offer to help with NIS? Join the NYS (yes NYS) channel, or send mail to pen@lysator.liu.se -- Michael A. Griffith grif@cs.ucr.edu ------------------------------ From: bill@bhhome.ci.net (Bill Heiser) Subject: Re: crontab entry for sendmail? Date: Sat, 2 Oct 1993 18:35:40 GMT u1086aa@unx.ucc.okstate.edu (11086) writes: >I'm trying to set up mail over a TCP/IP link using smail/sendmail >included with SLS 1.03. Reading the Network Administrator's Guide, >everything seems to be clear except that at the bottom of page 179 it >says >" With this setup, you still have to make sure the mail queue is >processed periodically. This can be done by adding the following line to >root's crontab: >10 * * * * /usr/lib/sendmail -q >/dev/null " Why wouldn't one just run sendmail as a daemon, i.e. from rc.local "/usr/lib/sendmail -bd -q30m"? -bill -- Bill Heiser bill@bhhome.ci.net heiser@world.std.com ------------------------------ From: mcodogno@nyx.cs.du.edu (Maurizio Codogno) Subject: [solved] mitsumi with kernel 0.99.13 Date: Sat, 2 Oct 93 21:53:41 GMT Thanks to all who replied me. The problem I had with the .99.13 kernel was the fact that I thought the mitsumi=irq,addr option in boot string was recognized by all kernels, while it is a SLS addon. At that point it was easy to modify /usr/include/linux/mcd.h to comply with my hw settings. (now i have 500K more memory... very nice, as I have just 8 Meg RAM) -- ciao! .mau. ===== Maurizio Codogno - CSELT UF/DU dept. - Torino Italy "home" email: mau@beatles.cselt.stet.it ------------------------------ ** 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 ******************************