HDTenEightyP/NetNews huggingface dataset:
From: peters@mips2.ma30.bull.com (Dan Peters)
Newsgroups: comp.os.linux
Subject: SLS Good, but...?
Date: 31 Aug 92 16:15:59 GMT
Distribution: comp
Organization: Bull HN Informations Systems Inc.

Hi,
	I am another person grateful for the SLS linux distribution.
	I installed the full set of 15 disks with just a few tricky spots.
	
	Linux is up and running, but my X server starts and quits.

	gwm is complaining about the missing 'mwm' file.

	looking at the .xinitrc file in the user1 home directory I see
	gwm invoked as follows (from my memory):

		gwm -rf mwm

	Anyway, I don't have any docs on gwm, I guessed that this was
	some sort of .mwmrc and copied '/usr/lib/X11/gwm/mwmrc.gwm' file
	to the home directory as 'mwm'.

	Now X starts to come up (blue screen background, xclock) then
	quits, with gwm complaining about error in profile.
	I believe he complains about several lines in this file I copied.
	Well, after deleting several lines in that file I copied, the complaint
	from gwm is 'Screen not defined'

	I am guessing here and have no docs for gwm.
	I left the exact info home, so my details may be sketchy.
	I am hoping that someone will recoginize and reply with a
	helpful suggestion.

	I really like the SLS distribution, found it easy.  Just this
	one problem (it looks like a simple one too).

	Two other things I noticed upon intallation:

		/tmp was writable only by root and vi could not start;
		(I changed the permissions and vi is fine)

		/home/user1 (home directory for user1) was also
		writable only by root (again changed the permissions
		and al is well)

	Again good job with SLS and thanks in advanced for any help,


	Dan Peters

-- 

== Dan Peters		 	Bull HN Information Systems Inc.
== (508) 294-3325 (294-3705)	300 Concord Road    MA30/MS850A
== D.Peters@bull.com		Billerica, MA		01821
Newsgroups: comp.os.linux
From: Kevin W. Hammond <hammond@kwhpc.caseng.com>
Subject: Re: Killing background processes on logout
Reply-To: hammond@kwhpc.caseng.com
Organization: The Internet
Date: Tue, 1 Sep 1992 23:39:59 GMT

| 
| In comp.os.linux you write:
| 
| >My best guess would be that when either X or the cmdtool exits, they are
| >killing background processes.
| 
|     Well, of course, any X clients will exit, because their connection
| to the X server will be broken and they'll freak.  If you run X on Linux
| and exit with clients running (even those started with "command &" from
| csh), you'll see Xlib error messages on the normal console after the X
| server exits from each of the clients.
| 
| >So, I stand (sit) corrected.  I now fully share the belief that the csh does
| >not kill background processes on exit.  Thank you everyone for helping me
| >to see the light!  :-)
| 
|     No problem.  :-)  The man page for csh would have done it quite some
| time ago, actually.
| 

Not necessarily so ... I fired up the man pages on my csh at work (SunOS) and
they did not mention it.  Of course, I don't have the man pages for the linux
tcsh, so that may be where I've gone wrong!  :-)

-kwh-
-- 
Kevin W. Hammond
hammond@kwhpc.caseng.com

  CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161
Newsgroups: comp.os.linux
From: hfaester@Physik.TU-Muenchen.DE (Hannes Faestermann)
Subject: Re: SLS: don't laugh now but...
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
Date: Thu, 27 Aug 1992 12:06:25 GMT

lynch@ccwf.cc.utexas.edu (Tom Lynch) writes:

>>From: pmacdona@sanjuan (Peter MacDonald)
>>although it is not clear that everyone will want to spend the 
>>~$400.00 (??) or so buy a player and the CD.  Maybe though.

>I do I do, imagine most of the hardisk just for user data!
>wow.. 

>Programs that should be on a CD distribution IMHO :-)

...bunch of reasonable utilities deleted...

>I must be missing a bunch of things.  Is there already a distribution
>wish list available?  Perhaps others could add to this.

