Subject: Linux-Misc Digest #568
From: Digestifier <Linux-Misc-Request@senator-bedfellow.MIT.EDU>
To: Linux-Misc@senator-bedfellow.MIT.EDU
Reply-To: Linux-Misc@senator-bedfellow.MIT.EDU
Date:     Wed, 19 Jan 94 06:13:58 EST

Linux-Misc Digest #568, Volume #1                Wed, 19 Jan 94 06:13:58 EST

Contents:
  HELP: ST41650 1.4GB Hard Drive (Chris Royle)
  Re: dos2unix, unix2dos text conversion programs?? (Uwe Bonnes)
  Re: Linux vs. microkernel based Unix: questions? (Dan Hildebrand)
  Re: Linux vs. microkernel based Unix: questions? (Dan Hildebrand)
  Re: Linux vs. microkernel based Unix: questions? (Paul JY Lahaie)
  Doing tricks with term 1.0.8.. :) help! (Dan Miner)
  Re: Windows emulation was Re: Microsoft Invented Inferior Personal C (Jim Frost)
  Re: Brain bugs wasting bandwidth (Larry McQueary)
  Re: HIGH load on CPU while using rz!  Why? (Thomas G. McWilliams)
  Archives of Torvalds/Tanenbaum discussion? (Gary Shea)
  Help Installing Linux!!! (Joseph Greene)
  Re: Japanese Extension to Linux, ideal for mule (multilingual emacs) users (Nelson Chin)
  Re: Where is libc src? (Mitchum DSouza)
  Re: Q: libc has _NEEDS_SHRLIB_libc_4 multiply defined? (Mitchum DSouza)
  [comp.os.linux.announce] Guidelines for posting (Matt Welsh)

----------------------------------------------------------------------------

From: Chris Royle <car1002@cus.cam.ac.uk>
Subject: HELP: ST41650 1.4GB Hard Drive
Date: Tue, 18 Jan 1994 22:26:18 GMT

In the Hardware incompatibility list, the ST41650 Drive is listed as only
having 1000MB accessible. 

Please could anyone confirm or deny this, and if it's a confirmation, 
offer and explanation as to why since the drive functions fine at its full
capacity under DOS.

Chris.

--
Chris Royle               "In the sex war, insensitivity is the weapon of the
Managing Director          male, vindictiveness of the female". C. Connoly (?)
Objectronix Limited        c@royle.org              (Internet)
Leeds, UK 0850 668151      car1002@uk.ac.cam.hermes (JANET)

------------------------------

From: bon@lte.e-technik.uni-erlangen.de (Uwe Bonnes)
Crossposted-To: comp.os.linux.help
Subject: Re: dos2unix, unix2dos text conversion programs??
Date: Sun, 16 Jan 1994 19:38:51 GMT


In article <2hape0$q5b@geraldo.cc.utexas.edu>, dcoleman@mbs.telesys.utexas.edu (Daniel M. Coleman) writes:
|> Does anyone know of anything equivalent to the SunOS 4.1.3 dos2unix and
|> unix2dos commands, which strip/add ^M's in text files, that is available for
|> Linux?

Look at gnu-recode
---
Uwe Bonnes  bon@lte.e-technik.uni-erlangen.de

------------------------------

From: danh@quantum.qnx.com (Dan Hildebrand)
Subject: Re: Linux vs. microkernel based Unix: questions?
Date: Tue, 18 Jan 94 17:29:09 GMT

In article <1994Jan15.014009.5072@kf8nh.wariat.org>,
Brandon S. Allbery <bsa@kf8nh.wariat.org> wrote:
>| Has that been conclusively proven?  I.e. is the debate between faster
>| context switches vs. more context switches been settled one way or
>| another? If so, do you have any references I could look up?
>
>Well, the hairy part is "equivalent"; the word is fuzzy enough that it's
>almost impossible to prove anything about it...  My point was that if you
>apply the same optimizations to a monolithic kernel that are generally applied
>to microkernels (context switch time in particular) the monolithic kernel will
>benefit as well.

