HDTenEightyP/NetNews huggingface dataset:
From: jplevyak@ncsa.uiuc.edu (John Plevyak)
Subject: Re: GCC2.1 (Wonderful !) (dynamic linking)
Originator: jplevyak@nvs.ncsa.uiuc.edu
Organization: Nat'l Ctr for Supercomp App (NCSA) @ University of Illinois
Date: Fri, 17 Apr 1992 21:01:36 GMT


I agree with burley@churchy.gnu.ai.mit.edu (Craig Burley), but I would
like to clarify and sum up a bit.

Craig writes:

> Either I misunderstand you or this is wrong. ... PRIMOS generally
> had pointers (especially unsnapped ones) in read/write segments (pointed to
> by the Link Base, LB%) along with ECBs (procedure Entry Control Blocks) and
> such.

I stand corrected.  In general, however, the problem is that if the functions are
not statically bound to offsets at the call site, dynamic linking either requires
(1) another level of indirection or (2) a fixup at the call site. Solution (1)
can be made more efficient if supported in hardware, and solution
(2) requires impure code.  In general, both these solutions have real performance
drawbacks.  In case (2) pointers to functions have to be handled as well.

Segmentation is related issue.  Segments can provide the extra level of
indirection for dynamic linking, handles for memory management etc, not
to mention other advantages.  The segment sizes are the issue ('286 and '386).
Too few large segments are not good for small blocks or functions, too many
small ones and you can't allocate large arrays.  The good and the bad... life.

The model for Unix has been flat memory, sharing by pages and basically
KISS.  I'm all for experimentation though.  My feeling is the proof is in the
pudding.  Build it.  If it works, everyone will use it.

john 
Xref: sparky comp.os.linux:359 alt.os.linux:2438
From: dingbat@diku.dk (Niels Skov Olsen)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Re: Keyboard dies when I hit Caps-Lock (+SCSI)
Date: 12 Apr 92 17:16:58 GMT
Organization: Department of Computer Science, U of Copenhagen

I wrote late one night:

>I just got my Adaptec 1542B the other day and installed the stuff
>from sc.tamu.edu with Tommy Thorn's SCSI driver in it. It works
>fine except that my keybord locks up completely when I hit
>Caps-Lock. That's very annoying because Tab is right above it
>and I use that one extensively for filename completion. I compiled
>the kernel with the Danish keyboard - it didn't help. I 'heard' that
>Drew Eckhardt was almost ready with incorporating low level Adaptec 
>support, so I thought I would poke around at headrest to see if 
>something had come up. There was a brand new vmunix which I installed
>and booted. It detected my adapter and disk just fine, but tried to
>load the root from device 0301. I changed that (vmunix[508]=02) and
>rebooted. That didn't help so I cleared the bytes at 508 and 509
>so that the rootimage would load from floppy. That worked (phew).
>But still no talking to /dev/hda2. And the keyboard still locks 
>up...

>Any clues? No problems in DOS. The keyboard is a cheap Taiwanese
>one called DANREX KB-6252EA.

OK, now that I am awake I noticed that SCSI devices now have major 8!
That's fine, but my keyboard still locks up. Linux is still running,
it is just not receiving my keystrokes - I have to hit the reset 
button (after waiting ~30 seconds for update to sync).

Am I the only one having such a problem???

Niels
dingbat@freja.diku.dk
From: ugewa001@unibi.uni-bielefeld.de (0134)
Newsgroups: comp.os.linux
Subject: Re: Patch to preset the SVGA mode
Summary: LINUX kills CMOS table
Keywords: Linux, Problems, CMOS
Date: 13 Apr 92 16:59:41 GMT
Organization: Universitaet Bielefeld

HELP !!


On our 40 MHZ 386 0.95a kills the CMOS-Setup (PRam)

It took some time to get the machine to boot again.

Linux has done this several times already, while trying to mkfs or pfdisk, the 
last time when I tried to login. My first attempt to login failed, the second 
caused the machine to reboot and then I had to rebuild the PRam. (after zapping
it that is)

