HDTenEightyP/NetNews huggingface dataset:
From: ejohnson@enuxha.eas.asu.edu (Eric R. Johnson)
Subject: Re: 99p3+extfs: Files disappeared miraculousely
Organization: Arizona State University, Tempe, AZ
Date: Tue, 26 Jan 1993 15:42:21 GMT

In article <michaelw.727945054@mcshh.hanse.de> michaelw@mcshh.Hanse.DE (Michael Will) writes:
>Then after I downloaded some things, I found some files I where shure not to
>have deleted where gone too.
>
>...
>
>Anyone had any experiences of this kind?

Yes, but it was rather nebulous when it happened, and it has not happened again
with me.  I did get a spontaneous re-boot once :-)
Newsgroups: comp.os.linux
From: fluet@ee.ualberta.ca (Kevin Blaine Fluet)
Subject: Re: BBS Package for Linux
Organization: University Of Alberta, Edmonton Canada
Date: Sat, 23 Jan 1993 05:56:35 GMT

wonge@fraser.sfu.ca (Edmund Wong) writes:
>that has that capability.  I haven't tested out PBBS(can be found
>at sunsite.unc.edu), because I always get a compilation error somewhere
>along the road, when I do a 'sh install.out.do' or something like that,
>so I gave up, hoping that sometime in the near future, a BBS will
>come out that may have the capabilities to handle incoming Fidonet
>calls as well as Internet packets(or whatever you call 'em).

Your file called "install.out.do" is actually "install.bbs.dontuse"
                                                           ^^^^^^^
with its title truncated.  The install script if for SunOS, so you have to
install manually.  The binaries were all included in the version of pbbs
that I got from Sunsite (I don't know which dir).  I don't have the thing
fully configured yet, so I can't give it a review.

I agree that a bbs system still has its purposes under unix.  I am setting
pbbs up mostly to allow people who aren't familiar with Unix (there are a
few, you know, out there in the real world) to download and try Linux.  I
will also be offering regular unix accounts, but the average DOS user
won't have a clue at least until they know a few basic commands.

-------------------------
Kevin Fluet
fluet@ee.ualberta.ca
-------------------------
From: sadkins@bigbird.cs.ohiou.edu (Scott W. Adkins)
Newsgroups: comp.os.linux
Subject: Re: Xwindows Virtual Desktop Size
Date: 22 Jan 93 02:38:30 GMT
Organization: Ohio University CS Dept., Athens

In article <19879@mindlink.bc.ca> Rob_Prior@mindlink.bc.ca (Rob Prior) writes:
>I was at a local computer fair recently and saw a display of 486's running (I
>beleive) SCO Unix and Xwindows.  The neat thing was, as you moved the mouse
>pointer 'past' the limits of the screen, the whole picture would scroll to
>follow it.  It was like having twice the space, but using a small window to
>scroll around on it.  Can this be implimented in Xfree?  I looked in all of
>the docs that I have and couldn't find anything...

Well, this is kind of supported in Xfree.  If you you use a lower resolution
grephics mode, then this is exactly what will happen.  You still get your
normal sized desktop, but now, not all of it can fit in the confines of 
your screen.  Moving the mouse to any edge of the display will effectively
scroll the rest of the desktop into view.

Alternatively, you can get the window manager TvTwm.  (The??? Virtual
Tabs Window Manager).  It allows you to have a huge desktop (you can
specify how big) and then provides a panner (which is just like a window
in itself) that allows you to essentially move the "screen window" over
the large desktop.  It isn't quite the same as moving the mouse to the
edge of the display, but the effect is kind of the same (in fact, it is
more impressive, IMHO).  Currently, there are people working on the 
port for tvtwm, and I hope they will make it available as soon as it
is finished.

Hope this helps.
Scott.
-- 
         Scott W. Adkins           Internet: sadkins@ohiou.edu
         ~~~~~~~~~~~~~~~                     ak323@cleveland.freenet.edu
    Ohio University of Athens        Bitnet: adkins@ouaccvma.bitnet
From: ry40@rz.uni-karlsruhe.de (Suffel / Hanauer)
Newsgroups: comp.os.linux
Subject: SLIP or KA9Q ?
Date: 25 Jan 1993 11:21:13 GMT
Organization: University of Karlsruhe, Germany
Distribution: world
NNTP-Posting-Host: rz30.rz.uni-karlsruhe.de

i want to use SLIP, but at sunsite.unc.edu it is private or empty.
Where can i get it, or should i use ka9q ?
I don't want to use kermit, with vt100, because it has to much overhaed.

Your     
M. Suffel
From: Ulf.Bartelt@p2.f3420.n241.z2.fidonet.org (Ulf Bartelt)
Newsgroups: comp.os.linux
Subject: FidoNet software
Date: Thu, 21 Jan 1993 12:39:40 -0800

Hi Louis!

Tuesday January 19 1993 09:03, Louis Lagendijk an All:

 LL> There is also Nixmail (mxm0.05q.tar.Z), a mailer written from
scratch
 LL> that I want to try soon.

I tried nxm...
It's still somewhat buggy but useable...

The more ppl use nxm, the more bugreports will be mailed to nxm's
author... ;-)
Try it...

I just juse nxm to poll from linux, reading mail still is a job for DOS
:(((

Bye,
     Ulf

 * Origin: Love is dead in Metropolis... (2:241/3420.2)

Newsgroups: comp.os.linux
From: vera@fanaraaken.Stanford.EDU (James S. Vera)
Subject: Re: kernal error(?) 99p4 (not p5)
Organization: Program Analysis and Verification Group, Stanford University
Date: 27 Jan 93 00:29:34 GMT

vera@fanaraaken.Stanford.EDU (James S. Vera) writes:

>I don't know if the following is of interest
>but I got the following messge:

>>FP emulator: internal error type 0x0112
>>At 6026CDDA d9 ff (f8+7)
>>  SW: b=1 st=0 es=1 sf=1 cc=0000 ef=111111
>>  CW: ic=0 rc=00 pc=10 iem=0     ef=100010
>>[data] + .8ba2 e900 0000 0000 e-1      Valid

>Means nothing to me but maybe it means something to someone else.

>Running 99p5, the X in SLS and term1.01

Loosing track of my patches, that should be 99p4 not p5 (of course).

James S. Vera       |         Internet         | Voice: +1.415.723.1089 
Stanford University |  vera@anna.stanford.edu  | FAX:   +1.415.725.7398

Newsgroups: comp.os.linux
From: eric@tantalus.nrl.navy.mil (Eric Youngdale)
Subject: Re: lfs 0.6 --> "xfs"
Organization: Naval Research Laboratory
Date: Thu, 21 Jan 1993 21:18:34 GMT

In article <1993Jan21.193335.7818@aio.jsc.nasa.gov> mancus@carla.jsc.nasa.gov (Keith Mancus/MDSSC) writes:
>  How about "lefs", for "Linux Extended File System"?  Easy to pronounce,
>very succinct, and clear.

	Or better yet, "lefse".  The 'e' does not stand for anything in
particular, but given the scandanavian origins of Linux, it would seem a
fitting name.  More Norweigian/Swedish than Finnish I suppose.

-Eric


-- 
A host is a host from coast to coast.....eric@tantalus.nrl.navy.mil
& no one will talk to a host that's close..........................
Unless the host (that isn't close).................................
is busy, hung or dead................................Eric Youngdale
Newsgroups: comp.os.linux
From: marc@r-node.pci.on.ca (Marc G Fournier)
Subject: need a clue as to where to look...
Organization: R-node Public Access Unix - 1 416 249 5366
Date: Tue, 26 Jan 1993 01:51:50 GMT

Help

I just installed 0.99pl4 and seem to be getting better results with
things then pl2 (but I may also be hallucinating it *sigh*)

Something is killing my uucico's and my tcp/ip processes :(  I realize
that this isn't the most informative post, but I just don't know where 
to look :(  Can someone give me a clue as to where/what I should be
looking at/for?  Is this a known bug, or is it just happening to me?

Also,  what is  /etc/ftpaccess?  format??  I've looked at other, 
Internet, sites, but noone seems to have that file, or information on it :(
Can someone direct me to some sort of man page or informational that 
describes the set up of it?

Hmmmm...thanks to he who told me about the debug levels for uugetty/getty. 
I finally got the high speed modem to work.  I had read both the man
pages that comes with the distribution, as well as that which comes with
gettyps, but neither detailed the  'debug' option...ended up finding
it in the README for  gettyps :)

Other then that...things seem to be working great...SLS v1.0 installed
much much easier then the previous version...most definitely liked
how it told me  how much space each  package was going to kill of my
hard drive :)

Thanks to all for the help...and to all who made this OS possible :)

marc

-- 
Marc G. Fournier      | R-node Public Access Unix running Linux 0.99p1
Etobicoke, Ontario    | 416-249-5366   24hrs 7 days/week   network email
voice: 249-4230       | shell accounts available  2500+ newsgroups  FREE
marc@r-node.pci.on.ca | Telebit WorldBlazer/SupraModem2400/Cardinal 2400
From: hedrick@geneva.rutgers.edu (Charles Hedrick)
Newsgroups: comp.os.linux
Subject: Re: KA9Q
Keywords: KA9Q Help SLS 0.98pl5
Date: 25 Jan 93 03:46:30 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

jmk@kksys.com (Jim Kaufman) writes:

>1) I downloaded the source files for KA9Q.7 from sunsite. Did I get the
>   right file?

Yes.

>2) If so, I am confused by the README.WD file. It tells me to move weregs.h
>   and we.c (possibly wrong names - I'm at work) to /kernel/chr_dev directory 
>   and make some changes to main.c and the Makefile.
>   However, there IS a version of we.c and weregs.h in
>   /net/tcp. Does one supercede the other or what?

The WE code with KA9Q is an older version of the WE code with TCP.
Unfortunately the facility that KA9Q depends upon (the ability to open
the raw device) was removed in later versions.  This means that you
can't use KA9Q and the kernel TCP with the same kernel.  Note also
that the kernel code distributed in KA9Q hasn't been tested since
about 0.97.  I should warn you that KA9Q is used primarily with async
lines.  While I believe it works with WD8003's if the kernel support
is properly installed, some people have reported problems getting
various WD things properly configured.  Note that I had access to
appropriate hardware for only about 4 hours, so this is hardly
finished code.  If you have Ethernet, I'd guess that you would be
happier using the kernel TCP implementation rather than KA9Q.

>3) Do I need to rebuild the kernel or is tcp/ip support and/or WD8003
>   support built in? (SLS 0.98, pl5).

Recent versions of SLS have the kernel TCP builtin, but not the
support for KA9Q.  I don't know whether 0.98 is recent enough, but
I think so.
From: esw@po.CWRU.Edu (Eric S. Wallace)
Newsgroups: comp.os.linux
Subject: 0.99 problem
Date: 23 Jan 1993 18:58:23 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: slc12.ins.cwru.edu



   I recently tried upgrading to version .99 of Linux and discovered that
the new kernel crashes at start up. I had to configure by hand since the
'Configure' script doesn't work (it only processes the first couple lines
of config.in before aborting), so its possible that something is configured
incorrectly. Here is what the init routines spit out at boot time:

Serial driver version 3.8 with no serial option enabled
ttys0 at 0x03f8 (irq = 4) is a 16450
8 virtual consoles
lp_init: lp1 exists (0)
Unable to handle kernel paging request at address c0400000
Oops: 0002
EIP:    0008:0003A410
EFLAGS: 00010287
fs: 0017
base: C0000000, limit: 000A0000
Pid: 0, processs nr: 0
cb 00 00 40 42 39 ca 7c f7 89
task[0] (swapper) killed: unable to recover
kernel panic: Trying to free up swapper memory space
In swapper task - not syncing

The computer freezes at this point. Does anyone know how to interpret those
messages? FYI, the following options were configured:

CONFIG_BLK_DEV_HD
CONFIG_TCPIP
CONFIG_MAX_16M
CONFIG_M486

CONFIG_MINIX_FS
CONFIG_PROC_FS
CONFIG_MSDOS_FS

Thanks in advance,

Eric Wallace
esw@po.cwru.edu
Newsgroups: comp.os.linux
Subject: Re: SCSI Autodetect? Static table? (Was: ST01/02 and Syquest 5110)
From: jesse@mars.slu.edu
Date: 25 Jan 93 12:33:12 CST
Organization: Parks College St. Louis Univ.

Gentlemen,  My two cents worth:

