HDTenEightyP/NetNews huggingface dataset:
From: ajt@puffin.doc.ic.ac.uk (Tony Travis)
Newsgroups: comp.os.linux
Subject: Re: Device names (was Re: ttys2 not responding)
Date: 27 Jul 92 13:08:49 GMT
Organization: Department of Computing, Imperial College, University of London, UK.
X-Newsreader: Tin 1.1 PL4

zlsiial@uts.mcc.ac.uk (A. V. Le Blanc) writes:
: In article <1992Jul19.163907.15892@doc.ic.ac.uk> ajt@swan.doc.ic.ac.uk (Tony Travis) writes:
: >Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin) writes:
: >This is very confusing - drive _letters_ are a DOS anachronism and
: >should have no place in Linux.  Drives should be numbered starting at
: >0 and partitions should be given letters starting a 'a' so eg....
: 
: When Linux first came out, its hard disks were numbered /dev/hd0, /dev/hd1.
: We changed somewhere around 0.12 or thereabouts; this was in no way a
: feature imported from MS-DOS; moreover I don't think there was ever a
: version of MS-DOS which called its hard disks A and B.
: 
: Having corrected this historical inaccuracy, I am puzzled about the

I think you are being pedantic, Owen.

Assigning drive _letters_ *is* a DOS anachronism (inherited from CP/M)
and even DOS refers to drives by drive number internally doesn't it? 
Also, Linux reports drives by number at boot-time.

: origins of the 'should' which you cite.  This question has been discussed
: over and over on the Linux standards mailing list.  Those people who
: believe Linux must do everything the way BSD does prefer the numbered
: drives, but there are important advantages to doing it the other way
: round; for example, Linux allows many more partitions on a disk than
: BSD does.

I was not aware of the discussions on the Linux standards list because
I don't read it.  I suspect lots of other people reading comp.os.linux
don't read the list either.

: A further consideration is this: virtually all Linux systems currently
: installed use /dev/hda and /dev/hdb for the drive devices; even SCSI
: systems which don't have hardware corresponding to /dev/hda have the
: device in the /dev directory.

so use links during a changeover period, then drop the old names.

: If you wish to continue this discussion, you might do so on the
: list linux-standards@banjo.concert.net; I wouldn't mind arguing

Is the fate of comp.os.linux to go the same way as comp.os.minix where
all the interesting discussions migrated to the beta-testers mailing
list and no-one outside that group knew what was happening to Minix?

: against your view in E-mail either.  But please don't publish
: prejudices as absolute truths.

Ouch!

Fortunately, I have my asbestos underpants on today ;-)

Other people responding to this thread have explained the BSD device
naming conventions, so I won't.  However, I would like to point out
that it is the features that different Unix systems have in common that
makes Unix an 'open' system - Please don't lose sight of that.

	Tony

--
Dr. A.J.Travis,                       |  Tony Travis
Rowett Research Institute,            |  JANET: <ajt@uk.ac.sari.rri>
Greenburn Road, Bucksburn,            |  other: <ajt@rri.sari.ac.uk>
Aberdeen, AB2 9SB. UK.                |  phone: 0224-712751
Newsgroups: comp.os.linux
From: negaard@aero.org (Eric Negaard)
Subject: /dev/fd1 not detected
Organization: The Aerospace Corporation, El Segundo, CA
Date: Mon, 27 Jul 1992 20:21:23 GMT

I've spent the last week or so installing Linux and getting it configured
the way I want.  I'm thrilled to have such a functional system at
home finally.  One tiny problem I thought I'd throw out is that
Linux doesn't seem to recognize my /dev/fd1 properly.

It correctly identifies fd0 at boot time (fd0 is 1.2M), and the second
(1.44M) drive works if I create /dev/PS1, it's only the auto-detecting
driver that doesn't seem to work.

At one time I removed the 1.2M drive and made the 1.44M drive be drive "0",
and that worked too (fd0 is 1.44M).  They just don't both seem to work
at the same time.

