Very Computer

Hi,

Is anyone else having trouble with Solaris 5.7 kernel patch 106541-04?

When I install it (on an Ultra 5 with a * Solaris 5.7 installation) I
get fatal INIT errors on reboot - 'Cannot access /var/adm/utmp and utmpx'

106541-03 works fine.

Regards,
Alan.

Yes, I have the same problem - I can boot from CD, mount the root
partition, and everything looks OK, but the version of the kernel on the
disk just doesn't want to play.

I've tried deleting and recreating the UTMP files, and that doesn't
help.  The next step is to go back to a clean install and start again,
which I don't appreciate....!

Any other ideas?

Paul.

--
+---------------------------------------------------------+
|Paul J Murphy,  Head of I.T., Gemini Research Ltd        |
|162 Science Park, Cambridge CB4 4GH - Tel. 01223 435305  |
+---------------------------------------------------------+

Quote:>> Hi,
>> Is anyone else having trouble with Solaris 5.7 kernel patch 106541-04?
>> When I install it (on an Ultra 5 with a * Solaris 5.7 installation) I
>> get fatal INIT errors on reboot - 'Cannot access /var/adm/utmp and utmpx'
>> 106541-03 works fine.

 PM-> Yes, I have the same problem - I can boot from CD, mount the root
 PM-> partition, and everything looks OK, but the version of the kernel on the
 PM-> disk just doesn't want to play.

 PM-> I've tried deleting and recreating the UTMP files, and that doesn't
 PM-> help.  The next step is to go back to a clean install and start again,
 PM-> which I don't appreciate....!

 PM-> Any other ideas?

 PM-> Paul.

Have a look at the "postpatch" script inside the 106541-04
patch directory.  It has to be ran before you reboot after
the patch.  Just boot from CD as before, mount the / partition
appropriately and then run the "postpatch" (with the correct
$ROOTDIR set of course).

Best,
HenSiong

Quote:> Have a look at the "postpatch" script inside the 106541-04
> patch directory.  It has to be ran before you reboot after
> the patch.  Just boot from CD as before, mount the / partition
> appropriately and then run the "postpatch" (with the correct
> $ROOTDIR set of course).

> Best,
> HenSiong

This works for me - our system is back up and running.

It appears that the "postpatch" was not run automatically, which may be
because the patch was installed using Casper's "fastpatch" program.
Some rethinking of our patch installation routine may be required now...

Thanks,

Paul.

Paul.Murphy.vcf < 1K Download

[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]

I believe this happens when the "sysmsg" driver is missing; (at least, it
happened when I installed MU2 on my second bootable partition when running
from the second one a few days ago).

You need to make sure /dev/sysmsg and the thing it points to in
/devices/pseudo both exist; there also nees to be a name_to_major
entry.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Quote:> Hi,

> Is anyone else having trouble with Solaris 5.7 kernel patch 106541-04?

> When I install it (on an Ultra 5 with a * Solaris 5.7 installation) I
> get fatal INIT errors on reboot - 'Cannot access /var/adm/utmp and utmpx'

> 106541-03 works fine.

After applying this patch and rebooting, my su command core dumps.
Luckily my sudo command works.  I suggest everyone wait for the next
revision of this patch...this one is not ready for prime time.

-Randy

I noticed yesterday that 106541-05 was made available on 6/11...

Quote:> I noticed yesterday that 106541-05 was made available on 6/11...

I installed the new patch 106541-05 on my system and su is still broken.  If
I use the su command while
i'm logged in as root, it works fine though...

-Randy

su works fine for me with 106541-05, and has worked fine with 106541-04.
I think your problem lies elsewhere. It's probably not setuid root,
hence it can't be used by non-root user. And it could be that you
have the wrong version in your path.

--
 .-.   .-.    Life is a *ly transmitted disease.
(_  \ /  _)

It has nothing to do with setuid permissions.  My problem with su appears to
be PAM related and
i'm using a custom PAM module ahead of the regular unix pam module.  I
wonder what changes
where put in this patch to the PAM interface.  Anyway I have a workaround
for the moment...

-Randy