HDTenEightyP/NetNews huggingface dataset:
From: cmetz@thor.tjhsst.edu (Craig Metz)
Subject: X11 - what's the proverbial "Latest", and what to do...
Reply-To: cmetz@thor.tjhsst.edu (Craig Metz)
Organization: The Internet
Date: Fri, 11 Sep 1992 01:31:04 GMT


	Ok, well I have run on my machine before (incessant flamers,
skip here - I have an ET4000 board and I've run it before) through
all the versions released to the public of the "Linux X11". Now, my
problme is that I want a reasonably fast server (ie, XFree86 - the
ET4000 speedups and such will really impact performance in a positive
way for my system!). I guess things can be summed up in two questions:

	1. What's the timetable for "Linux X11" 2.0? 

		- Last I heard was a chicken and egg problem between X11
		  and GCC...

	2. If "Linux X11" 2.0 isn't coming too soon, what do I need to
		build an XFree86 server that is Linux-aware (what is
		needed patch-wise to do such things as handling VCs in
		the "right" way and restoring video mode, all that...).

		- I've seen one X3861.2E server binary out on sunsite,
		  and it looks like it will work, but there's a big
		  difference in my book between working and working
		  CORRECTLY (handling Linux-isms right). 

	Any helps would be appreciated, preferably in mail unless it
would be of benefit to the world. The S/N ratio around here is enough
to make me stop reading the group. And no, for the "xjxtirn handles all
that for you" crowd, I can't do killfiles - reading e digests here.

							-Craig

-------------------------------------------------------------------------
The Thomas Jefferson High School for Science and Technology
Where nothing works, nothing is up, and everything is late.
Newsgroups: comp.os.linux
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Subject: Re: Bash Info files uploaded to tsx-11.mit.edu...
Reply-To: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Organization: The Internet
Date: Wed, 9 Sep 1992 03:00:21 GMT

   From: kfogel@occs.cs.oberlin.edu (Karl Fogel)
   Date: 5 Sep 92 21:02:49 GMT

	   The info files on Bash have been uploaded to tsx-11.mit.edu,
   where they hopefully soon appear in the linux/info directory. 

They've been installed in the linux/docs/info directory.  The info/
directory is for random information, not for info files, and I thought
it might get confusing.  At some point I may rename that directory to
information, or random-information, or something like that.

Note that I don't always acknowledge submissions with email or
announcements to the digest, although I try to at least acknowledge the
submission if I remember.  I've been rather swamped lately, so that's
the best I can do....

							- Ted
From: steve@Nyongwa.CAM.ORG (Steve M. Robbins)
Newsgroups: comp.os.linux
Subject: Re: Need help in compiling smail-3.1.26
Date: 5 Sep 92 19:39:21 GMT
Organization: Chiral Symmetry Breaking, Inc.

In article <1992Sep05.011651.2195@kithrup.COM> dje@cygnus.com (Doug Evans) writes:
>Pieter Immelman (pi@oliver.sun.ac.za) wrote:
>: Does anybody know what must be changed in the source/installation to
>: get smail linking?  Our current problem is that the linker is looking
>: for _lockf.  We had a prior problem with F_ULOCK, F_LOCK, F_TLOCK which
>: wasn't defined.  This was easily fixed ;) by adding it to unistd.h.
>: As we see it, we're either missing a library or _lockf has a different
>: name in Linux.
>
>There are various ways to proceed. What I did was tell smail to use
>fcntl(F_SETLK) which is the Posix way to do file locking.
>Unfortunately, my Linux box is 1000 miles away. :-(
>
>Lockf() isn't Posix, which is why it is currently unimplemented.

Having F_SETLK must be new, because it isn't in my 0.97p1 kernel.

For those of you with older kernels like me, you can set (in conf/os/linux) :
LOCKING_PROTOCOL=
LOCK_BY_NAME=TRUE

And it should work.

>Doug Evans        | With views like these ...
>dje@cygnus.com    |                           who needs disclaimers.


-- 
Steve Robbins  --  steve@nyongwa.cam.org
Do not think that I have come to bring peace on earth;
I have not come to bring peace, but a sword.
			- Jesus (Matthew 10:34)
Newsgroups: comp.os.linux
From: int177c@aurora.cc.monash.edu.au (Jae Won)
Subject: free on ps097pl4 doesn't know about my swap
Organization: Monash University
Date: Wed, 9 Sep 1992 09:20:25 GMT

Hi.

	I have been using 0.97 pl4...wonderful stuff. Anyway, I have installed...or
copied the binaries of ps for the new patch and it seems to be working pretty
well. The ps recognizes the swap partition but free doesn't seem to.
	How can I fix this?
	Another question, how come the memory doesn't add up to my physical memory?
(on free I meant. THis is also true with ps however).

Jae

Newsgroups: comp.os.linux
From: tvf@cci632.cci.com (Tom Frauenhofer)
Subject: Another Newbie Linux User
Organization: Northern Telecom, Network Applications Systems, Rochester, NY
Date: Wed, 9 Sep 1992 17:59:59 GMT

Just got the MCC distribution of Linux 0.97pl2 up and running on my home
system (386sx w/ Chips & Technolgies MB, 4 Meg RAM, ST-02 SCSI host adapter,
Realtek VGA card).  Real simple installation, I'm impressed, it looks like I
might have finally found the cheap home Unix I've always been seeking.

Just two quick questions:

1) I uploaded the taylor UUCP binaries from tsx-11.mit.ed but all it does is
   dump core.  I guess it was compiled for a previous (incompatible)
   version.  Is there a later revision of the binaries?  (I've got the
   source from prep and the extra stuff from the tsx-11 packages area, I
   might have it compiled before I get an answer.  Might.)

2) Does the X that is currently in beta have a driver for a "standard" VGA
   display device?  Failing that, is there anyone out there who knows how to
   get in touch with Realtek to get info on their board?  I'm sure my system
   is a little underpowered for X but there are times when I'd like to use
   some of the X applications anyway.

