Bug 200264 - ia64 default installs don't work
ia64 default installs don't work
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-26 12:22 EDT by Don Zickus
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-07-26 12:31:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Don Zickus 2006-07-26 12:22:27 EDT
Description of problem:
I installed rawhide 20060725 on an ia64.  Upon reboot, it wouldn't let me in. 
In single user mode, I found out there was no /etc/shadow file.  
Reinstall with some custom selections.  UPon reboot, I can log-in but no
network.  Apparently dhcp-client is not a high priority package.  

Version-Release number of selected component (if applicable):
rawhide-20060725

How reproducible:
Very.


Steps to Reproduce:
1. Try to install with 'linux text'
2. When prompted for packages to include -> select custom, leave defaults,
selecct done.
3. Reboot and try to login.
  
Actual results:
Can't login

Expected results:
Login

Additional info:
It seems the ia64 menu is different than x86_64.  On x86_64, you have the choice
of selecting one of three pre-configured environments (office/prod, development,
something else).  Ia64 doesn't seem to have those choices. 

Is this just the case of ia64 suffering some bitrot until fc6-test2 is out the
door, then pickup the pieces for rhel-5?
Comment 1 Jeremy Katz 2006-07-26 12:31:18 EDT
It's the case that you're installing 0725 on one machine and a different day's
rawhide on another -- and yesterday's rawhide happened to have this quirk. 
Should be fixed in today's

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