folker
ugewa001@unibi.uni-bielefeld.de
Newsgroups: comp.os.linux
From: cummings@hammer.Prime.COM (Kevin Cummings)
Subject: Re: Yet another X question
Keywords: X Windows
Organization: Prime Computer R&D
Date: Wed, 15 Apr 1992 19:29:03 GMT

In article <1992Apr15.145806.16235@ccu.umanitoba.ca>, umthom61@ccu.umanitoba.ca (Adam Thompson) writes:
> In <1992Apr15.053227.24310@serval.net.wsu.edu> hlu@yoda.eecs.wsu.edu (Hongjiu Lu -- Graduate Student) writes:
> 
> >From my own experience, a real X11R4 can take as little as 10MB to run.
> >on a 386. I only keep the minimum stufffs I need. Beside MIT stuffs,
> >I added some other programs, like xgif and xdvi. I can put off X source
> >from the net and compile it without much problem. I believe, for X11R5,
> >20MB should be a safe bet.
> >H.J.
> 
> Perhaps you're assuming he doesn't want to compile it :-)
>  
> According to the docs in the R5 distribution, the source tree untars to
> roughly 150-200 Megs.  To compile, expect to need at least another 100Meg.
>  
> As far as compiled binaries go, using shared libraries, on a Sun i386,
> the full MIT core plus about 50% again in added-on goodies takes somewhere
> in the range of 60-70 Megs.  Of course, to simply run R5 'functional', then,
> yes, expect to use ~20 megs.  Perhaps even a bit less if you only have one
> WM on call...

I plan on trying to run X over a slip connection to a "mainframe" host.
What I need locally is the local server, and maybe a few local
applications (a window manager, xterm, xmh, etc).  Most of the
other applications don't need to be local, but instead can run
from remote hosts.  I'm hoping that this is the 20MB scenario.  In fact
I'm willing to go to 40 or 50MB locally in this scenario.  I'm not
interested in compiling ALL of the X distribution, but I imagine that
there will be a fair number of people out there who will want to, mostly
because they won't have a live network connection, and will need to have
everything locally.

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

Work:  cummings@primerd.Prime.COM
Home:  cummings@kjc386.framingham.ma.us

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
Xref: sparky comp.os.linux:471 comp.sys.transputer:666
From: michael@gandalf.informatik.rwth-aachen.de (Michael Haardt)
Newsgroups: comp.os.linux,comp.sys.transputer
Subject: First small success in using Linux as transputer host
Date: 11 Apr 92 23:09:15 GMT
Reply-To: u31b3hs@messua.informatik.rwth-aachen.de (Michael Haardt)
Organization: Gandalf - a 386-20 machine

I ported dmake 3.8 to get a decent make on Linux (it compiles without
much effort, as usual on Linux) and built my small transputer tools a
few minutes ago.

Well, I started the transputer memory test with the start server and:
wow! It worked, and *so* much faster than under MINIX.  This simple
server uses /dev/port, and it was painful slow under MINIX.  Once again
I am really impressed by the speed of Linux.

I am still working on my transputer assembler and linker and I am still
not sure if I will release it to public domain, but if there is
interest, I will make binaries for Linux available per ftp.  I can't
make available the server, because it is a based on the server in "Das
Transputerbuch", but I will write my own server next time.

I will be away for vacation with my gf during next month.  When I come
back, I will develop a concept for a device driver to use the link
interface at highest possible speed.  I guess that the PC bus will be
the bottleneck, because the link is able to work at 20 MBit/second, but
it is used via an 8 bit port.  Here are two ideas of mine:

-   /dev/tlink, a character device with blocking read and write to the
    link.  Perhaps non blocking read/write may be supported, I don't know
    if it is useful.  ioctl's will control reset, error and analyse.