Any ideas?

My configuration is:

		Gateway 2000 486/33 ISA
		64 Kb Cache (disabled)
		8 Mb RAM
		1.2M 5.5" floppy 0
		1.44M 3.25" floppy 1
		CMS Jumbo 120 (DJ-10) tape backup
		2x200 Mb IDE drives
		ATI Graphics Ultra 1 Mb
		Microsoft Mouse

			Eric Negaard
From: vwllibmod@csghsg5a.bitnet
Newsgroups: comp.os.linux
Subject: patch for unzip sources on banjo
Date: 26 Jul 92 19:38:54 GMT
Organization: University of St.Gallen, Switzerland

I've uploaded 'unzipsrc.dff.Z' to /pub/Linux/Incoming on banjo.concert.net.

The patch is relative to 'unzipsrc.tar.Z' (can also be found in the incoming
directory on banjo). The patched sources are ready to compiled with GCC 2.2.2.
All executables have been successfully tested under Linux v0.96c-pl2

What's new?:
        o Targets 'linux' 'zi_linux' 'ship_linux' added to Makefile
        o Added a shell-script called 'Make_linux' to build/install 'unzip', 
	  'zipinfo', 'ship' and the corresponding man-pages.

Please have a look at the README's for more infos.

Regards,
--Fabian Mueller
From: rmk@rmkhome.UUCP (Rick Kelly)
Newsgroups: comp.os.linux
Subject: Re: Mail hint
Date: 21 Jul 92 03:16:00 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats

In article <1992Jul18.233313.19749@serval.net.wsu.edu> hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
>In article <1992Jul18.220856.22272@unislc.uucp>, erc@unislc.uucp (Ed Carp) writes:
>|> dhs@moeng2.minc.umd.edu (David H. Silber) writes:
>|> 
>
>[deleted]
>
>|> SVR4, and (2) to more accurately calculate throughput figures.  There are
>|> still problems with uucp, though.  I'm seeing uucico hang on a modem port without
>|> timing out - I wonder if it's related to H. J.'s recent patches affecting
>|> restartable system calls?
>
>I didn't change any sys calls. All is done inside the kernel.


Interestingly enough, I have Taylor UUCP up and running on Coherent 4.0
Beta.  I have seen the same uucico hang on a modem port problem, but it
only seems to happen every couple of weeks.  I haven't come up with a
reliable method of reproducing it yet.  It would seem that DTR isn't
changing state when the modem hangs up.

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
From: unixsys@ssg.com (Rick Emerson)
Newsgroups: comp.os.linux
Subject: Xphoon.  Again.
Date: 23 Jul 92 15:28:28 GMT
Organization: System Support Group

Well, to add to the fun, I need a definition for TIOCNOTTY which is sent to
ioctl.  The code piece in question reads:
if ( ioctl( tty, TIOCNOTTY, 0 ) < 0 )
   {
   # Gripe about tty and die
   }
   
A number of similar flags are defined in termios.h so I suspect this is
where this definition belongs, too.  Anyone want to give this a shot?

Rick


| Richard B. Emerson     | Replies may be sent to:                         |
| System Support Group   |         unixsys@ssg.com  -or-  rick@ssg.com     |
| Post Office Box 180    |-------------------------------------------------+
| Lansdale, PA 19446 USA |     "If I knew what I was doing,                |
| Voice: 215.855.1607    |      I wouldn't do it." - Me                    |
Newsgroups: comp.os.linux
From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
Subject: Re: tsx-11.mit.edu Linux
Organization: Harvey Mudd College, WIBSTR
Date: Tue, 28 Jul 1992 03:42:22 GMT

In article <8eR_8cS00WBFI=I0VM@andrew.cmu.edu> wm0i+@andrew.cmu.edu (Wayne P. Myers) writes:
>Is anyone else out there having problems ftp-ing from tsx-11.mit.edu?

It's not very helpful, but I haven't had any problems.

