HDTenEightyP/NetNews huggingface dataset:
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Subject: Re: Hey!  Linux fs on DOS partition!
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Fri, 14 Aug 1992 17:40:26 GMT

In article <713720748snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes:
> Hey, here's a cool idea I had yesterday: Make a Linux filesystem
> driver that puts its filesystem in a file on an MS-LOSS partition.

Sorry to disappoint you, but there are several people, who already
had this idea. No shiny new patents .. ;-)

Seriously: half of it is already there. The other half will be missing
until the variable block size code is completed. The first half is the
loop devices patch, that makes it possible to mount regular files on
file systems that support bmap as file systems.

Unfortunately, MS-DOS arranges its clusters in such an odd way, that
bmap can't be used on hard disks and on some floppies. But it works
with the old 360k (and I think also 1.2MB) format. If you have the
loop devices patch installed, you can try something like this:

# mount -t msdos /dev/fd0 /fd	# there's a 360kB floppy in /dev/fd0
# dd if=/dev/zero of=/fd/file bs=1k count=350
# mkfs /fd/file 350
# mount /fd/file /mnt

- 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_/
From: egustafs@herman.gem.valpo.edu (Eric Gustafson)
Newsgroups: comp.os.linux
Subject: TCP/IP:  supported ethernet cards
Date: 12 Aug 92 21:29:19 GMT
Organization: Glitches Ltd.

I'm looking into buying an ethernet card and was curious what chipsets
would be supported by the kernal TCP/IP.

thanks,
-- 
Eric Gustafson                                     egustafs@gem.valpo.edu
Computer Engineering                                 Work: (219) 464-5356 
Valparaiso University
** Warning ** Planet is 97% full please remove unneeded inhabitants !!
From: car@trux.UUCP (Chris Rende)
Newsgroups: comp.os.linux
Subject: How to test a computer for Linux-ableness?
Date: 21 Aug 92 21:03:21 GMT
Organization: Central Transport, Warren, MI


Are there any tests that I can run on my computer to see whether or not
Linux will run on my system? (WITHOUT loading Linux itself).
(Cache test, AMD386/40 test, etc...)

I'd like to run some tests before I go to the effort of getting Linux
and installing it on my system...

Thanks,


car.
-- 
Christopher A. Rende           Central Cartage (Nixdorf/Pyramid/SysVR2/BSD4.3)
uunet!edsews!rphroy!trux!car   Multics,DTSS,Unix,Shortwave,Scanners,UnixPC/3B1
car@trux.mi.org                Minix 1.2,PC/XT,Mac+,TRS-80 Model I,1802 ELF
trux!ramecs!car     "I don't ever remember forgetting anything." - Chris Rende
Newsgroups: comp.os.linux
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Subject: Re: header woes with 2.2.2d
Reply-To: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Organization: The Internet
Date: Tue, 18 Aug 1992 17:35:56 GMT

   From: davidsen@ariel.crd.GE.COM (william E Davidsen)
   Date: 18 Aug 92 13:51:35 GMT

     At the risk of sounding as if I'm complaining, I think the "phase
   errors" betweeen the ps, kernel, and gcc packages is getting to be
   enough hassle that the various maintainers should get together and agree
   on something and stick to it. Evertime a new version of one comes out,
   it seems to be a huge hassle getting it to work with the other two.

Don't take the newest version then!  Stick with 0.96c, and don't take a
new version until it's become fully stable.  After all, that's what
happens when you shell out megabucks for commercial software --- you
only get releases once every six months to every few years.  If you took
0.96c, and didn't upgrade to 0.97, or 0.97pl1, you'd have a perfectly
stable system.  I suggest that those people who are complaining take
either the MCC release, or the SLS release --- AND THEN NOT UPGRADE.

What you're seeing is the nature of distributed development, and it's
what has allowed Linux to grow so fast.  The main feature/problem is
that the kernel is continuing to evolve, and it is continuing to gain
new features and its internals have been revamped to make it be
stronger, better, faster, etc, etc.

Asking Linus, et. al to "stick to it" would mean freezing kernel
development.  It would mean abandoning new changes to eliminate the 64
process limit, and to make V86 emulation mode simpler to implement.  
That would be a Bad Thing.

							- Ted

P.S.  Just for the record, my personal system at home was at 0.95 long
after the 0.96[abc] releases were out.  I was busy doing other things,
and I didn't see the point in upgrading to one of the more recent
releases.  Since I wasn't doing active kernel development at the time,
it didn't make a difference.  If you want stability and a production
system, don't live on the bleeding edge.....
From: dminer@cs.umr.edu
Newsgroups: comp.os.linux
Subject: Re: Linux Documentation
Date: 16 Aug 1992 11:27:45 -0500
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu


