Project

General

Profile

Bug #2138

OpenIndiana prestable 151a2 reports 151a1 in uname -v

Added by Lou Picciano over 7 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-02-17
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

OpenIndiana prestable 151a2 reports 151a1 in uname -v

Noting that a zone installed on latest prestable is correctly reporting oi_151a2 in the login banner...
but uname -v is still reporting oi_151a1

Seems trivial, but may lead to unexpected results?

History

#1

Updated by Richard PALO over 7 years ago

? not for me

richard@shuttleX:~$ grep illumos /var/adm/messages
...
Feb 17 05:40:21 shuttleX genunix: [ID 198659 kern.notice] ^MOpenIndiana Build oi_151a2 32-bit (illumos fc320b2833d3)
richard@shuttleX:~$ uname -av
SunOS shuttleX 5.11 oi_151a2 i86pc i386 i86pc

did you do a beadm list to see if you're rebooted and that your oi_151a2 environement is active?

richard@shuttleX:~$ beadm list
BE          Active Mountpoint Space Policy Created
oi_151.1.2  NR     /          7,73G static 2012-02-14 07:25
oi_151a     -      -          13,6M static 2011-10-29 11:20
openindiana -      -          22,8M static 2011-10-12 07:44

#2

Updated by Lou Picciano over 7 years ago

This is on a zone, though.... no BEs, of course.

No, my point was that zlogin on the zone reports:
OpenIndiana (powered by illumos) SunOS 5.11 oi_151a2 January 2012
which seems reasonable, as this zone was just installed (17 Feb) from latest /prestable

while uname -zv (on the zone) reports:
SunOS build 5.11 oi_151a1 i86pc i386 i86pc

The global zone is still booted to 151a1 at this point - so, perhaps this is just expected mileage from uname in a zone; it's reporting on the kernel?

#3

Updated by Jon Tibble over 7 years ago

  • Status changed from New to Rejected

Yes, this isn't a bug. You should keep your zones in line with the global zone or unexpected things may happen (that will also get rejected ENOTABUG). Zones share the kernel so it is correctly reporting what is going on.

Also available in: Atom PDF