Subject: Linux-Misc Digest #826
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:     Thu, 17 Mar 94 15:13:19 EST

Linux-Misc Digest #826, Volume #1                Thu, 17 Mar 94 15:13:19 EST

Contents:
  [Q] Forcing lilo to wait for the kernel specification (Michael MNUK)
  Re: Version 1.0 (liuyu)
  Re: pronunciation of linux (Tom J. Jarmolowski)
  Re: When is the next Slackware coming? (David Fox)
  Re: *Please* comment on Gateway P4D-66  (486/PCI) (James D. Levine)
  Re: Version 1.0 (Nathan Bardsley)
  Simple **LOCAL** vt100 printing [USEFULL] (Mike R. Prevost)
  Re: PCI ATI VEDIO CARD (James D. Levine)
  *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07) (Ian Jackson)
  pronunciation of linux (Jeff Galbraith)
  Re: pronunciation of linux (Anup M Changaroth)
  Re: Prepare for DOOM (parody) (Dan Newcombe)
  Source code for /bin/login (Con Tassios)
  Re: Opinions wanted about SCO-unix (vs AIX/Linux). (Curt L. Olson (Admin))
  Re: Restricted Shell? (Alan Cox)
  Re: IBM MCA and Novell Netware [ (Alan Cox)

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

From: mmnuk@risc.uni-linz.ac.at (Michael MNUK)
Subject: [Q] Forcing lilo to wait for the kernel specification
Date: Thu, 17 Mar 1994 10:21:28 GMT

I have an 486DX2-66 PC booting linux with lilo. From time to time I
need to boot MSDOS getting lilo's attention by the space-key.  The
problem is that there is too little time between the POST-finished
beep of the system and starting lilo (~ 1 s). I can't press space too
early (causing some error). I would like lilo to wait for about 3 sec,
say, before loading the default kernel. I tried both delay and timeout
parameters. Neither of them gives me the desired result. On the other
hand I don't want to use the prompt parameter. Could someone help me?

Thanks

--
--
Michal Mnuk
Research Institute for Symbolic Computation
A-4040 Linz, Austria

Phone: +7236 3231 75
Fax  : +7236 3231 30
E-mail: mmnuk@risc.uni-linz.ac.at

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

From: liuyu@acf2.nyu.edu (liuyu)
Subject: Re: Version 1.0
Date: 15 Mar 1994 20:31:13 GMT

joslyn@benji.Colorado.EDU (Christopher Joslyn) writes:

>In article <1994Mar14.132245.9833@lulea.trab.se>,
>Anders Eriksson <anders@lulea.trab.se> wrote:
>>A couple of months ago I saw a post about Linux version 1.0 and it said
>>something like 'Version 1.0 will be available in about one month, when
>>XXX have received sufficent patches for version 0.99 pl 15'. Since then
>>I've hurd nothing! What's happening?

>Version 1.0 is out as of today.  Checkout sunsite.unc.edu in
>/pub/Linux/Incoming/linux-1.0*  Enjoy!

  I just dl v1.0.  But the question is how do I compile it?  I also
checked the slackware. It is still 0.99.  Do I have to wait until
slackware compiles them?  
BTW, I have a empty computer that needs a OS.



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

From: tjj@visual.com (Tom J. Jarmolowski)
Subject: Re: pronunciation of linux
Reply-To: tjj@visual.com
Date: Wed, 16 Mar 1994 19:40:02 GMT

In article <2m31ao$c62@harbinger.cc.monash.edu.au>, kevinl@bruce.cs.monash.edu.au (Kevin Lentin) writes:
|> On 14 Mar 1994 23:15:31 GMT, Tom Fox wrote:
|> > Linux rhymes with clinics
|> 
|> Why? All the posts from Linus et al seem to indicate that the u is
|> pronounced as in uncle but yes the i is pronouced as in clinic. (Even
|> though this sounds quite strange to me as an English speaker. I prefer the
|> i to be pronounced as in the pronoun I).
|> 
|> In his comment, Linus refers to 'like minix' and I am pretty sure he is
|> referring to the first i. 
|> 

The only solution to this never ending problem is for Linux to 
change his name. :-)


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Tom Jarmolowski              _/_                    tjj@visual.com
Visual Technology            /      __     _____    ...uunet!visual!tjj
120 Flanders Rd             (__    (_)    (  )  )   Voice: 1-800-VISUAL-C
Westboro MA  01581                                  (in MA) (508) 366-2949
                                                    Fax: (508) 366-4337


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

