Jack Schwartz wrote: > On 07/30/09 13:15, Shawn Walker wrote: >> That would assuage my fears greatly. There's really no protection in >> place to keep SVR4 packages from butchering files already on the system. > I just confirmed with an IPS team member that if an SVR4 package > contains only files which are orthogonal to those installed via IPS, the > SVR4-packaged files can co-exist with the other files without issues. > > So, if the files themselves are good, they should work. > > Bad files can come in any kind of package, including IPS, so this isn't > a reason to exclude SVR4 packages. >> >> However, it still leaves users with the issue that they may be stuck >> with a driver that won't be installable regardless of whether or not >> the check succeeds because of the architectural changes that were made >> in the OpenSolaris 200x releases. > What architectural changes are you referring to?
The non-existence of most of the contents of /usr/ucb, which may cause some driver setup scripts to fail. The lack of /usr/xpg6 by default? In short, some programs have been moved around (see /usr/has/bin), some programs are not there by default, and some are just gone altogether. Yes, all of these cases are likely 'bad drivers', but I think it's reasonable to tell the user that not all driver packages may be compatible. Cheers, -- Shawn Walker