One of the main reasons for doing a microkernel (other than architectural 
flexibility and robustness) is to make the kernel as lean, simple and fast 
as possible.  Clearly, the complexity of a monolithic kernel will have an 
impact on performance, as the various portions of the monolithic kernel 
contest for semaphores to gain access to protected regions of the kernel 
data space.  The greater simplicity of a microkernel allows it to be more 
easily optimized, since it has less complexity to deal with.  Having made 
that trade-off, the challenge is to architect the rest of the system to 
remain fast, and not lose that speed advantage to other inefficiencies.

>Perhaps not as much in terms of the *overhead* of specific
>operations (because the monolithic kernel does fewer context switches), but in
>the total time taken.  Nor are context switches the only issue; the time
>needed to pass data between two processes is greater when they have to use a
>"proper" linkage instead of just sharing a buffer a' la monolithic kernels.

Sharing a buffer requires semaphores and other handshaking.  In some cases, 
that handshake can be more expensive than passing the data.

>(On the flip side, it's easier to debug and test the microkernel-based system.

Absolutely.  This makes it easier to be experimental in your approach to 
trying new algorithms.  With a monolithic kernel, building and discarding 
prototypes for new ideas isn't as easy.

>There are tradeoffs in both directions:  speed comes at a price.)

The speed/performance tradeoff does not necessarily apply to microkernels. 
:-)

>This does not address the possibility that a microkernel may be easier to
>adapt to real-time constraints.  I would suspect that it's easier to make
>multiple restartable, reentrant processes than it is to make a monolithic
>kernel fully reentrant, for example.

Again, greater simplicity in the kernel results in greater adaptability and 
ease of optimization.  The trick is to not lose the gains made in the 
kernel to other aspects of the OS.  You want to gain enough in the kernel 
that the additional context switches cost less than what was gained in the 
kernel.
-- 
Dan Hildebrand                     email: danh@qnx.com
QNX Software Systems, Ltd.         QUICS: danh  (613) 591-0934 (data)
(613) 591-0931 x204 (voice)        mail:  175 Terence Matthews          
(613) 591-3579      (fax)                 Kanata, Ontario, Canada K2M 1W8

------------------------------

From: danh@quantum.qnx.com (Dan Hildebrand)
Subject: Re: Linux vs. microkernel based Unix: questions?
Date: Tue, 18 Jan 94 17:33:09 GMT

In article <1994Jan15.012134.4874@kf8nh.wariat.org>,
Brandon S. Allbery <bsa@kf8nh.wariat.org> wrote:
>
>I will, however, note that HP-RT was the only other real-time OS in the list
>(ignoring non-*ix-like OSes which I am generally unfamiliar with and can't say
>whether they're real-time or not).  Perhaps there are several that are better,
>that you didn't bother to show?  I found your list gappy and incomplete, and
>the choices of systems benched to be occasionally odd; seeing it a fourth time
>doesn't make it look any more complete or the comparisons any more sensible
>from any standpoint other than salesdroid-ism.

The listing was a collection of results posted to the net.  Nothing so
sinister as "salesdroid-ism".  :-)

-- 
Dan Hildebrand                     email: danh@qnx.com
QNX Software Systems, Ltd.         QUICS: danh  (613) 591-0934 (data)
(613) 591-0931 x204 (voice)        mail:  175 Terence Matthews          
(613) 591-3579      (fax)                 Kanata, Ontario, Canada K2M 1W8

------------------------------

From: pjlahaie@zeus.achilles.org (Paul JY Lahaie)
Subject: Re: Linux vs. microkernel based Unix: questions?
Date: 18 Jan 1994 16:59:59 GMT

Rennie Allen (rgallen@muug.mb.ca) wrote:
: do everything on my QNX system that I can do on a Linux box (and a few more),

     So QNX does have VM then.  Since Linux does.

                                                - Paul

------------------------------

