Ubuntu
casper package

plymouth copying progress counter for copy_live_to()

Bug #578109 reported by cleary on 2010-05-10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	casper (Ubuntu)	Triaged	Wishlist	Unassigned

Bug Description

Binary package hint: casper

Hi,
Thanks for reviving the very handy toram option - I've attached a patch to improve this functionality with the addition of a plymouth splash copying progress counter for the copy_live_to() function.

It is based on a similar concept employed by fll-live-initramfs[1] used by the sidux project

Regards,
Bernie

[1]: http://svn.berlios.de/svnroot/repos/fullstory/fll-live-initramfs/trunk/
Specifically, http://svn.berlios.de/svnroot/repos/fullstory/fll-live-initramfs/trunk/scripts/fll
See line 256, fll_copy_with_perc()

Tags:

Revision history for this message

cleary (bernard-gray) wrote on 2010-05-10:

Add progress bar to plymouth splash for the copy_live_to() function Edit (902 bytes, text/plain)

Revision history for this message

cleary (bernard-gray) wrote on 2010-05-11:

screenshot of the progress indicator in action Edit (13.4 KiB, image/png)

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-10-21:

The still applies cleanly.

tags:	added: patch
Changed in casper (Ubuntu):
importance:	Undecided → Wishlist
status:	New → Triaged

Brian Murray (brian-murray) on 2011-10-21

Changed in casper (Ubuntu):
assignee:	nobody → Colin Watson (cjwatson)

Colin Watson (cjwatson) on 2012-05-17

Changed in casper (Ubuntu):
assignee:	Colin Watson (cjwatson) → nobody

Revision history for this message

cleary (bernard-gray) wrote on 2012-05-17:

Can you guys give me some pointers on what I've done wrong with this report that after 2 years, it's
a) not added into the casper codebase
b) not even assigned to anyone

I am deploying ubuntu images to +100 desktops at work, I am working in casper regularly. I have 3 open reports on casper from as far back as Jan 2010 - This is a serious question:

What do I need to do better/differently to get these reports looked at, and dealt with definitively (either applied or rejected) rather than having them sit in limbo for years?

Revision history for this message

cleary (bernard-gray) wrote on 2022-02-04:

12 years in limbo ... fwiw I'm still using this patch in-house for my 20.04 iso