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

624 lines
22 KiB
Plaintext

Subject: Linux-Activists Digest #200
From: Digestifier <Linux-Activists-Request@senator-bedfellow.MIT.EDU>
To: Linux-Activists@senator-bedfellow.MIT.EDU
Reply-To: Linux-Activists@senator-bedfellow.MIT.EDU
Date: Fri, 3 Sep 93 17:13:16 EDT
Linux-Activists Digest #200, Volume #6 Fri, 3 Sep 93 17:13:16 EDT
Contents:
Re: Slackware installation Q? (Chris Cannon)
Problems with NET-2 and pl12
Re: Linux and Tcsh: Soooo Funny!! (A Joke) (Otmar Lendl)
Linux and OS/2 2.1 Boot Manager Co-existence. How? (Chuck Wegrzyn)
xvt (Bob Willard)
xvt (Bob Willard)
video cards (Peter P Chiu)
Will Linux run MSDOS applications (which use DMA/interrupts)? (Stan A. McClellan)
NeXTStep & Linux (Ullrich Martini)
xvt (Bob Willard)
What is QIC02? Mountain Mach 2? (Eric Kimminau)
Re: how do you uncompress zImage ? (Theodore Ts'o)
Re: [HELP-please] Kernel panic/swapper more info (Theodore Ts'o)
Re: OS/2 2.1 Boot mMgr and Linux (Mike Mills)
Re: xvt (Thomas Pfau)
Re: BSD UNIX (Michael L. VanLoon)
Re: dosemu won't work (Derek Bischoff)
Re: eth0: Receiver overrun (Derek Bischoff)
X386 mice and restart (Derek Bischoff)
----------------------------------------------------------------------------
From: cannon@mksol.dseg.ti.com (Chris Cannon)
Subject: Re: Slackware installation Q?
Date: Fri, 3 Sep 1993 14:37:38 GMT
Ken Geis (bogart@ucsee.Berkeley.EDU) wrote:
: So, I understand that the Slackware release comes on 3.5" disks.
: Is there any way to make a 5.25" bootstrap disk or any other easy way to
: install from a 5.25 A: and 3.5 B:? Thanks in advance,
You may not want to hear this, but you can swap y your floppy
cables to make a: the 3.5". Thats what I did. Don't forget the
bios setting, if you have one.
--
===================
cannon@lobby.ti.com
------------------------------
From: pramod@radon.ece.uiuc.edu ()
Subject: Problems with NET-2 and pl12
Date: 3 Sep 93 10:28:10 GMT
Hi,
I have been having some strange problems with pl12. From some
previous problems I see that the new kernel is stricter with routing etc.
Here is a synopsis of the problems.
1. I can't get access to machines on the local network. All machines outside
of the local net are fine. On checking netstat I find that my machine does
realize that another machine is trying to make a connection and it gives
a SYN_RECV but then hangs. I have gotten aroung this problem by directly
putting the ip addresses of the local machines into the routing table. Is this
the correct way of including machines on the localnet ? By the way I am using
a remote nameserver and a gateway to the outside world. in.telnetd processes
are also started for each connection that tries to get through.
2. After reading NET-2-FAQ and trying to follow it through I am also having
problems. The FAQ specifies that the loopback and at least the local net
should be specified in /etc/networks. I have found that if my local net is
included in /etc/networks, all the route add commands end up with a
SIOADDRT: Network is unreachable error. And the routing table ends up with
a route localnet that cannot be removed. If the localnet entry is deleted
from /networks then the routing table is okay.
3. After the daemons ( nfsd , routed etc) are run the routing table is
modified vs. looking at the routing table without running the daemons. Is
that to be expected ?
4. I have found that telnet sessions to the linux machine crash consistently
while running NCSA Telnet 2.5b for the Macintosh. The PC versions of NCSA
telnet and pctcp's tn all seem to work fine. ?????
Any advice and assistance would be appreciated. Is there a book or docs out
there yet other than NET-2-FAQ that go into more detail about TCP/IP routing
networks, etc ?
Thanks,
Pramod John
------------------------------
Crossposted-To: comp.os.linux.misc
From: lendl@cosy.sbg.ac.at (Otmar Lendl)
Subject: Re: Linux and Tcsh: Soooo Funny!! (A Joke)
Date: Fri, 3 Sep 1993 16:59:29 GMT
In article <265t08$cpk@max.physics.sunysb.edu> paul@pbunyk.physics.sunysb.edu () writes:
>In some Unixes on 'make love' make answers "I don't know how to make love..." -
>unfortunately, GNU make adds some unnecessary punctuation.
>
On my sun I added the lines
love:
@echo "... not war."
to the /usr/include/make/default.mk file.
This results in the following response:
15 lendl@orca:-> make love
... not war.
>Sorry for non-linux posting...
>
s/>//
otmar
--
| Otmar Lendl (lendl@cosy.sbg.ac.at) | University of Salzburg / Austria |
| I'm thinking of having my whole body surgically removed. --Lintilla |
------------------------------
From: wegrzyn@nic.cerf.net (Chuck Wegrzyn)
Subject: Linux and OS/2 2.1 Boot Manager Co-existence. How?
Date: 3 Sep 1993 17:41:56 GMT
Hello. I am trying to get Linux to co-exist on my OS/2 2.1 machine
by using the OS/2 Boot Manager. I am having troubles.
When I boot off the Yggdrasil floppy (and use the CDROM), things
go right -- I can boot up. When I log into INSTALL, and prepare to
update the partition info on the disk, it tells me it can't read
device 0800.
I am using a clone 486/25 CONTAQ motherboard, 32Mbytes of RAM, 256KB
cache, Adaptec 1542B SCSI controller with a 240MB Maxtor drive.
Does any one know what I am doing wrong? Or what I should be doing?
Many thanks for your time,
Chuck Wegrzyn...
------------------------------
From: bwillard@eskimo.com (Bob Willard)
Subject: xvt
Date: Thu, 2 Sep 1993 20:47:35 GMT
------------------------------
From: bwillard@eskimo.com (Bob Willard)
Subject: xvt
Date: Thu, 2 Sep 1993 20:59:19 GMT
Has anyone ported xvt to linux?
------------------------------
From: ppc2@cec2.wustl.edu (Peter P Chiu)
Subject: video cards
Date: Fri, 3 Sep 1993 18:21:44 GMT
Can anyone suggest some video cards that are good for both X and MS windows?
right now, i have a Diamond Stealth Pro and i don't know how to get it to
work with X.
Could someone please let me know?
Thanks
--
.&______~*@*~______&. m Peter Chiu
"w/%%%%%%%%%%%%%%%%%%%\w" mmm*** Washington University, St. Louis
`Y""Y""Y"""""Y""Y""Y' mm***** ppc2@cec2.wustl.edu
p-p_|__|__|_____|__|__|_q-q mm**Y** 275 Union Blvd, #711, St. Louis,
_-[EEEEM==M==MM===MM==M==MEEEE]-_.|..|.... Missouri 63108 (314) 367-3599
------------------------------
From: sam3103@tamsun.tamu.edu (Stan A. McClellan)
Crossposted-To: comp.os.linux.help,comp.os.linux.misc
Subject: Will Linux run MSDOS applications (which use DMA/interrupts)?
Date: 3 Sep 1993 13:31:51 -0500
We like everything I've heard/read about Linux, and we are considering
installing it on our PeeCees here. However, we have some reservations ...
We're hoping somebody in these newsgroups can clear this up for us.
We have several MSDOS applications which use add-on DSP/A-to-D boards and
we don't want to lose this functionality if we convert to the Linux
environment.
(1) How does Linux deal with MSDOS applications? Is it reliable?
Can it support real-time applications such as A/D and D/A?
(2) Will any special drivers need to be written/installed for Linux to
run MSDOS applications which do low-level I/O? If so, I assume that
software like this is application-specific. Is this correct?
(3) If the DOS emulator currently won't handle these situations, is there
work underway to address this, or am I hoping for too much from Linux?
Thanks for any and all info.
--
--
Stan McClellan Research Assistant
mcclella@eemips.tamu.edu Texas A&M University
323A WERC Dep't of Electrical Engineering
409/847-9493
------------------------------
From: martini@tournesol.hep.physik.uni-muenchen.de (Ullrich Martini)
Subject: NeXTStep & Linux
Date: Fri, 3 Sep 1993 18:52:31 GMT
hi,
we here a lot about running ms-windows apps on linux boxes, but there are
much better user interfaces than windows, for example NeXT Step. this is
why i am wondering if there are any activities to build a next-linux
interface like wabi.
maybe it would be sufficient to have a source-code compatibility. is it true
that the objective-c compiler used by next is available and ported to linux?
(heard something like that)
bye, ullrich
------------------------------
Subject: xvt
From: bwillard@eskimo.com (Bob Willard)
Date: 3 Sep 93 14:45:24 +0600
Message-ID: <CCqvGD.Cut@eskimo.com>
Organization: Eskimo North (206) For-Ever
Date: Thu, 2 Sep 1993 20:59:19 GMT
Lines: 1
Has anyone ported xvt to linux?
------------------------------
From: ekimmina@pms709.pms.ford.com (Eric Kimminau)
Subject: What is QIC02? Mountain Mach 2?
Date: 3 Sep 1993 19:03:57 GMT
> As you can see, your "QIC36" card is really something that is QIC02 on one
> end and QIC36 on the other.
>
> It does not pay to cut corners :-) I should have elaborated in the original
> post. Hope that is accurate enuff for you now...
>
> Sorry,
> Remco
What are some examples of "QIC02" cards? Is the Mountain Mach2 contrller a
QIC02? Anyone? Class?
--
Eric Kimminau Workstation Systems Department
313-322-3431 Product & Manufacturing Systems
ekimmina@pms709.pms.ford.com Ford Motor Co.
Planning and Implementation "Not an official Ford Spokesperson"
------------------------------
From: tytso@athena.mit.edu (Theodore Ts'o)
Subject: Re: how do you uncompress zImage ?
Date: 3 Sep 1993 15:37:01 -0400
Reply-To: tytso@athena.mit.edu (Theodore Ts'o)
From: bone@uncledad.nwscc.sea06.navy.mil (Mike Bone)
Date: 2 Sep 1993 11:12:39 -0500
I'm just updated to SLS 1.03 and I need to an uncompressed kernel image
to use for bootlin. How can I uncompress the zImage file in the root
directory? Can this be done without the kernel source?
bootlin should be able to work using the zImage file; have you tried
this?
Otherwise, there is no way short of recompiling the kernel from source.
- Ted
------------------------------
From: tytso@athena.mit.edu (Theodore Ts'o)
Subject: Re: [HELP-please] Kernel panic/swapper more info
Date: 3 Sep 1993 15:38:52 -0400
Reply-To: tytso@athena.mit.edu (Theodore Ts'o)
From: ajoseph@is.morgan.com (Adrian Joseph)
Date: Fri, 3 Sep 1993 09:43:37 GMT
There are a few minor variations on this including the apsence of the first
line, this being replaced with
general protection: 0000
and occationally something like
NMI received - Dazed and confused trying to continue
The NMI received message could be caused by a memory parity error.
Given all of your other symptoms, it sounds like your memory is
seriously scrod. Are you sure your SIMMS are of the right speed for
your clock speed?
- Ted
------------------------------
From: sam@ms.uky.edu (Mike Mills)
Subject: Re: OS/2 2.1 Boot mMgr and Linux
Date: Fri, 3 Sep 1993 19:40:54 GMT
person@plains.NoDak.edu (Brett Person) writes:
>In article <1D71C4D0HW@tron.gun.de> cindy@tron.gun.de (Holger Wiese) writes:
>>Am 26.08.93 um 03:35 schrieb IKS%BSU-CS.BSU.EDU@USENET.ZER unter dem Betreff OS/2 2.1 Boot mMgr and Linux:
>>
>>
>>i have tried successfully two ways to use OS/2 and Linux
>>together. But it seems to be unpossible to boot Linux from
>>the OS/2 Bootmanager directly. So try one of the following
>>two ways.
>Slackware will automatically install for Boot Manager and will boot Linux
>directly from the boot manager.
>--
>Brett Person
>Guest Account
>North Dakota State University
>person@plains.nodak.edu || person@plains.bitnet
I have 2 IDE drives and one SCSI drive. Since I have 2 IDE drives, my SCSI
drive is NOT controlled by the adapter BIOS. It takes a driver to use it.
As I understand it, OS/2 Bootmanager doesn't understand SCSI that isn't
controlled by the adapter BIOS. OS/2 apparently can't even boot off the
SCSI drive in this situation, because it doesn't understand SCSI (thats not
controlled by the adapter bios) until the device driver gets loaded.
I don't know if this is true or not, it just seems to be the case - can
someone enlighten me on this?
Thanks,
--
--Mike Mills E-Mail: sam@ms.uky.edu, {rutgers, uunet}!ukma!sam
--UK Math Sciences Dept. mike@ukpr.uky.edu
--(606) 257-1429 (work) 263-0721 (home)
------------------------------
From: pfau@coffee.enet.dec.com (Thomas Pfau)
Subject: Re: xvt
Date: 3 SEP 93 15:43:01
In article <1993Sep3.144524.597@nhqvax.hq.nasa.gov>, bwillard@eskimo.com
(Bob Willard) writes...
>Has anyone ported xvt to linux?
If you can't find xvt, look for rxvt. It's slightly more stripped down.
tom_p
======================================================================
pfau@coffee.enet.dec.com | Mapmaker's disclaimer:
16.69.208.195 | 'Not responsible for topographical
Compuserve: 73303,1136 | errors.'
======================================================================
------------------------------
Crossposted-To: comp.unix.bsd,comp.os.386bsd.misc
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: BSD UNIX
Date: Fri, 3 Sep 1993 19:27:02 GMT
In <MUTS.93Sep2205147@compi.hobby.nl> muts@compi.hobby.nl (Peter Mutsaers) writes:
>I am puzzled a bit by all the Net/386/Free BSD releases. This is a
>pity. At the moment I use Linux with very good result, but I 'grew up'
>with BSD and disliking SYSV. Therefore I would actually rather see a
>real BSD become the widespread and maybe defeat SYSVR4 in the end.
>However at the moment Linux has, I think, more coordinated development
>and therefore has a better defined standard and faster development. I
>wish the net/386/free BSD community(ies?) could agree more and make
>their Unix more unified and better.
Actually, from what I can gather, the only one not coordinating is
Bill Jolitz himself, since he refuses to let anyone see anything til
he decides to grace the world with his next new great release. It's
been over a year since his last year.
On the other hand, the NetBSD and FreeBSD development groups
cooperate, and in fact, share code and new developments with each
other. They're on quite friendly terms and have a "working"
relationship.
I run NetBSD. I love it and will not move to anything else unless
something truly momentous were to happen elsewhere. This is my
opinion.
The main differences are: 386BSD, the core of them all. NetBSD and
FreeBSD are derivatives of the original 386BSD work. 386BSD hasn't
been improved in over a year by its author, but has a "patchkit" that
helps it along. I would view this as a tedious and masochistic system
to install.
FreeBSD is the patchkit taken to an entirely seperate release. It's
fairly close to the original 386BSD for those who want to stay there,
but with mucho bug fixes and upgrades.
NetBSD is a completely current work apart from 386BSD. Although its
original source started with 386BSD, the massive amount of changes to
the kernel and other things qualify this as a totally seperate system.
The NetBSD maintainers have stated a few main goals (from *my*
understanding): a) The most stable, bugfree, production quality
release possible in a free unix, b) As complete as possible compliance
with 4.3BSD and Net/2, c) Incorporate as much of 4.4BSD as possible,
as it evolves, d) Buildable on as many architectures as possible
(386/486 currently in production, Amiga & HP300 in beta, many others
in alpha testing).
All three are true BSD unixes and are based on 4.3BSD for the most
part. They all also incorporate Berkeley Net Release 2 networking
code to a varrying degree (the stuff in 4.3 and 4.4BSD).
I hope I haven't erred too much in my analysis. :-)
Linux is a completely different beast. I haven't installed it and I
don't want it, but I know people who run it. It works for certain
people, and more power to them. We're all different. :-) Linux is not
based on any particular pre-existing unix, but is a built-from-scratch
OS designed to be posix compliant, and SysV/BSD compliant where
possible. It's development is a bit more erratic, but productive.
It's kernel structure is not as clean, having had things piled on top
to add functionality many times. Until recently, its networking was
not at all complete. They have recently adopted Net/2, but it is
still somewhat buggy. The advantage of Linux is that it has shared
libraries so uses much less memory and disk space. Also, its rumored
to co-exist with DOS better, but this may be more opinion than fact.
--
==============================================================================
Michael L. VanLoon Project Vincent Systems Staff
michaelv@iastate.edu Iowa State University Computation Center
==============================================================================
------------------------------
From: Derek.Bischoff%f1.n3641.z1@psybbs.durham.nc.us (Derek Bischoff)
Subject: Re: dosemu won't work
Date: 3 Sep 93 16:52:00 GMT
u> Hello,
u> I got Linux working just fine! and everything is hunkydory until I
u> tried running the dosemu thing. when I type dos* it doesn't run
u> but I get lots of errors. I can't find any literature on t, but if
u> anyone out there has it working, I would appreciate some advice.
u> I'm kinda afraid to run the programs in the dosemu directory without
u> knowing what they do exactly. I had enough problem installing Linux
u> and I don't wanna trash the partition or something so son.
u> so thanks
u> and please email!
u> J
Hello back.
I wouldn't consider what I have as a working dos system.(yet)
but I just got it to respond correctly yesterday.
this is the jist of a README file I had in my release:
mount your dos partition to /usr/dos
format a dos system disk, no autoexec.bat or config.sys
put it in your drive.
My existing dos binary was screwed up for some reason, so
I just rm'd it and ran make in /usr/src/dosemu
staying in that dir I ran ./dos > /dev/null
this caused my a: to whirl, and I had dos 5.0 on A:
go to C: drive, and run "LINUX.EXE D"
this puts what ever partition that is mounted to /usr/dos
on your "D:" drive.
that is as far as I have gotten. Can't run much, but it is
definitely dos.
... Sincerely, Derek
------------------------------
From: Derek.Bischoff%f1.n3641.z1@psybbs.durham.nc.us (Derek Bischoff)
Subject: Re: eth0: Receiver overrun
Date: 3 Sep 93 16:54:01 GMT
SB> Maybe this is a FAQ, but the problem is very serious and I couldn't
SB> find any help. I've 2 machines running Linux (386/25 8MB, 486/33 16MB).
SB> Both of them upgraded to SLS 1.03 with 0.99pl12 kernel. The ethernet
SB> cards are an old 8003 8-bit WD card and an Elite 16. Directly after
SB> rebooting the messages: eth0: Receiver overrun
SB> or
SB> eth0: Couldn't allocate a sk_buf of size 282
SB> occurs on both machines. What can I do to fix this?
SB> I tried different settings for the ther cards but nothing changed :(
Look for a README file that describes eth_if (I am away
from my Linux box, so I can't do it for you)
I recall that I had to change eth_0 to eth_if in one or more of the
files to get my 3c503 card to work. If I didn't I had the same
results you have now.
... Sincerely, Derek
------------------------------
From: Derek.Bischoff%f1.n3641.z1@psybbs.durham.nc.us (Derek Bischoff)
Subject: X386 mice and restart
Date: 3 Sep 93 17:25:02 GMT
Hello folks.
I am not on the Internet, and have to comb the bbs's
about to find any information that I need.
With much heartache, headache, and a few cartons of
cigarettes, I have successfully configured my display
to show me X. And let me start off by saying, I am impressed!
this looks at least as good as Xview, which I spent megabucks
for. I do however have a few problems to clear up, and
hope that someone would be good enough to give me some feedback.
First, I am running a HP 386/25 with 12Meg ram.
I have SLS 1.0, running 0.99.pl6-30
I have tcp/ip running well, with a 3c503 card attached.
I have (your choice) a HP Bus mouse (the old style, not ps/2)
and a microsoft serial mouse.
1. my Serial ports are autoconfigure in the kernel and they come up
with the same memory and IRQ as MSD.EXE does.
whether or not my Xconfig file says :
Busmouse "/dev/mouse"
Microsoft "/dev/ttys0" or
Microsoft "/dev/ttys1" I get the same response:
When I run X I can see the mouse cursor, but it just does not respond.
2. as I said, tcp/ip works great. (what performance!) however
when I run X it says "Setting TCP SO_LINGER: Protocol not available.
no SIOCGIFCONF
Where did I go wrong?
3. when I do a ctrl-alt-F2 to get another screen, it works great.
how do I jump back to tty1? that is , w/o getting the text config
screen. (I want to return to X)
4. Lastly, I have literally, 4 3 ring binders of FAQ's and README's
(my wife thinks I'm nuts, and I should just buy Unix if I want it)
But I enjoy seeing the ins and outs, being I admin SCO and HP/UX at
work, and know little about how everything works together.
Is there a FAQ that focuses on troubleshooting? Linux
has many verbose errormessages, and if I knew where to look
when I get one, it would have aided my installation.
Oh, and thanks to all that helped make Linux possible. I hope
to do serious development soon on it so I can donate to the cause
as well.
(PS if anyone gives me an Internet address to find info,
again, I have no access. Would someone please put up a BBS
that remains quit current? I will call just about anywhere
in the US)
Thank you to Unix people of vision. :)
... Sincerely, Derek
------------------------------
** 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.99pl9 released on April 23, 1993
End of Linux-Activists Digest
******************************