Thanks in advance!
--
Thomas V. Frauenhofer, WA2YYW, tvf@cci.com, ...!uunet!uupsi!cci632!tvf
Mandlebratwurst: The Meal that Eats Itself!
From: rdb@oasis.icl.co.uk (Roger Binns)
Newsgroups: comp.os.linux
Subject: Re: Can you access a virtual console directly?
Date: 15 Sep 92 18:11:52 GMT
X-Newsreader: TIN [version 1.1 PL6]

In article <1992Sep14.220800.12868@klaava.Helsinki.FI> Lars wrote:
: [ Does anybody else get tired of MS-DOS programmers whose first (and
: often enough only) thought is: ``How do I write directly to video
: memory?'' Perhaps we'll see requests for adding TSR support into Linux
: next. Urgh. ]

Well, I think any program should be able to take total control over the machine]
and use its own protected mode memory allocation system.  Also, the filename 
lengths should be reduced to match 8.3.  No one needs more than that.
Additionally, only companies owned by Bill Gates must be able to provide 
compilers, and further operating system software.

Any decent windowing products must use undocumented dos and gui calls, and
under no circumstances must software work with previous or newer versions
of any other software.

Finally, upgrades must be very expensive and thinly disguised bug fixes.

Now, have a breath of fresh air, and think about linux.

ahhhh

Roger
--
cs89rdb@brunel.ac.uk        Brunel University, Uxbridge, Middx, UK
rdb@oasis.icl.co.uk         International Computers Ltd., Bracknell, Berks, UK
"Is this stuff any good for ants? No, it kills them."
Newsgroups: comp.os.linux
From: jem@vipunen.hut.fi (Johan Myreen)
Subject: Re: using serial (ps/2 comp) mouse on Gateway
Organization: Helsinki University of Technology, Finland
Date: 9 Sep 92 16:38:49


First, to reduce (increase?) the confusion about mice, I'd like to
point out that

Serial mice != PS/2 mice != Bus mice.