>Now I've ftp'd from this site in the past with no problems, and it
>works fine if I try it from banjo.concert, but I can't find
>rootimage-0.96c at that site.

You can't find rootimage-0.96c because there is no such thing.  The
latest release of the root image was rootimage-0.96, which is on banjo
in /pub/Linux/Incoming.

The next release of the root disk will be either root-0.97, or
root-0.96.1.  Revision letters are used for kernel updates, number for
root disk updates.
-- 
                                    +    Jim Winstead Jr. (CSci '95)
                                    |            Harvey Mudd College
                                    | jwinstea@jarthur.Claremont.EDU
                                    + This is all my words.  Honest!
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: Re: Where is mkfs?
Date: 22 Jul 92 10:36:23 GMT
Reply-To: LeBlanc@mcc.ac.uk
Organization: Computing Centre, University of Manchester

In article <2749@ariel.its.unimelb.EDU.AU> pdp@ariel.its.unimelb.EDU.AU (Paul Douglas Page) writes:
>Can someone please tell me were I can find the source to mkfs?
>I have looked in most of the source archives and have had no luck.

The source to mkfs and many other Linux utilities distributed as part
of the MCC interim releases of Linux can be found in the file misc.tar.Z
in /pub/linux/mcc-interim/0.96c/source_files at ftp.mcc.ac.uk; this
is mirrored at banjo.concert.net and at tsx-11.mit.edu.

     -- Owen
     LeBlanc@mcc.ac.uk
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Newsgroups: comp.os.linux
Subject: Re: Logging as root....bad idea?
Date: 23 Jul 92 23:56:13 GMT
Organization: University of Helsinki

bairstow@haydn.psu.edu (Steven Bairstow) writes:
>What I would like is a new version of rm, where are the lastest sources? 
>The version that came on the last root disk allows someone in group other 
>to erase a file owned by root in group wheel. Even with the file I'm 
>trying to erase set to permissions 600, it will ask if you want to overide 
>these permissions and then merrily delete it. I have checked and rm is not 
>setuid. What is going on here?

The permission to delete a file is not dependent on the permissions of
the file itself but rather the permissions of the directory in which the
file resides.  If you can modify the directory (i.e. you have write
access) you can delete the name from the directory (directories are
basically only lists of names + inode numbers).

--
Lars.Wirzenius@helsinki.fi
From: dirkst@messua.informatik.rwth-aachen.de (Dirk Steinberg)
Newsgroups: comp.os.linux
Subject: Re: find 3.7 and fileutils 3.3 uploaded
Date: 28 Jul 92 15:04:26 GMT
Organization: Rechnerbetrieb Informatik  /  RWTH Aachen

faith@cs.unc.edu (Rik Faith) writes:

>Here is a synopsis of my new uploads, as of Mon Jul 27 10:50:50 1992

>Bug reports and comments to: faith@cs.unc.edu

>*bin.tar.Z: linked static with gcc 2.2.2 (release version) under 0.96c.pl2
                    ^^^^^^
I think it is a bad practice to upload static binaries. They are totally
useless for anyone who does not want to waste massive amounts of disk space.
I have both Linux 0.96cpl2 and 386BSD 0.1 installed on my 486 and I prefer
to use LINUX because it is more efficient and faster and it has shared
libraries (and because gdb-4.6 and X386-1.2E work). The shared libraries
are the single most biggest plus in favor of Linux, especially when it comes
to X.

We should always use the latest official gcc release shared images for
uploading binaries. Starting from next release, these will be based on
jump-tables anyway. If you really want, you can include /lib/libc.2.2.2
in your tar file; for larger programs, this will get you to about the same
total size.

Alternatively, you could upload *.a's, but that requires the user to have
gcc installed.

>-- 
>Rik Faith: faith@cs.unc.edu

	Dirk
-- 
---
Dirk W. Steinberg
Aachen University of Technology
email: dirkst@pool.informatik.rwth-aachen.de
Newsgroups: comp.os.linux
From: thoth@uiuc.edu (Ben Cox)
Subject: Re: shutdown problem
Originator: btc30679@uxa.cso.uiuc.edu
Reply-To: thoth@uiuc.edu (Ben Cox)
Organization: University of Illinois at Urbana
Date: Tue, 28 Jul 1992 00:35:29 GMT

pete@q106fm.UUCP (pete cervasio) writes:

>I've found that umount will not unmount a busy drive... '/' is ALWAYS
>mounted because you can't get any higher in the directory tree.  The big
>red switch is what umounts that one.  If you 'cd /' before shutdown, it
>should get rid of the other message, though.

You may also need to kill cron, if you're running it.  It cd's down
into its own directory, which on my system is under /usr.

Still, though, for me, sometimes shutdown works and sometimes it just
sits there forever (well, at least, until I get impatient and hit ^C).

--
Ben Cox
thoth@uiuc.edu
Newsgroups: comp.os.linux
From: janl@ifi.uio.no (Jan Nicolai Langfeldt)
Subject: Re: talk/ytalk
Organization: Folkeaksjonen for (tungt) eple cider p} Inf. stua
Date: Sun, 26 Jul 1992 21:48:07 GMT
Originator: janl@maud.ifi.uio.no


In article <64361@hydra.gatech.EDU>, gt0449a@prism.gatech.EDU (Rob Coleman) writes:
> Has anyone managed to find/compile a "talk" program to Linux?  I just
...
> that provides the same function (talking) that is easier to port?
> Thanks..

write(1)?

(y)talk needs networking (tcp/ip). Or they need to be rewritten using
fifos and no network calls.

Nicolai

Newsgroups: comp.os.linux
From: sheldon@iastate.edu (Steve Sheldon)
Subject: Easy as pie...
Organization: Iowa State University, Ames IA
Date: Tue, 21 Jul 1992 13:58:29 GMT

 I just found out about Linux about a month ago.  Started reading this group,
and was slightly overwhelmed by all the "Help me install this..." messages.
I tried to grasp all I could form the FAQ's and other help documents.
 Even though it still didn't quite make sense, I ftp'ed the MCC Interim release
of .96c last week and installed it on a 20 Meg partition of my 386sx-16.

 Just a word of thanks... As this is great!

 Everything went pretty much without a hitch.  I used shoelace and now have
available either my 20 Meg Linux partition, or 60 Meg DOS partition, and
no problems thus far.

 Sure I had a few problems.  Either I didn't read things quite right, or 
they're missing from the documentation.  But most of them were easily solved,
like shoelace not finding the Kernel until I copied it into the root directory,
etc.

 Well I'm eager to start playing with it...

Steve Sheldon
sheldon@iastate.edu

Newsgroups: comp.os.linux
From: cummings@hammer.Prime.COM (Kevin Cummings)
Subject: Re: Help Gcc, ftp tcp/ip, x
Organization: Prime Computer R&D
Date: Fri, 31 Jul 1992 15:48:24 GMT

Oh, I almost forgot, if you have to, try TARing up the compressed
tar files before you write them out to the floppy disks.  In that way,
there will be an EOF mark on the floppy disk, and you won't get any
error messages while reading the compressed images off of the raw floppy
disk.

If you write the compressed .tar.Z files directly to floppy, you may get
error messages when reading them in.  Read them in via:
	uncompress /dev/fdx > xxx.tar
Check the resulting .tar files to see if they look OK before punting them
as unsuccessful.

If you put the compressed tar files into a new tar file, writing this
to the floppy disk via rawrite should allow you to read it under LINUX
without getting any error messages with tar via:
	tar xf /dev/fdx
	uncompress xxx.tar.Z
	tar xf xxx.tar

Sure it's an extra step, but well worth it.

=================================================================
Kevin J. Cummings                       PrimeService
20 Briarwood Road                       A Computervision Company
Framingham, Mass.                       500 Old Connecticut Path
					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
