HDTenEightyP/NetNews huggingface dataset:
From: kotulla@talisker.informatik.rwth-aachen.de (Axel Kotulla)
Newsgroups: comp.os.linux
Subject: Linux useradd
Date: 23 Dec 1992 15:52:59 GMT
Organization: RWTH Aachen, Deutschland
Distribution: world
Reply-To: kotulla@talisker.informatik.rwth-aachen.de (Axel Kotulla)
NNTP-Posting-Host: talisker.informatik.rwth-aachen.de

Hi,

When I start the script adduser it establishes a new account for a new user.

The problem is that the new user has no password. O.K. one can log in but when
the new user tries to change (add) a password the system does not allow this.
The superuser is allowed to add a new password but then after each login the
new user gets a message that his password will be expired in 0 days. The
next day
no login is possible and the superuser has to create a new one.

What is wrong? How are new users established correctly?	

Axel Kotulla (E-Mail: axel@pool.informatik.rwth-aachen.de)
From: slc4x@cc.usu.edu
Newsgroups: comp.os.linux
Subject: LILO0.7 installed but goes X(LILO/XS3/Orchid f-1280)
Date: 2 Jan 93 18:16:20 MDT
Organization: Utah State University

Hi: 
     After I successfully install LILO-0.7 , I can boot linux from my
SCSI HD but the X386 went wrong.
     Every time when I startx the screen just pop some error message very fast
and then the system reboot itself.
     I can barely see the error message but I think it's something like

   general protection ...........
   EIP ...........
   EFLAGs .....
   fs .........
    ...........

So I have to go back, and boot from floppy, and X works well.
     I tried to install lilo in floppy, the same thing happy. And I remember
may be this problem has been asked in middle DEC 92'.

My config file is as following
---->    boot = /dev/sda1
         install = /etc/lilo/boot.b
         image = /Image
         label = linux
         root = /dev/sda
         vga = normal
         ramdisk = 0

I've try to setup different vga type and ramdisk size but it didn't work.
The X server I used is XS3-0.3, and the vga card is Orchid Fahrenheit 1280
, 16 MB RAM and phonex BIOS.

      Someone know what happen? Please help me to solve the problem.
Thanks in advance.
By the way I found that the news posted before(the news number lower than
current news we can see) is sometimes very useful. Does someone know is there
any to get them ?
Thanks again

Chen-Yuan Wu
From: sdw@meaddata.com (Stephen Williams)
Newsgroups: comp.os.linux
Subject: Re: Xconfig for LCD screen
Date: 30 Dec 1992 22:33:01 GMT
Organization: Mead Data Central, Dayton OH
NNTP-Posting-Host: bugatti.meaddata.com
X-Newsreader: Tin 1.1 PL5

Lou Berger (lberger@BBN.COM) wrote:
: 
: Does anyone out there have an Xconfig for a mono LCD screen with Cirrus
: Logic VGA driver and reported chip type of 'stingray'.  I'm having much
: trouble getting the timing parameters right.  (If I only had a spec
: sheet....) 

I have the same thing.  The standard 640x480 (plus 800x600 virtual)
worked fine for me.

sdw
--
Stephen D. Williams  Local Internet Gateway Co.; SDW Systems 513 496-5223APager
LIG dev./sales       Internet: sdw@world.std.com CIS 76244.210@compuserve.com
OO R&D Source Dist.  By Horse: 10028 Village Tree Ct., Miamisburg, OH 45342
GNU Support          ICBM: 39 34N 85 15W I love it when a plan comes together
Newsgroups: comp.os.linux
From: amir@avalon.physik.unizh.ch (Guindehi Amir)
Subject: Re: emacs cursor problem in Xterm
Organization: University of Zurich, Department of Computer Science
X-Newsreader: Tin 1.1 PL4
Date: Mon, 28 Dec 1992 17:08:06 GMT

Hi !

ah214@yfn.ysu.edu (Weijin Mai) writes:
: 
:Emacs runs fine in text mode. When I start emacs in a xterm, the seperae
:cursor keys print out B,A,C,D instead moving the cursor. I looked into Xmodmap
:andfound nothing wrong with the key assignment. I am sure some of you had this
:same problem and have solution for it.

I made a TERM=vt100, and after that they worked, but I'm not sure if this is
the right way ... ;-))