PS/2 mice resemble serial mice somewhat, they transmit the data
serially, and I think at least some PS/2 mice can be plugged into a
serial port with a suitable adapter. Normally you plug in a PS/2 mouse
into the mouse port, which uses a 6-pin Mini-DIN connector, which
inside the computer connects to the keyboard/auxiliary processor
(8042). The OS reads the data from a register in this processor, in
the same way the keyboard driver does.

In article <18j3iuINNf6e@usenet.INS.CWRU.Edu> bx516@cleveland.Freenet.Edu (Victor Charles Zandy) writes:
>I am trying to run X on my Gateway 2000 386sx under linux.  
>Everything seems to start up fine, but after two months of trying
>I have not been able to get X to recognize my mouse.  It's a
>microsoft mouse, and appears to be connected in a ps/2 style port.
>Could anyone provide me with major/minor device numbers or any
>other advice?

The PS/2 mouse driver went into Linux with 0.97PL3, so you will need
this or a later release to use a PS/2 mouse, or you will have to patch
your kernel with patches available on nic.funet.fi
(/pub/OS/Linux/kernel/ps2m097.tar.Z). The driver uses major=10,
minor=1; create the device with the following command

mknod /dev/psaux c 10 1

PS/2 mice use a protocol which isn't compatible with the Microsoft
serial protocol, or (to my knowledge) with any other mouse protocol.
But since the protocol was defined by IBM, all PS/2 mice use the
same protocol (knock on wood).

Of course, this protocol isn't supported by X386... To work around
this I have written a program which converts the PS/2 mouse packets
into corresponding ones using the Microsoft protocol. The program uses
a pseudo tty; in Xconfig you lie to X386 that you have a Microsoft
mouse on the slave side of a pty (e.g. /dev/ttyp1), start up the
conversion program and X is happy. This program is available in the
patch file too. Please read the README.

It would be nice if somebody could include PS/2 mouse support in
X386/XFree86. Unfortunately I don't have the disk space (nor the time)
to do this.

--
Johan Myreen
jem@cs.hut.fi
Newsgroups: comp.os.linux
From: david@prism.demon.co.uk (David Metcalfe)
ReplyTo: david@prism.demon.co.uk
Subject: 0.97pl4 breaks SCSI extended partition code
Distribution: world
X-Mailer: cppnews $Revision: 1.15 $
Organization: ** none **
Date: Tue, 8 Sep 1992 19:57:51 +0000

I recently upgraded from the mcc-interim version of 0.97pl2 to pl4.
However, when Linux boots up with pl4 it fails to read my extended
DOS partition on the SCSI drive with the following error message

Unable to read partition table of device 0803

My disks layouts are as follows:

Disk 0: ESDI
        1 DOS primary partition
        1 DOS extended partition with 3 logical DOS drives

Disk 1: SCSI with Adaptec 1542B
        1 DOS primary partition
        1 DOS extended partition with 2 logical DOS drives
        1 Linux partition with extfs

Note that I am using the extfs on the Linux partition.  However, the
problem lies with the DOS extended partition with the 2 logical
drives on the SCSI disk.  The partition is detected but not the
logical drives.  Note that the extended partition on the ESDI drive
is interpreted correctly.

I use one of the logical drives on the SCSI disk has my DOS->Linux
transfer disk as I have Stacker installed on the other drives, so its
important that I get access to that drive.

I have had no problems with either the mcc-interim 0.97pl2 release or
any other kernels since extended partition reading was implemented on
SCSI drives.  However, I only converted from the minix fs to the
extfs recently at the same time as I installed mcc-interim 0.97pl2.

David

-----------------------------------------------------
David Metcalfe          david@prism.demon.co.uk     
+44 81 361 3327         dmetcalf@cix.compulink.co.uk
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Newsgroups: comp.os.linux
Subject: Re: stderr buffering
Date: 6 Sep 92 16:09:30 GMT
Organization: State University of New York -- Institute of Technology

