Bug 623707 - RFE use squashfs directly instead of ext3 inside of squashfs
RFE use squashfs directly instead of ext3 inside of squashfs
Product: Fedora
Classification: Fedora
Component: livecd-tools (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Bruno Wolff III
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2010-08-12 11:12 EDT by Bruno Wolff III
Modified: 2011-08-30 23:20 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-08-08 19:04:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bruno Wolff III 2010-08-12 11:12:01 EDT
Description of problem:
Now (kernel 2.6.35, squashfs-tools 4.1) that squashfs supports xattr it may be possible to use squashfs for / directly instead of using ext3 inside of squashfs. (xattr support is needed for selinux support.) This should speed up both creation and use. It's possible that there are some other gotchas.
Comment 1 Fedora Admin XMLRPC Client 2010-10-21 13:53:21 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Bruno Wolff III 2011-02-05 11:10:53 EST
Note that this is going to impact installs from the live image as we will need to run unsquashfs instead of dd and we will not be able to use the resize trick. This will have performance implications. Also there is discussion about using a single way to install for both anaconda and liveinst they may impact this.
Comment 3 Brian Lane 2011-08-08 19:04:21 EDT
During an unrelated chat with wwoods today he mentioned that the extX inside squashfs is needed because we want to be able to do a writable overlay which you can't do with just a squashfs. So I don't think this will happen until squashfs has write support.

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