In article <1992Aug13.171211.26345@athena.mit.edu> komarimf@craft.camp.clarkson.edu writes:
>I'll volunteer for working on the documentation for linux.  At this point,
>I won't be able to start writing until the end of august (Downloading 13
>megs of stuff at 2400 bps is really really slow...).  Once I get back to
>school, I'll be able to keep up to date and make some current
>documentation that can be printed out or whatever.
>All I ask is that I get a rough idea of what everyone wants to see in the
>documentation.
>
>-Mark
>
>- Mark Komarinski - komarimf@craft.camp.clarkson.edu

	Mark, please join the mailing list
linux-man@stolaf.edu

	We are working on the documentations in a "formally" way.  I
am the Hackers' Guide Coordinator and would LOVE the help.. *hint*
But there are many areas to choose from or if you find something that isn't
being covered you can cover it. :)  
	All in all, if you have a beef about docs (other than software
packages, but we may try anyway) let us know at the above address or
join us.

Well, that's my pitch, :)
Dan Miner
Hackers' Guide Coordinator/writing
-- 
 Dan Miner
                           		 email: dminer@cs.umr.edu
Computer Science          
University of Missouri-Rolla             "It all begins with a glimmer."
From: copernicus@digund.uucp (Copernicus) 
Newsgroups: comp.os.linux
Subject: Linux support BBS- what h
Date: 21 Aug 92 20:12:00 GMT
Distribution: world
Organization: Digital Underground - PRIVATE
Reply-To: copernicus@digund.uucp (Copernicus) 

JMC:>What ever became of the Linux BBS on 508-793-9568? It was supposed to
JMC:>be for people with no Internet access so they could get Linux files.
JMC:>Everytime I call it, I handshake with a modem then nothing! My terminal
JMC:>doesn't echo local commands when I try to type anything. I hit enter
JMC:>a few times, still nada. I end up having to drop carrier and disconnect.
JMC:>--
JMC:>......................................................................
JMC:>shamus@eskimo.celestial.com            Jay Mottern in Sunny Seattle

JMC:>        Disclaimer: I didn't write this, Elvis did.

Call my system:

Digital Underground - 812-941-9427 - v32bis, v32, v42bis, v42, 1.5gig
Latest in Linux and 386BSD (sorta) files.

Chris Nalley
---
 . SLMR 2.1 . For A Hobby -- This SURE Is Getting EXPENSIVE!
                                                                                              
Newsgroups: comp.os.linux
From: mcguirk@enuxhb.eas.asu.edu (Dan McGuirk)
Subject: How do I get rid of vt100 graphics chars?
Organization: Arizona State University
Date: Wed, 19 Aug 1992 03:27:28 GMT

Sometimes, if I accidentally try to display a binary file, my tty gets
thrown into a mode where all lowercase characters appear as vt100
graphics characters.  I've tried various things with stty and setterm,
but I can't seem to find the command to get the terminal back to
normal.  Could some enlightened person out there tell me how to fix
this?

I'm sure everyone else knows how to do this by now, but I never
figured it out, and it's getting annoying having a bunch of terminals
disabled because they're showing these strange characters...
--
Dan McGuirk                                      mcguirk@enuxhb.eas.asu.edu
Newsgroups: comp.os.linux
From: Ching-Hsiang Chen <chchen@stat.fsu.edu>
Subject: Dial-in and kill -HUP 1
Reply-To: chchen@stat.fsu.edu
Organization: The Internet
Date: Fri, 14 Aug 1992 11:46:59 GMT


 Thanks to those who were so kind to help me in modem dial-in
problem. Since the getty_ps program needs M4 to compile the
manual pages and I am so lazy, I adopt the original getty
approach. I created the following 4 files to make things easy.
To allow remote dial-in, I just give the command 'dialin' and
to restore the modem and/or to allow dial-out, I use 'dialout'.
One small problem is that the 'init' and 'kill' from MCC-INTERIM
0.96 root disk can not work together to allow 'kill -HUP 1'
to kill the spawned getty. I need to retype 'kill -HUP 1'
several times or to kill the process by its job ID in order
to make it disapper under 'ps gu'. Any idea?

Steve Chen              chchen@stat.fsu.edu

   file name 'dialin' (put in /root/bin )