=================================================================
Newsgroups: comp.os.linux
From: herr@hp14.iti.informatik.th-darmstadt.de (Gabor Herr)
Subject: Re: Rebooting and bad cache
Date: Fri, 31 Jul 1992 10:47:50 GMT
Organization: TU Darmstadt

In article <1992Jul29.031659.2484@news.iastate.edu>, mhbrekke@iastate.edu (Monty H. Brekke) writes:
> Has anyone else received a bad cache memory error after rebooting Linux?
> Every time I reboot, my BIOS tells me that my cache memory is bad, and that
> I should disable it. This message comes up just before the Shoelace menu
> appears and only after I have rebotted from Linux. Rebooting from DOS does
> not seem to produce this error. Also, if I shutdown and then C-A-D instead of
> typing reboot, the error does not appear. Disabling the external cache seems
> to fix the problem.
> 
> My system configuration is as follows:
> 
> 486-33
> AMI BIOS/OPTi chipset
> 256K external cache
> 16MB memory
> 1.44MB 3.5 inch floppy drive on /dev/fd0
> 1.2MB 5 inch floppy drive on /dev/fd1
> Quantum 244MB hard drive partitioned as follows:
> 	~100MB DOS partition on /dev/hda1
> 	~64MB Linux root partition on /dev/hda2
> 	~50MB Linux partition on /dev/hda3, mounted as /home
> 	~20MB Linux swap partition on /dev/hda4
> Colorado Memory Systems 250MB tape drive
> 


I had similar problems with a 386/40Mhz, ETEQ Chipset board with 64K cache,
8MB memory. Linux produced segmentation fault or general protection errors from
time to time under heavy load. With disabled caching everything worked fine.

I thougth it was a timing problem, so I went back to the vendor and exchanged my
board for a 386/33Mhz, C&T chipset, 64K cache board. But that wasn't and I got
the same errors. Without caching everything OK.

A friend of mine has Linux running on similar board (other manufacturer but
same proc 386/33 with identical chipset (C&T), 64K cache, 8MB memory) without
any problems. To ensure that not the IO cards or the memory caused the errors,
we exchanged the two boards in our machines. And what happend? 

His board worked with my components: 8MB SIMMs, ColorImage VGA, HD (ST3144A) 
with IDE controller. My board didn't. :-(

Any ideas? Did anybody had this kind of problems?

Thanks in advance.

Gabor


############################################################################
Gabor Herr			Email: herr@iti.informatik.th-darmstadt.de
Computer Science Department
Technical University of Darmstadt, Germany
From: pete@q106fm.UUCP (pete cervasio)
Newsgroups: comp.os.linux
Subject: Re: shutdown problem
Date: Mon, 27 Jul 92 01:52:51 CDT
Organization: WKBQ-FM Engineering Department

Jim.Corbett@f35.n152.z1.fidonet.org (Jim Corbett) writes:

>  >>and it gave me messages "cannot umount /dev//dev/hda3" and "cannot
>  >>umount /dev//dev/hda2" or something to that effect. These are indeed

>  > Looks like you're _not_ using mount/umount from the 0.96 root
>  > disk. With those tools and a proper /etc/fstab it will work.

> Well I have been waiting for someone to ask that question or for it to
> show up in a FAQ, but it does that with RAWWRITEN copies of unaltered
> 0.96c boot and root on floppys on my system.

I've found that umount will not unmount a busy drive... '/' is ALWAYS
mounted because you can't get any higher in the directory tree.  The big
red switch is what umounts that one.  If you 'cd /' before shutdown, it
should get rid of the other message, though.

Pete C.


+----------------------------------------------------------------------+
| Pete Cervasio                | pete%q106fm.uucp@wupost.wustl.edu     |
| I fish, therefore I am.      | pete.cervasio@f1.n2250.z1.fidonet.org |
+----------------------------------------------------------------------+
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Re: Good news, bad news
Date: 23 Jul 92 16:10:59 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Jul22.205311.7687@serval.net.wsu.edu>, hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:

