Files
2024-02-19 00:25:02 -05:00

560 lines
21 KiB
Plaintext

From: Digestifier <Linux-Activists-Request@news-digests.mit.edu>
To: Linux-Activists@news-digests.mit.edu
Reply-To: Linux-Activists@news-digests.mit.edu
Date: Wed, 5 Feb 92 00:00:18 EST
Subject: Linux-Activists Digest #38
Linux-Activists Digest #38, Volume #1 Wed, 5 Feb 92 00:00:18 EST
Contents:
perl binaries on TSX-11 (Pietro Caselli)
mtools and logical DOS partitions (Christian Vandendorpe)
weird characters (Christian Vandendorpe)
Perl 4.019 on Linux 0.12, problems with $&... (Peter Orbaek)
Re: tubes (Mike Haertel)
Linux continues to reboot (John Lauro)
How About LINUX with MSDOS FAT Filesystem Support? (David Feustel)
Re: How About LINUX with file system daemons? (Lance Norskog)
Re: RLL drives? (Bryan Stansell)
Help: need someone to test a new gcc 1.40 (Hongjiu Lu -- Graduate Student)
Re: MicroEmacs (Humberto Ortiz-Zuazaga)
Re: another dead filesystem and that fsck can't fix (Humberto Ortiz-Zuazaga)
df (Chuck Boyer)
Re: Linux-Activists Digest #36 (Michael Campbell)
Re: Anomalies with vixie-cron (Thomas David Rivers)
Re: Deadline for 0.13 (Charles Hedrick)
Re: compress/freeze (was: Re: Comments to Directory Standard (banjo.concert.net)) (Ken Raeburn)
----------------------------------------------------------------------------
From: pietro@deis35.cineca.it (Pietro Caselli)
Subject: perl binaries on TSX-11
Date: 4 Feb 92 15:57:21 GMT
I have posted Andrew Haylett's porting on perl on TSX-11.
It works great !!!
Ciao.
--
Pietro Caselli |
Internet: pietro@deis35.cineca.it | IF YOU MEET THE BUDDHA
zaphod@petruz.sublink.org | ON THE ROAD,KILL HIM.
------------------------------
From: vandendo@qucis.queensu.ca (Christian Vandendorpe)
Subject: mtools and logical DOS partitions
Date: 4 Feb 92 17:25:39 GMT
I have a primary Linux partition, a primary OS/2 partition, and an extended
logical DOS partition. I am able to access my OS/2 partition using mtools
(although I get garbage because it was formatted with HPFS) but I cant
seem to access my logical dos partition (drive D:). Is this normal?
is mtools not supposed to be able to access these?
Christian Vandendorpe
------------------------------
From: vandendo@qucis.queensu.ca (Christian Vandendorpe)
Subject: weird characters
Date: 4 Feb 92 17:28:41 GMT
Sometimes when by mistake I cat a binary file to the screen, it will leave
Linux in a weird mode, all the characters typed or displayed from then on
are weird (from ascii 128 to 256). The only way to get out of this is to
reboot. Any ideas how I can reset my terminal to the regular characters?
Christian Vandendorpe
------------------------------
From: poe@daimi.aau.dk (Peter Orbaek)
Crossposted-To: comp.lang.perl
Subject: Perl 4.019 on Linux 0.12, problems with $&...
Date: 4 Feb 92 16:00:24 GMT
I'm attempting to get perl up and running on my 386/33 running linux 0.12,
using gcc 1.40 (the compiler that comes with linux).
After getting through configure, and doing various small hacks in the
makefile, I have got it to compile cleanly, except for minor warnings about
return-types of getgrgid() and such.
But problems arise when I run the test-suite. First I must say that floating
point support on linux is fairly bad, so I get several failed tests because
sprintf prints - for instance - 12 as 11.99999999997.
This can be remedied by compiling with these options, in effect making an
"integer-perl":
-Ddouble=int -Datof=atoi -DINT_PERL
and then doing some minor hacks in str.c and dolist.c to get proper conversions
from ints to strings, and removing packing of floats and doubles.
With these hacks I get fewer failed tests than with the original floatin-point
perl.
BUT , in both cases the produced perl fails on tests: op/pat 28,29,30
I seems that $& doesn't get set correctly. Why can this happen??
This problem also affects several other tests.
At least in op/pat test #28 $& is set to the empty string or null...
Another failure that seems to occur only with "integer-perl" is that the
test: comp/<something...> fails, due to length('\\\\') not returning 2
or, more accurately:
(length('\\\\') == 2) ==> false
but
$x = length('\\\\'); print $x; ==> prints 2
and
print length('\\\\'); ==> prints 2
I have tried these things both with and without the perl-malloc if that
matters.
Suggestions anyone?
Thanks in advance.
- Peter (poe@daimi.aau.dk)
--
Peter Orbaek ----------------- poe@daimi.aau.dk | ///
Hasle Ringvej 122, DK-8200 Aarhus N, DENMARK | ///
| \\\///
"Strong typing is for people with weak memories" | \XX/
------------------------------
From: haertel@euclid.uoregon.edu (Mike Haertel)
Subject: Re: tubes
Date: 4 Feb 92 18:46:50 GMT
In article <1992Feb4.123601.4700@athena.mit.edu> entropy@ee.WPI.EDU (Lawrence C. Foard) writes:
>The standard linux pipes always return with the read buffer full except
>when the pipe has been closed on the writting end. This works well for
Reads on standard Unix pipes always return right away if one or more
characters are available, without necessarily satisfying the whole read.
I've tried this at least on System V.2, 4.3 BSD, and research v10.
If Linux pipes don't work this way, they're broken.
>one way pipes but doesn't work for server/client communications where
>you have requests and responces going back and forth. Here are a few things
>I'm wondering about.
>Read has several possibilities:
> 1) Return only data in the buffer unless there is none then block (unless
> O_NONDELAY is on).
> 2) Try to read as much as one write call produced even if it doesn't fit
> in the buffer. This is rather messy since it has to keep track of where
> write calls ended.
> 3)Have it default to #1 and have an IOCTL to switch it back to totally
> fullfilling each read request when possible.
I think the most useful way to have tubes work would be to preserve
write boundaries on reads. I.e., if the writer writes 10 bytes, the
reader would get only ten bytes. Among other things, this makes it
possible to write "eof"s by writing 0 bytes. Useful when pretending
to be a terminal.
>I'm leaning toward 3 at this point, since this will work with the line
>based I/O that most demons expect. Demons expecting fixed sized data can
>switch it to the other mode. Does any one know of programs that would
>have problems with this?
Very few programs in Unix have trouble with this (default, and unchangable)
behavior in Unix pipes. The reason is the stdio library takes care of
dealing with partially fulfilled reads in the proper way. Such programs
can just use fread() and they'll work properly.
>Write also has several possibilities:
> 1) Write all data requested unless the pipe breaks, if O_NONDELAY then
> it will just write what will fit in the buffer.
> 2) Always write only what will fit in the buffer unless it is 0 then block.
>I'm leaning toward 1 at this point, can any one see any reason why #2 would be
>better?
I think it would be even better to try to preserve "write boundaries"
no matter how large the writes are. Difficult, though.
>TU_FS- file system requests passed on to server
Does this mean file system requests are turned into formatted data messages,
and then passed to the server as a sort of remote procedure call? Sounds
like a really good idea.
------------------------------
From: jal@acc.flint.umich.edu (John Lauro)
Subject: Linux continues to reboot
Date: 4 Feb 92 18:29:26 GMT
Linux continues to reboot itself after selcecting VGA mode. I have
received a message from one person experiencing the exact same problem
as me, plus another with a different problem. (The later is appended
to this article...)
It would be great if someone could make a diagnostics boot disk to help
determine where the problem is. I'll modify the existing code myself, if
someone tells me exactly where the source code is, and how to build the
file for RAWRITE to use...
======= Forwarded Message Follows =======
Date: Fri, 31 Jan 92 23:37:17 CST
From: glosson@mdtf12.fnal.gov (Rich Glosson)
To: jal@acc.flint.umich.edu (John Lauro)
Subject: Re: Problems getting started
I too am having problems getting started. I would like to post what my
problem is, but for some reason I can't post to alt.os.linux but I can to
all other groups.
If you would, would you please post the following message?
Newsgroups: alt.os.linux
Subject: Help, I've fallen and I can't get linux up!
Distribution: world
--text follows this line--
My system:
Gateway 2000 386/25 4 MB RAM
Western Digital Caviar 280 IDE hard drive
Hardcard PLUS 20 MB hard drive ( just slides into
a slot and is recognized as drive D: by DOS.
Gateway's NI VGA monitor w/1 MB 1024x768
SpeedSTAR VGA Vers 3.21 Diamond Computer Systems Inc.
Phoenix 80386 ROM BIOS PLUS version 1.10 M11
How I got the images:
ftp'd in binary r/bootimage-0.12.Z from tsx-11.mit.edu
uncompressed
mcopy'd to seperate 3.5 disks from my SPARCstation 1
rawrite'd to seperate 5.25 disks from my Gateway
What I saw when I tried to bring up linux:
Loading............................. EGAc
Press < return > to see SVGA-modes available ...etc...
8 virtual consoles
4 ptys
harddrive I/O error
dev 0300, block 0
unable to read partion table of drive 0
kernel panic
I looked at the last bytes of sector 0, track 0 and see "0000 55aa"
which is what I have been told to expect to see. I will try to take
out my Hardcard PLUS and see if thats causing the proplem ( which
did cause a problem when it co-existed with my ide drive and had
SCO xenix partition the active partion ).
I just took out my hardcard and I was able to bring linux up fine.
I can't figure out why the hardcard interfers when I try to boot up
linux or even Xenix. There is a jumper on the hardcard to tell it
whether its being used in a PC or a XT. If I dont use the jumper or
set it up for pc and then reboot the system I get a message saying that
there is a non-system disk. But, if I set the jumper up to say that it
is an XT the system reboots fine as DOS and recognizes the hardcard as
D:. My users guide for my IDE drive states the folling:
If you are installing two IDE drives, you must designate one
as the primary, or master drive, and the other as the secondary
or slave drive.
Well the hardcard is not an IDE drive so I didn't set up the jumper
to designate the IDE as either master or slave drive.
Any help will be greatly appreciated!!!!
Rich Glosson
glosson@mdtf12.fnal.gov
===========================================================================
John Lauro email: lauro_j@msb.flint.umich.edu
University of Michigan - Flint john_lauro@um.cc.umich.edu
Academic Computing Center
303 E. Kearsley St. phone: (313) 762-3123
Flint, MI 48502 fax: (313) 762-3687
------------------------------
From: feustel@netcom.COM (David Feustel)
Subject: How About LINUX with MSDOS FAT Filesystem Support?
Date: 4 Feb 92 18:43:07 GMT
I think that LINUX would become even more popular if it could work
with and boot from MSDOS filesystems. I've had Minix for quite a while
and its incompatibility with dos partitions has definitely made it
less useful to me. I would really like to be able to switch back and
forth easily between Linux, dos and OS/2.i by booting from an
appropriate diskette.
--
David Feustel N9MYI, 1930 Curdes Ave, Fort Wayne, IN 46805. (219)482-9631
"Economic Serfdom for All!"
= American Business Strategy & Implicit Republican Party Platform Plank =
=== NBC News: GE's Advertising And Public Relations Agency ===
------------------------------
From: thinman@netcom.COM (Lance Norskog)
Subject: Re: How About LINUX with file system daemons?
Date: 4 Feb 92 19:08:00 GMT
feustel@netcom.COM (David Feustel) writes:
>I think that LINUX would become even more popular if it could work
>with and boot from MSDOS filesystems.
Linux would become extremely popular if it was easy to write new
file systems: MS-DOS, NFS, AFS, CDROM, WORM, database, etc. This is
a core piece of technology missing from all the available Unixes.
It's either impossible or proprietary and very very hard.
Lance Norskog
thinman@netcom.com
------------------------------
From: cccbryan@yogi.ucdavis.edu (Bryan Stansell)
Subject: Re: RLL drives?
Date: 4 Feb 92 20:30:56 GMT
Adam> Will Linux work on a system with RLL drives? Enquiring minds and all
that.
It won't necessarily work though. It doesn't work with my contoller. Here's
what I got from the Linus:
=========================
.
.
.
This is the biggest problem about compatability right now: linux simply
doesn't work correctly with some drives (mostly slower old drives). I
haven't got any docs on the controller, so most of the hd-driver has
been "trial and error". I'll probably get some docs next week, and 0.13
/might/ correct the problem, but I won't promise anything.
.
.
.
Linus
=========================
--
+--------------------+
| Unix Consultant |
| Computing Services |
| UC Davis |
+--------------------+
+-----------------------------------------+
| Internet: cccbryan@underdog.ucdavis.edu |
| BITNET: bgstansell@ucdavis.bitnet |
| UUCP: ucdavis!stansell |
+-----------------------------------------+
------------------------------
From: hlu@luke.eecs.wsu.edu (Hongjiu Lu -- Graduate Student)
Subject: Help: need someone to test a new gcc 1.40
Date: Tue, 4 Feb 92 20:04:28 GMT
Hi,
I just finished a new gcc compiler and a new set of libraries which are
supposed to solve all the floating point number problems as well as the
problems caused by the brain-damaged estdio. With a 387, you can also
get a full libm.a.
It is working now with a 387. It is supposed to work without a 387
under 0.12 kernel. I need someone to test them on a machine without a
387. I prefer someone who has ftp access and is close to me. If anyone
is interested, please drop me a note.
H.J.
------------------------------
From: zuazaga@ucunix.san.uc.edu (Humberto Ortiz-Zuazaga)
Subject: Re: MicroEmacs
Date: Tue, 4 Feb 92 19:49:13 GMT
In article <gs_sm1k@rpi.edu> lingy@marcus.its.rpi.edu (Yong-Ernn Daniel Ling) writes:
>I would like to know where I can find MicroEmacs and do I need any patched
>to compile it as I am new to both Linux and Unix.
You've probably already got it, its in util.tar.Z as em. This is a
version 3.10+e8 or something like that. Version 3.11 is available from
midas.mgmt.purdue.edu in dist/uemacs311, after 6:00pm EST. It'll compile
with only a few changes. I'll try to put it up on tsx11.
--
Humberto Ortiz-Zuazaga INTERNET: zuazaga@ucunix.san.uc.edu
Dept. of Physiology & Biophysics BITNET: picone@ucbeh
University of Cincinnati CIS: 72301,2303
------------------------------
From: zuazaga@ucunix.san.uc.edu (Humberto Ortiz-Zuazaga)
Subject: Re: another dead filesystem and that fsck can't fix
Date: Tue, 4 Feb 92 19:56:05 GMT
In article <Feb.2.15.28.47.1992.19090@dumas.rutgers.edu> hedrick@dumas.rutgers.edu (Charles Hedrick) writes:
>By the way, it's now pretty clear that there's a timing problem (a
>race or something) in the file system or hd code. Basically whenever
>I am doing file system I/O in two jobs at the same time (e.g. on two
>screens), I lose.
I was compiling in two windows the other day, and decided to open a file in a
third. The machine, which had been churning along nicely, started to
slow down, and then stopped. I killed the third shell, and waited, and
slowly it started picking up steam again. I have 4mb memory, and no swap
space, so I thought I was just out of memory, but maybe not?
--
Humberto Ortiz-Zuazaga INTERNET: zuazaga@ucunix.san.uc.edu
Dept. of Physiology & Biophysics BITNET: picone@ucbeh
University of Cincinnati CIS: 72301,2303
------------------------------
From: boyer@sumax.seattleu.edu (Chuck Boyer)
Subject: df
Date: 4 Feb 92 23:50:55 GMT
where does one find 'df' utility, or how does one find out the partition
bytes left in Linux?
thanks
chuck
------------------------------
From: tarpit!obmarket!michaelc@uunet.UU.NET (Michael Campbell)
Subject: Re: Linux-Activists Digest #36
Reply-To: tarpit!obmarket!michaelc@uunet.UU.NET (Michael Campbell)
Date: Wed, 5 Feb 1992 02:17:30 GMT
Does Linux support SCSI yet? Specifically, Adaptek 1542b's? If not,
does this host adapter stand a chance of being supported in the
future, or are other adapters being looked at?
------------------------------
From: rivers@ponds.uucp (Thomas David Rivers)
Subject: Re: Anomalies with vixie-cron
Date: 4 Feb 92 23:46:36 GMT
Yes, I too am beginning to notice trouble.
First, I don't have ps running yet, so didn't notice what was going on.
But, after a while (usually running overnight) I can't get any more
processes going (fork failed, try again). Something is not dying
the way it should.
I haven't noticed the problem with not actually running any commands. It
seems to execute the commands fine for me; just leaves a lot of processes
lying around...
- Dave Rivers -
------------------------------
From: hedrick@dumas.rutgers.edu (Charles Hedrick)
Subject: Re: Deadline for 0.13
Date: 5 Feb 92 04:07:38 GMT
I agree with keeping the kernel small. I've ported several things,
and had little trouble with missing kernel facilities. I'd just as
soon not have things like System V semaphores, shared memory, etc.
Non-blocking tty I/O is essential to several kinds of applications,
and there will probably be a few other features like that, but I agree
that it's a mistake to put much more in the kernel.
The challenge is going to be to provide some basis for networking
without doubling the size of the kernel. Is there any chance you can
come up with a way to write TCP outside the kernel without losing
performance badly? There's a version of KA9Q that is designed to run
as a set of programs outside the kernel. There's a single server that
acts as a protocol engine. Applications talk to it rather than making
system calls. It uses System V shared memory and semaphores to talk
between the processes. If you could come up with a way to keep the
performance penalty of this down, it might be worth looking at.
I'd like to see priority in 0.13 (and maybe 0.14) put on completing
libc. In the ports I've done, the main area I've found lacking is in
that area: floating point support in the library (gcc compiles calls
to helper routines that don't exist), and various other random things
like alloca, bcopy/bcmp/bzero, regex, etc. I suspect we've identified
most of the missing stuff by now, and people have come up with them as
part of the source to various programs they've ported.
------------------------------
From: raeburn@athena.mit.edu (Ken Raeburn)
Subject: Re: compress/freeze (was: Re: Comments to Directory Standard (banjo.concert.net))
Date: Wed, 5 Feb 1992 04:57:36 GMT
In article <RAEBURN.92Jan28184937@cambridge.cygnus.com> I wrote:
A suggestion: There's a utility called "freeze" (which is probably
available from ftp.uu.net and other sites) which is slower but more
efficient than the standard UNIX "compress". I was able to build it
fairly easily under linux.
For people who have to do file transfer by slow modem or floppy disk,
using freeze rather than compress is likely to be a big help. Even
for people with relatively fast connections (I'm using 9600 now), it
helps for large files.
I finally looked up just where the sources are supposed to be.
According to "archie", sources are on ftp.uu.net, wuarchive.wustl.edu,
and several other sites in usenet/comp.sources.misc/volume26/freeze.
Also on nic.funet.fi in pub/archive/comp.sources.misc/volume26/freeze.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: Linux-Activists-Request@NEWS-DIGESTS.MIT.EDU
You can send mail to the entire list (and alt.os.linux) via:
Internet: Linux-Activsts@NEWS-DIGESTS.MIT.EDU
Linux may be obtained via one of these FTP sites:
nic.funet.fi pub/OS/Linux
tsx-11.mit.edu pub/linux
tupac-amaru.informatik.rwth-aachen.de pub/msdos/replace
The current version of Linux is 0.12, released on Jan 14, 1992
End of Linux-Activsts Digest
******************************