-   /dev/tlink for the link, /dev/tlinkctl for controlling error, reset and
    analyse with kind of message passing via fs.  This makes ioctl obsolete
    and I like it a lot since I read the Plan 9 papers, but on the other
    side it is totally different from anything else in Linux :(

Any other suggestions?

I haven't looked at device drivers in Linux yet, how difficult it will
be and what has to be done to support blocking/non blocking operations.

The transputer should be fast enough to use polling without loosing
performance.  I think the overhead of interrupts would even slow down
the data transfer, but I have no practical experience in that.

I also thought about a lock to allow only one process to deal with
/dev/tlink in the way like Parsytec uses semaphores for OpenLink, but I
decided to let the server program deal with that.  People who open
devices in their programs should know what they do and no restrictions
should be put on them.

If you post follow-ups, please send me a copy per email during next
month.  I will post a summary.

Michael
From: michael@gandalf.informatik.rwth-aachen.de (Michael Haardt)
Newsgroups: comp.os.linux
Subject: GNU m4 and chess work, awk, mawk and sort don't.
Date: 11 Apr 92 23:22:48 GMT
Article-I.D.: gandalf.9204121130
Reply-To: u31b3hs@messua.informatik.rwth-aachen.de (Michael Haardt)
Organization: Gandalf - a 386-20 machine

GNU m4 1.0 compiles without effort and runs, I suggest to use it as
standard Linux m4.

GNU chess 3.1 also compiles without effort.  I only compiled it for fun,
but it seems to work too.

I compiled both GNU awk 2.13 and mawk 1.1 (also without effort), but
both fail with the same problem:

awk -F @ '{ print $2 }'

foo@bar gives foo@bar as output, not only bar as expected.  Both GNU awk
and mawk work on SunOS 4.1.1 as expected.  I used gcc 1.40 as compiler,
on both Linux and SunOS.

sort from the GNU fileutils 3.2 compiles ok, but hangs in an infinite
loop.

I appreciate any hints.

If you post follow-ups, please send me a copy per email during next
month, I will post a summary when I am back from vacation.

Michael
Xref: sparky comp.os.linux:410 alt.os.linux:2485
From: knapka@athena.cs.uga.edu (Joseph Knapka)
Newsgroups: comp.os.linux
Subject: gcc-2.1 header files
Date: 7 Apr 92 14:55:23 GMT
Organization: University of Georgia, Athens

H.J. asked me to forward this exchange to the newsgroup:

I said:
>> Kernel build of .95c went fine, but when compiling ps, I get
>> "undefined symbol __ctype referenced from text segment" while linking
>> ps.o. This is with very latest gcc-2.1, libraries, and binutils from
>> banjo. I linked xxx/src/linux/lib/ctype.o and got it to compile, and
>> (seems that) everything works. Did I do the right thing?
>> 
>

H.J. said:
>No. Please get my 2.1ps.tar.Z, 2.1kernel.tar.Z and apply Linus's second
>patch first. When compile any application, do not use ANY header files
>from ./linux/include.

Joseph

P.S.: but I'd already applied .95c, 2.1kernel, and ps patches. Still
waiting for a reply...
Newsgroups: comp.os.linux
From: tselling@peabody.iusb.indiana.edu (Teresa Selling)
Subject: trouble with  dialin login and vi
Organization: Indiana University at South Bend
Date: Wed, 15 Apr 92 18:35:30 GMT

I can use vi fine on my system with Linux 0.95c+ installed, but when I
call into school I have trouble with vi messing up the lines and such.

I already do stty erase "^?" to make the backspace work.  Is there something
I need to do to fix this other problem.  I had no trouble with vi on the
school computer before (HP unix) with linux 0.12....any suggestions 
appreciated.
--
Teresa Selling, IUSB, Indiana.

Newsgroups: comp.os.linux,alt.config
From: joel@wam.umd.edu (Joel M. Hoffman)
Subject: Remove Alt.os.linux [was Re: Too many duplicated messages]
Organization: University of Maryland, College Park
Date: Thu, 16 Apr 1992 14:17:25 GMT

In article <1992Apr15.175109.10117@athena.mit.edu> tytso@athena.mit.edu (Theodore Y. Ts'o) writes:
>
>So, let me repeat my call.  Shall we rmgroup alt.os.linux?  I think its
>time has come.

I agree.  Having two groups is counterproductive.  Can't those
who still don't get Comp.os.linux use the digest?

-Joel
From: pca306c@nella1.cc.monash.edu.au (E Elu)
Newsgroups: comp.os.linux
Subject: news programs
Date: 12 Apr 92 11:44:52 GMT
Organization: Monash University


I am trying to get a news feed up and running on my Linux system, and I
was wondering if anyone has managed to get a newsreader an delivery agent
such as rn and c-news up and running. I have had no joy as yet though I 
managed to get the news reader Tass compiled but it failed the linking 
with libcurses.a in gcc 2.1. I included the curses.h file and put a
-lcurses at the end of the compilation string, but still no go.
Any suggestions?

thanks in advance

Ernie Elu
Newsgroups: comp.os.linux
From: haroldt@paralandra.yorku.ca (Harold Tomlinson)
Subject: Re: File system naming conventions
Organization: York Computing Services
Date: Mon, 6 Apr 1992 23:13:59 GMT


In article <92040532@gandalf.informatik.rwth-aachen.de> michael@gandalf.informatik.rwth-aachen.de (Michael Haardt) writes:

:)
:)   -  Where should the swap file/partition be?  I saw /swap, but personally,
:)      I would appreciate /dev/swap for various reasons.

  I'm not certain yet how you are partitioning the disk.  I'd agree
