At 11:53 AM +0100 3/25/02, Pieter Coolsma wrote:
>Can somebody tell me how to read this info? What does it mean?

Hi Pieter :-)

>  Is ok that .mk.conf is missing?

mk.conf is a file to tell "make" how to react when you're building 
stuff from source. There are default behaviors, and you would use 
/etc/mk.conf to override those behaviors. It's perfectly fine to have 
either no mk.conf or a blank one on current systems.

><begin>
>
>Checking the /etc/master.passwd file:
>Login toor is off but still has a valid shell (/bin/sh)

This is normal...toor is a safety net in case root is screwy for some 
reason. I don't know anyone who has ever needed to use it, but it's 
there by default.

>
>Checking setuid files and devices:
>
>Checking disk ownership and permissions.
>Disk /dev/cd0a is user root, group operator, permissions brw-------.
>Disk /dev/cd0c is user root, group operator, permissions brw-------.
>Disk /dev/cd1a is user root, group operator, permissions brw-------.
>Disk /dev/cd1c is user root, group operator, permissions brw-------.

On my alpha, these are all brw-r-----.

>Disk /dev/rcd0a is user root, group operator, permissions crw-------.
>Disk /dev/rcd0c is user root, group operator, permissions crw-------.
>Disk /dev/rcd1a is user root, group operator, permissions crw-------.
>Disk /dev/rcd1c is user root, group operator, permissions crw-------.

On my alpha, these are all crw-r-----.

>Disk /dev/sd0b is user root, group wheel, permissions brw-r-----.

On my alpha, this is root:operator

>Checking special files and directories.
>usr/pkgsrc:
>	permissions (0755, 0775)
>missing: ./etc/mk.conf

It's only complaining because it has a list of files to check the 
permissions on, and mk.conf is one of them. So it can't check the 
permissions if the file is missing.

HTH
Mike
-- 
Bikers don't *DO* taglines.