🚀 go-pugleaf

Hi,

	Well got the ram working great (thanks again), but unfortunetly my
Alpha (multia/udb) seems to have bit the dust and I wanted to be able to
access the files on its drives under my decstation (Ultrix 4.4) until I
could obtain another alpha. The decstation boots up fine and happy with
the temrination and scsi hardware fine. Atleast thats what cnfg 3 tells
me: 

KN02-CA V2.0m   (PC: 0x801c0b0, SP: 0xffffde70)
[SNIP]
            DEV   PID              VID     REV  SCSI DEV
            ===== ================ ======= ==== ========
            rz0   CD-ROM XM-5701TA TOSHIBA 0167 CD-ROM
            rz2   RZ25     (C) DEC DEC     0700 DIR
            rz5   FIREBALL ST3.2S  QUANTUM 0F0C DIR
            rz6   ST43400N         SEAGATE 1028 DIR
[SNIP]

	[A side question, is it possible to upgrade the firmware (KN02-CA
V2.0m) to a newer version or is the firmware hardware related?]

	My main problem happens when I try to mount the hard drives/cdrom
or boot from the cdrom. 

	Issuing 'boot 3/rz0/vmunix' at the console just reads the cd and
then sits until I ^C it. Is this the correct syntax? The cdrom is a
toshiba and it does boot ufs cd's (I used it to boot Digital Unix on my
multia). Are Ultrix/DECstations that picky when it comes to cdroms?

	When I mount an ISO9660 cd like so:

mount -t cdfs -o noversion -r /dev/rz0c /cdrom

	I get:

cdfs_mount: Unknown descriptor type
cdfs_mount: cannot mount /dev/rz0c on /cdrom: Invalid argument

	Even doing:

mount -t cdfs -r -o ro,defperm,noversion /dev/rz0c /cdrom 

	I get the same error message.

	
	The CDFS option is set in the config file that was used to build
the current kernel image and Ultrix does see the cdrom (It also sees the
quatum but not the segate, which I think I know why).

	On the other hand when I try to mount a UFS cd [Doc cds] like so: 

mount -t ufs -r /dev/rz0c /cdrom

	I get:

ufs_mount: /dev/rz0c on /cdrom: Invalid argument                              

	Those were just the cds, when I go to mount a UFS drive like so:

mount /dev/rz5a /mnt

	Again, I get:

ufs_mount: fs /dev/rz5a not cleaned -- please fsck
ufs_mount: /dev/rz5a on /mnt: Invalid Argument

	So then I force mount it like so: mount -o force /dev/rz0c /mnt

	And I get:

Warning, /dev/rz5a has exceeded 1 mounts threshold, fsck(8) is advised

	This atleast mounts the file system and lets me read *some* of the
files on the drive. Df shows the following which is really wierd

/dev/rz5a -1134396  199303 0 0% /mnt, it is a 3.2gig drive and there

	There was plenty of space on it when I last used it under Digital
Unix, also the disks were unmounted cleanly. They are not AdvFS, just
plain UFS. 

	Getting back to cnfg showing the seagate as rz6 and Ultrix not
seeing it, I believe I have to added rz6 to the kernel conf file, but when
I was looking through it ealier today I notice tp? was designated as rz6,
is it safe to put the seagate in as rz6 and the tp? as rz7 (I have a tape
drive). 

	My final question is about the "phsysmem" option in the kernel
configuration file. Previously the machine had 8megs of ram with 8 megs of
swap. The former maintainer set the phsysmem value to 16. The machine now
has 24megs of ram in addition to the 8 for swap. Eventually the machine
will get 40 megs of ram. I'm wondering it is safe to set phsysmem to 48? I
think it is since this value is software only (hardware stops at 40). 
Whats the recomendation on doing this? I apologize for the lenght of this
email, just wanted to include as much helpful detail as possible. Thanks
for any advice, help or assistance. Will summarize.

-
Parris Wood
 pwood@wilma.widomaker.com.
 pawood@vt.edu