with you on the /dev/swap but again, look to the future.  Will you
allow for a /dev/swap0, /dev/swap1...?  Are you using an fstab to
determine the partition mounts and can it (as with some versions of
*nix) include an additional swap partition?  

  Are you using a swap "file" or "partition"?  This makes a big
differance.  If you use a file, then I'd stick to /dev/swap.  If a
partition, then why mount it?

:)   -  If there is more than one device which should be mounted temporarily,
:)      /mnt is not enough.  I recently saw /mnt/exch0, /mnt/exch1 ...

  If more than one device is being mounted temporarily, it is up to
the user as to where to put it.  Usually, on Paralandra (DecStation
2100) I create a /mnt0,/mnt1... if I need more than one temporary mount.

:)   -  I don't like the various links of gcc, cc, gas, as, gcc-as etc.  gcc is
:)      the system compiler, why not just using cc, as, ld and putting cc1 in
:)      /usr/lib?  Concerning cpp, I am not sure.  I am used to see it in either
:)      /lib or /usr/lib, but never in /usr/bin.  But then again, I think it is
:)      very different to e.g. cc1 in meaning of being an internal compiler pass.
:)      Many programs use it as usual command, so /usr/bin might be better.

  No.  At least, not by convention.  Things in /usr/bin, if I'm not
mistaken, are things that users run.  Things like diff, du, make, and
sleep.  Things in /usr/lib and things that objects (in  /usr/bin) and
*not users* run.  Things like lpd, atrun, cron...

  Things in /bin are both for users and for the system.  Not that it
matters, except if you want to stick to the conventional *nix.  At
boot time only the root partition is mounted, so only /bin is
available.  In system installation, cc is needed so it appears in
/bin.  (So do other things that you need, for example, if you boot
"single user mode".)

:)   -  The floppy devices: Why not using the MINIX naming conventions?  /dev/at0
:)      would be /dev/fd0-dshd5in, /dev/PS1 would be /dev/fd1-dshd3in.  I can
:)      post the complete MINIX floppy names, but I think not all of them are
:)      implemented in Linux.
:)
:)   Any comments?
:)
:)   Michael
:)

  Sounds good to me.  If we can tell at a glance what the device is,
that's nice.  Under Ultrix, all disks are "rz".  rz0c could be my
floppy or my hard drive.  How it's handled and mounted is determined
from the /etc/fstab.  I like having a differant name better.