I miss especially Larry Wall's famous perl in the programs...

Nice thing, SLS, though.

	Hannes

--
Hannes Faestermann           |  Internet: 
Physik-Department E17        |   Hannes.Faestermann@Physik.TU-Muenchen.DE
TU Muenchen,                 |  
8046 Garching, West Germany  |
From: hammond@kwhpc.caseng.com (Kevin W. Hammond)
Newsgroups: comp.os.linux
Subject: Speed of 0.97
Date: 31 Aug 92 01:12:04 GMT
Reply-To: hammond@kwhpc.caseng.com
Organization: The Internet

Now that I've upgraded to 0.97pl2, I can put in my two cents worth about the
speed issues...I don't have any exact timings, but 0.97pl2 is definitely faster
than 0.96a.  I didn't bother to stop at 0.97pl1, so I can't interject about
pl1 vs. pl2, but i do like pl2.

I'm running linux on a 20 MHz 386sx with 8 MB (no swap) and a 40MB MFM drive on
an RLL controller.  Though it takes me the better part of an hour to compile the
kernel, (I *really* envy those of you who can compile it in under ten minutes!!!!)
the OS as a whole is fantastic.  If I can get X11 up and running, I'll almost have
no reason to into work anymore!! :-)

-kwh-
-- 
Kevin W. Hammond
hammond@kwhpc.caseng.com

  CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161
From: axlas@acad2.alaska.edu (Leif A Sawyer)
Newsgroups: comp.os.linux
Subject: Re: Linux still doesn't recognize my RLL drive
Date: 4 Sep 92 14:42:20 GMT
Organization: Bit for Tat Consulting

In article <1992Sep4.133839.14356@osf.org>, ede@kadabra.osf.org (Ted Ede) writes:
> 
> I used to have a wd1002-27x attached to my st238 30 meg drive.
> I was told linux doesn't support XT controllers, which I assumed
> to mean 8-bit controllers.
> 
 I would Imagine this is the correct view..  Linux does all its work
in 16 bit mode (save, I imagine, the serial/parallel ports).

> I installed it, configured it for my 238 and low level formatted it
> and it boots DOS properly.  Linux still does not recognize it.
> What exactly is linux looking for?  Does anyone in Linux-land use
> an RLL drive?  (Can't imagine I'm the only one.)  If so could you
> tell me the adapter that you use?
> 
 I've got a WD clone board with floppy controller built in.  Don't know
who makes it..some overseas company. Never had a problem with it.

> I have a 386/40 with AMI bios.  I have to tell the system the C:
> drive is not installed in order to boot of this drive.  If I configure
> it as a user defined drive giving it the proper number of head/cyls/
> sectors, I get a HD Error on boot.
> Thanks,
> ted

Check the HD controller to see if you have a jumper to enable/disable the
BIOS on the card.  I believe you have to have the BIOS *DISABLED* to use
a user-defined drive type (46?).  This is how I have my drive set up, I
believe, but I am at work, so can't open up the case to double-check.

I DO know, however, that if you have two HD controllers, the second one HAS
to have the BIOS enabled, because you cannot have it listed in the System BIOS.

 /* 
  Linux wish! -> Detect and use secondary controllers! Four hard drives would
be nice for those of us who can't afford to spend $800+ on big hard drives, but
can shell out $50-$100 for a used 30Meg drive.  If I knew more about system
level writing I'd try my hand at it.. C'est la vie.
 */


=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
| Leif Sawyer -= AXLAS@acad2.alaska.edu | Owner - Bit for Tat Consulting    |
| Try these also -= ASLAS@acad3.alaska.edu | BITNET -= AXLAS@alaska.BITNET  |
| USnail -= 3631 E. 42nd Circle #7 Anch, AK 99508 |  #define FLAME /dev/nul |
| "Views expressed by moi are not necessarily those Defined by my employer" |
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
Newsgroups: comp.os.linux
From: minyard@crchh453.bnr.ca (Corey Minyard)
Subject: Re: VM386?  Possible?
Reply-To: minyard@bnr.ca
Organization: BNR
Date: Tue, 01 Sep 1992 18:57:07 GMT

