[0459] daemon@ATHENA.MIT.EDU (Digestifier)  Linux Digest Archive  06/12/92 20:30 (565 lines)
Subject: Linux-Activists Digest #281
From: Digestifier <Linux-Activists-Request@BLOOM-PICAYUNE.MIT.EDU>
To: Linux-Activists@BLOOM-PICAYUNE.MIT.EDU
Reply-To: Linux-Activists@BLOOM-PICAYUNE.MIT.EDU
Date:     Fri, 12 Jun 92 20:30:11 EDT

Linux-Activists Digest #281, Volume #2           Fri, 12 Jun 92 20:30:11 EDT

Contents:
  Re: No ./local/. please (Darren Senn)
  GNU tar dies on multi-volume archive.  Help. (Joel M. Hoffman)
  Re: DOS convertees (Michael L. Cole)
  Re: UK ftp sites (Tony Travis)
  Re: GNU tar dies on multi-volume archive.  Help. (Rick Sladkey)
  Re: mtools question (Werner Almesberger)
  Re: power storms? (Anthony Lovell)
  How much do you need to install Linux (Glenn T Jayaputera)
  Re: GNU tar dies on multi-volume archive.  Help. (Joel M. Hoffman)
  bus mice (Rob Coleman)
  How to fix HD I/O errors (Duperval Laurent)
  Linux and Me II (Craig Burley)
  Re: How much do you need to install Linux (Chris Flatters)
  Re: Linux and Me II (Craig Burley)
  Re: MCC Interim Release (A. V. Le Blanc)
  Re: current version of joe? (A. V. Le Blanc)

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

From: sinster@tioga.ucsc.edu (Darren Senn)
Subject: Re: No ./local/. please
Date: 12 Jun 92 19:02:49 GMT
Reply-To: sinster@scintilla.capitola.ca.us

In article <1992Jun11.141818.2785@serval.net.wsu.edu>, hlu@yoda.eecs.wsu.edu (H.J. Lu) writes:
> I saw people use "./local/" while porting softwares to Linux. Can we
> just drop "./local/"? Linux is built from scratch. All those godd
> things should not be in "./local/". They belong to /usr/lib and
> /usr/bin. Unless you think it may not belong to Linux, please drop
> "./local/".

Why not?  In my mind, /bin is for basic UNIX utilities; /usr/bin is for
other unix utilities, text editors, and other simple packages; and
/usr/local/bin is for more complex packages: TeX, vgrind, webster, groff
(et. al.), rn, etc.

Besides: this let's me have the same .login/.cshrc at home that I have
on campus. :)

-- 
Darren Senn                                            Phone:    (408) 479-1521
sinster@scintilla.capitola.ca.us                       Snail: 1785 Halterman #1
Wasurenaide -- doko e itte mo soko ni anata wa iru yo.     Santa Cruz, Ca 95062

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

From: joel@wam.umd.edu (Joel M. Hoffman)
Subject: GNU tar dies on multi-volume archive.  Help.
Date: Fri, 12 Jun 1992 19:29:48 GMT

I'm trying to backup my /acc partition, using the following:

        tar +listed-incremental /etc/backup/full.acc +verbose +create
         +multi-volume +tape-length 1400000 +compress +one-file-system
         +file /dev/a: /acc/

