[0465] daemon@ATHENA.MIT.EDU (Digestifier)  Linux Digest Archive  06/13/92 20:15 (550 lines)
Subject: Linux-Activists Digest #287
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:     Sat, 13 Jun 92 20:15:12 EDT

Linux-Activists Digest #287, Volume #2           Sat, 13 Jun 92 20:15:12 EDT

Contents:
  A soln. to X11 v1.0 problems (Elan Feingold)
  Re: GNU tar dies on multi-volume archive. Help. (n.h.chandler)
  Re: How do I delete file named "-I" ? (Kolja Kaehler)
  Serial port drivers (Thomas H Keil)
  Re: Patch2 is a bad patch if it doesn't compile (Ken Corey - Operator)
  Re: Linux installation .96a? (Jim Winstead Jr.)
  Re: No ./local/. please (Rik Faith)
  Problem with Shoelace (Paul Ma)
  FAS driver, can it be done? (Greg K. Moeller)
  Re: Problem with Shoelace (Ben Cox)
  Re: Linux installation .96a? (Gene Choi)
  Linux pieces: Where are them? (edmond bo xiao)
  Xconfig :  Keyword Expected error (Daniel Newcombe)
  Re: Linux installation .96a? (Jim Winstead Jr.)

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

From: elan@tasha.cheme.cornell.edu (Elan Feingold)
Subject: A soln. to X11 v1.0 problems
Date: 13 Jun 92 13:36:57 GMT
Reply-To: elan@tasha.cheme.cornell.edu (Elan Feingold)


I keep getting mail about x11 v1.0 and problems.  I posted one solution but forgeot to mention that if you don'thave the 75dpi fonts, take that entry out of your Xconfig - and make sure that the path listed there is valid.  After you do this, you should have no problem with `cannot connect to server' messages.

--
Elan Feingold

CS/EE Departments
Cornell University

==============================================================================
This sig file is a virus.  If  If you are reading this right now then it has
already copied itself into your most important files.  Following is the 
assembly language that makes up the virus:
$%#$^##$%^#$%^F#F$%^#$%^^#VF$%^#G$%^VB#$%BN&W#$^%V$WY%B$^UB^#U$B^Y#B^#$Y^
##VF%^Y#%^BY%#^YB#Y^$%^Y#%^YJHKUIO(^*I*$NO(%IN%&FW%#C_CF{R}GTFBNJ}FJ^G$DB$H^B%
==============================================================================

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

From: nhc@cbnewsj.cb.att.com (n.h.chandler)
Subject: Re: GNU tar dies on multi-volume archive. Help.
Date: Sat, 13 Jun 1992 14:28:29 GMT

In article <mper.708400660@uipsuxb>, mper@uipsuxb.ps.uiuc.edu (Michael Pereckas) writes:
> joel@wam.umd.edu (Joel M. Hoffman) writes:
> 
> >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/
> 
> >Does anyone have a convenient way of doing what I'm trying to do?
> >Will
> 
> Use wrflops/rdflops, available on the ftp sites, although I have no
> 
> I use this for my backups and it really works.  I have been unable to
> Hope this helps.
> 


The file is floptools.sh posted by Bennet E. Todd (bet@internet.sbi.com)
on Wed Apr 22.  It is a very reliable backup tool.  I've been using it
since it was posted and haven't had any problems.

Neville H. Chandler
nhc@mtdcc.att.com


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

From: kk@cs.tu-berlin.de (Kolja Kaehler)
Subject: Re: How do I delete file named "-I" ?
Date: 13 Jun 92 14:32:17 GMT

tm@netcom.com (Toshiyasu Morita) writes:
> Subject line pretty much says it all. I've tried rm -I, rm "-I"...they both say
> "Unknown option -I". Help!
> 
> Toshi Morita
> tm@netcom.netcom.com
> 
> 

rm ./-I should work.

        Kolja
