ProbeForRootFilesystem
⇤ ← Revision 1 as of 2005-10-27 22:05:00
544
Comment:
|
1550
Draft
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
As of Ubuntu 5.10, the boot process relies on a kernel parameter to provide the device path for the root filesystem. This mechanism is subject to failure in the following scenarios: The device containing the root filesystem moves to a different bus, driver, port, or otherwise is recognized by Linux as a "different" device The device containing the root filesystem is relocated from one system to another (especially applicable to removable devices such as USB storage media) The hardware detection process within Linux or early userspace changes in incompatible ways (such as changing the order in which devices on a bus are detected) We should provide a mechanism which is not subject to these problems, while maintaining robustness in the common case (a device which doesn't move). |
|
Line 22: | Line 24: |
* Implement d-i bits to propagate UUID information for FS that supports this feature down the path so that whenever possible we will mount via UUID otherwise use classic system. |
|
Line 24: | Line 28: |
* d-i/partman/fstab |
|
Line 25: | Line 31: |
* None |
Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/foo
Created: Date(2005-10-27T22:05:00Z) by JeffBailey2
Contributors: JeffBailey2
Packages affected:
Summary
Rationale
As of Ubuntu 5.10, the boot process relies on a kernel parameter to provide the device path for the root filesystem. This mechanism is subject to failure in the following scenarios: The device containing the root filesystem moves to a different bus, driver, port, or otherwise is recognized by Linux as a "different" device The device containing the root filesystem is relocated from one system to another (especially applicable to removable devices such as USB storage media) The hardware detection process within Linux or early userspace changes in incompatible ways (such as changing the order in which devices on a bus are detected) We should provide a mechanism which is not subject to these problems, while maintaining robustness in the common case (a device which doesn't move).
Use cases
Scope
Design
Implementation
- One possibility for this is the 'search' command in grub2
- Implement d-i bits to propagate UUID information for FS that supports this feature down the path so that whenever possible we will mount via UUID otherwise use classic system.
Code
- d-i/partman/fstab
Data preservation and migration
- None
Outstanding issues
BoF agenda and discussion
ProbeForRootFilesystem (last edited 2008-08-06 16:24:45 by localhost)