Revision 1 as of 2007-11-07 19:14:47

Clear message

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

  • Launchpad Entry: foo

  • Packages affected:


This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.


This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

Use Cases



You can have subsections that better describe specific parts of the issue.


This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.



  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

Outstanding Issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

remove: /bin /boot /dev /etc /lib /lib32 /lib64 /proc /sbin /usr /var /sys /initrd* /vmlinuz*

preserve: /home /srv /root

warning saying, "this filesystem already seems to have some contents on it. If you want to go ahead I'll remove everything execept user data, but I'll remove the following:" "There is no guarentee, and you should back up your data." Needs to be a debconf question so OEMs can preseed it.

If the username already exists in /home, check the ID of that directory and use the same id. oem-config does the same thing. We just need to preseed the uid. Check gid as well.

don't worry about /etc/skel, but check user-setup to make sure it doesn't break things in this regard.

make sure /home is not a regular file. Remove it if it exists. It could be a symlink, in which case remove it.

Ignore failures to remove a directory. EBUSY will be triggered if it's a mount point.

Adding an option to the autopartitioner to enable all this functionality. Needs to meet the requirements: swap, ext3.

Logic to remove directories would need to be duplicated into a check for disk space available. Documentation: what we're removing we're not touching /etc/skel