--------------------------- cut here -----------------
#! /bin/sh
cp /etc/inittab1 /etc/inittab
echo ate0s0=2 >> /dev/ttys1
kill -HUP 1
--------------------------- cut here -----------------

   file name 'dialout' (put in /root/bin )

--------------------------- cut here -----------------
#! /bin/sh
cp /etc/inittab0 /etc/inittab
echo ate1s0=0 >> /dev/ttys1
kill -HUP 1
--------------------------- cut here -----------------

    file name 'inittab0'  (put in /etc)

--------------------------- cut here -----------------
tty1:console:/bin/getty 9600 tty1
tty2:console:/bin/getty 9600 tty2
tty3:console:/bin/getty 9600 tty3
tty4:console:/bin/getty 9600 tty4
--------------------------- cut here -----------------

    file name 'inittab1'  (put in /etc)

--------------------------- cut here -----------------
tty1:console:/bin/getty 9600 tty1
tty2:console:/bin/getty 9600 tty2
tty3:console:/bin/getty 9600 tty3
tty4:console:/bin/getty 9600 tty4
ttys1:vt100:/bin/getty 2400 ttys1
Newsgroups: comp.os.linux
From: lcd@ais.org (Leon Dent)
Subject: Re: Source for the rootdisk programs. Where?
Organization: UMCC
Date: Tue, 18 Aug 1992 11:30:35 GMT

In article <1992Aug18.061057.12073@muddcs.claremont.edu> jwinstea@fenris.claremont.edu (Jim Winstead Jr.) writes:
>(Note:  I will eventually make my patches for the GNU utilities
>available, but it's not one of my top priorities.  And before any
>bonehead who thinks he knows all there is to know about the GPL wants
>to squeak - refresh yourself on how long it took NeXT to make
>available their patches to the GNU stuff (gcc, in particular) to
>people who had *paid* them for it.)
>

Do you know if your GNU patches are significantly different than Rick
Faith's ports of GNU stuff?


Leon Dent
lcd@ais.org
From: khera@cs.duke.edu (Vivek Khera)
Newsgroups: comp.os.linux
Subject: Re: Screen Capture
Date: 19 Aug 92 21:53:12 GMT
Distribution: comp.os.linux
Organization: Duke University CS Dept., Durham, NC
In-reply-to: davidsen@ariel.crd.GE.COM's message of 17 Aug 92 14:59:58 GMT
X-Md4-Signature: 62f939f5ea0e828008fbb420c10c2bee

In article <1992Aug17.145958.2724@crd.ge.com> davidsen@ariel.crd.GE.COM (william E Davidsen) writes:


     You can add ppm as one of the supported output types of gnuplot and be
   a benefactor of mankind.

gee, when i do a "set term <RET>" in gnuplot, some of the supported
terminals are:

              pbm  Portable bitmap
              pgm  Portable graymap
              ppm  Portable pixmap (color)
       postscript  PostScript graphics language [mode "fontname" font_size]

so it looks to me like some other benefactor has already benefitted
mankind.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Gradual Student/Systems Guy  Department of Computer Science
Internet:   khera@cs.duke.edu             Box 90129
            (MIME mail accepted)          Durham, NC 27708-0129 (919)660-6528
Newsgroups: comp.os.linux
From: poe@daimi.aau.dk (Peter Orbaek)
Newsgroups: comp.os.linux
Subject: Re: Getty security bug ?
Date: 19 Aug 92 09:24:27 GMT
Organization: DAIMI: Computer Science Department, Aarhus University, Denmark

hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:

>Yes. It also happened to computers in our school. I sometimes got into someone
>else's account. They have fixed it now.

>-- 
>H.J.
>Gcc/libc maintainer for Linux.
>In article <2960@ariel.its.unimelb.EDU.AU>, pdp@ariel.its.unimelb.EDU.AU (Paul Douglas Page) writes:
>|> without logging out correctly the session remains active so the next caller gets to coninue on with the previous callers session. It happens with both my internal and external modems so it's not a cable problem.
>|> Any suggestions?

If the shell doesn't die, there is not much that getty or anything else can
do about it. The getty process is long gone when the shell is started, and
will not be re-spawned until the shell dies.

On an dial-in line the shell should get a SIGHUP when the carrier drops, and
this should in most cases kill the shell.

	- Peter.

-- 
Peter Orbaek <poe@daimi.aau.dk>
Hasle Ringvej 122, DK-8200 Aarhus N, DENMARK
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Newsgroups: comp.os.linux
Subject: Re: X*nix emulation test version on uunet
Date: 13 Aug 92 02:07:15 GMT
Reply-To: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Organization: The Internet