| Try gcc -traditional when 2.2.2d is release to public or contact me. You can
| also try to convert it to ANSI C if you really want to use gcc 2.2.2. That
| was what I did before I fed up with it and made some changes in 2.2.2d.

  I do appreciate the thought (and thanks to those who suggested other
header files by mail), but this program really is pretty portable, and
compiles on the AT&T V.4 compiler, gcc 2.1 -ansi -pedantic, and SCO -W3
without problems.

| For tty, Linux is POSIX. For IPC, you can only use Unix domain socket for now.
| If you don't use those SYSV IPC, it should be very easy to port it to Linux. Do
| you think that code is much more complicated than X11R5?

  Thanks, this clarifies some of the problems, I will shelve this port
until linux has a bit more IPC (and might even look at generating a few
patches for some of the stuff I need). As for your question, I want to
use shared memory, pipes, SysV semiphores and message queues. I think
it's fair to say that the code is reasonably demanding in the IPC area,
perhaps more than X11R5. That doesn't relate 1:1 with complexity, of
course.

  By adding enough ifdefs I think I can use the file and termio stuff
from various parts already written, although the big blocks of BSD vs
SysV vs streams will have to be broken up.

  Everyone has been most helpful.
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
	It never ceases to amaze me that otherwise rational people, able to
	understand calculus, compound interest, and the income tax form, can
	continue to believe that poker is a game of chance.
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: Re: Newbie Linuxer & misc. Qs (LONG!)
Date: 27 Jul 92 06:20:31 GMT
Reply-To: LeBlanc@mcc.ac.uk (A. V. Le Blanc)
Organization: Computing Centre, University of Manchester

In article <1992Jul26.220519.18078@sura.net> vargish@sura.net (Nick Vargish) writes:
>2. Can only log-in as "root". This is a big problem. I have tried
....
>   username (vargish) and Linux spits out the text in the file
>   "/etc/nologin".

The file /etc/rc should contain the command 'rm -f /etc/nologin'.
This file, which is created by the reboot command, prevents non-root
users from logging in unless it is deleted.

>4. Mtools sometimes can't initialize my floppies, and sometimes can't
>   even see them (depending on what random numbers I'm using in
>   /etc/mtools).

You should have

     A /dev/fd0 12 0 0 0
     B /dev/fd1 12 0 0 0

for the floppy entries in /etc/mtools.

     -- Owen
     LeBlanc@mcc.ac.uk
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.linux
Subject: Re: sigaction sys-call
Date: 25 Jul 92 11:49:12 GMT
Organization: University of Helsinki

In article <1992Jul25.110852.24366@fwi.uva.nl> vesseur@fwi.uva.nl (Joep JJ Vesseur) writes:
>
>Looking around in the include files, i came across a line that said
> "Ok, I haven't implemented sigactions, but trying to keep headers POSIX"
> (/usr/include/signal.h)
>but in the kernel source file signal.c there is code to implement 
>sigaction. Is this some sort of dummy code, or is signal.h out of date and
>is sigaction fully functional?

Sorry: I don't write too many comments, and when I do they seem to
become obsolete.  sigaction() is completely implemented, and has been
since 0.12 or something like that.. 

		Linus
From: thoth@uiuc.edu (Ben Cox)
Newsgroups: comp.os.linux
Subject: Re: xhetris
Date: 25 Jul 92 16:21:57 GMT
Reply-To: thoth@uiuc.edu (Ben Cox)
Organization: University of Illinois at Urbana
Originator: btc30679@uxa.cso.uiuc.edu

> and does anyone have xset? 

xset compiles with no changes.  Look on export.lcs.mit.edu under
/pub/R5untarres/mit/clients/xset (this may not be exactly the correct
path, but it's something close to that).

Grab the files, type "xmkmf" and "make install".

Presto!  This also works for xmag, xdpyinfo and many many others.

--
Ben Cox
thoth@uiuc.edu
Newsgroups: comp.os.linux