Files
2024-02-19 00:23:35 -05:00

262 lines
11 KiB
Plaintext

From: Digestifier <Linux-Activists-Request@news-digests.mit.edu>
To: Linux-Activists@news-digests.mit.edu
Reply-To: Linux-Activists@news-digests.mit.edu
Date: Wed, 25 Mar 92 04:45:07 EST
Subject: Linux-Activists Digest #148
Linux-Activists Digest #148, Volume #1 Wed, 25 Mar 92 04:45:07 EST
Contents:
Re: Linux in the spirit of the GNU General Public Liscense? (Jyrki Kuoppala)
Re: why do i need to format the disk before using raw write? (no, I don't repeat it!)
bibtex and mf available (Peter Williams 8169821)
Re: going faster than 38400... (Ed Carp)
Re: 33MHz fails, 8MHz works OK (Erik Fichtner)
Re: ESDI disk with 1629 cyl (Linus Benedict Torvalds)
----------------------------------------------------------------------------
From: jkp@cs.HUT.FI (Jyrki Kuoppala)
Subject: Re: Linux in the spirit of the GNU General Public Liscense?
Date: 24 Mar 92 16:01:09 GMT
Reply-To: jkp@cs.HUT.FI (Jyrki Kuoppala)
In article <kssijiINN1el@utkcs2.cs.utk.edu>, battle@cs (David Battle) writes:
>However, I was astounded at the near-hostile responses I received from
>some of the people working on development of Linux (Linus has NOT commented).
I think it's a good idea to offer commercial support - though it would
be appropriate to forward some part of the price the client pays to
the author(s?) of the software. I understand that the FSF recommends
something like this.
One social commentary - when you do this, don't brag and boast about
the tens of thousands of $$$$ you are getting and complain about how
bothersome it would be to implement any of the proposals to forward
some of the money to the community every week on alt.os.linux like
Eric S. Raymond is doing on alt.folklore.computers ;-) ;-)
>I think that the way these developers feel is blasphemy to the GNU GPL. The
>GPL is clearly set up to allow anyone who wants to to provide distribution and
>support services *and make a reasonable profit at it* while providing the
>users with the assurance of the availability of source code and the right
>to make copies. I'm sure Stallman is happy to have Cygnus Support around to
>take some of the hassle of distribution and support off his shoulders. I'm
>sure he's not at all upset that they aren't losing their shirts at it. In
>fact, I'll bet he would be tickled pink if they got filthy rich; it would
>just go to show that his philosophy about freely distributable software is
>economically viable.
I agree.
>Given this, I don't think it is a good idea for me to try to provide this
>service. I would need cooperation (or at least tolerance) from other Linux
>developers in order to provide this service effectively, and that doesn't seem
>to be forthcoming.
Oops, well I guess I haven't done anything for Linux so I guess I have
no business in meddling in the affairs.
Given the differences of opinion, I suppose someone would need to keep
track of the copyrights etc. - FSF policy seems to be the require
written paper disclaimers / assigments for the stuff they distribute
to keep clear of legal trouble.
//Jyrki
------------------------------
From: Pauli.Ramo@hut.fi (no, I don't repeat it!)
Subject: Re: why do i need to format the disk before using raw write?
Date: 24 Mar 92 17:44:43 GMT
Reply-To: Pauli.Ramo@hut.fi
In article <1992Mar23.192552.16081@ux1.cso.uiuc.edu> ctt31684@uxa.cso.uiuc.edu (... C H I N G ...) writes:
hello, while I was copying linux a while ago, i tried to use some unformatted
disks with raw write. and raw write couldn't recognize them or something until
I DOS formatted them. I'm wondering why do we need to DOS format in the
first place anyways since raw write just writes to the appropriate tracks
on the disk
In fact, DOS format does two or three separate things when used on a
diskette:
1. It creates the actual tracks on it (if they don't already exist)
2. It creates a DOS directory structure on the disk
3. It may also transfer the operating system files on the disk, if
asked
So, basically, you don't need the format command because of the DOS
directory structure, but to create the tracks for rawrite to write on.
In some operating systems the above things are separated to different
commands. For example, in SCO Unix (if I remember right), the format
command does only phase 1, and a separate command (mkfs) is used to
build the file system on the disk (phase 2)if required. This makes the
logical distinction much clearer, and I believe a linux-based format
will work that way, when (not 'if') created.
Pauli
--
Disclaimer fault - lawyers dumped
------------------------------
From: peterw@archsci.arch.su.oz.au (Peter Williams 8169821)
Subject: bibtex and mf available
Date: 25 Mar 92 05:04:46 GMT
BIBTEX
bibtex now works and is available for ftp in pub/linux/bibtex.tar.Z on
archsci.arch.su.oz.au (129.78.66.1). This file contains the binary file only
as the support files were included in texlib.tar.Z also available in the same
directory.
For those who need to do citations of the form (Knuth 1972) in their documents
the files in pub/harvard on the same site provide this capability together with
documentation in harvard.tex.
METAFONT
Binaries ONLY for metafont are available in pub/mfbin.tar.Z. You will need
to get font source files, etc from one of the standard tex sites.
dvips has a facility for generating fonts that it cannot find by calling a
script file called MakeTeXPK (provided either in texlib.tar.Z or dvips.tar.Z)
which will need modification w.r.t. where to put the generated pk files.
The dvips documentation describes this in more detail.
--
Peter Williams |e-mail: peterw@archsci.arch.su.oz.au
Key Centre for Design Quality |phone: +61-2-692 2053 or +61-2-660 6156
University of Sydney |+++++++++++++++++++++++++++++++++++++++
------------------------------
From: erc@Apple.COM (Ed Carp)
Subject: Re: going faster than 38400...
Date: 25 Mar 92 05:11:45 GMT
In article <11752@ns-mx.uiowa.edu> williams@herky.cs.uiowa.edu (Kent Williams) writes:
>From article <64259@apple.Apple.COM>, by erc@Apple.COM (Ed Carp):
>> It's quite easy (in theory, at least) - edit the quotient table (near the
>You can't run an asynchronous port reliably with a divisor of 1. It has
>to do with how the chip samples the analog signal -- you need divide by 2
>at least. So 57600 is about the upper limit on PC hardware. And with kernel
>and interrupt latency, that's pushing it.
Not necessarily so :) I hear that the 16550 can run at 115KB - also, if you're
running a fast 386 or 486, it might be able to handle it (with careful tuning
of the driver, that is). That's why I said "in theory". It certainly won't
work in all cases.
--
Ed Carp N7EKG/6 erc@khijol.UUCP erc@apple.com
Cupertino, CA 408/252-5947
-- Absolutely unabashed Gates McFadden groupie! --
------------------------------
From: techs@triton.unm.edu (Erik Fichtner)
Subject: Re: 33MHz fails, 8MHz works OK
Date: 25 Mar 92 07:12:30 GMT
In article <phil.701385550@calvin> phil@calvin.cs.scarolina.edu (Phil Moore) writes:
>
>In article <dave.701137159@stat.tamu.edu> dave@stat.tamu.edu (Dave Perry) writes:
>>I hate to waste bandwidth, but... :) I've successfully
>>installed basic linux on my pc (finally!) and have noticed
>>a few nagging problems. One is the refusal of the filesystem
>>to run in 33MHz on my 486.
>
>I can't offer any suggestions, but I'm having the same problem. I posted a
>message about it a few weeks ago, and only got a few mail responses which
>weren't much help.
> My system runs at 33 MHz with no problem under MSDOS. It's only under
>Linux that it crashes at 33 MHz. What motherboard are you using? I have a
>DTK 486-33 with 64K cache & 4 Megs RAM.
Oh bloody hell. This news leads me to believe that there is some problem with
DTK motherboards and Linux. I just hopped into here to post my own gripe about
a bug..
Linux 0.95 runs just fine on my 386sx/16 with 4mb of RAM. it runs FAST! kudos.
infact, it runs so fast that I decided to move it over to my BIG machine...
alas.. no joy.
Linux 0.95 on my DTK 386/25 (no cache) with 4mb of RAM and two Seagate ST1144A
IDE harddisks does very odd things.. here's a description:
It runs alright, but at random intervals it 'sticks' and keeps repeating
"HD timeout" and the hard disk makes evil angry noises. IT continues to do this
for about 8 to 10 retries and then reports "HD I/O error: bad block xxxx"
(or an error messgage similar to that. my system is just sitting there being
perfectly calm at the moment, so I can't quote the message) and then repeats
the entire cycle of "timeout-timeout-timeout-I/O error" over and over and over
until I give it a three finger salute. I've picked up the habit of appending
a ";sync" to all my commands so that i don't lose much when I reboot it.
Is there a fix? I am running 0.95.. would 0.95a help me any? Are there any
other DTK users who are not having this or other problems?
--
Techs techs@triton.unm.edu
Disclaimer: any inaccuracies are caused by the phase of the moon
"If you can't be with the one you love, honey, love the one you're
with" - Crosby, Stills, Nash, and Young
------------------------------
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Re: ESDI disk with 1629 cyl
Date: 25 Mar 92 08:07:58 GMT
In article <1992Mar24.223607.27070@afterlife.ncsc.mil> aegoldm@afterlife.ncsc.mil (Arthur Goldman) writes:
>Dilemma: I have a maxtor 600 MB drive with Ultrastor 12F esdi ctrlr.
>The controller offers me track mapping, which, when invoked, fools
>(DOS) into thinking it only has 1024 cyl (increases sectors/trk
>accordingly).
If the track-mapping is in the controller and not in some bios-routines,
linux should be able to run with it: indeed it happens automatically for
most machines I've heard of. Are you 100% sure linux can't use it
already?
/If/ linux seems unable to use the mapping-feature, there is still some
hope. I've left in the old code that hardcoded the harddisk parameters
instead of reading them from the BIOS, and by editing the config.h file
you can hardcode linux to think you have a specific number of sectors/
heads/tracks. Check out linux/config.h: the HD_TYPE macro. This isn't
guaranteed to help your problems, but it's worth a try.
Linus
------------------------------
** 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 alt.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.95a released on March 17, 1992
End of Linux-Activists Digest
******************************