lostecho/oldlinux-files
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add directory mail-archive

Browse Source
This commit is contained in:
gohigh
2024-02-19 00:25:02 -05:00
parent 07129c3397
commit a778c607a4
1056 changed files with 796887 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

645
mail-archive/linux-devel/Volume1/digest5XX/digest590 Normal file
View File

@@ -0,0 +1,645 @@
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: Wed, 30 Mar 94 18:13:09 EST
Subject: Linux-Development Digest #590
Linux-Development Digest #590, Volume #1 Wed, 30 Mar 94 18:13:09 EST
Contents:
Re: Hardware developing X/Motif (Mike Chapman)
Re: Proposal - Coordinating bug fixes with enhancements. (Christian Henry)
Re: Slackware as a tar.gz file? (NetDog)
Re: Proposal - Coordinating bug fixes with enhancements. (Brian Edmonds)
BusLogic BT445S driver? (Larry Pyeatt)
OPTI 495SLC+486DLC+Linux+Internal Cache? (Harri Pasanen)
Re: Slackware as a tar.gz file? (Dave Platt)
cluster-patches lead to error on fsync (Christopher Etz)
Re: profiling anyone? (Bas de Bakker)
Re: Kernel compile dying w/SIGSEGV (Gunther Mayer)
Re: Slackware as a tar.gz file? (Jerome Kaidor)
SCSI troubles (Andreas Kostyrka)
IDE disk contoller and segmentation faults (Michael MNUK)
Re: Adaptec 2742T anyone? (Doug McIntyre)
How To Cross-Compile for DOS? (Rick Miller)
Re: _NEED_SHRLIB_libc_4 ? I have libc.so.4 (Rene COUGNENC)
----------------------------------------------------------------------------
Crossposted-To: comp.os.linux,comp.unix.questions
From: Mike.Chapman@muc.de (Mike Chapman)
Subject: Re: Hardware developing X/Motif
Date: Tue, 29 Mar 1994 19:32:34 GMT
Tom Svaleklev (tsva@elmrd6.ineab.ikea.se) wrote:
: Hello there !
: I'm about to start my own firm consulting and teaching X windows/Motif,
: Unix and C. I looking for opinions/experiences on decent hardware
: requirements needen to run and develop X/Motif/Unix for personal use.
: I do own a PC 486/66, 4Mb/200Mb (IDE) and have thoughts on upgrading it
: and install Linux, FreeBSD or something like that.
Then you will need 16MB of RAM. (You will need this if you are running
Object Center or any of that kind of stuff). For building X apps you
will probably need a lot more disk. If your 200MB has already got something
on it you should probably consider at least another 300+MB disk.
: But since I also want DOS/Windows I understand that I have to buy
: another disk for my Unix system. Also it's been said that PC's can't
: cope with selected bootings therefore I've been suggested to throw
: my IDE disk away and buy a SCSI controller card and a new disk for my
: DOS system. Switching disks in the SCSI card will then determine
: what system to run. I also believe I need at least 16Mb of memory
: to cope with Unix.
Linux will run fine in 4MB, to run X you really need 8MB (yes there
are a few minimalists who do it in 4MB), to do X development you
should consider 16MB as a minimum.
LILO (the linux loader) will boot almost anything from anywhere
and allow you to choose at a prompt what you want to boot. It
is configurabale to do almost anything. IDE disks are no problem.
SCSI is normally no problem either but make sure your card is
supported.
You can put Linux and DOS/Windows on the same disk. No problem.
You should consider where you are going to get the necessary X libraries
etc. If you need the source code to them you might consider investing
in a CDROM drive otherwise you better get yet more disk space.
Get a decent source code control system and learn how to use it before
starting. I find CVS good for stuff spread over multiple directories
otherwise you could probably just make do with RCS or the likes.
: My second, and ideal, thought is to buy a proper workstation but the
: onces I've been using at my former jobs are far too expensive for
: personel use. Are there any that is less expensive ? How about licences,
: service agreements, release updates, etc ? I don't mind buying a used one.
Depends really on what software you need to run, and for what
environment you have to deliver. If your software has to run a RS/6000
then sooner or later you will need one (ditto SPARC, ALPHA, powerPC etc).
And yes, they do cost more than a low end PeeCee.
: What are your suggestions ? /Thanks a lot
--
Mike.Chapman@muc.de
Asked what he thought of Western civilization,
Mahatma Gandhi said, "I think it would be an excellent idea".
------------------------------
From: henryc@reality.UUCP (Christian Henry)
Subject: Re: Proposal - Coordinating bug fixes with enhancements.
Reply-To: henryc%reality%ionews@io.org
Date: Mon, 28 Mar 1994 03:38:36 GMT
In article <2n3h1l$88v@klaava.helsinki.fi>,
Linus Torvalds <torvalds@klaava.Helsinki.FI> wrote:
>There is already a "official" way to do this, which is
>
> 1.0 Stable (hope)
> 1.0.x minor bugfixes
>
> 1.1 development
> 1.1.x bugfixes, new features, more development
>
>After 1.1.x seems to be stable, we rename the last version as
>
> 1.2 Stable
> 1.2.x minor bugfixes
>
> 1.3 development
> 1.3.x bugfixes, new features, more development
>
>etc.. So even minor numbers would be stable releases, while odd minor
>numbers would be development releases. Both have patchlevels, but the
>stable releases would have only bugfixes.
Wouldn't this be a bit confusing to some users? IMHO, most people are used
to _both_ even and odd numbered versions of software (operating systems
included) being considered ``stable'' releases, while some alternative
method (such as the string ``ALPHA'' or ``BETA'', or simply an ``a'' or
``b'' following the main version number (``1.1'' for example)) is used to
indicate ``development'' or ``unstable'' releases.
In addition, due to the possible confusion which could occur from the
``even == stable, odd == development'' method, I'd imagine that even _more_
bandwidth in the comp.os.linux.* newsgroups would be needlessly wasted with
messages asking such questions as (from a new user), ``Why is Linux broken
[using v1.3]?'' or ``What's the difference between Linux v1.1 and v1.2?''
In other words, what _I'm_ suggesting is a version numbering method like
this:
1.0 Stable (hope)
1.0.x minor bugfixes
1.1 ALPHA
or 1.1 BETA development
1.1.x ALPHA
or 1.1.x BETA bugfixes, new features, more development
After 1.1.x ALPHA (or BETA) seems to be stable, we rename the last version as:
1.1 Stable
1.1.x minor bugfixes
Then, work begins on the next development:
1.2 ALPHA
or 1.2 BETA development
1.2 ALPHA
or 1.2.x BETA bugfixes, new features, more development
Which, when ``stable'', is renamed to:
1.2 Stable
1.2.x minor bugfixes
If possible, please duplicate your comments/critisms (if any) via e-mail to
the first address shown in my .sig.
--
| Christian Henry | e-mail: henryc%reality%ionews@io.org (preferred) |
| | or: henryc@io.org (if above address bounces) |
------------------------------
From: cdent@yod.honors.indiana.edu (NetDog)
Subject: Re: Slackware as a tar.gz file?
Date: Wed, 30 Mar 1994 02:32:43 GMT
>>>>> "Jerome" == Jerome Kaidor <jkaidor@synoptics.com> writes:
Jerome> I dreamt of a script that would activate FTP, tell it
Jerome> to get slackware.tar, and pipe its output straight up to
Jerome> tar on my machine, which would then spew out files and
Jerome> directories. Probably an impossible dream......
One possibility is to use mirror, the package that some archive sites
use to keep up their mirrors. I can be set up to get an entire
director and subdirectories. This is what the config file would look
like for slackware:
package=slackware
comment=The Linux Slackware Distribution
site=ftp.cdrom.com
remote_dir=pub/linux/slackware
local_dir=/foo/bar/slackware
mail_to=foofoo
The mirror package is available at:
src.doc.ic.ac.uk [146.169.2.1]
directory: computing/archiving/mirror
(shortcut packages/mirror)
Although it was originally intended to be used for continuous upkeep
of a collectin it works great for getting files just once. One thing
you have to watch out for (especially if you are doing the ftpping
from a linux box): check the logs when the program has finished for
the files that it timed out on. You will have to go back and get
those; either by hand or just run mirror again (it only gets files it
doesn't already have).
Chris
--
cdent@indiana.edu|"if you're so special why aren't you dead?"-TheBreeders
------------------------------
From: edmonds@cs.ubc.ca (Brian Edmonds)
Subject: Re: Proposal - Coordinating bug fixes with enhancements.
Date: 29 Mar 1994 20:55:53 GMT
Reply-To: Brian Edmonds <edmonds@cs.ubc.ca>
>>>>> On Mon, 28 Mar 1994, henryc@reality.UUCP (Christian Henry) said:
LT> [ even/odd versioning ]
CH> Wouldn't this be a bit confusing to some users?
Oh my, wouldn't that be too bad. Really now, we're talking about unix
systems administration and kernel level stuff (yes, compiling and
installing a new kernel is kernel level in my book -- most computer
users don't do this ever). I think if you want to get involved at this
level of the system, you can expect to learn at least a small amount of
technical detail. Maybe even/odd versioning isn't used in the software
you encounter, but I've certainly seen it often enough.
---Tenchi-Muyo---Dominion--KOC--Riding-Bean--UY--BGC---/================
Brian Edmonds (MSc CompSci) aka Jubal@tmi-2 / SCA: Bardas,OFLT
http://www.cs.ubc.ca/spider/edmonds ...FBI / Lions Gate, AnTir
----Dylans----Bruce-Cockburn---U2---Annie-Lennox----/___inux spoken here
Waaaaahhh! <Brain cells go on a mass lemming charge.....> ^_^
------------------------------
From: pyeatt@CS.ColoState.EDU (Larry Pyeatt)
Subject: BusLogic BT445S driver?
Date: 30 Mar 94 03:00:19 GMT
I have a BusLogic BT445S fast SCSI adapter. Is there a driver for
this board, or should I start writing my own. Any pointers would be
appreciated.
--
Larry D. Pyeatt All standard disclaimers apply.
pyeatt@cs.colostate.edu Void where prohibited.
------------------------------
From: pa@tekla.fi (Harri Pasanen)
Crossposted-To: comp.os.linux.help,comp.sys.ibm.pc.hardware.chips
Subject: OPTI 495SLC+486DLC+Linux+Internal Cache?
Date: 29 Mar 1994 06:32:19 GMT
Hello good people,
I noticed that my OPTI 495SLC mother board + TI486DLC40 does not
enable 486DLC's internal cache when running Linux. In AMI bios settings I
have both external (128K) cache and internal cache set enabled.
I tried enabling/disabling the internal cache, and sure enough, under
does all the benchmarks showed the expected results.
How do I know it is not enabled under Linux? Well, I get 7.98
Bogomips on linux. I tried CxPatch, and the Bogomips jumped to 13.21.
Unfortunately the system then died to a message along the lines:
Aha1542.c got the interrupt but no mail.
Sorry, can't remember the exact wording. However, seems that DMA has
not updated the cache.
Has anybody successfully licked this problem?
Software versions:
CxPatch v0.25, linux 0.99.13p, libc4.4.4, gcc 2.4.5.
Hardware:
OPTI 495SLC MB with TI495DLC, IIT4C87DLC, 128K Cache
AMI Bios v2.1
Please email the replys; I'll summarize on request.
Thanks,
Harri
--
======================================================
Harri Pasanen pa@tekla.fi
phone home: 802 5350 work: 887 9436
------------------------------
From: dplatt@ntg.com (Dave Platt)
Subject: Re: Slackware as a tar.gz file?
Date: Wed, 30 Mar 1994 04:30:47 GMT
In article <CnG7Ew.4z9@synoptics.com> jkaidor@synoptics.com writes:
> I dreamt of a script that would activate FTP, tell it to get
> slackware.tar, and pipe its output straight up to tar on my machine,
> which would then spew out files and directories. Probably an impossible
> dream......
Shouldn't even be all that difficult. At least some Unix ftp clients
(e.g. Sun) can direct the receive stream to standard output - so you
should be able to pipe this into tar.
Or, alternatively, write a C program to use pipe() to create a named
pipe "file", persuade your FTP client to "append" to this pipe, and
start up a tar process which reads its input from the pipe.
--
Dave Platt dplatt@ntg.com ..or.. ...netcomsv!ntg!dplatt
USNAIL: The 3DO Company, NTG division
2470 Embarcardero Way
Palo Alto CA 94303
------------------------------
From: cetz@cetz.rhein-main.de (Christopher Etz)
Subject: cluster-patches lead to error on fsync
Date: Tue, 29 Mar 1994 21:11:40 GMT
When I use the cluster patches with Linux 1.0, some fsync() calls return
EIO (unix error 5, "I/O error"). This behavior is the same since several
releases of Linux and the cluster pathches. The same binaries run well,
as long as I don't use these patches.
Did anybody encounter this problem? And does this one know of any workaround?
Background: I ported a DBMS system to Linux. It ensures that the write
operations went onto the disk via fsync() calls. (As far as I know, O_SYNC
isn't implemented yet, right?) This leads to quite a lot of fsync() calls.
I cannot reproduce the phenomen with a simple test program which does just
a few write()'s and fsync()'s. It would take me a lot of time to get a
debug version of the software; that's why I'm asking "the net".
AtDhVaAnNkCsE 4 any reply,
Christopher
--
============================================================================
Christopher Etz Telefon, Telefax: +49 69 318091
Kopernikusstr. 28 Email (priv.): cetz@cetz.rhein-main.de
D-65929 Frankfurt Email (biz.): christophere@ingres.com
------------------------------
Subject: Re: profiling anyone?
From: bas@phys.uva.nl (Bas de Bakker)
Date: 30 Mar 1994 06:58:13 GMT
Ivan <ivan@djomolungma.Eng.Sun.COM> writes:
> Linux doesn't have facilities for helping with sampling style
> profiling. I was hoping 1.0 would have something but no such
> luck. Soooo, I"m going to try and add it in myself.
I'm not sure what it is exactly that you want. There is indeed no
profil() system call in the Linux kernel, but there is a routine in
the C library under that name which does the same thing.
As to profiling tools: gprof is in the binutils package and recently I
wrote a "profiling per source code line" utility called bprof which
can be found in
sunsite.unc.edu:/pub/Linux/devel/bprof-0.1.tar.gz
Bas.
------------------------------
Crossposted-To: comp.os.linux.admin,comp.os.linux.misc,alt.uu.comp.os.linux.questions
From: gmayer@gypsy.physik.uni-kl.de (Gunther Mayer)
Subject: Re: Kernel compile dying w/SIGSEGV
Date: Wed, 30 Mar 1994 08:08:14 GMT
In article <2n7n35$pa3@bb29c.mdd.comm.mot.com>, mitchell@mdd.comm.mot.com (Bill Mitchell) writes:
|> in comp.os.linux.development, odoncaoa@panix.com (Douglas Donahue) said:
|>
|> >[...]
|> >A representative failure message:
|> >.
|> >.
|> >gcc -D__KERNEL__ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe \
|> > -m386 -c -o init/main.o init/main.c
|> >gcc: Internal compiler error: program cc1 got fatal signal 11
|> >make: ***[init/main.o] Error 1
|> >cpp: output pipe has been closed
|>
|> Just a followup to say that at least one other has similar woes.
|> I started at 0.99pl8, and kernel rebuilds were rock solid for a while.
|> Somewhere around pl12, I started seeing just exactly what is reported
|> above. I'm still seeing it with pl15h.
|>
|> I've commented about it a couple of times in comp.os.linix.whatever, and
|> responses indicated that it had to be a hardware error. That's reinforced
|> by rock-solid rebuilds on other linux installations. However, I don't
|> recall seeing anything like this with anything but cc, and can't localize
|> it to a hardware problems. Exercising the disks by copying massive amounts
|> of data works OK, and standalone memory-test programs run overnight report
|> no problems.
|>
|> For now, I'm just living with it. I restart "make zImage" as needed, and
|> reboot if that doesn't work (the problem appears less frequently on a
|> recently booted system).
|>
|> --
|> mitchell@mdd.comm.mot.com (Bill Mitchell)
|>
MY SOLUTION:
I experienced the same behaviour last summer ( even OS/2 2.0 TRAPed every
10 minutes). I installed a ventilator and NEVER saw this again.
I traced this down to the room temperature, the higher the temperature the
less time would OS/2 run. In Linux it happened nearly only when I compiled a
new Kernel (there you could continue, OS/2 had to be rebooted).
--
=====================================================================
Gunther Mayer, Burgalberstr.8, 66989 Hoeheinoed, Germany
at work: Gunther Mayer, Fachbereich Physik, Uni Kaiserslautern,
Erwin-Schroedinger-Str., 6750 Kaiserslautern, Tel ++49 631 205 4286
email: gmayer@physik.uni-kl.de
------------------------------
From: jkaidor@synoptics.com (Jerome Kaidor)
Subject: Re: Slackware as a tar.gz file?
Reply-To: jkaidor@synoptics.com
Date: Tue, 29 Mar 1994 22:49:43 GMT
In article 94Mar25210418@first.cs.nyu.edu, fox@graphics.cs.nyu.edu (David Fox) writes:
>In article <gat-240394180427@137.79.107.114> gat@robotics.jpl.nasa.gov (Erann Gat) writes:
>
>] Does anyone have the Slackware 1.2.0 distribution assembled into a
>] tar file? It would be nice to be able to snarf the whole thing without
>] having to do fifty cds, lcds, and mgets.
>
>cd to ftp.cdrom.com:pub/linux and do a "get slackware.tar".
>The resulting file is 75 meg...
**** I did this. Unfortunately, I didn't have space on my Sun workstation to hold both
the tarred file and the directories. So I wound up getting the stuff all over again,
directory by directory.
I dreamt of a script that would activate FTP, tell it to get slackware.tar, and pipe its
output straight up to tar on my machine, which would then spew out files and directories.
Probably an impossible dream......
- Jerry Kaidor ( jkaidor@synoptics.com )
------------------------------
From: akostyrk@track.cslab.tuwien.ac.at (Andreas Kostyrka)
Subject: SCSI troubles
Date: 30 Mar 1994 10:25:38 GMT
Hi,
yesterday at home I've got following error (on my new box)
scsi0: reseting for second half of retries
SCSI disk error: host 0 id 0 lun 0, return code 27070000
scsidisk I/O error: dev 0806, sector ???
This happened after a X-Crash, while checking the filesystem,
and the solution was to let the system cool down for 10 minutes,
afterwards it worked again.
My problem is that the X-Crash seems to repeat itself more often, but
thats another story. So what does this message mean?
My software:
Slackware 1.1.2 -> Linux kernel pl15f with PLIP compiled in and
without normal harddisk support, without SCSI support
except Adaptec 1542 support.
My Hardware:
SOYO (not sure about the name) VESA LB motherboard.
32MB RAM
2ser+1par I/O card.
SCSI controller: Buslogic 445 (is recognised as Adaptec 1542)
I/O adr: 330, IRQ 10/11 (not sure now, it's the default)
HD: QUANTUM ProDrive 1800 S
The kernel detects
QUANTUM PD1800S Revision 3162
Type: Direct-access Ansi-Rev. 2
Another thing: Sometime after a cold reboot the kernel just halt without any
messages at this time. This is not that big a trouble, because it happens really
seldom.
Thanx in advance for any suggestions,
Andreas
P.S.: I'll upgrade today to Linux 1.0 and see if the problem goes away.
--
\|/ \|/
(o o) (o o)
=============oOo==(_)==oOo=================oOo==(_)==oOo======
( Email:
* andreas@siegfried.smc.univie.ac.at [preferred]
* akostyrk@cslab.tuwien.ac.at
*
* FTP:
* siegfried.smc.univie.ac.at:/incoming/andreas
* (if you put something there, then please email me
* also a short note)
* [preferred] (compared to UUENCODE)
)
------------------------------
Crossposted-To: comp.os.linux.misc
From: mmnuk@risc.uni-linz.ac.at (Michael MNUK)
Subject: IDE disk contoller and segmentation faults
Date: Wed, 30 Mar 1994 09:40:06 GMT
I'm having problems when using gcc experiencing the well known SIGSEGV
when compiling the kernel. I consider this as a matter of the overall
stability of the hardware so I would really like to get rid of it. I
tried to play with some BIOS settings like wait states, AT bus speed,
etc., I got a new and more memory, to no avail.
Is there anybody who successfully eliminated segmentation faults by
replacing the HD VLB controller? Would you contact me please?
My hardware: 486-66 VLB, 16M RAM/16M swap partition, A7VL IDE controller,
IDE HD Maxtor 7345A; currently running Linux v1.0.
Michal
--
Michal Mnuk
Research Institute for Symbolic Computation
A-4040 Linz, Austria
Phone: +7236 3231 75
Fax : +7236 3231 30
E-mail: mmnuk@risc.uni-linz.ac.at
------------------------------
From: merlyn@winternet.mpls.mn.us (Doug McIntyre)
Subject: Re: Adaptec 2742T anyone?
Date: 29 Mar 94 21:22:37 GMT
In <CnEIJz.HrK@world.std.com> vandella@world.std.com (Vinny Andella) writes:
>David Rapchun (rapchun@suicide.sdsu.edu) wrote:
>: Hello, I understand there are some people working on writing a driver for
>: the Adaptec 7770 series chip. IE, the 2742 and 2842 both use this new chip.
>: I was just wondering how the work is coming along since I would really like
>: to run Linux soon. Thanx.
>I have a killer 486 66, with an Adaptec 2842 VL controller, I want to run
>Linux too. I got the CD 3 weeks ago and have been searching the internet
>for HELP !!!!!!
>Please send any information to vandella@world.std.com
>If a driver has not been developed yet please tell me the time frame for it.
No, its not ready yet. There is a person working on it (Scott Ferris), but
he hasn't had much time to work on it lately apparently. He says he will
be having more time in the upcoming weeks to do so..
--
Doug McIntyre merlyn@icicle.winternet.mpls.mn.us
Write to info@winternet.mpls.mn.us for more information about Winternet's
Internet services and dialups.
------------------------------
From: rick@discus.mil.wi.us (Rick Miller)
Subject: How To Cross-Compile for DOS?
Date: Wed, 30 Mar 1994 07:10:42 -0600 (CST)
Can someone tell me how to cross-compile something under Linux
to be run under DOS? I'm really getting sick of Quick-C...
Best wishes,
<rick@discus.mil.wi.us> Rick Miller
------------------------------
From: rene@renux.frmug.fr.net (Rene COUGNENC)
Subject: Re: _NEED_SHRLIB_libc_4 ? I have libc.so.4
Date: 29 Mar 1994 11:55:59 GMT
Reply-To: cougnenc@hsc.fr.net (Rene COUGNENC)
Ce brave Brad Hull ecrit:
> When I attempt to link a number of things, such as pppd or xrn, I get a
> messages stating that there are multiple definitions of _NEEDS_SHRLIB_libc_4
> in /usr/lib/libgcc.sa and /usr/lib/libc.sa. I tried the obvious things: I
Remove /usr/lib/libgcc.* as stated in the release notes of the libraries...
--
linux linux linux linux -[ cougnenc@renux.frmug.fr.net ]- linux linux linux
------------------------------
** 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
******************************