|From: lfoard@Turing.ORG (Lawrence C. Foard)
|
|I've uploaded a test version of the X*nix emulation program to
|ftp.uu.net, its in /tmp/xenix.tar.Z
|
|BTW-uunet files expire in 4 days.

Available on tsx-11, in ~ftp/ALPHA/xenix/xenix.tar.Z, on a somewhat more
permanent basis.

							- Ted
Newsgroups: comp.os.linux
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: What happened to nic.funet.fi
Date: 12 Aug 1992 15:18:01 -0500
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

erc@Apple.COM (Ed Carp) writes:

>Hmmm...anyone know what happened to nic.funet.fi?  DNS says that it doesn't
>exist... :(
>-- 
>Ed Carp, N7EKG     erc@apple.com                801/269-8125
>"This is the final task I will ever give you, and it  goes  on  forever.   Act
>happy, feel happy, be happy, without a reason in the world. Then you can love,
>and do what you will."           -- Dan Millman, "Way Of The Peaceful Warrior"

Yea, I  get the  same  response. More than likely the router  is down again
on their side. I remember this happening  about a  week ago when patch1  came
out.


-----------------------                              ---------------------------
-Oh the joy of finding-       James Chacon           -probreak@matt.ksu.ksu.edu-
-That last pizza slice-                              ---------------------------
-----------------------				     --------------------------
-
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: shared libs - can everyone be happy with this?
Date: 14 Aug 92 14:57:54 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY


  I have an idea which I think might be a useful compromise between the
"never recompile" and the "last ounce of performance" approaches.
Unfortunately I can't find enough info on the GNU ld to know if it is
feasible.

  What I propose is to have a module at the start of the shared library
which is the jump table module. When the module is used it provides defs
for each of the library functions by use of the jump table. The
jumptbl() module would always be physically first in the library, so it
would be "in the same place." So far this sounds like the original idea,
right?

  If you didn't want to use the jump tables, you don't load the module
and you get linked to the real routines directly in memory in the slib.
The advantage of this is that you get all the benefits of the current
slib implementation in terms of performance.

  This would allow
  a. static link - runs anywhere
  b. dynamic link - must relink for new slibs, but faster than -
  c. jtablink - no need to relink for new libs, slightly slower than (b)

That would let the user decide what combination of size, portability and
performance is best for each program, and that should make everyone happy.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    I admit that when I was in school I wrote COBOL. But I didn't compile.
From: eric@tantalus.dell.com (Eric Youngdale)
Newsgroups: comp.os.linux
Subject: Re: Problem w/ folppy boot when CD-ROM is attached to scsi controller
Date: 14 Aug 92 21:18:13 GMT
Distribution: na
Organization: Naval Research Laboratory

In article <1992Aug14.193537.15994@nas.nasa.gov> chiu@wk211.nas.nasa.gov (Ing-Tsau Chiu) writes:
>I got the following message when booting Linux 0.97 from floppy
>
>  aha1542_queuecommand: Two concurrent queuecommand?
>  70 00 02 00 00 00 00 0a 00 00 00 00
>
>I have an Adaptec 1542B scsi controller and a Toshiba XB3201 CD-ROM
>drive.  The computer is a clone 486/33 w/ Maxtor LXT-535 scsi disk.

	There are bugs in the error handling code in the stock scsi drivers
in 0.97.  (I am not sure, but as I recall, the standard CDROM drivers treat
the CDROM like a hard disk).  There are patches to fix this in the
cdrom-0.2.tar.Z distribution, which is available on tsx-11.mit.edu.

	I would be interested in knowing if there are any problems after you
have installed those patches.

-Eric
--
Eric Youngdale
eric@tantalus.nrl.navy.mil
Newsgroups: comp.os.linux
From: zhao@unixg.ubc.ca (Jiansheng Zhao)
Subject: Re: Motif Window Manager on Linux??
Keywords: is it possible?
Organization: University of British Columbia, Vancouver, B.C., Canada
Date: Thu, 20 Aug 1992 15:49:01 GMT

In <1992Aug20.031801.8851@monu6.cc.monash.edu.au> int177c@aurora.cc.monash.edu.au (Jae Won) writes:

>Just wondering: is there any possibility MWM will be ported to X386? Or is it
>just a wishful thinking....is there copyright prob? Oh well. Like isaid,,just wondering.

>Jae

mwm comes with SLS package, and it is working. You can find SLS package at
tsx-11.mit.edu.


-- 
Jiansheng Zhao
Dept. Chem. Eng, Univ. of B. C., Canada. V6T 1Z4
zhao@unixg.ubc.ca
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Memory mapped files?
Organization: University of Colorado at Boulder
Date: Thu, 13 Aug 1992 20:08:35 GMT

In article <1992Aug13.143944.17119@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
>In article <1992Aug13.054653.29996@colorado.edu>, drew@kinglear.cs.colorado.edu (Drew Eckhardt) writes:
>| In article <1992Aug12.215042.5114@murdoch.acc.Virginia.EDU> lfoard@Turing.ORG (Lawrence C. Foard) writes:
>| >Is there any soft of project underway to implement memory mapped files
>| >in Linux? It seems that the shared library code is pretty close except
>| >that it doesn't support writting pages back to the library file.
>| >
>| >Has anyone looked into what would be involved?
>| 
>| Ideally, some one will implement something along the lines of a 
>| vnode based vm system, where each virtual memory object has a mapping
>| and certain characteristics associated with it.
>
>  How about for a start someone fix mmap() to work? As the notes say "it
>works well enough for X," but it sure isn't a generally working
>implementation.

mmap() was only put in so that we could run 'X'.  The code reveals 
the follow restriction : 

        /*
         * for character devices, only /dev/mem may be mapped. when the
         * swapping code is modified to allow arbitrary sources of pages,
         * then we can open it up to regular files.
         */

        if (major != 1 || minor != 1)
                return (caddr_t)-ENODEV;

So, you can mmap() /dev/mem, and map the frame buffer into your process's 
space, but nothing else.

>
>| That mapping could be to a file, to a device, etc.  Ideally, a file mapping
>| would be a mapping to blocks as specified by the file's bmap, with those
>| blocks shared with buffercache.  Shared libararies / mmap / sysV 
>| shared memory semmantics could be implemented on top of this 
>| internal structure, quite easily.
>
>  There is a question of what mechanism mmap uses now (I don't have
>source code at work). 

Basically, it scrambles the page tables, and points an area in 
your process's address space someplace else in physical memory.

>| Not 4G per process.  You still want room for kernel space in the 
>| same page table, so you can keep most of the same code in place
>| for kernel<>user space transfers, with kernel and user space in 
>| different x86 segments. Linus has something going with
>| > 3G per process, with the remainder allocated to the kernel - 
>
>  I guess HURD will have 1GB for the user, 1 for the kernel, and 2 for
>the new release of emacs ;-) 