From: fox@graphics.cs.nyu.edu (David Fox)
Subject: Re: When is the next Slackware coming?
Date: 16 Mar 1994 20:05:45 GMT

In article <p116711.763826995@ee.tut.fi> p116711@cc.tut.fi (Tero Paananen) writes:

] Or should I just install Slackware 1.1.2 (or whatever is the latest)
] and get the source/binaries of v1.0 and Xfree v2.1 and hope that
] they won't break anything crucial?

That is what I have done.  It hasn't broken anything crucial.

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

From: jdl@netcom.com (James D. Levine)
Subject: Re: *Please* comment on Gateway P4D-66  (486/PCI)
Date: Wed, 16 Mar 1994 06:35:50 GMT

Gisli Ottarsson (gisli@timoshenko.eecs.umich.edu) wrote:
~

: I have just placed and order for a Gateway P2D-66 and
: would sleep a little better if I could resolve a few
: iffy areas.  I understand that Gateway is a moving
: target so what works this week may not work next week.

: Here are some questions:

:   o   Are there any problems with the PCI mother-
:       board used in this machine?  Does it work
:       with Linux?  Would you buy (another) one?
My P5-60 PCI motherboard works fine. 

:   o   The 2Mb MACH32 video card that comes with the
:       PCIs from Gateway uses DRAM.  This had been
:       solved for the DRAM VLB-version called ATI CLX 
:       a while ago and is supposedly OK in Xfree86 2.1.
:       Can I expect to use this card for 1280x1024NI
:       @ > 60Hz which is as high as the 17" CrystalScan
:       will go?  Does it work at all with Xfree86 2.0?

I've heard Gateway's display adapters referred to as "the ATI board du 
jour", and my experience bears that out.  The P5-60 I ordered was supposed
to come with a PCI ATI Mach32 XLR, instead what I got was something called
an ATI AX0 - I don't know what the model is, but in every way it seems to
be functionally equivalent to the XLR.  XFree 2.0 runs on it with the Mach32
server.  Xbench shows it to be on the high end, but not as good as the S3 or
#9 boards.  

The Mach32 server only supports dot clocks up to 80, which limits you to
1024x768 with VESA refresh rates.  I've got a NEC 5Fge, which is easily 
pushed up to 1152x900 or 1280x1024, but because of the dot clock limitation,
only 1152x900 is acceptable.  The board itself is capable of a higher dot
clock using some multiplexing scheme, so if anyone ever tweaks the Mach32
server, you will be able to run at higher resolutions, assuming your monitor
can sync to it.

:   o   I've saw one report of problems with the 540Mb
:       IDE hard disk available in this machine.  It 
:       had something to do with Linux not seeing it.
:       Can someone refute or substantiate this?  Is
:       the 424Mb a better choice?

I read a posting claiming that Linux didn't see the 540mb drive, but from 
what I could tell, the poster had installed it as a second drive.  Chances
are the SLS installer simply doesn't let you install a boot partition on
anything but the first drive, since typically PC BIOS only allows you to 
boot from the first (ie. C:) drive.  I doubt there will be any problem
with the 540 drive installed as the first one.  Installing subsequent 
partitions on other drives should work just fine - you just can't boot 
straight from other drives.

I have the 424mb version of the same drive (ie. WD Caviar).  Linux likes it
just fine.  The 540Mb is slightly faster.

 :   o  Has someone ordered this machine with the Colorado
:       Jumbo tape system?  Does it work with Linux and
:       if so, at what transfer rate?
I believe it's supported.

:   o   My system will have a CD-ROM.  Some kind soul 
:       posted info about which CD-ROMs work (according
:       to this source Gateway uses three kinds).  I
:       have lost this posting.  Any comments here?
:       Should I order the Gateway sound card?  Is it
:       any good under Linux?
When I checked last, they were shipping with the Mitsumi drive, which is
supposed to be supported under linux.

: Thanks for any comments.  Needless to say I will post a
: summary if any of these things become sufficiently clear.
:                               
:                                       Gisli
Of course, if you have any problems, Gateway will take the system back
for a full refund.  They also have a 30-day up/downgrade policy, so you can 
exchange pieces of your system that don't work.  I actually invoked this
when I realized my system came with half the simm slots they had 
claimed.  I bought denser RAM from a local vendor; Gateway bought back 
the RAM without any hassle (although, I'm still waiting for the full 
credit to show up on my VISA statement).

 : --