I dislike the idea of auto-renumbering the drives when one is unpluged. 
Another flavor of Unix does this.  What happened is that I went on vacation and
my assistant removed drive 1.  This automapped drives 2 and 3 to 1 and 2.  But
he didnt change fstab.  This resulted in fsck checking the WRONG partition d
instead of h and corrupting the disk.  

Apollo and Evans & Sutherland (sp?) have both developed another method to
handle the multiple controller/disk/partition problems.  What E&S does is call
their disks  isc0d0p11 for Internal Scsi Controller 0 Disk 0 Partition 11.  This
will allow multiple controllers, disks and partitions.  Same for tapes.  Then
what I have done is create a link between isc0t0 to exabyte, or whatever.  I
can then use a meaningfull name like /dev/exabyte to access a device.

This approch eliminates the problems with drives changing names, and allows you
to assign your own name to the disk.

Jesse

Newsgroups: comp.os.linux
From: ruediger@ramz.ing.tu-bs.de (Ruediger Helsch)
Subject: Re: Variable-length device major/minor (was Re: SCSI Autodetect?)
Organization: Mechanikzentrum, Technische Universitaet Braunschweig, Germany
Date: Fri, 22 Jan 1993 16:01:11 GMT

chip@tct.com (Chip Salzenberg) wrote:
>According to torvalds@klaava.Helsinki.FI (Linus Torvalds):
>>So, the only remaining reason for not making dev_t a 32-bit integer is
>>my lazyness (the win/work ratio is way too low).
>
>If the goal is to make MINOR(dev) greater than eight bits wide, why
>not consider making MAJOR(dev) smaller than eight bits?

Why should anybody do this? He could just as good make the dev_t
32 bit wide. HP-UX does this, taking 8 bit for major and 24 bit
for minor. Works very good.
If you invest the work to change something, please don't waste your time
counting bits like the IBM engineers did it with all those *&$% PC
interfaces.

Ruediger Helsch <ruediger@ramz.ing.tu-bs.de>
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.os.linux
Date: Mon, 25 Jan 1993 21:48:10 -0500 
From: Frank T Lofaro <fl0p+@andrew.cmu.edu>
Subject: Re: Linux .99pl4

    I have the same problem with the SVGA modes being a blurry mess, or
not actually chaging the font size, even though the kernel thinks it
has. I also have an Everex Viewpoint (but with only 512K, but this is
probably not a factor) on a 486/33 Everex Tempo. Could it be that the
autodetect for the video card in the kernel is mis-recognizing it,
incompatible, or just plain hosed? Or is the video BIOS bad. The card
works fine under X windows, both mono and color (using ET4000 as the
chipset when using color) for all resolutions that my monitor and video
memory can support. Weird, very weird. Maybe we should have a way to
select video modes based on chipset, that would fix this problem, and
also allow changes while the system is up, for those of us with ET4000's
or other such cards.
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: Groff won't do PostScript! Sob!
Date: 26 Jan 1993 07:02:22 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

cs911461@ariel.yorku.ca (CHRISTIAN D. ARMOUR) writes:


>Oh dear...

>Just on the eve I have to hand in a major project, I discover
>to my epic chagrin that the groff I have can't make PostScript
>files.  I'm trying to view/print the man page I just wrote to
>accompany the software I wrote beforehand.  Here's my command
>line:

>$ groff -Tps -man lc.1 > lc.ps

>Here's what it says:

>gtroff: can't open `DESC'
>gtroff: fatal error: sorry, I can't continue

>So I look in /usr/lib/groff/font for DESCs and all I see are:

>./          ../         devascii/   devdvi/     devlatin1/

>...each one of which has a DESC subdir...

>This is very unfortunate.  Can anyone assist in finding the 
>/devps/DESC's?  

Whomever compiled the version of groff you are using decided not to
use postscript for some reason. I also noticed the X device drivers 
weren't there either.

Your best bet is to get the groff source down from you favorite GNU ftp
site and compile it. Compiles with no problems here, and that way you
can decide on the devices included and the default output.

James
Newsgroups: comp.os.linux
From: spierce@wam.umd.edu (Stephen Pierce)
Subject: Two Bugs.
Organization: University of Maryland, College Park
Date: Sat, 23 Jan 1993 07:22:11 GMT

   I would like to report two bugs in Linux, both involving tcp/ip. 
I will be using tcp/ip extensively, under stress conditions, so I
will most likely find bugs. I do not know of whom to send bug reports
/fixes to, so I am posting here. Please, if you know of whom to send
these reports too, enlighten me.. <grin>

  Bug one is ion telnet. I am not sure what happens, but the telnet
program (and i think telnetd) locks up. This is frusterating, especially
in talks, because I can see the keystrokes being sent to me, but I can
not respond. I think that this is important, because when I try
to have the telnet program 'send ayt' nothing comes back. I am using
the built-in SMT Elite 16 netowkr driver and the SLS .99.1 kernal.

  The other bug is in my mud. I just brought it up and noticed some
sort of memory leak in it. It seemed to grow about 5-15K every 20 sec 
or so. I had a player log off, and it freed up about 50K, but abosrbed
it all back afterwards. the mud continuied to absorb memory, even
when no-one was on. I have 4 megs real, and 4 megs swap. 

  I am willing and able to try fixes and such. I like to be on the 
bleeding edge <grin>.

 Thanks to Linus, Peter, and everyone else whom I did not mention!
LINUX IS THE BEST THING TO HAPPEN TO THE i386 SINCE THE 387!

Steve

Newsgroups: comp.os.linux
From: glgam@cc.newcastle.edu.au (GLGAM)
Subject: Unable to handle kernel paging request..
Organization: University of Newcastle, AUSTRALIA
Date: Tue, 26 Jan 1993 07:02:05 GMT

Hi Experienced Linuxers,
	Today I attempted to begin some sort of hard drive installation
of Linux on my SX-20.  	I tried several versions of the boot/root images
with results varying from - continual rebooting to the following message

' Unable to handle kernel paging request at address c0057704'

Can someone enlighten me ?

The motherboard is an Informtech with 1 meg of 100ns DIP and 4Mbx9 70ns
SIMM memory, a seagate IDE HDD and an EGA card (waiting to afford Tseng
card and SVGA monitor)...

Regards,

Scott Mackenzie
From: benj@s-link.escape.de (Benjamin Harling)
Newsgroups: comp.os.linux
Subject: Re: remove LILO?
Organization: -S-LINK-> Public Mailbox, Braunschweig, Germany
Date: Tue, 26 Jan 1993 12:00:00 +0100

CHCHEN%STAT@S-UUCP.ZER meinte am 23.01.93
zum Thema "remove LILO?":

> From: chchen@stat (Ching-Hsiang Chen)
> Subject: remove LILO?
> Message-ID: <1993Jan23.093342.24069@mailer.cc.fsu.edu>
> Organization: Florida State University
>
> I am going to have a new 200mb IDE drive next week and my old 105mb IDE
> will be in my wife's PC. I had installed LILO before I saw the backup
> MBR caution in the LILO documentation. I am 99% sure that LILO had taken
> over DOS MBR. Is the only way to remove LILO and Linux from my old IDE
> to destroy all partitions setup (including my DOS partition)?