-- 
==============================================================================
Kolja Kaehler                                            <kk@cs.tu-berlin.de>

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

From: thkeil@wpi.WPI.EDU (Thomas H Keil)
Subject: Serial port drivers
Date: 13 Jun 92 15:52:10 GMT


                ttys1 (major 4, minor 64) is com1
                ttys2 (major 4, minor 65) is com2
                etc.

For me it is really (I think this comes from mcc-interim)

                ttys0 (4,64) is com1
                etc.

So I have to use /dev/ttys0 in Xconfig to make my mouse work -- in spite of
the installation instructions.

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

From: kenc@sol (Ken Corey - Operator)
Subject: Re: Patch2 is a bad patch if it doesn't compile
Date: Sat, 13 Jun 1992 16:16:24 GMT

vds7789@aw2.fsl.ca.boeing.com (Vincent D. Skahan) writes:

>sinster@dana.ucsc.edu (Darren Senn) writes:
>Hasn't anybody comsidered the possibility that a patch that installs
>correctly, yet doesn't compile is an incomplete (and therefore invalid)
>patch that we shouldn't be using until another comes out to make it
>complete (and therefore valid) ?

>Could Linus please either release a patch3 so that we're up at the
>current version and can just hit 'make' or release a patched-up 'good'
>set of sources ???

