From: Digestifier To: Linux-Development@senator-bedfellow.mit.edu Reply-To: Linux-Development@senator-bedfellow.mit.edu Date: Tue, 2 Nov 93 03:13:14 EST Subject: Linux-Development Digest #203 Linux-Development Digest #203, Volume #1 Tue, 2 Nov 93 03:13:14 EST Contents: Re: What's wrong with a DOS to Linux disk access? (Steef S.G. de Bruijn) Re: What's wrong with a DOS to Linux disk access? (Lars Wirzenius) Re: What's wrong with a DOS to Linux disk access? (David Barr) Re: GCC crashing Linux: kernel bug (Greg Patten) Re: GCC crashing Linux: kernel bug ("Eric Jeschke") Re: Tcl7.0 / Tk3.3 (John Waterson) Re: Dos discrimination, Politically Correctness in the Linux community. (Alan Cox) [Q] Support for SCSI DAT(EXB-4200/other) Tape Drives (Sohail M. Parekh) Re: GCC crashing Linux: kernel bug (Dan Miner) Re: Yet another core dumps name suggestion (Craig Milo Rogers) Re: What's wrong with a DOS to Linux disk access? (Tim Smith) modem dialing problems (Garcia G Roble) Re: MCA Support > Please (Mark Evans) Re: ugly name for core dumps (core.imagename) -> patch for "img.core" (Scott W. Adkins) Re: What's wrong with a DOS to Linux disk access? (Matthias Urlichs) Re: What's wrong with a DOS to Linux disk access? (Byron A Jeff) Linux and PCMCIA (Darryl Burke) Re: What's wrong with a DOS to Linux disk access? (Joel M. Hoffman) ---------------------------------------------------------------------------- From: debruijn@cs.utwente.nl (Steef S.G. de Bruijn) Subject: Re: What's wrong with a DOS to Linux disk access? Date: Mon, 1 Nov 1993 14:36:27 GMT Again about security: Maybe a sort of FTP server just for copiing files from and to the Linux FS AFTER legally logging in... Steef -- S.G. de Bruijn Twente University of Technoloy, Dept. of Computer Science E-Mail: debruijn@cs.utwente.nl ##### / \ < o o > | C | Stevie "SpikerJack" de Bruijn /--\___/--\ / |o \ / /| |o |\ \ / / | |o | \ \ -- | |o | -- --------- Planning is a difficult thing... Using Linux is not! ------------------------------ From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius) Subject: Re: What's wrong with a DOS to Linux disk access? Date: 1 Nov 1993 17:09:06 +0200 debruijn@cs.utwente.nl (Steef S.G. de Bruijn) writes: > Doesn't ANYBODY see a BIG security hole here? If such a DOS > driver existed, I would make SURE it was not present at my box. > If I make directories totally unreadable for normal Linux users, > I would like to keep it that way, also when people were Dozzing > my machine... As long as people have physical access to your machine (especially the floppy drive), you're going to have a hard time stopping them from booting Linux on a floppy, then mounting your hard disk, then doing whatever they want. -- Lars.Wirzenius@helsinki.fi (finger wirzeniu@klaava.helsinki.fi) It doesn't matter who you are, it's what you do that takes you far. --Madonna ------------------------------ From: barr@pop.psu.edu (David Barr) Subject: Re: What's wrong with a DOS to Linux disk access? Date: 1 Nov 1993 15:28:48 GMT In article , Steef S.G. de Bruijn wrote: >Doesn't ANYBODY see a BIG security hole here? If such a DOS >driver existed, I would make SURE it was not present at my box. Oh, ye of narrow mind. Giving your users access to DOS is inherently a security hole. --Dave -- System Administrator, Penn State Population Research Institute "When I was very young, I kissed my first woman, and smoked my first cigarette on the same day. Believe me, never since have I wasted any more time on tobacco" - Arturo Toscanini ------------------------------ From: greg@loose.apana.org.au (Greg Patten) Subject: Re: GCC crashing Linux: kernel bug Date: Mon, 1 Nov 1993 15:06:15 GMT zonni@supernalle.cs.hut.fi (John P. Norris) writes: >Yes, i have noticed this bug too, happens much more often when you run X. >I don't even have to GCC anything, just running EMACS sometimes is enough. And me..running X and getting into swap (I have 8M) is a sure way to ensure a reboot. Large compiles (eg. an new kernel) also cause the infamous sig-11 death (hehe - and I thought it was just me). -- Greg Patten greg@loose.apana.org.au ------------------------------ From: "Eric Jeschke" Subject: Re: GCC crashing Linux: kernel bug Date: Mon, 1 Nov 1993 12:34:27 -0500 Many people have reported this problem (SIG 11 during compiles) for months. Please try any of the following: 1) Disable your external cache in the BIOS setup. 2) Increase your RAM refresh rate in the BIOS setup (if possible). 3) Find a way to cool down your CPU operating environment. -- Eric Jeschke | Indiana University jeschke@cs.indiana.edu | Computer Science Department eric%marmot@moose.cs.indiana.edu | ------------------------------ From: watersoj@dcs.glasgow.ac.uk (John Waterson) Subject: Re: Tcl7.0 / Tk3.3 Date: Mon, 1 Nov 1993 17:58:27 GMT rjw9917@bcstec.ca.boeing.com (Robert J. Willard) writes: > Is anyone currently porting Tcl7.0 and Tk3.3 to Linux? I built static libraries for both of them the other day, and although I had a few problems, I'm almost certain that they were caused entirely by my own setup and won't trouble anybody else. While I'd be happy to put a distribution together, I haven't the first idea how to do it, so I'd advise that you compile them yourself. If I'm right about the problems I had, then you should only have to do a "configure" and a "make" for each package. And even if I'm wrong, and you hit the same problems as me, my workarounds for them are listed below, so that should get you by. BTW - I'm posting the descriptions of these two problems for an additional reason: I want to check that they're local to my setup. That means, if you hear about/come across/experience a similar problem, please let me know, and I'll assume it's a *real* bug and let the relevant authorities know. I can't remember full error messages, as I forgot them as soon as things started to work again, but they shouldn't be hard to spot. All of these on a no-name 486sx25, 8Mb RAM, 10Mb swap, running pl12 kernel, GCC 2.4.5 and libc 4.4.1 (I know, I'm out of date). :-) First problem, GCC starts whingeing about undefined stuff in "features.h," (in /usr/include (?)). This turned out to be a literal backspace character (ie, a real ^H) in the file instead of an open parenthesis. Easy fixed. The other took a little black magic. The make suddenly stopped, with a mysterious error that threatened possibly to be a compiler bug. I tried it again a few times, with no success, then tried running the last line again manually (ie, retyping all the flags, verbatim) except using the command name gcc instead of cc. It still barfed, but the next time I tried make again, everything went smoothly. I don't claim to understand what happened here; if hocus pocus works, I'll use hocus pocus. If you have similar problems, do shout. John Waterson watersoj@dcs.gla.ac.uk ------------------------------ From: iiitac@swan.pyr (Alan Cox) Subject: Re: Dos discrimination, Politically Correctness in the Linux community. Date: Mon, 1 Nov 1993 17:14:35 GMT In article <2asbme$phh@amhux3.amherst.edu> jedubins@unix.amherst.edu (Just a fellow traveller...) writes: >Alan Cox (iiitac@swan.pyr) wrote: >I really don't want to start a flamewar here, because it seems to be such >a senseless waste of human life, but.... > >I've been using and programming on different platforms and in different >languages for a long time. It's not like I just started using and programming >computers yesterday. I've always realized how important it was to know that >the computer was supposed to be my tool, and not the other way around. >If it's useful, and saves time under a general situation or otherwise, why not >implement it? Because it would take a good programmer 6-9months solid work, its a minor problem in most people's eyes and there are important things to do. If someone feels it is important enough they can go and write it (and for once nobody will yell copyright and sue them). I doubt anyone will. >I would've thought it would be morally repugnant for most Linux developers >to realize they had the same ways of approaching problems as MS employees. They don't. In this case microsoft have made it so hard to do this relatively easy to avoid operation that its not worth doing. Alan iiitac@pyr.swan.ac.uk ------------------------------ From: sohail@trixie (Sohail M. Parekh) Subject: [Q] Support for SCSI DAT(EXB-4200/other) Tape Drives Reply-To: sohail@rhonda.jsc.nasa.gov Date: Mon, 1 Nov 1993 18:44:13 GMT I am thinking of buying a EXB-4200 (or EXB-4200C) for my LINUX box. So I decided to ask a few questions of I may. a) How do you feel about the EXB-4200 (or EXB-4200C) support ? b) I have a UltraStor 34F SCSI controller that I will daisy-chain from are there any known problems in this configurations. c) Is there support for EXB-4200C ? d) Is there support for EXB-8200 ? e) why would one buy 8200 (usually more expensive) compare to 4200 ? f) Is there support for any other DAT tape drives ? g) Is the driver for EXB-4200 fairly mature ? Since the drive cost about $800 - $900 I want to make sure that I could use it effectively. Thanks in advance. My Configuration [486/66 99p13 GCC2.4.5 4.4.4 VLB UltraStor34F] Sincerely. Sohail -- Sohail M. Parekh Grumman Data Systems sohail@rhonda.jsc.nasa.gov 12000 Aerospace Ave. (713) 483-5912 Houston, TX 77034 ------------------------------ From: dminer@nyx10.cs.du.edu (Dan Miner) Subject: Re: GCC crashing Linux: kernel bug Reply-To: dminer@nyx10.UUCP (Dan Miner) Date: Mon, 1 Nov 93 19:26:40 GMT Too me... :) But, I'm under X windows and using alot of memory. For me, I can all most hear it coming, so I've avoided it a couple of times. (I crashed four times using ObjectBuilder). 386sx/20 6 megs IDE (80 meg) 5 swap partition 0.99.11 (w/ small patch, remember the DS_USER bug? ) Dan ------------------------------ From: rogers@drax.isi.edu (Craig Milo Rogers) Subject: Re: Yet another core dumps name suggestion Date: 1 Nov 1993 10:45:22 -0800 In article <1993Oct28.124410.15292@nenuphar.saclay.cea.fr> basile@soleil.serma.cea.fr writes: >Also, my opinion is that the whole idea of core files (a good idea in >the PDP-8 unix days) is wrong today, since more and more programs are ^ History Alert! PDP-11! If you really press, there was an earlier implementation (PDP-7?), but never on a PDP-8. >huge and buggy (todays core file can easily much bigger than the Agreed; it was so much easier when when Unix programs were small and buggy. :-) Craig Milo Rogers ------------------------------ From: tzs@stein3.u.washington.edu (Tim Smith) Subject: Re: What's wrong with a DOS to Linux disk access? Date: 1 Nov 1993 21:15:20 GMT Steef S.G. de Bruijn wrote: >Doesn't ANYBODY see a BIG security hole here? If such a DOS >driver existed, I would make SURE it was not present at my box. >If I make directories totally unreadable for normal Linux users, >I would like to keep it that way, also when people were Dozzing >my machine... The security hole is letting someone run DOS on your machine. A person with a disk sector editor and a listing of the file system data structures for whatever filesystem you use with Linux would have no trouble reading your files. No driver would be required. --Tim Smith ------------------------------ From: roble@CS.Arizona.EDU (Garcia G Roble) Subject: modem dialing problems Date: 1 Nov 1993 14:19:54 -0700 Hi, I just installed linux SLS in my PC clone (486DX, 8 MB RAM 210 MB HD), and every thing has been working Ok, except that the modem access to my University is having problems. I have an internal bayes compatible 2400 bps modem. I am using kermit. After the kermit prompt I dial a phone number. The modem starts sending its request of connection, as it does with the DOS program (procomm). But after the I get the connection, the message "call complete" appears, and then the prompt from the kermit is there waiting for the next command. I have read the FAQs, but no one is related with this. Any help will be appreciated. Send me your help to: roble@caslon.cs.arizona.edu (Saul Robles) thanks Saul ------------------------------ From: evansmp@mb48059.aston.ac.uk (Mark Evans) Subject: Re: MCA Support > Please Date: Mon, 1 Nov 1993 21:43:24 GMT Uri Blumenthal (uri@yktnews.UUCP) wrote: : From article <2avec1$8sv@hecate.umd.edu>, by ceham@w3eax.umd.edu (Maurice De Vidts NE3S): : > I would greatly appreciate if someone would POST an "official" update : > about the subject, since many of us linux-less PS/2 users are : > stranded. : Two things are to be done to get Linux up and runnng on MCA: : 1) ESDI support, publication 68X2234, form # S68X-2234. : 2) SCSI support, pubs 68X2397 and 68X2365. : [I'm working on ESDI, but I'm so bogged down with my "official" : work I don't have the slightest idea when any progress will : be made, if at all.] : To get display to work with anything better than 640x480x16 one : will need to port some XGA and/or V256C (ThinkPad-700 chip). Also microchannel ethernet cards. I have only seen BICC and WD cards for MCA, though there may be others. ------------------------------ From: sadkins@bigbird.cs.ohiou.edu (Scott W. Adkins) Subject: Re: ugly name for core dumps (core.imagename) -> patch for "img.core" Date: Mon, 1 Nov 1993 14:47:32 GMT In article <13326@dirac.physics.purdue.edu> bcr@bohr.physics.purdue.edu (Bill C. Riemers) writes: >In article rfrankel@us.oracle.com (Rick Frankel) writes: >>From: bcr@bohr.physics.purdue.edu (Bill C. Riemers) >>BR> --> I've modified make clean to remove core.* files, instead of core. >>All make `clean' will have to be modified to rm *.o, etc then execute >>the `rmcore' script. > >Fortunately there are not files in the /usr/src/linux tree that are named >core.c or core.h, so this is not a problem in this case... However in >general an inconvient wild card of: > >CORE = core.{[ab,d-g,j-r,t-z,AB,D-G,J-R,T-Z,0-9]*,[chsCHS]?*} > > rm -f $(CORE) > >needs to be used... I know I would much prefere to have core as an >extention to going through all these acrobatics in a "rm" command. If you know that there might exist a core.[cho] in the directory, and your binary is more than one character in length, then why not do something like rm -f core.??* or something like that? I have used this method many times to remove files greater than one character in length, and leaving all those files with exactly one character... Scott -- Scott W. Adkins Internet: sadkins@ohiou.edu ~~~~~~~~~~~~~~~ ak323@cleveland.freenet.edu Ohio University of Athens Bitnet: adkins@ouaccvma.bitnet ------------------------------ From: urlichs@smurf.sub.org (Matthias Urlichs) Subject: Re: What's wrong with a DOS to Linux disk access? Date: 1 Nov 1993 14:32:45 +0100 In comp.os.linux.development, article , debruijn@cs.utwente.nl (Steef S.G. de Bruijn) writes: > Doesn't ANYBODY see a BIG security hole here? If such a DOS > driver existed, I would make SURE it was not present at my box. > If I make directories totally unreadable for normal Linux users, > I would like to keep it that way, also when people were Dozzing > my machine... > Booting DOS implies being able to shutdown the machine and telling LILO to boot DOS and/or to boot from a floppy. Booting Linux single-user implies exactly the same. Either way, the guy/gal sitting in front of the box has access to all your data, so having or not having a DOS driver to access a Linux file system doesn't make any difference. If you want DOS users to not be able to access your Linux data, that's easy: disable booting from floppy, password-protect LILO, and let them use dosemu. NB: I do know that some programs don't work under the emulator. Yet. That being said, personally I try not to even think about the existence of MeSsy-DOS. The fact that I once wrote a comm program for the thing is shameful enough. ;-) Useless factoid: DOS once allowed you to create file names with spaces in them (maybe it still does, I wouldn't know), like "TEXT 1.TXT". No problem, just use a program that doesn't check for such inanities. Of course, no DOS tool is able to delete this file... and no, "DEL *.TXT" or DEBUG don't count. -- Many people have senseless attachments to heavy, clumsy things such as this 'Homer' of yours. -- Jacques in _Jacques_to_be_Wild_, from The Simpsons -- Matthias Urlichs \ XLink-POP Nürnberg | EMail: urlichs@smurf.sub.org Schleiermacherstraße 12 \ Unix+Linux+Mac | Phone: ...please use email. 90491 Nürnberg (Germany) \ Consulting+Networking+Programming+etc'ing 42 ------------------------------ From: byron@cc.gatech.edu (Byron A Jeff) Subject: Re: What's wrong with a DOS to Linux disk access? Date: Mon, 1 Nov 1993 23:44:32 GMT In article , Steef S.G. de Bruijn wrote: >Again about security: Maybe a sort of FTP server just for >copiing files from and to the Linux FS AFTER legally logging >in... > Considering that Linux won't be running at the time, I think that's going to be some magic trick. However since you'll have access to the password (and shadow I guess) files you can force the person to give a login and password before allowing file transfer. Since I only have Linux on my machine, none of this affects me personally. 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 ------------------------------ From: dburke@jupiter (Darryl Burke) Subject: Linux and PCMCIA Date: 2 Nov 1993 00:23:19 GMT Does anyone know of any PCMCIA devices that will run under linux?? Darryl Burke dburke@jupiter.scs.ryerson.ca ------------------------------ From: joel@rac3.wam.umd.edu (Joel M. Hoffman) Subject: Re: What's wrong with a DOS to Linux disk access? Date: Tue, 2 Nov 1993 00:14:32 GMT [who wrote what deleted] >>>Yes. I created a text file in emacs on the Linux disk, and now, when >>>I'm running Quark under Windows, I want to import it. How do I get it? > >It's hard to believe so many people responding to this thread can be >this thick, and even after it being re-explained. > >What he's asking is how to access the Linux filesystem FROM DOS! > >I don't know of a way, you'd have to write a Linux filesystem driver >that runs under DOS, and I don't know that one exists. You don't need anything so complicated as a filesystem driver. All you need is the reverse of mtools. You need a program that can read the minix FS, and read/write files on it. For example, from dos, you'd be able to copy lcopy hda4:/tmp/myunixfile mydosfil.e. Probably most of the code is already in the kernel. You'd just have to write the front end. -Joel (joel@wam.umd.edu) -- ============================================================================= |_|~~ Germany, Europe. 1943. "The diameter of the bomb was 30 centimeters, __|~| 16 Million DEAD. and the diameter of its destruction, about 7 meters, and in it four killed and 11 wounded. cnc Bosnia, Europe. 1993. And around these, in a larger circle of pain cnc HOW MANY MORE? and time, are scattered two hospitals and one cemetery. But the young woman who was buried in the place from where she came, at a distance of more than than 100 kilometers, enlarges the circle considerably. And the lonely man who is mourning her death in a distant country incorporates into the circle the whole world. And I won't speak of the cry of the orphans that reaches God's chair and from there makes the circle endless and godless." ============================================================================= Tell Clinton to stop the genocide: president@whitehouse.gov ------------------------------ ** 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-Development-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.development) via: Internet: Linux-Development@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-Development Digest ******************************