Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA15332; Fri, 15 Dec 95 22:17:11 EST Received: from SENATOR-BEDFELLOW.MIT.EDU by MIT.EDU with SMTP id AA04296; Fri, 15 Dec 95 22:17:12 EST Received: (from root@localhost) by senator-bedfellow.MIT.EDU (8.6.12/2.3JIK) id WAA01291 for Linux-Development-System-Dist@senator-bedfellow.mit.edu; Fri, 15 Dec 1995 22:13:59 -0500 Message-Id: <199512160313.WAA01291@senator-bedfellow.MIT.EDU> From: Digestifier To: Linux-Development-System@senator-bedfellow.MIT.EDU Reply-To: Linux-Development-System@senator-bedfellow.MIT.EDU Date: Fri, 15 Dec 95 22:13:55 EST Subject: Linux-Development-System Digest #122 Linux-Development-System Digest #122, Volume #2 Fri, 15 Dec 95 22:13:55 EST Contents: Re: Elf libraries dirty more pages? (Kirk Shipley) Re: How to write a patch (Uwe Bonnes) Re: Transputer Linux? - Oops (Alberto Vignani) libc-5.2.16 makes emacs coredump in XLoadFont() (Steve M. Robbins) need /proc-style program interface (root) Re: Kernel protection against device drivers! (Aurel Balmosan) 1.3.47 Failure. (Mark Swanson) Re: Linux Security - C2 and beyond (Ian Chard) Re: Does Linux support (or will) RAID 5 drives and/or Hot plugged drives ? (Bart Peirens) Re: Transputer Linux? (Bruce Stephens) Re: 'make' fails on 1.3.47 (sbeer@ibm.net) Re: Tape drives that connect to floppy controller (C Shamis) Strip.. Why NOT use it? (Phillip G Ezolt) Re: Are libc functions MT-safe? (Peter Hofmann) Question -- Virtual Interfaces (network, multiple IP's) Exist? (Jonathan Katz) Re: Linux ISO 7816 emulator (was: New Voyager) (Harald Koenig) Re: HELP: Compiling the Kernel: <<<<<< Segmentation fault >>>>>>> (Kevin Haddock) Re: Strip.. Why NOT use it? (Larry Daffner) Re: Login Accounting in Linux (Mark Donnelly) Re: Does Colorado work with Linux at all? (Amit Chatterjee) ---------------------------------------------------------------------------- From: Kirk Shipley Crossposted-To: comp.os.linux.development.apps,comp.os.linux.misc Subject: Re: Elf libraries dirty more pages? Date: Thu, 14 Dec 1995 11:09:03 -0600 Under HP-UX, you have the option in the linker of selecting immediate or deferred binding for the libraries. If you muck with your library after having built the executable, and you linked it with immediate binding, you get a well-deserved run-time fault when you try to get to those changed functions. Would something like this be an option for future ELF linking? -- Kirk Shipley shipley@l13kk.jsc.nasa.gov ^ Lockheed Martin Engineering & Science Services / \___| Unless otherwise explicitly noted, any opinions expressed are /\| |/\ | "mine, mine, mine, all mine" nobody else should bear the blame ||| ||| | or get the credit. /\^^^/\ |___ ------------------------------ From: bon@elektron.ikp.physik.th-darmstadt.de (Uwe Bonnes) Subject: Re: How to write a patch Date: 15 Dec 1995 21:14:52 GMT Li YunZhou (yunzhou@eeserver.ee.nus.sg) wrote: : Can anyone tell me how to write a patch file ? : I've done something for the Linux kernel, and : intend to let Linux people to apply that patch : file to use my program. : Read " man diff" and "man patch". I do "diff -uw > patchfile" and "cat patchfile |patch" -- Uwe Bonnes bon@elektron.ikp.physik.th-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt ========= Tel. 06151 162516 ======== Fax. 06151 164321 ========== ------------------------------ From: alberto.vignani@torino.alpcom.it (Alberto Vignani) Subject: Re: Transputer Linux? - Oops Date: 15 Dec 1995 19:38:16 -0500 Reply-To: alberto.vignani@torino.alpcom.it (Alberto Vignani) In a previous message I wrote: |There are(were?) some UNIX-like OSs available on Transputers, the best |known are Helios and Parix. There are no free OS for this chip AFAIK; Oops... Minix runs on Transputers, and it's now freeware. Check ftp://unix.hensa.ac.uk/pub/parallel/transputer/software/OSes/minix for details. Alberto ------------------------------ From: steve@nyongwa.montreal.qc.ca (Steve M. Robbins) Subject: libc-5.2.16 makes emacs coredump in XLoadFont() Date: Fri, 15 Dec 1995 20:10:00 GMT Hullo, I can't tell if this is an emacs problem, a libc problem, or an Xlib problem :( I have been running emacs 19.29 for months now, compiled in ELF with x-toolkit option. I have the ELF version of XF86-3.1.2, and all was working fine until I installed libc-5.2.16. After that, the menu option "Make New Frame" on the "Files" menu will cause emacs to coredump with SEGV in the XLoadFont() call. I recompiled emacs, (gcc 2.7.2) but no change. I can run the debugger on emacs, but of course it goes through all the crazy elisp calls, so that's not terribly useful. Besides, the SEGV happens in the Xlibrary, for which I don't have the source (and don't relish poring through even if I did have). This happens under kernel versions 1.3.45 and 1.3.47. Help? -- -- Steve Robbins Speeding motorcycle ... won't you take me ... ------------------------------ From: root Subject: need /proc-style program interface Date: Tue, 12 Dec 1995 18:47:45 -0600 Hello. I want to implement a /proc-style interface to a perl program which I am writing. Namely, I need to be able to 'cat' a location in the filesystem and have it feed to me information from my perl program. Can this be done in general? What are the specific c calls which I need to investigate? Should I do this, can I do this via Berkeley-style IPC sockets, such as 'cat /dev/todds_program'? Will I have to modify my kernel in order to support this function? Any pointers on how one might go about doing this would be helpful. TIA. Todd Lewis VP Networking Cheney Communications Company tlewis@cheney.net ------------------------------ From: aurel@xylo.owl.de (Aurel Balmosan) Subject: Re: Kernel protection against device drivers! Date: Fri, 15 Dec 1995 10:33:35 GMT Mats Andtbacka (mandtbac@news.abo.fi) wrote: : Alain Knaff, in <4am1g3$g98@imag.imag.fr>: : [...] : > I think VMS did this by using three protection rings: one for the : >user, one for the kernel, and one for the device driver. The INTEL : >processors have 4 protection rings, so this should be possible. : Maybe, but could it be kept portable wrt the other architectures? I'm : unclear on whether the 680x0 has any equivalent of 80x86 protection : rings, for example; please don't ask about the PPC or Sparc... : -- : " ... got to contaminate to alleviate this loneliness : i now know the depths i reach are limitless... " : -- nin Want about a general internal interface between the main kernel and device drivers or filesystems? So you only need a mmu to protect the pages that should not be accessed by the driver. -- ================================================================ Aurel Balmosan aurel@xylo.owl.de ------------------------------ From: mark@hunter.globalx.net (Mark Swanson) Subject: 1.3.47 Failure. Date: 15 Dec 1995 17:37:20 GMT linux-1.3.47.tar.gz uncompressed and compiled fine for me, however when I reboot I get a 'd' character in the top left position of the screen and it locks solid. this happens just after the kernel loads off the hard drive and uncompresses. The screen doesn't even get cleared. 586/100 Linux 1.3.47, libc5.2.16, 32MB RAM. Lilo 16. Linux 1.3.45 works like a charm! -- ===================================================================== Mark Swanson Tel: (613)565-0093 DigiCrypt Technologies, Inc. Fax: (613)729-5908 1318 Wellington Street Internet: mark@luckman.com Box 36041 Ottawa, Ontario K1Y 4V3, Canada ===================================================================== ------------------------------ From: ian@tanagra.demon.co.uk (Ian Chard) Subject: Re: Linux Security - C2 and beyond Date: Fri, 15 Dec 1995 18:39:38 GMT root writes: >What is to stop me from rebooting a "secure" win95 system w/ my >handy-dandy two-disk all-in-one general-purpose >linux-os-hardware-access-tool, mounting the fs, and going to town? >only the inanities of the M$ filesystem, a surmountable (though not >insignificant) problem. There are BIOSes around that you can configure so that they won't boot from a floppy, and can't be reconfigured without a password. Short of opening the machine up and disconnecting the battery, I'd say that's fairly secure. -- [ Ian Chard, back in Manchester | "I've only ever owned a tissue!" ] [ Email: ian@tanagra.demon.co.uk | ] [ NTS: G7OMZ @ GB7VRB.#38.GBR.EU | -- Sycho ] [ Phone: +44 161 434 6492 | ] ------------------------------ From: Bart.Peirens@ping.be (Bart Peirens) Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc Subject: Re: Does Linux support (or will) RAID 5 drives and/or Hot plugged drives ? Date: Thu, 14 Dec 1995 17:34:23 GMT Pierre Blanchet wrote: >My question is in the title. > Thank you for your responses, Only with RAID controllers. Only stable choice at the moment is I think an DPT controller. There very good. (read the SCSI faq for more info) Within some time the new Adaptec 3xxx should also support raid, but no chaching. The DPT controllers also support caching :-) >-- >~ Pierre Blanchet Universite de Bordeaux I ~ >~ E-mail: blanchet@emi.u-bordeaux.fr ~ >~ WWW : http://www.emi.u-bordeaux.fr/~blanchet ~ >~~~~~~~~~Les poissons rouges dansent mal le menuet.~~~~~~~~~~~~~~ ------------------------------ From: Bruce Stephens Subject: Re: Transputer Linux? Date: Fri, 15 Dec 1995 14:40:35 GMT >>>>> "V" == V Guruprasad writes: > In article <4ap67o$86v@papaioea.manawatu.gen.nz>, > alan@papaioea.manawatu.planet.org.nz (Alan Brown) writes: |> I > noticed some Transputer files in the kernel area on Funet. |> |> > How far has Linux progressed for this platform, if it's being ported > to it? > Should be interesting. Transputers do their own thing with process > management.. Wonder if there have been any other Unix ports to > transputers already, and how they went about it? Depends what you mean by "Unix"! Parsis (I think) produce Idris, which is a Unix-like thing. It clearly works differently underneath, and that sometimes shows, but basically it feels like Unix. Chorus Systemes (sp?) were working on an operating system for transputers which was supposed to be Unix, but I don't know anything else about it. -- Bruce Institute of Advanced Scientific Computation bruce@liverpool.ac.uk University of Liverpool http://supr.scm.liv.ac.uk/~bruce/ ------------------------------ From: sbeer@ibm.net Subject: Re: 'make' fails on 1.3.47 Date: 15 Dec 1995 19:21:58 GMT Reply-To: sbeer@ibm.net I guess "Latest and Greatest" is a relative term. I noticed the new libc immediately after posting my message, and loaded: libc.5.2.18, ld.so.1.7.12, and patched BAD_GNU_LIBRARY in the make 3.73 sources per the patch in the libc release notes. And guess what.... *IT WORKS*!!! Thanks a lot for your prompt e-mail responses. Steve Beer ------------------------------ From: cshamis@erinet.com (C Shamis) Subject: Re: Tape drives that connect to floppy controller Date: 12 Dec 1995 16:54:18 GMT Reply-To: cshamis@erinet.com Dimitris Evmorfopoulos (devmorfo@patmos.interport.com) wrote: : Ian Chard (ian@tanagra.demon.co.uk) wrote: : : Hi, : : : I'm interested in buying one of these little cheap tape drives, and : : I was told by a friend that I needed to use ftape to make them work : : with Linux. However, in the latest kernel I couldn't find it - has : : it been removed, or just renamed? : : Neither... ftape is a separate package. It is called zftape and its : latest version is 2.03b or higher. It is a module. Actually, zftape v1.02 is the newest. (Novemeber 17th 1995), It would seem that zftape2.03b was supposed to be zftape1.00, but that got confusing with the ftape stuff being numbered exactly the same. Heck, here's the 1.02 changelog... ===================================================================== Thu Nov 16 22:35:40 1995 Claus-Justus Heine * qic80-vtbl.h: keep track of non-qic80 mode * qic80-vtbl.c: removed function qic80_fake_single_volume() * ftape-write.c: minor changes * ftape-rw.c: _write_segment() in ftape_verify_write_segment() now retries on -EAGAIN ftape_set_flags(): handle mixing of different devices, i.e. making a backup with one device and rewinding with another. * ftape-read.c: trace levels, minor changes * ftape-dynmem.c: change __qic80_vtbl to __qic80_real_vtbl Thu Nov 16 16:22:21 1995 Claus-Justus Heine * kernel-interface.c: set version in printk message to 1.02 Thu Nov 16 16:01:19 1995 Claus-Justus Heine * test_ioctl.c: added test for MTIOC_ZFTAPE_GETBLKSZ * qic80-vtbl.c: added global variable __qic80_file_no. Was declared static in an inline function. * qic80-vtbl.h: fixed another negative array index in qic80_check_for_eom * ftape-ctl.c: added special ioctl MTIOC_ZFTAPE_GETBLKSZ to let user query the blocksize of the current volume * ftape-ioctl.h: added special ioctl MTIOC_ZFTAPE_GETBLKSZ to let the user query the blocksize of the current volume * README.zftape: added documentation on non-standard ioctls * compress/lzrw3.c: commented out RCSid to prevent compiler warning * ftape-rw.c: added tracing information to ftape_verify_write_segment() Thu Nov 16 13:43:06 1995 Claus-Justus Heine * ftape-write.c: replaced _write_segment() with ftape_verify_write_segment() in function update_header_segments() * qic80-vtbl.c: replaced _write_segment() with ftape_verify_write_segment in function qic80_update_volume_table() * ftape-rw.h: added prototype for ftape_verify_write_segment() * ftape-rw.c: Added new function: ftape_verify_write_segment( unsigned segment, byte *buffer ); This is because all the function that write header segments need to write segments with verification (i.e. rereading them). * qic80-compress.c: changed _write_segment() in ftape_update_compression_segments() to newly created function ftape_verify_write_segment() * INSTALL: minor changes * README.zftape: Structured it a little more, wrote more blurb * ftape-write.c: Adjusted trace levels Thu Nov 16 03:43:05 1995 Claus-Justus Heine * compress/Makefile: "make clean" also removes .depend now * compress/lzrw3.c, compress/compress.h: added RCSid * ftape-read.c: Adjusted trace levels * ftape-rw.c: Adjusted trace levels Thu Nov 16 03:03:09 1995 Claus-Justus Heine * ChangeLog: Added Changelog to version control Thu Nov 16 00:53:07 1995 Claus-Justus Heine * fdc-io.c: Added second fdc_catch_stray_interrupts in fdc_init(). At least if the floppy module is not inserted there is one unexpected interrupt on my system * ftape-ctl.c, kernel-interface.c: Adjusted trace levels * tracing.c: Set default trace level to 3 * qic80-vtbl.c: Fixed a bug that revealed itself after adding the internal volume table buffer __qic80_vtbl to the dynamic memory allocation. __qic80_last_vtbl was sometimes set to &_qic80_vtbl[-1] which caused a segmentation fault. Wed Nov 15 19:54:06 1995 Claus-Justus Heine * qic80-compress.c: Adjusted trace levels, wrote some more comments * qic80-vtbl.h: Enabled dynamic allocation of __qic80_vtbl. * qic80-vtbl.c: renamed num_of_volumes to __qic80_num_of_volumes. Export variable for inline functions. Enable dynamic allocation of __qic80_vtbl. * qic80-compress.c: Adjusted trace levels a bit. * qic80-vtbl.c: qic80_check_for_eom qic80_find_file_no qic80_get_volume_block_size qic80_get_volume_size qic80_get_volume_cmpr_flag qic80_get_volume_boundaries Now declared as inline in qic80-vtbl.h. vtbl, last_vtbl renamed to __qic80_vtbl and __qqic80_last_vtbl. They are now exported for the inline functions. * qic80-vtbl.h: qic80_check_for_eom qic80_find_file_no qic80_get_volume_block_size qic80_get_volume_size qic80_get_volume_cmpr_flag qic80_get_volume_boundaries : changed them to be "static inline". Source code for these functions removed from qic80-vtbl.c * qic80-vtbl.c: Adjusted trace level and fixed typos. * qic80-compress.h: Fixed a typo. * qic80-compress.h: Changed a comment. * RELEASE-NOTES.zftape: Added version control (CVS). Wed Nov 15 16:55:49 1995 Claus-Justus Heine * Notes-On-ftape-2.03b/RELEASE-NOTES, Notes-On-ftape-2.03b/Install-guide, Notes-On-ftape-2.03b/README.PCI, compress/.depend, compress/Makefile, compress/compress.h, compress/lzrw3.c, qic80-compress.h, qic80-vtbl.c, qic80-vtbl.h, tracing.c, tracing.h, vendors.h: zftape-1.01 Kernel module driverfor a floppy streamer. Built on top of Bas Larhovens ftape-2.03b. Adds builtin compression (lzrw3) and uses a QIC-80 compatible volume table und compression map. * Notes-On-ftape-2.03b/RELEASE-NOTES: Initial revision * 00_read__README.zftape!!!!, README.zftape, RELEASE-NOTES.zftape, ftape-dynmem.h, ftape-eof.c, ftape-eof.h, ftape-io.c, ftape-io.h, ftape-ioctl.h, ftape-read.c, ftape-read.h, ftape-rw.c, ftape-rw.h, ftape-write.c, ftape-write.h, kernel-interface.c, kernel-interface.h, qic117.h, qic80-compress.c, test_ioctl.c: zftape-1.01 Kernel module driverfor a floppy streamer. Built on top of Bas Larhovens ftape-2.03b. Adds builtin compression (lzrw3) and uses a QIC-80 compatible volume table und compression map. * Notes-On-ftape-2.03b/Install-guide, Notes-On-ftape-2.03b/README.PCI, compress/.depend, compress/Makefile, compress/compress.h, compress/lzrw3.c, qic80-compress.h, qic80-vtbl.c, qic80-vtbl.h, tracing.c, tracing.h, vendors.h: Initial revision * Configure, Configure.skel, calibr.c, calibr.h, ecc.c, ecc.h, fc-10.c, fc-10.h, fdc-io.c, fdc-io.h, fdc-isr.c, fdc-isr.h, ftape-bsm.c, ftape-bsm.h, ftape-ctl.c, ftape-ctl.h, ftape-dynmem.c, ftape.h: zftape-1.01 Kernel module driverfor a floppy streamer. Built on top of Bas Larhovens ftape-2.03b. Adds builtin compression (lzrw3) and uses a QIC-80 compatible volume table und compression map. * 00_read__README.zftape!!!!, README.zftape, RELEASE-NOTES.zftape, ftape-dynmem.h, ftape-eof.c, ftape-eof.h, ftape-io.c, ftape-io.h, ftape-ioctl.h, ftape-read.c, ftape-read.h, ftape-rw.c, ftape-rw.h, ftape-write.c, ftape-write.h, kernel-interface.c, kernel-interface.h, qic117.h, qic80-compress.c, test_ioctl.c: Initial revision * COPYING, INSTALL, Makefile: zftape-1.01 Kernel module driverfor a floppy streamer. Built on top of Bas Larhovens ftape-2.03b. Adds builtin compression (lzrw3) and uses a QIC-80 compatible volume table und compression map. * Configure, Configure.skel, calibr.c, calibr.h, ecc.c, ecc.h, fc-10.c, fc-10.h, fdc-io.c, fdc-io.h, fdc-isr.c, fdc-isr.h, ftape-bsm.c, ftape-bsm.h, ftape-ctl.c, ftape-ctl.h, ftape-dynmem.c, ftape.h, COPYING, INSTALL, Makefile: Initial revision --- FIN --------------------------------------------- ------------------------------ From: Phillip G Ezolt Subject: Strip.. Why NOT use it? Date: Tue, 12 Dec 1995 15:53:56 -0500 I have a whole bunch of programs that I have compiled, and they are considered "unstripped". When I use the strip command on them, they get SIGNIFICANTLY smaller.. Why would I NOT want to use that command? Phil ------------------------------ From: peter@I_should_put_my_domain_in_etc_NNTP_INEWS_DOMAIN (Peter Hofmann) Subject: Re: Are libc functions MT-safe? Date: 11 Dec 1995 20:32:35 GMT Doug Kwan ~{9XUq5B~} (ctkwan@cs.hku.hk) wrote: : I am writing a multi-thread application on SGI. Irix has got a : very nice system call for threads called sproc. It just "forks" : off a new thread in the addressing space of the parent with : a newly allocated stack. Also, library functions like malloc are : MT-safe. Hi, as of libc version 5.2.16 threads are supported in the linux libc. You have to compile the shared pthreads library yourself because it is not included in the binary distribution of libc-5.2.16. Please read the file release.libc-5.2.16 for details. Documentation on the pthread API can be obtained from the author's home page: http://www.mit.edu:8001/people/proven/home_page.html. I have used the pthreads library for different projects quite successfully. Have fun, Peter ------------------------------ From: jonathan@talus.seas.ucla.edu (Jonathan Katz) Subject: Question -- Virtual Interfaces (network, multiple IP's) Exist? Date: Tue, 12 Dec 1995 21:09:02 GMT Hello... I was wondering if Linux supported Virtual Interfaces for tcpip? Something like the BSDI ifconfig --- alias perhaps? If there currently is no support for this, is it being worked on? Thanks, Jonathan jonathan@ucla.edu ------------------------------ From: koenig@tat.physik.uni-tuebingen.de (Harald Koenig) Crossposted-To: alt.satellite.tv.crypt Subject: Re: Linux ISO 7816 emulator (was: New Voyager) Date: 14 Dec 95 17:02:07 MET In <4ak81e$1e1@cortex.dialin.rrze.uni-erlangen.de> mskuhn@unrza3.dialin.rrze.uni-erlangen.de (Markus Kuhn) writes: > I find your CMOS clock tick generator idea much more attractive at the > moment. The MC14818A data sheet says that among other interrupt > frequencies, the CMOS clock can generate also 128 Hz (write 1001 into > the RS bits), which is close to 100 Hz and will simplify even some of > the adjtimex code, because now HZ is a power of two. > Common tick interrupts used today: > Linux 1.2 and SunOS: 100 Hz > Ultrix: 256 Hz > OSF/1. 1024 Hz > What do you think, how much effort would it be to make the CMOS chip > the tick generator and to change HZ from 100 to 128? no bad idea if this really works for *ALL* CMOS clock versions and the interrupt line isn't used for other hardware (which IRQ line is the CMOS clock connected to ? couldn't find anything in my PC docs). Harald -- All SCSI disks will from now on ___ _____ be required to send an email notice 0--,| /OOOOOOO\ 24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\ \ \/OOOOOOOOOOOOOOO\ \ OOOOOOOOOOOOOOOOO|// Harald Koenig, \/\/\/\/\/\/\/\/\/ Inst.f.Theoret.Astrophysik // / \\ \ koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^ ------------------------------ From: militia@sierra.net (Kevin Haddock) Crossposted-To: alt.os.linux,comp.os.linux.misc,comp.os.linux.hardware,comp.os.linux.setup Subject: Re: HELP: Compiling the Kernel: <<<<<< Segmentation fault >>>>>>> Date: 11 Dec 1995 06:47:47 GMT The Unix Mighty (bikesh@scus1.ctstateu.edu) wrote: : Hi, : I just got kernel 1.3.45 : Everytime I try to compile.. : BTW I have tried almost every 1.3.?? kernels : I get the same error.. on each and every one.. : The get this errors : ********************************************************************** : ld -m elf_i386 -r -o kernel.o ksyms.o sched.o dma.o fork.o : exec_domain.o panic.o printk.o sys.o module.o exit.o signal.o itimer.o : info.o time.o softirq.o resource.o : make[1]: *** [kernel.o] Segmentation fault (core dumped) : make[1]: *** Deleting file `kernel.o' : make[1]: Leaving directory `/usr/src/linux/kernel' : make: *** [linuxsubdirs] Error 2 : ********************************************************************** : Any help app.. : Thankx a bunch : Bikesh I think your problem is you are using too old of a copy of gcc. Either upgrade or turn off your elf binary support in the kernel when you do make config. That will turn off the -m elf_i386 option in the ld and that should do it. G'luck -Kevin ------------------------------ From: ldaffner@convex.com (Larry Daffner) Subject: Re: Strip.. Why NOT use it? Date: 12 Dec 1995 16:27:24 -0600 In <0knSjY_00Von0QCXxc@andrew.cmu.edu> Phillip G Ezolt writes: >I have a whole bunch of programs that I have compiled, and they are >considered "unstripped". When I use the strip command on them, they get >SIGNIFICANTLY smaller.. Why would I NOT want to use that command? >Phil What strip does is removes all the symbol location info from the executable. The only time this comes into play is when you're firing up a debugger, usually. It's the information gdb et. al. use to find out what line/function/file a certain address in the program relates to. If you plan on debugging the programs in question, it's propbably not a bad idea to leave the program unstripped. On the other hand, if you DON'T plan to debug the program, there's little sense in not stripping the program. HTH -Larry -- Larry Daffner - Software Engineer | email: ldaffner@convex.com | Convex Computer Corporation | tel: (214)497-4274 / home: (214)380-4382 | Hare's Law: Inside every large program is a small program struggling to get out. ------------------------------ From: mark@tie.missouri.edu (Mark Donnelly) Crossposted-To: comp.os.linux.setup,comp.os.linux.networking Subject: Re: Login Accounting in Linux Date: 16 Dec 1995 02:35:23 GMT Well, since no one else seems to want to answer this, I guess I will :) >Hi there, > >I am looking for login accounting packages or programs for Linux so that >I can monitor who has logged into my system and for how long. If anyone >knows of software that does this, please leme know. Thx in advance. > Try the command "last" (you should probably pipe it thru less or more). This should come with any linux (or UN*X for that matter) installation. This will pipe out the last people to login, ususally starting with the most recent. --Mark "How may I be honest with you today?" Tuvok, ST:VOY ------------------------------ From: asav@ix.netcom.com (Amit Chatterjee) Crossposted-To: comp.os.linux.setup,comp.os.linux.hardware Subject: Re: Does Colorado work with Linux at all? Date: 13 Dec 1995 00:29:53 GMT In article <4ak7tm$akd@pentagon.io.com>, mskc@io.com (Casey Claiborne) writes: >Hello, > I am trying to get a Colorado 700 tape drive to work under >Linux 1.2.1.I compiled new module code (I used the "C" and ".h" >files that were part of the "modules" directory that came with newest >version of ftape that is on sunsite. I also retrieved the newest version >of "modules" located on sunsite. > Everything seemed to compile OK. I was also able to >do the test for "insmod" and that seemed to go pretty well. I then >tried "insmod ftape.o" that seemed to be OK. > > I then typed, "mt -f /dev/rft0 rewind" - I received *no* >messages whatsoever - no error or other type of messages. The >documentation also says to look at error messages genearted by syslogk. >Unfortunately, I do not have this. > > Where can I locate "syslogk"? Although I get no error messages, >when I try to contiue the test, typing "mt -f /dev/ftape reten", I get >an error message of > > "/dev/ftape retension 1 failed: Timer expired" > >I would be *grateful* for *any* type of help with this matter. > I got exactly the same behaviour with the Ditto 800 Ftape drive. But I managed to take a backup and restored a few sample files to test if the backup went alright. It worked without any problems. So, I think the timer values is bit small (for retension of a tape as big as 400MB) and it is not a serious problem. BTW, the retension went fine inspite of the error message. If I am wrong and there is a serious problem, would someone let me know, please. Amit Chatterjee ------------------------------ ** 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-System-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.development.system) via: Internet: Linux-Development-System@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-System Digest ******************************