(it's all on one line, of course).
        
but it dies before the end of the first disk with:

        tar (child): only wrote 0 of 10240 bytes to /dev/a:
        acc/joel/letters/personal/mike525.tex
        acc/joel/letters/personal/mike525.dvi

What's going on?  I purposely used tape-length 1400000, which is a
little less than 1440000, because I know there have been some problems
reading the last bit of floppies.  Any ideas?

``Tar +version'' tells me GNU tar version 1.10.  This is /not/ the
buggy tar distributed with 0.95; it untars gcc without a problem.  I'm
running 0.96 with the first patch applied.

-Joel
(joel@wam.umd.edu)Newsgroups: comp.os.linux



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

From: mlcole@nevada.edu (Michael L. Cole)
Subject: Re: DOS convertees
Date: 12 Jun 92 20:35:11 GMT

hello,

     i just heard about Linux thru our new systems guru and don't know the
first thing about it.  where can i find the FAQ for this news group?


                                                regards -- mlcole

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

From: ajt@puffin.doc.ic.ac.uk (Tony Travis)
Subject: Re: UK ftp sites
Date: 12 Jun 92 20:09:12 GMT

J.Jagger@sheffield-city-poly.ac.uk writes:
: Is there an up to date list of all the UK ftp sites that have Linux?
: 
: The reason I ask is that I have been unable to get any response from
: mcc (my usual site) for a couple of days now. Has anyone had the same
: problem?

Well, there is doc.ic.ac.uk:/public/os/Linux which is a mirror of nic.

Unfortunately, the contents have vanished recently, and Lee has gone to
Usenix ...  I recently asked him to enable mirror deletes because the
mirror contained lots of old versions of files and was very confusing.

It was working fine until a few days ago, and I ftp'ed the 0.96a/0.95c
boot/root + other things including Taylor uucp.

Since the Linux mirror has vanished (temporarily) I pulled the actual
Gnu distribution of taylor-uucp-1.03.tar.Z and discovered that the
version at nic is a *beta* version of 1.03.  The configure script, in
particular, now works under linux (you need "tr") except for minor
problems like "set +u".

Note the _news_ archive is still accessible as:

        doc.ic.ac.uk:/public/usenet/comp.os.linux
        doc.ic.ac.uk:/public/usenet/alt.os.linux        (now frozen)

and there are relevant articles in:

        doc.ic.ac.uk:/public/usenet/comp.os.minix

        Tony

--
    Tony Travis <ajt@uk.ac.sari.rri>  | Dr. A.J.Travis 
                                      | Rowett Research Institute,
                                      | Greenburn Road, Bucksburn, Aberdeen,
                                      | AB2 9SB. UK. tel 0224-712751

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

From: mvjrs@mviae.ATT.COM (Rick Sladkey)
Subject: Re: GNU tar dies on multi-volume archive.  Help.
Date: 12 Jun 92 22:00:18 GMT

>>>>> On Fri, 12 Jun 1992 19:29:48 GMT, joel@wam.umd.edu (Joel M. Hoffman) said:

Joel> I'm trying to backup my /acc partition, using the following:

Joel>   tar +listed-incremental /etc/backup/full.acc +verbose +create
Joel>    +multi-volume +tape-length 1400000 +compress +one-file-system
Joel>    +file /dev/a: /acc/

GNU tar texinfo file says: +compress is incompatible with +multi-volume.  Sorry.
--
Rick Sladkey
mvjrs@mviae.ATT.COM

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

From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Subject: Re: mtools question
Date: Fri, 12 Jun 1992 20:56:57 GMT

In article <1992Jun12.130443.7186@ncsu.edu> jlnance@eos.ncsu.edu (JAMES LEWIS NANCE) writes:
> There are two types of links, hard and symbolic.  You may use either one of
> them.

Hard links have the advantage that they only occupy an inode each while
symbolic links additionally consume one disk block (1kB). Thus, using hard
links for Mtools saves up to 14 kB of disk space. Accessing a file by a
hard link is also marginally faster than by a symbolic link.

The big disadvantages of hard links are that they're limited to the same
file system (this isn't a problem for Mtools) and that you really have to
look close to notice that they're not copies of the file. Some archiving
tools (e.g. some tars) aren't smart enough to detect hard links and they
happily include multiple copies of the same file in their archive.

- Werner
-- 
   _________________________________________________________________________
  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
 / IFW A44  Tel. +41 1 254 7213                 almesberger@rzvax.ethz.ch /
/_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/

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

From: alovell@cix.compulink.co.uk (Anthony Lovell)
Subject: Re: power storms?
Date: 12 Jun 92 22:39:00 GMT
Reply-To: alovell@cix.compulink.co.uk

In-Reply-To: <1992Jun9.040900.23664@athena.mit.edu> jgifford@attmail.com

TITLE: power storms?

In <1992Jun9.040900.23664@athena.mit.edu>
jgifford@attmail.com writes

> 
> I leave my machine up all the time, but there is a storm coming, and I am shutting 
down.
> 
> My question is, what does everyone else do?  leave it on, or turn it off over
> night?
> what if a storm comes, and you are unable to shut down?  (out of town maybe?)
> 
> later(after the storm)
> Jim Gifford
> jim@raskol.attmail.com
> jgifford@attmail.com

On Monday approx 14:50 GMT  we suffered lightning damage
I lost a modem and hard disk controller
Telecom lost a lot of cable
neighbours lost TV's VCR's Telephones and a private telephone exchange
that combined with power cuts totaling 22hrs out of 48hrs
The neighbour with the private exchange didn't get a working phone
system until Friday Afternoon (4 temp lines) ,he spent the week trying
to run a wholesale florists on radio telephones

--
Anthony Lovell                     |Itinerant Hackers of the World Unite
                                   |
alovell@cix.compulink.co.uk        |

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

From: gtj@goanna.cs.rmit.oz.au (Glenn T Jayaputera)
Subject: How much do you need to install Linux
Date: 12 Jun 92 16:36:44 GMT

Hi...I am wondering:
1. How much disk space do you need to install linux
2. Which one is better Coherent 4.0 or linux (or this is not a fair
   comparison)

Thanks so much
Glenn Jayaputera

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

From: joel@wam.umd.edu (Joel M. Hoffman)
Subject: Re: GNU tar dies on multi-volume archive.  Help.
Date: Fri, 12 Jun 1992 22:16:20 GMT

In article <MVJRS.92Jun12170018@mviae.ATT.COM> mvjrs@mviae.ATT.COM (Rick Sladkey) writes:
>>>>>> On Fri, 12 Jun 1992 19:29:48 GMT, joel@wam.umd.edu (Joel M. Hoffman) said:
>
>Joel> I'm trying to backup my /acc partition, using the following:
>
>Joel>  tar +listed-incremental /etc/backup/full.acc +verbose +create
>Joel>   +multi-volume +tape-length 1400000 +compress +one-file-system
>Joel>   +file /dev/a: /acc/
>
>GNU tar texinfo file says: +compress is incompatible with +multi-volume. Sorry

I'm sorry too.  (That's just like FSF, hiding important information in
the documentation.... :-))

