after Upgrade to 4.0B : changed owner for Directory, etc.

From: B. Boersch-Pulm <acp30_at_rs1.rrz.Uni-Koeln.DE>
Date: Thu, 20 Nov 1997 16:49:20 +0100

Hallo,

here they are, the next two questions :

1. during my system upgrade the owner of a user Directory (my own) has
        change to wnn

# ls -l /usr/users
total 21087
drwxr-xr-x 31 wnn users 3584 Nov 19 13:05 bbp

# cd /usr/users/bbp
#ls -la
-rw------- 1 wnn users 368 Nov 6 09:17 .Xauthority
-rw-r--r-- 1 wnn users 97 Jul 3 17:21 .Xdefaults
-rw-r--r-- 1 wnn users 32 Jul 3 17:21 .Xdefaults-org
.
.
.
There is an entry in the passwd file :

wnn:Nologin:12:1:Wnn System Account:/tmp:/bin/sh


chown bbp doesn't work, login seems to be o.k.


what does this mean and how can I change it.

2. Question

My Alpha 600 5/266 has the following messages in the boot sequence :
. .
. .
                                        isp0 at pci1000 slot 1
                                        isp0: QLOGIC ISP1020
                                        cam_logger: CAM_ERROR packet
                                        cam_logger: bus 0
                                        isp_probe
                                        NVRAM parameters invalid, using
                                                  driver
                                         _Fast10 defaults

the same one for isp1 :

                                        isp1 at pci1000 slot 2
                                        isp1: QLOGIC ISP1020
                                        cam_logger: CAM_ERROR packet
                                        cam_logger: bus 1
                                        isp_probe
                                        NVRAM parameters invalid, using
                                                driver
                                         _Fast10 defaults

the error messages about isp I know from DU 3.2C
(when I asked a technician from Digital he told me it doesn't matter
and it seemed so.)

the one about the cam_logger is new and for one time the machine stopped
booting at this position.

After reboot the error message is still there but the boot process
continued huhhhh.

Thanks for all hints


Birgitt Boersch-Pulm
Received on Thu Nov 20 1997 - 17:12:51 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT