From:     Digestifier <Linux-Development-Request@senator-bedfellow.mit.edu>
To:       Linux-Development@senator-bedfellow.mit.edu
Reply-To: Linux-Development@senator-bedfellow.mit.edu
Date:     Thu, 12 May 94 06:13:05 EDT
Subject:  Linux-Development Digest #713

Linux-Development Digest #713, Volume #1         Thu, 12 May 94 06:13:05 EDT

Contents:
  Format for Unix Binaries (rt@astro.ocis.temple.edu)
  Re: Compressed filesystem??? (Bill C. Riemers)
  Re: Stargate Plus 8 card supported! (vir@45acp.slip.com)
  Re: New kernel introduces gawk bug? (Rene COUGNENC)
  Re: CD-ROM's do all read and write now? (Elaine Walton)
  Re: UUGETTY ( smart ring ) (Gert Doering)
  Re: Source for Mosaic 2.4 with Term Support? (Steven Drinovsky)
  Re: 1.1.12:net/net.o: Undefined symbol _rarp_ioctl referenced from text seg (Christian Nelson)
  Re: Network File Server and 8 Workstations? Hardware Neede? (Charles B. Robey)
  Re: Linux CD-ROMs? (Brandon S. Allbery)
  Re: [Announcement] 386BSD Release 1.0 (Clarence Dold)
  Adaptec 1542C (Tom Briggs)
  Re: Compressed filesystem??? (Jim Graham)

----------------------------------------------------------------------------

From: rt@astro.ocis.temple.edu (rt@astro.ocis.temple.edu)
Crossposted-To: comp.os.linux.misc,comp.os.lynx,de.comp.os.linux
Subject: Format for Unix Binaries
Date: 11 May 1994 16:44:29 GMT


   What is the format of a UNIX binary? Are binaries for a particular
processor compatible between flavors of UNIX. I mean in terms of
migrating the binary from say.. SCO to Linux and such.

--
My opinion does not reflect that of Temple U. This is because it is made 
up of a non-reflective material. 

------------------------------

From: bcr@k9.via.term.none (Bill C. Riemers)
Subject: Re: Compressed filesystem???
Date: 11 May 94 16:35:37 GMT
Reply-To: bcr@physics.purdue.edu

In article <1994May8.134959.16508@n5ial.mythical.com> jim@n5ial.mythical.com (Jim Graham) writes:
   I've never tried this one (but I might!).  How fast is it?  Do you have to
   recompile everything?  Or does it work with existing binaries (that aren't
   statically linked)?

No, I haven't had to recompile anything, except itself when I upgrade shared
libraries.  Once you get it configured right, it is not a significant factor
in figuring out how fast you can access data on your disk...  Needless to say
you can't compress executables this way, so for those I use "tcx".  There is
a small script I wrote called "GZip" that automatically determines what to
compress.  So I can do things like:

  GZip -r /

Likewise

  Gunzip -r /

restores everything.


   there is also a third option which, btw, is the one I use.  Some time ago,
   there appeared a util called gexe.  I think it was posted to one of the
   comp.sources.* groups, but I'm not sure.  Anyways, it allows you to
   compress binaries.  It compresses the real binary and makes a /bin/sh
   header at the top that uses zcat (or perhaps gunzip) to uncompress the
   binary part into /tmp/[program_name], and then execs the uncompressed
   binary in /tmp.  It's slow, but it works....  I hacked it up just a bit
   so that it gives the message ``Uncompressing binary....'' as it loads.

Yes, if you look on tsx-11.mit.edu you'll find the "csh" version I wrote about
two years ago of "gexe".  I still use it under "TitanOS", but if you are 
going to be compressing a large # of executables, you'll find "tcx" is the
better choise.  However, the typical Linux system has less than 30% of the 
disk space taken by executables...

                              Bill

Requires ZLIB version 0.4a or greater.  ftp.imag.fr:pub/ZLIBC/
Requires tcx, gzip, gunzip, find
 
==============================================================================
For those interested here is the GZip script:

#!/bin/csh -fb
# This program is copyright 1993 by Bill C. Riemers, under the same terms of
# gzip.  If this is to restrictive, let me know and I will consider relaxing
# it.  (bcr@physics.purdue.edu, bcr@cernapo.cern.ch)
setenv ZLIB_DISABLE 1
setenv PROGRAM "$0"
setenv OPTIONS "$argv:q"

set noglob = ( )

# Put explicit paths here.  I'm not sure if this will work with other programs.
set gzip_data   = ( gzip  )
set ungzip_data = ( gunzip )
set compress_exec   = ( tcx )
set uncompress_exec = ( untcx -u )

