| Summary: | initscripts-9.78 or systemd-236 doesn't let mandrake_everytime update /etc/issue, so TTYs show wrong kernel version (and nothing about kernel version at all in recent cauldron installs) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marja Van Waes <marja11> |
| Component: | RPM Packages | Assignee: | Base system maintainers <basesystem> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | ngompa13, westel |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | initscripts-9.78-5.mga7, systemd-236-3.mga7 | CVE: | |
| Status comment: | |||
|
Description
Marja Van Waes
2018-01-09 14:41:55 CET
On the cauldron that I use for production, and where I updated initscripts and systemd rather late, the time stamp of /etc/issue matches: jan 07 20:07:14 localhost kernel: audit: type=1130 audit(1515352034.858:41): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mandriva-everytime comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' It is confusing to have a unit mandriva-everytime, while it's /etc/rc.d/init.d/mandrake_everytime Anyway, it seems systemd could be the culprit, instead of initscripts. There's nothing about a mandriva-everytime unit in my logs for more recent boots Source RPM:
initscripts-9.78-5.mga7 =>
initscripts-9.78-5.mga7, systemd-236-3.mga7 I wish I'd understand this part from /etc/rc.d/init.d/mandrake_everytime :
=========================================================================
# /etc/issue and /etc/issue.net stuff
[ -f /etc/sysconfig/system ] && source /etc/sysconfig/system
[ -f /etc/sysconfig/msec ] && source /etc/sysconfig/msec
[ -z "$SECURE_LEVEL" ] && SECURE_LEVEL=3
[ -f /etc/sysconfig/init ] && source /etc/sysconfig/init
if [ $SECURE_LEVEL -lt 4 ]; then
[ -z "$REWRITEISSUE" ] && REWRITEISSUE=rewrite
if [ $SECURE_LEVEL -lt 3 ]; then
[ -z "$REWRITEISSUENET" ] && REWRITEISSUENET=rewrite
fi
fi
========================================================================
Anyway, echo $SECURE_LEVEL returns nothing here, only echo $SECURITY returns something:
[root@localhost marja]# echo $SECURITY
3
[root@localhost marja]# echo $SECURE_LEVEL
[root@localhost marja]#
just to advise same here tty2 displays: kernel 4.14.10-desktop-1.mga7 on a x86_64 / tty2 "rpm -qa | sort | grep ^kernel" returns: kernel-desktop-4.14.13-1.mga7-1-1.mga7 kernel-desktop-4.14.14-1.mga7-1-1.mga7 kernel-desktop-4.14.14-2.mga7-1-1.mga7 kernel-desktop-4.14.15-1.mga7-1-1.mga7 kernel-desktop-devel-4.14.13-1.mga7-1-1.mga7 kernel-desktop-devel-4.14.14-1.mga7-1-1.mga7 kernel-desktop-devel-4.14.14-2.mga7-1-1.mga7 kernel-desktop-devel-4.14.15-1.mga7-1-1.mga7 kernel-desktop-devel-latest-4.14.15-1.mga7 kernel-desktop-latest-4.14.15-1.mga7 kernel-firmware-20170531-1.mga6 kernel-firmware-nonfree-20171220-1.mga7.nonfree kernel-userspace-headers-4.14.15-1.mga7 mageia welcome displays: kernel 4.14.15-desktop-1.mga7 CC:
(none) =>
westel Note that there is no message about kernel version at all in recent cauldron installs. The /etc/issue file doesn't exist. Summary:
initscripts-9.78 or systemd-236 doesn't let mandrake_everytime update /etc/issue, so TTYs show wrong kernel version =>
initscripts-9.78 or systemd-236 doesn't let mandrake_everytime update /etc/issue, so TTYs show wrong kernel version (and nothing about kernel version at all in recent cauldron installs) This got fixed some time ago. Thanks to whoever fixed it! Status:
NEW =>
RESOLVED |