Does anyone have a convenient way of doing what I'm trying to do?
Will

        tar +compress +file - /acc/ | tar +multi-volume +file /dev/a:

work (obvious flags omitted, like +create)?

-Joel
(joel@wam.umd.edu)

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

From: gt0449a@prism.gatech.EDU (Rob Coleman)
Subject: bus mice
Date: 12 Jun 92 22:59:03 GMT

I am currently setting up an X system using Linux and I need to know
where to go to find drivers for a microsoft-compatible bus mouse.
Others have posted this question, but I haven't been able to find an
answer yet.  Is the current revision (.96a) of the kernel sufficient, or
are additional kernel patches necessary to get the bus mouse to work?
Thanks.
-- 
Rob Coleman ][ gt0449a@prism.gatech.edu        ][  "I think I'm going bald!"
Comp. Sci.  ][ Georgia Institute of Technology ][        -Rush/COS

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

From: duperval@ERE.UMontreal.CA (Duperval Laurent)
Subject: How to fix HD I/O errors
Date: 12 Jun 92 23:06:32 GMT

Hi there,

I finally got my machine to boot Linux this week.  I've fallen on two
problems:

1- When I created my filesystem, I noticed that it reported I/O errors on two
of the blocks.  It didn't pay them any mind because I thought they would be
marked as bad and would become unusable.  But that isn't what happened.  Last
night I tried compiling a program for the first time.  gcc reported an I/O
error on one of the blocks I thought had been marked bad.  So now I can't
compile because it seems that the faulty block is in the way.  How can I fix
this?

2- This is more of an annoyance than anything else.  I'm getting all those HD
timeout problems that were prevalent during the month of April.  To circumvent
them I've decided to lower my CPU speed.  I'd like to know if there is a
better way to fix this, without havin to buy a new controller for my IDE
drive.  (I tried gettiing the answer from the digests at tsx but I don't know
how to get only the ones I need.  If someone can tell me how...)

I'm running on a 486-33, 4MB RAM, 210MB IDE HD, 0.95c+.

Thanks.

-- 
Laurent Duperval
duperval@ere.umontreal.ca
duperval@jsp.umontreal.ca

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

From: burley@geech.gnu.ai.mit.edu (Craig Burley)
Subject: Linux and Me II
Date: 12 Jun 92 22:12:53 GMT

In my previous posting, I mentioned that I'd run into some file errors
(writes and/or reads not working just right).  The conditions of all such
observed problems involved fairly large files and/or intensive disk
activity and, apparently, the 30-second update.

Several people suggested I incorporate patch #1 to 0.96a.  Not wanting
to try to build the kernel (and learn how to do that) with this bug lurking,
I put it off until I found that somebody had put 0.96a patch 1 of the boot
image up on a public ftp site (ftp.dfv.rwth-aachen.du -- thanks!).

I just installed this boot image and retried one activity in particular
that failed.  It consists of:

# cp -pr Personal /0h/craig

Meaning "copy a directory named Personal [on /dev/sd0d, along with all its
subfiles and directories] to a same-named directory under /0h/craig [on
/dev/sd0c]", which is a copy between partitions on the same disk.