In article <la78t4INN738@appserv.Eng.Sun.COM>, lm@slovax.Eng.Sun.COM (Larry McVoy) writes:
|> Forgive my ignorance, but is it possible to run a 386 program on a
|> virtual 386 on a real 386?  The reason I ask is this: aren't a lot 
|> of dos programs running in 386 mode?  So even if you got VM86 working
|> and got a dos emulator running, wouldn't things like windows apps
|> not run at all?  Or is everything still running as an 8086?
|> 
|> Thanks.
|> ---
|> Larry McVoy                  (415) 336-7627                   lm@sun.com

Unfortunately, no.  The problem comes in with the PUSHFD/POPFD 
instructions.  PUSHFD will put the status register (including processor
mode) onto the stack.  POPFD will restore the status register from
the stack.  If in supervisor mode, POPFD will restore the processor
mode bits (VM86, I/O priv, etc.).  If not in supervisor mode, POPFD
will not trap but it will not restore these bits.  So, there is no
way for a virtual machine control program to know if the program
running in the virtual machine is looking at the processor mode or
trying to change the processor mode via these instructions.

I guess you could write a full 386 simulator, but that would not
be terribly fast.

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

Corey Minyard
From: pspeer@cradle.UUCP (Sysop)
Newsgroups: comp.os.linux
Subject: Beginner questions
Date: Tue, 01 Sep 92 13:09:12 EDT
Organization: Cradle Consulting - Columbus, OH

I have just recently installed the SLS package on my PC. Version 0.96 full
base and X11. Everything has gone fairly well but I have a couple of problems
that I could use some help on...

1) Under X11 I have 640x480 running fine however I can't seem to get things
set correctly for 800x600 or 1024x768. I have one of the original Diamond
SpeedSTAR VGA boards and a MAG PMV1448 monitor. I am able to run these high
resolutions under Microsoft Windows with no problems so I assume I am not
setting things up correctly in Xconfig. The specs on these are:

Monitor - Bandwidth 65MHz, Vertical scan freq. 50Hz to 90Hz, Horizontal scan
          freq. 30KHz to 32 KHz and 47KHz to 49KHz (Dual-freuency monitor).

Board - Clock.exe reports clocks of 25MHz, 28MHz, 45MHz and 64MHz.

I tried numerous configurations and finally had to lie and say I had a 31MHz
clock to get 640x480 to work, however I cannot get the others. If anyone has
correct settings or can help I would appreciate it.

2) I want to upgrade to version 0.97, can I simply upgrade or will it require
a complete re-install? Any docs available on how to go about it?

3) Lastly, I currently have a 386DX-25MHz system w/o co-processor. I want to
speed X11 up and was wondering which of the following (I can't afford them
all) would provide the greatest speed increase.

    387 math co-processor
    Diamond Stealth video board
    more memory (I have 4 megs now)

Thanks for your time!

******************************************************************
Patrick Speer       -----------   pspeer@ohstpy.mps.ohio-state.edu
Cradle Consulting   -----------   pspeer@cradle.UUCP
From: hlu@poly2.eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.os.linux
Subject: Re: Does a 387 help Linux's performance?
Date: 1 Sep 92 20:11:49 GMT
Article-I.D.: serval.1992Sep1.201149.29493
Organization: Washington State University

In article <1992Sep1.160537.11089@afterlife.ncsc.mil>, swaliff@afterlife.ncsc.mil (Steve Aliff) writes:
|> I have a 33MHz 386DX. Would it improve my system performance to add
|> a 387? I plan to run X11 on top of Linux if that makes any
|> difference.
|> -- 
|> Steve Aliff (swaliff@afterlife.ncsc.mil [144.51.1.1])

Get a 387 if you consider X11.

