From: Digestifier To: Linux-Admin@senator-bedfellow.mit.edu Reply-To: Linux-Admin@senator-bedfellow.mit.edu Date: Fri, 1 Oct 93 09:26:19 EDT Subject: Linux-Admin Digest #86 Linux-Admin Digest #86, Volume #1 Fri, 1 Oct 93 09:26:19 EDT Contents: Re: 3.5 boot floppies. Not really Re: [Not] enough SLS bashing anymore (Kurt Siegl) Help configuring SLIP on Terminal Server DS300 (Jym Barnes) crontab entry for sendmail? (11086) Re: SECURITY HOLE in SLS [NOT-QUITE-FIX] (Uppie) Re: SECURITY HOLE in SLS [NOT-QUITE-FIX] (Olaf Schlueter) help with unix (Keith A Grider) [Q] shared memory and message-queues (Doerrsam) (followpu) problems with mitsumi (Maurizio Codogno) sendmail (Robert Seal (Law)) ---------------------------------------------------------------------------- From: siegl@risc.uni-linz.ac.at (Kurt Siegl) Subject: Re: 3.5 boot floppies. Not really Re: [Not] enough SLS bashing anymore Date: Thu, 30 Sep 1993 13:41:13 GMT In article <13049@dirac.physics.purdue.edu>, bcr@bohr.physics.purdue.edu (Bill C. Riemers) writes: > In article <1993Sep26.193920.1780@tcshb1.north.de> taifun@tcshb1.north.de (Markus Nolte) writes: > >Hi ! > >Well - here is my solution to install the slackware dist. without an 3.5" disc. > >There is a tool for MS-DOS called "fdformat" and "fdread" > >It must be available on many ftp-sites. > >This tool allows you to format 5.25" discs with more capacity and with > >"FDFORMAT A: /F144" you can format your 5.25" floppy like a 3.5" floppy. I use vgacopy to copy directly 3.5" to 5.25" now for a longer time and run both formats in parallel. Under Linux you just have to use the corresponding /dev/fd* name, that's all. Booting works only with correctly (1.2MB) formated disks with that technique. Here are my expiriences: > If you read the documentation for fdformat you'll find: > 1. It doesn't work on all 5.25" drives, in fact it mostly just works > with older ones of the right type... (Otherwise they would sell > 5.25" drives with higher capasity.) I hadn't any problems with different drives so far. Computers with both diskdrives understand also the high formated 5.25" disks whithout additional software under DOS, too. If you have only one 5.25" drive you need the fdread (or vgaread) program. > 2. It is dangerous on all 5.25" drives. It will cause your drive to > go out of alignment sooner. That's correct. In the last time I get more and more sector not found or other similar disk errors, when transfering my disks to an other computer. > 3. Standard 5.25HD/DS disks will normally still have a few bad sectors > when formated this way. (The boot disk can't have any errors!) I agree, too. Lot's of disks get damaged and I get read and write errors frequently. Especially if the disks get older, it's really a problem :-( > >YOU ARE ABLE TO BOOT AND INSTALL THE SLACKWARE RELEASE WITH THE 5.25" FLOPPY !! > I'm impressed. As you can tell I wouldn't expect this to work 95% of the time. > If it works for you, great, but I wouldn't recommend it as a general solution. I do it only if I get filled 3.5" installation disks and I'm forced to do, so. Maybe I should really by an 3.5" disk soon :-(. So from my long time experience with this, I wouldn't recommend it, too. Just use it if you have no other choice, only. Kurt ======================================================================= _/_/ _/_/ _/_/_/ Kurt Siegl _/ _/ _/ _/ _/ Email: siegl@risc.uni-linz.ac.at _/ _/ _/ _/ _/ IRC: Kurt007 (Kurt Siegl) _/_/ _/_/ _/ Rmail: RISC, University of Linz, Austria ======================================================================= ------------------------------ From: jybarnes@cs.umr.edu (Jym Barnes) Subject: Help configuring SLIP on Terminal Server DS300 Date: Thu, 30 Sep 1993 14:54:43 GMT HI, I just installed the latest release of LINUX, 99.12, and love it. The only problem I am having is getting the SLIP connection going. The environment I have is as follows. ----------------- | Home PC | | IP Address is | | 192.94.40.246 | ----------------- | Telephone line | --------------------------- | Decserver 300 | | Port IP Address | | 192.94.40.246 (static) | | Terminal servers IP | | Address is 192.94.40.18 | --------------------------- Simple configuration. I am using DIP and don't understand which address to give for remote? Can the address give for local in DIP be the same as the address specified for the port on the DECSERVER 300? Why would Linux need the address of the DECSERVER 300? Is DIP setup more for host based SLIP instead of Terminal server type? I can't find any documentation on the pointopoint argument to ifconfig. I know there is two kinds of SLIP connections and with a DECSERVER 300 the only choice I have is a non routing configuration. In other words only one node could be attached to the DECSERVER not another network. I don't know the terminology for this. Anyway, I would love it if someone could send be the DIP, ifconfig, and route commands to make this work. Also, if someone has set this up on a DECSERVER 300, I would love to have the port setup they used and what kind of flow control setup was used on the modem. If anyone would need more information let me know. Yes I did read the NET-2-FAQ thoroughly. Thanks a ton, Jym Barnes barnes@tweety.digsys.com ------------------------------ From: u1086aa@unx.ucc.okstate.edu (11086) Subject: crontab entry for sendmail? Date: Thu, 30 Sep 1993 15:22:02 GMT 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 " Unfortunately, this means nothing to me. I don't seem to have a man page for crontab (or cron for that matter), and the smail/sendmail man page doesn't mention this. The System Adminstrators Guide simply refers me to the missing manpage. :( Could someone plese help a novice on this? Thanks. Jim ========== Jim West Associate Professor Electrical and Computer Engineering Oklahoma State University jwest@jwest.ecen.okstate.edu ------------------------------ From: juphoff@uppieland.async.vt.edu (Uppie) Subject: Re: SECURITY HOLE in SLS [NOT-QUITE-FIX] Date: 30 Sep 1993 17:56:39 GMT cflatter@nrao.edu (Chris Flatters) writes: >{...} This would be a security hazard of itself (people have >exploited bugs in setuid-root programs to break into systems - the Internet >worm exploited such bugs - and the chances of a setuid/setgid program having >an exploitable bug rises as the number of setuid/setgid programs increases). Read "The Cuckoo's Egg" by Cliff Stoll for an excellent example of a bug like this in an older version of Emacs. -- Jeff Uphoff -- "Uppie" | "The secret to good teaching is sincerity. uppie@vt.edu | As soon as you learn to fake that, you've got juphoff@uppieland.async.vt.edu | it made." ------------------------------ From: olaf@tpki.toppoint.de (Olaf Schlueter) Subject: Re: SECURITY HOLE in SLS [NOT-QUITE-FIX] Date: 30 Sep 1993 20:22:35 +0100 frl@verdi.rd.sub.org (Frank Luthe) writes: >Maybe a stupid question, but, why don't we just keep the /etc/passwd world >unreadable? What's the advantage of the shadow method? Information like the Gecos field (contains full name of user), home directory location (for shells and tools with ~user expansion), and the mapping of user and group id's to user and group names (for the ls command) would become impossible. Some tools will probably break, for example elm, complains about "You have no passwd entry". The passwd access routines are designed to be world accessible and unix programs rely on that since the very beginning. The passwd entry is the only critical entry in /etc/passwd. The shadow method is a solution to that. Another solution is NIS+ from SUN, which let you define access rights per column (among other things). -- Olaf Schlüter, Sandkuhle 4-6, 24103 Kiel, Germany, Toppoint Mailbox e.V. "MSDOS didn't get as bad as it is overnight -- it took over ten years of careful development." David Megginson ------------------------------ From: kgrider@magnus.acs.ohio-state.edu (Keith A Grider) Subject: help with unix Date: 1 Oct 1993 00:16:09 GMT i hope i am in the right newsgroup. i hear from a friend that linux is the system to be able to get unix/xwindows on a 386 machine. is this true? if not, do you have any suggestions? i would like to be able to run an sgi machine remotely from my computer over a slip server. if this is possible please let me know and tell me where i could get this os. thanks, keith grider kgrider@magnusug.acs.ohio-state.edu -- __________________________________________________________________________ Keith Grider 'everybody wants prosthetic foreheads kgrider@magnus.acs.ohio-state.edu on their real heads' They Might Be Giants ------------------------------ From: hb15@uw70.rz.uni-karlsruhe.de (Doerrsam) Subject: [Q] shared memory and message-queues Date: 1 Oct 1993 08:57:29 GMT Reply-To: hb15@rz.uni-karlsruhe.de Hello I'm still a little bit confused where I should locate this query. I hope this newsgroup fits. The problem I run into is that we program some interprocess SW which passes messages in between some processes and the processes use a shared memory too. Since Linux hasn't a tool like 'ipcs' or 'iprm' the only way to get rid of unusable queues and shared memory is a reboot! :-\ Does anybody know how I can handle this problem in a more accurate way? Or is there somewhere a free bundle of 'ipc' tools? Volker =============================================================================== | Volker Doerrsam | Institut fuer Foerdertechnik | Abt. Materialfluss | Tel.: +49 721/608-4428 | Fax : +49 721/758378 =============================================================================== E-mail: hb15@uw70.mach.uni-karlsruhe.de =============================================================================== ------------------------------ From: mcodogno@nyx.cs.du.edu (Maurizio Codogno) Subject: (followpu) problems with mitsumi Date: Fri, 1 Oct 93 09:30:19 GMT Judging from the replies I got, I was not clear at all in my question - so I'll try to explain myself better. Now I am running SLS 1.03, and at boot time I use the command line boot: linux mitsumi=11,0x300 which let me see the cdrom. I got 0.99.13 kernel and I compiled them eliminating SCSI support, network support and other things I don't have nor I need. I retained the "Enable mitsumi" and "ISO9660" options, of course. I had made zImage, copied to /zImage2 and added to lilo that image, with the name linux13. Now, if I boot with linux13 mitsumi=11,0x300 the system works *except* for cdrom support (the message "mitsumi init failed"), while linux mitsumi=11,0x300 keeps working with the old kernel. I tried to add some printk lines to mcd.c, and the kernel could not decompress anymore. By the way, is there a chance to try mcd.c without putting it into the kernel? It could be easier for me to debug it... -- ciao! .mau. ===== Maurizio Codogno - CSELT UF/DU dept. - Torino Italy "home" email: mau@beatles.cselt.stet.it ------------------------------ From: rseal@mailer.cc.fsu.edu (Robert Seal (Law)) Subject: sendmail Date: Fri, 1 Oct 1993 11:14:08 GMT Got some sendmail problems. When I try to sendmail to a user with the first letter being upperacase, I get return mail saying the "the user does not exsist", however, I can sendmail to all my lower case users with no problem. It makes no difference what mailer use , which leads me to believe it is sendmail. Any ideas anyone. Thanks! ------------------------------ ** 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 ******************************