- Amir Guindhei

EMail : amir@avalon.physik.unizh.ch
From: Bob.Martin@f34.n343.z1.fidonet.org (Bob Martin)
Newsgroups: comp.os.linux
Subject: lpd
Date: Thu, 31 Dec 1992 12:49:46 -0800


 From : Bob Martin                      	Number : 1      
   To : all                             	 Ref.# : 191    
Subj. : Just hangs during boot fl       	  Conf : Linux
 Date : 12-31-92  Time : 07:06  [3/3]

  Michael Gerhards,
  In a message on 25 December, wrote :

MG> From: michael@jester.GUN.de (Michael Gerhards)
MG> 
MG> ben@rex.uokhsc.edu (Benjamin Z. Goldsteen) writes:
MG> >       My friend has a 486-33MHZ 16 MB EISA/FAST SCSI (AMI
motherboard MG> > and SCSI adapter). It sounds like the machine to run
UNIX on.  Well,MG> > I tried running both 386BSD and LINUX and they both
seem to die MG> > in the same places -- around the disk drive stage. 
386BSD stops MG> > right after it is changes root device to the floppy. 
LINUX stops MG> > right after it figures out that my SCSI adapter is
Adaptec 1542 compati MG> 
MG> Try to disable all cachable areas in the cmos-setup. I heard a lot
of MG> problems with these cache-areas set on. 
MG> 
MG> Michael
MG> --
MG> * michael@jester.gun.de   *   Michael Gerhards   *  
E.-Hoepner-Strasse 4 MG>                           *   D - 4040 Neuss 1 
 *   Voice: 49 2131 47098 MG> 
MG> ---
MG>  * Origin: Gated by {remote.uucp}, +1 206 292 9048 (1:343/94) MG> 
I've seen several post about the kernel hanging and they all seem to be
related to 486 platforms vs 386, so I'll relay my experience.

Two weeks ago I got 486SLC(Cyrix 25mhz Phoenix bios Oak chipset) and
attempted install Linux from my floppy boot/root diskettes. The kernel
would hang at the same place every time (The same diskettes work fine on
my 386dx desktop).

In the kernel init.c routine it was hanging after doing
execv("/bin/init",argv_init,argc_init). If the processor speed was in
slow speed it would hang after prompting to insert root floppy and press
ENTER. In both cases the floppy drive light stayed lit but the disk
wasn't being read. It also did not seem to be dependent on any one
version of the kernel ( I tried 0.95c, 0.981, 0.984, 0.985 and 0.99).
Any ideas Linus ?

Since I new the diskettes were good and the disk drive is ok (works fine
under dos and windows) I started looking at the CMOS settings. After
trial and error I found that if I added 1 wait state the hangups went
away.

Any body else seen this before or can confirm this, may just be my
hardware.  
...
 * ATP/Linux 1.40 * When you go to the market, use your eyes, not your
ears.


 * Origin: -[S'Qually Holler's]- HeadQuarters for Fidonet Linux Net