# What is the smallest size file you wish to compress in kilobytes
@ minsize = 5 

# Filenames to always exclude (things that you are constantly using...
# or things that aren't any smaller when compressed.)
# There is no need to list suid programs.  Wildcards are permitted.
set exclude = ( \
        vmlinuz vmlinuz.* zSystem.map zImage emacs lemacs fvwm \
        xinit getty selection uugetty syslogd oclock \
        *.Z *.gz *.tgz *.taz *.tpz *.gif \
        )

# We can also exclude directories and paths ...
# I like to exclude temporary files and everything needed for booting.
set path_exclude = ( \
        /tmp/* /mnt/* /boot/* /sbin/* /bin/* /etc/* */app-defaults/* \
        /usr/spool/* /usr/TeX/lib/tex/fonts \
        )

# Default extention
set suffix = .GZ


# The rest of this is the script.

if ! $?ZLIB_SUFFIX setenv ZLIB_SUFFIX $suffix
set goto = $PROGRAM
set options = ( --suffix "$ZLIB_SUFFIX" )
set files = ( )
set files_GZ = ( )
set files_NO_GZ = ( )
set maxdepth = ( -maxdepth 0 )

process_arguments:
foreach option ( $OPTIONS )
  if ! ( $?add_next_option ) then
    if( "X$option:q" =~ "X-"* & ! $?expression ) then
      if ( "X$option:q" =~ X--* ) then
        switch ( "X$option:q" )
          case X--suffix:
            set add_option = ( )
            set add_next_option = ( )
            breaksw
          case X--ascii:
          case X--force:
          case X--list:
          case X--no-name:
          case X--name:
          case X--quiet:
          case X--verbose:
          case X--fast:
          case X--best:
            set add_option = ( )
            breaksw
          case X--decompress:
          case X--uncompress:
            set goto = Gunzip
            breaksw
          case X--stdout:
          case X--to-stdout:
          case X--license:
          case X--test:
            if ( $goto == GZip ) exec $gzip_data --suffix "$ZLIB_SUFFIX" $argv:q
            exec $ungzip_data --suffix "$ZLIB_SUFFIX" $argv:q
            breaksw
          case X--recursive:
            set maxdepth = ( )
            breaksw 
        endsw
      else
        if ( "X$option:q" == X-*d* ) then
          set goto = Gunzip
        endif
        if ( "X$option:q" =~ X-S* ) then
          set add_option = ( )
          goto break_option
        endif
        if ( "X$option:q" =~ X-*[aflnNq,0-9]* ) then
          set add_option = ( )
        endif
        if ( "X$option:q" =~ X-*[cLt]* ) then
          if ( $goto == GZip ) exec gzip --suffix "$ZLIB_SUFFIX" $argv:q
          exec gunzip --suffix "$ZLIB_SUFFIX" $argv:q
        endif
        if ( "X$option:q" =~ X-*r* ) set maxdepth = ( )
      endif
    else
      if ( -d "$option:q" ) then
        set files = ( $files:q `cd "$option:q";echo -n "$PWD"` )
        set files_GZ = ( $files_GZ:q `cd "$option:q";echo -n "$PWD"` )
        set files_NO_GZ = ( $files_NO_GZ:q `cd "$option:q";echo -n "$PWD"` )
      else
        if ( -x "$option:q" ) then
          set files = ( $files:q "$option:q" )
        endif
        if ( ".$option:e" == "${ZLIB_SUFFIX}" && -e "$option:r" ) then
          set files_NO_GZ = ( $files_NO_GZ:q "$option:r" )
        else if ( -e "$option:q" ) then
          set files_NO_GZ = ( $files_NO_GZ:q "$option:q" )
        endif
        if ( -e "$option:q${ZLIB_SUFFIX}" ) then
          set files_GZ = ( $files_GZ:q "$option:q${ZLIB_SUFFIX}" )
        else if ( ".$option:e" == "${ZLIB_SUFFIX}" ) then
          set files_GZ = ( $files_GZ:q "$option:q" )
        endif
      endif
      unset expression 
    endif
  else
    set add_option = ( )
    unset add_next_option
  endif

break_option:

  if $?add_option then
    set options = ( $options:q $option:q )
    unset add_option
  endif
end

minimum_size:
set sizes = ( -not -empty -not -size 1k )
while ( $minsize > 1 )
  set sizes = ( $sizes -not -size "$minsize"k )
  @ minsize--
end

excluded_files:
set exclude_files = ( )
foreach  file ( lib*.so.* lib*.so g{,un}zip zforce zcat $compress_exec[1]:q $unc
ompress_exec[1]:q $exclude:q )
  set exclude_files = ( $exclude_files -not -name $file )
end
                      
exclude_dirs:
set exclude_dirs = ( )
foreach dir ( /tmp/* $path_exclude )
  set exclude_dirs = ( $exclude_dirs -not -path $dir )
end


if ( $goto:t == GZip ) then
  if ( $#files_NO_GZ != 0 ) then
    find $files_NO_GZ:q $maxdepth -type f -not -perm +7111 \
      -not -name "*${ZLIB_SUFFIX}" -not -name ".*" \
      $sizes $exclude_files:q $exclude_dirs:q -links 1 -not -fstype proc \
      -not -fstype iso9660 -not -fstype msdos \
      -exec $gzip_data:q $options:q '{}' ';'
  endif
  if ( $?compress_exec && $#files != 0) then
    find $files $maxdepth -type f -perm +111 -not -perm +7000 \
      $sizes $exclude_files:q $exclude_dirs:q -links 1 -not -fstype proc \
      -not -fstype iso9660 -not -fstype msdos -not -name .* \
      -not -name lib*.so -not -name lib*.so.* -not -name ld.so \
      -exec $compress_exec:q '{}' ';' |& grep -v 'in tcx format. Aborting'
  endif 
  exit 0
else if ( $goto:t == Gunzip ) then
  if ( $#files_GZ != 0 ) then
    find $files_GZ:q $maxdepth -type f -not -perm +7000 \
      -name "*${ZLIB_SUFFIX}" \
      -not -empty $exclude_files:q $exclude_dirs:q -links 1 -not -fstype proc \
      -not -fstype iso9660 -not -fstype msdos \
      -exec $ungzip_data:q $options:q '{}' ';'
  endif
  if ( $?uncompress_exec && $#files != 0) then
    find $files $maxdepth -type f -perm +111 -not -perm +7000 \
      -not -empty $exclude_files:q $exclude_dirs:q -links 1 -not -fstype proc \
      -not -fstype iso9660 -not -fstype msdos -not -name .* \
      -not -name lib*.so -not -name lib*.so.* -not -name ld.so \
      -exec $uncompress_exec:q '{}' ';' |& grep -v 'in tcx format. Aborting'
  endif
  exit 0
endif
exit 1



------------------------------

From: vir@xmission.com (vir@45acp.slip.com)
Subject: Re: Stargate Plus 8 card supported!
Date: 10 May 1994 03:18:18 GMT

        Mail bounced, so sorry for the post.

Sean Puckett (nate@loreli.ftl.fl.us) wrote:
: So, anyway, I put the card in my Linux box and told it where the UART's lived,
: and what the common interrupt line was, and Lo and Behold, it worked.  Amazing.
: It turns out you don't need a special driver for the Plus 8, because  it works
: just fine as a group of eight UARTS all tied to a common interrupt line (in
: my case, IRQ 2/9).

: All you have to do is use setserial to set up the port addresses, uart type
: (16450) and irq address (same for all eight ports) and it works just fine.
: I'd tell you my port address, but they're non-standard, as this card is oem.

: I suggest the keepers of the FAQ's add this bit of information to the FAQ's,
: because when I checked the hardware compatibility list and didn't see a Plus 8,
: I kinda paniced.

: More details?  Send mail!


: --
:                        ..:: nate@loreli.ftl.fl.us ::..
:              ..:: Sean Puckett - Albino Frog Software, Inc. ::..
:           ..:: The Right Reverend Aural Hardly, MSK, BoC, FCoC ::..

Please email me details on setup.  I have 2 of these from SCO days and
are just collecting dust...  Maybe now is a good time to revive them.

Thanks for the info,

CUL,
vir
--
    _/_/_/  _/      _/  _/_/_/   Salt Lake Internet Project(tm)
   _/      _/      _/  _/    _/  y.a.c.c.  : Vir Lagua, Jr.
  _/_/_/  _/      _/  _/_/_/     voice     : 801.571.5602
     _/  _/      _/  _/          data / fax: 801.571.2020
_/_/_/  _/_/_/  _/  _/           email     : vir@xmission.com
  


------------------------------

From: rene@renux.frmug.fr.net (Rene COUGNENC)
Subject: Re: New kernel introduces gawk bug?
Date: 9 May 1994 20:18:09 GMT
Reply-To: cougnenc@hsc.fr.net (Rene COUGNENC)

Ce brave Kevin Haddock ecrit:


> Here is how it is reproduced:
> > find / -print | awk ' { "echo " $1 | getline fubar; print fubar }'
> > 
> > I get about 90 lines of output then it says:
> > awk: cmd. line:1: (FILENAME=- FNR=91) fatal: cannot fork for "echo
>       /usr/X11/lib/fonts/75dpi/courB08.pcf.Z" (Try again)
> >Broken pipe

> Does anyone have a newer kernel running under SLS or debian they could
> try this line out on?

No problem on my system, running gawk 2.13pl2, gnu find 3.7,  under Linux 
1.1.12 (+ new tty drivers), bash 1.12  and libc 4.5.26.

--
 linux linux linux linux -[ cougnenc@renux.frmug.fr.net ]- linux linux linux 

------------------------------

From: ewalton@magnus.acs.ohio-state.edu (Elaine Walton)
Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix
Subject: Re: CD-ROM's do all read and write now?
Date: 10 May 1994 03:28:59 GMT

I am guessing that you are talking about WORM or WMRM drives.  Generally,
most CD drives are _ReadOnly_, because the laser is not powerful enough to
twittle the bits.  Furthermore, all CDs are designed in such a way to make
it impossible to modify them.
WORM (Write-Once-Read-Many) are about $2800-$6500 each with read/write disks
costing from $55-$75 a whack.  WMRM (Write-Many-Read-Many) drives similar in
price (between $5000 and $11000) with disks costing from $250 each.
I believe it will be a while before we see these prices come down.

-Sean

------------------------------

From: gert@greenie.muc.de (Gert Doering)
Subject: Re: UUGETTY ( smart ring )
Date: Tue, 10 May 1994 21:53:39 GMT

gordon@tradenet.tradenet.com (Gordon Soukoreff) writes:

>Anyone doing work on the TELCO's smart or distinctive ring feature for
>uugetty and friends ?

If your modem supports it (all that I know of are ZyXELs), you can try
mgetty or, more precise, vgetty. It has already some hooks in it, though
I'm not absolutely satisfied with the implementation yet.

gert
-- 
I've got a signature breakdown! Anybody got a spare one?

Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-3243328                         gert.doering@physik.tu-muenchen.de

------------------------------

From: stevend2@cs.utexas.edu (Steven Drinovsky)
Subject: Re: Source for Mosaic 2.4 with Term Support?
Date: 9 May 1994 22:48:37 -0500


Well, I found Mosaic 2.4 ( I grepped xmosaic and missed it the first
time).  Just incase someone else has the same problem, it was on
nic.funet.fi:/pub/OS/Linux/util/X11/contrib/mosaic/Mosaic-2.4.bin.tar.gz

Sorry for the waste of band width :)

Later,
Steven

-- 
Your superior intelligence is no match for our inferior weapons!


------------------------------

From: cnelson@csugrad.cs.vt.edu (Christian Nelson)
Subject: Re: 1.1.12:net/net.o: Undefined symbol _rarp_ioctl referenced from text seg
Date: 9 May 1994 23:41:52 -0400

Add 'rarp.o' to the list of objects (OBJS) in the Makefile under
linux/net/inet/.

That fixed it for me...


-- 
Christian                                                          Virgina Tech
cnelson@csugrad.cs.vt.edu                                      Computer Science

------------------------------

From: chuckr@glue.umd.edu (Charles B. Robey)
Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.misc
Subject: Re: Network File Server and 8 Workstations? Hardware Neede?
Date: 10 May 1994 03:37:49 GMT

Brian Fritz/ ADVISOR Russell (MAE) (rme81977@zach.fit.edu) wrote:
: Our company is looking to build a 8 to 10 person network, which is to
: include a server and 8/10 workstations.  Does anyone have any suggestions
: for hardware and software?
: Thanks in advance
: -Brian
Do you have any limitations that are set in stone, such as the boss
madly in love with a DOS application, or something like that?

--
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
7608 Topton St.             |
New Carrollton, MD 20784    |
(301) 459-2316              |
============================+===============================================

------------------------------

From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: Linux CD-ROMs?
Date: Tue, 10 May 1994 02:37:32 GMT

In article <1994May9.171727.2308@phavl.uucp>, rob@phavl.uucp (Rob Ransbottom) says:
+---------------
| Running off of a CD doesn't sound like much fun.  Slow. A good 
| way to get a taste of linux for the unix newbie, though.  
+------------->8

It can be a lifesaver if you can afford $30 for a CD but not $500 or more for
a large hard drive.  (Which doesn't apply to me, BTW; I still have a spare
unused partition, even! :-)

You can run off the Trans-Ameritech CD; it has a full working Slackware system
on it, including a lot of goodies in place and ready to run.

++Brandon
-- 
Brandon S. Allbery         kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
The FUDs at Microsoft are shouting "Kill The Wabi!"

------------------------------

Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.misc
From: dold@rahul.net (Clarence Dold)
Subject: Re: [Announcement] 386BSD Release 1.0
Date: Mon, 9 May 1994 04:06:00 GMT

Tim Smith (tzs@u.washington.edu) wrote:

: 0x80.  The system would then boot from it.  Heck, if the people who wrote
: the host adaptor firmware wanted to, they could support booting from a
: scanner...

Odd that you should mention that particular peripheral.  Urban legend at
Unisys indicates that a particular BIOS would indeed attempt a boot from a
scanner.  Or at least it would read some info from it ;-)

-- 
---
Clarence A Dold - dold@rahul.net
                - Milpitas (near San Jose) & Napa CA.

------------------------------

From: tbriggs@cutter.ship.edu (Tom Briggs)
Subject: Adaptec 1542C
Date: 9 May 1994 05:49:37 GMT

I 've got the same controller, and I had similar problems, and the problem 
was termination.  That is SCSI's biggest problem (in my opinion).  Anyway,
what I finally had to do was enable the terminator on the controller,
disable the terminator on my hard drive, and take the SCSI cable, chop off
the end of it, and order a 50-pin ribbon to Centronics 50pin connector, 
mount that on the end of the cable, and then take a standard 50 pin 
external drive terminator and put that on the end of the cable.  It isn't
pretty, but it worked.  I can't take credit for the design either... I 
copied the cable from a MIPS 4000

You can easily tell if you have the same problem,  run Norton Disk Doctor
or some other surface sacnner, and if it tells you "Close drive door" or
some other nonsense like that, try making this cable, it'll probably save
you a lot of headaches.

tom

------------------------------

From: jim@n5ial.mythical.com (Jim Graham)
Subject: Re: Compressed filesystem???
Date: Sun, 8 May 1994 13:49:59 GMT

In article <BCR.94May5192208@k9.via.term.none> bcr@physics.purdue.edu writes:

>still no compressed file system.  There are two tools available:
>
>   1. DOUBLE --> This is a patch available that allows you to create
>      compressed file partitions.

Like you, I'm a bit nervous about this.  I seem to recall that it was only
an alpha version (though I could be way off here).  Anyways, I think that's
what scared me away from it.  (I don't mind playing with alpha levels of a
lot of stuff...but my filesystem?  no.)

>   2. zlibc --> This is a patch for libc that allows you to use readonly
>      compressed files.  (Use the latest version, not the one on sunsite!)

I've never tried this one (but I might!).  How fast is it?  Do you have to
recompile everything?  Or does it work with existing binaries (that aren't
statically linked)?

There is also a third option which, btw, is the one I use.  Some time ago,
there appeared a util called gexe.  I think it was posted to one of the
comp.sources.* groups, but I'm not sure.  Anyways, it allows you to
compress binaries.  It compresses the real binary and makes a /bin/sh
header at the top that uses zcat (or perhaps gunzip) to uncompress the
binary part into /tmp/[program_name], and then execs the uncompressed
binary in /tmp.  It's slow, but it works....  I hacked it up just a bit
so that it gives the message ``Uncompressing binary....'' as it loads.

Like I said, though, it's slow.  It takes time to uncompress the binary,
and during that time, you're asking yourself if it was really worth the
space savings (I have no choice).  Therefore, this option is best used only
on stuff that you don't normally use, and that takes up large amounts of
space.  I also kept the originals on floppies---that proved to be a wise
choice when I decided to revert back to the originals on a few things.  :-)

Oh, btw, the machine here is a 20 MHz 386 w/ 6 Meg of RAM---the above
option might be fast enough to not care about on faster machines...I
wouldn't know about that, though.  :-(

One simple test, to give a bit of data:

    /usr/local/bin/xc, compressed with gexe:
       *) original size:  54276
       *) compressed size: 27512
       *) normal version loads almost instantly (as one would expect)
       *) compressed version loads in roughly 2.5 seconds

Later,
   --jim

--
73 DE N5IAL (/4)                           < Running Linux *1.00*! >
      jim@n5ial.mythical.com                 ICBM: 30.23N 86.32W
  ||  j.graham@ieee.org          Packet:  N5IAL@W4ZBB (Ft. Walton Beach, FL)
E-mail me for information about KAMterm (host mode for Kantronics TNCs).


------------------------------


** 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
******************************