In article <Bu2sr4.Brv@acsu.buffalo.edu> beers@acsu.buffalo.edu (Andrew Beers) writes:
>
>I just got the sc package from tsx-11.  I press '?' for help, and the help
>screen does not appear.  After a few more keypresses, the help screen appears
>and then quickly disappears.
>
>I have also noticed that when I press <ESC> to exit edit mode in vi, it can
>take several seconds before the cursor will move back one space.
>
>I compiled the unit conversion program units, and noted that fprintf's not
>ending with a carriage return were not immediately sent to the screen.  All of
>the fprintf's printed to stderr.
>
>It is my understanding that stderr should not be buffered at all.  These three
>cases lead me to believe that it is being buffered under Linux.
>
>System:  386sx/25, 4Meg, 0.96pl2 (have noticed it with earlier kernels, also).
>
>Any ideas on this problem?

I haven't used this version, but I didn't have any problems with my own.
It compiled out of the box, with just a couple #ifdef's, and the arrow keys
worked correctly.

-- 
Jim H.
*
* James L. Henrickson
* ujlh@sunyit.edu        "Some day I might have a real .signature!"
Newsgroups: comp.os.linux
From: golden@pineapple.cns.udel.edu (Edward Golden)
Subject: WD 7000 FASST SCSI ADAPTER
Organization: University of Delaware, Newark
Date: Fri, 11 Sep 1992 18:44:22 GMT

   Hi!  I'm new to Linux, and am struggling to make Linux work on my 386SX.
I have a WD7000 FASST scsi controller, and understand that linux is supposed
to support it.  I'm not having any luck making it work.

   I've tried both the 0.97 and the SLS release from tsx-11.mit.edu.  Linux
boots successfully from floppy disk, but is unable to find my hard drive.  It
boots with 0 host adapters, 0 scsi drives, and 0 tapes found.  Fdisk also 
does not work, failing with "unable to read /dev/hda2".  This shouldn't happen,
right?

   I've discovered a WD-7000 patch on tsx-11, but cannot figure out how to
apply it:  I can't get anything on the drive to patch.  I don't think I
need to apply it against 0.97 anyway...

   I wish to put linux in a 3rd, 60Mb partition on my hard drive (the first
two partitions belonging to DOS).  I've attempted loading Linux on the drive
when partitioned with the SSTSETUP utility and with MsDos's FDISK (when all
the SST partitions have been deleted).  

   I've hit a dead-end, and am becoming frustrated.  Any help would be
GREATLY appreciated.  

							[Golden]
Ed Golden
golden@pecan.cns.udel.edu
From: pete@q106fm.UUCP (pete cervasio)
Newsgroups: comp.os.linux
Subject: Possible MS Bus Mouse Detect (?)
Date: Sun, 13 Sep 92 14:06:24 CDT
Organization: WKBQ-FM Engineering Department

fwbent@watmsg.uwaterloo.ca (Fred Bent) writes:

>Hello,
>
>I have been reading several articles mention that currently
>there is no method for detecting a Microsoft Bus Mouse.
>
>Well, I have some code that shows how to do this (I think :-).
>Is this what you are asking for?  I have not tested this code
>with a Logitech so I am not sure what will happen, I only know
>that this code should work for detecting IF a Microsoft Bus Mouse
>is present (but not sure if will discriminate).
......Code Deleted......
>Hope this helps!  I can only test this under MS-DOS, but the method
>should be clear.  inp and outp simply get/send a byte to a IO port
>(in case not too obvious).

Hmm... I just tried this with MSC 5.1 under DOS and it reports the IRQ
as 0... It did think I had a MS Mouse, though, so it may be what we need
under Linux to do the detection (leaving the IRQ at 5).  Could someone
with a Logitech mouse try this code and mail me your results?

Thanks.
Pete C.