--
# Harold Tomlinson			##	haroldt@paralandra.yorku.ca #
# Computing & Communications Services	##	(416)736-5257-33802         #
# YORK UNIVERSITY, Ont, CANADA		##	########################### #

Newsgroups: comp.os.linux
From: ara@zurich.ai.mit.edu (Allan Adler)
Subject: GAP under LINUX
Organization: M.I.T. Artificial Intelligence Lab.
Distribution: comp
Date: Thu, 16 Apr 1992 23:45:45 GMT


Has anyone tried to install the recently released GAP program under LINUX.

GAP is some software for doing group theory and it is distributed for free.
It is supposed to work under UNIX, but I am not aware of anyone actually
installing and using it with LINUX. 

I feel that free software projects should be aware of and compatible with
each other, so I am bringing this question to the attention of the LINUX
news group and the mailing list for GAP.

Allan Adler
ara@altdorf.ai.mit.edu

Newsgroups: comp.os.linux
From: drew@romeo.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Linux SCSI support
Keywords: scsi, future domain, linux
Organization: University of Colorado at Boulder
Date: Fri, 10 Apr 1992 23:25:38 GMT

In article <1992Apr10.223301.24673@athena.mit.edu> alsaggaf@ERL.MIT.EDU (M. Saggaf) writes:
>Is there any way Linux can work with a SCSI Future Domain 1670 host
>adapter? I'm a new user of Linux. Version .95a could not recognize my
>hard drive. I also have an RLL drive connected to an Adaptec 8-bit

People are working on a lowlevel driver for the 16 bit Future domain
boards. However, I'm not sure what the timeframe is on this, mail 
out on the SCSI mailing list to find out who and the details.

>(XT) controller (in my 386 computer). Version .95a failed to recognize
>that one as well. Is there any way I can get Linux to work with any of
>these? Thanks.
>

The XT disk controllers are physically different from the AT disk 
controllers.  This doesn't matter when you're going through BIOS
and it looks all the same, but under a real operating system,
each piece of hardware must be dealt with individually at the 
register level.

Either controller could be supported with an appropriate driver - 
but since you can find an AT disk controller for ~$20, pulled
from equipment for upgrades, a driver for the XT controller 
wouldn't be  worth your time and effort.

As far as the SCSI host -  the generic SCSI package sticks most of 
the common code in one place, leaving relatively little for you 
to implement in your driver at the lowest level.  Basically, you're
concerned with getting data to/from the SCSI host- translation from
block device commands to SCSI, timeouts, error handling, etc are all handled 
higher up the driver stack.  You also have to provide an abort function,
SCSI bus reset function, probe, and info function.

Like I said, people are working on this, but if you have anything 
to contribute, feel free to join the SCSI mailing list at 

linux-scsi-request@headrest.woz.colorado.edu

Adaptec, Seagate, and Ultrstor lowlevel drivers have been
incorporated into the generic package, which is available from

headrest.woz.colorado.edu 

under 

/pub/linux/scsi.95c+.tar.Z
From: michael@gandalf.informatik.rwth-aachen.de (Michael Haardt)
Newsgroups: comp.os.linux
Subject: File system naming conventions
Date: 5 Apr 92 20:16:42 GMT
Reply-To: u31b3hs@messua.informatik.rwth-aachen.de (Michael Haardt)
Organization: Gandalf - a 386-20 machine
Return-Path: <u31b3hs@messua.informatik.rwth-aachen.de>

-  Where should the swap file/partition be?  I saw /swap, but personally,
   I would appreciate /dev/swap for various reasons.

-  If there is more than one device which should be mounted temporarily,
   /mnt is not enough.  I recently saw /mnt/exch0, /mnt/exch1 ...

-  I don't like the various links of gcc, cc, gas, as, gcc-as etc.  gcc is
   the system compiler, why not just using cc, as, ld and putting cc1 in
   /usr/lib?  Concerning cpp, I am not sure.  I am used to see it in either
   /lib or /usr/lib, but never in /usr/bin.  But then again, I think it is
   very different to e.g. cc1 in meaning of being an internal compiler pass.
   Many programs use it as usual command, so /usr/bin might be better.

