I had one conversation with a user who upgraded from phase 0.5 to 1
(using onu) whose /etc/nwam/llp did not get upgraded. The bits were
post-IPS integration. The user was running OpenSolaris in a VirtualBox
and had a static IP configured in /etc/nwam/llp and also had NIS
configured. After upgrade, no User NCP was created. A User location was
created and selected on upgrade.

In my test with BFU on Nevada, /etc/nwam/llp was upgraded to the User
NCP. I'll try to find/build such IPS bits on Monday and test. However,
in the meantime, if anyone has such bits, please send me a pointer.

Any ideas for the cause of the problem?

Assuming you're speaking of the system/network package in the ON gate,
the issue is probably that no package previously claimed ownership of
/etc/nwam (which was a package bug).

As a result, when you did the upgrade, the package system salvaged
what was there (and moved it to lost+found; see below) since it was
unexpected.

If I'm right, you'll find the missing files in /var/pkg/lost+found/*
I just tried to recreate this issue, and I am not able to do so. There
is no /var/pkg/lost+found directory, hence no lost files. By the way,
this has never been an issue during our testing with IPS repositories
and image-update.

Did you test an image-update from b133 or earlier with something that has /etc/nwam/llp to 135+ bits that have /etc/nwam? That's the only place I'd expect you to see this issue.
Rishi S. has confirmed with me that he was able to image-update from build 128 to on-nightly dated March 8 and his /etc/nwam/llp file with a static IP was upgraded to the User NCP as expected. /var/pkg/lost+found does not have the /etc/nwam/llp file.

Anurag

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to