+----------------------------------------------------------------------+
| Pete Cervasio                | pete%q106fm.uucp@wupost.wustl.edu     |
| I fish, therefore I am.      | pete.cervasio@f1.n2250.z1.fidonet.org |
+----------------------------------------------------------------------+
|  If you think of C as a preprocessor for your assembler, it makes    |
|                   just as little sense as before.   (me)             |
+----------------------------------------------------------------------+
Newsgroups: comp.os.linux
From: bjl@loki.research.ptt.nl (Ben Lippolt)
Subject: Re: MBR recommendation needed
Reply-To: B.J.Lippolt@research.ptt.nl
Organization: PTT Research
Date: Mon, 7 Sep 1992 10:57:28 GMT

ujlh@pool.info.sunyit.edu (James Henrickson) writes:

>Hi all,

>I would like to boot DOS and Linux off the hard drive.  I am currently 
>using LILO and the MS-DOS MBR with the active partition set to Linux.  
>I am looking for an MBR similar to the one that come with Coherent, that 
>will boot the active partition by default but allow me to select the boot 
>partition if I want to boot DOS.  I have seen a few less-flexible MBR's 
>that either wait for you to make a selection (no timeout default) or have 
>no selection (like the DOS MBR), and I have seen DOS utilities that will
>boot Linux (I don't want to be dependent on DOS), but I haven't quite
>found what I'm looking for.  I will, of course, settle for a clone of
>the Coherent MBR if one is available but I'd prefer a user-defined
>timeout period.

Take a look at 'pfdisk'. It comes with a MBR (bootactv.bin) which does
exactly what you want. It has a default time-out of 10 seconds and after
that it boot the default partition.


Ben Lippolt.
From: hedrick@athos.rutgers.edu (Charles Hedrick)
Newsgroups: comp.os.linux
Subject: Re: SLIP with 7-bit connection? Even thinkable?
Date: 9 Sep 92 02:26:20 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

jonathan@nova.next.nd.edu (Jonathan Bradshaw) writes:

>I was wondering if it is possible to run KA9Q over a 7 bit connection? 

Not using SLIP at least.  I don't know about the code for ham radio.
The SLIP protocol is defined as requiring an 8 bit connection.  So
this isn't a limitation of KA9Q, but is basic to SLIP.
From: Emmett.Sauer@f215.n3802.z1.fidonet.org (Emmett Sauer)
Newsgroups: comp.os.linux
Subject: Unable to mount msdos partition
Date: Wed, 02 Sep 1992 23:24:00 -0800

* Replying to a message originally All on 09-02-92

KW> From: Kevin W. Hammond <hammond@kwhpc.caseng.com>
KW> Reply-To: hammond@kwhpc.caseng.com
KW> I can mount/umount minix file systems and the /etc/fstab stuff
KW> is working,
KW> but for the life of me, I cannot mount a DOS partition or
KW> floppy.  I am
KW> using the following command:
KW>
KW> 	mount -t msdos /dev/hda1 /mnt
KW>
KW> /dev/hda1 is my C: drive for DOS.  The message I get back from

Well I am running 0.97p2 MCC-INTERIM and just tried the MSDOS mount with
your
command line and no problem.....

What kinda of drive is your dos drive, what version of LNX you running,
and what kind of MB you using?

As strange as these questions may seem they all have a bearing on the
operation of the mount... this I have found through experience..

emmett@tenet.edu                   |   ADVANCED BBS    |
                                   |  (512) 578-2720   |
                                   |  FIDO 1:3802/215  |
                                   | Linux and Support |
                                   |  File available   |


 * Origin: Advanced BBS - Line 1 (512)578-2720 (1:3802/215)

Organization: Administrative Systems, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.os.linux
Date: Wed,  9 Sep 1992 11:46:04 -0400 
From: "Brian E. Gallew" <geek+@CMU.EDU>
Subject: Re: Two suggestions .. comments welcome, please!
	<1992Sep9.071853.6652@klaava.Helsinki.FI>
Distribution: comp.os.linux

>A better idea would be for the boot disk to optionally ask the data from
>the user, instead of requiring hardwired, patched-in values.  This
Actually, I am working on this even now.  The problem I have run into
is that I am almost completely clueless on how to get the kernel to
get keystrokes where I can use them.  Otherwise, it is basically done.

Want to help?  Send me some kernel input routines!


                                  -Brian

You drop the bomb -more-
It goes off... -more-
-------------------------------------------------------------------------
|  My cluelessness is more real than apparent...                        |
-------------------------------------------------------------------------
|  DEC measures their benchmarks with a calendar!!                      |
-------------------------------------------------------------------------
Newsgroups: comp.os.linux
From: Kevin W. Hammond <hammond@kwhpc.caseng.com>
Subject: Major/Minor numbers
Reply-To: hammond@kwhpc.caseng.com
Organization: The Internet
Date: Fri, 11 Sep 1992 02:57:38 GMT

I'm in the process of backing up my root drive and getting ready to
re-mkfs it.  One problem lies in the way ... I don't have an original
root disk on floppy any more so I am creating one by hand.  However,
I do not know the major/minor numbers for mknod to create the needed
devices in /dev for the reboot.  Could you (or someone) send me a list
of device numbers as soon as possible?  Thanks!

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

                               "99.9% FAT Free"

  CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161
Newsgroups: comp.os.linux
From: harp@netcom.com (Gregory O. Harp)
Subject: Re: running high speed modems under *nix
Date: Fri, 11 Sep 92 09:49:21 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

Upholder@uiuc.edu (THE Upholder of Truth) writes:

>What would it take to get higher than 38.4K rates under linux?
>(at least 57.6K and perferably 115.2K)

In my somewhat limited experience of coding serial routines for DOS, I
have noted that rates above 38.4Kbaud are usually achieved through
tight polling loops rather than interrupt serial communications.
Remember the DOS box, since it runs a single-tasking interrupt handler
rather than a real OS, doesn't have to do anything other than hit the
serial port.

In other words, it ain't likely to happen in Linux... ;)
-- 
-----------------Greg-Harp----------------harp@netcom.com------------------
  Love me, love my ferrets.               "Break out of the mold before
  Or at least love my ferrets. ;)          the mold sets in" -- B52's
