Reactivate swap file generation by Jasper
Bug #627201 reported by
Ricardo Salveti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jasper-initramfs (Ubuntu) |
Fix Released
|
Undecided
|
Ricardo Salveti |
Bug Description
Previously jasper was creating a swap file during the first pre-installed omap image, but got disabled by bug 605739.
As this bug is currently fixed, we should reactivate the swap file creation at Jasper so it can be used by Beagleboard and Panda.
Related branches
lp:~rsalveti/ubuntu/maverick/jasper-initramfs/swap-file-fix-627201
Ready for review
for merging
into
lp:ubuntu/maverick/jasper-initramfs
- Oliver Grawert: Pending requested
-
Diff: 26 lines (+7/-1)2 files modifieddebian/changelog (+6/-0)
scripts/local-bottom/jasper_setup (+1/-1)
To post a comment you must log in.
Proposed fix to re-enable swapfile generation.
Using the same code as before, as we're unable to use a sparse file for swap (swapon: Skipping file /SWAP.swap - it appears to have holes).
The bad thing is that the first boot now takes more 3 minutes to finish :-(
As this change is important for all omap related boards (as we're still using ES1 for OMAP 4), it'd be good to push it and write an exception for Beta release, otherwise none of the Omap images will be ready for normal usage. What do you think Oliver?
For the final release we could study other possibilities to have a swap file and still have a fast installer (maybe creating it while generating the image).