Personal contains four files totalling just under 7MB.

With 0.96a, the behavior I got was:

    1.  A few minutes of disk activity.

    2.  An apparently successful copy (i.e. no error messages).

    3.  In response to "diff -r Personal /0h/craig/Personal", which recursively
        compares the source and target directories, messages that indicated
        that two files were different, separated by a "scsidisk read error".

    4.  In response to subsequent "diff..." commands, messages indicating that
        only one file (the first of the two listed in #3) was different, each
        time, with no more scsidisk read errors.

With 0.96a patch 1, I got this behavior:

    1.  [Same]

    2.  [Same]

    3.  In response to "diff", one message indicating that one file differed.

    4.  In response to subsequent "diff"s, no more messages!

To be more "careful", I "sync"ed between Steps 1 and 2 for patch 1 and between
each check in Steps 3 and 4.

Also, I rebooted as part of Step 4 to see if forcing Linux to re-read all of
the files would affect the results, but no.

So, it appears, based on this single (and easily inadequate) test, that patch 1
to 0.96a might indeed fix some problem involving writing to disk, but not
necessarily all problems involving reading from disk.  And, since most
of the problems I encountered involved copying, it's possible I was really
seeing occasional _read_ errors being reflected as _writes_ incorporating those
errors (though one such write was of a bad executable; I don't know how
plausible it is for ld to write a bad executable as a result of erroneous
disk reads from the OS and not complain in some way).

I'll remain a bit "anal" about doing lots of work under Linux until these
bugs seem more definitively fixed.  Fortunately, this means I can play with
Linux more and get less serious work done!  :-)
--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu
Member of the League for Programming Freedom (LPF)

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

From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: How much do you need to install Linux
Reply-To: cflatter@nrao.edu
Date: Fri, 12 Jun 1992 23:13:10 GMT

In article 11648@goanna.cs.rmit.oz.au, gtj@goanna.cs.rmit.oz.au (Glenn T Jayaputera) writes:
>Hi...I am wondering:
>1. How much disk space do you need to install linux

You could put a minimal system in 10 Mbytes or so.  You will probably want more
tho'.  My current installation lives in a 30 Mbyte partition and leaves about
9 Mbytes free (it would leave 19 free if I could live without emacs and the odds
and ends that come with it) but I don't keep sources on line.  

A GNU emacs installation takes about 10 Mbytes including all the lisp and info
files.  A TeX installation will probably take another 10.

>2. Which one is better Coherent 4.0 or linux (or this is not a fair
>   comparison)

Linux sources are available; Coherent sources are not.

        Chris Flatters
        cflatter@nrao.edu




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

From: burley@geech.gnu.ai.mit.edu (Craig Burley)
Subject: Re: Linux and Me II
Date: 12 Jun 92 23:32:01 GMT

Okay, folks, I now have a fairly-easy-to-reproduce command I can run that
reports different results pretty much every time:

    # diff -r ffe newffe

It compares two sourcefile subdirectories (containing, in case you care,
my GNU Fortran source code).

