-----BEGIN PGP SIGNED MESSAGE-----


  I did something bad to my Solaris boot disk. Eventually, I got to the point
where /sbin/init said it couldn't find /etc/lib/ld.so.1. BAD. No CDROM at
home, and I nuked my Solaris netboot image for the disk space.
  Another attached drive has NetBSD/Sparc on it. I mounted, everything looked
fine, only it wasn't. 
  I reloaded the CD today, netbooted Solaris, and I find... /etc/lib/ld.so.1
had perms... "----------".
  When I fsck'ed the drive I got lots of complaints about bad non-zero ACLs.
Is there someway we can teach our fsck and/or ffs not to stomp on the Solaris
parts?

  [My original problem was a messed up /etc/driver_classes and
/etc/driver_aliases. If I needed any convincing that SVR4 was a bad thing, I
have plenty of evidence now. /sbin/init is dynamically linked on
Solaris. DUH.] 

   :!mcr!:            |  Sandelman Software Works Corporation, Ottawa, ON  
   Michael Richardson |Network and security consulting and contract programming
 Personal: mcr@sandelman.ottawa.on.ca. PGP key available.
 Corporate: sales@sandelman.ottawa.on.ca. 



   

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBNQ3RLtiXVu0RiA21AQGdnAMAivvHV6Xspv1VRLfMKSAqpTuN9k0+V4c8
6OVgrejFzXttYXA5dWh2BmxP9yPIsaWlHYNnsiayBZX5+dXJ3LsWeis68vI2ttGf
mmE7SY84KKetutnnJfV+rNeHwCAlVPzm
=O8zA
-----END PGP SIGNATURE-----