Bug 1577598
Summary: | /etc/issue does not contain the proper information | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matt Daveson <reportbug> |
Component: | fedora-release | Assignee: | Mohan Boddu <mboddu> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | dennis, jdisnard, jkeating, kellin, kevin, mboddu, pbrobinson, reportbug, sgallagh, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-13 15:34:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matt Daveson
2018-05-13 12:08:56 UTC
Could you perhaps provide some information about what you think it *should* be displaying? Because this bug report is not useful as-is. Maybe Fedora 28 Workstation or something like that, I don't know... /etc/issue is used by agetty to determine what the vty/tty/serial login prompts look like. From 'man agetty': S or S{VARIABLE} Insert the VARIABLE data from /etc/os-release. If this file does not exist then fall back to /usr/lib/os-release. If the VARIABLE argument is not specified, then use PRETTY_NAME from the file or the system name (see \s). This escape code allows to keep /etc/issue distribution and release inde‐ pendent. Note that \S{ANSI_COLOR} is converted to the real terminal escape sequence. So, the /etc/issue we ship results in agetty displaying something like: Fedora 29 (Workstation Edition) Kernel 4.17.0-0.rc4.git2.1.fc29.x86_64 on a x86_64 (tty1) (or server edition, or cloud, etc) which seems completely reasonable. Perhaps you are looking for some information that is in /etc/os-release? |