Crossposted-To: comp.os.linux.help
From: dminer@nyx10.cs.du.edu (Dan Miner)
Subject: Doing tricks with term 1.0.8.. :) help!
Date: Wed, 19 Jan 94 02:33:19 GMT

I got a strange one here.. *evil grin*

Background info:
        I currently have a Mac classic connected to my Linux
box as a terminal.  Now  I, myself, login at the console (real
machine).  My girlfriend login on her Mac.  Ok?  I have my
account (on Linux) and she has one for herself.  (both
non superuser).

Ok, we both have accounts on Nyx.  We have a 14.4 modem (on Linux) and ONE 
telephone line.  So, term is great for multiplexing our sessions.  
[I have partially overcome the separate logins for us on Nyx.]

Now, to get BOTH accounts on my Linux box to use ONE term server;
I had to make root run it and all ~/.term/sockets (except root's)
point to (symlink) root's actual socket.  For some reason,
it didn't work for non superuser accounts... *sigh*

Problem:
        When the secondary account, the one who didn't first logged in
and started this stuff, tries to 'tupload' (or probably anything) on Nyx;
they get 'Permission denied' on Nyx.  Now, this is what I was getting
on my end BEFORE I made the server a superuser process.  Well, I can't
do that on Nyx.  *grin*

So, any ideas on how to fix this?  Mine would be to make the
term clients suid and suid and add the code to switch to
the other user..  I think that will work?

[Note: security isn't a big issue here..  Uploading and downloading
with both of us "dialed-in" IS!  :) ]


Thanks,
Dan
--
Dan Miner                                       dminer@nyx.cs.du.edu

Future student                                  Linux: try it, you'll like.
"Your program is encoded in pi."                I started with a 64

------------------------------

From: jimf@centerline.com (Jim Frost)
Crossposted-To: alt.folklore.computers,alt.religion.kibology,comp.os.ms-windows.advocacy,alt.fan.mike-dahmus
Subject: Re: Windows emulation was Re: Microsoft Invented Inferior Personal C
Date: 14 Jan 1994 19:27:05 GMT

sikes@nic.cerf.net (Terry Sikes) writes:
>In article <1994Jan6.235745.30548@kf8nh.wariat.org> bsa@kf8nh.wariat.org (Brandon S. Allbery) writes:
>>Open Computing just obliged you with a quote from your best buddy Microsoft:
>>250,000.  So much for "a million copies by the end of the year"...

>Um, MS predicted a million NT sales after the first year of sales.hat is
>to say by 8/1/94.

Was 8/1 the real ship date?  I thought they delayed it until November.

jim

------------------------------

From: mcqueary@nova.umd.edu (Larry McQueary)
Subject: Re: Brain bugs wasting bandwidth
Date: 18 Jan 1994 19:01:48 -0500

In <1994Jan18.093309.3648@kub.nl> paai@kub.nl (J.J. Paijmans) writes:

[ bunch of stuff axed ]

>Listen, Dan. If you read back the postings it all started with you
>venting your displeasure with the Satan-discussion, wasting as much
>time and band-breadth as you accuse me of. I then pointed

[ more stuff axed ]

>and the occasional joke (or flame war) between people that have
>Linux as their common denominator is just that: miscellaneous.

[ more stuff axed ]

>exchanging some quips and I take it that you can recognize
>such messages at a glance and hit the 'n' button, or 'k' button
>or whatever you use, so you can't me accuse me of wasting

[ more stuff axed ]

>So what are you so concerned about? If it really raises your bloodpressure to
>the point that you blow your top, you'd better take a nice holiday.

I concur whole-heartedly.  Dan, please take a deep breath while holding 
down the k (or calling your travel agent). 

-- 
=========================================================
| Larry McQueary  ......  mcqueary@nova.umd.edu         |
=========================================================

------------------------------

From: tgm@netcom.com (Thomas G. McWilliams)
Subject: Re: HIGH load on CPU while using rz!  Why?
Date: Tue, 18 Jan 1994 23:53:04 GMT

