Bug 633421
Summary: | [6.1 FEAT] Tool to safety start getty through init - inittab/startup | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | IBM Bug Proxy <bugproxy> |
Component: | initscripts | Assignee: | initscripts Maintenance Team <initscripts-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons |
Severity: | urgent | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | brueckner, gmuelas, jjarvis, nobody+PNT0273897, notting, pknirsch, sbest |
Target Milestone: | alpha | Keywords: | FutureFeature |
Target Release: | 6.1 | ||
Hardware: | s390x | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-24 16:18:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 538808, 580566 |
Description
IBM Bug Proxy
2010-09-13 18:12:27 UTC
Hello John, this feature is requesting to integrate ttyrun in an startup job. Unfortunately through the mirroring this information got lost. I have updated the component here directly. This needs integrated into the core code; we do not need to ship a separate program just for handling s390 gettys. Closing RFE as WONTFIX in its current form. Note that if you have multiple gettys on the same device due to a getting running on /dev/console... you've misconfigured your system. We don't set it up that way. Also, passing the console type via kernel parameters is a horrible interface. ------- Comment From brueckner.ibm.com 2010-09-27 10:21 EDT------- Hi Bill, thanks for your feedback, please find my answers below. (In reply to comment #7) > Note that if you have multiple gettys on the same device due to a getting > running on /dev/console... you've misconfigured your system. That's right. But the ttyrun tool is not intented to run multiple getty programs on the same terminal. It helps admin's to preconfigure terminal devices even if the terminals might not be currently active. Originally, ttyrun has been developed for HVC terminal devices which can be activated through a kernel parameter. As terminal devices are statically allocated, all terminal (minor devices) are created. > We don't set it up that way. Hmm.... even in RHEL5?! > Also, passing the console type via kernel parameters is a horrible interface. Well, that's the way it works. The last console statement designates the preferred console which is then visible as /dev/console. Of course, /dev/console is a associated to a terminal devices (if the preferred console driver has one). (In reply to comment #5) > ------- Comment From brueckner.ibm.com 2010-09-27 10:21 EDT------- > Hi Bill, > > thanks for your feedback, please find my answers below. > > (In reply to comment #7) > > Note that if you have multiple gettys on the same device due to a getting > > running on /dev/console... you've misconfigured your system. > > That's right. But the ttyrun tool is not intented to run multiple getty > programs on the same terminal. No, my point is you've created a tool that appears to have a motivation of only being useful to fix a system that the admin has broken. > > We don't set it up that way. > Hmm.... even in RHEL5?! We do not ever set up the machines to run gettys on both /dev/console and the backing device of /dev/console, no. ------- Comment From brueckner.ibm.com 2010-09-27 14:21 EDT-------
Hi Bill,
> > (In reply to comment #7)
> > > Note that if you have multiple gettys on the same device due to a getting
> > > running on /dev/console... you've misconfigured your system.
> >
> > That's right. But the ttyrun tool is not intented to run multiple getty
> > programs on the same terminal.
> No, my point is you've created a tool that appears to have a motivation of only
> being useful to fix a system that the admin has broken.
Sorry for that misunderstanding. Let me describe it in more detail:
With RHEL6.0, we introduced a new kernel device driver for System z that
provides HVC terminal devices reusing the hypervisor console terminal
device driver. The kernel parameter specifies the number of active HVC terminal
devices. The point is that the tty core layer always statically allocates terminal devices,
i.e. device nodes for all 7 hvc terminal devices are created. But only the specified
number are active. To help admins to "safely" a getty on a hvc terminal device, ttyrun
can be used. Later, the admin can change the kernel parameters as necessary w/o
worrying about changes in the inittab.
Another use case of ttyrun is enable and start getty programs on s390x terminals. For s390x,
availability of terminal devices depend on the environment LPAR, z/VM, etc. So again, ttyrun
can be used to configure and start a getty program too.
Kind regards,
Hendrik
And, as I'm saying, a magic s390-only program to do this isn't practical - if the admin wants to set up additional terminal devices, they can do it via inittab as normal on all other architectures. ------- Comment From rsisk.com 2010-10-04 10:42 EDT------- Code Upstream Status: No Code Required ------- Comment From mgrf.com 2010-12-13 11:08 EDT------- We will request this feature for R 6.2 again - set to rejected for R 6.1 I think what Bill's feedback here indicates is the entire approach needs to re-thought and not just re-requested for the next release. |