H.J.
From: ching@angelo.amd.com (Mike Ching)
Newsgroups: comp.os.linux
Subject: Re: Beta TCP/IP
Date: 27 Aug 92 22:01:28 GMT
Organization: Advanced Micro Devices, Santa Clara, CA

In article <714839549snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes:
>In article <1992Aug25.233806.11161@morrow.stanford.edu> bir7@leland.Stanford.EDU writes:
>
>   Currently only the Western Digital Ethercard Plus and compatibles
>   are supported (wd80[01]3 boards).  If you have a different ethernet
>   board you will either have to write your own driver or wait until
>   someone else does (There is someone who claims to be working on
>   drivers for many different ethernet boards.)
>
>Yes.  I'm going to get a NE2000 driver going first, because they're
>so ubiquitious and cheap.  Any votes for what comes after that?
>3Com's brand new 3c509 is a pretty high-tech card...
>
>-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
>Crynwr Software            Crynwr Software sells packet driver support.
>11 Grant St.               315-268-1925 Voice
>Potsdam, NY 13676          315-268-9201 FAX


My biased vote would be for a PCnet-ISA driver (it's the NE2100 card
in a chip). It's a high performance bus master ethernet chip which
we are agressively designing into PC motherboards. Depends on whether
you're interested in existing systems or future systems.

Mike Ching
Newsgroups: comp.os.linux
From: rgb@esleng.ocunix.on.ca (Richard Briggs)
Subject: Re: problems getting X running
Keywords: X11 configuration bourne shell script testing tool
Organization: Excalibur Systems Limited, Kanata, Ontario, Canada
Date: Tue, 25 Aug 1992 18:43:49 GMT

In article <1992Aug24.204326.8604@julian.uwo.ca> klode@syslab.csd.uwo.ca (Claude Morin) writes:
>In article <Aug.19.22.38.33.1992.8120@athos.rutgers.edu> hedrick@athos.rutgers.edu (Charles Hedrick) writes:
>>rgb@esleng.ocunix.on.ca (Richard Briggs) writes:
>>
>>>Hi Linux'ers:
>>
>>>Any time I try to initialize, the screen goes dead and a terminal on a serial
>>>port is the only feedback I've been able to get aside from capture files. 
>
>I've had the same problem with MGR and X11.  Configuring either one is
>incredibly frustrating because of the need to capture output blindly, then
>reboot if things go wrong.  I got so sick of this a few months ago that
>I wrote the following (tiny) script.

As I said this wasn't a problem, as I had a pc beside to use as an ASCII
terminal, but I had no idea where to go from the error messages.
>
>BTW, I would appreciate it if someone would post at least one followup to this
>article, since I'm not sure my postings are making it out into the world.
>
I found the problem, which was in fact the Modes line missing or commented
out....in any case, the clocks and modes could not talk.  All fixed :-)

	Thanks, Richard