Slim (gt4565d@prism.gatech.EDU) wrote:

:       I have a 386sx/25 with 8mb ram.  I have a Supra 14.4 internal modem.
: When I download files, my CPU load goes way up.  (Around .8 to 1.7 or so)
: It hogs the CPU so bad that I get lag trying to do anything else on another
: console.  One thing I can't figure out is that when I boot my system, it sees
: a 16450 UART on COM2 (where my modem is).  I have two COM ports on my IDE 
: card, but I have COM2 diabled on it.  ( The IDE card has 16450s)  I tried 
: recompiling my kernel hoping that it would see the 16550 on my modem, but 
: that didn't work.  Any ideas?  (Please email responses) Thanks in advance!

The internal Supra V32bis modem does not contain a true 16550 UART.
However it does contain large buffer to help prevent buffer overun.
But unfortunately, unlike a true 16550, your modem generates an
interrupt for every received character. A true 16550 UART does not
generate an interrupt for every received character but allows you
to set a threshold. This is not a Linux problem. Your solution would
be to get an external modem and use a serial port which has a true
16550.

Thomas

------------------------------

Subject: Archives of Torvalds/Tanenbaum discussion?
From: shea@hawk.cs.ukans.edu (Gary Shea)
Date: Wed, 19 Jan 1994 00:00:25 GMT

Did anyone archive the discussion between Linus Torvalds
and Andrew Tanenbaum that apparently took place as
Linux was being developed?

I'm curious what they had to say.

        Gary
-- 
Gary Shea (shea@cs.ukans.edu)           Department of Computer Science
      System Manager                    University of Kansas, Lawrence

------------------------------

Crossposted-To: comp.os.linux.help
From: jngreene@nyx10.cs.du.edu (Joseph Greene)
Subject: Help Installing Linux!!!
Date: Wed, 19 Jan 94 05:29:18 GMT

Hello!
I'm attempting to install Linux on my sytem. I have partitioned of a section 
of my hard drive (roughly 34Meg). I have generic.exe from sunsite.unc.edu and
I have a disk with the kernel and stuff on it. However every time I try to 
get it to install I get the error message of 
"Kernel panic: unable to access root sector"
                                ^^^^(boot?)