(1:343/34)
From: makisara@vtinsx.ins.vtt.fi (Kai Makisara)
Newsgroups: comp.os.linux
Subject: Re: Fujistu
Date: 23 Dec 92 00:10:04
Organization: Technical Research Centre, Instrument Lab., Espoo, Finland
NNTP-Posting-Host: vtinsx.ins.vtt.fi
In-reply-to: stephen@glas.rtsg.mot.com's message of Tue, 22 Dec 1992 11:15:02 GMT

   tannerrj@cnsvax (ROOT OF INSIGHT-- A 486 RUNNING LINUX V0.99) writes:

   >I am looking for the stats (heads, sectors and cylinders) for
   >the Fujistu SCSI drive model number m2624F-512. Thanks

   Do you need this info for fdisk? If so, and you know the capacity of
   the drive, you can `fake' it. As I understand it, linux does not use
   the drive geometry. It just puts it in the partition table to keep 
   DOS happy. When linux talks to the SCSI controller, it talks in 
   terms of blocks, and lets the controller/disk (?) translate to
   cylinder/sector/head. 

   So....if you set heads=64, sectors=32 and cylinders=<capacity of 
   drive in Mb> everything should work ok. i.e. with 64 heads and
   32 sectors, each cylinder is 1Mb.

You should use the same translation that the SCSI adapter BIOS or the
DOS driver use for DOS. Otherwise you may get trouble. The translation
64 heads, 32 sectors applies to most of the current Adaptec adapters.
The Future Domain adapters use a different scheme (I don't have the
numbers here) and other adapters may have still other schemes.

...

   Stephen....

   -- 
   | Stephen Shortland,      | Motorola Ireland Ltd,    |                      |
   |                         | Mahon Industrial Estate, | stephen@             |
   | Phone +353-21-357101    | Blackrock, Cork,         |    glas.rtsg.mot.com |
   | Fax.  +353-21-357635    | IRELAND.                 |                      |

	Kai

--
DISCLAIMER: The views expressed here are mine and may not always
coincide with the views of my employer.

*  Kai Makisara                *  email Kai.Makisara@vtt.fi    *
From: nation@dopey.sanders.lockheed.com (Robert Nation)
Newsgroups: comp.os.linux
Subject: More on big cursors
Date: 22 Dec 92 13:52:19 GMT
Distribution: comp.os.linux
Organization: Lockheed Sanders, Inc.


After seeing Ed Carp's (I think) message about wimpy cursors, I
thought that big cursors were just the thing for laptops. It is very
hard to see the underline cursor on an LCD screen. Unfortunately,
I didn't think that patching the kernel was really the best way to fix
the problem, particularly since some of those laptops are 386 sx's and
it takes a year and day to recompile the kernel. So here's a little
program which lets you change your cursor size whenever you feel like
it
#include <unistd.h>
#include <stdlib.h>

void outb_p(char value, unsigned short port)
{
  __asm__ __volatile__ ("outb %%al,%%dx"
                        ::"a" ((char)value),"d" ((unsigned short) port));
}

main(int argc, char **argv)
{
  unsigned long video_port_reg, video_port_val;
  int val1,val2,top,bottom;

  if(argc!=4)
    {
      printf("Usage: %s cons_type top bottom\n",argv[0]);
      printf("cons_type is m for monochrome, c for color or grey-scale\n");
      printf("top is the top row of the cursorwhich is on\n");
      printf("bottom is the bottom row\n");
      printf("Example %s c 0 17 make a block cursor on 80x25 color vga\n",
	     argv[0]);
    }
     
  if(argv[1][0]=='c')
    {
      video_port_reg = 0x3d4;
      video_port_val = 0x3d5;
    }
  else
    {
      video_port_reg = 0x3b4;
      video_port_val = 0x3b5;
    }
  top=atoi(argv[2]);
  bottom=atoi(argv[3]);


  val1=ioperm(video_port_reg,1,1);

  val2=ioperm(video_port_val,1,1);

  outb_p(10,video_port_reg);
  outb_p(top,video_port_val);
  outb_p(11,video_port_reg);
  outb_p(bottom,video_port_val);
}

I called the program cursor_size and put in /bin or /usr/bin. You need
to make it setuid root if you want to be able to use it as a regular
user. I put the line in my rc.local "cursor_size c 0 17" which makes a
full block cursor on an 80x85 color VGA screen. the "c" says to use a
color (or greyscale LCD) screen, instead of a mono screen, for which
you would use "m". 0 and 17 are the cursor extents, in rows.

		Hope someone finds this useful,
		Rob Nation
		nation@rocket.sanders.lockheed.com
From: eichin@athena.mit.edu (Mark Eichin)
Newsgroups: comp.os.linux
Subject: Re: "the `gets' function is unreliable and should not be used"??!!!
Date: 2 Jan 1993 00:22:44 GMT
Organization: Massachusetts Institute of Technology
NNTP-Posting-Host: tweedledumber.cygnus.com
In-reply-to: dld54032@uxa.cso.uiuc.edu's message of Thu, 31 Dec 1992 21:53:06 GMT

