RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 585397 - Install mode option "text" Is not offered
Summary: Install mode option "text" Is not offered
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-23 21:18 UTC by Gordan Bobic
Modified: 2010-04-23 22:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-23 22:47:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gordan Bobic 2010-04-23 21:18:17 UTC
Unlike in previous versions of RHEL, there appears to be no "text install" option offered in the boot menu of RHEL6 beta. However, if "tab" is used to change boot parameters and "askmethod" is replaced by "text", text mode installer does in fact work.

Since a lot of servers don't have a mouse for a graphical install, and/or might be being installed via a serial only text console, this important installation method option should be clearly offered, especially since it is already built in.

Comment 1 Bill Nottingham 2010-04-23 21:21:25 UTC
text mode install is deprecated, and not fully featured; therefore it's not offered as a first-level option.

Using something like VNC is greatly preferred.

Comment 2 Gordan Bobic 2010-04-23 21:59:38 UTC
In that case there needs to be an alternative way to break out to the command line to run fdisk and mkfs manually. This is pretty much impossible in cases such as installing in a VM using virt-manager. Even if there is a shell running on tty 2, there is no way to access it from the graphical install via virt-manager, since pressing Ctrl-Alt-F2 switches to the HOST's VT 2.

Having full manual control over this part of the install process is vital, especially for making sure partitions are aligned properly on SSDs and other media sensitive to it (e.g. disks with non-standard hardware sector sizes), along with any special mkfs options that need to be applied (e.g. mkfs.ext2/3/4 -b 4096 -E stripe-width=32 for SSDs with erase block size of 128KB).

Comment 4 David Cantrell 2010-04-23 22:47:57 UTC
(In reply to comment #2)
> In that case there needs to be an alternative way to break out to the command
> line to run fdisk and mkfs manually. This is pretty much impossible in cases
> such as installing in a VM using virt-manager. Even if there is a shell running
> on tty 2, there is no way to access it from the graphical install via
> virt-manager, since pressing Ctrl-Alt-F2 switches to the HOST's VT 2.

virt-manager's Send Key menu offers the ability to send Ctrl-Alt-Fx to the virt machine rather than the host system.

> Having full manual control over this part of the install process is vital,
> especially for making sure partitions are aligned properly on SSDs and other
> media sensitive to it (e.g. disks with non-standard hardware sector sizes),
> along with any special mkfs options that need to be applied (e.g. mkfs.ext2/3/4
> -b 4096 -E stripe-width=32 for SSDs with erase block size of 128KB).    

For complex setups like this, kickstart is your best bet.  Once you figure out the commands you need to run for a particular installation doing an interactive install, construct a kickstart file and perform the partitioning and formatting in the kickstart's %pre script.  Then use the kickstart "part" commands to assign the newly created partitions to different mount points, making sure to pass the --noformat option.


Note You need to log in before you can comment on or make changes to this bug.