I have tried this both with partition 2 (the one I want it installed to) as 
the Active partition (Unformatted and DOS formatted), and as the inactive 
partition (Unformatted and DOS formatted). I read the Docs with generic.exe 
and it mentions a program (I think it's a DOS one) called "mke2fs" that will
format a drive for Linux. However I'm unable to find this program. 
sunsite.unc.edu doesn't seem to have it. I REALLY want Linux on my system but 
I obviously need help. Please help! I've already had to rebuild my hard drive 
once and I still have my backup, so I'm not worried about that too much. 

--
Aoooooooooooooooooooooooooooooooooooooooh!!!(pant,pant)
Wild Wolf 
a.k.a. Joe Greene
"The mortal flesh weakens as the wolf's teeth rend!"

------------------------------

From: butta1@bu.edu (Nelson Chin)
Subject: Re: Japanese Extension to Linux, ideal for mule (multilingual emacs) users
Date: 19 Jan 1994 07:12:03 GMT

Charles Denny (cdenny@dellgate.us.dell.com) wrote:
:   I haven't looked at this package yet (still configuring Xwindows),
: but has anyone gotten this running on any other distribution set other
: than SLS?  I noticed it uses SLS's sysinstall program and since I'm
: running TAMU, it looks as if I'll have to mess with the install.

: Just curious,

: CDenny

here's something i got in the mail today which tested JE with slackware and
came out OK. maybe this can be added to the CD-ROM distribution if there's
space left.
Nelson

----cut here----

Subject: Re: Linux to Kiritsubo to no tatakai 
Return-Receipt-To: yasuhiko@chao.elect.chuo-u.ac.jp
In-Reply-To: Your message of "Mon, 10 Jan 1994 13:08:08 EST."
             <Pine.3.89.9401101355.B24019-0100000@ithake> 
Date: Wed, 19 Jan 1994 15:23:54 +0900
From: MIYATA Yasuhiko <yasuhiko@chao.elect.chuo-u.ac.jp>


 Hello!

 Four persons in fj.os.linux("fj" means, you know, "From Japan")
replied whether JE matches well with Slackware.
 The result is it's OK. But there are two small problem.
 The first is you cannot use setup command while installing JE on
Slacware, though you can use setup while installing disk JE1 which is
first disk of JE. That is, you'd better install disk JE1 with setup
command and install other disks of JE with pkgtool of Slackware or
EZINSTALL which is an installation program of JE.
 Second is the difference of the format of man manuals. Slackware's
are ".gz" file, but JE's are ".Z" file. So you have to reformat them
with znew command.
 Except these small problems, I heard, they are well matched. Enjoy JE! 

                                                       MIYATA Yasuhiko

======================================================================
     Chao lab.,Department of Electrical and Electronic Engineering, 
                      Chuo University, Tokyo, Japan
               E-mail : yasuhiko@chao.elect.chuo-u.ac.jp


------------------------------

From: Mitchum DSouza <m.dsouza@mrc-apu.cam.ac.uk>
Subject: Re: Where is libc src?
Date: 19 Jan 1994 05:30:53 -0500
Reply-To: m.dsouza@mrc-apu.cam.ac.uk

Eric Brown:
| What is the ftp location of the libc source code.
| 
| I want to work with .99pl14 kernel and would like the most current library
| first. I currently have the source (linux-libc) to libc.so.4.3.2, but assume
| there is something more recent. Has the format of shared librarys changed
| again or something?

GCC question == read the GCC-FAQ first.

        sunsite.unc.edu /pub/Linux/docs/faqs

Mitch

------------------------------

From: Mitchum DSouza <m.dsouza@mrc-apu.cam.ac.uk>
Subject: Re: Q: libc has _NEEDS_SHRLIB_libc_4 multiply defined?
Date: 19 Jan 1994 05:30:56 -0500
Reply-To: m.dsouza@mrc-apu.cam.ac.uk

John F Skoda:
|   I get this message when trying to compile programs that use 
|  shared libraries.  Does Linux support shared libs?  I thunk

Yup

|  it did?  I just upgraded to libc.so.4.5.8 and got all the
|  files I needed (lib, extra, inc...)  So what am I doing 
|  wrong ?
| 

Please give exact error messages. But the probable reason is that you haven't
read the release notes to the letter. I.e. you haven't deleted /usr/lib/libgcc*
first.

Mitch

------------------------------

From: mdw@sunSITE.unc.edu (Matt Welsh)
Crossposted-To: comp.os.linux.announce,news.answers,comp.answers
Subject: [comp.os.linux.announce] Guidelines for posting
Date: 19 Jan 1994 07:48:45 GMT

Archive-name: linux/announce/guide
Last-modified: 26 Mar 93

HOW TO POST TO COMP.OS.LINUX.ANNOUNCE

This article gives info on how and what to post to comp.os.linux.announce.
Please read the whole thing, to avoid any confusion. :)

To submit an article to this group, please mail the article to:
        linux-announce@tc.cornell.edu

If you have questions or problems with posting to comp.os.linux.announce,
please send mail to the moderators at:
        linux-announce-request@tc.cornell.edu
Or, you may send mail to us directly. The moderators for this group are
Matt Welsh (mdw@sunsite.unc.edu) and Lars Wirzenius (wirzeniu@cc.helsinki.fi).

Whereas most versions of the C-News news software will automatically mail
postings to the moderator address, it may take some time for this address
to propagate (and there are many systems out there not supporting this
automatic mailing feature). Therefore, to ensure that your posting will get
to us, you should probably mail it to us by hand. Once we receive your article
and approve it, we will post your article.

NOTE: Your article will not show up in any newsgroups that it may be
crossposted to (e.g. other than comp.os.linux.announce) until we approve the
article. The delay should be negligible (we read email all the time), so
please don't post the same article separately to other groups. That
causes multiple copies to be sent around under most setups.

