From: Digestifier To: Linux-Admin@senator-bedfellow.mit.edu Reply-To: Linux-Admin@senator-bedfellow.mit.edu Date: Thu, 16 Sep 93 13:13:31 EDT Subject: Linux-Admin Digest #61 Linux-Admin Digest #61, Volume #1 Thu, 16 Sep 93 13:13:31 EDT Contents: Re: Linux standard for system UID/GIDs ?? (Joern Rennecke) Re: [Summary] /etc/shutdown by non-root (Geoffrey Lowney) Re: SLIP / PPP (Charles Hedrick) domain name lookups fail for non-root users (James E Ward) NFS help on setup (Chris Thompson) Linux on HP-Vectra, Busmouse don't work (Bodo Bauer) Want to add swap and repartition (Joe Klemmer) New bash and elm warning (Martin-D. Lacasse) Re: run level testing (Greg Wettstein) Re: CRON jobs not running (John Henders) Re: [Not] enough SLS bashing (Jerry Gaiser) using syssetup and changing mouse configurations (travis jensen) Re: CRON jobs not running (Schneider Klaus) Re: SLIP / PPP (Roos van Raadshooven L.A.) Re: CRON jobs not running (Olaf Titz) Re: domain name lookups fail for non-root users (Olaf Titz) Re: New bash and elm warning (John Henders) Re: [Not] enough SLS bashing (Byron A Jeff) ---------------------------------------------------------------------------- From: amylaar@meolyon.hanse.de (Joern Rennecke) Subject: Re: Linux standard for system UID/GIDs ?? Date: Wed, 15 Sep 1993 07:17:01 GMT edmonds@edmonds.home.cs.ubc.ca (Brian Edmonds) writes: >>>>>> On 15 Aug 1993 17:42:37 GMT, Michael Elkins said: >ME> I looked through the linux-standards, but I couldn't find any >ME> references for a standard list of UIDs and GIDs that a linux box >ME> should have. Obvsiouly, root is UID=0 and GID=0, but what about >ME> other "standard" users and groups such as bin, daemon, sys, etc...? >ME> It seems like it would be a good idea for everyone to be using >ME> roughly the same scheme for these things. >Well, that's a nice idea at first appearance. It might be handy for >people who have standalone systems, or isolated networks, just to give >them some idea what groups they should have, but I'm not convinced that >everyone being different in their choice of ids is likely to affect >anything. >The problem comes with those who are on networks with other machines >(esp. NFS), as they really need to have their ids match the others on >the network, or things start looking rather wierd, and you can get some >interesting security holes. Any standards document must certainly >mention that for cross-platform NFS none of the linux standards should >be considered to apply. On the other hand, with such a standard commonly used for new installations that need not match a previous setup, it would make tar files of system files more meaningful, especially with extra packages to install. And when you want to connect previously unconnected linux boxes with NFS, it saves some effort to have the ids matching already. Joern Rennecke ------------------------------ Crossposted-To: comp.unix.admin From: geoffl@bcstec.ca.boeing.com (Geoffrey Lowney) Subject: Re: [Summary] /etc/shutdown by non-root Date: Wed, 15 Sep 1993 19:24:16 GMT In article <1993Sep15.000813.1013@sol.cs.wmich.edu> stempien@cs.wmich.edu (Brian Stempien) writes: >The method that I use is a program called doas. The source is in >source/usr.bin I think on tsx-11. It basically sets up a control list in >which you place user:program pairs. This is a way to give limit root privs >to select users. Of course you have to trust the program to do the right >thing..... I have a similar program on our Suns. Its called op. It uses an authorization file with lines of the form: execname:tuname:pwdstat:logstat:username,username,... Execname is the name of the program to run. Tuname is the name of the user to become while running execname (usually root). Pwdstat is a "*" to indicate that no password is required, or "#" to indicate a password is required. Pwdstat is a "=" to indicate op should require the user's actual password, or anything else to indicate op should require the special op password (which is encreypted in a file which only root can read). Logstat us a "#" to indicate that a log entry (via syslog), or a "*" to indicate that the command should not be logged. The list of users is a list of user names, or a "*" to indicate all users. Before op runs execname, it sets the path to a known state, preventing the user from inserting their own version of a program in the path before the approved version. To use it, the op directory is placed in the user's path (first), and then soft links are placed in the directory which point to op (i.e. shutdown -> op). When the user enters the command, op runs, sees that it was run as the program, and goes from there. You can also call op as op, and pass the program name as an argument. There are actually more features than can be described in a short space. If you want more info, email me. Geoffrey A. Lowney The Boeing Company Phone: (206) 655-1734 Email: geoffl@bcstec.ca.boeing.com ------------------------------ From: hedrick@geneva.rutgers.edu (Charles Hedrick) Subject: Re: SLIP / PPP Date: 15 Sep 93 22:51:59 GMT jP@hpacv.com writes: > Could someone please tell me if there is any SLIP software >that can be used with 0.99.pl9 WITHOUT patching the kernel and upping >to "NET-2." KA9Q will work. It's on tsx-11.mit.edu somewhere, and also in athos.rutgers.edu /pub/linux/ka9qbin.15.tar.Z and ka9qsrc.15.tar.Z. I'm not sure why you're worried about reinstalling. You don't need to redo all of SLS, just the kernel and network utilities. ------------------------------ From: jward@arizona.edu (James E Ward) Subject: domain name lookups fail for non-root users Date: 15 Sep 93 18:26:24 I hope this isn't a FAQ, but non-root users on my newly installed MCC distribution fail to get domain name resolution. Everything works fine for root. Can anyone tell me what files need to be set to what permissions to remedy this situation? Thanks in advance! ------------------------------ From: thompsch@ccmail.orst.edu (Chris Thompson) Subject: NFS help on setup Date: 15 Sep 1993 23:35:54 GMT Ok I give up I have read the net-2 faq, the Linux administrator's guide, and even looked through several books on how to set up NFS. I have to linux boxes one a 386/40 and the other 486/33 both runing slackware 1.01 or 1.02? I am very new to unix/linux and can't seem to get NFS to work if someone out ther could tell me where to find info or let me take a peak at there rc. inet2 file and there exports file I would be greatful. Or just some step by step instructions would be helpful. Every time I try to mount the files from the other server I get- mount clntudp_create: RPC: program not registerd please send info to Thompsoc@kerr.orst.edu ------------------------------ From: bodo@hal.nbg.sub.org (Bodo Bauer) Subject: Linux on HP-Vectra, Busmouse don't work Date: Wed, 15 Sep 1993 07:36:09 GMT Hi, I tried to install Linux 0.99p12 (the SLS 1.03 Release) on a 486/66 HP-Vectra VL of a friend yesterday evening and run into a Problem with the HP busmouse. It seems to be a Logitech compatible mouse (AUTOCAD works fine with the Logitech-driver under DOS) so I compiled the Logitech busmouse driver into the kernel, linked /dev/bmouselogitec (Major 10, Minor 0) to /dev/mouse, added the line Busmouse "/dev/mouse" to /usr/X386/lib/X11/Xconfig, and startet X. The X-Server started, but after a few seconds it stopped with the message 'cannot open device: /dev/mouse'. I tried it again, but now with a serial mouse attached and everything was fine. So, whats to do? Ciao, BB -- Bodo Bauer UUCP: bodo@hal.nbg.sub.org Voice +49 911 705377 Nuernberger Str. 81 Internet: bodo@guug.de Fax +49 911 705857 D-90762 Fuerth ------------------------------ From: Joe.Klemmer@f370.n109.z1.fidonet.org (Joe Klemmer) Subject: Want to add swap and repartition Date: Wed, 15 Sep 1993 22:10:54 -0500 Raghunath K. Rao wrote in a message to All: RKR> As the header says, I need to add a swap partition (though I RKR> have 16MB!) since some jobs dont run simultaneously with X RKR> on my 486 (SLS1.02). I also want to repartition my hard disk RKR> (reduce the DOS and RKR> increase /user1 and so on...) . Can someone let me know the RKR> best way to handle this? I have a lot of users and need to RKR> minimize down time and retain all the accounts and RKR> configuration! RKR> And please give me details on how to add the swap space. Any RKR> disadvantages in doing this? I don't mean this to sound condisending or anything but have you looked into just adding another drive? It moght be the "least messy" solution overall. Just a suggestion. Later, Joe ------------------------------ From: isaac@elrond.physics.mcgill.ca (Martin-D. Lacasse) Subject: New bash and elm warning Reply-To: isaac@physics.mcgill.ca Date: Thu, 16 Sep 1993 06:30:01 GMT To all those who installed the small beta release (announced a few days ago) of bash as /bin/sh: Be careful!! All your mail message sent by elm will have a correct header but might have an empty message. It took me a while to track this down since a few other changes have been made to my system in the mean time. Anyone else had this problem too? Martin ------------------------------ Date: Wed, 15 Sep 1993 12:19:26 CDT From: Greg Wettstein Subject: Re: run level testing I was plagued by the same concerns for display of run-level information when I re-worked an early version of Miguel's sysv-init for our systems here. I modified the sources so that init places its current run level in its arguement list (argv) when it starts and when it changes run-levels. That way ps and friends can display what run-level the machine is in. I sent these changes along with changes which allow the use of syslog for logging init messages and a recursive alarm scheduler to Miguel but either they did not get to him or he did not consider them appropriate. The only trick in this was to re-exec init with a fake arguement if there were no arguements coming from the kernel/boot process. This was necessary to insure that there was a place for init to write the process-level information to. Actually the kernel probably needs a proctitle system call (or whatever POSIX calls it) to handle this cleanly. Anyway, it solved a problem for us. As always, Dr. G.W. Wettstein Oncology Research Div. Computing Facility Roger Maris Cancer Center UUCP: uunet!plains!wind!greg Fargo, ND 58122 INTERNET: greg%wind.UUCP@plains.nodak.edu Phone: 701-234-2833 ====================================================================== `The truest mark of a man's wisdom is his ability to listen to other men expound their wisdom.' -- GWW ------------------------------ From: jhenders@jonh.wimsey.bc.ca (John Henders) Subject: Re: CRON jobs not running Date: Wed, 15 Sep 1993 23:26:55 GMT bill@unixland.ci.net (Bill Heiser) writes: >I'm wondering, has anyone else run into problems where CRON jobs >don't all seem to run? I have a number of crontab entries, some >of which run, others of which don't ever seem to do anything. >Is cron in .99P12 (SLS 1.03) flakey? I never did get the crond from SLS 1.00 to work. I don't know if it changed since. I found a simpler cron which only uses one crontab file and it works great. -- John Henders GO/MU/E d* -p+ c+++ l++ t- m--- s/++ g+ w+++ -x+ Segments are for Worms ------------------------------ From: jerryg@jaiser.rain.com (Jerry Gaiser) Subject: Re: [Not] enough SLS bashing Date: Wed, 15 Sep 1993 20:11:51 PST Reply-To: jerryg@jaiser.rain.com (Jerry Gaiser) grif@ucrengr.ucr.edu (Michael Griffith) writes: > In article <1993Sep10.041506.8617@cc.gatech.edu> byron@cc.gatech.edu > (Byron A Jeff) writes: > >>But that's exactly the point Jon is trying to make. When someone attempted >>to improve on SLS (with copywrite notices and SLS attributions galore) >>Peter posted a rant and rave about how SLS is his and nobody should use his >>precious scripts. >> >>BTW check out Slackware 1.02 with it's own new scripts. Really cool. > > Slackware already works very nicely. Debian sounds like a great idea. > MCC advocates are practically violent about how great MCC is. Next > time try another distribution and see how you like it. Well, I don't know about Slackware, because it requires me to have a 3 1/2 inch diskette to boot and, believe it or not, I don't. So for _some_ of us Slackware is worthless. All of these have their problems. But until the distributor of Slackware decides to support 5 1/4, I'll have to stick with SLS and MCC. -- Jerry Gaiser (jerryg@jaiser.rain.com) (voice) 503-359-4017 Fidonet 1:105/380 (bbs) 503-359-5111 Inritum est qua legibus prohibitum est ------------------------------ From: jensen%peruvian.cs.utah.edu@cs.utah.edu (travis jensen) Subject: using syssetup and changing mouse configurations Date: 16 Sep 93 03:50:30 MDT I just finished installing SLS 1.03 on my 486dx33 and screwed up already. :/ Instead of configuring a PS/2 mouse (like I have), I entered a serial mouse (don't ask why). I tried to change it in the install program, but it wouldn't work; so I tried to change it using syssetup. Here's what happened: #/syssetup #/ Is there a specific configuration for syssetup or is there something else I can do to get this fixed. BTW, my ps/2 mouse is recognized when booting up, so do I even have to worry about this? Travis *who would like to thank anybody who takes the time to help a newbie* -- Travis A. Jensen jensen@peruvian.cs.utah.edu (preferred) jensen@cadehp0.eng.utah.edu (next best) "My elelator! Not your elelator, my elelator!!"--Baby Plucky Duck ------------------------------ From: uk0q@rzstud1.rz.uni-karlsruhe.de (Schneider Klaus) Subject: Re: CRON jobs not running Date: 16 Sep 1993 10:53:53 GMT John Henders (jhenders@jonh.wimsey.bc.ca) wrote: : I never did get the crond from SLS 1.00 to work. I don't know if it : changed since. I found a simpler cron which only uses one crontab file : and it works great. John, would you please care to tell us where you found your "simpler cron?" Klaus ------------------------------ From: roosvanr@athena.research.ptt.nl (Roos van Raadshooven L.A.) Subject: Re: SLIP / PPP Date: Thu, 16 Sep 1993 11:34:53 GMT hedrick@geneva.rutgers.edu (Charles Hedrick) writes: >jP@hpacv.com writes: >> Could someone please tell me if there is any SLIP software >>that can be used with 0.99.pl9 WITHOUT patching the kernel and upping >>to "NET-2." >KA9Q will work. It's on tsx-11.mit.edu somewhere, and also in >athos.rutgers.edu /pub/linux/ka9qbin.15.tar.Z and ka9qsrc.15.tar.Z. >I'm not sure why you're worried about reinstalling. You don't need to >redo all of SLS, just the kernel and network utilities. ... and GCC & libc ------------------------------ From: uknf@rzstud1.rz.uni-karlsruhe.de (Olaf Titz) Subject: Re: CRON jobs not running Date: 16 Sep 1993 14:04:35 GMT In article <1993Sep13.000027.156@unixland.ci.net>, Bill Heiser wrote: > I'm wondering, has anyone else run into problems where CRON jobs > don't all seem to run? I have a number of crontab entries, some > of which run, others of which don't ever seem to do anything. > Is cron in .99P12 (SLS 1.03) flakey? I have this version, and cron does its work well. You have to ensure that the &$%$/!# permissions are set right, though (i.e. /usr/spool/cron belongs to root.daemon and is not world read/writable and the crontabs files belong to the respective users, and crontab is setuid.) Olaf -- olaf titz o olaf@bigred.ka.sub.org praetorius@irc comp.sc.student _>\ _ s_titz@ira.uka.de LINUX - the choice karlsruhe germany (_)<(_) uknf@dkauni2.bitnet of a GNU generation what good is a photograph of you? everytime i look at it it makes me feel blue ------------------------------ From: uknf@rzstud1.rz.uni-karlsruhe.de (Olaf Titz) Subject: Re: domain name lookups fail for non-root users Date: 16 Sep 1993 15:26:27 GMT In article , James E Ward wrote: > I hope this isn't a FAQ, but non-root users on my newly installed MCC > distribution fail to get domain name resolution. Everything works > fine for root. Can anyone tell me what files need to be set to what > permissions to remedy this situation? /etc/hosts, /etc/host.conf, /etc/resolv.conf(?) world-readable -- olaf titz o olaf@bigred.ka.sub.org praetorius@irc comp.sc.student _>\ _ s_titz@ira.uka.de LINUX - the choice karlsruhe germany (_)<(_) uknf@dkauni2.bitnet of a GNU generation what good is a photograph of you? everytime i look at it it makes me feel blue ------------------------------ From: jhenders@jonh.wimsey.bc.ca (John Henders) Subject: Re: New bash and elm warning Date: Thu, 16 Sep 1993 09:34:54 GMT isaac@elrond.physics.mcgill.ca (Martin-D. Lacasse) writes: > To all those who installed the small beta release (announced > a few days ago) of bash as /bin/sh: Be careful!! > All your mail message sent by elm will have a correct > header but might have an empty message. It took me a while to > track this down since a few other changes have been made > to my system in the mean time. > Anyone else had this problem too? YES!! Here I just logged in to report this, after spending the last 1/2 hour trying to figure out how I'd broken elm, and what do I see? I'm not the first to notice. It's definately the new bash, as I restored everything else to confirm. Also, it's only elm that breaks. Sending mail with mailx and nn works fine. -- John Henders GO/MU/E d* -p+ c+++ l++ t- m--- s/++ g+ w+++ -x+ Segments are for Worms ------------------------------ From: byron@cc.gatech.edu (Byron A Jeff) Subject: Re: [Not] enough SLS bashing Date: Thu, 16 Sep 1993 16:20:04 GMT In article <930915.201151.2C5.rusnews.w165w@jaiser.rain.com>, Jerry Gaiser wrote: >grif@ucrengr.ucr.edu (Michael Griffith) writes: > >> In article <1993Sep10.041506.8617@cc.gatech.edu> byron@cc.gatech.edu >> (Byron A Jeff) writes: >> >>>But that's exactly the point Jon is trying to make. When someone attempted >>>to improve on SLS (with copywrite notices and SLS attributions galore) >>>Peter posted a rant and rave about how SLS is his and nobody should use his >>>precious scripts. >>> >>>BTW check out Slackware 1.02 with it's own new scripts. Really cool. >> >> Slackware already works very nicely. Debian sounds like a great idea. >> MCC advocates are practically violent about how great MCC is. Next >> time try another distribution and see how you like it. > >Well, I don't know about Slackware, because it requires me to have a 3 1/2 >inch diskette to boot and, believe it or not, I don't. > >So for _some_ of us Slackware is worthless. > >All of these have their problems. But until the distributor of Slackware >decides to support 5 1/4, I'll have to stick with SLS and MCC. In principle you are correct. However Patrick has provided a couple of features that can help. 1) He has a test version of a 5.25 boot/root pair on ftp.cdrom.com:/pub/linux/tst. The README for the 5.25 can be found with the rest of the distribution. 2) 5.25 is really only required for booting. You can install via hard disk or NFS. Unfortunately many people don't have access to a network and don't have enough disk space to temporarily store the distribution to the HD in order to install it. Patrick does try his best to keep Slackware up to date. But maintaining 2 separate distributions will slow him down. As a last resort of course you can shuffle the packages into a 1.2M format. If you try that you'll see why Patrick doesn't keep track of 2 distributions! I'll be glad to help anyone I can to get Slackware on their machine. It's my distribution of choice. BTW I do have only a 5.25 drive on my home machine. I ended up bringing it to work, putting it on the network and installing via NFS. Works like a champ! Later, BAJ --- Another random extraction from the mental bit stream of... Byron A. Jeff - PhD student operating in parallel! Georgia Tech, Atlanta GA 30332 Internet: byron@cc.gatech.edu ------------------------------ ** 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 ******************************