This patch is good, with the LONE exception that itimer.c is mentioned in
lib/Makefile.  Period.  End of statement.  The problems I had with it were
due to my own stupidity (I'd copied the net's itimer.c for the library over
the itimer.c in kernel/, making compilation difficult.  Once I found this
part of the patch, and reinstalled, it went perfectly.

If you haven't changed your kernel sources from the distribution, and if you
have installed the patches the proper way, it's automatic, and very easy to
deal with upgrading.

>I'm not installing anything above patch1 if I have to tweak anything
>to get it to compile...

Then what are you doing with Linux in the first place?  This is advertised
as a hacker's OS, guaranteeing many hours of 'tweaking'.  That's one of the
reasons I wanted to GET linux in the first place.

Ken == kenc@sol.acs.unt.edu == kenc@vaxb.acs.unt.edu == MAX_DOUBLE();

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

From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
Subject: Re: Linux installation .96a?
Date: Sat, 13 Jun 1992 17:39:14 GMT

In article <3ndltdd.genie@netcom.com> genie@netcom.com (Gene Choi) writes:
>
>Well, I was successful in installing Linux boot and root into
>my IBM 386 33!  I installed version 0.95c+.  I wanted to
>install 0.96a (the newest version?) but was only able
>to find the boot image disk to .96a...  I was unsuccessful
>in finding the root (utility) image in any of the ftp sites.
>Can someone please tell me what I'm doing wrong?
>

The reason you're not able to find the root image for 0.96 is because
it hasn't been released yet.  I apologize greatly for this, but the
shift from school to home was a little rougher than I expected, and I
haven't had the resources to put together the 0.96 root disk.

This will change this next week, however, as I will be getting an
account on a University of Minnesota machine, and will be able to
telnet over to my account here and also have ftp access again.

Because of this, I hope to have the 0.96 root disk released by the end
of next week.  It will use shared libraries (hopefully from the gcc
2.2.1 release) and not contain the horrid tar/compress from the 0.95a
root disk.

Also, sometime after I release the 0.96 root disk, I will be releasing
a 'supplemental' disk, with some of what I, and others, consider the
essential utilities for Lnux.  This will include, but not be limited
to, kermit, pcomm, an editor or two, mtools, the GNU shell and text
utilities, and whatever else people suggest.

Again, I apologize for being so late on all this.  I did not expect
moving back home for the summer would be so traumatic....

One last thing, I have made the offer in several places (Compu$erve
and RIME) to send Linux itself and many utilities on disk or QIC-40
tape.  If you'd be interested in such a thing please send me email at
the address below.  (Oh, this is a summer-only type of deal....)
-- 
                                    +    Jim Winstead Jr. (CSci '95)
                                    |            Harvey Mudd College
                                    | jwinstea@jarthur.Claremont.EDU
                                    + This is all my words.  Honest!

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

From: faith@cs.unc.edu (Rik Faith)
Subject: Re: No ./local/. please
Date: 13 Jun 92 16:59:20 GMT

In article <1992Jun12.120249@tioga.ucsc.edu>, sinster@tioga.ucsc.edu (Darren Senn) writes:
|> 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.

For standard unix systems, these tools do not come with the system.  Your 
sys admins on campus didn't want to munge up their /usr/bin when they installed
other packages.  With Linux, this isn't a problem.  The GNU utilities belong
in /usr/bin, for example, because they aren't *add ons* -- they are a large
part of the "standard" Linux utilities.  This includes, for example, groff,
which is relatively standard and should be installed exactly the same way
on everyone's system.

You should put your private hacks in /usr/local/bin: like your private, hacked
up version of TeX (vs. the version in the ABC Release, for example).  Or your
Linux-specific ls which highlights the directories in bright red, for example.
Or your hacked up version of the groff ms macro package.

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

This is nothing that a few if statements can't fix.  I actually use the
same .login/.cshrc on several different systems and on Linux without any
problem.

-- 
Rik Faith: faith@cs.unc.edu
Paradox is the question of Chaos.

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

From: pm2@doc.ic.ac.uk (Paul Ma)
Subject: Problem with Shoelace
Date: 13 Jun 92 18:51:28 GMT

Hi,

After spending hours reorganising my new and old hard disk, I re-install Linux
and Dos.  The installation was OK (I'm using the MCC interim 0.95C+ release).
I then tried to set up shoelace.  I can boot from the 'Image' disk produced
during the MCC installation.  But when I tried to boot from the floppy produced
by shoelace.  The machine hanged after I chose to boot Linux, it works fine if
I choose to boot DOS.  Any ideas?  

Partition of my hard disks:

Drive 0

Part. no.  Boot  begin   start     end    blocks   Id   System
/dev/hda2   *        1      33   123023   61495+    6   Dos 16-bit
/dev/hda3       123024  123024   196943   36960     5   Extended
/dev/hda4   *   196944  196944   204863    3960    41   Unknown 
/dev/hda5       123025  123057   188759   32851     6   Dos 16-bit
/dev/hda6       188761  188793   196943    4075     1   Dos 12-bit

Drive 1

/dev/hdb1            1       1   130000   65000    41   Unknown
/dev/hdb2       130001  130001   160000   15000    41   Unknown
/dev/hdb3       160001  160001   170000    5000    82   Linux Swap
/dev/hdb4       170001  170001   659231  244615+    6   Dos 16-bit


The Linux partitions are set to unknown because I'm using DR-DOS 6.0
/dev/hda4 is the root
/dev/hdb1 is mounted as /usr
/dev/hdb2 is mounted as /home

Also, when I boot successfully using the MCC-created boot disk, "free" shows
that 46980 out of 51976 of swap disk is used.  Surely, this can't be right, my
machine has 8M of RAM and nothing else was loaded.

Any help will be appreciated.


Paul.

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

From: gkm@muug.mb.ca (Greg K. Moeller)
Subject: FAS driver, can it be done?
Date: Sat, 13 Jun 1992 19:07:38 GMT

I've heard of the FAS serial driver that supports shared IRQs and 16550s.
Has anyone tryed to make this work under Linux, and did it work?

Here's a bit of the README file that comes with it.
I found it on csn.org in the directory /FAS

Greg.


README file for the FAS Final Async Solution driver
===================================================

What is this package:

     This is an alternate async driver for 386 based unix systems that
     adds several features that are not supported by vendors drivers.

        1.  It supports the NS16550 UART chips in full FIFO mode.
        2.  It supports modem sharing for input and output.
            Microport almost supported this feature but none
            of the other vendors did.
        3.  It supports hardware flow control.


     This driver should work with most of the UNIX SYS V/386 3.X ports
     currently available. You can have both this and the original
     vendor driver in the same kernel. Each driver controls its own
     separate set of serial ports. The only restriction here is that
     any int vector must not be used by more than one of the drivers.
     The kernel config program will complain otherwise.

     Note: This driver supports neither VP/ix nor DosMerge virtual
           serial devices. If you need COM ports for your DOS programs
           you have to connect the needed devices to ports that are
           controlled by the original vendor async driver. You won't
           have the special features of the FAS driver on these ports,
           though. If you don't need to access serial ports from DOS
           the vendor driver can be removed from the kernel.

========================================================================
     
A little about what it does:

     This driver supports shared line usage by having two logical
     devices sharing one physical line.  To those familiar with
     Microport this is very similar.  For the other readers a
     brief description follows.  For each line there are two
     names.  For example for the first line the names are ttyF00
     (minor device 0) and ttyFM00 (minor device 192).  The ttyF00
     is used for cu, kermit, and other programs that want to dial
     out.  It ignores the modem signals and just goes to it.  The
     ttyFM00 line is strictly for getty.  When getty calls open on
     ttyFM00 the driver hangs the open until the modem asserts the
     carrier detect signal and then lets the open complete.  If cu
     opens ttyF00 while getty is waiting for the open to complete
     the device is given to cu and the getty open must wait for cu
     to finish and then will again wait for the carrier.  If cu
     tries to open the ttyF00 line while getty has ttyFM00 open cu
     will get an error.  If getty tries to open ttyFM00 while cu has
     ttyF00 open the getty open will just hang and wait for cu to
     close the line and then wait for the carrier.  To put it simply
     you should put up a getty on ttyFM00 with a -t 60 and use ttyF00
     for cu and uucico.

     The modem devices ttyFMxx is the minor device of ttyFxx plus
     192.  There are several other possible minor devices for
     each port.  See the description in `fas.c'.


Originally written by
Jim Murray              encore!cloud9!jjmhome!jjm
2 Mohawk Circle         harvard!m2c!jjmhome!jjm
Westboro Mass 01581     jjm%jjmhome@m2c.m2c.org
USA                     voice (508) 366-2813

Current author:
Uwe Doering             gemini@geminix.mbx.sub.org
Billstedter Pfad 17 B
1000 Berlin 20
West Germany


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

From: thoth@uiuc.edu (Ben Cox)
Subject: Re: Problem with Shoelace
Reply-To: thoth@uiuc.edu (Ben Cox)
Date: Sat, 13 Jun 1992 20:12:23 GMT

pm2@doc.ic.ac.uk (Paul Ma) writes:

> After spending hours reorganising my new and old hard disk, I
> re-install Linux and Dos.  The installation was OK (I'm using the MCC
> interim 0.95C+ release).  I then tried to set up shoelace.  I can boot
> from the 'Image' disk produced during the MCC installation.  But when
> I tried to boot from the floppy produced by shoelace.  The machine
> hanged after I chose to boot Linux, it works fine if I choose to boot
> DOS.  Any ideas?

Sounds like you made the same mistake I did.

Even to test on a floppy, the first laceup command must be done on
your HD.  That's the "laceup /dev/hda? wini" command.  Do that first,
whether you're testing on a floppy or not.

Then you do either "laceup -w ? /dev/hda" to change your HD master
boot record or "laceup -w ? /dev/fd0H1440" to make a test floppy.

Hope this helps.

--
Ben Cox
thoth@uiuc.edu

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

From: genie@netcom.com (Gene Choi)
Subject: Re: Linux installation .96a?
Date: 13 Jun 92 20:00:05 GMT

In article <1992Jun13.173914.24222@muddcs.claremont.edu> jwinstea@jarthur.claremont.edu (Jim Winstead Jr.) writes:
>In article <3ndltdd.genie@netcom.com> genie@netcom.com (Gene Choi) writes:
>>
>
>The reason you're not able to find the root image for 0.96 is because
>it hasn't been released yet.  I apologize greatly for this, but the

Hmm...  If I want to install 0.96a, how do I do it without the
root image?  Most people here seem to be running 0.96a.  Does
it require that I upgrade a couple of files from previous
version? (0.95c+)  Or do I just use the 0.96a boot disk with
the 0.95c+ util/root disk?  Thanks in advance.

Gene

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

From: ebx@scs.carleton.ca (edmond bo xiao)
Subject: Linux pieces: Where are them?
Reply-To: ebx@scs.carleton.ca
Date: Sat, 13 Jun 1992 20:49:02 GMT

I have just put linux on my 384-40. It runs happily. Instalation and rebuilding
the kernel didn't give me much trouble. However, searching around ftp sites to
get all the necessory pieces does trouble me alot. Today, you find you are missing
less, nroff or so. Tomorrow, wc or sort may hang you up. I know there is an ABC
release but not much stuff down the tree. 

Any clues about this?

Besides, when issue a man, pages are displayed fine, but have to ^C to exit.
Moreover, after ^C, linux doesn't echo my typing. I know they are thers 'cause
hitting CR gives me feedbacks.

Anybody has a simaliar problem?

edmond





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

From: ae007@yfn.ysu.edu (Daniel Newcombe)
Subject: Xconfig :  Keyword Expected error
Date: Sat, 13 Jun 1992 21:33:39 GMT


Well, I uncommented the two lines for the fonts in the Xconfig    
and it stopped giving me the error. In fact it just stopped.
I have poured over the FAQ list and the solution for this prob.
is not in there.  After trapping the output from running
startx 2>t.t
it tells me that for line 24 in Xconfig a keyword is expected. 
SO I looked at the file and it was a blank line so I commented
it out and tried again. This time same error on line 29. The line
was Keyboard, so I commented it out and try try again. Error on
line 30 - autorepeat, so I gave up and here I am.

Actually I am beginning to wonder if X11 really works or not. It
seems to fight any attempt to get it running.  Could someone that
has it running give me a hand, as the get-an-error-and-hope-it-
is-covered-in-the-FAQ method is not working.
    Thanks,
     -Dan

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

From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
Subject: Re: Linux installation .96a?
Date: Sat, 13 Jun 1992 23:49:04 GMT

In article <99dl8xh.genie@netcom.com> genie@netcom.com (Gene Choi) writes:
>In article <1992Jun13.173914.24222@muddcs.claremont.edu> jwinstea@jarthur.claremont.edu (Jim Winstead Jr.) writes:
>>In article <3ndltdd.genie@netcom.com> genie@netcom.com (Gene Choi) writes:
>>>
>>
>>The reason you're not able to find the root image for 0.96 is because
>>it hasn't been released yet.  I apologize greatly for this, but the
>
>Hmm...  If I want to install 0.96a, how do I do it without the
>root image?  Most people here seem to be running 0.96a.  Does
>it require that I upgrade a couple of files from previous
>version? (0.95c+)  Or do I just use the 0.96a boot disk with
>the 0.95c+ util/root disk?  Thanks in advance.

Right, to install 0.96a *now*, you can use the 0.95a root disk.  Be
sure to replace the tar/compress combination from that root disk with
the new ones on TSX-11 or other sites as soon as possible, though,
because the ones on the root disk are known to be corrupt.

If you're willing to wait a week, just use the 0.96 root disk that
should be coming out.  :)
-- 
                                    +    Jim Winstead Jr. (CSci '95)
                                    |            Harvey Mudd College
                                    | jwinstea@jarthur.Claremont.EDU
                                    + This is all my words.  Honest!

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


** 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
******************************
--[0465]--