>---
>Claude Morin
>(that's "klode", NOT "clod"...French :-)
>London, Ontario, Canada

-- 
__________________________________________________________________________
 Richard Guy Briggs         |   briggs@aix1.uottawa.ca
 Excalibur Systems Limited  |   rgb@[esleng|excalibur].ocunix.on.ca
 Kanata, Ontario, Canada    |   [esleng|excalibur]!rgb
From: hedrick@athos.rutgers.edu (Charles Hedrick)
Newsgroups: comp.os.linux
Subject: Re: Linux-Activists Digest #86
Date: 3 Sep 92 19:59:10 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

allredkl@choc01.dnet.dupont.com (Kevin L. Allred, 615-875-7167) writes:

>1% packet loss.  I exchanged mail with Ross Biro about the problem,
>and he told me that current linux TCP/IP code doesn't slow down the
>rate at which it send packets even when it receives a signal from the
>router to do so.  He says that the linux host is probably overloading
>the router with packets, thus producing hung connections.  He
>suggested a temporary solution that works by cripling the server so it
>can't send packets too fast, but I am reluctant to try this approach.

>A better approach would be to fix the server so it payes attention to
>router signals to slow down.  I looked at the net source code for a
>a little while, but it was clear that it is going to take deep
>understanding to add this type capability.

Actually, the current feeling among TCP/IP experts is that it's a
mistake to pay attention to ICMP source quench, which I assume is what
you're referring to.  Instead, you want to keep track of round trip
times and packet loss rates, and set your retransmission times and
local window based on them.  There's a fairly simple set of code from
Van Jacobson to do this.  These algorithms are now used in most TCP
implementations.  Currently it looks like the Linux TCP doesn't
compute round trip times at all.  I assume it's got a hardwired RTT
that is appropriate for Ethernet.  The SLIP implementation that people
are working on is going to have to fix this, or they're going to get
very odd results.

The necessary algorithms are listed in the TCP section of RFC 1122.
Those point to other references that document them in detail.  Note
that these algorithms are specified with a MUST, so implementation of
them is not optional.  I assume the current situation with Linux TCP
is due to the fact that it's still a pre-release version, and that no
one intends to release it without appropriate congestion avoidance and
slow start code.  Fortunately, the code is fairly easy.  It should not
require any restructuring of the current implementation, though it
will require some additional variables.  Certainly any new TCP/IP
implementations should conform to RFC's 1122 and 1123 before official
release.  I believe it would be highly unfriendly to use any
implementation not having these algorithms on any network beyond a
local Ethernet or a set of Ethernets connected via links that at
least T1.
Newsgroups: comp.os.linux
From: jwinstea@fenris.claremont.edu (Jim Winstead Jr.)
Subject: Re: WANT GCC? FORGET FAQ.GCC AND README?? READ THIS FIRST!!!!
Organization: Harvey Mudd College, WIBSTR
Date: Fri, 4 Sep 1992 03:06:12 GMT

In article <186a86INNcsb@usenet.INS.CWRU.Edu> mal11@po.CWRU.Edu (Matthew A. Lewis) writes:
>
>unfortunately....I can't find make. And I haven't an editor. My vi
>doesn't work yet. 

If you used the 0.96 or later root disk to install, you do have an
editor.  It's called joe.  If you installed from the MCC interim
version, you also have elvis, a vi clone.

Also, with the MS-DOS filesystem available, you've made your
instructions overly complicated.

>BTW, if you don't like these instruction, screw you. It worked for me :)
>
>Hopefully this will motivate someone (in authority?) to make this
>installation process a little easier.

The best way to get better documentation and installation procedures
is to WRITE THEM YOURSELF!  Bitching at someone "in authority" will
not help, and will likely just tick them off.  Kind suggestions are
always welcome, but complaining gets you nothing.  The best way to get
an improvement is to write it yourself and kick it back to the author
- I'm sure that HJ Lu would like it for the GCC installation to be as
painless as possible, but he doesn't have much time.  I would love to
have an 'update' script on the root disk, but there are simply other
things I would much rather do (since I don't need a root disk update
script myself - maybe a script to update the root disk from my hard
drive.  :)
-- 
                                    +      Jim Winstead Jr. (CSci '95)
                                    |      Harvey Mudd College, WIBSTR
                                    |   jwinstea@jarthur.Claremont.EDU
                                    + or jwinstea@fenris.Claremont.EDU
Newsgroups: comp.os.linux
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Subject: MS-DOS FS: FAT corruption bug, the dirty details
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Fri, 4 Sep 1992 01:38:03 GMT

This is a short description of the FAT corruption bug mentioned in
the dosfs.8 announcement. People who are using an older version of
the MS-DOS FS should read this in order to find out how to avoid
that problem.

The MS-DOS FS uses "inode numbers" to describe the location of the
corresponding directory entry. E.g. the first file in a directory may
have the "inode number" 320, the second 321, etc.

The MS-DOS FS also uses a small cache that caches FAT accesses. It is
accessed by a device/inode-number/cluster-number key.

Whenever a file is removed, the associated cache entries are
invalidated, because the next file created in the same directory may
occupy the same entry and may therefore inherit the same "inode
number". This matters for regular files that contain holes and for
directory files, because they are accessed on a per cluster basis in
the FS.

Unfortunately, I forgot to do this when renaming a file into a
different directory. So if the FAT cache contains references to the
blocks of a file _and_ the file is moved to a different directory
_and_ a new directory (or, to a lesser extent, a new file) is created
in the same directory, it may "inherit" those FAT references to the
blocks of the old file.

This bug exists in versions 5, 6 and 7 of the MS-DOS FS. It is fixed
in version 8.

If you don't want to upgrade or if you can't, I'd suggest to either
avoid the situation described above or to unmount and re-mount the FS
after the rename. (The FAT cache is invalidated during a umount.)

- 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_/
Newsgroups: comp.os.linux
From: callison@uokmax.ecn.uoknor.edu (James P. Callison)
Subject: Re: EISA bus machines
Keywords: EISA
Organization: Engineering Computer Network, University of Oklahoma, Norman, OK, USA
Date: Wed, 26 Aug 1992 19:01:49 GMT

In article <1992Aug25.013943.22305@microsoft.com> satishc@microsoft.com (Satish Chittamuru) writes:
>In article <BtE228.D6J@kingston.ac.uk> cc_s525@kingston.ac.uk (Francis Bell) writes:
> > Hi Linuxers,
> >        The FAQ says that Linux won't run on EISA machines. Can anyone
> > explain why, and suggest how difficult it would be to remedy ?
>
>If the FAQ says that, then the FAQ is out of date. I am running linux 0.97
>on a Compaq Deskpro 486/33M (one of the newer EISAs) with a Conner 302xx
>(I don't remember the exact drive number) IDE drive and 16MB memory. Linux
>runs just fine on it.

As I recall, the FAQ doesn't say it won't run on EISA machines; it says 
something along the lines of not having 32-bit SCSI support. But it's been
a few weeks since I last read the FAQ...and I've slept once or twice since
then. :-)

				James

James P. Callison       Microcomputer Coordinator        OU Law Library 
Callison@aardvark.ucs.uoknor.edu   /\    Callison@uokmax.ecn.uoknor.edu
	constellation!biglaw!callison@mailhost.ecn.uoknor.edu
DISCLAIMER: I'm not an engineer, but I play one at work...
At the Republican Convention, any male over 40 could get a free rectal
exam at the Bob Dole Prostate Cancer Institute. And you thought it was 
painful getting Republican policies shoved down your throat!	
				--Jay Leno
From: lm@slovax.Eng.Sun.COM (Larry McVoy)
Newsgroups: comp.os.linux
Subject: VM386?  Possible?
Date: 1 Sep 1992 17:08:52 GMT
Organization: Sun Microsystems, Mountain View
Distribution: world
Reply-To: lm@sun.UUCP (Larry McVoy)
NNTP-Posting-Host: slovax

Forgive my ignorance, but is it possible to run a 386 program on a
virtual 386 on a real 386?  The reason I ask is this: aren't a lot 
of dos programs running in 386 mode?  So even if you got VM86 working
and got a dos emulator running, wouldn't things like windows apps
not run at all?  Or is everything still running as an 8086?

Thanks.
---
Larry McVoy			(415) 336-7627			 lm@sun.com
Newsgroups: comp.os.linux
From: hammond@kwhpc.caseng.com (Kevin W. Hammond)
Subject: VM86
Reply-To: hammond@kwhpc.caseng.com (Kevin W. Hammond)
Organization: The Internet
Date: Sat, 29 Aug 1992 06:59:40 GMT

I see with patch 2 there is a vm86.h file and I recall seeing some mention
of Linux supporting a virtual 8086 mode.  Is this true and, if so, how does
one use the virtual 8086 driver?

-kwh-
-- 
Kevin W. Hammond
hammond@kwhpc.caseng.com

  CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA