Ticket #6188 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

drop mkinitrd and its nasty chain of dependencies

Reported by: bernie Owned by: bernie
Priority: normal Milestone:
Component: distro Version:
Keywords: Cc: cscott, dsaxena, dilinger
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking: #7353

Description

...which include lvm2, dmraid, parted, e2fstools, nash, and a few others I can't remember. A few MBs saving in the image.

The relevant patch is already in olpc-2.6-rpm, and has been reverted due to missing dependencies of initscripts and olpc-utils. These have long been fixed, so I expect a painless experience this time.

Attachments

kernel-rpm-cleanup.patch (14.3 kB) - added by dsaxena 6 years ago.
Remove mkinitrd dependencies from kernel package and remove !OLPC targets

Change History

Changed 6 years ago by cscott

Hey bernie, can we try this patch again? We probably actually want e2fstools, though, since people often use ext2/3 formatted USB keys.

Changed 6 years ago by cscott

  • owner changed from cscott to bernie

Changed 6 years ago by cscott

  • cc cscott added

See also trac #2772, with a long list of other bloat to be dropped.

Changed 6 years ago by cscott

Er, I mean #7353. My bad.

Changed 6 years ago by cscott

  • blocking 7353 added

Changed 6 years ago by cscott

  • cc dsaxena, dilinger added
  • next_action set to never set

Changed 6 years ago by dsaxena

Remove mkinitrd dependencies from kernel package and remove !OLPC targets

Changed 6 years ago by dsaxena

Attached patch remove mkinitrd from the dependencies of the kernel RPM in addition to removing all the non-OLPC targets (PAE, SMP, xen, kdump) that we don't care about at the moment. We may someday want a xen target but we can just bring that in later. Andres, can you apply to your repo?

Changed 6 years ago by dilinger

Patch committed to olpc-2.6-rpm tree, thanks.

Changed 6 years ago by gregorio

  • milestone deleted

Milestone Never Assigned deleted

Changed 6 years ago by cscott

Done in joyride. Can we just close the bug, or do we need to "test" it first?

Changed 6 years ago by dsd

  • status changed from new to closed
  • resolution set to fixed

We can just close it because there is no user-visible impact.

Note: See TracTickets for help on using tickets.