DEC ALPHA

Ronald Maggio r.v.maggio at worldnet.att.net
Tue Feb 19 08:49:44 EST 2002


----- Original Message -----
From: "Darin Perusich" <Darin.Perusich at cognigencorp.com>
To: <nflug at nflug.org>
Sent: Monday, February 18, 2002 8:57 AM
Subject: Re: DEC ALPHA


> does redhat's diskdruid see all of you hard drives? if not does fdisk?

Yes diskdruid at first did see the all the drives, but could not work with
them
do to incorrect disklables. Diskdruid's popup screen stated that I needed to
go into fdisk to correct this matter. Which I did. The only problem I saw
was that
no where in the installation guide did it state what kind of BSD disklables
I should
set in fdisk. The default was (Unknown) I left it at that and set the letter
to (a) on all the
drives to provide the initial unallocated space as stated in the manual, so
that diskdruid
as I understood it would be able to allocate it. I also started the
partitions at cylinder 2 as
stated for workstations/servers. Diskdruid did see all the drives before and
after this operation,
but after this operation I could now be able to address (access) them
through diskdruid.


> as long as you can see all the drives from the installer you should be
> in a good position. i'll cover NOT being able to see the drives in a
> second. in diskdruid delete any Unknown filesystem types and then set
> the drives how you want them.

All well and good to set the (Unknown)s to Linux native in diskdruid.
My only problem is to figure out what to put where! I have the following
disks to use for this system. sda=528mb, sdb=4.3gig, sdc=1.010gig, sdd=426mb
and sde=426mb.
sda is in desktop not drive tower. All pinned in order 0 through 4 and
terminated.
Now sda is way to small to put / but large enough for boot, but as Bob Meyer
tolled
me that I should just go ahead and install everything on the 4.3gig drive
sdb=scsi 1.
So if I did it that way how will I be able to access the other drives in
order to use them?
ie: Install programs & storage? Raid software? How?


>setting up the drives is personal preference, there are really no right or
wrong ways to setup
> filesystems, other they one big filesystem. with that said you should at
> least setup /, /usr, /var, and swap, anything else is debatable.
> if diskdruid and/or fdisk DO NOT see all your drives you most likely
> have a termination problem, or a bad drive. when you boot up the machine
> get into the bios/eeprom what ever you want to call it. there should be
> a section where you can view the hardware, if you're using the DEC
> console type disk to probe the disk drives, or test to probe all
> hardware. any termination issues should come up here.

Did that and all showed up.

>
<---------------------------------snip--------------------------------------
-------------------------------->
> > OK the GUI did not take care of this and I had to use fdisk to set BSD
> > disklables. What should I name the partition type? The BSD disklable
program
> > uses a default partition type of (Unknown) I set the letter of each
drive to
> > (a) and it states in the installation guide "To provide the initial
> > unallocated space, you will need to start the partitions at cylinder 2.
If
> > you do a workstation or server class installation" I'm installing a
> > workstation class system.
>
> fstab(5) is the filesystem table file, it contains info on how to mount
> filesytems.
>
> > What is (fstab)?
>
>
> --
> Darin Perusich
> Unix Systems Administrator
> Cognigen Corp.
> darinper at cognigencorp.com
>



More information about the nflug mailing list