Alan Coopersmith gave some interesting info just now: some (not all) files appeared in /var/pkg/lost+found/.

The missing man files weren't there, but most (80 %?) of the missing /usr/local tree was.

I had no idea that dir was there. There you go, manuals should be read.
i e rtfm not waefrtfm.

On 2012-05-07 16:33, [email protected] wrote:
Message: 2 Date: Mon, 07 May 2012 15:31:19 +0200 From: "Hans J. Albertsson" <[email protected]> To: [email protected] Subject: Re: [OpenIndiana-discuss] Massive numbers of man files, missing on 151a4 Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed No, that's not it: I thought of that possibility, but my /usr/local is just another directory /usr. And where did the man files go?? I'm actually thinking I would have liked to be able to trace what updatemanager did, after the fact. Still, I now know I must do a snapshot at every step of any fishy pkg stuff. And I've got the files back, and things work. Next time I'll be more observant. On 2012-05-07 14:50, [email protected] wrote:
>  Message: 5
>  Date: Mon, 07 May 2012 07:21:32 -0400
>  From: James Carlson<[email protected]>
>  To: Discussion list for OpenIndiana
>    <[email protected]>
>  Subject: Re: [OpenIndiana-discuss] Massive numbers of man files,
>    missing on 151a4
>  Message-ID:<[email protected]>
>  Content-Type: text/plain; charset=ISO-8859-1
>
>  Hans J. Albertsson wrote:
>>  >    I  managed to determine (ocular inspection of "ls" in several 
snapshots)
>>  >    that the only files missing were about 1200 man pages in man1, and the
>>  >    entire /usr/local tree.
>> > >> > And I think it must have happened as I removed the sfe version of
>>  >    imagemagick.
>  One way I've seen this sort of thing happen is when an administrator
>  uses a symlink for a common directory (such as /usr/local), and a
>  package delivers a directory entry for that same path.  The packaging
>  system will happily blow the symlink away.
>
>  If that's what you've been doing, I suggest using mounts instead of
>  symlinks.  The simplest thing to do is to make /usr/local (or whatever
>  is being symlink'd) be a separate zfs file system.  Alternatively, if
>  separate file systems are not your taste for some reason, consider using
>  a lofs mount.  (Of course, getting that mount in place at boot time may
>     be slightly tougher to do on a modern Open Indiana system, as zfs works
>  outside of the /etc/vfstab scheme.)
>
>  -- James Carlson 42.703N 71.076W<[email protected]>

_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to