: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: Gisli Ottarsson                                          
: Grad Student and a Gentleman                    
:                                                    Delenda est Carthago.      
: University of Michigan                                         
: gisli@umich.edu

: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

From: nathan@ftp.health.org (Nathan Bardsley)
Subject: Re: Version 1.0
Date: 15 Mar 1994 22:26:56 -0000

In article <2m55uh$dr0@cmcl2.nyu.edu>, liuyu <liuyu@acf2.nyu.edu> wrote:
>joslyn@benji.Colorado.EDU (Christopher Joslyn) writes:
>
>  I just dl v1.0.  But the question is how do I compile it?  I also
>checked the slackware. It is still 0.99.  Do I have to wait until
>slackware compiles them?  
>BTW, I have a empty computer that needs a OS.

Yes.  As everybody knows, all the documentation, FAQS, READMES, and all
the work of the LDP are invalid as of 1.0.  From now on, only authorized
developers will be able to compile programs for Linux.

Come on people.  How can anyone who's unsure of what they're doing not
leap at the chance to get a book called "Linux Installation and Getting
Started"?

0.  Get and read the HOWTOs, and the LDP books.  

1.  Untar & un gzip the file in /usr/src so that it makes /usr/src/linux and
subdirectories.  (What?  you don't know how to untar or un gzip?  Then
go away until you've read some manuals.)

2.  Verify the links for asm and linux to /usr/include.

3.  make mrproper

4.  make config

5.  make dep
 
6.  make clean

7.  make zImage

8.  reconfigure/rerun lilo to clean up the boot image maps.
-- 
Nathan Bardsley -- nathan@health.org

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

From: mprevost@aslnx1.asb.uah.edu (Mike R. Prevost)
Subject: Simple **LOCAL** vt100 printing [USEFULL]
Date: Thu, 17 Mar 94 06:25:50 GMT


WHAT IT IS:
Here's a simple C program that lets you print file from unix to a printer
connected to a vt100 terminal.  I wrote and test this little thing just
a few minutes ago over a modem->terminal_server->linux link.  It will work
with NCSA telnet too.  Should work with _any_ vt100/102 terminal.  Umm,
I hope your printer doesn't start printing when you read this.  ;)

HOW IT WORKS:
Well, all it does is send an 'ESC [ 5 i' to the terminal which means
to start the vt100 printer.  Then it just gets characters and writes
them to the terminal (which is writing to the printer) until it runs out 
of characters.  Then it sends a  'ESC [ 4 i' which just says to turn off 
the vt100 printer.  Simple.

HOW TO USE IT:
If you have a text file 'myprog.c' and you want to print it, just type
"cat myprog.c | prn" where prn is the compiled binary of the included 
code.  I've used it to print to a printer on a novell network too and it 
works great.  

It probably needs some enhancements, like being able to take a file name 
on the command line and stuff.  but here is is (all 8 lines):
=======start==========
#include <stdio.h>
int main () {
   printf("%s", "[5i");
   while (!feof(stdin)) 
      printf("%c", getchar());
   printf("%s", "[4i");
   return 0;
}
======stop============

-- 

--- mIke

 /*--------------------------------+-----------------------------------------+

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

Crossposted-To: comp.os.linux.help,comp.unix.admin
From: jdl@netcom.com (James D. Levine)
Subject: Re: PCI ATI VEDIO CARD
Date: Wed, 16 Mar 1994 06:49:22 GMT

Edmund Knowles (d0zawjh@server4.bell-atl.com) wrote:
: Hi,
:       I have a gateway pentium that has a ati ax0 video card ont the PCI bus.
:       I cannot get x windows to run in ati-vga mode because it
:       does not have the proper chipset, it seems that linux was released 
:       before the PCI video card was available.
:       does any one know if the right chipset or whatever I need is availiable?
:       and how do I go about getting it. 
:       I can run X in monochrome-vga but that is all.
:       Thanks in advance.
:       Ed.
:       dzawjh@server4.bell-atl.com

I have the same configuration - you need XFree 2.0 (or now, 2.1), with the
Mach32 accelerated server.  

James


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

From: ijackson@nyx.cs.du.edu (Ian Jackson)
Subject: *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07)
Date: Thu, 17 Mar 1994 11:03:01 GMT

Please do not post questions to comp.os.linux.misc - read on for details of
which groups you should read and post to.

Please do not crosspost anything between different groups of the comp.os.linux
hierarchy.  See Matt Welsh's introduction to the hierarchy, posted weekly.

If you have a question about Linux you should get and read the Linux Frequently
Asked Questions with Answers list from sunsite.unc.edu, in /pub/Linux/docs, or
from another Linux FTP site.  It is also posted periodically to c.o.l.announce.

In particular, read the question `You still haven't answered my question!'
The FAQ will refer you to the Linux HOWTOs (more detailed descriptions of
particular topics) found in the HOWTO directory in the same place.

Then you should consider posting to comp.os.linux.help - not
comp.os.linux.misc.

Note that X Windows related questions should go to comp.windows.x.i386unix, and
that non-Linux-specific Unix questions should go to comp.unix.questions.
Please read the FAQs for these groups before posting - look on rtfm.mit.edu in
/pub/usenet/news.answers/Intel-Unix-X-faq and .../unix-faq.

Only if you have a posting that is not more appropriate for one of the other
Linux groups - ie it is not a question, not about the future development of
Linux, not an announcement or bug report and not about system administration -
should you post to comp.os.linux.misc.


Comments on this posting are welcomed - please email me !
--
Ian Jackson  <ijackson@nyx.cs.du.edu>  (urgent email: iwj10@phx.cam.ac.uk)
2 Lexington Close, Cambridge, CB4 3LS, England;  phone: +44 223 64238

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

From: Jeff.Galbraith%f21.n5500.z201@cpubbs.cuug.ab.ca (Jeff Galbraith)
Reply-To: Jeff.Galbraith%f21.n5500.z201@cpubbs.cuug.ab.ca (Jeff Galbraith)
Subject: pronunciation of linux
Date: Mon, 14 Mar 94 19:34:48 

Howdy kevinl@bruce.cs.monash.edu.au!

 >> How should I pronunce the letter "i" in "linux", like the one
 >> in "line" or the one in "linear"?  Thanks.

 kcmea> There's a post somewhere around where Linus describes how it
 kcmea> should be pronounced. Strangely though, it made no sense to me. I
 kcmea> managed to conclude that the u should be prounced like the i in
 kcmea> "it". So I gave up on that one and pronounce it lie-nuks. (i as
 kcmea> in "line" and u as in "ugly").

 kcmea> I've also heard linix (it and it, like minix), linux (it and
 kcmea> ugly).

 kcmea> I always presumed linux would be pronounced similarly to Linus
 kcmea> which I pronounce as desribed above. I'd love a definitive
 kcmea> answer.

I've always pronounced it Lie-knicks, for the very fact that it's close to
Linus. However, I recently read that it should be pronounced like minix, with
an L, since Linux is a Minix dirivitive. It was in some FAQ.

Jeff.Galbraith
@f21.n134.z1.fidonet.org
%f21.n5500.z201@cpubbs.cuug.ab.ca

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

From: aa160@city.ac.uk (Anup M Changaroth)
Subject: Re: pronunciation of linux
Date: 17 Mar 94 13:16:28 GMT

marauder@lod.amaranth.com (marauder) writes:

>Mark A. Davis (mark@taylor.wyvern.com) wrote:
>: kjetilho@ifi.uio.no (Kjetil Torgrim Homme) writes:

[...]

>: >Linux is then /'li:nuks/ or "Lee-nooks".

>: continue calling it  /'Lie-nucks/.  Besides, it matches the English 
>: pronunciation of Linus and Unix combined...

>Me too, at the risk of becoming a periah amongst the purist's I'm afraid
>I'll stick with pronouncing it "lie-nucks" too, since that's how I
>pronounced it prior to reading the "pronunciation-FAQ". It's too late to
>amend my verbal ways..

>mar

Anyone for "line-X" (pronounced in quick succession)? Somehow I've always
prefered this, instead of rhyming with "clinics" :)


-- 
                                ______
 Anup M Changaroth              \    /       Computer Systems Engineering
 Internet: aa160@city.ac.uk    L I N U X      City University, London. UK
                                  \/

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

From: newcombe@aa.csc.peachnet.edu (Dan Newcombe)
Subject: Re: Prepare for DOOM (parody)
Date: Thu, 17 Mar 1994 10:02:10

In article <1994Mar16.162046.17116@taylor.wyvern.com> mark@taylor.wyvern.com (Mark A. Davis) writes:
>>Ah, what the heck.  It is a .misc group.

>>How about:  Can I run Linux Doom under windows?

>Indeed, that is the whole point- running under Unix and Xwindows.....
>or were you refering to the product named MS-Windows?


Yes, I was refering to MS-Windows.  After all, they are both windowing 
software, and Microsoft is a bigger company than X is (What kinda company
name is that anyway?)  Besides, MS-Windows is easier to use and way more
powerful, and....  :)   Hmmm...maybe I should send this to the MS advocay 
group (hehe)

  -Dan

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

From: cpt@infinity.apana.org.au (Con Tassios)
Subject: Source code for /bin/login
Date: 17 Mar 1994 21:36:05 -0000


I am looking for the source code for the /bin/login included in Slackware
1.1.2.  I have checked the directory /pub/linux/slackware_source
on ftp.cdrom.com but haven't been able to locate it anywhere.

If anyone knows of its whereabouts, please mail me.


Thanks,
Con.   <cpt@infinity.apana.org.au>

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

Crossposted-To: comp.unix.advocacy,biz.sco.general
From: clolson@me.umn.edu (Curt L. Olson (Admin))
Subject: Re: Opinions wanted about SCO-unix (vs AIX/Linux).
Date: Thu, 17 Mar 1994 14:54:26 GMT

kees@echelon.uucp (Kees Hendrikse) writes:

>In <Mario.Eduardo.13.000C52CA@vu-wien.ac.at> Mario EDUARDO writes:

>> it is very simple to determine the quality of the SCO system :
>> get some public domain software (gnu cpio, gnu tar, gnu sed, inn, sendmail, 
>> various tcp daemons) and try to compile it. it was  a lot of work to compile 
>> GCPIO on ODT 1.1.0, and because of the compatibility ODT 1 to ODT 2 to ODT 3
>> it is lost time to try it on ODT 3. 

>Mario, you realy should try it. You might be in for a pleasant surprise.
>Also, if your experience with SCO DS stopped with 1.1, please refrain
>from commenting on later systems.

I too had no trouble compiling these packages --- after I installed GCC!

Does the c compiler under ODT 3 still have optimizing bugs?

Curt.

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

From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: Restricted Shell?
Date: Thu, 17 Mar 1994 10:51:25 GMT

In article <2m7b1o$1h4@darkstar.rsa.lib.il.us> wbeckner@darkstar.rsa.lib.il.us (William Beckner) writes:
>Does Linux have a restricted shell?  If so, what is it called?  The man
>pages says that rsh is a remote shell.  I'm trying to set up a guest-like
>account that can only run gopher, so any help in setting this user up would
>be greatly appreciated.  TIA!
>
Don't rely on a restricted shell on any machine. It's TOO easy to make a
mistake. For example on most Unixes you can set the LD_LIBRARY_PATH env
variable in a restricted shell, upload a 'library' of your own design and
get it run by the restricted shells commands.

You can almost certainly just put gopher in as the login shell instead.

Alan


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

From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: IBM MCA and Novell Netware [
Date: Thu, 17 Mar 1994 10:57:09 GMT

In article <2m4s00$nl1@lyra.csx.cam.ac.uk> nmm@cl.cam.ac.uk (Nick Maclaren) writes:
>In article <1994Mar13.204656.10648.chiark.ijackson@nyx.cs.du.edu>, iwj10@cus.cam.ac.uk (Ian Jackson) writes:
>|> 
>|> The reason Linux doesn't run support MCA or NetWare is in each case
>|> difficulty in obtaining relevant information.  I expect that the same
>|> is true of AppleTalk, though a lack of people wanting the facility may
>|> well have some impact there.
>
IBM are normally very forthcoming with often good quality documentation. They
tend to charge 'market prices' but they do deliver.

>As far as I know, Netware is a totally closed design.  While it would be
>easy for someone to become a registered Netware developer and get access
>to the information, it would cost real money.  I would be surprised if the
>Linux development community feel like paying real money to Novell for the
>privilege of supporting their system.

Netware is a closed design, and if you pay them money ($30,000 for server docs)
last time I investigated this you then can release binary only and must pay
royalties. You can reverse engineer it but in the states if you do this they
still have patents for you to worry about.

Alan


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


** 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
******************************