And the delays we're seeing are probably the HURD folks waiting for 
64 bit machine donations, because they've discovered that EMACS 19
won't run in a puny 32 bit address space....
 
-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but neither is as bad as AT&T.  Boycott AT&T, and let them know how you feel.
From: David.Fox@Saigon.COM
Newsgroups: comp.os.linux
Subject: linux .97/.95
Date: 9 Aug 92 03:52:38 GMT
Organization: Station Zebra Corp, Sunnyvale CA Ph:408-739-1520

Hi Linuxers,

I'm a bit new to linux, but I have already gotten 0.97 boot disk and I have
had 0.95 root disk for some time.  I've seen info about 0.97 boot so I got
it of course, but is it OK to run 0.95 root with 0.97 boot or should I 
really update my root disk?  I haven't seen anything about new root disk
versions.

reply to slix%svcs1.mips.com or davidfox@west.darkside.com or here.
From: imhw400@indyvax.iupui.edu
Newsgroups: comp.os.linux
Subject: Re: EISA bus machines
Date: 23 Aug 92 08:02:48 -0500

In article <1992Aug23.054741.316@athena.mit.edu>, tytso@ATHENA.MIT.EDU (Theodore Ts'o) writes:
[....]
> The same situation is true for the MCA bus, although that will be much
> harder, since MCA isn't even backwards compatible with ISA.  At least
> with EISA, someone could borrow a ISA hard disk controller while he/she
> was debugging the EISA controller; thus development would be much easier
> under EISA than it would be under MCA.  That's not to say that it
> wouldn't be possible to include MCA support as well; it would just be
> much more complicated.  So I wouldn't hold your breath for MCA support,
> but EISA support is within the realm of possibility, assuming someone
> blessed with such a machine is willing to look at writing Linux drivers
> for these new controllers.

OK, I'll bite -- why can't an MCA implementation just use the protected-mode
drivers that came with the machine, that is, the ABIOS?  MCA "drivers" should
be very simple:  set up the request block, call the ABIOS routine, interpret
the updated request block.  But I haven't actually tried it, so what have I
missed?
-- 
Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
Celebrate freedom:  read a banned newsgroup.