Please don't crosspost articles between comp.os.linux.announce and 
other Linux newsgroups (excepting very important announcements, namely the 
Linux FAQ, new kernel/library releases, and others which I'll crosspost at 
my discretion :) ). If enough c.o.l.a articles end up in junk on sites 
which don't carry the group, maybe they'll start to carry it.

If you don't get c.o.l.a at your site, please encourage your news admin to
create it. It's a bona fide group and we need to get wider distribution.

Remember: no announcement is too insignificant for this group. Don't be
afraid to submit something if you think it isn't important enough; that's
why we have moderators, to screen the content of the group. I plan to 
approve almost anything (announcement-wise) that's submitted.

The following guidelines should be used when submitting articles:

  - I will approve a wide range of articles for this group. The only postings
    that are discouraged are discussions and questions about Linux. 
    This group is mainly for:

    * Announcements of new software that has been ported to Linux
      (e.g. "DikuMUD v4.2 is now available on sunsite....")

    * Announcements of new versions or patchlevels of existing software,
      such as GCC, the kernel, libraries, new versions of utilities and so on.
      (e.g. "Linux v1.0 is finally available...")

    * Bug fixes and software patches (or announcements of available patches).
      If you have a fix for a known bug in any Linux software, please post
      the fix and the relevant patch (if any). If the patch is huge, instead
      post an announcement as to where it's available.
      (e.g. "Patch to fix broken 0.98.5 scsi.c....")

    * Summaries of responses for individual requests for information. If you
      requested some Linux-related information on c.o.l.h, and are posting a
      summary of that information, please submit it to c.o.l.a. 
      (e.g. "Summary: What's the best VGA card for Xfree86?")

    * Just about anything else of any importance. If you're not sure if you
      should post the article to c.o.l.a, submit it anyway. It can't hurt,
      and most of the time your article will be approved anyway.

  - When submitting articles, please include valid Newsgroups, Subject,
    Keywords, From, and Date lines in the header. These may either be in
    the mail header itself, or you may simply include the article, header
    and all, in the body of the mail message. Please don't send mail with
    only the body of the article to be posted, as this doesn't include
    the Newsgroups: line and other article-specific information.

  - When submitting articles, please use a descriptive Subject line. 
    If you crosspost the article to other groups, starting your subject with
    "ANNOUNCEMENT" helps it to stick out in those groups. If you're posting a 
    patch or summary, use "SUMMARY" or "PATCH" at the beginning of your
    subject, as "ANNOUNCEMENT" isn't quite appropriate.

  - Also, please use a Keywords line in your header, so that articles may
    be searched more easily in the archives (when we have the archives up).
    The Keywords field should contain one or more of the following:
      Type of announcement: new version, patch, urgent, summary, etc.
      Package: kernel, GCC, X, TeX, SLS, jump tables, etc.
      Type of program: A keyword or two on what your program is.
        This is especially important if the program isn't part of
        a well-known package. Ex: editor, tcpip utils, game, etc.
      Version: 0.98.5, jumptables 4.2, etc.

    For example, if you're announcing v4.2 of Shoopsort for Linux, you
    might want a subject and keywords that look like this:
      Subject: ANNOUNCEMENT: Shoopsoft v4.2 now ported to Linux
      Keywords: Shoopsort 4.2, sorting algorithm, new port

    Or, if you're announcing a summary on ethernet cards for Linux, you
    could have:
      Subject: SUMMARY: Best ethernet cards for Linux TCP/IP
      Keywords: summary, ethernet, tcpip, cards, hardware

If you have any problems or questions, please contact the moderators at
linux-announce-request@tc.cornell.edu. 

Thanks,
Matt Welsh, comp.os.linux.announce moderator

------------------------------


** 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-Misc-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: Linux-Misc@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
    sunsite.unc.edu				pub/Linux

End of Linux-Misc Digest
******************************