-  The floppy devices: Why not using the MINIX naming conventions?  /dev/at0
   would be /dev/fd0-dshd5in, /dev/PS1 would be /dev/fd1-dshd3in.  I can
   post the complete MINIX floppy names, but I think not all of them are
   implemented in Linux.

Any comments?

Michael
From: nicolai@lysator.liu.se (Nicolai Wadstr|m)
Newsgroups: comp.os.linux
Subject: Has anyone thought about threads?
Date: 6 Apr 92 22:29:32 GMT
Organization: Lysator Computer Club, Linkoping University, Sweden

Has anyone given any thoughts on implementing threads in linux?
I know it's not a standard UNIX feature, but it's were nice to
write programs with threads, it's often possible to gain a lot
of performance in using threads.
(I've done a lot of OS/2 programming and just love the idea of 
threads!)
The shared libraray support (when implemented), will it be like
OS/2 DLL's? I mean a .lib or .dll file that is loaded upon runtime
of the program?

Regards,
                  nicolai, nicolai@lysator.liu.se


--
Nicolai Wadstr|m                   # Internet:      nicolai@lysator.liu.se
                                   #
                                   # BBS:           +46-40-124554 (down)
                                   # Voice:         +46-40-975535
Xref: sparky comp.os.linux:526 alt.os.linux:2559
From: rob@cad4.lbl.gov (Robert J. McNamara)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Re: How to set the path ?
Date: 16 Apr 92 16:40:40 GMT
Article-I.D.: dog.22742
Reply-To: rob@cad4.lbl.gov (Robert J. McNamara)
Organization: Lawrence Berkeley Laboratory
NNTP-Posting-Host: 128.3.252.177

In article <1992Apr15.104226.1795@csdvax.csd.unsw.edu.au> s9100786@csdvax.csd.unsw.edu.au (Matthew Jackson) writes:

>Now I have a few questions (of course). When I was running the install scripts,
>I checked they were flagged as executable, and tried to run them. No go. I then
>tried /INSTALL/install and it worked ! OK, I thought Linux doesn't look in the
>current directory for a file before searching the path (ala DOS) (is this
>meant to work this way ? I am used to DOS and VMS, only just got started with
>Unix). OK (he thinks again), why don't I put the current directory in the path ?
>I typed set and got a list of the environment variables and there was one called
>PATH, so I tried set PATH=....:. and still no go. 
>
>So can someone tell me how to change the path under Linux ?
>
>Thanks in advance,

Yeah, that kinda screwed me up to for a bit since I was used to csh and 
dos...
Use that last method that you mentioned, but exclude the "set" command.
Just type "PATH=.:/bin:/usr/bin:<other paths>"

+-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Rob McNamara          | Happy! Happy! |  Lankhmar BBS                     |
| rob@cad4.lbl.gov      |   Joy! Joy!   |  1-916-757-6391                   |
| Lawrence Berkeley Lab |               |  1200/2400/9600/14.4k HST/v.32bis |
+-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
From: faith@cs.unc.edu (Rik Faith)
Newsgroups: comp.os.linux
Subject: Re: Linux SCSI support
Keywords: scsi, future domain, linux
Date: 14 Apr 92 20:54:29 GMT
Organization: UNC-Chapel Hill Computer Science

In article <1992Apr10.223301.24673@athena.mit.edu>, alsaggaf@ERL.MIT.EDU (M. Saggaf) writes:
> Is there any way Linux can work with a SCSI Future Domain 1670 host
> adapter?

I'm one of the people working on the FD 1680 (which is a 1670 with floppy
support) driver.  I expect to have it finished early in May (right now Ken
and I are somewhat swamped with classes).  Perhaps you can e-mail me in May
and check out the progress. 

-- 
Rik Faith: faith@cs.unc.edu
Paradox is the question of Chaos.
Xref: sparky comp.os.linux:559 alt.os.linux:2573