🚀 go-pugleaf

On Fri, 04 Aug 2000 21:42:43 -0800, Alan Murrell <alanm@NOSPAMvcn.bc.ca> wrote:
>Greetings!
>
>I have another question for you all:  how do you set up a SCSI device
>*after* installation?
>
>Again, Thanx in advance!
	What exactly do you mean by this? What type of devices are you
asking about, Hard Drives? Cd-roms/worms/rw? Scsi Tape?
	Being a Scsi user I will explain the scsi thing based on the
catagories of devices
Hard Drives:
	Hard Drives use device names of /dev/sdDP where D stands for
Device and P stands for partition. if you have 3 Scsi Hard drives.
REGUARDLESS of device number.. the lowest hard drive is /dev/sda, the
next is sdb and the last is sdc. Zip,jaz drives and Iomega Bernoulli boxes
are also considered hard drives by linux.
	If your first hard drive only has one partition it is
/dev/sda1 for that partition.
	Installation of the media is similar to IDE. First you use
fdisk or cfdisk (its a nicer looking fdisk btw). to define your
partions like you would IDE. Instead of saying fdisk /dev/hda you would type
fdisk /dev/sda instead.
	You format your partions with mke2fs  the same way you do with
IDE. which is mke2fs -c /dev/sda1 the '-c' means find bad blocks and
remove them from active use.
Cd devices (ROM, RW, R etc.
	Cdroms can get a bit tricky as linux has several names for
them. I will approach the SCSI CD-ROM system as thats what I have.
Scsi cdroms have device names of /dev/srD where the D referes to the
Drive on the  Scsi Buss. NOTE like the  Hard Drives this does not
refer to the Scsi id. it means which  drive  in the orde from  first
to last. if you have two cdroms using ids 4 and 5 and wanted to read
the first one you select /dev/sr0 for the second it is /dev/sr0
To mount these you need the iso9660 file system. a Scsi cdrom is
mounted like an IDE unit. to mount the first drive under /cdrom type
mount /dev/sr0 /cdrom -t iso9660 ro

Scsi Tapes
	Heres where even I run into a brick wall! device names are
/dev/stD (the D stands for which Scsi tape unit). Scsi tapes can be
tricky as there is many styles of how to handle the advanced features
of a tape. I have a wangtek 5150ES therefore I will speak of my drive.
Scsi Tape units have two names. the /dev/st0 and /dev/nst0. Since I
only have one tape drive its 0, if I had two the would be st0 and st1.
	the /dev/st0 device rewinds a tape automatically when you are
done writing/reading it. the /dev/nst0 device  does no such thing and
requires one to use mt  to rewind the volume after one is done using
it. Using mt allows one to add multiple volumes to a tape. The
treachery is this. How does one low level format a tape cartridge?
The best answer is. YOU DON'T! (I am unsure about the travans, dds,4mm
or 8mm units however). the mt program has very little documenation but
has tons of modes for densitys and options. the ftape ftmt program is
a better looking version of mt (you can use the ftmt for your basics
btw just as you can use mt for most of your floppy tape use also.
	Getting your devices density  and configs right can be tricky
but usually one can  use it right out of the box for a backup
(advanced features are drive specific)
under scsi to initalize (erase) a tape one types
st -f /dev/st0 erase

to backup your /home directory(s) to tape type
I am going to use the older tar method as tar 1.13 skips some of this
stuff
cd / # go to the root
tar -cvf /dev/st0 home  #backup home with verbose display of results
and the outputfile is /dev/st0 (rewinding tape drive)
to intall the files into say /new instead of /home do this
mkdir /new
cd /new
tar -xvPf /dev/st0 home
your tape files are now copied to /new

Scsi Flopicals
	I know nothing of these
Scsi Ls120 drives
	Ditto, possibly uses the /dev/sd devices
Scsi Floppy Drives
	I don't have a scsi floppy drive to try out. possibly
/dev/sd devices
Scsi Scanners
	I don't know anything about scanners as I never used one.
Scsi Printers
	See Scsi Scanners.

	If any of this answers any or all of your questions I would
like to know.



--

			B'ichela

In article <slrn8oou5s.3d0.mdalene@pinkrose.ctol.net>,
mdalene@pinkrose.ctol.net (B'ichela) wrote:
> 	What exactly do you mean by this? What type of devices are you

Okay, you're right, I should have been a tad more specific.  I have a Zip
drive attached to a SCSI card that I would like to be able to access.
However, my SCSI card does not seem to be able to be recognized.  Here is
the info for the card, which i got from the Win95 info:

Acculogic ISApport/10 adapter SYM53406

Someone suggested I try using the NRC53c406a.O chip setup, and considering
the similarity in "ID numbers", I would like to tryt hat.  However, now
that my system is set up, I do not know how to go back and get my system
to recognize, or set up, my SCSI card.

--
Alan Murrell <alanm@vcn.bc.ca> ICQ: 1147392
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.geocities.com/Area51/Comet/1777

Try the following as root.

modprobe NCR53c406a

If that causes it to recognize your drive then you just to to put that
somwhere in your startup scripts.

Perry


On Sat, 05 Aug 2000 15:37:31 -0800,
Alan Murrell <alanm@vcn.bc.ca> wrote:
>In article <slrn8oou5s.3d0.mdalene@pinkrose.ctol.net>,
>mdalene@pinkrose.ctol.net (B'ichela) wrote:
>> 	What exactly do you mean by this? What type of devices are you
>
>Okay, you're right, I should have been a tad more specific.  I have a Zip
>drive attached to a SCSI card that I would like to be able to access.
>However, my SCSI card does not seem to be able to be recognized.  Here is
>the info for the card, which i got from the Win95 info:
>
>Acculogic ISApport/10 adapter SYM53406
>
>Someone suggested I try using the NRC53c406a.O chip setup, and considering
>the similarity in "ID numbers", I would like to tryt hat.  However, now
>that my system is set up, I do not know how to go back and get my system
>to recognize, or set up, my SCSI card.
>
>--
>Alan Murrell <alanm@vcn.bc.ca> ICQ: 1147392
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>http://www.geocities.com/Area51/Comet/1777
>

In article
<F2E37122B2C0E309.3F578D0D2D863CA6.5E76B05915C3CE2D@lp.airnews.net>,
perrypip@my-deja.com (Perry Pip) wrote:
> Try the following as root.
>
> modprobe NCR53c406a

Worked like a charm!  fdisk even finds it no problem, but not I just got
to find a way to mount it.  Guess I'll have to doa little editing of my
/dev/etc file...

--
Alan Murrell <alanm@vcn.bc.ca> ICQ: 1147392
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.geocities.com/Area51/Comet/1777

In article <539j5.20725$47.320575@news.bc.tac.net>, "Alan Murrell"
<alanmNOSPAM@vcn.bc.ca> wrote:
> In article
> <F2E37122B2C0E309.3F578D0D2D863CA6.5E76B05915C3CE2D@lp.airnews.net>,
> perrypip@my-deja.com (Perry Pip) wrote:
>> Try the following as root.
>>
>> modprobe NCR53c406a
>
> Worked like a charm!  fdisk even finds it no problem, but not I just got
> to find a way to mount it.  Guess I'll have to doa little editing of my
> /dev/etc file...

Oooops, that should have been /dev/fstab, of course :-)

--
Alan Murrell <alanm@vcn.bc.ca>  ICQ: 1147394
http://www.geocities.com/Area51/Comet/1777

Remove the NOSPAM to reply

Well you seem to have done the hard bit. As it is an SCSI zip you will most
probably refer to it as dev/sda4 in your fstab. Don't forget to creat that
mount point though.

Karl

Alan Murrell wrote:

> In article <539j5.20725$47.320575@news.bc.tac.net>, "Alan Murrell"
> <alanmNOSPAM@vcn.bc.ca> wrote:
> > In article
> > <F2E37122B2C0E309.3F578D0D2D863CA6.5E76B05915C3CE2D@lp.airnews.net>,
> > perrypip@my-deja.com (Perry Pip) wrote:
> >> Try the following as root.
> >>
> >> modprobe NCR53c406a
> >
> > Worked like a charm!  fdisk even finds it no problem, but not I just got
> > to find a way to mount it.  Guess I'll have to doa little editing of my
> > /dev/etc file...
>
> Oooops, that should have been /dev/fstab, of course :-)
>

maybe /etc/fstab?

Colin Day