The two subdirectories are nearly identical.  One has a couple files the
other doesn't; and two text files are different.

About 50% of the time, diff reports these differences exactly as expected.

The rest of the time, diff reports these differences plus spurious
additional differences, sometimes in one file (in the form of a large
block of extra text), sometimes on another (in the form of a large block
of uuencoded-like text in the uuencoded-like file), etc.

The upshot is that it looks like the files are all okay on disk, but that
sometimes Linux misreads the data, convincing diff that files are different
when they aren't.  The differences seem more suggestive to me of block-level
(OS-interface-level) problems, though since I haven't looked at how diff is
implemented, I cannot be sure it isn't a diff bug (though it'd have to be
a random bug).

If anyone is working on these problems (probably related to SCSI support)
and wants me to test fixes, just email me.  Or, if anyone has an _idea_ of
where the bugs are in Linux but hasn't the time to carefully analyze the
code, point me at it and I'll give it a shot (I have 0.96a sources on my
system, though as yet untarred).  It'd be my first look at Linux source code,
but that shouldn't scare me, right?  :-)

For reference, here's my system configuration:

Central stuff:
    Tower case w/8 drive bays and 250-watt power supply
    Intel 32-bit 80486 CPU @33MHz
    Micronics EISA motherboard
    64KB cache RAM standard
    Support for Weitek 4167-33 math co-processor (don't need the chip yet)
    Phoenix 80486/EISA ROM BIOS PLUS Version 1.01.22-2
    16MB RAM, @70ns?
    2 serial ports, 1 parallel port
    8 EISA slots

Peripherals:
    Adaptec AHA-1740 SCSI-2 controller (BIOS v1.34)
    Maxtor PO-12S 1.2GB SCSI-2 hard drive
    5.25" (1.2MB) internal floppy
    3.5" (1.44MB) internal floppy
    Colorado Jumbo 250 tape drive (thru floppy interface, I think)

Hard Drive:
    64MB DOS, 807MB DOS extended, 62MB Linux, 64MB Linux partitioning (first
    two done by DOS FDISK, latter two done by hand using DOS DEBUG)

Wetware Interface:
    Sigma Designs L-View 1664x1200 120dpi 4-gray-scale monitor & card
    Northgate Computer Systems' OmniKey/101 (modified so CTRL to left of
        "A", CAPS LOCK left of SPC, etc)
    Standard Technologies Mouse (switchable Microsoft/Mouse system)
    Howtek Scanmaster
--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu
Member of the League for Programming Freedom (LPF)

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

From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Subject: Re: MCC Interim Release
Date: 12 Jun 92 05:57:45 GMT

In article <1992Jun10.225904.8791@amhux2.amherst.edu> pfcouvar@amhux1.amherst.edu (Peter Couvares) writes:
>
>       Does anyone know when the next MCC Interim version of Linux is going
>to be released? A few weeks ago I remember someone saying early June, but I
>have yet to see any mention of it.

Thanks for the interest.  I'm working on it, but have been help up by
complications (such as having traded in my 40mb hard disk for a 120mb one.
Perhaps bits will be available by Monday 15 June.  Watch this space!

     -- Owen
     LeBlanc@mcc.ac.uk

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

From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Subject: Re: current version of joe?
Date: 12 Jun 92 06:08:30 GMT

In article <1992Jun11.153038.24344@mercury.unt.edu> kenc@sol (Ken Corey - Operator) writes:
>Can someone point me to the latest version of joe?  I had found the sources
>to 1.4, but can't find them any longer.
>
>If you're frustrated by vi or emacs, try joe!  (It's REAL easy to modify!)

The standard distribution site for joe is wpi.wpi.edu in /stusrc.
The latest version is dated June 9, and is also available from
ftp.mcc.ac.uk in /pub/misc-unix/joe-20609.tar.Z.

     -- Owen
     LeBlanc@mcc.ac.uk

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


** 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-Activists-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux) via:

    Internet: Linux-Activists@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
    tupac-amaru.informatik.rwth-aachen.de	pub/msdos/replace

The current version of Linux is 0.96a released on May 22, 1992

End of Linux-Activists Digest
******************************
--[0459]--