>> From: dld54032@uxa.cso.uiuc.edu (Dave Dribin)
>> really unreliable.  I would think that all the standard ASNI functions would
>> be reliable!  Thanx in andvance, and happy new year...
	The ANSI C standard (or at least, X3.159-1989, I believe there
was a 1990 update that I don't have yet) makes no mention of the
problem; the "Rationale" only mentions that fgets subsumes gets
because gets has no way to limit the size of the input buffer. The
documentation I wrote for a free C library documents gets in a much
stronger way:

	This is a <[dangerous]> function, as it has no way of checking
	the amount of space available in <[buf]>. One of the attacks
	used by the Internet Virus of 1988 used this to overrun a
	buffer allocated on the stack of the finger daemon and
	overwrite the return address, causing the daemon to execute
	code downloaded into it over the connection.

If you look up some of the papers written about the Morris Virus,
you'll find some of them mention that BSD only had gets for backwards
compatibility, and that fgets had been introduced around ***1978***
and there was no reason for any code written since then to use gets.
You'll also find vivid detail of how sloppy code (like gets) can make
it possible for someone to break into your system.
	I think it was a mistake for ANSI to standardize that
interface (especially without at least justifying it in the rationale)
but they were, after all, only supposed to codify existing practice,
even if existing practice was incorrect.

				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
				Cygnus Support <eichin@cygnus.com>
ps. Feel free to forward this to whoever teaches the class that you
were writing that code for :-)
Newsgroups: comp.os.linux
From: rahardj@ccu.umanitoba.ca (Budi Rahardjo)
Subject: Re: something screwy with mail...
Organization: University of Manitoba, Winnipeg, Canada
Date: Sun, 3 Jan 1993 01:47:41 GMT

Another problem with mail. I have a smail alias, say
'budi_rahardjo' is aliased to 'budi'.
I can receive mail to budi_rahardjo from a remote site.
Thus my smail alias works.
But for some reasons I can use 'mail' or 'elm' to send
mail to userid 'budi_rahardjo'.

I found this when I tried to alias 'usenet' to 'news'.
(I don't have 'usenet' userid and cnews sends error msg to
that userid).

mail or elm should use the aliases (or let smail handles it).

-- budi
-- 
Budi Rahardjo <Budi_Rahardjo@UManitoba.Ca>
Unix Support - Computer Services - University of Manitoba
Newsgroups: comp.os.linux
From: "david shadoff" <david.shadoff@canrem.com>
Subject: question and observat
Reply-To: "david shadoff" <david.shadoff@canrem.com>
Organization: Canada Remote Systems
Distribution: comp
Date: 1 Jan 93 20:37:22 EST

In message <725809501.AA28841@remote.halcyon.com>,
Jim.Corbett@f35.n152.z1.fidonet.org (Jim Corbett) writes (of Peter
MacDonald's efforts regarding SLS distributions):

>May I suggest that you not try to keep up with all the
>latest releases of everything, and just release SLS sets that you are
>very happy with.
>
>Or release a SOLID SLS and a BEAT-BETA SLS set, so those that have to
>have the latest and greatest will be able to help you debug and those
>that are wanting something more solid can have that as well.

Hear Hear.  Well put.  I agree that Peter's efforts are one of the
major forces propelling Linux forward, and that more (vocal)
appreciation will come when stability does (progress need not suffer!).
Perhaps Linux kernel version 1.0 will assist in this regard.

Hey, won't that be a kick ?  In, say, May... maybe Linux 1.0 will
be out, (and the newsgroup split vote will again be available...the
neverending thread...).  Linux users and Linux developers should
both be out in force by then.  ;-)

 - Dave
 
 /===================================================================\
|    David Shadoff       |  Usenet:  david.shadoff@canrem.com         |
 \===================================================================/
---
  DeLuxe 1.21 #7291  Home is anywhere you hang your head.
--
Canada Remote Systems  - Toronto, Ontario
World's Largest PCBOARD System - 416-629-7000/629-7044
Xref: sparky comp.os.linux:21814 comp.windows.x.i386unix:154
From: jem@snakemail.hut.fi (Johan Myreen)
Newsgroups: comp.os.linux,comp.windows.x.i386unix
Subject: Re: Xfree86 1.1 on Linux: et4000 clocks-resetting problem?
Date: 27 Dec 92 13:14:21 GMT
Organization: Helsinki University of Technology, Finland

In article <1992Dec23.015133.9900@cbnewsj.cb.att.com> dwex@cbnewsj.cb.att.com (david.e.wexelblat) writes:

>> first time I tried it after running 1.0Ya, but on subsequent
>> invocations the clocks were different from what I see with 1.0Ya on
>> linux and 1.1 on sysV.4 (this is with a Speedstar 1MB card).

