Please add support for using /casper/uImage

Bug #430136 reported by Michael Casadevall
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Low
Unassigned

Bug Description

On architectures that use u-boot, we use /casper/uImage vs. a normal vmlinuz file due to the requirements imposed on u-boot for its kernels and ramdisks. ubiquity should be able to use this file directly vs. requiring a vmlinuz file or leaving one embedded in the squashfs.

Tags: armel
Changed in ubiquity (Ubuntu):
importance: Undecided → Wishlist
milestone: none → ubuntu-9.10-beta
assignee: nobody → Michael Casadevall (mcasadevall)
importance: Wishlist → Low
tags: added: armel
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu):
status: New → Triaged
Changed in ubiquity (Ubuntu):
assignee: Michael Casadevall (mcasadevall) → nobody
Revision history for this message
Tobin Davis (gruemaster) wrote :

Is this bug still active? Can it be closed?

Revision history for this message
Tobin Davis (gruemaster) wrote :

Marking as incomplete. No current arm images use ubiquity in this way. If this is still an issue in future images, a new bug can be created and tracked.

Changed in ubiquity (Ubuntu):
milestone: ubuntu-9.10-beta → none
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.