My Coherent manual says that if you changed the MBR and did not backup the
original, one way to work around is to destroy the MBR, either with the
program which wrote it or with some kind of tool (Norton Utilities or likes or
with the DIAGNOSTICS menu of the AMI BIOS) and have it rebuild by DOS fdisk.
You just have to overwrite the last two bytes. If no valid signature appears
at the end of the current contents of the Master-Boot-Block, DOS fdisk will
write a new one. But there is no guarantee that fdisk will actually do so.
Their experience is that you shouldn't expect any data to be available after
fdisk rewrites an invalid MBR, even if previously existing DOS partitions
are re-allocated with identical cylinder ranges as at the time of their
initial creation. So backup your stuff.
The other way is to overwrite it with an MBR from another OS, which might
work with the OS/2 BootManager.


Gruss Benjamin

--
Benjamin Harling ++ 2:240/505.1 ++ benj@s-link.escape.de +++++++++++++++++
+++++++++++++++++++ benj@s-link.zer ++ 0531/791607 (Voice) +++++++++++++++
## CrossPoint v2.0 ##
Newsgroups: comp.os.linux
From: loser@clueless.newbie.tyro.org ()
Subject: Need proc fs information!
Organization: Workstations at Maryland, University of Maryland, College Park
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 25 Jan 1993 17:29:12 GMT


Well, the subject line says it all.  I'm looking for technical information on
the proc file system (its interface, how to program it, etc).  Thanks,

Jaime

Newsgroups: comp.os.linux
From: rchen@fraser.sfu.ca (Robert Chen)
Subject: Re: Filesystems for people providing packets
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Tue, 26 Jan 1993 19:32:18 GMT

In article <1993Jan26.023948.4305@cheshire.oxy.edu> rafetmad@cheshire.oxy.edu (David Giller) writes:
>bogstad@blaze.cs.jhu.edu (Bill Bogstad) wrote:
>>In article <1993Jan24.032251.22453@umibox.hanse.de> root@umibox.hanse.de (Bernd Meyer) writes:
>>>It's this:
>>>I want to encourage everyone who plans to upload any of his works to
>>>ftp-sites to use a file system that is NOT the minix one. The reason is that
>>>while names like "page-up-window" match the request "page-up-window.h" when
>>>used on that fs, it is a nightmare for everybody using a fs with long names 
>>>to rename all the files with truncated names.

>>	A better solution in my opinion is to use shorter filenames
>>(pgup-window.h for example).  Until efs, xfs or some other filesystem with
>>longer names becomes the "standard" Linux filesystem; it is preferable that

>overwrite the first with no error when untarring.  This is unavoidable
>on packages which originated outside Linux, but it would be nice if
>people would provide for the 14-char limit that is still common on
>UNIX systems today.
>
>-Dave


#ifdef SLIGHTLY_IRATE_MODE   (hit 'n' now, apologies in advance, etc)

Sigh...  Must we really condemn ourselves to names like dskblkdrv.c
for the rest of time because of bad decisions made 20 years ago?  Given
current trends, the minix file system is going to be around a very
long time.  The author of xfs respectfully suggests that we replace
the minix file system with the xfs because it has more functionality
than minix, while still being based strongly on the minix code so that
it retains most of minix's stability - a damn good idea IMO. 

But what happens?  People jump on him for his tyranical ways and 
for not adding every bell and wistle to the filesystem (bells that 
minix doesn't have anyway).  Then we busilly truncate perfectly good 
file names like page_up_window to pgupwin.  

I do not know of a modern Unix operating system that does not support
long file names.  Berkeley got it right years ago.  When linux 1.0
gets released and reviews start being written, people will see linux
with its 64 megabyte 14 character filename standard filesystem and
will think "gee, how cute, it's just like minix/coherent, only free."
I think that linux deservs better than this.  


Feeling better now,

- Rob
Newsgroups: comp.os.linux