>prior to the timing loop.  But filling in the Clocks line in the
>Xconfig file is always a good idea, if for no other reason than it
>saves a couple of seconds at server startup time.

I have a similar problem which shows up when I'm using xdm. X always
comes up fine the first time, but when X is restarted when I log out
*most* of the time the clocks or something else is wrong with the
settings on my ET4000 card, resulting in a flickering and distorted
display. The strange thing is, I *have* a clocks line my Xconfig. When
I start the server with 'startx' the clock frequencies are reported
correctly. I tried changing an unused frequency in the clocks line,
and yes, the line reported on startup changed too, so X recognizes the
clocks line. But it still looks like it is attempting autodetection,
and failing.

My configuration: Linux 0.99.1, X server 1.0Ya (from the SLS kit),
ET4000 based video card.

Johan
Organization: Ryerson Polytechnical Institute
Distribution: na
Date: Thursday, 24 Dec 1992 11:23:09 EST
From: <ACPS7221@RyeVm.Ryerson.Ca>
Newsgroups: comp.os.linux
Subject: Re: SED is buggy (libc.so.4.2 bug ?)
 <BzrJ7x.Fx@nmrdc1.nmrdc.nnmc.navy.mil>

    The new sed (1.13) compiles perfectly out of the box with 99.1.  I kept my
old one around just in case. The sources can be found at many places, including
prep.ai.mit.edu in /pub/gnu/sed-1.13.tar.Z (something like that).
                                                Michael.
Newsgroups: comp.os.linux
From: wyvern@gnu.ai.mit.edu (The Wyvern)
Subject: Re: Ctrl-Alt-Del
Organization: Free Software Foundation
Date: Tue, 29 Dec 1992 16:28:38 GMT

In article <350102Tu30st01@JUTS.ccc.amdahl.com> jdg00@amail.amdahl.com (Josh Grosse) writes:
>I found that I couldn't do a "three finger salute" on my notebook pc when Linux
>was running until I turned off the shadow ram bios in my bios set up.  Shadow 
>ram consumes 128K, and is a copy of the rom bios (slow) running in ram (fast).
>
>As far as I can tell, Linux only uses bios during boot, so I turn off shadow
>ram (and get an extra 128K) when I run Linux.
>

I'm running a 486 using Phoenix BIOS, and have also noticed that reboot and
ctrl-alt-delete wouldn't work unless I turned off the shadow ram.
I don't want to disable it if it'll slow down the system significantly,
but I was also under the impression Linux didn't use the BIOS much.
Can someone who knows confirm this?


>The same version of SLS loaded onto a friend's machine does not have this 
>problem.  So, this may be indicative of particular clone configurations.
>
>My notebook (TI 3000) uses a blend of Phoenix and Quadtel bioses.
>-- 
>-----------------------------------------------------------------
>Josh Grosse                                jdg00@amail.amdahl.com
>Amdahl Corp.                               313-358-4440
>Southfield, Michigan
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: Defragment on Linux extfs
Date: 24 Dec 1992 04:34:49 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

cp79111@csie.nctu.edu.tw (Kuo-Ping Hsu) writes:


>I got a defragement program at tsx-11.mit.edu (linux/ALPHA/defrag-0.2.tar.Z).
>When I install and use it, my file system crashed. Have anyone can tell me
>why. My Linux extended file system is ALPHA 11.

>------
>cp79111@csie.nctu.edu.tw
>K.P. Hsu

Did you run it on a mounted file system?? This is bad news, as it is moving
disk structures around, and the last thing you want it to do is update and
rewrite the old inode map and superblock back to the disk.  

Try running efsck on it, but good luck as I don't know if it could help this.

James
From: keithc@welchgate.welch.jhu.edu (Keith Christopher)
Newsgroups: comp.os.linux
Subject: UUCP 103 (taylor)
Date: 21 Dec 92 15:36:25 GMT
Organization: Johns Hopkins Univ. Welch Medical Library

Hi,


 I have almost everything in the SLS installed (not X) and the compiler is installed correctly as well as mail and ELM2.3. The problem is when I FPTd uucp103.tar from TSX-11. I untarred it to my /usr partition. And ran make. the error messages I get are these:


Infile included from uucico.c:304:uucp.h:1180:conflicting types for 'strncasecmp'
/usr/include/string.h:36: previous declaration of 'strncasecmp'

make *** [uucico.o] error 1




any ideas ?


keithc@welchgate.welch.jhu.edu
Newsgroups: comp.os.linux
From: marcf@nexus.yorku.ca (Marc G Fournier)
Subject: Re: Am I dreaming, or is this possible?
Organization: York University
Date: Mon, 28 Dec 1992 16:01:09 GMT

tweek@netcom.com (Michael D. Maxfield) writes:

>Of course I mentioned a few posts back, that I am a newcomer to the world
>of un*x sysadmin, and all the devices that go with it.  I know this question
>doesn't entirely belong in this newsgroup, but I'd bet I'd get flamed royaly
>if I asked it on comp.os.unix and the like. :)

>What I eventually plan (want) to do, is to network my 386 Linux box to
>my 286 Dos BBS box via a serial port.  (so far, sounds simple enough)
>What I would like to do is allow (through some sort of door program [no
>windows, desqview, or doubledos being used] on the 286) a dialin BBS user
>to telnet (and maybe ftp) to the Linux box.  (ah, but theres more...)  There
>would be options to telnet to different ports (ie: the internet type... 2010,
>4013, 4020...) to access either a logon, or a mud, or some other type of
>program.  Am I crazy, and I should toss in the towel on that idea know, or
>will some sort of SLIP program do this.  Any ideas.  A FORGET IT or YES, THAT
>IS POSSIBLE is all I'm looking for at the moment.  If I know it's
>possible, I can do the research, probably, on my own... and if not, I may 
>come whining back saying It Don't Work.... Waaaaaaa.

	Yes, it is possible.  There are PD SLIP/telnet/ftp programs
available on wuarchive.wustl.edu that I downloaded a while back...yet
haven't had time to play with :(

Marc
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: "No free inodes - contact linus" 0.99pl0 kernel
Date: 23 Dec 1992 11:55:57 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu
Keywords: Linux, kernel problem

arumble@extro.ucc.su.OZ.AU (Anthony Rumble) writes:

>I get this coming up a few times while I was under X running
>some applications..

>"no free inodes - contact linus"

>What does this mean???

>Thankyou in advance..

>-- 
>Anthony Rumble

This means you should upgrade to 0.99.1 :-)

In 0.99.1, Linus incorporated the fix for this. There is a constant in 
/usr/include/linux/fs.h called NR_INODE which was set to 128 under pl0.

By changing it to 256, I haven't seen any problems with this happening yet.

You should be able to get full source, patches against pl0, or a binary image
from either tsx-11.mit.edu or nic.funet.fi.

James
Newsgroups: comp.os.linux
From: philipr@extro.ucc.su.OZ.AU (Philip Rhoades)
Subject: Situation deteriorating - SCSI? Swap Part.? - HELP!
Summary: Booting prob on 4th install - swapper
Keywords: install prob scsi swap X
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Tue, 22 Dec 1992 22:28:25 GMT

I posted a note earlier about a problem getting X going at all on a
second machine - details:
	386DX - Western Digital (old)
	4Mb RAM
	Adaptec SCSI 1542 controller
	Seagate ST3283N 240Mb Hard Drive

The first installation I didn't worry about a swap partition or file -
I got 0.98.5 installed alright and the boot disk created. When I started 
up X there were problems, no amount of configuring helped so I conclude
it was a memory problem and decided to add swap space as a file - that
didn't work so I decided to re-install with a swap partition. After two
attempts to get that right I try to start from the boot disk. 

The system appears to be working alright - it detects the SCSI drive etc
but then stops with the following message:

	task[0] (swapper) killed: unable to recover
	Kernel panic: Trying to free up swapper memory space
	In swapper task - not syncing

I don't know where to go from here - both the main partition and the
swap partition should be active shouldn't they?

Any help from linux/scsi gurus? I am really keen to get Linux going -
it looks great from what I have read.

Thanks in advance,

Phil

-- 
Philip Rhoades
First Year Biology
University of Sydney
phil@biox.bio.su.OZ.AU or philipr@extro.ucc.su.OZ.AU
Newsgroups: comp.os.linux