Newsgroups: comp.os.linux
From: mdw@theory.TC.Cornell.EDU (Matt Welsh)
Subject: Re: compiling 0.97p5
Organization: Cornell Theory Center
Date: Mon, 14 Sep 1992 02:49:14 GMT

In article <kegzWfS00WBM44l0x3@andrew.cmu.edu> ce12+@andrew.cmu.edu (Christopher Aaron Ekberg) writes:
>Hello,
>
>Until now, I have never had any problems upgrading kernels.  I am
>currently running 0.97pl4 (upgraded originally from 0.97.2 MCC), and
>when I applied patch 5, everything looked ok.  But when I make'ed it,
>make choked:  in init/main.c, mem_init had the wrong number of
>parameters!  It wanted two, and it had three:
>(low_memory_start,memory_start,memory_end) or something like that.  

[Description of errors deleted]

>
>This exact thing happened when I tried to make from the 0.97.5 sources.
>
>Am I missing some files or anything?  Incorrect libs/headers?  I did ln
>-fs the include directories (and the asm dirs).  I haven't seen anyone
>else having these problems!  I know that a new version will be out
>shortly, but I would really like to figure this out.

Oops. Okay, guys: the ln -fs will NOT work correctly if you ALREADY have
the target directory at the time you make the link. I.e. if you do

% mkdir foo
% ln -fs bar foo

You end up with the link "bar" being *inside* the directory foo, as in

foo/bar -> foo

I don't know if this is "correct" behavior or not, but this is what happened
to me when I made those links because (of course) the /usr/include/linux and
/usr/include/asm directories were already in existence when I made the
link, so it put the link inside those directories. The solution: either
rename or nuke the two existing directories, then make the link.

mdw


-- 
Matt Welsh    mdw@tc.cornell.edu        +1 607 253 2737
Random Hacker, Cornell Engineering and Theory Center 
  "I'll eat anything that's BRIGHT BLUE!!"